Most MozillaZine Poll Respondents in Favour of New Roadmap Proposals
Tuesday April 15th, 2003
Our most recent poll questioned you about your thoughts on the new Mozilla Development Roadmap. 1,935 people answered with the majority being in favour of the plans. 58% are fully supportive of the proposals, while 30% are generally supportive but have some reservations. 4% of respondents describe themselves as neutral, 5% are generally opposed but like some of the new ideas and just 1% say they are completely opposed.
#12 Re: i dont think so
Thursday April 17th, 2003 12:05 AM
You are replying to this message
Johan, we'll be including "official" extensions (some off by default in the extension manager) like the DOM Inspector and the JS Debugger. These won't get into "extension hell" or anything like that because they'll be a part of the official process. Providing an "official" build with a few "official" extensions will give Mozilla Firebird browser distributors more choice in what they deliver to their users while allowing mozilla.org to ship something more fully featured.
As for the mozdev and other extensions which are not a part of the official mozilla.org product, they will probably be both good and bad. If there are seven different tabbed browser extensions and you install all of them I can see a situation where you'd have problems. But why would you install more that "just the right one"? Take the tabbed browsing preferences which does far less than TBE and is probably less likely to interact poorly because of a more limited scope. The opposite (I guess) might hold true for the combo extensions like the all-in-one gestures <http://texturizer.net/fir…tml#All-in-One%20Gestures> which combines the mouse gestures, rocker gestures, autoscroll and (I think) more. Doing several features in one extension should cut down on the chances of unanticipated interactions between different feature extensions because they'd all be tested together by the developer and his testers.
I think that we'll have to all get smarter about how we implement and manage extensions. The Mozilla Firebird browser will have to make changes and the extension developers may have to move toward some better model of testing/certification at mozdev (or maybe not). The good news is that we're starting to see some of this change already. One really helpful tool in the Mozilla Firebird browser is the ability to disable without having to uninstall one (or more) extension to see which one was causing problems. Next we need an uninstall API so extension developers don't have to roll their own.
I think it's also worth noting that Phoenix isn't missing so many features that most users will need to install a bunch of extensions to be able to migrate from the old suite. The biggest concern that I've seen so far is preferences and there aren't a bunch of conflicting preference editors (is there more than the toolbar and the preferential extensions?) The other apps like Dom Inspector and Venkman won't be a problem since they'll be in the official builds (possibly off by default extensions). The html sidebar support is underway and will be in the official builds (possibly an off by default extension). Something with functionality for site navigation and alternate style sheet UI will [robably also be in the official builds (possibly an off by default but included extension). Hopefully the other "official" standalone applications will install their own integration points so there shouldn't be any "extension hell" for the integration features.
So what else is there that any large segment of Moz users will want in the Mozilla Firebird browser and need to get from extensions to be able to migrate from Seamonkey?