Philip TAYLOR (Webmaster, Ret'd) wrote:
Stanimir Stamenkov wrote: > Sat, 06 Aug 2011 21:47:15 +0100, /Philip TAYLOR (Webmaster, Ret'd)/: >> Robert Kaiser wrote: >> >>> Well, the mass of innovation-resistant people posting in those >>> forums is at least one of the reasons why I moved away my focus >>> from SeaMonkey and work on making Firefox more stable (in terms of >>> not crashing) now. >> >> Understood, Robert. I can quite see that from the perspective >> of a developer, pushing the frontiers of science is a far more >> appealing prospect than a daily grind of bug-fixing and papering >> over the cracks. Unfortunately, from a user perspective, major >> change is rarely welcome, whilst increased security and incremental >> bug fixes are universally appreciated. > > Do you guys clearly understand the SeaMonkey developers > don't get paid for their work on SeaMonkey? This guy understands it perfectly, and is very grateful to those volunteers for their work and efforts on what has, until recently, been a superb suite of software that has formed a central part of his everyday working regime. His concern is that this suite is now evolving in a way and a direction that will make it ever less usable. > Once again - it is all volunteer effort! > Do you understand the maintenance of SeaMonkey > involves various compromises to fit with the ever evolving Mozilla platform? That may well be the reality of the situation, in which case we should be neither surprised nor disappointed to realise that what Seamonkey users want will be given far less weight than what Mozilla and the Firefox team want. Which does not make it any less of a shame. > If you want completely feature frozen product - > just use whatever version you've been satisfied > with at some point in time. However you understand > you can't use just that version because of necessary > security fixes appearing in subsequent releases, or > just because the browser or another component becomes > too outdated to support required latest technologies. > Note, the SeaMonkey developers don't develop these > latest technologies and they can't provide security > fixes to the platform on their own - we (the SeaMonkey > users) are all dependent on the Mozilla platform > (the development of which is mainly driven by the Firefox development). > You can either continue to bitch, Putting a reasoned argument on behalf of those who prefer stability and security to non-essential change is not "bitching"; it is offering a constructive criticism that should be interpreted as such. > or get your hands dirty by keeping track of how the Mozilla > platform evolves, then get some technical knowledge to > understand how this affects SeaMonkey, and then probably > come up with some constructive comments... or code patches > you're ready to maintain. Like most Seamonkey users, I prefer to leave code changes to those who know what they are doing; that should not make my input, as a Seamonkey user since day-1, any less valued. And I have already made some constructive comments, such as o "Why are tabs now being forced on Seamonkey users ?" o "Why are Seamonkey users now restricted to three levels of zoom, compared to eight in earlier versions ?" and o "What is the expected/intended behaviour of the DOM inspector if a wildcard is used as the leading element of a value field in the "Find" dialogue ? ", the latter two of which have elicited zero response.
I don't know the answer to the DOM-inspector question, which is why I chose not to answer it when I read it. That said there is a newsgroup for DOM Inspector in these newsgroups (though much less frequented then SeaMonkey) and it *is* an on-topic question in our group here so I'm not about to ask you to switch either. :-)
Though the "Why ... three levels of zoom" I recall us describing the why many times; Us mentioning a bug #; and (recently) one of our newsgroup readers actually FIXING that "issue" with code and a solution that satisfied our requirements of a localisable Zoom Menu. Sadly I cannot remember for certain which SeaMonkey version is the first to carry that fix, (I *think* 2.4 but I may be wrong)
And lastly tabs, are not being "forced" on our users, they are being enabled by default. And the default menu orderings being changed to reflect that in some cases. [Users worldwide and across many browsers have a strong liking for tabs]. But any piece of our code that does not respect the tab prefs, is a bug and if we are made aware of it, we plan to fix it as soon as possible. [This means that if a tab is *forced* on you, not if we *allow* tabs to be chosen/used, fwiw]
-- ~Justin Wood (Callek) _______________________________________________ support-seamonkey mailing list [email protected] https://lists.mozilla.org/listinfo/support-seamonkey
