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
I am using the new book on Tapestry 5 by Alexander Kolesnikov and I
notice that there is a subtle difference between the Tapestry web
Tutorial and what is in the book:
t:PageLink t:page=...
t:PageLink page=...
I noticed that when doing
t:form t:id=...
that the t: for id was required or
Hi,
I don't clearly understand the use of the t: prefix (anyone can
correct me if I am wrong), but I think that's a good practice to
always use it when declaring a t:type and t:id parameters, like in
a t:type=t:ActionLink t:id=link /a
For the other parameters, this is not necessary(i.e. declaring
Sorry about the action link. The correct form is:
a t:type=ActionLink t:id=link /a
:)
On Mon, Jul 21, 2008 at 9:07 AM, Marcelo Lotif [EMAIL PROTECTED] wrote:
Hi,
I don't clearly understand the use of the t: prefix (anyone can
correct me if I am wrong), but I think that's a good practice to
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
