Gary,
My perspective as an XForms user: XQuery is designed for querying and
working with document structures, which makes it a great fit for
declarative client-side DOM manipulation--as I recall, the XQuery
implementation in Fleur.js lets users manipulate the HTML5 DOM directly
(even though it's n
Thanks, Alain. Your explanation is very helpful, and thought-provoking. I
imagine other new outsiders will also find it helpful.
A question, if you will indulge someone that doesn’t fully understand the
XForms technology landscape yet. Why do we need a new XQuery engine? I believe
XQuery on
Tim,
Since XSLTForms 1.5, repeats within tables are converted into attributes ("xf-repeat-ref" or "xf-repeat-bind") without adding potentially missing tbody elements.
XSLTForms 1.5.4 now supports table/xf:repeat, not just tbody/xf:repeat.
When developing web applications, XForms, because it has been specified to be implemented in browsers, is not enough.
XSLTForms is a client-side XForms implementation using XSLT 1.0 as a trick to transform XForms pages into HTML pages with CSS and _javascript_. It wo
It's heading in the direction of XForms 2, adding new features at each
release I guess. The most important one implemented is Attribute Value
Templates.
Steven
On Monday 29 March 2021 23:00:43 (+02:00), Gary Kopp wrote:
Does xsltforms 1.5.x support the XForms 2.0 spec, or am I still limit
