Alex It appears to me difficult. The portal generater have 2 stages: 1. it resolve all events, and set coplets data / attributes 2. render thee coplet based on its datas Later in the pipeline you have the cinclude to fill coplets. Here, is too late to change the aspect of a coplet. The best way is to now before if a coplet will have data or not, may be based on parameters, and set the visibility aspect with a cl:link. Laurent
> Hi Laurent, > > I think I like the second option better. One thing > I'm not sure about: how do I know if my coplet has > returned any content when I render the window? IIUTC, > when portal renders the coplet window, the actual > coplet content is not included yet (this is done later > with cinlcude transformer). Is this correct? > > Thanks, > -Alex > > --- Laurent Trillaud <[EMAIL PROTECTED]> wrote: > > Alex > > I see 2 solutions: the first one is easy to do but > > it's just an hack. The > > second is, in my opinion, a better way but I haven't > > tested it. > > I suppose that you can check if a coplet as data by > > any input module > > 1. The easy way > > The goal is to modify the > > skins/.../styles/window.xsl. Put the code inside a > > DIV with the style 'visibility' set ` show or hide > > depend of a parameters in > > the XSL got from the layout/portal.xml with the tag > > <parameter name="" > > value=""/> > > 2. The better way > > The goal is to create another aspect for a coplet > > called for exemple > > 'coplet-visibility'. You must declare it in the > > cocoon.xconf (use the > > coplet-full-screen as sample) and declare this new > > aspect in the the > > renderer window). > > Then you will be able to hide or show a coplet with > > the same way that you > > minimize or maximize a coplet. > > Good Luck ;-) > > Laurent --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
