t: is absolutely critical only for two things: id, and type.
t:id or t:type clearly identify a particular tag as a reference to a
component, either an explicit one (t:id) or implicit (t:type).
Without one of those two things (or both), having, eg, t:page="Index"
is meaningless.
Beyond those two attributes, nothing has to be prefixed with t:, and
is a matter of personal preference. Personally, I try to move as much
as I can out of the template, although I frequently leave informal,
html-attribute parameters in the template.
Robert
On Jul 21, 2008, at 7/219:01 AM , Thiago H. de Paula Figueiredo wrote:
Em Mon, 21 Jul 2008 06:00:33 -0300, <[EMAIL PROTECTED]> escreveu:
Can someone please explain why "t:" is required for parameters and,
if that is the case, why is it missing in examples in the Tutorial?
AFAIK, t: exists to clearly differentiate what is a component
parameter from what is an HTML attribute. It does more difference
when using invisible instrumentation:
<a t:type="PageLink" t:page="Index" class="mainlink">Index page</a>
page is a PageLink parameter, so I always put t: on it. On the other
hand, class is not a PageLink parameter, it is an attribute of the a
tag, so it never gets a t: prefix.
Thiago
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
