Return-Path: Delivered-To: apmail-cocoon-dev-archive@www.apache.org Received: (qmail 16975 invoked from network); 24 Oct 2003 13:55:45 -0000 Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12) by minotaur-2.apache.org with SMTP; 24 Oct 2003 13:55:45 -0000 Received: (qmail 2298 invoked by uid 500); 24 Oct 2003 13:55:36 -0000 Delivered-To: apmail-cocoon-dev-archive@cocoon.apache.org Received: (qmail 2275 invoked by uid 500); 24 Oct 2003 13:55:35 -0000 Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: dev@cocoon.apache.org Delivered-To: mailing list dev@cocoon.apache.org Received: (qmail 2261 invoked from network); 24 Oct 2003 13:55:35 -0000 Received: from unknown (HELO smtp1.jouve.fr) (193.108.166.138) by daedalus.apache.org with SMTP; 24 Oct 2003 13:55:35 -0000 From: "Laurent Trillaud" To: Subject: [RT] Portal Engine with multiple menus and multiple levels Date: Fri, 24 Oct 2003 15:55:29 +0200 Message-ID: <003e01c39a36$7c768740$c924a8c0@L138LT> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook, Build 10.0.4024 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 Importance: Normal X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N Hi cocooners First of all, thanks to Carsten and all the others contributors for this excellent portal engine with skin capabilities. But it seems that I reach the limit with menus handlers. I wanna use the portal for a big web site with the following functionalities: - a menu can have multiple level - a work area can be driven by more than one menu (i.e. horizontal, vertical, contextual) - a page can have more than one work area - a menu can have more than one render (i.e. dhtml and text) My first idea was to write a new renderer, but from the point of view of a cocoon's user isn't a piece of cake because you have to solve: - miscellaneous parameters in cocoon.xconf - database mapping for new tags in layout.xml - persistence of the selected item - and so on. But even with brand new renderers, I not sure to fill all functionalities. IMO the main restriction is the nest of XSL, driven by the composite-layout. You haven't a total freedom to organize the page as you want. Therefore the second idea is to consider menu like a regular coplet. A cocoon's user design its menus with its own pipelines and just configure new coplets - no more renderer to code, java to compile - and associate a menu item with an event id. The selected item can be store with the persistence mechanism of the coplet. The portal.xml becomes a flat list of all menu items by their event id with all composite-layout under to describe the page as usual. The main stuff to do is to associate a fixed event number to a menu item. The benefit will be to have also a bookmarkable portal. So, as a conclusion: does make sense? Laurent Trillaud