JJZolx;248498 Wrote: > The part that interests me the most is having a 'default' (master) > player from which all new players will take their settings, as per 'bug > 726' (http://bugs.slimdevices.com/show_bug.cgi?id=726). > > Could this really be done as a plugin?
I think so. The plugin init routine would note the known players (not connected players, but players with prefs; this might involve some hairy direct parsing of the YAML files, but should be very doable), and register for new player events. When a new player event fires, see if that player has been recognized. If not, start creating pref objects and setting values based on the chosen default set. There are some concerns about how 3rd party plugins deal with preferences. They ought to always use the prefs APIs for accessing prefs values, but right now it'd probably be fairly safe for plugins to read values at startup, stash them in local scalars, and not refer to the prefs API unless the user used that plugin to change the value. Any solution like SettingsManager that allows changing a plugins' prefs would require that plugins use the prefs API every time they need to use a value that's stored in a pref. Most that I've read do always use the official API, and should be safe. And any plugin that allows users to edit prefs (the way, say, Firefox's about:config lets you relatively easily view & edit all the Firefox named prefs) would mean that 3rd party plugins might want to include internal consistency checks. > It would be desirable to have different defaults for different types of > players. Hardware vs. software, or possibly 'local' (on the local > subnet) and 'remote' players. New software/remote players will nearly > always be connecting across the Internet over a connection that can't > sustain a lossless stream. As it stands currently, when I connect to > the server remotely using a software player from a new IP address I > can't even listen to music until I go in and set a bitrate limit for > the new player. Right, that's what I called the "web" settings. If the player is not a slimp3/squeezebox/squeezebox2(3)/transporter, it'd be "web". It would be nice to have an option to have different defaults for different types of local/native players (slimp3/sb/softsqueeze/transporter). I'd flag that as Phase Five. > One important need is to be able to view, edit and delete settings for > all known players, whether or or not they're connected to the server. > This is 'bug 429' (http://bugs.slimdevices.com/show_bug.cgi?id=429). > Right now, for instance, there's no way to delete orphaned players, > other than to stop the server and carefully edit the prefs file. Now, who has time to tackle this? :-) -Peter -- peterw http://www.tux.org/~peterw/ free plugins: http://www.tux.org/~peterw/#slim AllQuiet BlankSaver BottleRocket FuzzyTime SaverSwitcher SleepFade StatusFirst VolumeLock ------------------------------------------------------------------------ peterw's Profile: http://forums.slimdevices.com/member.php?userid=2107 View this thread: http://forums.slimdevices.com/showthread.php?t=40924 _______________________________________________ plugins mailing list [email protected] http://lists.slimdevices.com/lists/listinfo/plugins
