I am trying to use XBL to create an address component. I appreciate some help with what I am doing:
in address_test.html
..
<link rel="bindings" href="my-bindings.xml" />
..
<xf:input ref="my_address" appearance="address">
<xf:label>customer address:</xf:label>
</xf:input>
..
in my-bindings.xml:
<?xml version="1.0" encoding="UTF-16"?>
<bindings xmlns="http://www.x-port.net/bindingresolver/" xmlns:xf="http://www.w3.org/2002/xforms">
<binding match="xf:input[@appearance='address']/xf:pe--value" binding="library.xbl" />
</bindings>
in library.xbl
<?xml version="1.0"?>
<bindings xmlns="http://www.mozilla.org/xbl"
xmlns="http://www.x-port.net/bindingresolver/"
xmlns:xf="http://www.w3.org/2002/xforms">
<binding id="address">
<content>
<xf:input label="Address1"/>
<xf:input label="Address2"/>
<xf:input label="City"/>
<xf:input label="Postcode"/>
</content>
</binding>
</bindings>
The web browser doesn't even go "xforms" mode - so I am not pulling the "custom component" (to use the phrase loosely!) into the document at all - "View Source" in IE shows the html as it is - no "include" behaviour has taken place.
I have tried using the XInclude method too but without any joy either. XBL is the way I am supposed to go - but it just ain't going!
Cheers
Hi Terry, In the current
Hi Terry,
In the current version of formsPlayer, I think that only
xf:outputworks with XBL. It works on all controls in a prototype version we had called formsPlayer 2, but that code hasn't been completely backported yet. We will be adding the remaining controls soon, but we're pretty busy on other things at the moment.However, I thank that using
xf:outputfor now should be good enough for you to get the principles working. So try changing the input to an output, which refers to the parent of all the address items and see how you get on.One thing I would say though is that it would be best to ensure that you have full controls when doing this, just so that you can be sure that things are being expanded correctly. So for example, I would add the
xf:labels to each of your input controls, as well as the closing tags.(Note that you won't see the changes to the document when you do 'view source', but you will if you use a debugging tool to navigate the DOM.)
Regards,
Mark
--
Mark Birbeck, formsPlayer
http://www.formsPlayer.com | http://internet-apps.blogspot.com
standards. innovation.