Jens Hatlak wrote:
Rufus wrote:
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.
Sure. But that's as good as we can get. We cannot force the add-on
authors to do anything. We cannot change the add-on install back-end
because it's part of the platform (well, some knowledgeable developer
could fork the code, but no-one has the time to maintain that!).
That I can also understand - a sort of "vendor lag" that's common with
any major software rewrite.
So we only have two alternatives:
a) Say that whatever is incompatible is just that and be done with it.
Not our fault, not our problem. Deal with it. If you want to get
something to work, find out yourself.
b) Try as good as we can do document the state of affairs and what you
can do in the different cases. Ask add-on authors to update the
compatibility of their add-ons. Tell everyone to use the Add-on
Compatibility Reporter in order to help the process.
Yeah - I'm ok with that. And good on ya for the write ups....that makes
it easier for someone like myself to determine if/when it's advisable to
move up based on their own personal requirements for usage. In my
personal case, it's not prudent for me to update at this point based on
what I need the program to do for me.
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.
Fair enough. But be told that 2.3 and probably also 2.4 will not contain
too many changes beside *some* bug fixes. With the rapid release train,
releases come more frequent, but that also gives us much less time to
fix things (or work on features, which takes even longer).
HTH
Jens
Again, I'm mainly interested in *features* and how the interface will or
won't be changed to accommodate the full-screen app implementation in
the coming Mac Lion OS. I think that bothers me more than anything else
because it is seriously going to alter my work flow for more than just
SM - total elimination of PPC and Rosetta support being another huge
concern for me.
In the case of SM, I would think that the way around it would be opening
SM Mail in a tab in the same window - which I recall hearing is on the
road map, but I don't recall anyone saying just when I should expect it
to appear. But I expect tabs within an app window will end up becomming
the new "window" under Lion.
--
- Rufus
_______________________________________________
support-seamonkey mailing list
[email protected]
https://lists.mozilla.org/listinfo/support-seamonkey
