W3C home > Mailing lists > Public > public-forms@w3.org > November 2007

RE: Major problem with schema needs immediate attention.

From: Klotz, Leigh <Leigh.Klotz@xerox.com>
Date: Thu, 1 Nov 2007 11:59:50 -0700
Message-ID: <E254B0A7E0268949ABFE5EA97B7D0CF403BBDE74@USA7061MS01.na.xerox.net>
To: "John Boyer" <boyerj@ca.ibm.com>
Cc: <ebruchez@orbeon.com>, "Forms WG (new)" <public-forms@w3.org>
Actually, you can with select/copy.


From: John Boyer [mailto:boyerj@ca.ibm.com] 
Sent: Thursday, November 01, 2007 10:46 AM
To: Klotz, Leigh
Cc: ebruchez@orbeon.com; Forms WG (new)
Subject: RE: Major problem with schema needs immediate attention.

setvalue can't cross models either. 

Intentionally, xforms doesn't internally contain mechanisms that move
data between models. 
We do need a communication layer in the future, but it the preference is
for something that is thought out and intentional, rather than ad hoc
and anything goes. 
As such the only real way to move data between models is external script
that uses the DOM interface. 

John M. Boyer, Ph.D.
STSM: Lotus Forms Architect and Researcher
Chair, W3C Forms Working Group
Workplace, Portal and Collaboration Software
IBM Victoria Software Lab
E-Mail: boyerj@ca.ibm.com  

Blog: http://www.ibm.com/developerworks/blogs/page/JohnBoyer

"Klotz, Leigh" <Leigh.Klotz@xerox.com> 
Sent by: public-forms-request@w3.org 

11/01/2007 10:17 AM 

<ebruchez@orbeon.com>, "Forms WG (new)" <public-forms@w3.org> 
RE: Major problem with schema needs immediate attention.


Erik wrote:
>Or, put your temp var in a different model.

Yes, this is one of the problems.  You can't use them with calculate if
you put them in another model.
I think you can use setvalue, though.

Received on Thursday, 1 November 2007 19:00:47 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:48:27 UTC