They cut out a lot of the Mozilla's best features to make a smaller browser. There is a note in the prefs under advanced saying "your favorite features will be here soon".
Gone:
* Themes. This browser has yellow buttons that look pretty good but a bit bright. You can go in the prefs and rearrange the buttons with drag and drop or choose small icons.
The browser is still themable. There just aren't any themes for it yet. When we get a little further along I'll bet you'll see more themes for Phoenix than for Mozilla (it's about 1/3rd the work to create a Phoenix theme).
* Ability to block popups without disabling javascript.
Wrong. The ability to block popups is not removed. The UI to not block pop-ups has been removed. We just block them rather than expecting the user to dig through a mountain of prefs to turn them off.
* Fine grained cookie management. No more "alert me" and "remember this decision". This isn't removed at all. The pref UI is broken at the moment (read the FAQ). This is an 0.1 release and not everything works yet. Don't leap to conclusions without investigating first.
* Sidebar
We're going to implement a better sidebar. The Mozilla sidebar is slow and difficult to use. Give it time.
* Chatzilla, Mail, Composer
They won't be part of the Phoenix browser. They will be add-ons/plug-ins/extensions. You'll be able to install them into Phoenix if you want them. Not only that but you'll be able to selectively enable, disable and uninstall Phoenix add-ons (unlike Mozilla).
* Site Navigation Bar
Hopefully someone will build a link toolbar XPI.
This is an 0.1 (first) release. It's not done yet. Give it time.
--Asa
Not just looking into the matter. Someone, (bryner), actaully implemented it. Until we get a crasher that happens with particular linux distros fixed it has been disabled in the Mozilla testing binaries. You're free to turn it on in a build you compile yourself.
Not all builds are linked to immediately from the releases page. We link to the builds we have at the time of release.
Sometimes other builds arrive later (all of the 'ports' that mozilla.org doesn't build itself filter in when we point people to the release tag or source tarball and give them the time to actually build it).
In this case it was probably an oversight on my part or the zip build wasn't at ftp yet when endico and I went home for the night. To tell you the truth, I don't remember. It was late.
The recommendation says nothing about your profile. All you have to do is uninstall the old mozilla and install the new one (leaving your profile alone) and everything will be fine.
Clean install doesn't touch your bookmarks and if you installed your plugins into your profile directory you'd be able to hold onto them (or just back up your plugins dir. if you're reading slashdot you should be able to do that).
Try Jesse's Zap embeds bookmarklet. It's not perfect but I've come to depend on it. Just add the bookmarklet to your personal toolbar and whenever you visit a site with an annoying flash ad or java plugin just bonk on the personal toolbar link and the plugin gets zapped.
There are lots of great bookmarklets at Jesse's site. Take a look around and give some of them a try. I couldn't get by without them.
At this rate you should save your bandwidth, and look for 1.2b tommorow night!
Actually, not quite that soon;-) and not 1.2b. Mozilla 1.1alpha, however, is right around the corner. Expect to see it sometime in the next couple of weeks.
I just want to know what program they used to generate that funky [mozilla.org] milestone graph. Anyone know?
I used a combination of Paint Shop Pro and the Gimp. I'm actually interested in finding some kind of CVS graph program that would generate a picture like this from CVS data. It obviously wouldn't be able to predict the future but it should be able to build an image of CVS activity (branches, checkin volume, tags, etc). I have tried in the past to take some cvs measurements and use checkin volume to determine the thickness of the branch lines but it was just too much effort. If something like that could be done programatically I'd be as happy as a pig in shit.:)
Wheres the spell checker? They said it was going to be out with 1.0
Who said it was going to be out with 1.0? Certainly not me. You can get an open-source spellchecker at mozdev.org that works with some Mozilla releases but I'm not sure if they've updated it to work with 1.1beta.
Point me to a cross-platform JavaScript debugger that beats Venkman from 1.1alpha (crossing at least Mac, Windows and Linux would be a good start, throwing in a dozen additional platforms would be impressive).
If you're talking about the venkman that shipped with 1.0 then you're talking about a completely different beast. Seems kind of odd that you'd post about Venkman getting better one day than mozilla1.0 and we're telling you about one day having arrived with 1.1alpha.
Get current, (this venkman is many months worth of development improved from the one that shipped with 1.0) read the how-to/FAQ at http://www.hacksrus.com/~ginda/venkman/faq/venkman -faq.html and then follow-up to this post pointing me to a better cross-platform JavaScript debugger and don't point me to one that doesn't do JS performance profiling because I require that.
mozdev.org is the premier destination for those seeking Mozilla plug-ins, add-ons and enhancements. You can find all kinds of XUL projects, some made to work with Mozilla, some completely unrelated to Mozilla. Have a look, maybe a touch.
Mozilla flash support comes from Macromedia's Flash plugin. The latest Flash plugin just released in recent days supports scripting in Mozilla so the support is coming along well (real is also now scriptable in Mozilla).
The branch will have a subset of the fixes that land on the trunk. It will not have all of the new features that the trunk has, although some of the features will eventually migrate to the branch after they are well tested on the trunk.
Mozilla builds a set of technologies from which end user products can be built. We provide these technologies to everyone but our primary consumers are companies and organizations that use our technologies in their products. The stable 1.0 branch and the 1.0.x releases on that branch are intended for companies and organizations looking for the most stable technologies they can get. The 1.x development trunk is intended for testing large changes and new features as well as working toward a Mozilla 2.0. We intend to have stable points on the 1.x trunk about once a quarter for those vendors who are a little less conservative or need the latest and greatest feature set for use in their products.
So to answer your question, yes, we will have two different development paths but one will be tracking the other as closely as stability will allow. You won't _have_ to choose from anything but if you're interested in helping us test our latest technologies then please grab trunk (1.x) builds and report any problems. If we need help testing builds on the more conservative 1.0 branch then we'll let you know.
3500 unconfrimed bugzilla reports is not the same as 3500 bugs. Think of an unconfirmed bugzilla report as nearly equivalent to a slashdot reader commenting about something he doesn't like in Mozilla or some feature he want's implemented in Mozilla. Until the report has been 'confirmed' then it is not considered a bug in Mozilla. The top of this thread was encouraging people to help us sort through those reports and resolve the bad ones and confirm the good ones. More information on this can be found at http://www.mozilla.org/quality/help/
So get the latest 1.1alpha build (today's nightly trunk build) where this is fixed. If you're willing to test less that 1.0 stability builds you get the latest bug fixes and features.
I run mozilla mail with about 15 folders, only 2 or 3 of which ever have fewer than about 10,000 mails each. I get between 300 and 1000 messages a day and they get filtered to my different folders. Mozilla mail has no problems with my volume.
Slashdot Mirror
They cut out a lot of the Mozilla's best features to make a smaller browser. There is a note in the prefs under advanced saying "your favorite features will be here soon".
Gone: * Themes. This browser has yellow buttons that look pretty good but a bit bright. You can go in the prefs and rearrange the buttons with drag and drop or choose small icons.
The browser is still themable. There just aren't any themes for it yet. When we get a little further along I'll bet you'll see more themes for Phoenix than for Mozilla (it's about 1/3rd the work to create a Phoenix theme).
* Ability to block popups without disabling javascript.
Wrong. The ability to block popups is not removed. The UI to not block pop-ups has been removed. We just block them rather than expecting the user to dig through a mountain of prefs to turn them off.
* Fine grained cookie management. No more "alert me" and "remember this decision".
This isn't removed at all. The pref UI is broken at the moment (read the FAQ). This is an 0.1 release and not everything works yet. Don't leap to conclusions without investigating first.
* Sidebar
We're going to implement a better sidebar. The Mozilla sidebar is slow and difficult to use. Give it time.
* Chatzilla, Mail, Composer
They won't be part of the Phoenix browser. They will be add-ons/plug-ins/extensions. You'll be able to install them into Phoenix if you want them. Not only that but you'll be able to selectively enable, disable and uninstall Phoenix add-ons (unlike Mozilla).
* Site Navigation Bar
Hopefully someone will build a link toolbar XPI.
This is an 0.1 (first) release. It's not done yet. Give it time. --Asa
Not just looking into the matter. Someone, (bryner), actaully implemented it. Until we get a crasher that happens with particular linux distros fixed it has been disabled in the Mozilla testing binaries. You're free to turn it on in a build you compile yourself.
--Asa
In Phoenix do this:
View | Customize Toolbar...
Click and drag the go button up to the toolbar.
Hit the OK button.
Now you have a Go button. Easy, wasn't it.
--Asa
For instance, the new keyboard stuff in 1.2a (ok, it's an Alpha I know), had screwed up Javascript's keydown events....
Say it with me again, slowly this time. "Aaalphaaa". Now, one more time. "Aalphaa". Again. "Alpha". Feeling better? Urge to rant fading? Gooood.
--Asa
Not all builds are linked to immediately from the releases page. We link to the builds we have at the time of release.
l a1.2a/
Sometimes other builds arrive later (all of the 'ports' that mozilla.org doesn't build itself filter in when we point people to the release tag or source tarball and give them the time to actually build it).
In this case it was probably an oversight on my part or the zip build wasn't at ftp yet when endico and I went home for the night. To tell you the truth, I don't remember. It was late.
But don't count on us to be perfect. Just go directly to the ftp directory to see what's really available http://ftp.mozilla.org/pub/mozilla/releases/mozil
--Asa
The recommendation says nothing about your profile. All you have to do is uninstall the old mozilla and install the new one (leaving your profile alone) and everything will be fine.
--Asa
Yes, you do have to click and click and swipe.
If this is your big gripe about Mozilla then you're gonna love 1.1 because it works as you'd expect now.
--Asa
Clean install doesn't touch your bookmarks and if you installed your plugins into your profile directory you'd be able to hold onto them (or just back up your plugins dir. if you're reading slashdot you should be able to do that).
--Asa
http://ftp.mozilla.org/pub/mozilla/releases/mozill a1.1/
If it's not there yet then it's not done yet. Check back later today.
--Asa
Try Jesse's Zap embeds bookmarklet. It's not perfect but I've come to depend on it. Just add the bookmarklet to your personal toolbar and whenever you visit a site with an annoying flash ad or java plugin just bonk on the personal toolbar link and the plugin gets zapped.
There are lots of great bookmarklets at Jesse's site. Take a look around and give some of them a try. I couldn't get by without them.
--Asa
it took them forever to reach 1.0 (although the 0.9 releases were already really good), but now they're releasing a 1.1 after only a short time
We branched for 1.0 around April 09. That day we began work on 1.1. Mozilla 1.1 was finished on August 26. That's more than 4 months of development.
We branched for 1.1 around August 05. That day we began work on Mozilla 1.2. We should be seeing a Mozilla 1.2alpha pretty soon.
--Asa
At this rate you should save your bandwidth, and look for 1.2b tommorow night!
;-) and not 1.2b. Mozilla 1.1alpha, however, is right around the corner. Expect to see it sometime in the next couple of weeks.
Actually, not quite that soon
--Asa
I just want to know what program they used to generate that funky [mozilla.org] milestone graph. Anyone know?
:)
I used a combination of Paint Shop Pro and the Gimp. I'm actually interested in finding some kind of CVS graph program that would generate a picture like this from CVS data. It obviously wouldn't be able to predict the future but it should be able to build an image of CVS activity (branches, checkin volume, tags, etc). I have tried in the past to take some cvs measurements and use checkin volume to determine the thickness of the branch lines but it was just too much effort. If something like that could be done programatically I'd be as happy as a pig in shit.
--Asa
patience. tarball coming soon. it's always a little b it later than the binaries.
--Asa
It depends on if they were using public and frozen or private APIs.
--Asa
Wheres the spell checker? They said it was going to be out with 1.0
Who said it was going to be out with 1.0? Certainly not me. You can get an open-source spellchecker at mozdev.org that works with some Mozilla releases but I'm not sure if they've updated it to work with 1.1beta.
--Asa
Point me to a cross-platform JavaScript debugger that beats Venkman from 1.1alpha (crossing at least Mac, Windows and Linux would be a good start, throwing in a dozen additional platforms would be impressive).
n -faq.html and then follow-up to this post pointing me to a better cross-platform JavaScript debugger and don't point me to one that doesn't do JS performance profiling because I require that.
If you're talking about the venkman that shipped with 1.0 then you're talking about a completely different beast. Seems kind of odd that you'd post about Venkman getting better one day than mozilla1.0 and we're telling you about one day having arrived with 1.1alpha.
Get current, (this venkman is many months worth of development improved from the one that shipped with 1.0) read the how-to/FAQ at http://www.hacksrus.com/~ginda/venkman/faq/venkma
--Asa
mozdev.org is the premier destination for those seeking Mozilla plug-ins, add-ons and enhancements. You can find all kinds of XUL projects, some made to work with Mozilla, some completely unrelated to Mozilla. Have a look, maybe a touch.
--Asa
Mozilla flash support comes from Macromedia's Flash plugin. The latest Flash plugin just released in recent days supports scripting in Mozilla so the support is coming along well (real is also now scriptable in Mozilla).
--Asa
The branch will have a subset of the fixes that land on the trunk. It will not have all of the new features that the trunk has, although some of the features will eventually migrate to the branch after they are well tested on the trunk.
Mozilla builds a set of technologies from which end user products can be built. We provide these technologies to everyone but our primary consumers are companies and organizations that use our technologies in their products. The stable 1.0 branch and the 1.0.x releases on that branch are intended for companies and organizations looking for the most stable technologies they can get. The 1.x development trunk is intended for testing large changes and new features as well as working toward a Mozilla 2.0. We intend to have stable points on the 1.x trunk about once a quarter for those vendors who are a little less conservative or need the latest and greatest feature set for use in their products.
So to answer your question, yes, we will have two different development paths but one will be tracking the other as closely as stability will allow. You won't _have_ to choose from anything but if you're interested in helping us test our latest technologies then please grab trunk (1.x) builds and report any problems. If we need help testing builds on the more conservative 1.0 branch then we'll let you know.
--asa
I wonder if the developers working on the 1.0.x releases will get bored quickly?
They are the same developers that are working on the 1.x releases. Why would they get bored checking in a fix to the trunk and to the branch?
--Asa
Mozilla 1.1 Alpha was not released "days ago". It was released on 2002-06-11 in the late afternoon.
--Asa
3500 unconfrimed bugzilla reports is not the same as 3500 bugs. Think of an unconfirmed bugzilla report as nearly equivalent to a slashdot reader commenting about something he doesn't like in Mozilla or some feature he want's implemented in Mozilla. Until the report has been 'confirmed' then it is not considered a bug in Mozilla. The top of this thread was encouraging people to help us sort through those reports and resolve the bad ones and confirm the good ones. More information on this can be found at http://www.mozilla.org/quality/help/
--Asa
So get the latest 1.1alpha build (today's nightly trunk build) where this is fixed. If you're willing to test less that 1.0 stability builds you get the latest bug fixes and features.
--Asa
I run mozilla mail with about 15 folders, only 2 or 3 of which ever have fewer than about 10,000 mails each. I get between 300 and 1000 messages a day and they get filtered to my different folders. Mozilla mail has no problems with my volume.
--Asa