Hi,
I did if for a client with an extra skinning property something like:
af|table {
-tr-show-detail-column:false;
}
I'm not 100% happy with my code, so I didn't hurry to commit it.
But I might do it, if other people want it and like it.
Regards,
On Wed, Apr 9, 2008 at 9:28 AM, Henk Vanhoe <[EMAIL PROTECTED]> wrote:
> Hi,
>
> I suppose it would not be particularly difficult to add an extra attribute
> to the trinidad table, something like a "detailsLinkEnabled" attribute with
> which it would be possible to show/hide the extra "Details"-column. That
> would be handy when the detailstamp should always be shown or when you want
> to show/hide the detailstamp with pure client-side javascript (which is
> faster than PPR with small pages and with which you can avoid some extra
> complexities related with PPR). But of course, if there is another way to do
> that, I would prefer not to add an extra attribute...
>
> Regards,
> Henk
>
>
> Henk Vanhoe wrote:
>
> > Hi,
> >
> > Another question I was having...
> >
> > In one of our tables we are using the detailStamp facet. When I add a
> > detailStamp there automatically appears an extra column with a
> > "Details"-link in it. Does anybody know a way to disable this column? (The
> > details should always be visible in the screen we are building.) I noticed
> > there is an "allDetailsEnabled" attribute where I could disable/enable the
> > show/hide all links, but I don't find a similar attribute for the regular
> > show/hide links...
> >
> > Thanks,
> > Henk
> >
> >
> >
>
>
--
Cristi Toth
-------------
Codebeat
www.codebeat.ro
