Only the last bind element is considered because all bindings are defined for the very same node set.
This particular file had something than others don't: CSS comments. Just remove comments or make it as in the XML way (<!-- A comment! -->). But for some reason, any image referenced is not loaded......
xml,xpath,rdf,xforms,xsltforms
At present, the default URIs are all coming from the same namespace (http://id.loc.gov/vocabulary/...), so a temporary solution is just to filter for that value: not(starts-with(@rdf:resource, 'http://id.loc.gov/vocabulary/geographicAreas/')). For the longer term, I'm investigating nomisma.org, which embodies a more sustainable approach to linked data vocab management in XForms. <?xml version="1.0" encoding="UTF-8"?> <?xml-stylesheet...
xml,checkbox,xforms,exist-db,xsltforms
I finally figured out that I just needed a nested xf:repeat to iterate through the set of records. I think my problem stemmed from a confusion about the functionality of the xf:bind element, which I ended up removing. With this revised form structure, the value of each @sru:test attributes now...
Just had to copy the main data model definition in the subform. I checked if another cloned model is made, but no, everything went ok!
It is a major feature of XForms to consider properties, such as readonly, at data level not at control level. So, this has to be decided with a binding within the model. The CSS class xforms-readonly is automatically associated/removed by XSLTForms according to the effective status of the corresponding node....
You have two options: Disable the Delete button when only one item remains. The XForms Wikibook shows how: http://en.wikibooks.org/wiki/XForms/Disable_Trigger Set the origin of the rows to a different instance, not to the last row of the repeat. Read this article to see how: http://en.wikibooks.org/wiki/XForms/Insert_with_Origin HTH!...
Write this in xforms header and remove the <css></css> tags at the beggining and at the end of the file (for pre-processor) <?css-conversion no?> ...
The solution was comment a line in the setView: function (center, zoom, options), allowing the _resetView method to refresh: if (animated) { clearTimeout(this._sizeTimer); /*return this;*/ } I also had to comment this line in order to drag and drop with no problems: /*if (L.DomUtil.hasClass(this._element, 'leaflet-zoom-anim')) { return; }*/ ...
Duw to limitations in browsers, it's not possible to use the POST method and replace="all" in XSLTForms. Instead, you must use method="xml-urlencoded-post", this is a hack that only works for XSLTForms. You won't get a pure XML body in your server, but it'll be in a form field called postdata...
There were no problem at all with manipulating the instance structure through javascript. The problem was due to binding declarations that I used in subform to block the user to modify manually the data. E.g. <xf:bind nodeset="/application/params/param[@id='id']" readonly="true()" /> <xf:bind nodeset="/application/params/param[@id='description']" readonly="true()" /> I removed that and everything went ok,...
XSLTForms does not support XForms repeat attributes but XForms repeat elements which can also be used with HTML tables. Implementing them should not be difficult, users did not yet ask for them actually!
There is a namespace issue for your instances: default namespace is HTML. Please try again adding xmlns="" within them.
You should give a try to dialog which is a new feature in XForms 2.0 which is already partially supported in XSLTForms.
There is no evaluate function in XPath 1.0 but, as a workaround, if the variable part of the expression is limited, you can always use just a predicate to select the corresponding element such as in /tmp/*[name() = substring-after(/tmp/configuration/@uri, '/tmp/)].