You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@forrest.apache.org by ni...@apache.org on 2003/01/03 19:15:30 UTC
cvs commit: xml-forrest status.xml
nicolaken 2003/01/03 10:15:30
Modified: . status.xml
Log:
Updated todos with latest stuff and committed myself to some tasks.
Revision Changes Path
1.87 +122 -21 xml-forrest/status.xml
Index: status.xml
===================================================================
RCS file: /home/cvs/xml-forrest/status.xml,v
retrieving revision 1.86
retrieving revision 1.87
diff -u -r1.86 -r1.87
--- status.xml 31 Dec 2002 08:23:36 -0000 1.86
+++ status.xml 3 Jan 2003 18:15:29 -0000 1.87
@@ -424,6 +424,7 @@
<todo>
<actions priority="high">
+
<action context="code" dev="SN">
Standardize the work on
the rest of the DTDs that will be required by Forrest.
@@ -442,50 +443,130 @@
See email discussion -
<link href="http://marc.theaimsgroup.com/?l=forrest-dev&m=102328646710432">DTD/XSLT mods: link and jump</link> and
<link href="http://marc.theaimsgroup.com/?l=forrest-dev&m=102339964119473">DTD questions</link>
+ Eventually move to something more similar to xhtml 1.1 or 2-draft.
+ Nicola Ken suggests adding 'a' as an altrernative tag for 'link'.
+ </action>
+ <action context="code" dev="open">
+ Fix or work around the
+ <link href="http://marc.theaimsgroup.com/?t=104065768300003&r=1&w=2">images-in-PDF problem </link>
+ by using latest FOP and Cocoon from CVS.
+ </action>
+ <action context="code" dev="open">
+ Images (<figure>) 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&m=102725960101549">Re: document2Fo.xsl</link>
+ and
+ <link href="http://marc.theaimsgroup.com/?l=forrest-dev&m=103009053230213">Re: Images not appearing in PDF's</link>
+ </action>
+ <action context="code" dev="open">
+ Fix the logging (logkit.xconf) to stop Cocoon generating 370k (!) of
+ logs per page rendered.
+ </action>
+ <action context="code" dev="open">
+ Fix whatever it is that causes Jisp to fill error.log with these:
+ <code>
+ ERROR (2002-12-25) 23:15.44:410 [core.store.persistent] (/forrest/community/index.html) Thread-13/JispFilesystemStore: get(..): Exception
+ com.coyotegulch.jisp.DatabaseException: no indexes associated with this database
+ at com.coyotegulch.jisp.IndexedObjectDatabase.<clinit>(IndexedObjectDatabase.java:88)
+ at org.apache.cocoon.components.store.JispFilesystemStore.initialize(JispFilesystemStore.java:237)
+ at org.apache.avalon.excalibur.component.DefaultComponentFactory.newInstance(DefaultComponentFactory.java:275)
+ at org.apache.avalon.excalibur.component.ThreadSafeComponentHandler.initialize(ThreadSafeComponentHandler.java:98)
+ at org.apache.avalon.excalibur.component.ExcaliburComponentManager.initialize(ExcaliburComponentManager.java:513)
+ at org.apache.cocoon.Cocoon.initialize(Cocoon.java:288)
+ </code>
</action>
</actions>
<actions priority="medium">
+ <action context="code" dev="NKB">
+ Finish the RSS feed for status.xml.
+ Aggregate status.xml and project.xml to have all needed project data.
+ </action>
<action context="webapp" dev="open">
Continue development of the editing system in the webapp.
Needs bugfixes, xml2wiki stylesheet and enhancements to the wiki grammer
especially to define sections and titles.
</action>
- <action context="code" dev="NKB">
- Add the PATCHQUEUE system to Forrest, as used by cocoon-dev.at.xml.apache.org
+ <action context="docs" dev="open">
+ Ad stylesheets to render the enhanced status.xml file contents.
</action>
- <action context="code" dev="open">
- 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 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">
- Images (<figure>) 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&m=102725960101549">Re: document2Fo.xsl</link>
- and
- <link href="http://marc.theaimsgroup.com/?l=forrest-dev&m=103009053230213">Re: Images not appearing in PDF's</link>
- </action>
- <action context="design" dev="open">
- Clarify the URL namespace architecture for Forrest and document it.
- </action>
- <action context="code" dev="open">
+ <action context="code" dev="NKB">
Enhance the initial forrest toolbar for Mozilla.
See email discussion <link href="http://marc.theaimsgroup.com/?l=forrest-dev&m=102471820523388">draft forrest toolbar for Mozilla</link>.
</action>
+ <action context="code" dev="open">
+ Optimise the CLI to deal with Javadocs, and other large sets of
+ pre-generated content. For example the Javadocs are placed in
+ src/documentation/content/javadocs, they will be traversed, but far too
+ slowly to be of practical use.
+ </action>
+ <action context="code" dev="NKB">
+ Make a CSS Generator and a stylesheet to serialize it to text.
+ </action>
+ <action context="code" dev="open">
+ Simplify the sitemap. It is getting rather complex, and as the source
+ of Forrest's power we need it to be accessible to newcomers.
+ I'd suggest moving all the stuff specific to Forrest's site
+ (apachestats, community/revision stuff, libre, .dtdx, editor) out into
+ a Forrest site-specific sitemap.xmap. Move anything else that can be
+ moved into subsitemaps. Perhaps using XML entities to suck in bits of
+ sitemap would be a decent way to manage future sitemap complexity, at
+ least until Cocoon Blocks arrive. Perhaps we can add XInclude support
+ to the sitemap?
+ </action>
+ <action context="code" dev="open">
+ Fix things so docs can be edited in src/*, and have the changes appear
+ immediately in the webapp. Involves creating/using an InputModule for
+ passing 'forrest.skin' and other properties to the sitemap, so we can
+ avoid the @skin@ hack, and a bit of forrest.build.xml hacking. There
+ are some @tokens@ in a forrest-site CSS file that also need some sort
+ of in-place modification. Perhaps a @token@-to-value Transformer could
+ be the same ${variable}-to-value Transformer mentioned in the RT [3].
+ </action>
+ <action context="code" dev="open">
+ Act on <link href="http://marc.theaimsgroup.com/?t=104099660500001&r=1&w=2">'Entities in XML docs' RT</link>.
+ I can implement Stefano's
+ suggested solution quite easily, but is such limited functionality
+ worth the cost of introducing a proprietary ${variable} syntax? Maybe..
+ Best short-term alternative seems to be using the XNI XInclude
+ processor for pre-validation inclusion.
+ </action>
+ <action context="code" dev="open">
+ Finish linkmaps, currently sitting in LINKMAP_BRANCH, I'd like to make
+ site.xml much more LSB-like, with file/folder element names and RDF
+ file metadata.
+ </action>
+ <action context="code" dev="open">
+ Skinify Miles Elam's forrest.iguanacharlie.com CSS mockup. The rounded
+ tabs would require the CSS image traversal fix, but it's not essential.
+ </action>
+ <action context="code" dev="open">
+ Schema issues. There are lots of change requests (see
+ etc/DTD_DEFICIENCIES.txt) and an immediate need for some sort of DTD
+ versioning policy.
+ </action>
+ <action context="code" dev="open">
+ Docs. A lot of the info on the website is outdated. With metadata
+ from site.xml, it would at least be possible to indicate how old the
+ doc is, and perhaps indicate its relevance from a small controlled
+ vocabulary.
+ </action>
</actions>
<actions priority="low">
- <action context="docs" dev="open">
- Ad stylesheets to render the enhanced status.xml file contents.
+ <action context="code" dev="open">
+ Define a simple mechanism for staging.
</action>
+ <action context="code" dev="NKB">
+ Add the PATCHQUEUE system to Forrest, as used by cocoon-dev.at.xml.apache.org
+ </action>
<action context="design" dev="open">
Develop a mechanism for supporting legacy URLs.
See email discussion -
@@ -499,6 +580,26 @@
<action context="docs" dev="open">
Start a community doc where we list such
tools as forrestbar, config files for XMetaL, etc.
+ </action>
+ <action context="code" dev="open">
+ Migrate to a decent schema language, primarily so that we can use
+ namespaces in XML docs, allowing things like XInclude,
+ <link href="http://www.xml.com/pub/a/2002/10/30/rdf-friendly.html">in-line metadata</link>,
+ in-line SVG, Jelly snippets, or anything else users can make a
+ Transformer for.
+ </action>
+ <action context="code" dev="open">
+ Streamline the process of adding support for new schemas. Ideally we'd
+ have an auto-download system, eg 'forrest-update docbook' would fetch
+ and install the Docbook DTDs, create catalog entries, sitemap mods etc.
+ </action>
+ <action context="code" dev="open">
+ Create a forrest-users list, so we can have flaming rows on forrest-dev
+ over arcana without annoying users :)
+ </action>
+ <action context="code" dev="open">
+ Create a Forrest Maven plugin. This is probably the biggest single way
+ to widen Forrest's exposure and attract new users.
</action>
</actions>
</todo>