W3C home > Mailing lists > Public > public-forms@w3.org > April 2012

Re: Supporting AVTs in bind and model attributes

From: John Boyer <boyerj@ca.ibm.com>
Date: Wed, 18 Apr 2012 07:17:26 -0700
To: Nick Van den Bleeken <Nick.Van.den.Bleeken@inventivegroup.com>
Cc: Public Forms <public-forms@w3.org>, "public-xformsusers@w3.org" <public-xformsusers@w3.org>
Message-ID: <OF172FA6E2.C8AD256B-ON882579E4.004E5E22-882579E4.004E80A5@ca.ibm.com>
Hi Nick,

I think we agreed previously to just call those out as binding exceptions 
for now.

John M. Boyer, Ph.D.
Distinguished Engineer, IBM Forms and Smarter Web Applications
IBM Canada Software Lab, Victoria
E-Mail: boyerj@ca.ibm.com 

Twitter: http://twitter.com/johnboyerphd
Blog: http://www.ibm.com/developerworks/blogs/page/JohnBoyer
Blog RSS feed: 

From:   Nick Van den Bleeken <Nick.Van.den.Bleeken@inventivegroup.com>
To:     Public Forms <public-forms@w3.org>
Cc:     "public-xformsusers@w3.org" <public-xformsusers@w3.org>
Date:   18/04/2012 03:45 AM
Subject:        Supporting AVTs in bind and model attributes


Do we want to support AVTs in bind and model attributes? This will require 
some rewiring of UI controls if their value changes. And even cause 
exceptions because a custom function isn't available in the new model if 
the value of the model attribute changes. 
Kind regards,

Nick Van den Bleeken
R&D Manager

Phone: +32 3 425 41 02
Office fax: +32 3 821 01 71

Inventive Designers' Email Disclaimer:

(image/png attachment: 01-part)

(image/png attachment: 02-part)

(image/png attachment: 03-part)

Received on Wednesday, 18 April 2012 14:18:18 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:14:06 UTC