S T A T U S =========== $Id: STATUS,v 1.8 2003/06/28 05:09:27 nbubna Exp $ Known Issues/Bugs: - Nothing of note! :) Documentation: - get docs up on jakarta public site - Complete user guide. - Document RenderTool, ViewRenderTool, IteratorTool, AbstractSearchTool - Create a developer's guide. - Update plan for Velocimacro libraries Proposed Features/Upgrades: General: - convert project to use Maven VelocityView: - add a library of general velocimacros - Convert XMLToolboxManager to use commons' Digester - Switch to non-singleton mode of Velocity to allow different instances/configurations of VVS in the same classloader/application/JVM - Pluggable toolbox manager in VelocityViewServlet - Tool pooling support (use commons-pool probably) - add an ImportTool? (actually might fit under generic tools) - add CookieTool Generic tools: - add a library of velocimacros for use with these tools - Template debugging tool(s)/support VelocityStruts: - add a library of velocimacros for use with struts tools (ideally these would be roughly parallel to struts tags to ease transition) - Struts 1.1 Support: - ActionMessages - add getActionMessages() to StrutsUtils - move ActionMessagesTool from whiteboard/nathan to main - Validator - tool to access javascripts? - integration with FormTool/MessagesTool? - Tiles? - Modules (sub-apps) - multiple config files - multiple message resources - etc. Examples: - Create a blank Velocity-Struts application as the starting point for development. - Create a simple Velocity-Struts application to demonstrate use of VelocityLayoutServlet (and other new features like the search tool) - Create a Struts 1.1 example. Take one of the existing Struts 1.1 examples and replace the view layer with Velocity. - Create example app(s) that demonstrate the use of other new features. (a macro-library example would be a good one to start with.)