| 1 |
S T A T U S
|
| 2 |
===========
|
| 3 |
$Id$
|
| 4 |
|
| 5 |
|
| 6 |
Known Issues/Bugs:
|
| 7 |
- see http://issues.apache.org/jira/browse/VELTOOLS
|
| 8 |
|
| 9 |
|
| 10 |
Documentation Wishlist:
|
| 11 |
- Complete user guide.
|
| 12 |
- Improve documention of the view tools (either xml/dvsl or javadoc)
|
| 13 |
- Create a developer's guide (how to write tools, tips on extending VVS, etc.)
|
| 14 |
|
| 15 |
|
| 16 |
Proposed Features/Upgrades:
|
| 17 |
General:
|
| 18 |
- finish/fix/improve Maven2 build support
|
| 19 |
- add more automated testing of tools
|
| 20 |
|
| 21 |
Generic tools:
|
| 22 |
- TableTool (VELTOOLS-102)
|
| 23 |
- Template debugging tool(s)/support
|
| 24 |
- Add support for ValueParser to use a properties file as a source
|
| 25 |
|
| 26 |
VelocityView:
|
| 27 |
- Tool pooling/cleanup support (use commons-pool probably)
|
| 28 |
- look into supporting arbitrary layout depth (sort of a "tiles lite")
|
| 29 |
for the VelocityLayoutServlet (cf. Niall's work with Simple)
|
| 30 |
- support for JSP tags
|
| 31 |
- develop Tiles2 compatible TilesTool
|
| 32 |
|
| 33 |
VelocityStruts:
|
| 34 |
- add a library of velocimacros for use with struts tools
|
| 35 |
(ideally these would be roughly parallel to struts tags to ease transition)
|
| 36 |
- move dynamic javascript generation from java (ValidatorTool) to templates
|
| 37 |
(this would probably work in concert with the velocimacro libraries)
|
| 38 |
|
| 39 |
|
| 40 |
Example Ideas:
|
| 41 |
- a FooShop-type demo app (i.e. something closer to real-world use)
|
| 42 |
|
Parent Directory
| 
Revision Log