RE: [Webwork-devel] DRAFT 4 - next release features/requirements

[<fbe...@py...>]

1.
Some people have been using WW for a while and have done some independent
work.
It may be interesting to include some of this stuff in WW.
Wouldn't it be nice that a process would be in place so that people could
submit their independent work, it would be evaluated by a steering comitee
and included in WW.

2.
In a eXtreme Programming like fashion, it would interesting to split next
release into iterations and then specify target dates for each iteration.

Cheers,
___________________________
François Beauregard, b.ing.
Vice-président
Recherche et développement
Pyxis Technologies
www.pyxis-tech.com

T : (450) 681-9094, poste 102
F : (450) 681-5758
fbe...@py...

-----Original Message-----
From: web...@li...
[mailto:web...@li...]On Behalf Of Matt
Baldree
Sent: April 6, 2002 8:03 AM
To: web...@li...;
web...@li...
Subject: [Webwork-devel] DRAFT 4 - next release features/requirements


4th draft of possible next release feature/requirements based on what people
have posted. I've also listed the person that requested the
feature/requirement based on memory. Could be wrong? Looks like we have a
pretty good list. I'll wait for revisions and then I propose that my next
post be for inclusion/exclusion/prioritization.

 Documentation
1. Better velocity documentation (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. (Paolo)
3. A detailed description on the single items and configuration of the
webwork.properties should be done (based on the default.properties) (Paolo)
4. Client Action documentation (Mike)
5. Splitting documentation into a RedBook and a reference. (Peter)

 Enhancements
1. More velocity macros, etc. (Matt)
2. WML tags (Matt)
3. XHTML tags (possible move our existing tags to be XHTML compliant) (Matt)
4. VXML tags (Matt)
5. Ability to chain actions (Pat)
6. XSLT should be enhanced slightly to be really useful. We need some XSLT
java extension for URL-escaping and so on. (Billy)
7. Ability to receive multi-part content - AttachmentAware? (Mike)
8. 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. (Jason)
9. Support for Java Server Faces (Rickard)
10. Support for Java Standard Tag Library (Rickard)
11. Support for Portlet API (Rickard)
12. Ability to have more than one servlet dispatcher (need more info)
(Rickard)
13. Revaluate the standard configuration scheme (Rickard)
14. Management console - some configuration tool would be nice. (Low)
15. Security model/framework (Low)

 Examples/Tests
1. More Swing/Client side examples (Pat)

 Misc
1. Bug list
2. Feature list
3. Instrument/profile code - where is our bottlenecks? how well does WW
scale? (Matt)
4. Logging - overhaul debug statements to use proper logging levels - debug,
info, etc.(Matt)
5. Nightly builds (Matt)
6. Tool integration - DreamWeaver integration for the ui tag. (Low)

 Incorporating new view technologies
1. Flash (Rickard)
2. Apache Axis (SOAP) (Matt)

 -Matt




_______________________________________________
Webwork-devel mailing list
Web...@li...
https://lists.sourceforge.net/lists/listinfo/webwork-devel