[Framework-Team] Re: Review of PLIP 142 - Martin vs. global_contentmenu

2006-09-23 Thread Martin Aspeli
Hi Hanno, The other thing is that the browser:menuItem and browser:menu directives do all kinds of non-fun magic in the ZCML registration that we'd have to replicate, and I don't know how hard this would be. Mmh, but this means we don't know how easy this is to accomplish and we leave the pro

[Framework-Team] Re: Review of PLIP 142 - Martin vs. global_contentmenu

2006-09-23 Thread Hanno Schlichting
Martin Aspeli wrote: > Hi Hanno, > >> 1. Global configuration: >> >> Currently menus (Actions menu, Workflow menu, ...) are configured in >> ZCML and thus immediately available without any installation step. >> >> For an add-on product this means there is no way to unregister a >> particular menu

[Framework-Team] Re: Review of PLIP 142 - Martin vs. global_contentmenu

2006-09-23 Thread Rocky Burt
On Thu, 2006-21-09 at 21:55 +0100, Martin Aspeli wrote: > > For an add-on product this means there is no way to unregister a > > particular menu and menus added this way are available without > > installation as they are global adapters and utilities. > > Well, a third party product can of course

[Framework-Team] Re: Review of PLIP 142 - Martin vs. global_contentmenu

2006-09-21 Thread Martin Aspeli
Hi Hanno, The short summary is: Martin vs. global_contentmenu round 1: Martin uses his special attack called "viewlets and contentproviders" and wins the battle in round one with a knockout ;) :) 1. Global configuration: Currently menus (Actions menu, Workflow menu, ...) are configured in