Acknowledged. I've finished writing what I was going to put into the user guide, but I'll move that to a "howto" section and replace it with a short paragraph in both the "Model" and "View" sections in the user guide which will just refer to the howto section.
> -----Original Message----- > From: Ted Husted [mailto:[EMAIL PROTECTED]] > > Personally, I'm finding that the user guide format is becoming a > pain to maintain. I'd like to start moving some material out into > their own HOWTO sections, especially anything that includes a > significant amount of code. Some of the sections I was looking at > include > > 4.2.1 => how to write an DynaAtionForm > > 4.2.2 => how to write a map-backed ActionForm > > 4.6.4 > -> How to configure your web.xml > > -> How to setup the Struts taglibs > > The goals being > > * to turn the user guide back into high-level overview of the > archtechture that helps people get the big picture, > > * to make it easier to add and maintain sections that include > implementation details, and > > * to avoid "pigeonholing" articles under "model", "view", or > "controller", since many implementation strategies include > building components on either side of a fence. > > So, personally, I would suggest starting with a paragraph or two > that introduced index and mapped properties from an arcitechtural > pespective, and then link to a separate article with more details > that we could also put into the faq/howto area. (Something like > the preface, but with the links point to our own material.) > > -Ted. > > 11/24/2002 6:28:06 PM, [EMAIL PROTECTED] (David M. Karr) wrote: > > >I believe that the current user guide doesn't cover indexed > properties, mapped > >properties, or indexed tags, very well. The API docs at least > mention indexed > >tags. > > > >Over the last few days I've been writing something about these > areas that I > >hope can go into the user guide. I consider what I have to be a > reasonable > >first draft. Despite it being a draft, I think I'd like to > commit it in close > >to its present form, as I doubt I'm going to get a great deal of > useful > >feedback until it gets into the user guide. It's sort of > longish, almost 350 > >lines of 80-column text. Much of this length is from several > versions of a > >simple JSP page showing usage of this. > > > >I'd like to add this as section 3.3.6, in the "Forms and FormBean > Interactions" > >section, titled "Indexed & Mapped Properties". -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
