I think the issue is for someone relatively new to T5, they don't know/understand why <input t:type="textfield.../> and <t:textfield.../> are equivalent, but <div t:type="remove> fails. To them it just seems buggy and/or inconsistent. The basic mechanisms look the same, but they don't act the same. That causes confusion.
mrg On Wed, Mar 10, 2010 at 1:00 PM, Howard Lewis Ship <hls...@gmail.com> wrote: > Ok, the deal is that t:type is used to identify the actual component > type (the type name is resolved to a component class name). T5 > already has some magic elements, a.k.a. directives, such as t:body, > t:parameter, t:block, t:content and t:remove. I don't want to > introduce magic component types as well. > > The fact that you can do <t:textfield> rather than <input > t:type="textfield"> came later, and is an ease of use optimization. I > think it makes the templates look nice, it mimics a common approach > used in T4 and it's very concise. > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
