You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@myfaces.apache.org by Henk Vanhoe <he...@kava.be> on 2008/04/07 16:06:01 UTC

[Trinidad] Disable details-link

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

Re: [Trinidad] Disable details-link

Posted by cr...@gmail.com.
that skinning-property is not currently in the code
I have it in my code, but I want to think wisely before comitting it.
I also plan to reenable/add some features (related to rendering) of
the tr:table component
But some decisions have to be made before I do that.

I could give you a custom renderer that overrides that behavior when I
have some spare time.

cheers,

On 4/11/08, Henk Vanhoe <he...@kava.be> wrote:
> Unfortunately my problem is that I don't know how I can disable the
> detail column itself without changing the trinidad source code. I
> already found out how to make my own link that hides/shows the detail
> itself (I use pure client-side javascript that simply sets the
> javascript/CSS property display to 'none' so there is no PPR/Ajax
> involved). I suppose the extra skinning property you mentioned is not
> part of the trinidad source code?
>
> Thanks,
> Henk
>
> Cristi Toth wrote:
> > after you manage to disable the detail column
> > it's really easy to have a link that does the same thing the original
> > one does
> > if you look a bit in the generated code you'll notice a pattern on the
> > onclick event:
> >
> > to show:
> > return _submitHideShow('_idJsp1',1,'show','_idJsp12','_idJsp12dd2','2')
> > '_idJsp1 - is the id of the form
> > '_idJsp12' - is the id of the table
> > '_idJsp12dd2' - is the id of the link itself (format:
> > tableId+'dd'+rowNumber)
> >
> > to hide:
> > "return _submitHideShow('_idJsp1',1,'hide','_idJsp12','_idJsp12dd2','2')"
> > only 'show' is replaced with 'hide'
> >
> > so you don't have to do it programatically
> > just use the trinidad js code ;)
> >
> > On Thu, Apr 10, 2008 at 2:37 PM, Mathias Walter
> > <mathias.walter@gmx.net <ma...@gmx.net>> wrote:
> >
> >     Henk,
> >
> >     would you open a JIRA issue, please?
> >
> >     --
> >     Kind regards,
> >     Mathias
> >
> >     > -----Original Message-----
> >     > From: Henk Vanhoe [mailto:henk.vanhoe@kava.be
> >     <ma...@kava.be>]
> >     > Sent: Thursday, April 10, 2008 1:55 PM
> >     > To: MyFaces Discussion
> >     > Subject: Re: [Trinidad] Disable details-link
> >     >
> >     >
> >     > Hi,
> >     >
> >     > It would help me a lot if  you would commit your code. But
> >     > even if you
> >     > don't want to commit it, I would be very glad if you could
> >     > post the code
> >     > here, so I could add it myself to my own copy of the trinidad source
> >     > code and recompile it...
> >     >
> >     > On the other hand, if other people are interested in this
> >     > functionality,
> >     > an extra attribute "detailsLinkEnabled" may be more flexible,
> >     because
> >     > then you could show all details by default when this
> >     > attribute is false
> >     > (with the skinning property I suppose you still need to expand all
> >     > detail rows yourself with the disclosedRowKeys attribute).
> >     >
> >     > Thanks a lot,
> >     > Henk
> >     >
> >     > Cristi Toth wrote:
> >     > > 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
> >     <henk.vanhoe@kava.be <ma...@kava.be>
> >     > > <mailto:henk.vanhoe@kava.be <ma...@kava.be>>> 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 <http://www.codebeat.ro> <http://www.codebeat.ro>
> >
> >
> >
> >
> > --
> > Cristi Toth
> >
> > -------------
> > Codebeat
> > www.codebeat.ro <http://www.codebeat.ro>
>
>


-- 
Cristi Toth

-------------
Codebeat
www.codebeat.ro

Re: [Trinidad] Disable details-link

Posted by Henk Vanhoe <he...@kava.be>.
Unfortunately my problem is that I don't know how I can disable the 
detail column itself without changing the trinidad source code. I 
already found out how to make my own link that hides/shows the detail 
itself (I use pure client-side javascript that simply sets the 
javascript/CSS property display to 'none' so there is no PPR/Ajax 
involved). I suppose the extra skinning property you mentioned is not 
part of the trinidad source code?

