Good post, that all sounds perfectly sensible. The goal should be to avoid needing to rescan music library when changing options anyway.
Get rid of the wizard and make assumptions to set the configuration. But I think upon trying to browse the music library to play something, detect that there's no music in the library, and inform the user that they need to perform a scan (any user interface - web UI, player UI, SBC). I often see complaints (eg. choppy playback), which are due to a background scan that the user is not aware of. The default skin web UI is better now, in that during a scan there is a progress indicator at the bottom of the page. But there's no indication on the player UI, which really matters - after all, that's where new users will be focussed - they want to try their new consumer product and are not so interested in the software. Or at least tell the user that the scanner has started/is active, that it may take some time before they may be able to reliably browse and play music. Phil _______________________________________________ discuss mailing list [email protected] http://lists.slimdevices.com/lists/listinfo/discuss
