[FOray-commit] SF.net SVN: foray:[12801] trunk/foray/foray-fotree/src/main/java/org/foray /fotree/package-info.java

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

Revision: 12801
          http://sourceforge.net/p/foray/code/12801
Author:   victormote
Date:     2022-12-07 13:29:23 +0000 (Wed, 07 Dec 2022)
Log Message:
-----------
Doc changes only.

Modified Paths:
--------------
    trunk/foray/foray-fotree/src/main/java/org/foray/fotree/package-info.java

Modified: trunk/foray/foray-fotree/src/main/java/org/foray/fotree/package-info.java
===================================================================
--- trunk/foray/foray-fotree/src/main/java/org/foray/fotree/package-info.java	2022-12-07 12:52:54 UTC (rev 12800)
+++ trunk/foray/foray-fotree/src/main/java/org/foray/fotree/package-info.java	2022-12-07 13:29:23 UTC (rev 12801)
@@ -29,6 +29,26 @@
 /**
  * <p>Classes for parsing and representing the XSL-FO document input objects and properties in the various
  * namespaces.</p>
+ *
+ * <p>Future development for foray-fotree:</p>
+ * <ul>
+ *   <li>TODO: Make property value objects immutable and therefore reusable, where possible.</li>
+ *   <li>TODO: Make property objects immutable and therefore reusable, where possible. This should be trivial for
+ *   properties whose value is a keyword, but may be possible and practical for others as well. For example, a font-size
+ *   of "11pt" is highly likely to be used many times. For an example of doing this with keywords, see
+ *   {@link org.foray.fotree.fo.prop.PdDominantBaseline}. Some thought should be given how best to store and retrieve
+ *   the reusable properties, making that a standard, and pushing it to the superclass(es).</li>
+ *   <li>TODO: There are opportunities in the {@link org.foray.fotree.Namespace} subclasses to push some logic from the
+ *   subclasses into {@link org.foray.fotree.Namespace}, especially error-handling.</li>
+ *   <li>TODO: There are cleanup opportunites in the test classes and superclasses, for example
+ *   org.foray.fotree.AbstractPropertyTests.</li>
+ *   <li>TODO: Do we still need the object and property ID classes, i.e. those that are enums of the names of objects
+ *   and properties in each namespace. Examples: {@link org.foray.fotree.fo.FoObjectId} and
+ *   {@link org.foray.fotree.fo.FoPropertyId}. Some of those were written to allow switch statements to work back when
+ *   we could not switch on String. It could be that switching on String would be more efficient now.</li>
+ *   <li>TODO: Investigate whether Java 1.8 lambda functions would help us with parsing.</li>
+ *   <li>TODO: There is a lot of unit tests still be be written.</li>
+ * </ul>
  */
 
 package org.foray.fotree;

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