commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From di...@apache.org
Subject cvs commit: jakarta-commons-sandbox/javaflow/xdocs/images javaflow-logo-white.png javaflow-logo-white.xcf
Date Sun, 16 Jan 2005 20:02:10 GMT
dirkv       2005/01/16 12:02:10

  Added:       javaflow/xdocs downloads.xml index.xml navigation.xml
               javaflow/xdocs/images javaflow-logo-white.png
                        javaflow-logo-white.xcf
  Log:
  add website
  
  Revision  Changes    Path
  1.1                  jakarta-commons-sandbox/javaflow/xdocs/downloads.xml
  
  Index: downloads.xml
  ===================================================================
  <?xml version="1.0"?>
  <document>
     <properties>
        <title>Downloads</title>
        <author email="commons-dev@jakarta.apache.org">Commons Documentation Team</author>
        <revision>$Id: downloads.xml,v 1.1 2005/01/16 20:02:10 dirkv Exp $</revision>
     </properties>
  
     <body>
        <section name="Releases">
           <p>There are no releases available.</p>
  
  <!--
           <p>The following releases are available:</p>
           <ul>
             <li>Version 1.1 - 20 October 2003</li>
             <li>Version 1.0 - 12 August 2002</li>
           </ul>
           <br/>
           <p>
              The latest binary release is always available on the 
              <a href="http://jakarta.apache.org/site/binindex.cgi#commons-javaflow">
              Jakarta Binary Downloads page</a>,
              its source is available from 
              <a href="http://jakarta.apache.org/site/sourceindex.cgi#commons-javaflow">
              Jakarta Source Downloads page</a>.
           </p>
           <p>
              Older releases are retained by the Apache Software Foundation but are 
              moved into a
              <a href="http://archive.apache.org/dist/jakarta/commons/javaflow/">
              special archive area</a>.
           </p>
           <p>
             <a href="http://cvs.apache.org/builds/jakarta-commons/nightly/commons-javaflow/">
             Nightly source and binary drops</a> are available.
           </p>
  -->
           <p>
              Access to the source tree to see the latest and greatest code is possible
              through <a href="cvs-usage.html">anonymous CVS access</a>.
           </p>
        </section>
  
  <!--
        <section name="Release Candidate">
           <p>
              Release candidates for the upcoming 1.1 release can be downloaded 
              <a href="http://cvs.apache.org/~dirkv/builds/">here</a>.
           </p>
           <p>
              Please review and report any problem on the 
              <a href="mail-lists.html">mailing list</a>.
           </p>
           <p>
              Final release target is 20 October 2003. 
           </p>
        </section>
  -->
     </body>
  </document>
  
  
  
  1.1                  jakarta-commons-sandbox/javaflow/xdocs/index.xml
  
  Index: index.xml
  ===================================================================
  <?xml version="1.0"?>
  
  <document>
  
   <properties>
    <title>Overview</title>
    <author email="commons-dev@jakarta.apache.org">Commons Documentation Team</author>
   </properties>
  
   <body>
  
  <section name="The Javaflow Component">
  
  <p>
     Sometimes it is usefull if we can capture the state of the application, its 
     stack of function calls, which includes local variables, the global variables 
     and the program counter, and save them into an object. If this object would 
     give us the ability to restart the processing from the point stored in it.
  </p>
  <p>
     A continuation is exactly the type of object that we need. Think of a 
     continuation as an object that, for a given point in your program, contains
     a snapshot of the stack trace, including all the local variables, and the 
     program counter. You can not only store these things in the continuation 
     object, but also restore the execution of the program from a continuation 
     object. This means that the stack trace and the program counter of the 
     running program become the ones stored in a continuation.
  </p>
  <p>
     Continuations are powerful concepts from the world of functional languages,
     like Scheme, but they are becoming popular in other languages as well.
  </p>
  
  </section>
  
  <section name="Releases">
      <p>
         See the <a href="downloads.html">downloads</a> page for information on
obtaining releases.
      </p>
  </section>
  
  <section name="Documentation">
    <p>
       The <a href="apidocs/index.html">JavaDoc API documents</a> are available
online.
    </p>
  </section>
  
  </body>
  </document>
  
  
  
  1.1                  jakarta-commons-sandbox/javaflow/xdocs/navigation.xml
  
  Index: navigation.xml
  ===================================================================
  <?xml version="1.0" encoding="ISO-8859-1"?>
  <!DOCTYPE org.apache.commons.menus SYSTEM '../../../jakarta-commons/commons-build/menus/menus.dtd'>
  <project name="Commons&#xA0;JCI">
      <title>Commons&#xA0;Javaflow</title>
      <body>
          <menu name="Commons&#xA0;Javaflow">
              <item name="Overview"                      href="/index.html" />
              <item name="API&#xA0;Documentation"        href="/apidocs/index.html"/>
              <item name="Downloads"                     href="/downloads.html"/>
          </menu>
          &common-menus;
      </body>
  </project>
  
  
  
  1.1                  jakarta-commons-sandbox/javaflow/xdocs/images/javaflow-logo-white.png
  
  	<<Binary file>>
  
  
  1.1                  jakarta-commons-sandbox/javaflow/xdocs/images/javaflow-logo-white.xcf
  
  	<<Binary file>>
  
  

---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org


Mime
View raw message