Wow, what a great release! I think that 0.9.3 really is a key step in the right direction for 1.0. See http://www.mozilla.org/roadmap.html for more details on the roadmap and plans for 1.0.
Also, as a mozilla developer, I would like to thank all those who have joined the project recently and done something to help. Even if you cannot code, there is still lots that you can do. I urge you to download 0.9.4 or even better, a nightly build, and to look at http://www.mozilla.org/start, http://www.mozilla.org/qa/help, and http://www.mozilla.org/get-involved.html. There are many things that you can do to help which will help get 1.0 out the door sooner and better.
As a student, I must disagree with you completely. Many a time have I done homework assignments, only to find that I couldn't print them at home (classic lack of black ink error), or needed them at school early. This is why I run ftpd and afpd on my computer. My teachers have a general rule of: if you can't get your homework in, make every damm effort. If you can't print it, email it in; if you can't email it (and that's what the assignment was); print it and bring it in. Just because the school network isn't working properly doesn't mean that you are free from all obligation to do work. Can you imagine schools sending students home because the ISP disconnected them by mistake? Laws are important, but this is something that the school should be able to work out with their standard procedures.
Zach
As someone involved in the Mozilla project, I feel that I must give some attention to the reson for the delay. http://komodo.mozilla.org/planning/branches.cgi is the mozilla.org branch 'anti-crash-landing' monitor. In the last few release cycles, the following major changes have occured:
new security manager (ssl, tls...)
LDAP autocomplete
New Modern theme
Enhanced frameset and iFrame printing
XUL perf improvements (front end speed!)
removal of old cache (disk space)
api changes for more modular code
accessibility code landed
editor improvements
css perf so that css styles are loaded into ram only when needed.
Mailnews perf (much better now)
style memory requirements reduced
*new image rendering library!
Improved string APIs
new cache
bidirectional text support for other languages
improved autocomplete
new pref APIs for embedding
Each one of these things takes time to be put into ship shape. By holding off 1.0 a little longer, the bugs in the new things can be fixed! We wouldn't want to have another nscp 6.0, would we?
The Netscape image rendering team decided to name the new rendering library libpr0n. I shouldn't be telling anyone about this, but http://www.libpr0n.com gives you the gory details:
From the libpr0n faq:
Do you plan to make any money from libpr0n?
The intention is to restrict the version of libpr0n shipped with Mozilla to a fixed number of pixels per session. To unlock the restriction, users will be encouraged to register their copy (we estimate that this will be about $34.95).
However, if you act _now_, you are entitled to a free registration. http://www.libpr0n.com has all the information. However, "Note. Children under the age of 13 should not need a porn rendering library."
Yes, Mozilla (and netscape) does have a "hidden" prefrence that allows you to set the useragent string. You can look at your prefs.js file (stored as part of your profile) and change the setting to comply with your wishes.
Re:What has Changed & How to get Involved
on
Mozilla 0.9 Out
·
· Score: 1
Also, do remember that even non-coders can help out with Mozilla. Come to irc.mozilla.org #mozillazine or check out http://www.mozilla.org/quality/help
Slashdot Mirror
This used to be a huge issue and something that prevented lots of people from using Mozilla before. Thank you to those who have fixed this!
There is a bug on this in bugzilla though I forgot the # offhand. I do know that it is in the works and will be done as soon as possible.
Zach
Wow, what a great release! I think that 0.9.3 really is a key step in the right direction for 1.0. See http://www.mozilla.org/roadmap.html for more details on the roadmap and plans for 1.0.
Also, as a mozilla developer, I would like to thank all those who have joined the project recently and done something to help. Even if you cannot code, there is still lots that you can do. I urge you to download 0.9.4 or even better, a nightly build, and to look at http://www.mozilla.org/start, http://www.mozilla.org/qa/help, and http://www.mozilla.org/get-involved.html. There are many things that you can do to help which will help get 1.0 out the door sooner and better.
As a student, I must disagree with you completely. Many a time have I done homework assignments, only to find that I couldn't print them at home (classic lack of black ink error), or needed them at school early. This is why I run ftpd and afpd on my computer. My teachers have a general rule of: if you can't get your homework in, make every damm effort. If you can't print it, email it in; if you can't email it (and that's what the assignment was); print it and bring it in. Just because the school network isn't working properly doesn't mean that you are free from all obligation to do work. Can you imagine schools sending students home because the ISP disconnected them by mistake? Laws are important, but this is something that the school should be able to work out with their standard procedures. Zach
As someone involved in the Mozilla project, I feel that I must give some attention to the reson for the delay. http://komodo.mozilla.org/planning/branches.cgi is the mozilla.org branch 'anti-crash-landing' monitor. In the last few release cycles, the following major changes have occured: new security manager (ssl, tls...) LDAP autocomplete New Modern theme Enhanced frameset and iFrame printing XUL perf improvements (front end speed!) removal of old cache (disk space) api changes for more modular code accessibility code landed editor improvements css perf so that css styles are loaded into ram only when needed. Mailnews perf (much better now) style memory requirements reduced *new image rendering library! Improved string APIs new cache bidirectional text support for other languages improved autocomplete new pref APIs for embedding Each one of these things takes time to be put into ship shape. By holding off 1.0 a little longer, the bugs in the new things can be fixed! We wouldn't want to have another nscp 6.0, would we?
The Netscape image rendering team decided to name the new rendering library libpr0n. I shouldn't be telling anyone about this, but http://www.libpr0n.com gives you the gory details: From the libpr0n faq: Do you plan to make any money from libpr0n? The intention is to restrict the version of libpr0n shipped with Mozilla to a fixed number of pixels per session. To unlock the restriction, users will be encouraged to register their copy (we estimate that this will be about $34.95). However, if you act _now_, you are entitled to a free registration. http://www.libpr0n.com has all the information. However, "Note. Children under the age of 13 should not need a porn rendering library."
Yes, Mozilla (and netscape) does have a "hidden" prefrence that allows you to set the useragent string. You can look at your prefs.js file (stored as part of your profile) and change the setting to comply with your wishes.
Also, do remember that even non-coders can help out with Mozilla. Come to irc.mozilla.org #mozillazine or check out http://www.mozilla.org/quality/help
Actually, libpr0n is new in this release, it was checked into cvs after prior releases.