Return-Path: 
 <cocoon-dev-return-42795-apmail-xml-cocoon-dev-archive=xml.apache.org@xml.apache.org>
Delivered-To: apmail-xml-cocoon-dev-archive@xml.apache.org
Received: (qmail 84676 invoked by uid 500); 26 May 2003 07:25:34 -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 84624 invoked from network); 26 May 2003 07:25:34 -0000
Received: from unknown (HELO mail.cbim.it) (212.131.130.82)
  by daedalus.apache.org with SMTP; 26 May 2003 07:25:34 -0000
Received: from cuprouter.cbim.it (cuprouter.cbim.it [192.168.4.10])
	by mail.cbim.it (8.11.6/8.11.0) with ESMTP id h4Q7mB625603
	for <cocoon-dev@xml.apache.org>; Mon, 26 May 2003 09:48:11 +0200
Received: from cbim.it (caterina.cbim.it [192.168.4.42])
	by cuprouter.cbim.it (8.9.3/8.9.3) with ESMTP id JAA30253;
	Mon, 26 May 2003 09:26:29 +0200
Message-ID: <3ED1C1A6.6010900@cbim.it>
Date: Mon, 26 May 2003 09:26:30 +0200
From: Ugo Cei <u.cei@cbim.it>
Organization: C.B.I.M.
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3) Gecko/20030314
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: cocoon-dev@xml.apache.org
Subject: Re: [RT] XMLForm
References: <3ED119C5.1040906@verizon.net>
In-Reply-To: <3ED119C5.1040906@verizon.net>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N

Christopher Oliver 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.

+1 :-)

We just started implementing a new application, and before deciding 
which kind of GUI to use (native, Swing or web), we are doing a 
proof-of-concept using XMLForm/JXForms. So expect me to fill many bug 
reports in the coming days.

> Unfortunately, however, the stylesheets that are shipped with XMLForm 
> are not generic, but instead, apparently, must be reused in a 
> cut-and-paste fashion, and modified for each application.

Indeed. Maybe we should design a helper stylesheet to transform xf:* 
elements to HTML <input>s and the like, and leave the composition of 
those into a page, using a <table> or something else, to an 
application-specific stylesheet. Easier said than done, though.

I'd also like to explore the possibility of deriving client-side 
validation code from a Schematron, Relax_NG or other type of schema.

And last but not least, my personal pet peeve: make "views" internal 
only. At the moment, IIUC, you cannot call sendPage(URI) if the URI is 
matched by a matcher in an internal-only pipeline.

	Ugo

-- 
Ugo Cei - Consorzio di Bioingegneria e Informatica Medica
P.le Volontari del Sangue, 2 - 27100 Pavia - Italy
Phone: +39.0382.525100 - E-mail: u.cei@cbim.it