Bugzilla – Bug 1386
Live365 to use INPUT.* modes for browsing
Last modified: 2008-09-15 14:39:24 UTC
other plugins do though (shoutcast, radioio) but also the behavior between these plugins could be more consistent. shoutcast lets you enter a discrete number to jump to whereas radioio does the percentage thing where 1 = 10% through 2 = 20% through etc...
have received another complaint about this...
Now that radioio and shoutcast both use the INPUT.* modes for list handling, the one remaining is really Live365
kdf - how hard is this to do?
There is a lot of conversion to do, as this plugin in particular has never really been written in a way that is more common to slimserver code. It's hard to read, being used to a very different style of writing. On first inspection, i tlooks like at least 3 modes that must be converted. I can give it a go, after some whitespace cleanup.
Looks like it isn't too bad. Main mode and search took only a few mins. Genre and channel listings wil take a bit longer, but probably not by much. assigning to me
first run done in change 8528
change 8546 finishes the work on this. INPUT.List is used at all levels. The feed is XML, but doesn't seem to work with the xml browser (not sure why). Genre level is sorted, so we use teh alphanumeric jump. Channel lists are not sorted, so the numeric jump is used by the INPUT.List !isSorted. I suppose hte ideal would be to use xmlbrowser, but that might need something from live365 end in the form of an opml, or squeezenetwork hosted conversion like what appears in Shoutcastbrowser. adding andy as cc for this last msg just in case it inspires...cause I'm just THAT motivating ;)