File: STATUS

package info (click to toggle)
velocity-tools 2.0-2
  • links: PTS, VCS
  • area: main
  • in suites: wheezy
  • size: 3,864 kB
  • sloc: java: 24,410; xml: 7,944; jsp: 459; makefile: 20
file content (42 lines) | stat: -rw-r--r-- 1,416 bytes parent folder | download | duplicates (6)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
S T A T U S
===========
$Id: STATUS 672102 2008-06-27 03:08:02Z nbubna $


Known Issues/Bugs:
    - see http://issues.apache.org/jira/browse/VELTOOLS


Documentation Wishlist:
   - Complete user guide.
   - Improve documention of the view tools (either xml/dvsl or javadoc)
   - Create a developer's guide (how to write tools, tips on extending VVS, etc.)


Proposed Features/Upgrades:
    General:
        - finish/fix/improve Maven2 build support
        - add more automated testing of tools
        
    Generic tools:
        - TableTool (VELTOOLS-102)
        - Template debugging tool(s)/support
        - Add support for ValueParser to use a properties file as a source

    VelocityView:
        - Tool pooling/cleanup support (use commons-pool probably)
        - look into supporting arbitrary layout depth (sort of a "tiles lite")
          for the VelocityLayoutServlet (cf. Niall's work with Simple)
        - support for JSP tags
        - develop Tiles2 compatible TilesTool

    VelocityStruts:
        - add a library of velocimacros for use with struts tools
          (ideally these would be roughly parallel to struts tags to ease transition)
        - move dynamic javascript generation from java (ValidatorTool) to templates
          (this would probably work in concert with the velocimacro libraries)


Example Ideas:
   - a FooShop-type demo app (i.e. something closer to real-world use)