|
From: Jason C. <jas...@no...> - 2002-04-05 14:10:12
|
> -----Original Message----- > From: Matt Baldree [mailto:ma...@sm...]=20 > Enhancements > 1. More velocity macros, etc. > 2. WML tags > 3. XHTML tags (possible move our existing tags to be XHTML compliant) > 4. VXML tags > 5. Ability to chain actions > 6. XSLT should be enhanced slightly to be really useful. We=20 > need some XSLT > java extension for URL-escaping and so on. > 7. Ability to receive multi-part content - AttachmentAware? 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. |
|
From: Heng S. L. <low...@ya...> - 2002-04-06 03:21:01
|
1. Management console - some configuration tool would be nice. 2. Tool integration - DreamWeaver integration for the ui tag. 3. Debugging tool - A value stack inspection tool would be usefull. 4. SWT client ? 5. Security model/framework ? 6. Action repository api - I think it might be usefull to abstract out the storage of action definition and its associated view mapping, possibly allowing runtime configuration/customization. 7. Support for the forth coming portlet api ? 8. Multi-channel view mapping ? - For e.g, define different view for the same action base on the output channel type ( xml, wml, html, etc ) 9. More real world example/usage pattern - eCommerce - portal Regards, Low __________________________________________________ Do You Yahoo!? Yahoo! Tax Center - online filing with TurboTax http://taxes.yahoo.com/ |
|
From: Rickard <ri...@dr...> - 2002-04-06 09:59:52
|
Heng Sin Low wrote: > 1. Management console > - some configuration tool would be nice. > 2. Tool integration > - DreamWeaver integration for the ui tag. > 3. Debugging tool > - A value stack inspection tool would be usefull. You can get that today by using the XSLT view "showtree.xslt". > 4. SWT client ? > 5. Security model/framework ? Yes, this needs to be thought about more. > 6. Action repository api > - I think it might be usefull to abstract out the > storage of action definition and its associated view > mapping, possibly allowing runtime > configuration/customization. Can you expand on this? > 7. Support for the forth coming portlet api ? Absolutely!! > 8. Multi-channel view mapping ? > - For e.g, define different view for the same action > base on the output channel type ( xml, wml, html, etc > ) This can be done by using different action mappings. > 9. More real world example/usage pattern > - eCommerce > - portal Portal stuff is in the planning stage. /Rickard -- Rickard Öberg |
|
From: Matt B. <ma...@sm...> - 2002-04-06 12:25:28
|
makes sense to me. ----- Original Message ----- From: "Peter Kelley" <yel...@ya...> To: <web...@li...> Sent: Friday, April 05, 2002 11:52 PM Subject: [Webwork-user] DRAFT 3 - next release features/requirements > Has anybody ever seen the IBM Redbook documentation ? They are a > practical guide to a software or hardware product. They usually have > stuff like "We tried to do this and this happened" or "We figured out > how to use this product feature and here is the sample code". I think > it would be really cool to have that sort of practical documentation > for WebWork. The reference documentation could then be seperate. At > the moment it's all jumbled in there together. > > I'd even be prepared to help out once I know a little bit more about the > product, I helped write 2 Redbooks when I was at IBM. > > Good idea ? Bad Idea ? Thoughts ? > > > > 3rd draft of possible next release feature/requirements based on what people > > have posted. Right now these are candidate ideas. Once we have a good list, > > we can repost for inclusion/exclusion/prioritization, etc. > > > > Other ideas? > > > > Documentation > > 1. Better velocity documentation > > 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. > > 3. A detailed description on the single items and configuration of the > > webwork.properties should be done (based on the default.properties) > > 4. Client Action documentation > > > > Enhancements > > 1. More velocity macros, etc. > > 2. WML tags > > 3. XHTML tags (possible move our existing tags to be XHTML compliant) > > 4. VXML tags > > 5. Ability to chain actions > > 6. XSLT should be enhanced slightly to be really useful. We need some XSLT > > java extension for URL-escaping and so on. > > 7. Ability to receive multi-part content - AttachmentAware? > > > > Examples/Tests > > 1. More Swing/Client side examples > > > > Misc > > 1. Bug list > > 2. Feature list > > 3. Instrument/profile code - where is our bottlenecks? how well does WW > > scale? > > 4. Logging - overhaul debug statements to use proper logging levels - debug, > > info, etc. > > 5. Nightly builds > > > > Incorporating new view technologies > > 1. Flash > > 2. Apache Axis (SOAP) > > > > -Matt > > > > > > > > > > _______________________________________________ > > Webwork-user mailing list > > Web...@li... > > https://lists.sourceforge.net/lists/listinfo/webwork-user > > > -- > Peter Kelley > > > _______________________________________________ > Webwork-user mailing list > Web...@li... > https://lists.sourceforge.net/lists/listinfo/webwork-user > > |
|
From: Jay B. <dig...@ya...> - 2002-04-06 04:07:45
|
> Examples/Tests > 1. More Swing/Client side examples > > Misc > 1. Bug list > 2. Feature list > 3. Instrument/profile code - where is our bottlenecks? how well does WW > scale? > 4. Logging - overhaul debug statements to use proper logging levels - debug, > info, etc. > 5. Nightly builds I'd like to help here... Let me know how. ===== Respectfully, Jay Bose __________________________________________________ Do You Yahoo!? Yahoo! Tax Center - online filing with TurboTax http://taxes.yahoo.com/ |
|
From: Rickard <ri...@dr...> - 2002-04-05 14:18:18
|
Jason Carreira wrote: > 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. Yes, this should be added somehow. /Rickard -- Rickard Öberg |
