Bill Davidsen wrote:
JD wrote:
Bill Davidsen wrote:
Robert Kaiser wrote:
JeffM schrieb:
...then there is Google included an actual API for extensions
in their Chrome Browser.
There's an "Add-On SDK" for Mozilla software that does the same. Still,
add-ons built with that only or the Google Chrome API can do so much
less than full-blown add-ons for Mozilla products that I don't expect
all add-ons to switch to using it.
The thing is, in most cases the add-on didn't break, it just needs to
have install.rdf updated. And that is really hostile to users, when a
pop-up could ask if the user wanted to install and warned that it might
break things. That is so much safer than having users unpacking,
modifying, repacking, and then trying an add-on.
Follow this logic: not only are there more users who can figure out a
[TRY IT] button without messing up, but the number of people
distributing hacked versions of add-ons would drop to zero. Sooner or
later someone will figure out that offering an "updated" add-on is a
great way to slip in malware.
These are the prices you pay for being a pioneer:
Not just for being a pioneer, but also for allowing many more
degrees of
freedom that others.
Could you at least hint WHY a working "disable compatibility check" in
button or about:config form is not available, while developers tell
people to hack the add-on which has higher risks. The add-on manager
whines that compatibility checking is disabled, but clearly it isn't. At
least a button would force the user to consider the issue before blindly
hacking install.rdf.
It's really not a difficult "hack" to change a install.rdf file. More of
a minor "edit." I'm talking about my old add-ons that were deemed
incompatible with SM2.1. Hacking the install.rdf in a .xpi file is a
little more difficult but still not that difficult.
I suspect that the average user will not even know the steps.
- download the xpi file
- unzip
- edit with an editor which doesn't mess up a plain text file
(from experience, Windows users use Word and HTML)
- rezip
- find the "install from file" feature
as opposed to
- click [TRY INSTALL ANYWAY]
It's easy to forget how many people use SM because it provides news,
mail, browse, chat, and compose, without learning five programs. And how
large the bozo-American subculture really is. :-(
I'm not taking sides and I'm not saying anything about what you're
saying. I'm just saying what I'm saying. Enough said.
Taken as such.
JD wrote:
>> Hacking the install.rdf in a .xpi file is a
>> little more difficult but still not that difficult.
And i cannot agree. It difficult for most of people. And sometimes did
not give the solution.
When i passed from 2.0 to 2.1, i had the problem with
spelling-french-addon which is incompatible with SM 2.1 - So i modify
it, and it was installable, but we cannot use it - The day after a new
version was installable and works ok.
_______________________________________________
support-seamonkey mailing list
[email protected]
https://lists.mozilla.org/listinfo/support-seamonkey
