Probably not adding anything useful to the conversation, but is the
intention that this is just an example of how to use nested parameter
block controls? If so, cool!
If it is an example of the "real" If component (I can't imagine it is,
but who knows) then I'd be very concerned about the example. Not from
the component writing ease of use standpoint, but more from the
template writing point of view / readability.
On 1/12/07, Howard Lewis Ship <[EMAIL PROTECTED]> wrote:
A new concept in Tapestry: parameters in the templates for a content
range. Example:
<t:comp type='If" test="loggedIn">
Welcome to the show, ${userName}!
<t:parameter name="else">
Click <a t:type="ActionLink" t:id="login">here</a> to log in.
</t:parameter>
</t:comp>
--
Jesse Kuhnert
Tapestry/Dojo team member/developer
Open source based consulting work centered around
dojo/tapestry/tacos/hivemind. http://blog.opencomponentry.com
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
