I'm catching up after 4 days spent moving into a new home. +1 on Nathan's proposal to keep naming shortened and Velocity-like (ex. $form.token)
--- 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 "getBean() Retrieve and return the form bean associated with this request." QUESTION: Does a Designer really need to know about 'beans'? "This is a convenience method. The form bean is automatically available in the Velocity context under the name defined in the Struts configuration." QUESTION: Why would a Designer ever use a generic $form.bean.username instead of $LoginForm.username (assuming the Struts form name is "LoginForm") "If the form bean is used repeatedly, it is recommended to create a local variable referencing the bean rather than calling getBean() multiple times." QUESTION: What is the benefit of doing this local assignment? Optimization/speed QUESTION: Should the "Tools" documentation be written for reading by Designers or Developers? 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? -Tim --- --- Nathan Bubna wrote: > I would suggest as a general rule that we go with the more elegant and > less java-like syntax everywhere possible. for example, things like: > > $form.token instead of $form.getToken() > $msg.foo instead of $msg.get('foo') > #set( $tool.foo = 'bar' ) instead of $tool.setFoo('bar') > and so on... > things are just shorter, cleaner, and prettier this way. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
