Mozilla Development Roadmap Updated
yota writes: "The guys at mozilla.org just published an updated development roadmap with some interesting thoughts about what will happen after Mozilla 1.0 will be released. Enjoy!" This is worth reading even if you skim toward the bottom and jump to the Intertwingle link. The Mozilla project isn't slapped together -- this kind of forethought and explanation is proof.
I switched to Linux as my primary OS a few months ago, and I haven't looked back. I find I don't miss Windows a bit, and I'm happy with my Slackware/AfterStep setup.
I use Mozilla as my primary browser (Nightly builds), and I find that it has gotten much better than it used to be. Bug reports hit Bugzilla, and are usually updated and/or assigned the same day. Their system is really great.
Sure, the browser has a few annoying things. Text boxes STILL don't behave properly, opening a new window in any shape or form (Ctrl+N, or a javascript function) takes *forever*, and other little things. Overall though, Mozilla is a pretty decent browser. Gecko is a great rendering engine, and tabbed browsing is just totally fucking fantastic.
Once the speed issues are addressed and the behaivior kinks are worked out, that's when 1.0 should hit.
Unfortunately, I find that I do miss the incredible speed of IE 5x. Say what you will about IE security, but it's still the best browser out there. Fortunately, I can happily make that trade-off as a Linux desktop user.
-- Give him Head? Be a Beacon? :P)
(If you can't figure out how to E-Mail me, Don't.
Its in second place
Netscape is Mozilla. Mozilla is netscape.
If you use Linux, please help development of Autopac
Am I the only one who loves this browser?
I was a hardcore IE addict. Been using linux for years, but was so sucked into browsing with IE I was sickening myself. I attempted to use Mozilla over the span of the project and for sure it got better and better over time, but I do agree with folks who say: "why not just a browser?"
This is one of the strengths of IE if you ask me. IE is just a browser the other tools are moved into the mess, and IE (IMHO) has a feeling of transparancy in this way.
I never got that from Netscape, and Mozilla felt that was more and more, but it just has too many 'features' I can get elsewhere.
So anyway, I ended up getting really paranoid about IE and was searching. I realized that if I had complaints about moz then I should use it and use bugzilla. I was doing this under windows as well as linux. I found myself (like a junkie) slipping over to IE again and again.
But then I found Galeon, it has saved me from this terrible addiction. I have not missed IE in the least bit. In fact, I am completly in love with it as a browser. Mozilla is cool too, but Galeon is the one that people who complain that Mozilla should have just been a browser, galeon is this.
Galeon is what it is all about.
So that ALL of the parsing/paining logic (as well as javascript) would behave EXACTLY as IE
With what IE specification?
Mozilla is shooting for the W3C specs, which have the virtue that they do exist. Mozilla actually does have a 'broken HTML compatibility mode', which it will use if a given HTML page doesn't specify a modern HTML DTD.
- jon
Ganymede, a GPL'ed metadirectory for UNIX
Mozilla uses the Java Plug-in from Sun. This is an API that allows Mozilla to use the lastest version of Java with out having to wait for Netscape to provide support. Need to create an applet that uses Java 1.4 functionaly? Just install the lastest plugin, copy a few files from your JRE to mozilla's plugin directory and restart!
Currently Mozilla needs work in the area of finding the Java Plugin and setting up the connection between the two. Until then, copy the file 'NPOJI610.DLL' from your JRE's bin directory to the plugin folder for Mozilla and restart Mozilla.
This is documented in the relase notes
You have to enable Java support by dropping:
user_pref("plugin.do_JRE_Plugin_Scan", true);
into user.js in the appropriate directory (c:\windows\application data\mozilla\profiles\default\${something_stupid}
user_pref("dom.disable_open_during_load", true)
user_pref("browser.target_new_blocked", true)
... which disables popups.