cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Carsten Ziegeler <cziege...@apache.org>
Subject Re: Supported and unsupported blocks
Date Wed, 16 Mar 2005 14:57:34 GMT
Vadim Gritsenko wrote:
> 
> And I think nobody disagrees with that. Status page (suggested somewhere up the 
> thread) indicating the status of the block, some additional information about 
> the block, etc, will accomplish this even with flat directory structure in SVN.
> 
> What exactly changing directory structure buys you? If there is clear and 
> structured documentation about the blocks (it can use structure like 
> supported/unsupported/contributed/abandoned/whatever) and similarly structured 
> hierarchy in the sample webapp, what, on top of this, directory structure in SVN 
> gives?
> 
> I'm not so against moving stuff, but I'm just trying to understand why to move.
> 
Documenting the state is one thing, but imho just doing this in some
descriptor isn't very visible. Who reads documentation or looks into a
meta descriptor? :)
So, by using a directory structure, it's immediately visible for everyone.

Carsten

-- 
Carsten Ziegeler - Open Source Group, S&N AG
http://www.s-und-n.de
http://www.osoco.org/weblogs/rael/

Mime
View raw message