Gabe said: ... > BTW, I want to mention that I really like the diagram on the > overview page of the VelocityStruts documentation. Great job!
+1 :) ... > > QUESTION: Should the "Tools" documentation be written for reading by > > Designers or Developers? > > Designers! Do you see many things that are more aimed at developers? > I hope not. :-) > > > QUESTION: Similar to Velocity Main which has separate User and Developer > > Guides, perhaps we should have a Guide that is devoted to the Struts > > Designer who is now in VelocityStruts land? > > Which would be things that are only relevant for the developers? Download > and installation? All the rest is pretty much aiming the designers. For developers, i think the primary issue is probably creating their own tools and dealing with the toolbox (yes, designers might do the latter to some extent). so some other suggestions might be... perhaps a brief section on tool scoping, the ViewTool interface (esp. what's passed to init() based on scope). the <create-session> element in the toolbox definition might deserve mention. there could be mention of the ChainedContext's search order (and even taking advantage of that to wrap and/or hide the request/response/session/servletContext objects from designers). obviously, nothing here so urgent or important to document that it would hold up doing a release, but i think some sort of developer's guide could be useful. and there are other things i can imagine going in there someday as this project grows and evolves. Nathan Bubna [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
