Philip Meyer;603195 Wrote:
>
> What I think should be done is add provision for another version
> property (eg. maxTestedVersion). If maxVersion is exceeded, the plugin
> should not run/install. If maxTestedVersion is exceeded but maxVersion
> isn't, allow the plugin to run, but warn that the plugin may not be
> compatible.
>
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 have no idea
if tomorrows 7.5.3 nightly is going to break my plugins so I can only
mark set maxTestedVersion to the official 7.5.2 release since that's
the only version I've tested them with. To be honest, I can probably
only set them to 7.5.0 because that's the only version I've personally
really tested all functionality with.
Sure, I can also set my maxTestedVersion to 7.5.* and hope that
Logitech won't introduce anything that breaks anything in all the
methods I call in my plugins in nightly minor releases.
I can never mark them as tested with 7.6.* until 7.6.0 is released, so
everyone running nightly for the next major version is going to get all
third party plugins marked as incompatible.
A possible issue with a setup like this is that all users that
immediately upgrade to a new production release is going to see all my
plugins as incompatible because it usually takes me a few days/weeks to
ensure that I've verified that every thing still works correctly after a
new major release has been published.
I'm not against introducing a maxTestedVersion but I'm not sure it's
going to solve the problem, the reason is that it's not going to be
accurate for all plugins due to the fact that the third party
developers does this on their spare time.
Philip Meyer;603195 Wrote:
>
> 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.
--
erland
Erland Isaksson ('My homepage' (http://erland.isaksson.info))
(Developer of 'many plugins/applets'
(http://wiki.slimdevices.com/index.php/User:Erland). If my answer
helped you and you like to encourage future presence on this forum
and/or third party plugin/applet development, 'donations are always
appreciated' (http://erland.isaksson.info/donate))
------------------------------------------------------------------------
erland's Profile: http://forums.slimdevices.com/member.php?userid=3124
View this thread: http://forums.slimdevices.com/showthread.php?t=84697
_______________________________________________
beta mailing list
[email protected]
http://lists.slimdevices.com/mailman/listinfo/beta
