Recent changes to Binding

WikiPage Binding modified by aappddeevv

aappddeevv — Sun, 25 Nov 2012 17:56:26 -0000

--- v2
+++ v3
@@ -8,5 +8,7 @@
 
 * path specification: Once a source for the binding is identified, the "path" to the property has to be setup. There is a general object graph syntax for that.
 
+* data conversion: XIML already has type conversion built into it so this mechanism will be employed to handle type conversion where needed between binding data.
+
 
 More details on the binding will be forthcoming but generally speaking, the binding will use POJO objects to manage the binding and ensure it happens in a vocabulary specific way.

WikiPage Binding modified by aappddeevv

aappddeevv — Sun, 25 Nov 2012 17:54:50 -0000

--- v1
+++ v2
@@ -1,6 +1,6 @@
 It would be nice to have a general purpose binding facility in XIML that allows the vocabulary specific binding support to be engaged underneath. To do this, binding is separated out into a few parts:
 
-* binding source: The source of the binding must be looked up. This can be a static resource, another element or a default place to look for an object to bind to.
+* binding source: The source of the binding must be looked up. This can be a static resource, another element (a relative resource) or a default place to look for an object to bind to.
 
 * binding object: XIML does not provide any machinery for the actual binding, just machinery to manage it generically and let the vocabulary handle it underneath. The binding object is really a binding manager object.

WikiPage Binding modified by aappddeevv

aappddeevv — Sun, 25 Nov 2012 17:54:24 -0000

It would be nice to have a general purpose binding facility in XIML that allows the vocabulary specific binding support to be engaged underneath. To do this, binding is separated out into a few parts: * binding source: The source of the binding must be looked up. This can be a static resource, another element or a default place to look for an object to bind to. * binding object: XIML does not provide any machinery for the actual binding, just machinery to manage it generically and let the vocabulary handle it underneath. The binding object is really a binding manager object. * binding context: Since objects that are bound to the same object may have some characteristics that need to be shared, such as unbinding all at once when necessary, some binding context information is created. * path specification: Once a source for the binding is identified, the "path" to the property has to be setup. There is a general object graph syntax for that. More details on the binding will be forthcoming but generally speaking, the binding will use POJO objects to manage the binding and ensure it happens in a vocabulary specific way.