Return-Path: 
 <cocoon-dev-return-39405-apmail-xml-cocoon-dev-archive=xml.apache.org@xml.apache.org>
Delivered-To: apmail-xml-cocoon-dev-archive@xml.apache.org
Received: (qmail 78994 invoked by uid 500); 28 Mar 2003 14:40:02 -0000
Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm
Precedence: bulk
list-help: <mailto:cocoon-dev-help@xml.apache.org>
list-unsubscribe: <mailto:cocoon-dev-unsubscribe@xml.apache.org>
list-post: <mailto:cocoon-dev@xml.apache.org>
Reply-To: cocoon-dev@xml.apache.org
Delivered-To: mailing list cocoon-dev@xml.apache.org
Received: (qmail 78981 invoked from network); 28 Mar 2003 14:40:02 -0000
Received: from smtp809.mail.sc5.yahoo.com (66.163.168.188)
  by daedalus.apache.org with SMTP; 28 Mar 2003 14:40:02 -0000
Received: from adsl-66-141-54-62.dsl.rcsntx.swbell.net (HELO MAUCHI)
 (ivelin@sbcglobal.net@66.141.54.62 with login)
  by smtp-sbc-v1.mail.vip.sc5.yahoo.com with SMTP; 28 Mar 2003 14:40:03 -0000
Message-ID: <00c501c2f537$f0813080$0100a8c0@MAUCHI>
From: "ivelin" <ivelin@apache.org>
To: <cocoon-dev@xml.apache.org>
References: <BAA96CD5.17C07%pier@betaversion.org>
 <008b01c2f4e0$530d08d0$0100a8c0@MAUCHI> <3E841F63.7010407@dff.st>
Subject: Re: [ANN] XMLForm as a standalone servlet toolkit
Date: Fri, 28 Mar 2003 08:40:10 -0600
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2600.0000
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2600.0000
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N



> > Let me explain, maybe the goodwill will prevail.
> > Otherwise this will turn into another example of a sad finish of an
exciting
> > jorney.
>
> <snip/>
>
> I am sure goodwill is a main reason but some question come to my mind
>
> *) why don't you wanna share your thoughts with us and let us
>     (or at least some of us) together steer the direction of XMLForms?

Wrong assumption!
I always welcome feedback, comments and improvements, even if I don't agree
with some of them.

>
> *) how do you wanna contribute back? this might become harder as
>     we currently might think. the "standalone version" thing really
>     points that way.
>
> *) project and communication wise this might give an unwanted
>     perspective that XMLForm might not be maintained under the
>     cocoon umbrella anymore. not a good marketing...


I don't like hosting elsewhere either, but what are the options?


>
> *) why don't you go the scratchpad way?

Does this mean that in order for someone who wants to help with the
experimental code to build and run,
they will have to get and build the whole latest 2.1 HEAD? If so, then not a
good option.
Too many moving parts in 2.1., a lot of dependencies and coupling. I want to
focus on one thing at a time.
If we can dedicate a piece in scratchpad to build a module which can be
build and use on its own, then that's cool, I'll go for it.

> Is that the main reason for this - you wanna catch up with the XForms
> standard?

What do you mean?
Look at Chiba

> At least *I* honstely don't see a good reason for XMLForm becoming it's
> own Apache project - sorry.

Others disagree with you.
I have been asked numerous times via private emails, if it can be used
independently for smaller projects?
It can be cleanly isolated and interfaced with cocoon via some sort of
adapter.
This only confirms the value and need for blocks.


Ivelin