>Might be a good idea but it means that for everyone running a nightly >more or less all plugins will be marked as incompatible. > I'm not sure "incompatible" is the right word. I was thinking more of a warning that the plugin is "Not Tested", "Not Verified for this point release", etc. i.e. people running a SBS beta release will be able to run the plugin where the developer has no reason to doubt that it won't work, but the beta test user should be aware that the plugin might not function correctly.
>> Perhaps automatically change logging level to debug, or something like >> that. >> >Bad idea, this will fill all beta testers hard drive and make the >performance really bad when some plugins are activated. It could >possibly change the logging level one level below the default but not >to debug. Personally I think indicating that the plugin is incompatible >in the plugins page would be good enough, before and after it has been >installed. > Yeah, I wasn't convinced myself that setting to debug would be a good idea. I'm not sure if SBS could know enough about a plugin's logging config to be able to automatically change it anyway (there's no fixed relationship from a plugin name to log category name, and nothing to stop a plugin setting up more than one log category, etc). However, my experience is that most plugins don't log much, even in debug mode, and that it doesn't affect performance much. The default level is "Error" I think? If possible, switching to Warning level might be a good idea. _______________________________________________ beta mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/beta
