MozillaZine

Phoenix 0.5 Update

Saturday November 2nd, 2002

Blake Ross has posted a message to the Phoenix General forum that includes details about Phoenix 0.5. The 0.5 release will take a little longer than previous milestones because the developers see it as a "transition milestone" that begins the push towards 1.0. Post-0.5, the team plans to select a new default theme, icon and logo and also set up a new Phoenix website.


#1 Releases coming fast?

by googolplex

Saturday November 2nd, 2002 7:08 PM

Reply to this message

Wow, they just keep cranking out new releases...

I wonder what their defintion of long is. All the other releases were quite quick.

#2 take your time....

by whiprush <jorge@whiprush.org>

Saturday November 2nd, 2002 11:25 PM

Reply to this message

Phoenix has been cranking out releases ... with 1.2 around the corner, this gives us a breather!

#3 a month ago..

by macpeep

Sunday November 3rd, 2002 2:11 AM

Reply to this message

.. I was laughing when people were going "Phoenix is going to be the real IE killer". And yes, I had tried it and tested it.. Yesterday, I installed the nightly build and quickly replaced the default theme with Qute (I *hate* Orbit's icons for some reason.. probably the colors and the stop-button that seems so out of place) and I must say I was extremely positively surprised. With a more neutral default theme that nobody will hate (something along the lines of Mozilla's Classic, Qute or Luna) and all the missing features (such as the password manager UI, missing preferences options etc.) and a liiiitle bit more stability and we're having a *real* killer app on our hands!

Now the question becomes, how do we get the rest of the world to find out? I've always followed Netscape and Mozilla closely, even before Netscape's first 1.0 release back in 1994 (or 1995 or whatever). And even I was very sceptical about Phoenix, even with my knowledge about who was working on the project and what the goals of it were (which are goals that I agree with 100%). Perhaps there's some need for some really distinct separate branding from Mozilla. Basically, I'm suggesting that a really clear Phoenix brand be established, naturally so that it's clear that it's based on Mozilla, but so that there's a clear website to go to and link to when some site does a review of Phoenix and people come looking for more information. This hypothetical site would not be in the form of a zine but more along the lines of a traditional company software product web page.

#4 Totally Agree

by TonyG <tony.gorman@blueyonder.co.Yuk>

Sunday November 3rd, 2002 10:28 AM

Reply to this message

Phoenix is a very important step in the *zilla evolution and could really take off with the right marketting.

A nice them, distinct icons and a dedicated site will all help sell Phoenix.

Perhaps Microsoft can be persuaded to bundle Phoenix on the Windows desktop, now it is a chastened company :)

#5 Re: Totally Agree

by ezh <ezh@menelon.ee>

Sunday November 3rd, 2002 3:26 PM

Reply to this message

Hmmm, Netscape may release Netscape 7 Lite...

#6 Totally Agree

by TonyG <tony.gorman@blueyonder.co.Yuk>

Sunday November 3rd, 2002 4:59 PM

Reply to this message

Is that based on any sort of possibility? Be nice if it was...

#7 Snap

by rwc

Sunday November 3rd, 2002 8:07 PM

Reply to this message

I'm a Big Fan of Phoenix and Mozilla (made the decision to install the latter on several hundred PCs in a public library serving about 400k residents), I followed Netscape from 0.9, yadda yadda, so I'm asking as a friend: will any Mozilla-ish browser ever approach snappyness? Here's my definition of snappy: On a 1Ghz Pentium-III w/ 256MB RAM under Windows 2000, Opera gives the impression on cached and "local" pages up to about 50k in size with a few images (from servers on the same LAN as the browsing computer), that the page is displayed even before you have a chance to take your finger off the mouse button (or alt-arrow key). Well okay, if you're spastic about it you can remove your finger before you see the page, but only by a few tens of milliseconds. How about another unit of measure, the Blink. (Hey, if Swatch can make a "Beat", I can make a "Blink".) Using the same configuration as above, cached or local pages on Opera take about one Blink to load (I close my eyes and simultaneously click a navigation button, then open my eyes as quickly as possible and the page has in most cases already loaded). The same navigation pattern on Mozilla-ish browsers takes 2-4 Blinks to load pages. An unchromed Mozilla is somewhat faster than a chromed one, but still doesn't approach Opera's speed.

I heard that after Mozilla 1.0 was released, there was going to be a really serious all-out gung-ho effort towards improving all-around (but especially rendering) performance, but I can't say I've really seen any difference in the past five months. Phoenix has certainly provided SOME improvement however.

Now for my stupid look-into-your-crystal-ball question: will any Gecko-based browser even come close to Opera's rendering speed? Mozilla doesn't. Phoenix doesn't. K-Meleon doesn't. Netscape 7 doesn't...

#8 Re: Snap

by bzbarsky

Sunday November 3rd, 2002 10:32 PM

Reply to this message

The performance effort is going on. It doesn't help that everyone involved is working on Mozilla _very_ part-time... That said, it _is_ happening, though it may be a few months yet before it produces any really noticeable results.

I think a better question is how Opera 7 (With its promised DOM support) will compare with Opera 6 and Mozilla... I'll be very impressed if they pull off not making it slower as they add the DOM support. :)

#9 Re: Snap

by mesostinky

Sunday November 3rd, 2002 10:34 PM

Reply to this message

Personally I don't see much difference in rendering speed between Opera and Moz. I've used Opera as recently as a few weeks ago and I just didn't think it had much of an advantage speedwise. Opera does have an advantage on low end hardware no dount, but that's about it. Plus all other things considered Mozilla is just all around a superior browser. Of course that's just IMHO, but I having tried everything else around that's just the conclusion I've come to.

#12 The difference...

by rwc

Monday November 4th, 2002 11:49 AM

Reply to this message

See <http://burlco.org/moz/> and view the "simple" and "less simple" pages (admittedly you probably wouldn't come across pages like these during daily browsing). Once cached, navigate back and forth between the two pages using a Gecko-based browser, then try it with Opera. I reckon that rendering the cached pages is about two orders of magnitude faster with Opera, using the same hardware I mentioned before (1Ghz Pentium-III w/ 256MB RAM under Windows 2000).

#11 Re: Snap

by Balboa

Monday November 4th, 2002 2:02 AM

Reply to this message

I'm trying to think of a positive way of stating this, but aside from speed, the Opera 'engine' still has a long way to go, in terms of DOM support, and fuller CSS. Not to mention it costs money! (*gasp*!)

#10 Turning off annoying features?

by alehmann <aaronl@vitelus.com>

Sunday November 3rd, 2002 10:56 PM

Reply to this message

I've been pretty disappointed so far with the Phoenix releases, actually. I'm extremely picky about my browser, and my acquired taste is pretty close to Netscape 4's UI. I was originally excited about Phoenix because it promised to be a leaner, meaner Mozilla, but in the last release I tried there were more features turned on than in my Mozilla prefs but in Phoenix there was no way to turn them off. I realize that Phoenix is still in early development, but is a full set of preferences on the way? If I can't turn off things like that menu of choices that pops up when you type something in the URL bar (thanks IE for the inspiration?), I'll frankly be happier with the full Mozilla.

If it's merely the prefs UI that is incomplete but there is some way I can change a file and get rid of the "features" I don't want, that works for me and I would be glad if someone could point me to documentation if there is any, or give me some basic tips on what to change and where. The biggest gripe that I can remember is the URL completion, but there may have been others.