_FANTASTIC_ idea - I've always loved the IBM redbooks!

+1 from me.

-mike

On 6/4/02 3:52 PM, "Peter Kelley" ([EMAIL PROTECTED]) penned the words:

> 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
>> [EMAIL PROTECTED]
>> https://lists.sourceforge.net/lists/listinfo/webwork-user
> 


_______________________________________________
Webwork-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/webwork-user

Reply via email to