Vadim Gritsenko wrote:
Sylvain Wallez wrote:
...
- do you want each block to have it's own status.xml file?
-0, reduces visibility.
Having a separate file doesn't mean it doesn't appear on a different page in the docs. Cocoon has some nice features for aggregation ;-)
It is easier to peek into one file, especially if it resides in module root ;-) instead of ferreting through all blocks - and I'm thinking about developers (including me) here :-)
Let's do instead:
* Do you want to add a block="name" attribute on <action> in changes.xml?
+1
Good. The important point is to have a per-block classification, even if I personally prefer a per-block file.
Let's do an attribute, please :-)
Vadim
