of the if component page. D'oh.
> -Original Message-
> From: Filip S. Adamsen [mailto:[EMAIL PROTECTED]
> Sent: 23 September 2008 21:19
> To: Tapestry users
> Subject: Re: Overriding a render phase method
>
> Well... You could try this:
>
>
> ;
r require a custom component. Maybe I'm missing some
easy solution to this problem or something?
-Original Message-
From: Filip S. Adamsen [mailto:[EMAIL PROTECTED]
Sent: 23 September 2008 20:34
To: Tapestry users
Subject: Re: Overriding a render phase method
Hi Andy,
I totally agre
-
> From: Filip S. Adamsen [mailto:[EMAIL PROTECTED]
> Sent: 23 September 2008 20:34
> To: Tapestry users
> Subject: Re: Overriding a render phase method
>
> Hi Andy,
>
> I totally agree on first and last parameters. As it is now, I'm using
> if-else components pretty
Hi Andy,
I totally agree on first and last parameters. As it is now, I'm using
if-else components pretty much everywhere. =/
You'd have my vote on a JIRA issue.
-Filip
On 2008-09-23 21:12, Blower, Andy wrote:
To be honest I think the standard loop component would benefit from first &
last
re set to true for first and last iterations
repectively. Anyone else agree, or is this an unusual need?
Thanks,
Andy.
> -Original Message-
> From: Jonathan Barker [mailto:[EMAIL PROTECTED]
> Sent: 23 September 2008 18:29
> To: 'Tapestry users'
> Subject: RE: Overri
rs'
> Subject: RE: Overriding a render phase method
>
> Sorry to 'bump' this, but I'd really like some guidance/opinions.
>
> > -Original Message-
> > From: Blower, Andy
> > Sent: 17 September 2008 11:30
> > To: 'Tapestry users
Sorry to 'bump' this, but I'd really like some guidance/opinions.
> -Original Message-
> From: Blower, Andy
> Sent: 17 September 2008 11:30
> To: 'Tapestry users'
> Subject: Overriding a render phase method
>
> From the T5 documentation:
>
> "When a sub-class overrides an render phase meth