After six years of maintaining the Struts 1 User Guide, for what its
worth, here's some personal feedback.
* Separating the content into model, view, and controller sections is
often problematic since most workflows cross that boundary. It's hard
to discuss a routine task beginning to end.
*
It's also not clear whether the intention is to create new content or
link to the old.
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
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
On 2/12/07, Musachy Barroso [EMAIL PROTECTED] wrote:
It's also not clear whether the intention is to create new content or
link to the old.
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
Just to add my 2 cents...
I agree with Ted that the wiki is a bad place to do long cohesive
documents. Would a PDF format be a better choice?
With webwork, what most users had was Jason's/Pat's 'Webwork in
Action' in combination with the online documentation. This was a
really good
Could we merge the users guide with the bootstrap tutorial? Adding an
introduction/overview and explaining the concepts along the tutorials?
musachy
Philip Luppens wrote:
On 2/12/07, Tom Schneider [EMAIL PROTECTED] wrote:
Just to add my 2 cents...
I agree with Ted that the wiki is a bad
Copy what is successful: The Spring Framework Reference Guide. That kind
of thing is awesome and is basically a book in itself:
http://static.springframework.org/spring/docs/2.0.x/reference/index.html
I don't know what format they write it in, but they export identical
texts to both HTML and
About an hour ago I could not access http://struts.apache.org/1.3.5,
now I cannot access http://wiki.apache.org/struts/, returns 500
Internal Server Error. Is this a know issue, someone is working on
this?
Michael.
-
To
Based on this thread, and some others, I've rearranged the pages in
the Core Developers Guide to follow the natural flow of the framework.
* http://struts.apache.org/2.x/docs/guides.html
For now, I've also added markers for some missing pages that would
help fill in the gaps. For example, we
On 2/12/07, Michael Jouravlev [EMAIL PROTECTED] wrote:
About an hour ago I could not access http://struts.apache.org/1.3.5,
now I cannot access http://wiki.apache.org/struts/, returns 500
Internal Server Error. Is this a know issue, someone is working on
this?
It seems to be okay now. If
10 matches
Mail list logo