cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From giacomo <giac...@apache.org>
Subject Re: [status & RT] design challenges
Date Mon, 08 Apr 2002 11:30:13 GMT
On Mon, 8 Apr 2002, Stefano Mazzocchi wrote:

> Ovidiu Predescu wrote:
>
> > They already live together!
>
> Ok, but what I want is:
>
>  1) merge 'schecoon' with the trunk

big +1

I hope the CM bug will be eliminated faster this way having other to
look at it more closely than today (where almost only Ovidiu is in
charge of this).

>  2) have the ability to mount a 'flowmap' into a 'sitemap' and a
> 'sitemap' into a 'flowmap'.

This is an absolute must IMHO. This allows a flow to state its views
(not cocoon views but MVC views expressed in a sitemap). Today it's the
sitemap that mounts the
flow (because today it has to be done so) but naturally it makes more
sense to have the flowmap to mount the sitemap

> Until I have this, they are not living together in my book.
>
> Now, I'll be in favor of 'branching the CVS module' to keep the '2.0.x'
> series clean and start moving stuff from the scratchpad into the trunk
> and name that 2.1-dev

We are familliar with this kind of environment (even if some might see
overhead).

+1 on creating a branch for either 2.0.x or 2.1.

> I want more visibility for what currently lies in the scratchpad because
> I think that currently Schecoon is an 'internal fork' and I personally
> don't consider it *working* in Cocoon until the two things are merged
> together.

I agree.

Giacomo


---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org


Mime
View raw message