I think there's a good argument for making the components as malleable
as possible - much more so than the other framework APIs. The exposure
to upgrade breakages is probably a necessary trade-off. E.g. for the full
utility of mixins to be realized:
https://issues.apache.org/jira/browse/TAPESTRY-1
Alternately, you could subclass GridRows to provide the hooks for what you
need, then subclass Grid to make use of your custom GridRows.
The components in Tapestry are not meant to be sacrosanct, just useful.
Though that does bring up the question of component compatibility between
releases. Hmp
Having now had the chance to tidy up my example code, here's my MixIn code
for the Grid Component:
@MixinAfter
public class ActionRows {
public static final String event = "rowAction";
@Parameter(value="click", defaultPrefix="literal")
private String action;
@
To achieve this effect, I've defined a mixin class that, after the component
has rendered, finds each row in the rendered element and then adds in an
attribute analogous to your example below.
Its far from glamourous (and certainly not as robust as one would like), but
it does the trick.
Jean-P
blah blah blah
> -Original Message-
> From: news [mailto:[EMAIL PROTECTED] On Behalf Of sun58224
> Sent: Wednesday, September 26, 2007 2:17 AM
> To: users@tapestry.apache.org
> Subject: Re: [T5] Linkable rows with Grid component
>
>
Howard Lewis Ship gmail.com> writes:
>
> You just leverage the ability to override how particular columns are
rendered:
>
> This assumes that your items have a property named label that you want
> to convert into a link.
>
>
>
> ${item.label}
>
>
>
> On 9/25/07, Jean-Philippe
You just leverage the ability to override how particular columns are rendered:
This assumes that your items have a property named label that you want
to convert into a link.
${item.label}
On 9/25/07, Jean-Philippe Steinmetz <[EMAIL PROTECTED]> wrote:
> I would like to make each of
