- From: Tim Thompson <timathom@gmail.com>
- Date: Mon, 21 May 2018 11:50:20 -0400
- To: Steven Pemberton <steven.pemberton@cwi.nl>
- Cc: public-xformsusers@w3.org
- Message-ID: <CAPPeUfhcGvVvN6Ww=pMJ3EwO-s_tT4S=Sg2uKs=83bEc8f25xw@mail.gmail.com>
Hello, Isn't what you're describing the same as the subform/component functionality implemented by XSLTForms [1], betterForm, and Orbeon? Eric van der Vlist did a comparison of subform functionality a few years ago [2]. As an XForms user, I have often wished that subforms could be standardized and incorporated into the specification. To date, each implementation does things a little differently, which seems a detriment to interoperability. Seems like a crucial feature when developing larger forms. Best, Tim [1] XSLTForms subform example: http://www.agencexml.com/xsltforms/writers.xml [2] http://eric.van-der-vlist.com/blog/2013/06/17/when-mvc-becomes-a-burden-for-xforms-xml-london-2013/#Subforms -- Tim A. Thompson Discovery Metadata Librarian Yale University Library On Mon, May 21, 2018 at 10:36 AM, Steven Pemberton <steven.pemberton@cwi.nl> wrote: > Hi gang, > > This is a sort of day-dream email. > > Recently I have had a number of use-cases that included embedding forms > within forms (the biggest example of course being the test suite). > > My current method of doing this is to use an iframe; easy to do but with a > hurdle: it is hard to communicate between the parent and child forms. The > only way, it seems to me, is via a submit to a shared resource; not ideal. > > Has anyone tried such things already? > > It seems to me that the most XForms-like approach would be to pre-populate > a child-form's instance in some way, and to return values using some form > of submit to the parent. > > Any experience? > > Steven > >
Received on Monday, 21 May 2018 15:51:17 UTC