1. In SC settings/plugins add checkbox to every incompatible plugin to
load without valid version number.
2. In the startmenu add an entry to start SC without any plugins, just
in case of trouble. Point at this option at 1.
Feel free to file an enhancement request on bugzilla. But IMHO it's
mherger;311813 Wrote:
1. In SC settings/plugins add checkbox to every incompatible plugin
to
load without valid version number.
2. In the startmenu add an entry to start SC without any plugins,
just
in case of trouble. Point at this option at 1.
Feel free to file an enhancement
How is an incompatible plugin indicated today ?
Plugin is incompatible with this version of SqueezeCenter. Please update.
--
Michael
___
plugins mailing list
plugins@lists.slimdevices.com
http://lists.slimdevices.com/lists/listinfo/plugins
mherger;311813 Wrote:
But IMHO it's the wrong way.
After some digging in the forum about plugin issues I agree with you -
bad idea. I like it when programmers keep an eye on usabillity but in
this case you're right, you've to keep the barrier higher. I don't want
to rise the burden on
But IMHO it's the wrong way. People who know what they're doing, can easily
enable any plugin. The others just shouldn't do it. There's a good reason we
introduced version checking.
I agree with your reasoning, that people may call helpdesk/raise bugs when
their problems are due to
I think it's reasonable to allow plugins to run when the MaxVersion is lower
than SC version, but to display warnings. This is what my locl patch does -
it still checks MaxVersion, but logs a warning and continues. It would be
good for possible incompatible plugins to be shown as warnings on
Example of incompatibility between 7.0 and 7.1 and the desirability for
enforced warning with MaxVersion.
In 7.1 with AlienBBC 2.0 - FFWD and REW of Listen Again programs is
broken.
There will be a new version of AlienBBC for 7.1 to support the new
FFW/REW mechanism UI used with Podcast and
So some people have a different opinion of what MaxVersion means - either:
a) The highest version that the plugin has been tested against and deemed to
work.
b) The highest version after which the plugin will not work any more.
I was thinking it was (b).
Perhaps there could be two attributes
The issues of FFWD/REW with AlienBBC highlights two points and I think
it is in regard to working version of Plugins and not testing plugins
with betas of SC.
1. For some users breaking FFW/REW in 7.1 was enough to go back to 7.0
- acceptable compatibility varies by user. So I see the MaxVersion
On 14-Jun-08, at 5:44 AM, adamslim wrote:
How you guys change it I leave to you, but lots of install.xml files
have maxversion at 7.0+, rather than 7+. If point changes are
considered pretty minor, this will catch a few out.
yes, and this was a bit of an error in the initial instructions
You should always consider who do use the product. Is it (1) the geek
already posted 1000 messages in this forum and do know SB, SC ans SN
in nearly every detail *or* is it (2) somebody who only want to enjoy
music and do know very little about computers. I guess it's in most
cases (2).
AND they
A switch in the settings pages to ignore maxVersion would be great. In
this case each plugin developer can decide what to support but still
let the user take the chance and ignore it and run it anyway.
A user who knows better than the plugin author can still edit the
install.xml file. The
@Michael
Just an idea to keep it simpel for non PC geeks.
1. In SC settings/plugins add checkbox to every incompatible plugin to
load without valid version number.
2. In the startmenu add an entry to start SC without any plugins, just
in case of trouble. Point at this option at 1.
Regards
Philip Meyer;310692 Wrote:
I went for choice 3: I modified PluginManager.pm to ignore MaxVersion
checks :-)
How about putting a little test so that if a beta version of SC is
running, the maxversion is ignored (or a switch is enabled in the
webUI), while the maxversion is active for release
adamslim;311199 Wrote:
How about putting a little test so that if a beta version of SC is
running, the maxversion is ignored (or a switch is enabled in the
webUI), while the maxversion is active for release versions?
A switch in the settings pages to ignore maxVersion would be great. In
this
That's what I meant: authors should test against 7.1 and update the
install.xml file.
I still think this is a bit crazy. MinVersion is fine as plugin developers
(probably) know what version of SC is required to support their plugin.
However, MaxVersion should be an optional property of the
However, MaxVersion should be an optional property of the plugin, as
Wait... it is. Put in an asterisk, and it will always be accepted. But
Erland doesn't like this, as it renders the check obsolete. Thus I
explained how it should be done. Which you don't like. But you've got the
choice.
Do you think that plugin developers should always release plugins with
MaxVersion set to represent the version it was last tested against, or
is it okay for developers to release plugins with MaxVersion=*?
As I said: you have the choice to do so. But I wouldn't generally
recommand it.
As I said: you have the choice to do so. But I wouldn't generally
recommand it.
Many plugins have not been published to officially support anything greater
than 7.0. There's not much choice for casual people beta-testing new versions
of SC: either hack the maxVersion in all of the plugins
I've just upgraded my SC from a previous nightly (probably about 3-4
weeks ago) to the latest (20460) and loads of my plugins are reporting
that they are incompatible. Is this new/deliberate? Is there any way
I can disable this?
--
adamslim
Those are my principles, and if you don't like
Check the value of -maxversion- in each install.xml.
To work with 7.1 and higher it should be a value such as 7+
maxVersion7+/maxVersion
--
bonze
TranquilPC T2-WHS-A3 - SqueezeCenter Version: 7.2 - 20482 - Windows
Server 2003 - EN - cp1252
3 x wireless SB3 + a Duet
Check the value of -maxversion- in each install.xml.
...and as you do so please inform the plugin's author to fix this for good.
--
Michael
___
plugins mailing list
plugins@lists.slimdevices.com
http://lists.slimdevices.com/lists/listinfo/plugins
mherger;310022 Wrote:
Check the value of -maxversion- in each install.xml.
and as you do so please inform the plugin's author to fix this for
good.
It isn't really an error, it just means that the plugin author haven't
tested the plugin against 7.1.
If we aren't going to use
It isn't really an error, it just means that the plugin author haven't
tested the plugin against 7.1.
That's what I meant: authors should test against 7.1 and update the install.xml
file.
--
Michael
___
plugins mailing list
24 matches
Mail list logo
