On Fri, 16 Aug 2013 14:06:36 -0300, Nicolas Barrera <nbarr...@gmail.com>
wrote:
Thank you Lance and Thiago,
I was trying to avoid doing this,
<t:if t:test="decideHowToShow">
<input t:type="TextField" ... />
<p:else>
<input t:type="PasswordField" ... />
</p:else>
</t:if>
or the equivalent blocks and delegate structure.
For the love of everything sacred, please don't use the else block of If.
It's way confusing.
<t:if t:test="decideHowToShow">
<input t:type="TextField" ... />
</t:if>
<t:if t:test="!decideHowToShow">
<input t:type="PasswordField" ... />
</t:if>
But now I 've learnt that the t:type parameter uses always LITERAL prefix
and that can't be changed.
I'm sorry, but what you said is completely wrong.
As Lance said, t:type isn't a component parameter, it's a component
declaration, so talking about bindings about it makes absolutely no sense
because no binding is used there. What you've really learned today is that
you cannot declare Tapestry component instances dynamically. ;) In other
words, Tapestry templates have static structure, but dynamic behavior.
--
Thiago H. de Paula Figueiredo
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
