Diff for /books/www/articles/xpfe_dhtml.html between versions 1.7 and 1.8

version 1.7, 2001/08/09 19:47:35 version 1.8, 2001/08/09 20:01:34
Line 7 Line 7
 <font size="+1"><b>XPFE vs. DHTML</b></font>  <font size="+1"><b>XPFE vs. DHTML</b></font>
   
 <p>'In the beginning, there were 3 front ends: Mac, Windows and Unix. Each took a suite of developers to maintain. Adding a new feature (even just a  <p>'In the beginning, there were 3 front ends: Mac, Windows and Unix. Each took a suite of developers to maintain. Adding a new feature (even just a
button)  required 3 engineers to waste at least a day (more often a week) slaving away until the feature was complete. This had to change.'button) required 3 engineers to waste at least a day (more often a week) slaving away until the feature was complete. This had to change.' This <a
href="http://mozilla.org/xpfe/ElevatorTouchyFeely.html">quote</a> is posted on mozilla.org and describes how the Netscape 4.x browsers required a
<p>This is an explanation quote is posted on mozilla.org and describesing how the Netscape 4.x browsers required a different set of engineers to createdifferent set of engineers to create and maintain the code for the user interface, even though the browser looked nearly identical on each different
and maintain the code for the user interface code, even though the browser looked nearly identical on each different platform. version looked nearlysupported platform.
identical.
<p>For a company committed to creating an application that runs on a wide range of different systems, using platform specific code was a big waste of
<p>For a company n organization committed to creating an application that runs on a wide range of different systems platforms, this system of usingtime. XPFE, Mozilla's cross-platform front end, was designed to solve this problem by enabling engineers to create one interface that would then work on
platform specific code was a huge investment and a big waste of time. XPFE, Mozilla's cross-platform front end, was designed to solve this problem bysoany operating system.  
that enabling engineers would be able to create one interface that would then work on any all operating systems.
<p>This new technology started out as a time-saving technique and turned into one of Mozilla's most powerful innovations. When they started work on XPFE
<p>This new technology started out as a time-saving technique and turned into one of Mozilla's most powerful innovations. When they started work onMozilla engineers were trying to create a more efficient process that would save them time and effort, but this technology ended up having the unintended
creating XPFE, Mozilla engineers were trying to create a more efficient process that would save them time and effort when they started work on XPFE, butconsequence of lowering the barriers to entry for application developers.
this technology ended up having the unintended consequence of lowering the barriers to entry for application developers. 
   
 <p>Mike Cornall, in an article about Mozilla published on LinuxToday, summarizes the history of XPFE well when he says: 'The application platform  <p>Mike Cornall, in an article about Mozilla published on LinuxToday, summarizes the history of XPFE well when he says: 'The application platform
 capabilities of Mozilla came about through a happy coincidence of Open Source development, good design, and far-sighted developers who were paying  capabilities of Mozilla came about through a happy coincidence of Open Source development, good design, and far-sighted developers who were paying
attention.'attention.'  To better understand this happy coincidence it is necessary to take a closer look at what XPFE is made of.
   
 <hr>  <hr>
   
 <p>'In the beginning, there were 3 front ends: Mac, Windows and Unix.  Each took a suite of developers to maintain. Adding a new feature (even just a  
 button) required 3 engineers to waste at least a day (more often a week) slaving away until the feature was complete.  This had to change.' This is an <a  
 href="http://www.mozilla.org/xpfe/ElevatorTouchyFeely.html">explanation posted</a> on mozilla.org describing how the Netscape 4.x browsers required a  
 different set of engineers to create and maintain the interface code for Netscape on each different platform, even though each version looked nearly  
 identical.  
   
 <p>For an organization committed to creating an application that runs on a range of <a href="http://www.mozilla.org/ports/">different platforms</a> this  
 system of using platform specific code was a huge investment and a big waste of time.  XPFE, Mozilla's cross-platform front end, was designed to fix this  
 by allowing engineers to be able to create one interface that would then work on any operating system.  This new technology started out as a time-saving  
 technique and then turned into one of Mozilla's most powerful innovations.  
   
 <p>Mozilla engineers were trying to create a more efficient process that would save them time and effort when they started work on XPFE, but this  
 technology ended up having the unintended consequence of lowering the barriers to entry for application developers.  Mike Cornall, in <a  
 href="http://linuxtoday.com/news_story.php3?ltsn=2000-07-25-001-07-OP-SM-0036">an article</a> about Mozilla published on LinuxToday, summarizes the  
 history of XPFE well when he says: 'The application platform capabilities of Mozilla came about through a happy coincidence of Open Source development,  
 good design, and far-sighted developers who were paying attention.'  
   
 <p>All browsers allow people using any type of computer to access applications on the Web, such as Yahoo! Mail, Amazon and Ebay. Mozilla is simply  
 building on this idea.  Using new technologies in conjunction with existing Web standards Mozilla enables the creation of more powerful applications, so  
 instead of using Opera, Netscape 4.x or Internet Explorer to access a Web page you can use a full-featured application with Mozilla.  
   
 <p><b>Understanding XPFE</b>  <p><b>Understanding XPFE</b>
   
 <p>The technologies that XPFE uses are all existing Web standards, such as Cascading Style Sheets, JavaScript and XML (the XML component is a new  <p>The technologies that XPFE uses are all existing Web standards, such as Cascading Style Sheets, JavaScript and XML (the XML component is a new

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


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