Diff for /books/www/articles/bloom.html between versions 1.6 and 1.7

version 1.6, 2002/08/27 20:55:43 version 1.7, 2002/08/28 19:51:44
Line 1 Line 1
<pre><h1>Let a Hundred Browsers Bloom</h1>
let a hundred browsers bloom
 <p>...
   
(double-check links and project capitalization)<h2>Who is the Target Audience?</h2>
(grab sidebar text out of chapter 1) 
   
   <ul>
   <li>aol users for netscape 7?
   <li>power users for the mozilla developers
   <li>no one browser can fit...
   </ul>
   
   <h2>Gecko Based Browsers</h2>
   
gecko-based browsers<pre>
 Chimera                 http://chimera.mozdev.org
 Galeon                  http://galeon.sourceforge.net 
 K-Meleon                http://kmeleon.sourceforge.net
 SkipStone               http://www.muhri.net/skipstone
 Q.Bati                  http://qbati2.sourceforge.net
 </pre>
   
Chimera                        http://chimera.mozdev.org<h2>XUL Based Browsers</h2>
Galeon                        http://galeon.sourceforge.net
K-Meleon                http://kmeleon.sourceforge.net<pre>
SkipStone                http://www.muhri.net/skipstoneAphrodite               http://aphrodite.mozdev.org
Q.Bati                        http://qbati2.sourceforge.net/        include aphrodite themes
 skyline                 http://bugzilla.mozilla.org/show_bug.cgi?id=154414
 m/b                     http://www.blakeross.com/images/mb (screenshot)   
         phoenix                 http://bugzilla.mozilla.org/show_bug.cgi?id=161041
         project piglet          http://mb.mozdev.org
 </pre>
   
   <h2>Conclusion</h2>
   
mozilla-based browsers<pre>
         - links to other browsers
         - minotaur reference???
         - let 100 browsers bloom
 </pre>
   
Aphrodite               http://aphrodite.mozdev.org-------------------------------------------------
skyline                 http://bugzilla.mozilla.org/show_bug.cgi?id=154414 
m/b                     http://www.blakeross.com/images/mb (screenshot) 
        phoenix                 http://bugzilla.mozilla.org/show_bug.cgi?id=161041 
        project piglet          http://mb.mozdev.org 
   
   <pre>
   notes
   
 others  others
   
Line 70  http://www.mozilla.org/mailnews/minotaur Line 90  http://www.mozilla.org/mailnews/minotaur
   
 http://www.mozillazine.org/weblogs/hyatt/2002_04_07_mozillian_archive.html#75279564  http://www.mozillazine.org/weblogs/hyatt/2002_04_07_mozillian_archive.html#75279564
 http://www.mozillazine.org/weblogs/hyatt/2002_04_07_mozillian_archive.html#75307435  http://www.mozillazine.org/weblogs/hyatt/2002_04_07_mozillian_archive.html#75307435
   
   
   -------------------------------
   
   reasons for creating alternate browsers
   
   from http://www.mozillazine.org/weblogs/hyatt/2002_04_07_mozillian_archive.html#75307435
   
   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 
   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 
   Mac OS X, both of which have fast friendly user switching, I'd claim that they aren't.
   
   Another example of horrid user interface is the Mozilla Preferences dialog. Again, all prefs are shoved down into the hierarchy by an extra level, 
   because the top level must necessarily be given over to individual application branches. User interface that logically belonged in preferences has 
   been torn out because it would have ended up too buried to be useful, e.g., the Mail/News account settings.
   
   from http://www.mozillazine.org/weblogs/hyatt/2002_04_07_mozillian_archive.html#75279564
   
   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
   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
   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
   in order to keep Netscape happy. [...] You'll never see eye-to-eye, because you're not trying to produce the same browser.
   
   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
   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
   people try to design the power user's dream browser, while another works on a simpler elegant user experience.
   
   ----------------------------------------
   
   ch1 sidebar
   
   Let a Hundred Browsers Bloom
   
   Because Mozilla can be used to create any sort of application, there's no reason why it can't be used to create different types of browsers. 
   Several projects are currently under development independently from the work being done on the default Mozilla browser. This variety is a huge 
   asset because the Mozilla community doesn't have to try to create one browser that is all things to all people.
   
   A few of these projects are working on improving the basic Mozilla browser interface. One of the first Mozilla applications, Aphrodite 
   (http://aphrodite.mozdev.org), has an interface designed and created by members of the Mozilla community. Another project called m/b (short for 
   mozilla/browser) addresses shortcomings that some people see with the default browser interface. In many ways, these projects are similar to 
   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 
   look of the browser.
   
   Additional projects are creating different types of alternative browsers, but instead of using Mozilla itself to create the application they use 
   the native user interface toolkits for different platforms. These projects create stripped-down browsers that use just Gecko, Mozilla's layout 
   engine. Because these projects use platform-specific code they work only on a specific operating system. Some examples include Chimera 
   (http://chimera.mozdev.org) for Mac OS X, Galeon (http://galeon.sourceforge.net) for Unix, and K-Meleon (http://kmeleon.sourceforge.net) for 
   Windows.
   
   These projects are just a few examples of the different available browsers. Others include Dino!, Beonex, SkipStone, and BrowserG!. If you are 
   interested in learning more about any of these browsers, links to many of them can be found at http://www.mozdev.org/categories/browsers.html. 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.
   
   </pre>

Removed from v.1.6  
changed lines
  Added in v.1.7


FreeBSD-CVSweb <freebsd-cvsweb@FreeBSD.org>