Thanks,
Henk

Cristi Toth wrote:
> after you manage to disable the detail column
> it's really easy to have a link that does the same thing the original 
> one does
> if you look a bit in the generated code you'll notice a pattern on the 
> onclick event:
>
> to show:
> return _submitHideShow('_idJsp1',1,'show','_idJsp12','_idJsp12dd2','2')
> '_idJsp1 - is the id of the form
> '_idJsp12' - is the id of the table
> '_idJsp12dd2' - is the id of the link itself (format: 
> tableId+'dd'+rowNumber)
>
> to hide:
> "return _submitHideShow('_idJsp1',1,'hide','_idJsp12','_idJsp12dd2','2')"
> only 'show' is replaced with 'hide'
>
> so you don't have to do it programatically
> just use the trinidad js code ;)
>
> On Thu, Apr 10, 2008 at 2:37 PM, Mathias Walter 
> <mathias.walter@gmx.net <ma...@gmx.net>> wrote:
>
>     Henk,
>
>     would you open a JIRA issue, please?
>
>     --
>     Kind regards,
>     Mathias
>
>     > -----Original Message-----
>     > From: Henk Vanhoe [mailto:henk.vanhoe@kava.be
>     <ma...@kava.be>]
>     > Sent: Thursday, April 10, 2008 1:55 PM
>     > To: MyFaces Discussion
>     > Subject: Re: [Trinidad] Disable details-link
>     >
>     >
>     > Hi,
>     >
>     > It would help me a lot if  you would commit your code. But
>     > even if you
>     > don't want to commit it, I would be very glad if you could
>     > post the code
>     > here, so I could add it myself to my own copy of the trinidad source
>     > code and recompile it...
>     >
>     > On the other hand, if other people are interested in this
>     > functionality,
>     > an extra attribute "detailsLinkEnabled" may be more flexible,
>     because
>     > then you could show all details by default when this
>     > attribute is false
>     > (with the skinning property I suppose you still need to expand all
>     > detail rows yourself with the disclosedRowKeys attribute).
>     >
>     > Thanks a lot,
>     > Henk
>     >
>     > Cristi Toth wrote:
>     > > 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
>     <henk.vanhoe@kava.be <ma...@kava.be>
>     > > <mailto:henk.vanhoe@kava.be <ma...@kava.be>>> 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 <http://www.codebeat.ro> <http://www.codebeat.ro>
>
>
>
>
> -- 
> Cristi Toth
>
> -------------
> Codebeat
> www.codebeat.ro <http://www.codebeat.ro> 


Re: [Trinidad] Disable details-link

Posted by Cristi Toth <cr...@gmail.com>.
after you manage to disable the detail column
it's really easy to have a link that does the same thing the original one
does
if you look a bit in the generated code you'll notice a pattern on the
onclick event:

to show:
return _submitHideShow('_idJsp1',1,'show','_idJsp12','_idJsp12dd2','2')
'_idJsp1 - is the id of the form
'_idJsp12' - is the id of the table
'_idJsp12dd2' - is the id of the link itself (format:
tableId+'dd'+rowNumber)

to hide:
"return _submitHideShow('_idJsp1',1,'hide','_idJsp12','_idJsp12dd2','2')"
only 'show' is replaced with 'hide'

so you don't have to do it programatically
just use the trinidad js code ;)

On Thu, Apr 10, 2008 at 2:37 PM, Mathias Walter <ma...@gmx.net>
wrote:

> Henk,
>
> would you open a JIRA issue, please?
>
> --
> Kind regards,
> Mathias
>
> > -----Original Message-----
> > From: Henk Vanhoe [mailto:henk.vanhoe@kava.be]
> > Sent: Thursday, April 10, 2008 1:55 PM
> > To: MyFaces Discussion
> > Subject: Re: [Trinidad] Disable details-link
> >
> >
> > Hi,
> >
> > It would help me a lot if  you would commit your code. But
> > even if you
> > don't want to commit it, I would be very glad if you could
> > post the code
> > here, so I could add it myself to my own copy of the trinidad source
> > code and recompile it...
> >
> > On the other hand, if other people are interested in this
> > functionality,
> > an extra attribute "detailsLinkEnabled" may be more flexible, because
> > then you could show all details by default when this
> > attribute is false
> > (with the skinning property I suppose you still need to expand all
> > detail rows yourself with the disclosedRowKeys attribute).
> >
> > Thanks a lot,
> > Henk
> >
> > Cristi Toth wrote:
> > > 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 <henk.vanhoe@kava.be
> > > <ma...@kava.be>> 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 <http://www.codebeat.ro>
>
>


-- 
Cristi Toth

-------------
Codebeat
www.codebeat.ro

RE: [Trinidad] Disable details-link

Posted by Mathias Walter <ma...@gmx.net>.
Hi,

I'm also very interested in such an attribute.
In my case, I have an inline editable table with an extra 'action' column
(the right most column) which contains links (visibility depends on the
action itself) for editing, deleting, canceling and updating of rows.
It would be great to disable the details column. Than I can add a further
link into the action column to show the details programmatically.

--
Kind regards,
Mathias

> -----Original Message-----
> From: Henk Vanhoe [mailto:henk.vanhoe@kava.be] 
> Sent: Thursday, April 10, 2008 1:55 PM
> To: MyFaces Discussion
> Subject: Re: [Trinidad] Disable details-link
> 
> 
> Hi,
> 
> It would help me a lot if  you would commit your code. But 
> even if you 
> don't want to commit it, I would be very glad if you could 
> post the code 
> here, so I could add it myself to my own copy of the trinidad source 
> code and recompile it...
> 
> On the other hand, if other people are interested in this 
> functionality, 
> an extra attribute "detailsLinkEnabled" may be more flexible, because 
> then you could show all details by default when this 
> attribute is false 
> (with the skinning property I suppose you still need to expand all 
> detail rows yourself with the disclosedRowKeys attribute).
> 
> Thanks a lot,
> Henk
> 
> Cristi Toth wrote:
> > 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 <henk.vanhoe@kava.be 
> > <ma...@kava.be>> 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 <http://www.codebeat.ro> 


RE: [Trinidad] Disable details-link

Posted by Mathias Walter <ma...@gmx.net>.
Henk,

would you open a JIRA issue, please?

--
Kind regards,
Mathias

> -----Original Message-----
> From: Henk Vanhoe [mailto:henk.vanhoe@kava.be] 
> Sent: Thursday, April 10, 2008 1:55 PM
> To: MyFaces Discussion
> Subject: Re: [Trinidad] Disable details-link
> 
> 
> Hi,
> 
> It would help me a lot if  you would commit your code. But 
> even if you 
> don't want to commit it, I would be very glad if you could 
> post the code 
> here, so I could add it myself to my own copy of the trinidad source 
> code and recompile it...
> 
> On the other hand, if other people are interested in this 
> functionality, 
> an extra attribute "detailsLinkEnabled" may be more flexible, because 
> then you could show all details by default when this 
> attribute is false 
> (with the skinning property I suppose you still need to expand all 
> detail rows yourself with the disclosedRowKeys attribute).
> 
> Thanks a lot,
> Henk
> 
> Cristi Toth wrote:
> > 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 <henk.vanhoe@kava.be 
> > <ma...@kava.be>> 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 <http://www.codebeat.ro> 


Re: [Trinidad] Disable details-link

Posted by Henk Vanhoe <he...@kava.be>.
Hi,

It would help me a lot if  you would commit your code. But even if you 
don't want to commit it, I would be very glad if you could post the code 
here, so I could add it myself to my own copy of the trinidad source 
code and recompile it...

On the other hand, if other people are interested in this functionality, 
an extra attribute "detailsLinkEnabled" may be more flexible, because 
then you could show all details by default when this attribute is false 
(with the skinning property I suppose you still need to expand all 
detail rows yourself with the disclosedRowKeys attribute).

Thanks a lot,
Henk

Cristi Toth wrote:
> 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 <henk.vanhoe@kava.be 
> <ma...@kava.be>> 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 <http://www.codebeat.ro> 


Re: [Trinidad] Disable details-link

Posted by Cristi Toth <cr...@gmail.com>.
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 <he...@kava.be> 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

Re: [Trinidad] Disable details-link

Posted by Henk Vanhoe <he...@kava.be>.
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
>
>