Tim Colson wrote: > I'm catching up after 4 days spent moving into a new home. >
Cool! Put all the boxes away? :-) BTW, I want to mention that I really like the diagram on the overview page of the VelocityStruts documentation. Great job! > +1 on Nathan's proposal to keep naming shortened and Velocity-like (ex. > $form.token) -0 on Nathan's proposal. I don't want to stop you from simplyfing this but here is the reason I chose to mention the formal and the informal syntax in the docs: The formal and the informal syntax are not equally powerful. There are cases where the informal syntax doesn't work, for example if you need to pass two or more parameters to a method, etc. This is not an exotic case but quite a common thing. My opinion is that a designer will need to know how Velocity maps variables to method names in Java. On the velocity-user list, the mapping of Velocity variables to Java methods is quite frequently a topic that creates questions. Showing both notations in the docs makes users familiar with them. We could do this: Instead of showing both notations in most examples, we could just mention this in one place, for example in an additional section in the user guide. But, I strongly feel that designers need to be made aware of the two notations. Formal vs. information syntax is something that always leads to difficulties for new users. Unfortunately you don't get by with the informal notation only. > --- > On the topic of simple and clean naming - I do not understand why > form.getBean() exists. > > http://crufty.happysearch.com/velocity/tools/struts/docs/FormTool.html Yes, I don't see are reason either and I don't remember why I originally added it. But, I just noticed, that nowwhere else the form bean is mentioned. I suggest that the form bean is mentioned in the section "Access to Struts Framework Resources" of the users guide. > 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. I actually think that the tool reference pages are pretty cool. http://crufty.happysearch.com/velocity/tools/struts/docs/FormTool.html But I am always open for improvements. Gabe --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
