Return-Path: Delivered-To: apmail-xml-cocoon-dev-archive@xml.apache.org Received: (qmail 70676 invoked by uid 500); 26 May 2003 07:17:16 -0000 Mailing-List: contact cocoon-dev-help@xml.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: list-post: Reply-To: cocoon-dev@xml.apache.org Delivered-To: mailing list cocoon-dev@xml.apache.org Received: (qmail 70527 invoked from network); 26 May 2003 07:17:14 -0000 Received: from fw.otego.com (HELO lapgp.otego.com) (195.216.81.146) by daedalus.apache.org with SMTP; 26 May 2003 07:17:14 -0000 Received: (qmail 17914 invoked from network); 26 May 2003 07:17:16 -0000 Received: from localhost (127.0.0.1) by localhost with SMTP; 26 May 2003 07:17:16 -0000 Date: Mon, 26 May 2003 09:17:15 +0200 (CEST) From: Giacomo Pati Sender: giacomo@lapgp.otego.com To: cocoon-dev@xml.apache.org Subject: Re: [RT] XMLForm In-Reply-To: <003801c3231d$5afc6520$0100a8c0@MAUCHI> Message-ID: References: <3ED119C5.1040906@verizon.net> <003801c3231d$5afc6520$0100a8c0@MAUCHI> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N On Sun, 25 May 2003, Ivelin Ivanov wrote: > > I received a private communication from Ivelin suggesting to replace the > > XMLForm block with the JXForms implementation in the scratchpad, > > incorporating features he added in his xmlform.org code for the 2.1 > release. > > > > After some thought, I decided that at this point this makes most sense, > provided that Chris is committed to drive the effort to completion in a > triumphal C2.1 final. > > I will try to assist from the sidelines with whatever time I have. > > As a one line overview to folks that are not familiar with JXForm yet: > It reuses much of the XMLForm code, while heavily emphasizing on the flow > integration. > Chris, please correct me if I am wrong. Absolutely. We first decided to use xmlform together with flow and switched to jxform later because of the better integration with the flow stuff. Giacomo