Carsten Ziegeler wrote: > > Nicola Ken Barozzi wrote: > > > > ... > > > Ah, the good, old and famous discussion about blocks vs. > > modules. I never > > > liked the name "blocks" for our current directory structure :) I > > > think we shouldn't change anything *now*, wait for the > "real blocks" > > > and decide then how the structure might look like. > > > > Well, regardless of the names and of the future directory > structure, > > the ParanoidStuff is not a block, and will never be a real > block. We > > can change the layout later, but IMHO it makes sense to > differentiate > > right now the two types of compilation units. > > > Ah, ok, now I see your point. I'm not very happy if the build > gets more complicated but I'm not against it. So, what do > others think? >
I think I agree with Nicola Ken. This kind of modularization can be very useful for using cocoon in a wider variety of setups. It will also expose dependencies that will need rethinking. One of the things is that the core is still too much bound to the http environment. It would be a good thing IMO to try and sort these things out. Unico
