Carsten Ziegeler wrote:
Stefano Mazzocchi wrote:
I think this is not too hard to do: a simple ant task that copies the xconf for a block into the xconf directory and adds all include statements.
The more it think about this, the more I believe that <imports> should not be done explicitly but implicitly, based on some aggregated dependency information (for example, the blocks should have their block descriptor block.xml and include the dependency information there)
If I have time, I will look into that this weekend, but can't promise anything :)
The include features in xconf allows to very simply add or remove a block by just moving files around. I would like to keep this simplicity and avoid by all means to go back to some build-time generation of these files like we have today with xpatch in 2.1
Amen.
There aren't that much inter-block dependencies, and I don't have the feeling hand maintaining them is really complicated.
What I would like to see is something like this:
1) src/block/*/block.xml
that contains something as simple as
<block name="a"> <depends-on block="b"/> <depends-on block="c"/> </block>
2) this info used by cocoon at startup time (NOT COMPILE TIME!) to drive the xconf imports.
How hard can that be!?!
-- Stefano.
