T5: Default t-error CSS style FF vs IE7

[Martijn Brinkers (List)-2]

I noticed that the error component is not correctly displayed in IE7.
The <li> is shifted to the left.

The CSS definition that comes with Tapestry 5.0.13 is

HTML>BODY DIV.t-error LI {
    margin-left: -20px;
}

this is fine for FF2 but not for IE7. IE7 requires:

HTML>BODY DIV.t-error LI {
    margin-left: 20px;
}

Is this a known problem?

Martijn Brinkers


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

[photos-4]

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 my onSubmitXXX method was not called.

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?

Also, where is there anywhere I can see what tags are defined for TML  
and what they do.

Thanks,
p.




---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

[Marcelo Lotif-2]

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
"t:page" or "page" has the same effect).

On Mon, Jul 21, 2008 at 6:00 AM,  <photos@...> wrote:

> 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 my onSubmitXXX method was not called.
>
> 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?
>
> Also, where is there anywhere I can see what tags are defined for TML and
> what they do.
>
> Thanks,
> p.
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@...
> For additional commands, e-mail: users-help@...
>
>

--
Atenciosamente,

Marcelo Lotif
Programador Java e Tapestry
FIEC - Federação das Indústrias do Estado do Ceará
(85) 3477-5910

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

[Marcelo Lotif-2]

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 <mlotifjava@...> 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
> 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
> "t:page" or "page" has the same effect).
>
> On Mon, Jul 21, 2008 at 6:00 AM,  <photos@...> wrote:
>> 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 my onSubmitXXX method was not called.
>>
>> 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?
>>
>> Also, where is there anywhere I can see what tags are defined for TML and
>> what they do.
>>
>> Thanks,
>> p.
>>
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@...
>> For additional commands, e-mail: users-help@...
>>
>>
>
>
>
> --
> Atenciosamente,
>
> Marcelo Lotif
> Programador Java e Tapestry
> FIEC - Federação das Indústrias do Estado do Ceará
> (85) 3477-5910
>

--
Atenciosamente,

Marcelo Lotif
Programador Java e Tapestry
FIEC - Federação das Indústrias do Estado do Ceará
(85) 3477-5910

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...

[Thiago H. de Paula Figueiredo]

Em Mon, 21 Jul 2008 06:00:33 -0300, <photos@...> 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: users-unsubscribe@...
For additional commands, e-mail: users-help@...

[Robert Zeigler]

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, <photos@...> 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: users-unsubscribe@...
> For additional commands, e-mail: users-help@...

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...