W3C home > Mailing lists > Public > www-forms@w3.org > August 2006

RE: Reusing a form in another form

From: Klotz, Leigh <Leigh.Klotz@xerox.com>
Date: Tue, 1 Aug 2006 16:10:25 -0700
Message-ID: <E254B0A7E0268949ABFE5EA97B7D0CF402127ABF@usa7061ms01.na.xerox.net>
To: <mark.birbeck@x-port.net>, "Alessandro Triglia" <sandro@mclink.it>
Cc: <www-forms@w3.org>

Early on, XForms had re-usable UI components, but they were dropped with
the idea that we would eventually use XSLT or XInclude.
We called the definition defcomponent and the use of it component.

-----Original Message-----
From: www-forms-request@w3.org [mailto:www-forms-request@w3.org] On
Behalf Of Mark Birbeck
Sent: Tuesday, August 01, 2006 4:03 PM
To: Alessandro Triglia
Cc: www-forms@w3.org
Subject: Re: Reusing a form in another form

Hi Alessandro,

> This sounds like a great idea.  I was thinking more in "static"

We use XInclude a lot, but the problem is the forms can end up very
big. What we're really after is a situation where the author doesn't
have to think about it, but how do you explain to an author why they
can't use 10 XInclude statements?

> ... but
> deferred loading is more interesting than static aggregation and
covers even
> more use cases.

Yes, I agree. Replacing part of a form with HTML is something that is
done a lot in the Ajax world, but it's very difficult to manage in a
scripted environment. Our approach using XForms makes it really easy.

> Did you say you are going to implement this?

Yes, we've already implemented it. And you have inspired me to write a
short blog entry about it too, which shows an example of the mark-up:


All the best,


Mark Birbeck
x-port.net Ltd.

e: Mark.Birbeck@x-port.net
t: +44 (0) 20 7689 9232
w: http://www.formsPlayer.com/
b: http://internet-apps.blogspot.com/

Download our XForms processor from
Received on Tuesday, 1 August 2006 23:10:50 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:36:18 UTC