Jeremy Quinn wrote:
>
> At 4:55 pm +0200 12/4/02, Stefano Mazzocchi wrote:
> >Jeremy Quinn wrote:
> >>
> >> At 1:53 pm +0200 11/4/02, Stefano Mazzocchi wrote:
> >> >Jeremy Quinn wrote:
> >> >
> >> >> How can we reconcile the differences between the needs of a generic form
> >> >> handling mechani
At 4:55 pm +0200 12/4/02, Stefano Mazzocchi wrote:
>Jeremy Quinn wrote:
>>
>> At 1:53 pm +0200 11/4/02, Stefano Mazzocchi wrote:
>> >Jeremy Quinn wrote:
>> >
>> >> How can we reconcile the differences between the needs of a generic form
>> >> handling mechanism for both Business Logic and Content
> From: Carsten Ziegeler [mailto:[EMAIL PROTECTED]]
>
> Nicola Ken Barozzi wrote:
> >
> >
> > What about:
> >
> > org.apache.cocoon.webapps.session
> > org.apache.cocoon.webapps.authentication
> > org.apache.cocoon.webapps.portal
> > org.apache.cocoon.webapps.forms
> >
> Funny, in fact (belie
Nicola Ken Barozzi wrote:
>
>
> What about:
>
> org.apache.cocoon.webapps.session
> org.apache.cocoon.webapps.authentication
> org.apache.cocoon.webapps.portal
> org.apache.cocoon.webapps.forms
>
Funny, in fact (believe it or not) "webapps" was my first
thought, too. But I thought noone would
From: "Carsten Ziegeler" <[EMAIL PROTECTED]>
> last week we agreed on moving the authentication and portal
> components from the scratchpad into the main area.
> For this we have to remove the sun*** names from the components.
>
> It seems that the "functionality" approach is the way to go,
> so
Hi Team,
last week we agreed on moving the authentication and portal
components from the scratchpad into the main area.
For this we have to remove the sun*** names from the components.
It seems that the "functionality" approach is the way to go,
so the packages should be named "authentication" a
Jeremy Quinn wrote:
>
> At 1:53 pm +0200 11/4/02, Stefano Mazzocchi wrote:
> >Jeremy Quinn wrote:
> >
> >> How can we reconcile the differences between the needs of a generic form
> >> handling mechanism for both Business Logic and Content Management?
> >
> >I say we don't even try.
>
> fair eno
At 1:53 pm +0200 11/4/02, Stefano Mazzocchi wrote:
>Jeremy Quinn wrote:
>
>> How can we reconcile the differences between the needs of a generic form
>> handling mechanism for both Business Logic and Content Management?
>
>I say we don't even try.
fair enough
>Forms generate highly structured da
On Thu, 11 Apr 2002, Stefano Mazzocchi wrote:
> Forms generate highly structured data while browser-based content
> editing generates semi-structured data.
>
> These datasets are so different they can't be handled (nicely!) with the
> same database, why would you think this model doesn't apply to
Jeremy Quinn wrote:
> How can we reconcile the differences between the needs of a generic form
> handling mechanism for both Business Logic and Content Management?
I say we don't even try.
Forms generate highly structured data while browser-based content
editing generates semi-structured data.
At 2:16 pm +0200 10/4/02, Stefano Mazzocchi wrote:
> b) the form-handling stuff should be merged into a coherent proposal
>and moved over to the trunk. The old stuff currently placed in the
>scratchpad should be removed.
The main problem as I see it for integrating abilities of the
"content-edit
On 10.Apr.2002 -- 02:16 PM, Stefano Mazzocchi wrote:
> This series has been placed in a CVS branch. The Cocoon developers are
> committed to support the 2.0.x branch until the 2.1.x branch becomes
> solid enough for people to move over.
+1 although I though this scratchpad thingy is as good as a
John Morrison wrote:
>>
I'd prefer them seperated - I can imagine uses where the
auth toolkit is needed but not the portal...
<<
Yepp of course. That's correct. They should be seperated.
Matthew
-
To unsubscribe, e-mail: [EMAIL
> So, this said, here is the summary of the previous vote for 2.1-dev:
>
> 1) the TreeProcessor becomes the central pipeline manager. The old
> compiled sitemap gets removed (not 'deprecated' because that might
> happen in future versions of the 2.0.x branch, I see no need in
> deprecating this
Weblogging at: http://www.need-a-cake.com
> Cocoon book: http://www.amazon.com/exec/obidos/ASIN/0735712352
> =
>
>
>
> -Original Message-----
> From: Steven Noels [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, April 10, 2002 3:50 PM
> To: [EMAIL PROTECTED]
> Su
m/exec/obidos/ASIN/0735712352
=
-Original Message-
From: Steven Noels [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, April 10, 2002 3:50 PM
To: [EMAIL PROTECTED]
Subject: RE: [vote] Development Roadmap
Carsten wrote:
> >
Carsten wrote:
> First we need some good package names. Of course the
> effective approach
> would
> be to use something like "session", "authentication" and "portal", but
> that's
> really boring.
But effective & clear...
We could get rid of the Sun prefix, rephrase some of them using these
'b
> From: Carsten Ziegeler [mailto:[EMAIL PROTECTED]]
>
> Steven Noels wrote:
> >
> > Carsten wrote:
> >
> > > > a) the sun stuff must change name and things must be
> > > refactored to
> > > > understand what is a global feature and what is a sample. I
> > > would like
> > > > Carsten to prop
To: [EMAIL PROTECTED]
> Sent: Wednesday, April 10, 2002 10:08 AM
> To: [EMAIL PROTECTED]
> Subject: RE: [vote] Development Roadmap
>
>
> Steven Noels wrote:
> >
> > Carsten wrote:
> >
> > > > a) the sun stuff must change name and t
Steven Noels wrote:
>
> Carsten wrote:
>
> > > a) the sun stuff must change name and things must be
> > refactored to
> > > understand what is a global feature and what is a sample. I
> > would like
> > > Carsten to propose a plan on this specificaly
> > >
> > Yes, a name change is really re
Carsten wrote:
> > a) the sun stuff must change name and things must be
> refactored to
> > understand what is a global feature and what is a sample. I
> would like
> > Carsten to propose a plan on this specificaly
> >
> Yes, a name change is really required. Unfortunately, we are
> currentl
Stefano Mazzocchi wrote:
> Before we go on, I think we should vote on the 'development roadmap'
> that we should follow. This helps us understand what should go in the
> main trunk and why.
>
> 2.0.x
> -
>
> This series has been placed in a CVS branch. The Cocoon developers are
> committed t
Stefano Mazzocchi wrote:
>
> Before we go on, I think we should vote on the 'development roadmap'
> that we should follow. This helps us understand what should go in the
> main trunk and why.
>
Very good idea!
> 2.0.x
> -
>
> This series has been placed in a CVS branch. The Cocoon develop
Before we go on, I think we should vote on the 'development roadmap'
that we should follow. This helps us understand what should go in the
main trunk and why.
2.0.x
-
This series has been placed in a CVS branch. The Cocoon developers are
committed to support the 2.0.x branch until the 2.1.x
24 matches
Mail list logo
