On 05.04.2004 00:18, Stefano Mazzocchi wrote:
in the past I was used to:

 1) cp blocks.properties local.blocks.properties
 2) vi local.blocks.properties
 3) uncomment the blocks that I wanted to exclude

Today, I have to go thru a bunch of include and change them from true to false. Much more hassle than just uncommenting/commenting one line.

That's true obviously. But you can still use the exclude syntax in your local.blocks.properties if you want.


Please, revert back to how it was before or make it equivalently painless to reduce the blocks tuning time.

Tony already pointed it out, it was based on a vote started by me. The reason for the change is naming itself on the one hand. Not only native English speaking people found the exclude syntax a mass.


But the real need for changing it came out of the discussion about default excludes of blocks (e.g. javaflow or all unstable blocks). You have *no* possibility to re-include a block then in local.blocks.properties.

Furthermore the ideas already go beyond the current version:
http://marc.theaimsgroup.com/?t=108084941400006&r=1&w=4
http://marc.theaimsgroup.com/?l=xml-cocoon-dev&m=108091508726085&w=4

Joerg

Reply via email to