Normal
that's an impressive piece of xml you just made up.I thing this is absolutely useable.some problems/suggestions:- I think favourite handling shouldn't be in the published list on the internet location. Favourites are personal, so this should be on your local machine.- the menu system is absolutely useable. I think that this isn't the hardest part to come up with. Perhaps when a lot of people are uploading to this list. it's better to split the list in multiple files, each with their own url. Perhaps by country/genre/mediatype/...- perhaps it's possible to generate more than one xml file and use the same technique as PCZapper does. their menu system is build on multiple xml files/urls that form their own menu structure. There is a main menu that's just an xml file with links to other xml files. an xml file can have links to media streams and/or links to other xml files (like sub menus).that's an easy to manage tree system.of course someone needs to host it on a website. If this is going to be a full functional plugin, I think a lot of people will be using it, so the website is going to need enough bandwidth to support it (if it's going to be a success...).
that's an impressive piece of xml you just made up.
I thing this is absolutely useable.
some problems/suggestions:
- I think favourite handling shouldn't be in the published list on the internet location. Favourites are personal, so this should be on your local machine.
- the menu system is absolutely useable. I think that this isn't the hardest part to come up with. Perhaps when a lot of people are uploading to this list. it's better to split the list in multiple files, each with their own url. Perhaps by country/genre/mediatype/...
- perhaps it's possible to generate more than one xml file and use the same technique as PCZapper does. their menu system is build on multiple xml files/urls that form their own menu structure. There is a main menu that's just an xml file with links to other xml files. an xml file can have links to media streams and/or links to other xml files (like sub menus).
that's an easy to manage tree system.
of course someone needs to host it on a website. If this is going to be a full functional plugin, I think a lot of people will be using it, so the website is going to need enough bandwidth to support it (if it's going to be a success...).