Jens Hatlak wrote:
Rufus wrote:
If a *user* has to be savy enough to hack code to get a
"finished" product to work, then that product isn't "finished".
You don't have to hack anything to use SeaMonkey. Some extensions need
minor tweaks to make them work. By your own logic, these extensions are
unfinished, not the product. Extensions may be a vital part of our
ecosystem, but they are not under our (direct) control. We know there
are issues, but there are efforts to minimize the impact as much as we can:
1. The Add-on Compatibility Reporter allows you to install any add-on
that has been declared compatible with an earlier version of SeaMonkey
(well, starting with 2.0, since that marked the beginning of the new
install system support) *and* report to the add-on authors whether it
still works or not.
That's a nice feature.
2. We created a Wiki page that lists add-ons and their state of
compatibility: <https://wiki.mozilla.org/SeaMonkey/2.1/AddonCompat>.
That list is actively maintained. While it may not list all your
favorite add-ons, it allows you to easily see whether their state is
known or not. Granted, it's still for SM 2.1, but given the very few
changes between 2.1 and 2.2, I'd expect all add-ons that worked with 2.1
to work with 2.2 as long as the Add-on Compatibility Reporter is installed.
I currently have 93 add-ons installed, 66 of which are active, and the
vast majority of those is either directly compatible with SM 2.2 or just
needed the Add-on Compatibility Reporter to be installed first.
Great job there, too...but...
If I have to use or even know anything about about:config to get
something in SM to work, that's a "hack". That's the sort of thing I
was referring to. Not documentation.
Actually, I miss all of the features that the 1.1.x series included. I
didn't use the Forms Manager, but I get the impression that enough
people miss it to put me on their side.
So you acknowledge that you never used it, but still that determines
that you don't like the change. That's ill logic. I'm not saying this is
a non-issue, but it should be for you!
I said I didn't like the change(s) between the 1.1.x series and the
2.0.x series - all of which I *have* and do use, in the case of 2.0.14.
But I'll add that I've read enough complaints here that I'm not even
interested in trying the 2.1 or 2.2 because too many people are saying
that too many things I depend on are broken. I'll wait for 2.3+, and
only then after I upgrade to Lion.
Anyway, Philip Chee was kind enough to make the Autofill Forms extension
compatible with SM 2.0 and AFAIK it still works with SM 2.2. Problem
solved.
HTH
Jens
That's great for that issue, but that's just one problem, and it's an
issue that doesn't apply to me because I don't/won't use the Forms
Manager in any browser for the reasons I've detailed previously.
--
- Rufus
_______________________________________________
support-seamonkey mailing list
[email protected]
https://lists.mozilla.org/listinfo/support-seamonkey
