[Webwork-devel] rc - next release features

[<ma...@sm...>]

Ok, here is a final summary of potential new WW
features for the next release. I have indicated who
mentioned each feature so we can go back to them for
more information if needed.

Have I left any features out? Should any feature be
removed? What do you believe are a *must* for the next
release? Do you have any feature(s) you would like to
work on or take ownership of? If you have any revisions
or comments, please reply.

I will commit this summary as TODO.txt to the root of
CVS.=20

-Matt

- Documentation
1. Better velocity documentation. [suggested by Matt]
2. A more detailed section describing the view mapping
focusing on using actions.xml and views.properties with
an example containing all the goodies (commands,
aliases, hierarchical aspects etc.) and describing the
main differences between them. [suggested by Paolo]
3. A detailed description on the single items and
configuration of the webwork.properties should be done
(based on the default.properties) [suggested by Paolo]
4. Client Action documentation [suggested by Mike]
5. Splitting documentation into a RedBook and a
reference. [suggested by Peter]

- Core
6. Ability to chain actions [suggested by Pat]
7. XSLT should be enhanced slightly to be really
useful. We need some XSLT java extension for
URL-escaping and so on. [suggested by Billy]
8. Ability to receive multi-part content -
AttachmentAware? [suggested by Mike]
9. Ability to reuse the same action - i.e.
I've also got a SessionActionFactory that I built a
while back that will reuse the same action by saving it
and pulling it from the session, which makes things
like multi-page forms easy, because you don't have to
keep passing the data along as hidden fields, etc.
[suggested by Jason]
10. Support for Java Server Faces [suggested by Rickard]
11. Support for Java Standard Tag Library [suggested by
Rickard]
12. Support for Portlet API [suggested by Rickard]
13. Ability to have more than one servlet dispatcher
(need more info) [suggested by Rickard]
14. Revaluate the standard configuration scheme
[suggested by Rickard]
15. Management console - some configuration tool would
be nice. [suggested by Low]
16. Security model/framework [suggested by Low]
17. Include i18n in ValidationEditorSupport. [suggested
by Paolo]
18. Factor out HTTP stuff out of the dispatcher.
[suggested by Sven]

- Tags
Existing tags
19. Convert to XHTML [suggested by Matt]
20. Provide escape support. [suggested by Taavi]

Contrib tags
21. Mike offered the inclusion of Jira tags in the
library where they made sense.

New tags
22. VXML (voice XML) [suggested by Matt]
23. WML [suggested by Matt]

- Velocity
24. More velocity macros, etc. [suggested by Matt]

- Examples/Tests
25. More Swing/Client side examples [suggested by Pat]
26. SVG example [suggested by Billy]

- Misc
27. Bug fixes
28. Instrument/profile code - where is our bottlenecks?
how well does WW scale? [suggested by Matt]
29. Logging - overhaul debug statements to use proper
logging levels - debug, info, etc.[suggested by Matt]
30. Nightly builds [suggested by Matt]
31. JUnit test cases [suggested by Billy]
32. Tool integration - DreamWeaver integration for the
ui tag. [suggested by Low](Low)
33. Reloadable actions [suggested by Bill]
34. Reloadable configuration(s) [suggested by Bill]
35. Include contrib work from other people [suggested
by Fran=E7ois]

- Incorporating new view technologies
36. Flash [suggested by Rickard]
37. Apache Axis (SOAP) [suggested by Matt]
=0D