Alain Couthures

Since XSLTForms 1.5, there is a notation with xforms-* element to directly write forms within HTML pages without having to apply an XSLT transformation first. It is not mandatory: it is still possible to apply the modified XSLT stylesheet included in the recent releases. When migrating from older XSLTForms, old CSS rendering should probably be reconsidered because the new default rendering is different and it is defined for the xforms-* elements instead of old CSS classes on div or span elements....

Since XSLTForms 1.5, there is a notation with xforms- element to directly write forms within HTML pages without having to apply an XSLT transformation first. It is not mandatory: it is still possible a apply the modified XSLT stylesheet included in the recent releases. When migrating from older XSLTForms, old CSS rendering should probably be reconsidered because the new default rendering is different and it is defined for the xforms- elements instead of old CSS classes on div or span elements. About...

Hello Ian, The calculate MIP is to be used to compute a value to be stored in a node. For just rendering expression values, xf:output/@value is more appropriate. Concerning the namespace used in data, as in XSLT or XQuery, XForms allows you to define your own prefix for the form to be used in XPath expressions (there is not a good namespace support in Mozilla Firefox so an extra attribute is used as a workaround for XSLTForms). To reduce XPath expressions length, it is possible to embed bindings...

Hello Josselin, It is currently not possible with XSLTForms to put the same submission more than once in asynchronous mode while the previous one is not yet finished. As a workaround, I suggest you to add "mode='synchronous'" to your submission declarations. Thank you for your feedback! --Alain

Hello Josselin, It is currently not possible with XSLTForms to put the same submission more than once in asynchronous mode while the previous one is not yet finished. As a workaround, I suggest you to add "mode='asynchronous'" to your submission declarations. Thank you for your feedback! --Alain

Hi Luis, This might not be as easy as it seems to implement this with XForms. First, I would use select/itemset/copy to always have a copy of each set of selected items somewhere in a work instance. Then, each trigger should copy the corresponding selected items using insert at the end of the targeted select. Please have a look at https://www.w3.org/community/xformsusers/wiki/XForms_2.0#The_insert_Element for more details. Finally, deleting the inserted copy should be enough to refresh the initial...

Hello Dmitrii, Using a local HTTP server is now the unique solution I see to effectively save a file locally from any browser. It is very easy to write a basic HTTP server with just Nodejs. It is a possible workaround for you? I am also working on an XQuery engine, named "Fleur", which can operate as an HTTP server with Nodejs. For example, I use it locally everyday to serve XSLTForms files and test files. It is not yet supporting PUT, POST or DELETE methods but it should be very easy to add them......

XSLTForms 1.2