#xsltforms search results
Update! Stand-alone #xforms in single HTML file which can save itself with user-modified data for #xsltforms next release
Thinking about defining <xforms:template> for next #xsltforms release #xforms
Hello World! from the #html custom elements for #xforms of #xsltforms 1.5 :-)
Stand-alone #xforms in single HTML file with open/save files capability for #xsltforms next release
#markdown now supported for outputs and labels in #xsltforms #xforms :
@wsalesky, did you ever integrate drag & drop functionality with #XSLTForms?
Next #XSLTForms release will use web components (with workarounds for IE11 and Edge) #xforms:
Custom mips to be added to #xsltforms? Not just strings but atomic values from XPath expressions declared within xf:bind with dedicated namespace meta:name and read with meta(node?, 'name')... #xforms
Next #xsltforms release: Please give it a try! Performance improvements with an html5 notation and easier CSS styling sourceforge.net/p/xsltforms/ma… #xforms
@AlainCouthures I see that the debugger has changed in the latest version of #XSLTForms. Is there still a way to open the separate profiler form in a new tab, as before? Thanks!
When I run wolf.xqy, #xsltforms complains that "match" (used in the xf:bind expression) is not defined. Also, fn:doc only seems to resolve for me if I replace the relative path in the let clause with an absolute path.
#xforms as #html5 custom elements (<xforms-input ref="..."/>) but not in IE: eval() is divine for class declarations! #xsltforms
For #xsltforms, it will just be a way to mention the corresponding #xforms element name for the added SVG grouping element, data-* not being an SVG thing either...
HTML5 custom elements for #xforms: name conflicts for boolean attributes (selected="false" treated as selected="true"!). Renaming rule required! #xsltforms
Vanilla Javascript is well supported ;) and I now consider adding attributes (data-* or xf-*) more convenient than manipulating numerous CSS classes. Attribute selectors can, then, be used for styling with CSS... #xforms #xsltforms
Looking for the best way to offer a preview of XML instance in XSLTForms. When I open the instance in the browser, even with the correct headings, I am getting a HTML rendering. #XForms #XSLTForms
For #xforms, #xsltforms 1.5 won't use shadowDOM so it won't break a11y, it will add "is" attribute within SVG and all resulting HTML custom elements will be prefixed with "xforms-" instead of "xforms:"
So, web components • break a11y • break progressive enhancement (no SSR, broken without JS) • don't work with SVG • share a global namespace instead of being modular • ... Imagine how much tedious moralising we'd see if JS frameworks shipped with similar limitations
Thinking about extending #xforms select control to allow editing controls per item for full appearance: a sort of #xforms repeat where items can also be selected! #xsltforms
Adding support for comments in #json project files for #xsltforms and #fleur was the least I had to do for blaming me for non-XML notation use...
Well, I now have my first standalone #xforms in a single HTML page! I need more testing and I will commit the next #xsltforms release.
@wsalesky, did you ever integrate drag & drop functionality with #XSLTForms?
Looking for the best way to offer a preview of XML instance in XSLTForms. When I open the instance in the browser, even with the correct headings, I am getting a HTML rendering. #XForms #XSLTForms
Well, I now have my first standalone #xforms in a single HTML page! I need more testing and I will commit the next #xsltforms release.
Update! Stand-alone #xforms in single HTML file which can save itself with user-modified data for #xsltforms next release
Stand-alone #xforms in single HTML file with open/save files capability for #xsltforms next release
@AlainCouthures I see that the debugger has changed in the latest version of #XSLTForms. Is there still a way to open the separate profiler form in a new tab, as before? Thanks!
J’allais presque oublier l’excellente spécification #xforms et le non moins fabuleux #XSLTForms d’@alainCouthures qui nous ont été si utiles cette année.
Vanilla Javascript is well supported ;) and I now consider adding attributes (data-* or xf-*) more convenient than manipulating numerous CSS classes. Attribute selectors can, then, be used for styling with CSS... #xforms #xsltforms
Custom mips to be added to #xsltforms? Not just strings but atomic values from XPath expressions declared within xf:bind with dedicated namespace meta:name and read with meta(node?, 'name')... #xforms
Thinking about extending #xforms select control to allow editing controls per item for full appearance: a sort of #xforms repeat where items can also be selected! #xsltforms
My own projects with #xsltforms used to work with PHP servers. Now, they work preferably with NodeJS, as it is now for both #xsltforms and #fleur development environment. #xforms
The latest on #XForms (#XSLTForms) development. @stevenpemberton and @AlainCouthures: (Re)presentation in XForms youtu.be/PiLxYieKdmg
youtube.com
YouTube
17. Steven Pemberton (CWI) and Alain Couthures (AgenceXML): (Re)pre...
Next #xsltforms release: Please give it a try! Performance improvements with an html5 notation and easier CSS styling sourceforge.net/p/xsltforms/ma… #xforms
HTML5 custom elements for #xforms: name conflicts for boolean attributes (selected="false" treated as selected="true"!). Renaming rule required! #xsltforms
For #xsltforms, it will just be a way to mention the corresponding #xforms element name for the added SVG grouping element, data-* not being an SVG thing either...
For #xforms, #xsltforms 1.5 won't use shadowDOM so it won't break a11y, it will add "is" attribute within SVG and all resulting HTML custom elements will be prefixed with "xforms-" instead of "xforms:"
So, web components • break a11y • break progressive enhancement (no SSR, broken without JS) • don't work with SVG • share a global namespace instead of being modular • ... Imagine how much tedious moralising we'd see if JS frameworks shipped with similar limitations
Adding support for comments in #json project files for #xsltforms and #fleur was the least I had to do for blaming me for non-XML notation use...
Hello World! from the #html custom elements for #xforms of #xsltforms 1.5 :-)
Thinking about defining <xforms:template> for next #xsltforms release #xforms
#xforms as #html5 custom elements (<xforms-input ref="..."/>) but not in IE: eval() is divine for class declarations! #xsltforms
First component now working in #xsltforms: based on subform mechanism with 2 extra functions and 1 extra mip #xforms
Something went wrong.
Something went wrong.
United States Trends
- 1. #Worlds2025 46.3K posts
- 2. Doran 19K posts
- 3. #T1WIN 29.4K posts
- 4. Good Sunday 47K posts
- 5. Faker 33.1K posts
- 6. Sam Houston 1,622 posts
- 7. Oregon State 4,750 posts
- 8. #T1fighting 3,621 posts
- 9. Vergil 8,807 posts
- 10. Boots 30K posts
- 11. Option 2 4,360 posts
- 12. Lubin 5,922 posts
- 13. #Toonami 2,731 posts
- 14. Keria 11.4K posts
- 15. Hyan 1,490 posts
- 16. Frankenstein 127K posts
- 17. Louisville 14.5K posts
- 18. UCLA 7,841 posts
- 19. #GoAvsGo 1,607 posts
- 20. Oilers 5,382 posts