Hi Laurent, Yes, it does make sense, however if I make it a bit more complex, it's becoming difficult to manage.
Let's say my "News Story" page has the following coplets: - News Story - Related News Stories (if any) - Related Photos (if any) - List of other sites talking about the topic (if any) - Auctions on eBay selling items related to this story ;-)... I think you know what I'm getting at :) Technically each portlet is capable of rendering itself give the story-id. The only thing out of its contol is the window. -Alex --- Laurent Trillaud <[EMAIL PROTECTED]> wrote: > Alex > For me it's straight forward, unless I miss > something. You haven't even need > of visibility feature, just page switching. > Your portal has 3 pages: > 1. a page with 1 coplet with the list of all the > stories > 2. a page with 1 coplet with the story selected > 3. a page with 2 coplets with the story selected and > the related story. > When you process the list of all stories, you can > build a link with events > depends of the story. > For a story without related, generate: > - an event to switch to page 2 > - an event to put the story id in coplet 1 > For a story with related, generate: > - an event to switch to page 3 > - an event to put the story id in coplet 1 > - an event to put the related story id in coplet 2 > The pipeline associated to the display of stories, > just get the story id > from his coplet attributes. > Does make sense for you? > Laurent > > > Hi Laurent, > > > > There are two scenarios I can think of: > > - I have a page with a "list of news stories" > portlet > > and when I click on the story, another portlet > shows > > up with the story itself on the same page. I > think > > you approach will work here. > > - I have "news story" portlet and "related news" > > portlet on the same page. If there are any > related > > news, then show the portlet, if not, the header > should > > not be displayed. I think this is the one the > portal > > might not be able to handle. The only thing I can > > think of is running a "cleanup" stylesheet, which > > removes empty headers, but that's a bit of a hack > :-) > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: > [EMAIL PROTECTED] > For additional commands, e-mail: > [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
