W3C home > Mailing lists > Public > www-forms@w3.org > March 2002

Binding and constraints dereferencing

From: Stefano Debenedetti <sdebenedetti@e-tree.com>
Date: Fri, 22 Mar 2002 16:46:52 +0100
Message-ID: <3C9B51EC.3060005@e-tree.com>
To: Micah Dubinko <MDubinko@cardiff.com>
CC: www-forms@w3.org
Hello Micah,

thank you very much, I will come up soon with some questions regarding 
combining XForms with other languages, for now I have a question 
concerning this specific paragraph of the spec:

4.4.1 xforms:submit Dispatched in response to: a user request to submit 
the instance data.
Target: submitInfo
(....)
Default processing for this event results in the following:

1.A node from the instance data is selected, based on the attribute ref 
on element submitInfo. This node and all child nodes, are considered for 
the remainder of the submit process.

My question is: only the ref attribute should be considered? Isn't it 
more convenient to check for a bind attribute first?

I mean: I can't understand how the overriding of the binding references 
works, what happens if I use both a bind and a ref attribute on a UI or 
a sumbitInfo element? The funny thing is that step 3 of process 
described in the 6.4.2 paragraph (getting to know what schema 
constraints should be applied) depends on that too but isn't clear 
enough anyways (to me, of course).

Can you please clarify a bit those two algoritms a bit? I think it is 
important because of course different behaviors on this vital 
functionality for an XForms processor would bring to very different 
XForms document writing strategies.

Thank you very much, ciao
ste



Micah Dubinko wrote:
> Hi Stefano,
> 
> Briefly,
> 
> <xforms:switch>
>   <xforms:case>
>     <!-- page 1 goes here (both HTML and XForms UI) -->
>   </xforms:case>
>   <xforms:case>
>     <!-- page 2 goes here -->
>   </xforms:case>
>   <xforms:case>
>     <!-- page ... goes here -->
>   </xforms:case>
> </xforms:switch>
> 
> Then you would need buttons or perhaps a list to fire 'toggle' events to
> flip the pages.
> 
> Thanks,
> 
> .micah
> 
> -----Original Message-----
> From: Stefano Debenedetti [mailto:sdebenedetti@e-tree.com]
> Sent: Monday, March 18, 2002 9:04 AM
> To: www-forms@w3.org
> Subject: grouping form controls in multiple XHTML pages
> 
> 
> Hello, I'm trying to visualize how a multi-page form would look like in 
> XForms/XHTML, is there any example I can copy from?
> What I'm trying to acheive is the same functionality that can be seen on 
> the XSmiles browser under Edit|Configuration (xsmiles/cfg/config.xml): 
> only one model at the beginning of the document, followed by a series of 
> "UI-cards" implementing it in the rest of the document.
> I know that actual functionalities like navigation and persistance of 
> data between between cards will someday be provided by a 
> browser-specific-standard UI element (like the "Site navigation bar" in 
> mozilla), I don't care about seeing it work today, I just need an 
> example of how would it be done in XForms/XHTML.
> Thank you, ciao
> ste
> 
Received on Friday, 22 March 2002 10:45:35 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Saturday, 10 March 2012 06:21:50 GMT