File:  [mozdev] / books / www / articles / xpfe_dhtml.html
Revision 1.17: download - view: text, annotated - select for diffs - revision graph
Thu Aug 9 21:26:35 2001 UTC (18 years, 8 months ago) by david
Branches: MAIN
CVS tags: HEAD
editing article

<title>XPFE vs. DHTML</title>
<body bgcolor="#FFFFFF">

<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
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.' 

<p>This <a href="">quote</a> is posted on and describes how the Netscape 4.x browsers
required a different set of engineers to create and maintain the code for the user interface, even though the browser looked nearly identical on each
different supported platform.

<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
time. 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
any operating system.  (In this context a front end is more than the look and feel of a Mozilla-based application, but can also include the functionality
and structure of that application.  For example, Netscape 6 does use XPFE to allow for the creation of <a
href="">different themes</a> for their browser suite, but the browser suite itself is also created using XPFE.)

<p>This new technology started out as a time-saving technique and turned into one of Mozilla's most powerful innovations.  Mike Cornall, in <a
href="">an article</a> 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>Mozilla engineers were trying to create a more efficient process that would save them time and effort, but this technology ended up having the
unintended consequence of lowering the barriers to entry to application development.  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.

<p><b>Understanding XPFE</b>

<p>The technologies that XPFE uses are all existing Web standards, such as <a href="">Cascading Style Sheets</a>, 
<a href="">JavaScript</a> and <a href="">XML</a> (the XML component is a new
language called XUL, the XML-based User Interface Language).  In it's most simple form, XPFE can be thought of as simply the union of each of these 

<p><img src=""><br>
<font size="-1"><i>Figure 1: XPFE Framework</i></font>

<p>To understand how XPFE works, 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 application's structure.  
Viewed together these three standards can be seen forming XPFE in Figure 1 above.

<p>Instead of using platform-specific C code to create an application, XPFE uses these well understood Web standards that are by design inherently
platform independent.  Since the framework of XPFE is inherently platform independent, so are the applications that are created with it.  Since the
framework is also made up of tools that are used to create Web pages, anyone familiar with creating a Web page can use XPFE to create a cross-platform

<p>Although the actual creation of Mozilla-based applications can be much more complicated than building a Web page, XPFE allows developers to create
applications in the same way they would create a Web page.  Or to put it another way, the application is now a Web page.  Gecko, the rendering engine
that Mozilla uses to draw a Web page in the browser, even draws the Mozilla application on the desktop.

<p><b>Comparing XPFE and DHTML</b>

<p>In many ways XPFE is very similar to <a href="">DHTML</a>.  Dynamic HTML is a combination of HTML with JavaScript
and CSS that allows a developer to create a Web application that is contained within the content area of a browser.  XPFE provides a logical evolution to
this idea by allowing the creation of applications that are more powerful, more flexible and that can live outside of the browser window as stand-alone

<p>Figure 2 below illustrates the similarities between XPFE and DHTML.  Both use JavaScript to create functionality, both use CSS to format design and
layout, and both use a fairly simple mark-up language to describe content.  The difference between the two is that one of these mark-up languages is HTML
and the other is XUL.

<p><img src=""><br>
<font size="-1"><i>Figure 2: Comparison of DHTML and XPFE</i></font>

<p>Although HTML has been put to many different uses, it was <a href="">originally designed</a> as a simple system to
link together separate text documents on the Internet.  Later additions to the HTML standard have extended its functionality, but even these enhancements
can't make it an appropriate language to use for developing applications.  XUL is a language specifically designed for creating user interfaces, so it
makes sense that XPFE is more suited for application development than DHTML.

<p>Since XUL is structurally similar to HTML, knowledge of building Web pages will give you a boost in learning how to create cross-platform
Mozilla-based applications.  Even if you have never used HTML before, XUL uses a straight-forward <a
href="">collection of tags</a> that makes it easy to get comfortable with it in a short time.  Once you become
accustomed to using XUL you will be ready to start using XPFE to create your own applications.

<p><b>Oversimplifying Things</b>

<p>Describing XPFE as a more sophisticated version of DHTML is an oversimplification and deliberately leaves out much important information.  These
details were ignored in the comparison to give a better understanding of the basic framework of XPFE.  Now that we've gotten past the basics, we can go
back and talk about the rest of the functionality available with Mozilla that makes it such a powerful framework for creating applications.

<p>At the <a href="">Second Mozilla Developer Meeting</a>, Rob Ginda, the creator of ChatZilla, lead a
discussion group about Mozilla as Platform.  In this session he listed all of the following as components of a Mozilla-based application:

<LI>XUL (XML-based User Interface Language) - Used to create the structure and content of an application.<br><br>
<LI>CSS (Cascading Style Sheets) - Used to create the look and feel of an application.<br><br>
<LI>JavaScript - Used to create the functionality of an application. (Other scripting languages, such as Python, Perl or Ruby, can be used in 
place of Javascript to create functionality for an application.)<br><br>
<LI>XPInstall (Cross-Platform Install) - Used to package applications so that they can be installed on any platform.<br><br>
<LI>RDF (Resource Description Framework) - Used to store data and transmit information.  Generally regarded to be one of the most complicated 
aspects of XPFE.<br><br>
<LI>DTD (Document Type Definition) - Used for localization and internationalization, more commonly referred to in short-hand as L12N and I18N 
<LI>XBL (eXtensible Binding Language) - Used to create reusable widgets using a combination of XUL and JavaScript.<br><br>
<LI>XUL templates - Used to create a framework for importing data into an application with a combination of RDF and XUL.<br><br>
<LI>XPCOM/XPConnect - Used to allow JavaScript, or potentially any other scripting language, to access and utilize C and C++ libraries.

<p>Each of these technologies is important and several of these deserve to have whole books devoted to them.  Although each of these technologies is
important there is a distinction to be made among them.  Some of these are essential to the creation of a Mozilla application and some of them provide
powerful extra features that can be used in addition to the basic functionality.

<p>For example, <a href="">RDF</a> is an extremely powerful technology for using data in Mozilla but it is possible to
create an application without it.  <a href="">Localization</a> also provides Mozilla with a great amount of
flexibility but there are many existing applications that don't take advantage of this feature.  It wouldn't be possible to create an application without
XUL though.


<p><b>Judge For Yourself</b>

<p>XPFE is a new technology that has yet to prove itself to the Web community and many people are skeptical about the need for an application framework
such as this.  Before you make up your mind about XPFE, you should take a look at the many different applications that have already been created using
Mozilla so you can judge for yourself.

<p>If you are interested in trying out some of these, there are currently over 40 different Mozilla-based applications being hosted on <a
href=""></a> that have been created using XPFE.  Other applications using the same technology include
ActiveState's <a href="">Komodo</a> IDE, Rob Ginda's <a
href="">ChatZilla</a> IRC client, and Zope's <a href="">Mozilla


<p><i>Thanks to Julia Kleyman for creating the illustrations used in this article.</i>


FreeBSD-CVSweb <>