From forrest-cvs-return-881-apmail-xml-forrest-dev-archive=xml.apache.org@xml.apache.org Mon Apr 28 13:25:44 2003 Return-Path: Delivered-To: apmail-xml-forrest-dev-archive@xml.apache.org Received: (qmail 95631 invoked by uid 500); 28 Apr 2003 13:25:41 -0000 Mailing-List: contact forrest-cvs-help@xml.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: forrest-dev@xml.apache.org Delivered-To: mailing list forrest-cvs@xml.apache.org Received: (qmail 95552 invoked from network); 28 Apr 2003 13:25:38 -0000 Received: from icarus.apache.org (208.185.179.13) by daedalus.apache.org with SMTP; 28 Apr 2003 13:25:38 -0000 Received: (qmail 11966 invoked by uid 1352); 28 Apr 2003 13:25:37 -0000 Date: 28 Apr 2003 13:25:37 -0000 Message-ID: <20030428132537.11965.qmail@icarus.apache.org> From: jefft@apache.org To: xml-forrest-cvs@apache.org Subject: cvs commit: xml-forrest status.xml X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N jefft 2003/04/28 06:25:37 Modified: . status.xml Log: Update todo list Revision Changes Path 1.152 +145 -178 xml-forrest/status.xml Index: status.xml =================================================================== RCS file: /home/cvs/xml-forrest/status.xml,v retrieving revision 1.151 retrieving revision 1.152 diff -u -r1.151 -r1.152 --- status.xml 28 Apr 2003 06:21:12 -0000 1.151 +++ status.xml 28 Apr 2003 13:25:37 -0000 1.152 @@ -726,187 +726,154 @@ - - - Standardize the work on - the rest of the DTDs that will be required by Forrest. - - - Ensure that PHP-like stuff can be enbedded easily in Forrest files and - document it. - - - Finalise the project-definition DTDs, like status.xml and module.xml; - try to come up with a common format with others on community.at.apache.org. - - - The document-v11 DTD needs to rationalise the use of link|jump|fork - elements and clarify their use in the documentation. - See email discussion - - DTD/XSLT mods: link and jump and - DTD questions - Eventually move to something more similar to xhtml 1.1 or 2-draft. - Nicola Ken suggests adding 'a' as an altrernative tag for 'link'. - - - Fix or work around the - images-in-PDF problem - by using latest FOP and Cocoon from CVS. - - - Images (<figure>) are not yet handled by the PDF generation. - see skins/forrest-site/xslt/fo/document2fo.xsl and email - Re: document2Fo.xsl - and - Re: Images not appearing in PDF's - - - Fix the logging (logkit.xconf) to stop Cocoon generating 370k (!) of - logs per page rendered. - - Fix whatever it is that causes Jisp to fill error.log with these: - - 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) - - - + Rework the menu generation system to make it more flexible. See thread + Fixing + menus + + + Define an 'object model' for Forrest sites, in the form of a Cocoon + pipeline, that defines +
    +
  • The directory structure of a site
    • +
  • Site metadata (what currently lives in skinconf.xml + gump.xml + stuff)
    • +
  • Perhaps site.xml metadata for pages?
    • +
+ This info can then be made public to the sitemap (via XMLFileModule + attributes) and the stylesheets (through + document(cocoon:/...) calls or inlined with source XML). + + + Finalise the project-definition DTDs, like status.xml and module.xml; + try to come up with a common format with others on community.at.apache.org. + + + The document-v11 DTD needs to rationalise the use of link|jump|fork + elements and clarify their use in the documentation. + See email discussion - + DTD/XSLT mods: link and jump and + DTD questions + Eventually move to something more similar to xhtml 1.1 or 2-draft. + Nicola Ken suggests adding 'a' as an altrernative tag for 'link'. + + + Figure out a way of rendering pages that aren't linked to from anywhere. + + - - - Finish the RSS feed for status.xml. - Aggregate status.xml and project.xml to have all needed project data. - - - 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. - - - Add stylesheets to render the enhanced status.xml file contents. - - - Allow the obfuscation of mailto links to be configurable. - - - Add a document about authoring in XML for beginners.. - - - In skinconf.xml, change 'disable-search' to 'enable-search'. - - - Enhance the initial forrest toolbar for Mozilla. - See email discussion draft forrest toolbar for Mozilla. - - - 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. - - - Make a CSS Generator and a stylesheet to serialize it to text. - - - 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? - - - 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]. - - - Act on 'Entities in XML docs' RT. - 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. - - - 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. - - - Skinify Miles Elam's forrest.iguanacharlie.com CSS mockup. The rounded - tabs would require the CSS image traversal fix, but it's not essential. - - - Schema issues. There are lots of change requests (see - etc/DTD_DEFICIENCIES.txt) and an immediate need for some sort of DTD - versioning policy. - - - 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. - - + + + Finish the RSS feed for status.xml. + Aggregate status.xml and project.xml to have all needed project data. + + + 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. + + + Add stylesheets to render the enhanced status.xml file contents. + + + Allow the obfuscation of mailto links to be configurable. + + + In skinconf.xml, change 'disable-search' to 'enable-search'. + + + Enhance the initial forrest toolbar for Mozilla. + See email discussion draft forrest toolbar for Mozilla. + + + 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. + - - - Define a simple mechanism for staging. - - - Add the PATCHQUEUE system to Forrest, as used by cocoon-dev.at.xml.apache.org - - - Develop a mechanism for supporting legacy URLs. - See email discussion - - redirects with static sites - - - Continue the development of the new - Libre - facility - replacement for */book.xml - - - Start a community doc where we list such - tools as forrestbar, config files for XMetaL, etc. - - - Migrate to a decent schema language, primarily so that we can use - namespaces in XML docs, allowing things like XInclude, - in-line metadata, - in-line SVG, Jelly snippets, or anything else users can make a - Transformer for. - - - 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. - - - Create a forrest-users list, so we can have flaming rows on forrest-dev - over arcana without annoying users :) - - - Create a Forrest Maven plugin. This is probably the biggest single way - to widen Forrest's exposure and attract new users. - - - + + 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]. + + + Act on 'Entities in XML docs' RT. + 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. + + + Skinify Miles Elam's forrest.iguanacharlie.com CSS mockup. The rounded + tabs would require the CSS image traversal fix, but it's not essential. + + + 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. + + + Develop a mechanism for supporting legacy URLs. + See email discussion - + redirects with static sites + + + Create a Forrest Maven plugin. This is probably the biggest single way + to widen Forrest's exposure and attract new users. + + + + + + + Ensure that PHP-like stuff can be enbedded easily in Forrest files and + document it. + + + Add the PATCHQUEUE system to Forrest, as used by cocoon-dev + + + Continue the development of the Libre facility - replacement for + */book.xml + + + Start a community doc where we list such + tools as forrestbar, config files for XMetaL, etc. + + + Migrate to a decent schema language, primarily so that we can use + namespaces in XML docs, allowing things like XInclude, + in-line metadata, + in-line SVG, Jelly snippets, or anything else users can make a + Transformer for. + + + 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. + + + Create a forrest-users list, so we can have flaming rows on forrest-dev + over arcana without annoying users :) + + + Make a CSS Generator and a stylesheet to serialize it to text. + + + Add a document about authoring in XML for beginners.. + + + +