MozillaZine

Phoenix 0.1 Released

Monday September 23rd, 2002

Asa Dotzler writes: "The first Phoenix milestone, 0.1, has been released. Phoenix is a redesign of the Mozilla browser component, similar to Galeon, K-Meleon and Chimera, but written using the XUL user interface language and designed to be cross-platform. This first Phoenix release includes great new features like a customizable toolbar and quicksearch filtering for bookmarks and history. See the Phoenix release notes for more information or go directly to the builds."


#21 Re: AWESOME but....

by fuzzygorilla

Tuesday September 24th, 2002 8:18 AM

You are replying to this message

It is my personal opinion, that Phoenix is not taking any time away from the core. I feel this for a few reasons. The first is Phoenix *is* a part of the Mozilla project. Work on Phoenix is work on Mozilla, just as work on Netscape is work on Mozilla. This code is going into the same CVS repository with the rest of Mozilla, just a different branch. As the developers stated, they are "using this as a prototype to demonstrate possible optimizations to the trunk" <http://lxr.mozilla.org/mo…ource/browser/README.html> . This is not the first branch for doing development before folding all or parts of the work back into Mozilla <http://komodo.mozilla.org/planning/branches.cgi> . Other examples include the Calendar, SOAP, BIDI, and other important contributions to the Trunk. The work that is being done with Phoenix will have a direct impact on the Trunk. A new wallet, plug-in manager, download manager, etc. would probably not have been developed in the Trunk anyway. They would have needed a branch of their own. The second is that the more consumers of the Mozilla core (gecko, nspr, nss, etc.) the better the code will be forced to become. Using the existing Trunk is new applications helps to uncover ways that the shared code can be improved and made more general. This is an indirect benefit to the Trunk but a benefit none the less. The third is that by demonstrating that XUL can be fast and efficient, with low overhead compared to a native toolkit, more developers will be encouraged to work with XUL. Right now, some perceive XUL to be too heavyweight for use in other tools. Once again, this will not directly or immediately impact the Trunk but it will make the Trunk better in the long run. My final opinion is that I would rather have developers doing things they enjoy and viewing their work as a drudgery or a boat anchor around their necks. By keeping the Mozilla developers interested and productive, this is a big win for the Trunk, since they will continue to do work on problems they find in the Trunk while working on Phoenix. But those are just my opinions.