>> QUESTION: Does a Designer really need to know about 'beans'? >does it hurt? Dunno. Potential for harm exists in everything from knives to cotton balls. <grin>
> whether using the form bean's name or using $form.bean, > the object is the same. isn't this question just > complaining about the term being used? Oh, no complaining meant. It was the first time I'd seen the nomenclature. So I'm just wondering if it's necessary, or just a shortcut that is optional. Looks like the latter in this case. But I also avoid telling my Designers about 'beans', so maybe I must admit to some lurking complaining after all. :-) > using the form bean's attribute and/or name is a little extra work. Hah ha... I can pull out an old quote, "A little extra work... For whom?" :-) >it's one more thing that needs to be sync'ed to the struts-config.xml. Hmm... lazy Developer. <grin> > it's one more thing to remember to change if you change the config. Both Developer and Designer stuff, but the Developer instigated the change. > having $form.bean available means that you always have a consistent interface. > not a big deal in this case, but i think it's nice to have handy. Hmm... Consistent from template to template maybe. It might even be arguably easier to remember, but I don't believe this is consistent with how Struts works without Velocity. And what if there are two forms on a page? (Actually...not sure that can happen.) I'm just thinking "as simple as possible"... $form.bean.username is understandable to me the Dev dude, but I wonder if that'll throw the Designer. And I wonder if it'll throw folks who are used to 'doing it the Struts + JSP' way? It might be just fine... I'm not sure I mind either way. :-) >> QUESTION: What is the benefit of doing this local assignment? >> Optimization/speed > yep. the ActionForm is not cached in the FormTool, so every > $form.bean.whatever would repeat the whole lookup process. Ok. Maybe addressable on the Developer side? I wouldn't expect Designers to understand why they should do that trick to speed things up. >> QUESTION: Should the "Tools" documentation be written for reading by >> Designers or Developers? > hmm. must think on this... what are your thoughts here? Nothing much, I always ask, "Who's my audience?" before writing stuff. When I look at the Struts Tools docs, they are nicely organized by Gabe...but they look like they might be intimidating for a Designer. My personal bias is to provide an alternative that's so freakin' simple people will start fleeing from JSP in droves. <grin> So maybe a quick and simple page for the Designers, with grittier details for Developers left in the reference docs? > so, for instance, i know only enough about JSP to > know that i don't like it. :-) lol Timo --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
