Return-Path: Delivered-To: apmail-jakarta-jetspeed-dev-archive@www.apache.org Received: (qmail 91029 invoked from network); 19 Jun 2004 13:45:29 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur-2.apache.org with SMTP; 19 Jun 2004 13:45:29 -0000 Received: (qmail 31615 invoked by uid 500); 19 Jun 2004 13:45:26 -0000 Delivered-To: apmail-jakarta-jetspeed-dev-archive@jakarta.apache.org Received: (qmail 31579 invoked by uid 500); 19 Jun 2004 13:45:25 -0000 Mailing-List: contact jetspeed-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Jetspeed Developers List" Reply-To: "Jetspeed Developers List" Delivered-To: mailing list jetspeed-dev@jakarta.apache.org Received: (qmail 31559 invoked by uid 99); 19 Jun 2004 13:45:25 -0000 Received: from [65.24.5.135] (HELO ms-smtp-01-eri0.ohiordc.rr.com) (65.24.5.135) by apache.org (qpsmtpd/0.27.1) with ESMTP; Sat, 19 Jun 2004 06:45:25 -0700 Received: from 192.168.1.101 (cpe-024-165-122-126.cinci.rr.com [24.165.122.126]) by ms-smtp-01-eri0.ohiordc.rr.com (8.12.10/8.12.7) with ESMTP id i5JDjHJW028529 for ; Sat, 19 Jun 2004 09:45:18 -0400 (EDT) Subject: Re: [J2] Menu implementation From: Scott T Weaver To: Jetspeed Developers List In-Reply-To: <40D36544.9050309@douma.nu> References: <40CF1B72.8090307@douma.nu> <45B5E6E0-BEF0-11D8-BCF6-000393C78E78@bluesunrise.com> <40CF7815.3010809@douma.nu> <1087392717.3409.65.camel@pnqnp008-und538547.net.plm.eds.com> <1BC1AF50-BFD5-11D8-BCF6-000393C78E78@bluesunrise.com> <40D1B7F8.40900@apache.org> <1087487879.3468.29.camel@pnqnp008-und538547.net.plm.eds.com> <40D1C615.7010208@apache.org> <40D1F0FA.7090803@douma.nu> <1087500859.3468.37.camel@pnqnp008-und538547.net.plm.eds.com> <40D1F3A4.7030300@douma.nu> <6.1.1.1.2.20040618101723.02762ee0@mail.jahia.com> <40D30F47.7010803@douma.nu> <1087586296.3446.60.camel@pnqnp008-und538547.net.plm.eds.com> <40D3520F.1080305@douma.nu> <40D35F37.7040000@douma.nu> <4B70F320-C170-11D8-A0D3-000393C78E78@bluesunrise.com> <40D36544.9050309@douma.nu> Content-Type: text/plain Message-Id: <1087652709.3396.23.camel@scott> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.5-4mdk Date: Sat, 19 Jun 2004 09:45:15 -0400 Content-Transfer-Encoding: 7bit X-Virus-Scanned: Symantec AntiVirus Scan Engine X-Virus-Checked: Checked X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N On Fri, 2004-06-18 at 17:57, Ate Douma wrote: > David Sean Taylor wrote: > > > > > On Jun 18, 2004, at 2:31 PM, Ate Douma wrote: > > > >>>> > >>>> What I'm still missing is where folder/menu specific configuration is > >>>> defined. Things like ordering (I've read JS2-69, but that doesn't tell > >>>> me more), ACL, menu rendering depth. > >>>> > >>> If you look at the current PSML, ACLs are defined on the page and > >>> fragment level > >> > >> Yes. I know. > >> But I still don't know where to specify an ACL on a subfolder, or in > >> which > >> order I want my pages / subfolders be displayed in a menu (other than > >> alphabetically). > > > > > > A subfolder is just a page (PSML) right? > Wow. I didn't get that one yet. > I have the impression Scott wants to derive folders directly from > filesystem folders. Yes. That is exactly what I had in mind. > His comment on 6/16/2004: > >> Do I understand it now correctly that folders (for a file based Page Manager) > >> are simply derived from filesystem folders? > > That is how I see it. Or possibly using a VFS file system. > Furthermore, how would that psml look like? If a folder is a page, a folder > contains pages, and pages are all defined in their own psml you need external > references to define containment... > > > So the ACL is on the page in its respective PSML file > > > > For ordering, you need some metadata on the top level page > > > >> And, menu rendering depth probably will be the same for all pages within > >> a folder (and even pages within subfolders thereof). > >> Seems kinda strange to have to define this on each and every page. > > > > > > I think I misunderstand this. Wouldn't the menu for a page only have the > > menu-items from the immediate subpages (by default) below it? > > The user could then add or remove(disable) as needed > Normally not. > Consider a menu of depth 2 (Scott's example). > If I'm on a page from depth 1 and navigate to a page from depth2 wouldn't I want > to see the exact same menu (only indicating a different selection). > And if I navigate to a page from depth 3 I probably again want to see the same > menu. The parent folder (depth 2) menu item should then be selected. > A tree type menu (on the left) of unlimited depth starting from depth 3 would then > indicate the current page selection. > This is only one use case but a valid and a very common one I think. Yes, Ate this is a perfect use case. I would like to here others takes on use cases also just so we don't miss something. > > > > >> Menus based on folder navigation really are somewhat 'above' pages and > >> even > >> folders. > >> I don't want to update all of them just to increase/decrease the depth. > >> > > Im sorry but I don't understand what you are saying here > If you take the example I gave above, the menu (depth) configuration really should > be defined on the 'top' folder and be inherited/enforced below. If we need to define > this on or through each and every page definition it becomes troublesome to update it. > > > > >>>> Menu rendering depth could be hard coded and/or configured within > >>>> the layout > >>>> decoration but that would make it hard to modify through an Customizer. > >>>> > >>> Why not have menu metadata in the PSML? > >> > >> See above why that may not be so nice... > >> > > You lost me again. Do you mean immediately above? > > The whole point of PSML is that has a model that can be customized. > > When you customize, you manipulate PSML > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: jetspeed-dev-unsubscribe@jakarta.apache.org > > For additional commands, e-mail: jetspeed-dev-help@jakarta.apache.org > > > > > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: jetspeed-dev-unsubscribe@jakarta.apache.org > For additional commands, e-mail: jetspeed-dev-help@jakarta.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: jetspeed-dev-unsubscribe@jakarta.apache.org For additional commands, e-mail: jetspeed-dev-help@jakarta.apache.org