value and copy fix, was RE: Major problem with schema needs immediate attention.

I know we had a big row about that at some face to face and agreed that 
you could not in fact have value or copy point to a model different from 
the selection control.
This was a big issue because Mark S. was using it and we told him not to.
May have even been the Edinburgh FtF.
Of course the resolution and action item to make note of it in the spec 
seems to have fallen through the cracks...

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> 
11/01/2007 11:59 AM

To
John Boyer/CanWest/IBM@IBMCA
cc
<ebruchez@orbeon.com>, "Forms WG (new)" <public-forms@w3.org>
Subject
RE: Major problem with schema needs immediate attention.






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. 

Cheers, 
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 


To
<ebruchez@orbeon.com>, "Forms WG (new)" <public-forms@w3.org> 
cc

Subject
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.

Leigh.