Many good comments, mostly I think you are actually agreeing with me, so
I'll try and be brief...
>>
>>Yes, and I'm still advocating the brainstorming. What I'm suggesting is
>>that only one person can really "design" something.
>>
>
> I strongly disagree with this : although there must be a
> Since I know I wouldn't have been able to do it alone (Cocoon1 was done
> by myself alone and we saw where that went :), I think it's the entire
> dev community that did the cocoon design.
:-) How many of us can say that any of their first version systems are even
running long after version 2
Hunsberger, Peter wrote:
My real point is that I think that it's really hard for
multiple people to write an architecture together. I trust that
anyone proposing a major change to an architecture is experienced
enough or smart enough to know how to get to the end point.
Hmmm, have you
You touch important points, Peter, I'll try to answer them at my very best.
Hunsberger, Peter wrote:
>>My real point is that I think that it's really hard for
>>multiple people to write an architecture together. I trust that
>>anyone proposing a major change to an architecture is experienced
>>
>> My real point is that I think that it's really hard for
>> multiple people to write an architecture together. I trust that
>> anyone proposing a major change to an architecture is experienced
>> enough or smart enough to know how to get to the end point.
>
> Hmmm, have you ever read some o
Hunsberger, Peter wrote:
I don't think that any of this is really any different than what is
happening today.
Yes, Cocoon was, in fact, built entirely like this: one person has an
idea and a development community refines it. Maybe using several
design/implement/test phases.
My real point is
>>
>> I've been calling this way of doing software "open development" since
>> "open source" refers to the distribution of software, not the way the
>> development community is run.
>>
>> I don't want anybody (so myself included) to do anything behind the back
>> of anybody. Nor to make it a
Stefano Mazzocchi wrote:
>
>
> I've been calling this way of doing software "open development" since
> "open source" refers to the distribution of software, not the way the
> development community is run.
>
> I don't want anybody (so myself included) to do anything behind the back
> of anyb
Leo Sutic wrote:
Stefano,
1) I don't care if you do it behind my back or wherever.
You might not, but I do.
I've been calling this way of doing software "open development" since
"open source" refers to the distribution of software, not the way the
development community is run.
I don't want
> From: Stefano Mazzocchi [mailto:stefano@;apache.org]
>
> Leo Sutic wrote:
>
> >
> > >From: Stefano Mazzocchi [mailto:stefano@;apache.org]
> > >
> > > phase 2) use blocks just for deployment. This is mostly
> similar at
> > >WAR files today: just package your stuff as a block and
> deploy
Leo Sutic wrote:
>From: Stefano Mazzocchi [mailto:stefano@;apache.org]
>
> phase 2) use blocks just for deployment. This is mostly
>similar at WAR
>files today: just package your stuff as a block and deploy it on a
>running Cocoon.
Stefano,
does this imply that Cocoon will move from being a
Amir Rosen wrote:
>And the great thing is, that this web interface will be
>developed using
>Cocoon and it's components. So it is also a good presentation
>of Cocoon
>itself: we can show flow script, svg generation etc.
>
>Carsten
>
So You'll have to install the batik block (and any other block
Leo Sutic wrote:
From: Stefano Mazzocchi [mailto:stefano@;apache.org]
phase 2) use blocks just for deployment. This is mostly
similar at WAR
files today: just package your stuff as a block and deploy it on a
running Cocoon.
Stefano,
does this imply that Cocoon will move from being a
Amir Rosen wrote:
> .
> > > Also, we planned on having a web interface on top of Cocoon for
> > > configurations and for block deployment. Of course, all secured and
> > > possibly to be turned off for production environments.
> > >
> > And this is the part where we spend most time, because this
>
> From: Stefano Mazzocchi [mailto:stefano@;apache.org]
>
> phase 2) use blocks just for deployment. This is mostly
> similar at WAR
> files today: just package your stuff as a block and deploy it on a
> running Cocoon.
Stefano,
does this imply that Cocoon will move from being a servlet t
.
.
.
> > Also, we planned on having a web interface on top of Cocoon for
> > configurations and for block deployment. Of course, all secured and
> > possibly to be turned off for production environments.
> >
> And this is the part where we spend most time, because this
> is the interface
> to the
Stefano Mazzocchi wrote:
>
> All right, I'm back from Germany.
>
I hope you had a nice and easy trip back without any storm!
>
> Anyway, I won't go over everything that happened there, but the
> important thing for us is that I finally managed to explain the block
> concept to Carsten the way I in
17 matches
Mail list logo
