Annotation of books/www/articles/bloom.html, revision 1.12
1.7 david 1: <h1>Let a Hundred Browsers Bloom</h1>
1.8 david 3:
1.9 david 4: <p>The recently released <a href="http://wp.netscape.com/eng/mozilla/ns7/relnotes/7.html">Netscape 7</a> may be the most well known browser built with Mozilla, but it certainly is not the only one. Mozilla is being used as a framework to create many different types of applications including OEone's <a href="http://oeone.com/products/desktop.html">HomeBase DESKTOP</a>, ActiveState's <a href="http://activestate.com/Products/Komodo/">Komodo IDE</a>, and <a href="http://www.mozdev.org/projects.html">all of the projects</a> hosted on mozdev.org. People are also using Mozilla to create their own custom browsers [link to brian's article].
1.1 david 5:
1.9 david 6:
7: <h2>Why Do We Need More Than One?</h2>
9: <p>One of the benefits of Open Source development is that it prevents someone from having to reinvent the wheel whenever they are working on developing something that has been done before. Since the Mozilla community is already working on a browser, wouldn't it be better if everyone just focused on making that browser as good as it can be?
11: <p>Instead of being a bad thing, the several different browser development projects that are currently underway are one of the Mozilla community's greatest assets for the simple reason that one browser can not be all things to all people. Each new browser that gets built is filling a need that is not being met by any other existing option. Each new browser that is built also has the potential to appeal to a whole new audience that will help expand Mozilla's adoption.
13: <p>Another positive benefit of having multiple browsers is that it helps avoid compromises that don't make anyone happy. AOL is interesting in Mozilla because they want a browser that appeals to novice Internet users. The Mozilla developers who contribute their time to the project want to create a powerful browser with a collection of advanced features. If the community is locked into working on only one browser, then the end result of this development process will be a browser that has a bewildering array of features and that doesn't appeal to either intended audience.
15: <p>If one browser can't possibly to beginning users and power users at the same time, why not create two different browsers? For that matter, why not create as many different browsers as there are different types of users? Since all of these browsers are built using Mozilla, web developers can create sites that work with Mozilla and users can browse with whatever tool suits them best. Everyone wins.
1.1 david 16:
1.8 david 17:
1.7 david 18: <h2>Gecko Based Browsers</h2>
1.1 david 19:
1.9 david 20: <p>There are two main types of browsers that are built using Mozilla. Some developers choose to create their application using XUL, Mozilla's XML-based User Interface language. Other developers prefer to use just Gecko, Mozilla's rendering, and then create the GUI of their browser using one of the toolkits native to a specific platform. There are Gecko based browsers for each of the major operating systems in use today, including Windows, Linux and Mac OS X.
1.11 david 22: <p>*** need screenshot *** The goal of the <a href="http://chimera.mozdev.org">Chimera</a> project is to create a best-of-breed browser for the Mac OS X platform with an user-interface that is as simple and as clean as possible. Chimera uses <a href="http://www.mozilla.org/ports/fizzilla/Cocoazilla.html">Cocoazilla</a>, a variant of <a href="http://www.mozilla.org/ports/fizzilla/">Fizzilla</a> that consists of a UNIX back end connected to a Cocoa front end. Since Chimera uses a native toolkit to create it's GUI it can't run on any platform other than OS X, but since it doesn't use XUL it is faster than the default Mozilla browser on the same computer (applications written with XUL will always be slightly slower than applications written with native toolkits because *** need explanation here, ask brian ***). The most recent stable release, <a href="ftp://ftp.mozilla.org/pub/chimera/releases/chimera-0.4.dmg.gz">version 0.4</a>, is available for download along with <a href="ftp://ftp.mozilla.org/pub/chimera/nightly/latest-trunk/">nightly development builds</a>.
1.9 david 23:
1.10 david 24: <p><a href="http://galeon.sourceforge.net">Galeon</a> and <a href="http://kmeleon.sourceforge.net">K-Meleon</a> are projects that also have the goal of creating a simple standards-compliant browser using Mozilla's rendering engine. Galeon uses Gecko to create a browser for the <a href="http://www.gnome.org/">GNOME</a> desktop and K-Meleon uses Gecko to create a Windows only browser. The latest stable version of Galeon can be <a href="http://galeon.sourceforge.net/download/">downloaded</a> for a variety of Linux distributions. There are also alpha versions available for <a href="http://galeon.sourceforge.net/galeon2/">Galeon2</a>, which is a new major version of the browser that takes advantage of the huge changes in architecture in the new GNOME 2 desktop. K-Meleon download is at...
1.8 david 25:
1.7 david 27: <h2>XUL Based Browsers</h2>
1.8 david 29: <p>A few of these projects are working on improving the basic Mozilla browser interface. One of the first Mozilla applications, Aphrodite
30: (http://aphrodite.mozdev.org), has an interface designed and created by members of the Mozilla community. Another project called m/b (short for
31: mozilla/browser) addresses shortcomings that some people see with the default browser interface. In many ways, these projects are similar to
33: look of the browser.
1.7 david 35: <pre>
36: Aphrodite http://aphrodite.mozdev.org
37: include aphrodite themes
38: skyline http://bugzilla.mozilla.org/show_bug.cgi?id=154414
39: m/b http://www.blakeross.com/images/mb (screenshot)
40: phoenix http://bugzilla.mozilla.org/show_bug.cgi?id=161041
41: project piglet http://mb.mozdev.org
1.5 david 43:
1.8 david 44:
1.12 ! david 45: <p><h2>The Future of Mozilla Browsers</h2>
1.5 david 46:
1.12 ! david 47: <p>The browsers that are currently under development using Mozilla are just the tip of the iceberg. One of the most interesting possibilities for future browser development comes from AOL, the same company that owns Netscape and that is the main sponsor of the Mozilla community. Currently the Windows version of the AOL client uses Internet Explorer as the core of it's browser, but their are indications that this way soon change. If AOL were to use Mozilla in a new version of their software, tens of millions of people would be exposed to Mozilla.
1.5 david 48:
1.12 ! david 49: <p>AOL has already made some moves in this direction. The latest version of the <a href="http://www.apple.com/macosx/applications/aol/">AOL client for Mac OS X</a> uses Gecko as it's rendering engine. Gecko has also replaced Internet Explorer in <a href="http://news.com.com/2100-1023-883808.html">CompuServe 7.0</a>, the latest version of AOL's other online service. The decision to use Gecko in these two offerings are seen by many as ways for AOL to iron out any rough spots before they move forward with releasing the latest version of their AOL client for Windows.
1.8 david 50:
1.12 ! david 51: <p>It will be interesting to see what happens with the future of the AOL client, but it is just one of many browser projects worth keeping on eye on. Other projects to take a look at include <a href="http://www.muhri.net/skipstone">SkipStone</a>, <a href="http://qbati2.sourceforge.net">Q.Bati</a>, <a href="http://beonex.com/communicator/">Beonex Communicator</a>, <a href="http://browserg.mozdev.org">BrowserG!</a>, and <a href="http://dino.mozdev.org">Dino</a>. *** any others? ***
1.8 david 52:
1.12 ! david 53: <p>If there is a browser that you would like to use that isn't already being worked on, remember that you can always create your own browser with Mozilla [link to brian's article]. Each of the projects listed here could also use help with testing and development, so you can also contribute by adding features or fixing bugs to make these browsers even better. This wealth of options is a great strength, so let's hope that each of these browsers matures into...
! 54: Let 100 browsers bloom.
1.5 david 55:
1.8 david 56:
1.7 david 57: <pre>
1.5 david 58:
1.12 ! david 59: -------------------------------------------------
1.5 david 60:
1.12 ! david 61: notes
1.6 david 62:
64: minotaur - alternative mail client
65: phoenix reference on the page
1.1 david 67:
1.3 david 69:
72: Lot's of changes are under way for the Mozilla browser
75: - The "Skyline" project, which is a version of Mozilla is being worked on internally at Netscape, "is a short-term project to build a working
76: prototype of a new web client that provides for the daily needs of novice-intermediate users, is fun to use, and really shines in a broadband
79: - Project "Phoenix", "...a redesign of the Mozilla browser component, similar to Galeon, K-Meleon and Chimera, but written using the XUL user
80: interface language and designed to be cross-platform" (via mpt's site)
82: - The mozilla/browser project, mentioned a while ago on this site has resurfaced on mozdev. There are some screenshots, but the installable
83: XPI is not working, yet.
1.4 david 85:
89: http://www.mozilla.org/mailnews/minotaur/index.html (stand-alone mail client)
1.6 david 90:
1.7 david 93: -------------------------------
95: reasons for creating alternate browsers
97: from http://www.mozillazine.org/weblogs/hyatt/2002_04_07_mozillian_archive.html#75307435
99: In some cases features that are of more obvious benefit to one app end up affecting the design of all the apps. For example, profiles are of far
100: more use to mail than they are to a browser. Are profiles even really necessary if you were designing just a browser? In this era of Windows XP and
101: Mac OS X, both of which have fast friendly user switching, I'd claim that they aren't.
103: Another example of horrid user interface is the Mozilla Preferences dialog. Again, all prefs are shoved down into the hierarchy by an extra level,
104: because the top level must necessarily be given over to individual application branches. User interface that logically belonged in preferences has
105: been torn out because it would have ended up too buried to be useful, e.g., the Mail/News account settings.
107: from http://www.mozillazine.org/weblogs/hyatt/2002_04_07_mozillian_archive.html#75279564
1.9 david 109:
1.7 david 111: The end result of these colliding forces is Mozilla 1.0, a lumbering beast of an application suite that boasts a bewildering array of features
112: supplied by contributors whose respective agendas are inevitably at odds. What's even worse is that none of the warring factions is happy with the
113: end result. Mozilla ends up with geek features like the Links Toolbar that make Netscape unhappy, and Mozilla ends up with a lousy toolbar design
114: in order to keep Netscape happy. [...] You'll never see eye-to-eye, because you're not trying to produce the same browser.
116: The only real solution I see to this problem is for Mozilla to escape the one-browser mold. After Mozilla 1.0, Mozilla.org should relinquish
117: control of its flagship application to Netscape and strike out on its own with new browser projects that are truly innovative. Let one group of
118: people try to design the power user's dream browser, while another works on a simpler elegant user experience.
1.9 david 119:
1.7 david 120: