Hi Dave, src/site/xdoc/skin-selectors.xml from Trinidad project root (not trinidad-api nor trinidad-impl).
Regards, ~ Simon On Nov 26, 2007 2:15 PM, Dave Brunette <[EMAIL PROTECTED]> wrote: > > What I was asking was if it's appropriate to use it. It seems right > to me, but I just wanted to make sure I wasn't stepping on somebody else's > property. I'll move on with using it until I hear otherwise. > > No doubt, it's important to keep the the documentation updated. Any > tips on where I can go to patch/update the Skin Selectors Doc? > > ------------------------------ > Date: Mon, 26 Nov 2007 13:54:10 -0500 > From: [EMAIL PROTECTED] > > To: [email protected] > Subject: Re: [Trinidad] Enhancement to hide Select All/Select None on > table? > > If it's appropriate, then use it, otherwise remove it. Whatever you > decide, the skin property will need to be added to the skinning reference > doc. > > Thanks, > > D. > > On Nov 26, 2007 12:48 PM, Dave Brunette < [EMAIL PROTECTED]> wrote: > > > Thanks Simon. I had found the breadcrumb renderer and it was a good > example of how to use this. Cool stuff. > > While looking around, I came across a skin property that already > existed called SkinProperties.AF_TABLE_SELECTION_BAR_IN_TABLE... but it > didn't seem to be used by anything. Does anybody know anything about this > property? Should I just implement a usage of this already existing > property, or should I leave this alone and create a new property altogether? > > Dave > > ------------------------------ > Date: Mon, 26 Nov 2007 12:27:46 -0500 > > From: [EMAIL PROTECTED] > To: [email protected] > Subject: Re: [Trinidad] Enhancement to hide Select All/Select None on > table? > > You can check train or breadcrumb renderers for usage examples. The former > use an integer property to determine how many visible station at a time it > should render while the latter use a boolean property to determine if the > current location should be rendered or not. > > > Regards, > > ~ Simon > > On Nov 26, 2007 12:08 PM, Dave Brunette <[EMAIL PROTECTED]> wrote: > > > Oh... I didn't know the skin could prevent rendering. OK, that would > seem fine to me. I'll have to read up on that stuff, but I can re-work the > patch and submit a new one using a skinning property instead. > > ------------------------------ > Date: Mon, 26 Nov 2007 11:58:50 -0500 > From: [EMAIL PROTECTED] > > To: [email protected] > Subject: Re: [Trinidad] Enhancement to hide Select All/Select None on > table? > > Skinning property would prevent rendering as well, we're not talking about > using visibility: hidden here, but rather having something like > -tr-showSelectAllLink: false set on af|table selector. > > > Regards, > > ~ Simon > > On Nov 26, 2007 11:41 AM, Dave Brunette <[EMAIL PROTECTED]> wrote: > > > Yeah, I had thought about just letting the skin take care of it > too... but I figured, why render it if we know we don't want it? Sure, it > could be rendered and then hidden, but if we know we don't want it, then > that would just be one less thing to render on the page. > > > Date: Mon, 26 Nov 2007 17:12:52 +0100 > > From: [EMAIL PROTECTED] > > To: [email protected] > > Subject: Re: [Trinidad] Enhancement to hide Select All/Select None on > table? > > > > > Thanks for filing https://issues.apache.org/jira/browse/TRINIDAD-840 > > and providing a patch. > > > > Simon had a valid point, that this could be handled via skin property as > well. > > > > -M > > > > On Nov 21, 2007 7:29 PM, Dave Brunette < [EMAIL PROTECTED]> wrote: > > > > > > > > > Hi all. > > > > > > I have heard coworkers and seen forum posts asking how to hide the > Select > > > All/Select None links on a tr:table component... but to this point I > haven't > > > heard/seen any solution. So I'd like to propose a new attribute on the > > > tr:table component to take care of this: <tr:table > showAllVisible='false' > > > />. The showAllVisible attribute would only have an effect if > > > rowSelection='multiple'. If set to false, it would make > > > TableRenderingContext.hasSelectAll() return false so these controls > are not > > > rendered. > > > > > > Does anybody see a problem with this? If not, I'll log something in > JIRA > > > and move on a patch. > > > > > > Dave > > > > > > ________________________________ > > > Share life as it happens with the new Windows Live. Share now! > > > > > > > > -- > > Matthias Wessendorf > > > > further stuff: > > blog: http://matthiaswessendorf.wordpress.com/ > > sessions: http://www.slideshare.net/mwessendorf > > mail: matzew-at-apache-dot-org > > ------------------------------ > Connect and share in new ways with Windows Live. Connect > now!<http://www.windowslive.com/connect.html?ocid=TXT_TAGLM_Wave2_newways_112007> > > > > ------------------------------ > You keep typing, we keep giving. Download Messenger and join the i'm > Initiative now. Join > in!<http://im.live.com/messenger/im/home/?source=CRM_WL_joinnow> > > > > ------------------------------ > Share life as it happens with the new Windows Live. Share > now!<http://www.windowslive.com/share.html?ocid=TXT_TAGLM_Wave2_sharelife_112007> > > > > > -- > Chordiant Software Inc. > www.chordiant.com > > > ------------------------------ > Your smile counts. The more smiles you share, the more we donate. Join > in!<http://www.windowslive.com/smile?ocid=TXT_TAGLM_Wave2_oprsmilewlhmtagline> >
