forrest-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From nicola...@apache.org
Subject cvs commit: xml-forrest status.xml
Date Tue, 05 Nov 2002 07:26:47 GMT
nicolaken    2002/11/04 23:26:47

  Modified:    .        status.xml
  Log:
  Updated todo list.
  
  Revision  Changes    Path
  1.35      +24 -38    xml-forrest/status.xml
  
  Index: status.xml
  ===================================================================
  RCS file: /home/cvs/xml-forrest/status.xml,v
  retrieving revision 1.34
  retrieving revision 1.35
  diff -u -r1.34 -r1.35
  --- status.xml	4 Nov 2002 21:37:15 -0000	1.34
  +++ status.xml	5 Nov 2002 07:26:47 -0000	1.35
  @@ -21,21 +21,17 @@
     <todo>
      <actions priority="high">
       <action context="code" dev="SN">
  -     Merge other Gump DTDs and work on them. We have to standardize the work on
  +     Standardize the work on
        the rest of the DTDs that will be required by Forrest.
       </action>
       <action context="code" dev="open">
  -     Fine-tune the draft XGump DTD for forrest.xgump
  -    </action>
  -    <action context="code" dev="open">
  -     Ensure solid XML infrastructure. Ensure that the catalog entity resolver
  -     is working. At least the initial XML instances need to validate using
  -     external tools.
  -    </action>
  +     Ensure that PHP-like stuff can be enbedded easily in Forrest files and
  +     document it.
  +    </action>    
       <action context="code" dev="NKB">
  -     Make Gump update Forrest site automagically;
  -     in the future this will be used for the generation of other projects too.
  -    </action>
  +     Finalise the project-definition DTDs, like status.xml and module.xml;
  +     try to come up with a common format with others on community@apache.org.
  +    </action>    
       <action context="code" dev="open">
        The document-v11 DTD needs to rationalise the use of link|jump|fork
        elements and clarify their use in the documentation.
  @@ -47,58 +43,48 @@
   
      <actions priority="medium">
       <action context="code" dev="open">
  -     Fix the Cocoon CLI so that book.xml links can specify directories
  -     ("subdir/") and not break.
  -    </action>
  +     Define a simple mechanism for staging.
  +    </action>      
  +    <action context="docs" dev="open">
  +     Add a document about authoring in XML for beginners..
  +    </action>   
       <action context="code" dev="open">
  -     Fix font size for forrest-site skin. It is currently set to '90%'.
  -     See thread <link
  -      href="http://marc.theaimsgroup.com/?t=103114847800007&amp;r=1&amp;w=2">Font
too
  -      small?</link>
  +     Fix the Cocoon CLI so that it spits out more meaningful error messages.
       </action>
       <action context="code" dev="JT">
          In skinconf.xml, change 'disable-search' to 'enable-search'.
       </action>
       <action context="code" dev="open">
  -     Continue the development of the new
  -     <link href="libre-intro.html">Libre</link>
  -     facility - replacement for */book.xml
  -    </action>
  -    <action context="code" dev="open">
        Images (&lt;figure&gt;) are not yet handled by the PDF generation.
        see <code>skins/forrest-site/xslt/fo/document2fo.xsl</code> and email
        <link href="http://marc.theaimsgroup.com/?l=forrest-dev&amp;m=102725960101549">Re:
document2Fo.xsl</link>
        and 
        <link href="http://marc.theaimsgroup.com/?l=forrest-dev&amp;m=103009053230213">Re:
Images not appearing in PDF's</link>
       </action>
  -    <action context="code" dev="open">
  -     Remove the dependency on IzPress ... this causes the automated Gump build 
  -     of Forrest to fail. It has been temporarily disabled by comment-out
  -     of forrest.xgump, but the jar and Ant tasks remain. (See
  -     <link href="http://marc.theaimsgroup.com/?l=forrest-dev&amp;m=102406503426469">Gumping
_Forrest_</link>)
  -    </action>
  -    <action context="code" dev="open">
  -     Why do we need to always use "build clean" before doing "build docs"?
  -     Perhaps something with the re-introduction of Jisp.
  -     See email discussion at <link href="http://marc.theaimsgroup.com/?l=forrest-dev&amp;m=102767862102557">http://marc.theaimsgroup.com/?l=forrest-dev&amp;m=102767862102557</link>
  -    </action>
       <action context="design" dev="open">
        Clarify the URL namespace architecture for Forrest and document it.
       </action>
  +    <action context="code" dev="open">
  +     Enhance the initial forrest toolbar for Mozilla.
  +     See email discussion <link href="http://marc.theaimsgroup.com/?l=forrest-dev&amp;m=102471820523388">draft
forrest toolbar for Mozilla</link>.
  +    </action>
  +   </actions>
  +   <actions priority="low">
       <action context="design" dev="open">
        Develop a mechanism for supporting legacy URLs.
        See email discussion -
        <link href="http://marc.theaimsgroup.com/?l=forrest-dev&amp;m=102390892524750">redirects
with static sites</link>
  -    </action>
  +    </action>   
       <action context="code" dev="open">
  -     Enhance the initial forrest toolbar for Mozilla.
  -     See email discussion <link href="http://marc.theaimsgroup.com/?l=forrest-dev&amp;m=102471820523388">draft
forrest toolbar for Mozilla</link>.
  +     Continue the development of the new
  +     <link href="libre-intro.html">Libre</link>
  +     facility - replacement for */book.xml
       </action>
       <action context="docs" dev="open">
        Start a community doc where we list such
        tools as forrestbar, config files for XMetaL, etc.
       </action>
  -   </actions>
  +   </actions>    
     </todo>
   
     <changes>
  
  
  

Mime
View raw message