[FOray-commit] SF.net SVN: foray: [7589] trunk/foray/doc/web/dev/fotree/index.html

[<vic...@us...>]

Revision: 7589
Author:   victormote
Date:     2006-06-14 10:16:29 -0700 (Wed, 14 Jun 2006)
ViewCVS:  http://svn.sourceforge.net/foray/?rev=7589&view=rev

Log Message:
-----------
Add more big-picture to-do items.

Modified Paths:
--------------
    trunk/foray/doc/web/dev/fotree/index.html
Modified: trunk/foray/doc/web/dev/fotree/index.html
===================================================================
--- trunk/foray/doc/web/dev/fotree/index.html	2006-06-14 16:49:53 UTC (rev 7588)
+++ trunk/foray/doc/web/dev/fotree/index.html	2006-06-14 17:16:29 UTC (rev 7589)
@@ -319,8 +319,27 @@
 instantiation.</p>
 
 <h2><a name="todo"/>To Do</h2>
-<p>The "to-do" items are recorded in the source code itself, and tagged with
-the string "TODO".</p>
+<p>Known code deficiencies are recorded in the source code itself, and tagged
+with the string "TODO".</p>
+<p>General features that we would like to add include the following:</p>
+<ul>
+  <li>If the user doesn't need round-tripping of the FOTree, consider allowing
+earlier binding of property values where possible. Also, if performance is
+improved by it, allow bound properties to be pushed down to child objects that
+need them. These are purely for performance reasons.</li>
+  <li>So far, data validation has been on an opportunistic, haphazard manner.
+We need to comprehensively address every FO object for proper ancestry,
+properties, and descendants.</li>
+  <li>We need a testing system specifically for the FOTree.</li>
+  <li>After absolutely all property-related to-do items in the code itself
+are cleared, we need a project to clean up and consolidate code in the property
+sub-system.</li>
+  <li>Devise a new (extension) Formatting Object whose purpose is solely to
+contain properties, and which can be referenced from other Formatting objects by
+name. This would significantly reduce parsing time and increase FO document
+human readability, and may make stylesheet creation more intuitive.</li>
+  <li>FOTrees that cannot fit in memory should be serialized.</li>
+</ul>
 
 <h2><a name="resolved"/>Resolved Issues</h2>
 <p>Compound properties can be created either with a short form or a complete form,


This was sent by the SourceForge.net collaborative development platform, the world's largest Open Source development site.