On 2/12/07, Musachy Barroso <[EMAIL PROTECTED]> wrote:
I think the idea is just to organize the info in a way that a user new
to struts 2 can understand. From my personal experience, when I started
with S2, I couldn't make sense out of the wiki, I had to read WW in
Action, and after that, the wiki was just great!
In the beginning, I had to dissect the MailReader to figure it out,
which lead to the MailReader Tour.
Again, a slonger tutorial that included the CRUD stuff would help
orientate people so that they have a "framework of reference" for the
rest of framework reference :)
What might be helpful would be to break it down into guides that
follow the natural flow of the framework. So, within the Core Guide,
we might have Architecture, Configuration, Validation, Interceptors,
Results, and Actions.
Core Guide
* Architecture
o AJAX
o ObjectFactory
o Dependency Injection
+ Spring
+ Plexus
o Profiling
o Debugging
* Configuration
o Annotations
o Zero Configuration
o Struts Configuration Elements
o Action Mapper & Action Mapping
o ActionMapper
o Wildcard Mappings
o Configuration Provider & Configuration
o Configuration Files
+ web.xml
+ struts.xml
+ struts.properties
+ struts-default.xml
+ velocity.properties
+ struts-default.vm
o Application Servers
* Validation
o Type Conversion
o Localization
* Interceptors
o Interceptor Types
* Actions
o Action Proxy & ActionProxy Factory
o Action Chaining
* Results
o Result Types
o DispatcherListener
o PreResultListener
That's everything we have now as top-level links, except for the
plugin registry and portlet stuff, which should go under plugins.
The key might be to have a decent overview in the Architecture
section. Jason's presentation would be a good starting point for that.
*
http://opensource.atlassian.com/confluence/oss/download/attachments/829/webwork.pdf
Good point. We could definitely consider that, because I think it would
be good enough, to get the bootstrap edited and beefed up. The other
problem would be duplicated documentation which would be hard to
maintain.
Yes. There *must not* be duplicated content, unless it is the form of
a tutorial or FAQ meant to point to the rest of the documentation.
Even then, we should try to cross-reference bits, so that the guide
entries point to the FAQs and tutorial sections. Then, when we update
a page in the guide, it will be easier to check to see if the tutorial
and FAQs are current.
Besides, there's got to be a couple of S2 books on the make. Phil?
> But, we all have to scratch our own itches, and if a book-style user
> guide is your itch, more power to you :)
Well, I don't like writing at all, but I worry about the newbies :) .
musachy
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
