Sylvain Wallez wrote:
Team, here's a formal vote about splitting cocoon.xconf.
I propose to add a new <import> feature in cocoon.xconf so that
adding/removing blocks to a Cocoon instance doesn't require do merge
each block's configuration in a unique cocoon.xconf file as of today.
With this feature, cocoon.xconf can simply be a list of imports, thus
allowing to very easily add/remove blocks in a Cocoon application. For
more background, please see the initial "splitting cocoon.xconf" post [1].
The first implementation will focus on basic import (one file per
<import> element), and later on we'll implement globbing features
proposed by Carsten [2].
Please cast your votes.
Here's my +1 (of course!)
Sylvain
[1] http://marc.theaimsgroup.com/?l=xml-cocoon-dev&m=110354180900487&w=2
[2] http://marc.theaimsgroup.com/?l=xml-cocoon-dev&m=110361460811792&w=2
Lovely, I won't have to use XPath.
+1
--
Leszek Gawron [EMAIL PROTECTED]
Project Manager MobileBox sp. z o.o.
+48 (61) 855 06 67 http://www.mobilebox.pl
mobile: +48 (501) 720 812 fax: +48 (61) 853 29 65
