mherger;619125 Wrote: > > We're still missing 'Additional Playlist Buttons' from the web UI. > > One of the onebrowser goals was to get rid of UI specific handling. > Which means instead of adding those buttons we should probably think > about adding a way to bring up an item's context menu. This would cover > the mixer issue as well.
That doesn't sound like a very user friendly solution. So there would still be 'Play' and 'Add' buttons, but 'Play Next' would be on some kind of context menu? The goal as I understood it, was to simply to make browsing by the different methods more consistent in the data seen by the user. And in the process to also fix several dozen SqueezePlay browsing mistakes that were made during development of the Duet, Touch and Radio. I guess I don't see how the database queries being run and the data being returned to SP, the ip3k UI, the web UI, the CLI has anything to do with how that data is presented in a specific UI. There must be differences in how the data is handled by each of them. This was my greatest fear about onebrowser - that the web UI would take a fairly large step backward because it would present things more like SqueezePlay, which is a rather primitive interface in comparison. -- JJZolx ------------------------------------------------------------------------ JJZolx's Profile: http://forums.slimdevices.com/member.php?userid=10 View this thread: http://forums.slimdevices.com/showthread.php?t=85895 _______________________________________________ beta mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/beta
