[Phoenix-commits] rev 12955 - public/phoenix/deliverables/planning
andi at wyona.com
andi at wyona.com
Fri Apr 28 23:06:10 CEST 2006
Author: andi
Date: 2006-04-28 23:06:06 +0200 (Fri, 28 Apr 2006)
New Revision: 12955
Modified:
public/phoenix/deliverables/planning/roadmap.xhtml
public/phoenix/deliverables/planning/roadmap.xml
Log:
Extended the roadmap.
Modified: public/phoenix/deliverables/planning/roadmap.xhtml
===================================================================
--- public/phoenix/deliverables/planning/roadmap.xhtml 2006-04-28 20:38:22 UTC (rev 12954)
+++ public/phoenix/deliverables/planning/roadmap.xhtml 2006-04-28 21:06:06 UTC (rev 12955)
@@ -86,31 +86,31 @@
<dl>
<dt>
<span class="section">
- <a href="#id342780">1.1.1.1. Browser Integrated Variant (BROWSER)</a>
+ <a href="#id342786">1.1.1.1. Browser Integrated Variant (BROWSER)</a>
</span>
</dt>
<dt>
<span class="section">
- <a href="#id342794">1.1.1.2. Standalone Variant (STANDALONE)</a>
+ <a href="#id342801">1.1.1.2. Standalone Variant (STANDALONE)</a>
</span>
</dt>
</dl>
</dd>
<dt>
<span class="section">
- <a href="#id342805">1.1.2. Back End Component (BACKEND)</a>
+ <a href="#id342815">1.1.2. Back End Component (BACKEND)</a>
</span>
</dt>
<dd>
<dl>
<dt>
<span class="section">
- <a href="#id342810">1.1.2.1. Client Based Variant (CLIENT)</a>
+ <a href="#id342826">1.1.2.1. Client Based Variant (CLIENT)</a>
</span>
</dt>
<dt>
<span class="section">
- <a href="#id342820">1.1.2.2. Server Based (SERVER)</a>
+ <a href="#id342836">1.1.2.2. Server Based (SERVER)</a>
</span>
</dt>
</dl>
@@ -150,28 +150,31 @@
</div>
</div>
</div>
+ <p>
+ The front end component is responsible for the handling the view. FRONTEND performs tasks like rendering the document, supplying user interaction facilities, etc.
+ </p>
<div class="section" lang="en">
<div class="titlepage">
<div>
<div>
- <h5 class="title"><a id="id342780"/>1.1.1.1. Browser Integrated Variant (BROWSER)</h5>
+ <h5 class="title"><a id="id342786"/>1.1.1.1. Browser Integrated Variant (BROWSER)</h5>
</div>
</div>
</div>
<p>
- The browser integrated variant of the front end is a XUL widget which integrates seamlessly into web browsers based on the Mozilla Platform. BROWSER must be able to work with up-to-date versions of Firefox and SeaMonkey (formerly Mozilla Suite).
+ The browser integrated variant of FRONTEND is a XUL widget which integrates seamlessly into web browsers based on the Mozilla Platform. BROWSER must be able to work with up-to-date versions of Firefox and SeaMonkey (formerly Mozilla Suite).
</p>
</div>
<div class="section" lang="en">
<div class="titlepage">
<div>
<div>
- <h5 class="title"><a id="id342794"/>1.1.1.2. Standalone Variant (STANDALONE)</h5>
+ <h5 class="title"><a id="id342801"/>1.1.1.2. Standalone Variant (STANDALONE)</h5>
</div>
</div>
</div>
<p>
- The
+ The standalone variant of the FRONTEND can be used as a standalone editor, independent of a web browser. Like the browser integrated version, STANDALONE is based on XUL.
</p>
</div>
</div>
@@ -179,32 +182,35 @@
<div class="titlepage">
<div>
<div>
- <h4 class="title"><a id="id342805"/>1.1.2. Back End Component (BACKEND)</h4>
+ <h4 class="title"><a id="id342815"/>1.1.2. Back End Component (BACKEND)</h4>
</div>
</div>
</div>
+ <p>
+ The back end component comprises the controller and the model. BACKEND performs tasks like ID Tagging, XSLT processing, validation, etc.
+ </p>
<div class="section" lang="en">
<div class="titlepage">
<div>
<div>
- <h5 class="title"><a id="id342810"/>1.1.2.1. Client Based Variant (CLIENT)</h5>
+ <h5 class="title"><a id="id342826"/>1.1.2.1. Client Based Variant (CLIENT)</h5>
</div>
</div>
</div>
<p>
- The
+ The client based variant of BACKEND places the back end logic on the client side.
</p>
</div>
<div class="section" lang="en">
<div class="titlepage">
<div>
<div>
- <h5 class="title"><a id="id342820"/>1.1.2.2. Server Based (SERVER)</h5>
+ <h5 class="title"><a id="id342836"/>1.1.2.2. Server Based (SERVER)</h5>
</div>
</div>
</div>
<p>
- The
+ The server based variant of BACKEND places the back end logic on the server side. SERVER additionally provides logic for FRONTEND to be able to communicate with the server side code.
</p>
</div>
</div>
Modified: public/phoenix/deliverables/planning/roadmap.xml
===================================================================
--- public/phoenix/deliverables/planning/roadmap.xml 2006-04-28 20:38:22 UTC (rev 12954)
+++ public/phoenix/deliverables/planning/roadmap.xml 2006-04-28 21:06:06 UTC (rev 12955)
@@ -46,31 +46,37 @@
</para>
<section>
<title>Front End Component (FRONTEND)</title>
+ <para>
+ The front end component is responsible for the handling the view. FRONTEND performs tasks like rendering the document, supplying user interaction facilities, etc.
+ </para>
<section>
<title>Browser Integrated Variant (BROWSER)</title>
<para>
- The browser integrated variant of the front end is a XUL widget which integrates seamlessly into web browsers based on the Mozilla Platform. BROWSER must be able to work with up-to-date versions of Firefox and SeaMonkey (formerly Mozilla Suite).
+ The browser integrated variant of FRONTEND is a XUL widget which integrates seamlessly into web browsers based on the Mozilla Platform. BROWSER must be able to work with up-to-date versions of Firefox and SeaMonkey (formerly Mozilla Suite).
</para>
</section>
<section>
<title>Standalone Variant (STANDALONE)</title>
<para>
- The
+ The standalone variant of the FRONTEND can be used as a standalone editor, independent of a web browser. Like the browser integrated version, STANDALONE is based on XUL.
</para>
</section>
</section>
<section>
<title>Back End Component (BACKEND)</title>
+ <para>
+ The back end component comprises the controller and the model. BACKEND performs tasks like ID Tagging, XSLT processing, validation, etc.
+ </para>
<section>
<title>Client Based Variant (CLIENT)</title>
<para>
- The
+ The client based variant of BACKEND places the back end logic on the client side.
</para>
</section>
<section>
<title>Server Based (SERVER)</title>
<para>
- The
+ The server based variant of BACKEND places the back end logic on the server side. SERVER additionally provides logic for FRONTEND to be able to communicate with the server side code.
</para>
</section>
</section>
More information about the Phoenix-commits
mailing list