[Webwork-devel] RE: [Webwork-user] feature prioritization?

[Jason C. <jas...@no...>]

I think 6, action chaining, is the most important thing on this list. =
(MHO)

> -----Original Message-----
> From: Matt Baldree [mailto:ma...@sm...]
> Sent: Sunday, April 28, 2002 11:35 PM
> To: Webwork-Developer; Webwork-User
> Subject: [Webwork-user] feature prioritization?
>=20
>=20
> I wanted to throw out a feature prioritization strawman and=20
> see what people
> thought. I did not list the Java Spec API support like Java=20
> Server Faces and
> others since these are not released at this time. Here is=20
> what I believe are
> priorities. This list doesn't mean other items cannot be=20
> worked on before
> these but rather serves as a temperature gauge to see what=20
> people would like
> released for 1.1.
>=20
> [Priority]
> 20
> 8
> 29
> 9
> 6
> 19
> 28
>=20
> -Matt
>=20
>=20
> [From TODO.txt]
> - Documentation
> 1. Better velocity documentation. [suggested by Matt]
> 2. A more detailed section describing the view mapping=20
> focusing on using
> actions.xml and views.properties with an example containing=20
> 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.=20
> [suggested by
> Peter]
>=20
> - Core
> 6. Ability to chain actions [suggested by Pat]
> 7. XSLT should be enhanced slightly to be really useful. We=20
> need some XSLT
> java extension for URL-escaping and so on. [suggested by Billy]
> 8. Ability to receive multi-part content - AttachmentAware?=20
> [suggested by
> Mike]
> 9. Ability to reuse the same action - i.e.
> I've also got a SessionActionFactory that I built a while=20
> back that will
> reuse the same action by saving it and pulling it from the=20
> session, which
> makes things like multi-page forms easy, because you don't=20
> 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=20
> nice. [suggested
> by Low]
>    15.1 Consider implementing this as an Eclipse plugin
> 16. Security model/framework [suggested by Low]
> 17. Include i18n in ValidationEditorSupport. [suggested by Paolo]
> 18. Factor out HTTP stuff out of the=20
> ActionFactory/ActionContext. [suggested
> by Sven]
>=20
> - Tags
> Existing tags
> 19. Convert to XHTML [suggested by Matt]
> 20. Provide escape support. [suggested by Taavi]
>=20
> Contrib tags
> 21. Mike offered the inclusion of Jira tags in the library=20
> where they made
> sense.
>=20
> New tags
> 22. VXML (voice XML) [suggested by Matt]
> 23. WML [suggested by Matt]
>=20
> - Velocity
> 24. More velocity macros, etc. [suggested by Matt]
>=20
> - Examples/Tests
> 25. More Swing/Client side examples [suggested by Pat]
> 26. SVG example [suggested by Billy]
>=20
> - Misc
> 27. (done - mostly) Bug fixes
> 28. Instrument/profile code - where is our bottlenecks? how=20
> well does WW
> scale? [suggested by Matt]
>    28.1. Are there any memory leaks from the value stack? Do=20
> the objects in
> the stack get reclaimed properly?
> 29. Logging - overhaul debug statements to use proper logging levels -
> debug, info, etc.[suggested by Matt]
>    29.1. Investigate using Jakarta commons-logging (allows=20
> transparent use
> of a logger both
>    log4j and jdk1.4 logger
> 30. Nightly builds [suggested by Matt]
> 31. JUnit test cases [suggested by Billy]
>    31.1 Need unit tests for BeanUtil and ValueStack (should=20
> test for all
> expression scenarios)
> 32. Tool integration - DreamWeaver integration for the ui=20
> 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]
>=20
> - Incorporating new view technologies
> 36. Flash [suggested by Rickard]
> 37. Apache Axis (SOAP) [suggested by Matt]
>=20
>=20
>=20
>=20
> _______________________________________________
> Webwork-user mailing list
> Web...@li...
> https://lists.sourceforge.net/lists/listinfo/webwork-user
>=20