File:  [mozdev] / books / www / articles / bloom.html
Revision 1.9: download - view: text, annotated - select for diffs - revision graph
Thu Aug 29 21:03:05 2002 UTC (17 years, 9 months ago) by david
Branches: MAIN
CVS tags: HEAD
updating draft

    1: <h1>Let a Hundred Browsers Bloom</h1>
    4: <p>The recently released <a href="">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="">HomeBase DESKTOP</a>, ActiveState's <a href="">Komodo IDE</a>, and <a href="">all of the projects</a> hosted on  People are also using Mozilla to create their own custom browsers [link to brian's article].
    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.
   18: <h2>Gecko Based Browsers</h2>
   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.
   22: <p>*** need screenshot *** The goal of the <a href="">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.  The most recent stable release, <a href="">Chimera 0.4</a>, is available for download along with <a href="">nightly development builds</a>.
   24: <p>Chimera uses <a href="">Cocoazilla</a>, a variant of <a href="">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 ***).  
   26: <p><a href="">Galeon</a> and <a href="">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="">GNOME</a> desktop and K-Meleon uses Gecko to create a Windows only browser.  The latest stable version of Galeon can be <a href="">downloaded</a> for a variety of Linux distributions.  There are also alpha versions available for <a href="">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.
   30: <pre>
   31: Chimera       
   32: Galeon         
   33: K-Meleon      
   34: SkipStone     
   35: Q.Bati        
   36: </pre>
   39: <h2>XUL Based Browsers</h2>
   41: <p>A few of these projects are working on improving the basic Mozilla browser interface. One of the first Mozilla applications, Aphrodite
   42: (, has an interface designed and created by members of the Mozilla community. Another project called m/b (short for
   43: mozilla/browser) addresses shortcomings that some people see with the default browser interface. In many ways, these projects are similar to
   44: themes, but they take this idea one step further and use XUL, CSS, and JavaScript to change the layout of the browser interface and not just the
   45: look of the browser.
   47: <pre>
   48: Aphrodite     
   49: 	include aphrodite themes
   50: skyline       
   51: m/b            (screenshot)   
   52:         phoenix       
   53:         project piglet
   54: </pre>
   57: <h2>Conclusion</h2>
   59: <pre>
   60: 	- links to other browsers
   61: 	- minotaur reference???
   62: 	- let 100 browsers bloom
   63: </pre>
   65: <p>If you think of a type of browser that is needed but that is not being developed right now, use Mozilla to create your own browser.
   68: -------------------------------------------------
   71: <pre>
   72: notes
   74: others
   76: Beonex Communicator
   77: BrowserG!
   78: Dino
   79: more
   84: aol and compuserve clients	gecko based or mozilla based?
   87: minotaur  - alternative mail client
   88: 	phoenix reference on the page
   95: Lot's of changes are under way for the Mozilla browser
   98: - 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 
   99: 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 
  100: environment"
  102: - Project "Phoenix", "...a redesign of the Mozilla browser component, similar to Galeon, K-Meleon and Chimera, but written using the XUL user 
  103: interface language and designed to be cross-platform" (via mpt's site)
  105: - The mozilla/browser project, mentioned a while ago on this site has resurfaced on mozdev. There are some screenshots, but the installable 
  106: XPI is not working, yet.
  112: (stand-alone mail client)
  116: -------------------------------
  118: reasons for creating alternate browsers
  120: from
  122: 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 
  123: 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 
  124: Mac OS X, both of which have fast friendly user switching, I'd claim that they aren't.
  126: Another example of horrid user interface is the Mozilla Preferences dialog. Again, all prefs are shoved down into the hierarchy by an extra level, 
  127: because the top level must necessarily be given over to individual application branches. User interface that logically belonged in preferences has 
  128: been torn out because it would have ended up too buried to be useful, e.g., the Mail/News account settings.
  130: from
  134: 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
  135: 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
  136: 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
  137: in order to keep Netscape happy. [...] You'll never see eye-to-eye, because you're not trying to produce the same browser.
  139: The only real solution I see to this problem is for Mozilla to escape the one-browser mold. After Mozilla 1.0, should relinquish
  140: 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
  141: people try to design the power user's dream browser, while another works on a simpler elegant user experience.
  144: </pre>

FreeBSD-CVSweb <>