On Sat, 13 Mar 2010 12:20:52 -0300, Pierce T. Wetter III
<pie...@paceap.com> wrote:
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.
Agreed, but does it seem unreasonable to have the directives work with
invisible instrumentation as well? Even if it had to be
t:directive="remove"?
I really like this idea. :) Please file a JIRA asking for it.
I'm willing to do the work to make that happen if someone gives me a
hint of where I should do that. Though couldn't t:type just match
against the list of directives either first or last?
I prefer the t:directive option, so t:type is only used for declaring
components. The simpler, the better.
--
Thiago H. de Paula Figueiredo
Independent Java, Apache Tapestry 5 and Hibernate consultant, developer,
and instructor
Owner, software architect and developer, Ars Machina Tecnologia da
Informação Ltda.
http://www.arsmachina.com.br
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
