Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cocoon.apache.org
Mime-Version: 1.0 (Apple Message framework v613)
In-Reply-To: <29844.1080150799@www23.gmx.net>
References: <c3sgt1$i2d$1@sea.gmane.org> <29844.1080150799@www23.gmx.net>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Message-Id: <57B03014-7DBE-11D8-B430-000A95AF004E@codeconsult.ch>
Content-Transfer-Encoding: quoted-printable
From: Bertrand Delacretaz <bdelacretaz@codeconsult.ch>
Subject: Re: [RT] On building on stone
Date: Wed, 24 Mar 2004 19:09:07 +0100
To: dev@cocoon.apache.org

Le 24 mars 04, =E0 18:53, Peter Brant a =E9crit :

> (also from a normal-developer-user perspective) I agree with Jorg that=20=

> it's
> really nifty to be able to reuse my Cocoon components outside of a
> Cocoon/Web-oriented environment.  It would be great to retain this=20
> ability regardless
> of the results of this discussion.

If the Cocoon Core becomes sufficiently small and simple (and I believe=20=

it will given the right container), it won't matter much if you use it=20=

without requiring the web features.

IMHO the current perception that Cocoon is a "big thing" is largely due=20=

to the complexity imposed by Avalon, and this will go away with a=20
simpler container framework. We'll just have to adjust our user's=20
perceptions once this is realized ;-)

-Bertrand=