> -----Original Message----- > From: Ralph Goers [mailto:[EMAIL PROTECTED] > Sent: Wednesday, December 01, 2004 2:08 PM > To: [EMAIL PROTECTED] > Subject: Re: Portal - Event Handling > > I'm very confused. Where is your generator used? In the > pipeline that retrieves the layout portal.xml file? As I > have no idea how the original Portal framework worked I am > not sure what you are attempting to do. > > If you are attempting to dynamically create layouts you can > do that by manipulating the pipelines that generate the > various portal.xml files. > However, that only happens at the start of a session. Are > you trying to add stuff later? > > Ralph OK, this is a coplet that allows the creation and manipulation of portal layouts, which is to say a collection of coplet references which are defined in a vector (columns) of vectors(rows). At the graphical terminus of the pipeline, this ends up as a set of coplet names with various buttons (left, right, up, down and delete) next to each name name. Also included is a list of all coplet names. I recommend you run the portal-fw block if you need to see how such a mechanism works. I believe it's an admin function. The process is a fairly popular one in portals where the layout is less flexible than Cocoon Portal's (but I had to start somewhere). Although at the moment, the layout info is retrieved by the generator from a database, it's equally valid to do so from an XML source (e.g. a user-specific profiles/layout/portal.xml file). This is a layout DESIGNER, not the layout EXECUTION. It allows me to manipulate the layout database items graphically. Converting them into a layout portal.xml file (or, for that matter, dynamically generating the layout execution itself) comes later. And, unless I'm even more confused than I think I am, while the portal as a whole conforms to the Cocoon pipeline model of one beginning, one ending, the individual coplets that are embedded in the portal are each themselves pipeline constructs which get merged into the main portal flow. Since my layout designer is a coplet, it, too needs a generator, and since my data source is currently idiosyncratic, that mean a custom generator. However, as I'd mentioned earlier, the idea of a generator that is simultaneously a mutator doesn't strike me as the cleanest or safest solution. Tim > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > This e-mail and any files transmitted with it are confidential and are intended solely for the use of the individual or entity to whom it is addressed. If you are not the intended recipient or the person responsible for delivering the e-mail to the intended recipient, be advised that you have received this e-mail in error, and that any use, dissemination, forwarding, printing, or copying of this e-mail is strictly prohibited. If you received this e-mail in error, please return the e-mail to the sender and delete it from your computer. Although our company attempts to sweep e-mail and attachments for viruses, it does not guarantee that either are virus-free and accepts no liability for any damage sustained as a result of viruses. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
