Diff for /books/www/articles/xpfe_dhtml.html between versions 1.11 and 1.12

version 1.11, 2001/08/09 20:11:51 version 1.12, 2001/08/09 20:17:27
Line 25  coincidence of Open Source development,  Line 25  coincidence of Open Source development, 
 unintended consequence of lowering the barriers to entry for application developers.  To better understand this happy coincidence and why it can be so  unintended consequence of lowering the barriers to entry for application developers.  To better understand this happy coincidence and why it can be so
 useful for developers it is necessary to take a closer look at what XPFE is made of.  useful for developers it is necessary to take a closer look at what XPFE is made of.
   
 <hr>  
   
 <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
language called XUL, the XML-based User Interface Language).  Since well understood Web standards are being used to create applications instead oflanguage called XUL, the XML-based User Interface Language).  In it's most simple form, XPFE can be thought of a simply the union of each of these 
platform-specific C code, a whole new group of people now have the ability to create their own applications using Mozilla.standards.
 
 <center>
 <p><img src="http://books.mozdev.org/screenshots/moz_0101.gif"><br>
 <font size="-1"><i>Figure 1: XPFE Framework</i></font>
 </center>
 
 <hr>
 
 <p>Since well understood Web standards are being used to create applications instead of platform-specific C code, a whole new group of people now have the
 ability to create their own applications using Mozilla.
 
 
   
 <p>In the sense that XPFE uses some of the same standards that are used to create Web pages, Mozilla-based applications can even be thought of as Web  <p>In the sense that XPFE uses some of the same standards that are used to create Web pages, Mozilla-based applications can even be thought of as Web
 pages.  Gecko, the HTML rendering engine that Mozilla uses, also draws all XPFE content, so a Web page and an application created with XPFE are on one  pages.  Gecko, the HTML rendering engine that Mozilla uses, also draws all XPFE content, so a Web page and an application created with XPFE are on one
Line 47  just create a skin for an application.   Line 57  just create a skin for an application.  
 href="http://www.netscape.com/themes/">different themes</a> for their browser suite, but the browser suite itself is also created out of these same  href="http://www.netscape.com/themes/">different themes</a> for their browser suite, but the browser suite itself is also created out of these same
 technologies.  technologies.
   
 <center>  
 <p><img src="http://books.mozdev.org/screenshots/moz_0101.gif"><br>  
 <font size="-1"><i>Figure 1: XPFE Framework</i></font>  
 </center>  
   
 <p>To understand all of the capabilities of XPFE, we can look at how the different components of it fit together.  JavaScript is used to create the  <p>To understand all of the capabilities of XPFE, we can look at how the different components of it fit together.  JavaScript is used to create the
 functionality for a Mozilla-based application, Cascading Style Sheets are used for formatting the look and feel, and XUL is used for creating the  functionality for a Mozilla-based application, Cascading Style Sheets are used for formatting the look and feel, and XUL is used for creating the
 application's structure.  Viewed together these three standards can be seen forming the triangle in Figure 1 above.  application's structure.  Viewed together these three standards can be seen forming the triangle in Figure 1 above.

Removed from v.1.11  
changed lines
  Added in v.1.12


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