Dominik Huber wrote:
We should have an application/framework-level hook within the site.zcml
that is processed before *-configure.zcml are invoked.
Problem: A framework package 'b.x' registers a dedicated menu 'b_views'.
A package 'a.x' using 'b.x' should be able to register menu items
On Monday 25 April 2005 09:03, Dominik Huber wrote:
Problem: A framework package 'b.x' registers a dedicated menu 'b_views'.
A package 'a.x' using 'b.x' should be able to register menu items
refering 'b_views'. The initialisation will fail because 'a.x' is loaded
before 'b.x' and therefore
Hi Shane
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On
Behalf Of Shane Hathaway
Sent: Monday, April 25, 2005 3:38 PM
To: Dominik Huber
Cc: zope3-dev@zope.org
Subject: Re: [Zope3-dev] site.zcml (ftesting.zcml) extension
Dominik Huber wrote:
We should have an application
Stephan Richter wrote:
On Monday 25 April 2005 09:03, Dominik Huber wrote:
Problem: A framework package 'b.x' registers a dedicated menu 'b_views'.
A package 'a.x' using 'b.x' should be able to register menu items
refering 'b_views'. The initialisation will fail because 'a.x' is loaded
before
On Monday 25 April 2005 10:52, Roger Ineichen wrote:
The alphabtice order of configure.zcml like Stephan proposed
is one solution. But I like a more explicit solution for this
like Dominik proposed with a additional application level
for 3rd party packages.
I did not propose to have
On Monday 25 April 2005 11:08, Dominik Huber wrote:
Stephan Richter wrote:
On Monday 25 April 2005 09:03, Dominik Huber wrote:
Problem: A framework package 'b.x' registers a dedicated menu 'b_views'.
A package 'a.x' using 'b.x' should be able to register menu items
refering 'b_views'. The
Shane Hathaway wrote:
Dominik Huber wrote:
We should have an application/framework-level hook within the site.zcml
that is processed before *-configure.zcml are invoked.
Problem: A framework package 'b.x' registers a dedicated menu 'b_views'.
A package 'a.x' using 'b.x' should be able to
