"Andrew C. Oliver" wrote:
> > > Just what IS Cocoon?
> >
> >This one will be solved when Cocoon Blocks are available and every
> >installation can be customized depending on the needs and 3rd party stuff
> >can be provided as blocks and not with the core.
>
> No. It will be mitigated, but not solved. Still answer "What is
> Cocoon?" -- try it.
I've been thinking a lot about this: how should we market Cocoon? Right
now it's simply too hard since Cocoon has grown to be too many things in
one place. This is why I proposed the creation of blocks.
After blocks are implemented (yes, expect big RT on this very soon)
Cocoon will change from a big WAR to a smaller WAR that implements a COB
(COcoon Block) container and provides some standard blocks.
Giacomo calls this block container a 'naked cocoon' and I love the
concept: it's the cocoon core, with no direct functionality. Blocks will
provide functionality. Some blocks are written by you, some blocks are
installed from other places.
A 'naked cocoon' is an server-side XML application framework.
That is: cocoon is glue for your web needs.
--
Stefano Mazzocchi One must still have chaos in oneself to be
able to give birth to a dancing star.
<[EMAIL PROTECTED]> Friedrich Nietzsche
--------------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]