cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From stef...@locus.apache.org
Subject cvs commit: xml-cocoon/xdocs cocoon2.xml docs-book.xml installing.xml site-book.xml
Date Wed, 23 Feb 2000 00:42:53 GMT
stefano     00/02/22 16:42:52

  Modified:    xdocs    cocoon2.xml docs-book.xml installing.xml
                        site-book.xml
  Log:
  improved sitebars and better doc on cocoon2 + sitemap
  
  Revision  Changes    Path
  1.3       +68 -13    xml-cocoon/xdocs/cocoon2.xml
  
  Index: cocoon2.xml
  ===================================================================
  RCS file: /home/cvs/xml-cocoon/xdocs/cocoon2.xml,v
  retrieving revision 1.2
  retrieving revision 1.3
  diff -u -r1.2 -r1.3
  --- cocoon2.xml	2000/02/14 00:57:52	1.2
  +++ cocoon2.xml	2000/02/23 00:42:51	1.3
  @@ -11,6 +11,13 @@
    </header>
   
    <body>
  + <s1 title="A new look">
  +  <p>The Cocoon Project will evidence its new course with a new logo that was
  +  designed by Cocoon's creator Stefano Mazzocchi. Here it is:</p>
  +
  +  <figure src="images/cocoon2.gif" alt="The new Cocoon Logo"/>
  + </s1>
  +
    <s1 title="Introduction">
     <p>The Cocoon Project has gone a long way since it's creation on
     January 1999. It started as a simple servlet for static XSL styling and became
  @@ -43,7 +50,7 @@
   
     <p>For the above reasons, Cocoon1 was based on the DOM level 1
     API which is a <em>passive</em> API and was intended mainly for client side
  -  operation. This is mainly due to the fact that most (if not all!) DOM
  +  operation. This is mainly due to the fact that most DOM
     implementations require the document to reside in memory. While this is
     practical for small documents and thus good for the &quot;proof of
     concept&quot; stage, it is now considered a main design constraint for Cocoon
  @@ -140,13 +147,13 @@
     distributing them back on information owners. While this model is great for
     user communities (scientists, students, employees, or people in general) each
     of them managing small amount of personal information, it becomes impractical
  -  for highly centralized information systems where distributed management is
  -  simply not practical.</p>
  +  for highly centralized information systems where <em>distributed management</em>
  +  is simply not practical.</p>
   
     <p>While in the HTML web model the page format and URL names
     where the only necessary contracts between individuals to create a world wide
     web, in more structured information systems the number of contracts increases
  -  by a significant factor due to the need of increased coherence between the
  +  by a significant factor due to the need of coherence between the
     hosted information: common style, common design issues, common languages,
     server side logic integration, data validation, etc...</p>
   
  @@ -195,7 +202,7 @@
       </dd>
     </dl>
   
  -  <p>and five contracts contexts (the lines)</p>
  +  <p>and five contracts (the lines)</p>
   
     <ul>
       <li>management - content</li>
  @@ -204,6 +211,10 @@
       <li>content - logic</li>
       <li>content - style</li>
     </ul>
  +
  +  <p>note that there is no <em>logic - style</em> contract. Cocoon2 aims
to
  +  provide both software and guidelines to allow you to remove such
  +  contract.</p>
   </s1>
   
   <s1 title="Overlapping contexts and Chain Mapping">
  @@ -219,7 +230,7 @@
     break the pyramid model and increase the management costs.</p>
   
     <p>In Cocoon2, the reactor pattern will be abandoned in favor of
  -  a chain mapping technique. This is based on the fact that the number of
  +  a pipeline mapping technique. This is based on the fact that the number of
     different contracts is limited even for big sites and grows with a rate
     that is normally much less than its size.</p>
   
  @@ -241,6 +252,44 @@
      core</note>
   </s1>
   
  +<s1 title="Sitemap">
  +  <p>In Cocoon2 terminology, a <em>sitemap</em> is the collection of
