kdf;426882 Wrote: > > 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
kdf, I understand exactly what you're saying... I showed the post to my wife and she looked at me as if it was written in a lost ancient language. I think I'm familiar with the SC interface and I also understand the modularity that plugins bring into the mix... I just don't find this specific function of the server to be very user friendly. I can live with its complexity, but I assure you that others find it confusing. -- tamanaco ------------------------------------------------------------------------ tamanaco's Profile: http://forums.slimdevices.com/member.php?userid=4620 View this thread: http://forums.slimdevices.com/showthread.php?t=63623 _______________________________________________ beta mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/beta
