the point here is mozilla made a big hype of opensourcing main browser code and is way behind schedule
mozilla didn't make a big hype about much of anything. mozilla, defined as the people contributing thousands upon thousands of hours making Mozilla, have been too busy to hype anything. Netscape and the press made a big hype of opensourcing the Communicator 5 sourcecode. mozilla (remember, the people actually working on this project) made very little hype when they started scrapping large chunks of the Communicator code and building an new set of apps from the ground up. mozilla (remember, the dedicated contributors, paid and unpaid, who have been busting their butts to make something useful) didn't make a lot of hype when the first major commercial Distribution was releases. They were too busy trying to make it better. mozilla (those people fixing the bugs you reported) didn't make a big hype about anything.
But they should have had a browser out (moz 1.0) and converted into that mozilla-os platform in ver 2.0.
So you'd be thrilled if mozilla (those folks working to make a free and open source browser for you) had decided to drop support for everyone except win32 and had instead focused on building a simple win32 browser around the old Communicator codebase which neither supported the standards nor had any future (as a codebase) beyond 5.0. You think that it would have made better sense to have build a so-so win32 only Communicator 5 suite and and then a year or two later scrapped that codebase and start all over again on a 2.0 which was cross platform.
I think that the piece of the puzzle that you're missing here is that the decision to scrap the old codebase and move over to this 'yet another crossplatform appdev platform' means that Mozilla can be built for mac, or linux, or BSD, or solaris, or win32, or hpux, or BeOS, or irix, or AIX, OpenVMS, OS/2, True64 and others. Sure, mozilla (those folks giving you a free and open source, standards supporting, fully featured internet application suite with support for DOM, CSS, HTML, mathML, SVG, bi-di, XSLT, SSL/TLS, simplified I18N and L10N, and a set of technologies that help you to build your own networked apps like forumzilla, xmlterm, protozilla, galeon, kmeleon, nautilus and others) could have scrapped the idea of making something really useful and focused on a win32 browser to compete with MS for the windows desktop (a futal effort in my opinion) completely throwing out the tradition of supporting linux and other non MS operating systems. mozilla (they're the good guys) could have done a lot of things differently but I suspect that folks would have criticized them for whatever the decisions were and I'm personally pretty happy with the results of the decisions as they were made.
You don't need to know c++ do contribute to mozilla. Visit irc.mozilla.org #mozilla and #mozillazine for pointers to non c++ coding (javascript, XUL, CSS, etc).
On or about september 22 a development branch called MN6 was cut from the Mozilla trunk. This branch was a slower moving branch that resulted a couple months later in the Mozilla code which was at the heart of the Netscape 6 product.
a couple weeks after the MN6 branch was cut there was a Mozilla Milestone made from the trunk. This was M18. The next trunk Milestone was 0.7 in early January and the latest tunk release is 0.8
There are a couple easy things you might try to work around this problem. First and easiest is to create a new Mozilla profile. To do this simply run mozilla.exe" -profilemanager and it should launch a profike manager window. Create a new profile in that window and you should be good to go. If that doesn't do the trick (if the profile manager won't launch) then the next thing you might try is to remove your Mozilla/ directory in winnt/profiles/user/applicatin data/ This folder contains a component registry file and your old mozilla profiles (note, this will destroy previous profiles and the data they contain including bookmarks, mail, etc). Then reinstall mozilla and try to run it again. If these steps don't work then please visit Bugzilla and file a bug with clear steps to reproduce your problem and all relevant mozilla install and system information.
Of course, the people at Mozilla were just saying don't set the version 0.8 as the default browser - perhaps they're simply recommending waiting a few builds for more bug fixes.
um. no the people at Mozilla did not say that. a guy from the webpages mozillaquest.com said that.
To load the JRE you'll need to have the latest SUN JRE on your system. Then it's as simple as creating a symlink in the/mozilla/plugins/ directory pointing at the JRE OJI plugin.
Blackdown's JRE was working for some folks last I heard so if you've got that give it a try.
mozilla.org did not release Protozila (or Protozilla). This is an independent project that is being developed at mozdev.org. mozdev.org is not a part of mozilla.org.
From the mozdev front page:
mozdev.org is the location for development projects based on the open source Mozilla project. Anyone interested in Mozilla is welcome to look around and try out any of the more than 20 projects hosted on this site, and anyone working on a project is welcome to host their development here free of charge.
The projects currently on mozdev.org include a number of the development projects that Alphanumerica had been developing. After Alphanumerica's merger with CollabNet these development projects were integrated with SourceCast, CollabNet's project hosting tool, to create mozdev.org.
While this project is not being developed (or released for that matter) from within mozilla.org itself, it and other projects at mozdev demonstrate how mozilla technologies can be used and extended and how the community of mozilla developers has and continues to expand "beyond the browser".
--Asa
no it wouldn't be legal. the editing and distribution wouldn't be the problem. the filming of a minor who isn't old enough to give consent is the problem.
this will probably be fixed in the next day or two on the trunk either with that patch or by backing out that revision. We took the easy route on 0.7 and just bakced out the revision that was causing the problem.
both are still in the source. Previous mathml and svg enabled builds were contributed to mozilla.org by interested folks in the community. If they don't show up sometime in the next couple of weeks ping me and I'll ask around. The win32 mathml & svg enabled build was contributed by a regular build contributor so I imagine that will show up soon.
Actually, that's just some of what's new. That list highlights some of the features that users are likely to notice right off. For a more comprehensive list you might try a bugzilla query something like the 1500 or so bugs fixed since around Mozilla 0.6
It's not a perfect query since a few of those were in M18 and not in 0.6 and vise versa but you get the picture.
--Asa
mozilla is looking for contributions of bulds on platforms other than linux, mac and win32. See http://mozilla.org/build/distribution.html
for info on how to contribute builds to mozilla.org.
Do a little research. Look at the records of the Democrat science and technology leaders in the Senate:
John Rockefeller IV (D-WV)
John Kerry (D-MA)
Richard Bryan (D-NV)
Byron Dorgan (D-ND)
Look at the Democratic House members vocal in science, technology and space.
Jane Harman (D-CA36)
Mike Ward (D-KY3)
Ralph Hall (D-TX4)
James Traficant (D-OH17)
Tim Roemer (D-IN3)
Bud Cramer (D-Al5)
James Barcia (D-MI5)
Alcee Hastings (D-FL23)
Shelia Jackson Lee (D-TX18)
William Luther (D-MN6)
Take a look at their voting records. I'm not arguing that you won't find Republicans there and some of them even voting to make NASA stronger but the "friends of NASA" are most definitely Democrats.
President's don't make budgets. Take a civics class. The Congress prepairs the budget and it's been the Republican controlled Congress which has slashed and burned NASA over the last half-decade. If we see an increase in spending over the next few years it won't be because of the brothers Bush. It will be because the US Congress is no longer dominated by Republicans more interested in spending money on the Military or Corporate tax breaks than spending on science and exploration.
The current projected budget spending over the next five years (projected by a Republican dominated Congress) pushes DoD spending up and NASA spending down. Don't expect to see this change unless friends of NASA in the Congress do something to change it.
"So kick back, relax, and let NASA enjoy its already massive budget."
Are you a total asshole. NASA's budget has been cut every year since the Republicans took over in the Congress. They forced NASA to scrap some of it's most exciting missions that had been in planning for years. "already massive budget"?!?! What the hell are you smoking. NASA gets less than 5% of what the US Military gets! They get less than 1% of the total US Federal spending!
2000 DEPARTMENT OF DEFENSE-MILITARY
Total Department of Defense-Military 279,924,000,000
2000 NATIONAL AERONAUTICS AND SPACE ADMINISTRATION
Total National Aeronautics and Space Administration 13,602,000,000
2000 Federal Government totals 1,801,079,000,000
...And it's worse for 2001. We're losing missions to Mars that cost less than a single US Military vehicle and you're saying relax! Sorry, not gonna happen. You might do yourself some good actually looking at some US Fed Budget figures.
Try a nightly build from here
0.6 is quite old. It is a snapshot of the MN6 branch at the time Netscape 6 was released. That branch was cut on 9/22 and development on the branch (lasting about 6 weeks) was slower than it was on the trunk. Nightly trunk builds at the Netscape 6/Mozilla 0.6 release point were significantly better than 0.6 and we've gotten a lot better since then.
--Asa
Slashdot Mirror
mozilla didn't make a big hype about much of anything. mozilla, defined as the people contributing thousands upon thousands of hours making Mozilla, have been too busy to hype anything. Netscape and the press made a big hype of opensourcing the Communicator 5 sourcecode. mozilla (remember, the people actually working on this project) made very little hype when they started scrapping large chunks of the Communicator code and building an new set of apps from the ground up. mozilla (remember, the dedicated contributors, paid and unpaid, who have been busting their butts to make something useful) didn't make a lot of hype when the first major commercial Distribution was releases. They were too busy trying to make it better. mozilla (those people fixing the bugs you reported) didn't make a big hype about anything.
So you'd be thrilled if mozilla (those folks working to make a free and open source browser for you) had decided to drop support for everyone except win32 and had instead focused on building a simple win32 browser around the old Communicator codebase which neither supported the standards nor had any future (as a codebase) beyond 5.0. You think that it would have made better sense to have build a so-so win32 only Communicator 5 suite and and then a year or two later scrapped that codebase and start all over again on a 2.0 which was cross platform.
I think that the piece of the puzzle that you're missing here is that the decision to scrap the old codebase and move over to this 'yet another crossplatform appdev platform' means that Mozilla can be built for mac, or linux, or BSD, or solaris, or win32, or hpux, or BeOS, or irix, or AIX, OpenVMS, OS/2, True64 and others. Sure, mozilla (those folks giving you a free and open source, standards supporting, fully featured internet application suite with support for DOM, CSS, HTML, mathML, SVG, bi-di, XSLT, SSL/TLS, simplified I18N and L10N, and a set of technologies that help you to build your own networked apps like forumzilla, xmlterm, protozilla, galeon, kmeleon, nautilus and others) could have scrapped the idea of making something really useful and focused on a win32 browser to compete with MS for the windows desktop (a futal effort in my opinion) completely throwing out the tradition of supporting linux and other non MS operating systems. mozilla (they're the good guys) could have done a lot of things differently but I suspect that folks would have criticized them for whatever the decisions were and I'm personally pretty happy with the results of the decisions as they were made.
--Asa
please point me to the versions of this wonderful browser which work on my mac or on my windows machine.
--Asa
You don't need to know c++ do contribute to mozilla. Visit irc.mozilla.org #mozilla and #mozillazine for pointers to non c++ coding (javascript, XUL, CSS, etc).
--Asa
read the release notes. there is no UI for this yet, backend first, UI second.
--Asa
some history:
On or about september 22 a development branch called MN6 was cut from the Mozilla trunk. This branch was a slower moving branch that resulted a couple months later in the Mozilla code which was at the heart of the Netscape 6 product.
a couple weeks after the MN6 branch was cut there was a Mozilla Milestone made from the trunk. This was M18. The next trunk Milestone was 0.7 in early January and the latest tunk release is 0.8
--Asa
I think that chris blizzard is the person to thank.
--Asa
There are a couple easy things you might try to work around this problem. First and easiest is to create a new Mozilla profile. To do this simply run mozilla.exe" -profilemanager and it should launch a profike manager window. Create a new profile in that window and you should be good to go. If that doesn't do the trick (if the profile manager won't launch) then the next thing you might try is to remove your Mozilla/ directory in winnt/profiles/user/applicatin data/ This folder contains a component registry file and your old mozilla profiles (note, this will destroy previous profiles and the data they contain including bookmarks, mail, etc). Then reinstall mozilla and try to run it again. If these steps don't work then please visit Bugzilla and file a bug with clear steps to reproduce your problem and all relevant mozilla install and system information.
--Asa
If you would like to see the real roadmap go to http://mozilla.org/roadmap.html
The roadmap you pointed to was a table on a webpage called mozillaquest.com.
--Asa
Of course, the people at Mozilla were just saying don't set the version 0.8 as the default browser - perhaps they're simply recommending waiting a few builds for more bug fixes.
um. no the people at Mozilla did not say that. a guy from the webpages mozillaquest.com said that.
--Asa
To load the JRE you'll need to have the latest SUN JRE on your system. Then it's as simple as creating a symlink in the /mozilla/plugins/ directory pointing at the JRE OJI plugin.
Blackdown's JRE was working for some folks last I heard so if you've got that give it a try.
--Asa
From the mozdev front page:
While this project is not being developed (or released for that matter) from within mozilla.org itself, it and other projects at mozdev demonstrate how mozilla technologies can be used and extended and how the community of mozilla developers has and continues to expand "beyond the browser".
--Asa
no it wouldn't be legal. the editing and distribution wouldn't be the problem. the filming of a minor who isn't old enough to give consent is the problem.
um, done. didnt you see the comdex best in show consumer electronics gateway aol linux device? (seriously)
--Asa
oh, and one other thing. our build machines never sit idle. we produce builds every day. check them out at ftp.mozilla.org/pub/mozilla/nightly
this will probably be fixed in the next day or two on the trunk either with that patch or by backing out that revision. We took the easy route on 0.7 and just bakced out the revision that was causing the problem.
-Asa
both are still in the source. Previous mathml and svg enabled builds were contributed to mozilla.org by interested folks in the community. If they don't show up sometime in the next couple of weeks ping me and I'll ask around. The win32 mathml & svg enabled build was contributed by a regular build contributor so I imagine that will show up soon.
--Asa
Actually, that's just some of what's new. That list highlights some of the features that users are likely to notice right off. For a more comprehensive list you might try a bugzilla query something like the 1500 or so bugs fixed since around Mozilla 0.6 It's not a perfect query since a few of those were in M18 and not in 0.6 and vise versa but you get the picture. --Asa
mozilla is looking for contributions of bulds on platforms other than linux, mac and win32. See http://mozilla.org/build/distribution.html
for info on how to contribute builds to mozilla.org.
--Asa
Look at the Democratic House members vocal in science, technology and space.
Take a look at their voting records. I'm not arguing that you won't find Republicans there and some of them even voting to make NASA stronger but the "friends of NASA" are most definitely Democrats.
--Asa
--Asa
President's don't make budgets. Take a civics class. The Congress prepairs the budget and it's been the Republican controlled Congress which has slashed and burned NASA over the last half-decade. If we see an increase in spending over the next few years it won't be because of the brothers Bush. It will be because the US Congress is no longer dominated by Republicans more interested in spending money on the Military or Corporate tax breaks than spending on science and exploration.
The current projected budget spending over the next five years (projected by a Republican dominated Congress) pushes DoD spending up and NASA spending down. Don't expect to see this change unless friends of NASA in the Congress do something to change it.
--Asa
Are you a total asshole. NASA's budget has been cut every year since the Republicans took over in the Congress. They forced NASA to scrap some of it's most exciting missions that had been in planning for years. "already massive budget"?!?! What the hell are you smoking. NASA gets less than 5% of what the US Military gets! They get less than 1% of the total US Federal spending!
--Asa
2000121306 ^^---checkin # for that day.
um, actually that 06 is the hour that the pull for that build happened.
--Asa
Try a nightly build from here
0.6 is quite old. It is a snapshot of the MN6 branch at the time Netscape 6 was released. That branch was cut on 9/22 and development on the branch (lasting about 6 weeks) was slower than it was on the trunk. Nightly trunk builds at the Netscape 6/Mozilla 0.6 release point were significantly better than 0.6 and we've gotten a lot better since then.
--Asa
"I can't believe this guy (EverCode) is supposedly a mozilla coder" I missed that part. Where does he say heis a Mozilla developer? -Asa