> The Extension Installer should not even be a plugin... it should be a > basic "native" function of SC that can be enabled/disabled.
This is exactly what it is. Just that anything that can be, as a module, enabled or disabled is handled through the plugin API. "Native" plugins are Slim/Plugin/* modules, while third party are installed in Plugins, or the cache (in the case of installation using ED). I highly doubt it would be perceived as all that much "simpler" if there were two pages for accessing enable/disable of featuresets. Much of the functions you know are done through the plugin API now simply because it's matured into a API that can simply hook into the various UIs and maintain a feature set in one module. Examples: song scanning, favourites UI, Random Mix, and most of the online music services. -kdf _______________________________________________ beta mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/beta
