Carsten Ziegeler wrote:
I think that the idea is excellent, but I wouldn't make it a block.Hi,it just came across my mind to create a "deprecated" block/module which contains all deprecated classes and interfaces. This would clean our core but we would still have compatibility when the block is used. Does this make sense? What do you think?
Blocks will be pluggable components, ut what you envision may need the classes at startup.
I would propose that we mimic the blocks build system for a section that contains Cocoon "parts" that can be used on startup, but can be taken out of the core.
I sent a mail some time ago about this, to create "modules" alongside blocks, but then I married, didn't follow it, and didn't even see if it had arrived ;-)
In this way the core can be smaller still, and we can keep additional functionality that is not part of the blocks concept separate. This could also help in making Cocoon profiles for smaller devices or such.
We would still have to decide the name though, is "modules" ok? Dunno.
--
Nicola Ken Barozzi [EMAIL PROTECTED]
- verba volant, scripta manent -
(discussions get forgotten, just code remains)
---------------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
