Sylvain Wallez wrote: [...]
<map:components> is getting bigger and bigger, and often bigger than <map:pipelines> itself. So what about allowing it to be in a separate file :At one time we wanted all the components in sitemap.xmap, at other times we leaned to putting them in cocoon.xconf.
<map:sitemap>
<map:components src="sitemap.xconf"/>
<map:pipelines>
....
</map:pipelines>
<map:sitemap>
This can also be a first step towards the future structure of blocks.
After some time, this is MHO on the subject:
- cocoon.xconf is just about the components that make up Cocoon
the contents are hardcoded or added by the build system for the
"features" and "environments"
- sitemap.xmap is about defining the sitemap. Its components
can be declared in a separate file it references
- components.xmap, or components.xcomp or sitemap.xcomp
or sitemap.xconf ...
holds component declarations for sitemaps, that can reference it.
I know it's what you have just said, I just can't help being formal these days ;-)
--
Nicola Ken Barozzi [EMAIL PROTECTED]
- verba volant, scripta manent -
(discussions get forgotten, just code remains)
---------------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
