Review of Mozilla's 2002 271
An anonymous reader writes "MozillaZine is currently featuring an article looking back at the last 12 months of the Mozilla project. It's amazing to see how far things have come in 2002. A year ago, there was no Mozilla 1.0, no Netscape 7, no Phoenix, no Chimera and no shipping AOL clients using Gecko (Mozilla's rendering engine). An interesting read."
Chimera (Score:5, Informative)
Chimera provides exactly the features I need, and none more, none less. big kudoos to the chimdevs. If you read this : u guys rock !
I used IE (Score:5, Informative)
Re:I used IE (Score:3, Informative)
If you haven't done it yet, check out Opera as well. Although I find phoenix very alluring, Opera is still king in the low resource / high speed / high efficiency department.
I finally dropped IE for Moz this year... (Score:4, Informative)
You can! (Score:5, Informative)
Re:Chimera (Score:3, Informative)
Not Mozilla's problem (Score:1, Informative)
The main focus of the Mozilla project is and always will be software development. It's up to the Mozilla based distributions (Chimera, KMeleon, Phoenix, Netscape, Beonex, etc.) to worry about marketing and distribution.
Re:Chimera (Score:3, Informative)
If you don't have a file there, make one and put this in it:
// Don't play those animated gifs over and over.
user_pref("image.animation_mode", "once");
Re:1.7 % Market Share (Score:3, Informative)
Re:Is the road to success as a standalone? (Score:4, Informative)
Re: Validation (Score:3, Informative)
Re:No Chimera? (Score:3, Informative)
Wrong direction, guys (Score:4, Informative)
"Currently, remote Mozilla applications are not prevalent because development focuses on making the client applications as stable and efficient as possible. Therefore, this area of Mozilla development is largely speculatative. This chapter argues that remote applications are worth looking at more closely."
The Mozilla developers are focused on making another VB instead of providing remote HTTP-friendly GUI apps. That is where the real need is. The developers are getting away from webbiness, but that *should* be the focus of a browser.
I don't get it.
Re:a year ago (Score:5, Informative)
1.) He was able to import his Outlook stuff into Mozilla Mail no problem.
2.) All he needed was a spelling checker plugin for the mail client (Got one from Mozdev) and it was 100% perfect for him.
3.) Mozilla "Imported" his many hundreds of bookmarks which he definatly needed.
4.) The built in popup blocker has worked wonders for him.
5.) He has Mozilla sit in the system tray so he doesn't notice any load up delays.
When I was converting my Dad to Mozilla I showed him how much better it is and he definatly agreed. He asked a few questions about how to make some things work and I got him up and running no sweat. Ever since he got klez because of Outlook (Partially his fault, yadda yadda yadda..) he believes that Mozilla Mail is greater since he now doesn't worry (for the most part) about mail viruses.
So if you wanna convert someone, start with a family member.
Re: Validation (Score:5, Informative)
It seems like you're suggesting that validation assures standards-compliance. Validation does not ensure standards-compliance.
HTML Validation [w3.org] only ensures that you've met certain constraints of syntax and containment, but it doesn't ensure that you're following the standard. If you're using one of the Transitional doctype declarations, it doesn't ensure that you're avoiding deprecated features. More importantly, it doesn't show if you're depending on a bug in the browsers you're testing in. For example, a browser that doesn't implement section 14.3 of the HTML 4.0 spec [w3.org] correctly (pretty much any browser other than Mozilla, right now) might load stylesheets that the HTML spec says shouldn't be loaded. Thus you'll have valid markup, and your browser will load your stylesheets, but any standards-compliant browser will treat some of your stylesheets as alternate stylesheets and not load them. (This happens if you specify different title attributes on the LINK element linking to the stylesheets, since it makes some of the stylesheets alternate stylesheets.) Similar traps can happen in other ways and allow you to write perfectly valid markup that means something other than what you think it does and what you intended it to do.
CSS validation [w3.org] has similar problems. (It also has the problem that the validators themselves have rather significant bugs, since there aren't any mature implementations of CSS parsers using which one can build validators like the SGML parsers on which HTML validators are based.) For example, MSIE for Windows treats the height property on block-level elements incorrectly: it treats it as min-height and allows the height of the block to be larger if the contents overflow. This is incorrect, so there are pages that are displayed nicely on MSIE for Windows but have lots of overlapping text on any CSS-compliant browser. Likewise, you could be writing pages that work fine at your default font size or window width but display very badly at others.
In other words, validation tools for HTML and CSS are nowhere near smart enough to be a substitute for really knowing what you're doing. (Does anyone rely on lint to verify that their C programs are bug-free?)
(I actually wrote this post before on slashdot, but way too late in the thread for anyone to notice it. I'm afraid I'm doing the same thing again, though...)
Re:Chimera (Score:2, Informative)
We frequently ask for graphic designers and documenters and testers for our OSS projects. Positive and constructive feedback such as otis' comments are just as useful because they help developers understand which parts of their app are useful and well received, and where there is room for impovement.
My Mozilla Experience in 2002 (Score:3, Informative)
Re: Validation (Score:3, Informative)
In my experience, I have removed serious structural errors from web pages, in pages that I wrote as well as in pages that other wrote, far more easily by validating the HTML instead of trying to check in different browsers. After validating, you can always go the extra mile and check the page in other browsers, but usually you don't even need to.
Tired of IE users. (Score:5, Informative)
From this I found a few interesting things. The first, which is encouraging, is that it seem to be working. The percentage of people who visit my site using Mozilla started rising sharply. I went from about 1% to almost 5%. The second thing, which is curious, is that a lot less people are actually using IE than you might think. My server logs show that about 80% of my visitors use IE, but only about 40% get the popunder. My conclusion is that there are a lot of browsers out there that fake the user agent, or many people have found a way to disable popunders in IE. (have javascript disabled, or some such).
If you want the code to do the popunder so you can advertise mozilla on your site, its easy to grab the Javascript from my home page, just view source.
Re:Technical advancement not the issue. (Score:3, Informative)
Netscape and Mozilla are almost the exact same thing--the only real difference is logo and the 50 AOL shortcuts that Netscape installs. Other than that, each version of Netscape is from a Mozilla build, and the programmers working on Netscape are basically the same ones working on Mozilla.
Re:Chimera (Score:3, Informative)
The Chimera documentation about proxy settings [mozilla.org] states:
Proxy Servers
Some organizations block direct connections to the Internet, for security or other reasons. In these situations, connections are required to go through proxy servers, which are intermediate servers that redirect connections to their final destination.
Chimera normally gets information about yor proxy server settings from the Network System Preferences pane (see the "Proxies" tab there). If you switch network locations, or change the proxy settings, Chimera will pick up those new settings without restarting.
It then goes on to describe how to enable Proxy Auto Config support in Chimera by way of several hidden preferences.
Slightly different approach (Score:3, Informative)
var strBrowser = navigator.userAgent;
if (strBrowser.indexOf("MSIE")> 0) {
document.write("<p><strong>");
document.write("Warning: you appear to be viewing this page with Microsoft Internet Explorer, which has numerous bugs and ");
document.write('<a href="http://www.nwnetworks.com/iesc.html"> security holes.</a>');
document.write(" It is recommended that you upgrade to a more secure browser, ");
document.write('such as <a href="http://www.mozilla.org">Mozilla,</a> ; ');
document.write('<a href="http://home.netscape.com/computing/download
document.write('or <a href="http://www.opera.com">Opera.</a>');
document.write("</strong></p>");
}