pipeline
  +  matching informations that allow the Cocoon engine to associate the requested
  +  URI to the proper response-producing pipeline.</p>
  +
  +  <p>The sitemap physically represents the central repository for web site
  +  administration, where the URI space and its handling is maintained. An example
  +  of the sitemap is given below:</p>
  +
  +<source>
  +<![CDATA[
  +  <sitemap>
  +   <process match="/press/en/*.html">
  +    <generator type="file" src="/docs/english/press/*.xml"
  +    <filter type="xslt">
  +     <parameter name="stylesheet" value="/styles/simple-press-html.xsl"/>
  +    </filter>
  +    <serializer type="html"/>
  +   </process>
  +
  +   <process match="/press/en/*.pdf">
  +    <generator type="file" src="/docs/english/press/*.xml"
  +    <filter type="xslt">
  +     <parameter name="stylesheet" value="/styles/simple-press-pdf.xsl"/>
  +    </filter>
  +    <serializer type="fop"/>
  +   </process>
  +  </sitemap>
  +]]>
  +</source>
  +
  +  <note>The sitemap DTD has not yet been standardized and it's not guaranteed
  +  to solidify until Cocoon 2.0 is out final. So, the above should be considered
  +  just as a preview and not a specification or even a working draft. For more
  +  information dig into the development mail list digests.</note>
  +
  +</s1>
  +
   <s1 title="Pre-compilation, Pre-generation and Caching">
     <p>The cache system in Cocoon1 will be ported with no important
     design changes since it's very flexible and was not polluted by early design
  @@ -255,6 +304,8 @@
     way to <em>regenerate</em> the static part of a web site (images and tables
     included!) based on the same XML model used in the dynamic operation version.</p>
   
  +  <p>Cocoon2 will, in fact, be the integration between Cocoon1 and Stylebook.</p>
  +
     <p>It will be up to the web server administrator to use static
     regeneration capabilities on a time basis, manually or triggered by some
     particular event (database update signal) since Cocoon2 will only provide
  @@ -268,14 +319,18 @@
     compilation (which make debugging harder) with command line pre-compilation
     hooks that will work like normal compilers from a developer's point of view.</p>
   </s1>
  +
  +<s1 title="Development Status">
  +  <p>Cocoon2 development already started, but should be considered of pre-alpha
  +  quality. If you dare, you might take a look at it on the <em>xml-cocoon2</em>
  +  CVS branch in the Cocoon CVS module, or, if you are not a CVS expert, this means
  +  typing:</p>
   
  -<s1 title="Conclusions">
  -  <p>Cocoon2 is a big and very ambitious project, not only for the
  -  technological issues involved (which will require strong integration with XML
  -  components) but also for the significant paradigm shifts imposed by the new
  -  technologies. On the other hand, we strongly believe this to be the winner
  -  model for future web engineering and if you believe in this yourself, we
  -  invite you to join us or help us in any way you can provide.</p>
  +  <source>cvs checkout -r xml-cocoon2 cocoon-xml</source>
  +
  +  <p>For more information on CVS access, refer to the CVS-howtos on this web
  +  site.</p>
   </s1>
  +
   </body>
   </document>
  
  
  
  1.4       +4 -2      xml-cocoon/xdocs/docs-book.xml
  
  Index: docs-book.xml
  ===================================================================
  RCS file: /home/cvs/xml-cocoon/xdocs/docs-book.xml,v
  retrieving revision 1.3
  retrieving revision 1.4
  diff -u -r1.3 -r1.4
  --- docs-book.xml	2000/02/13 18:29:43	1.3
  +++ docs-book.xml	2000/02/23 00:42:51	1.4
  @@ -18,7 +18,7 @@
   <separator/>
     <spec id="wd-xsp" label="XSP WD" source="WD-xsp.xml"/>
   <separator/>
  -  <external href="./api/index.html"  label="Javadocs"/>
  +  <external label="Javadocs" href="./api/index.html"/>
   <separator/>
     <page id="cocoon2" label="Cocoon 2" source="cocoon2.xml"/>
     <page id="javadoc" label="Javadoc XML" source="javadoc.xml"/>
  @@ -26,5 +26,7 @@
     <faqs id="faqs" label="FAQ" source="faq.xml"/>
     <changes id="changes" label="Changes" source="changes.xml"/>
     <todo id="todo" label="Todo" source="todo.xml"/>
  - 
  +<separator/>
  +  <external label="Mail Archive" href="http://xml-archive.webweaving.org"/>
  +  <external label="Bug Database" href="http://xml.apache.org/bugs/"/>
   </book>
  
  
  
  1.5       +6 -0      xml-cocoon/xdocs/installing.xml
  
  Index: installing.xml
  ===================================================================
  RCS file: /home/cvs/xml-cocoon/xdocs/installing.xml,v
  retrieving revision 1.4
  retrieving revision 1.5
  diff -u -r1.4 -r1.5
  --- installing.xml	2000/02/14 12:21:14	1.4
  +++ installing.xml	2000/02/23 00:42:51	1.5
  @@ -443,6 +443,12 @@
      <td colspan="2">Jetty Java HTTP Server v2.3.3</td>
      <td>Blackdown jdk-1.2.2-RC4-linux-i386-glibc</td>
     </tr>
  +  <tr>
  +   <td>SuSE 6.3 Linux</td>
  +   <td>Apache 1.3.9</td>
  +   <td>Apache JServ 1.1</td>
  +   <td>Sun JDK 1.2.2</td>
  +  </tr>
     </table>
   
     <note>
  
  
  
  1.3       +7 -2      xml-cocoon/xdocs/site-book.xml
  
  Index: site-book.xml
  ===================================================================
  RCS file: /home/cvs/xml-cocoon/xdocs/site-book.xml,v
  retrieving revision 1.2
  retrieving revision 1.3
  diff -u -r1.2 -r1.3
  --- site-book.xml	2000/02/09 21:12:14	1.2
  +++ site-book.xml	2000/02/23 00:42:51	1.3
  @@ -1,6 +1,6 @@
   <?xml version="1.0"?>
   
  -<book title="Cocoon documentation" copyright="1999 The Apache Software Foundation">
  +<book title="Cocoon documentation" copyright="@year@ The Apache Software Foundation">
   
     <external href="../index.html"  label="Back"/>
   <separator/>
  @@ -30,5 +30,10 @@
     <faqs id="faqs" label="FAQ" source="faq.xml"/>
     <changes id="changes" label="Changes" source="changes.xml"/>
     <todo id="todo" label="Todo" source="todo.xml"/>
  - 
  +<separator/>
  +  <external label="Code Repository" href="http://xml.apache.org/websrc/cvsweb.cgi/xml-cocoon"/>
  +  <external label="Dev Snapshots" href="http://xml.apache.org/from-cvs/xml-cocoon/"/>
  +  <external label="Mail Archive" href="http://xml-archive.webweaving.org"/>
  +  <external label="Bug Database" href="http://xml.apache.org/bugs/"/>
  +
   </book>
  
  
  

Mime
View raw message