xsltforms-support Mailing List for XSLTForms (Page 4)
Brought to you by:
alain-couthures
Menu
▾
▴
xsltforms-support — XSLTForms support list
You can subscribe to this list here.
| 2009 |
Jan
|
Feb
|
Mar
|
Apr
(1) |
May
(6) |
Jun
(9) |
Jul
(16) |
Aug
(5) |
Sep
(43) |
Oct
(36) |
Nov
(58) |
Dec
(43) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2010 |
Jan
(79) |
Feb
(81) |
Mar
(107) |
Apr
(93) |
May
(85) |
Jun
(54) |
Jul
(64) |
Aug
(54) |
Sep
(45) |
Oct
(53) |
Nov
(34) |
Dec
(77) |
| 2011 |
Jan
(56) |
Feb
(53) |
Mar
(52) |
Apr
(66) |
May
(44) |
Jun
(16) |
Jul
(28) |
Aug
(5) |
Sep
(15) |
Oct
(21) |
Nov
(51) |
Dec
(46) |
| 2012 |
Jan
(16) |
Feb
(38) |
Mar
(47) |
Apr
(45) |
May
(41) |
Jun
(41) |
Jul
(72) |
Aug
(17) |
Sep
(10) |
Oct
(16) |
Nov
(29) |
Dec
(30) |
| 2013 |
Jan
(25) |
Feb
(13) |
Mar
(20) |
Apr
(25) |
May
(34) |
Jun
(8) |
Jul
(12) |
Aug
(9) |
Sep
(21) |
Oct
(19) |
Nov
(6) |
Dec
(2) |
| 2014 |
Jan
(14) |
Feb
(8) |
Mar
(7) |
Apr
(13) |
May
(33) |
Jun
(13) |
Jul
(6) |
Aug
(5) |
Sep
(5) |
Oct
(34) |
Nov
(7) |
Dec
|
| 2015 |
Jan
(1) |
Feb
(6) |
Mar
(17) |
Apr
(12) |
May
(10) |
Jun
(18) |
Jul
(31) |
Aug
(9) |
Sep
(3) |
Oct
(6) |
Nov
(19) |
Dec
(1) |
| 2016 |
Jan
(18) |
Feb
(4) |
Mar
(13) |
Apr
(19) |
May
|
Jun
(17) |
Jul
(7) |
Aug
|
Sep
(3) |
Oct
(6) |
Nov
(3) |
Dec
|
| 2017 |
Jan
(5) |
Feb
(17) |
Mar
(4) |
Apr
(8) |
May
(3) |
Jun
|
Jul
(8) |
Aug
(2) |
Sep
|
Oct
(5) |
Nov
(6) |
Dec
(4) |
| 2018 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(6) |
Nov
|
Dec
(1) |
| 2019 |
Jan
|
Feb
|
Mar
(4) |
Apr
(2) |
May
(4) |
Jun
|
Jul
|
Aug
(2) |
Sep
(7) |
Oct
|
Nov
|
Dec
|
| 2020 |
Jan
(13) |
Feb
(17) |
Mar
(8) |
Apr
(11) |
May
(15) |
Jun
(11) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(6) |
| 2021 |
Jan
(9) |
Feb
(26) |
Mar
(17) |
Apr
|
May
(7) |
Jun
(18) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(10) |
| 2022 |
Jan
|
Feb
(1) |
Mar
|
Apr
|
May
(3) |
Jun
|
Jul
|
Aug
(2) |
Sep
(3) |
Oct
(2) |
Nov
(10) |
Dec
(1) |
| 2023 |
Jan
(10) |
Feb
|
Mar
(7) |
Apr
(8) |
May
(3) |
Jun
|
Jul
|
Aug
|
Sep
(8) |
Oct
(11) |
Nov
(8) |
Dec
(5) |
| 2024 |
Jan
(7) |
Feb
(3) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2025 |
Jan
(4) |
Feb
(2) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Robert K. <ro...@er...> - 2023-01-05 14:42:50
|
Hello, I unsuccessfully tried to run the following Wiki book <https://en.wikibooks.org/wiki/XForms/Message_Types> example. Event trapping and message modes do not work as expected (using Chrome). Here-attached is my use case, derived from the wiki with corrections of the missing bindings Best regards. Robert. |
|
From: Alain C. <ala...@ag...> - 2022-12-08 20:42:58
|
<!doctype html> <html> <head> <meta charset="UTF-8"> </head> <body> <div> Hello Tim, </div> <div class="default-style"> </div> <div class="default-style"> The next XSLTForms release will improve autofill support by automatically adding an embedding HTML "form" element and accepting the HTML "autocomplete" attribute for XForms input controls. </div> <div class="default-style"> </div> <div class="default-style"> Nevertheless, autofill is not a trusted action and it is not possible to manipulate such values until an user interaction. </div> <div class="default-style"> </div> <div class="default-style"> There is a Javascript API to store credentials but it is not supported yet by neither Firefox nor Safari (<a href="https://developer.mozilla.org/fr/docs/Web/API/PasswordCredential">https://developer.mozilla.org/fr/docs/Web/API/PasswordCredential</a>). I would like to have a look at your sign-in form to analyze when it should be called (according to @replace=all, I presume). </div> <div class="default-style"> </div> <div class="default-style"> Thanks in advance, </div> <div class="default-style"> </div> <div class="default-style"> --Alain </div> <blockquote type="cite"> <div> Le 16/08/2022 19:57 CEST, Alain Couthures <ala...@ag...> a écrit : </div> <div> </div> <div> </div> <div> Hello Tim, </div> <div class="default-style"> </div> <div class="default-style"> As usual, events are not fired similarly in these browsers. </div> <div class="default-style"> </div> <div class="default-style"> I already have a possible fix but for Firefox only. </div> <div class="default-style"> </div> <div class="default-style"> I will investigate some CSS trick to detect autofill for Chromium browsers. </div> <div class="default-style"> </div> <div class="default-style"> It would also be nice if the browser could suggest by itself to save user/password for next times... </div> <div class="default-style"> </div> <div class="default-style"> Are you in a hurry? Are you already using the latest XSLTForms release? </div> <div class="default-style"> </div> <div class="default-style"> --Alain </div> <blockquote type="cite"> <div> Le 06/08/2022 03:00 CEST, Tim Thompson <tim...@gm...> a écrit : </div> <div> </div> <div> </div> <div dir="ltr"> <div> Hello, </div> <div> </div> <div> I have a form with login and password fields. Using Firefox, if I save the login information in the browser password manager and then reload the form, the saved login information--which is prepopulated in the input fields--is not automatically bound to my XForms instance. </div> <div> </div> <div> Using Chrome, the prepopulated login information becomes bound once I click into the page. </div> <div> </div> <div> Is it possible to force a refresh of the saved login information, or to achieve a consistent cross-browser behavior? </div> <div> </div> <div> Thanks in advance, </div> <div> Tim </div> <div> </div> <div> </div> <div> <div> <div class="gmail_signature" dir="ltr" data-smartmail="gmail_signature"> <div dir="ltr"> -- <br>Tim A. Thompson (he, him) <br>Librarian for Applied Metadata Research <br>Yale University Library <br> <br> </div> </div> </div> </div> </div> _______________________________________________ Xsltforms-support mailing list Xsl...@li... https://lists.sourceforge.net/lists/listinfo/xsltforms-support </blockquote> </blockquote> </body> </html> |
|
From: Alain C. <ala...@ag...> - 2022-11-29 18:02:45
|
<!doctype html>
<html>
<head>
<meta charset="UTF-8">
</head>
<body>
<div>
Hello Habs,
</div>
<div class="default-style">
</div>
<div class="default-style">
Thank you for reporting this issue.
</div>
<div class="default-style">
</div>
<div class="default-style">
As a workaround, it is still possible to use an XPath 1.0 extension in XSLTForms: a wildcard for all existing prefixes. In your example, "instance('myinstance')/*:personname" should be evaluated as expected.
</div>
<div class="default-style">
</div>
<div class="default-style">
Kind regards,
</div>
<div class="default-style">
</div>
<div class="default-style">
--Alain
</div>
<blockquote type="cite">
<div>
Le 27/11/2022 20:25 CET, Habs <<a href="mailto:ge...@us...">ge...@us...</a>> a écrit :
</div>
<div>
</div>
<div>
</div>
<div>
Hello Alain, List
</div>
<div>
</div>
<div>
Thank you for the reply Alain (to both quesions) and for your detailed
</div>
<div>
info ... most helpful.
</div>
<div>
</div>
<div>
I understand better now as a result and will explore some more.
</div>
<div>
</div>
<div>
Entering such as this: instance('myinstance') in the debugger console,
</div>
<div>
indeed does reveal the xml (unformatted).
</div>
<div>
</div>
<div>
Now I know that the debigger is an XPath type query engine, I can play
</div>
<div>
around with it.
</div>
<div>
</div>
<div>
Before I 'disappear' for a while to have play, do you have any comment on
</div>
<div>
whether namespaces are handled and if so, how one might enter and XPath
</div>
<div>
for a particular node please ?
</div>
<div>
</div>
<div>
For example, when entering:
</div>
<div>
</div>
<div>
instance('myinstance')/personname
</div>
<div>
</div>
<div>
... this error is produced:
</div>
<div>
</div>
<div>
Error: nsresolver.lookupNamespaceURI is not a function
</div>
<div>
</div>
<div>
</div>
<div>
How would one select 'personname' if the xml instance employs a namespace
</div>
<div>
eg. for the error above, this is the xml:
</div>
<div>
</div>
<div>
<root xmlns="somenamespace">
</div>
<div>
<personname>anon</personname>
</div>
<div>
</root>
</div>
<div>
</div>
<div>
</div>
<div>
Regards
</div>
<div>
Habs
</div>
<div>
</div>
<div>
</div>
<div>
On Sun, 27 Nov 2022, Alain Couthures wrote:
</div>
<div>
</div>
<blockquote type="cite">
<div>
Hello Habs,
</div>
<div>
</div>
<div>
The new debugger console allows you to dynamically evaluate any XPath expressions such as "instance()".
</div>
<div>
</div>
<div>
Extra XPath functions might help debugging (for example, the next XPath/XQuery engine will come with a "instance-ids()" function...). Any idea?
</div>
<div>
</div>
<div>
Kind regards,
</div>
<div>
</div>
<div>
--Alain
</div>
<div>
Le 26/11/2022 18:35 CET, Habs <<a href="mailto:ge...@us...">ge...@us...</a>> a écrit :
</div>
<div>
</div>
<div>
</div>
<div>
sorry List,
</div>
<div>
</div>
<div>
A bit of an update to the last (below) regarding v1.6
</div>
<div>
</div>
<div>
I have noticed that the console/debugger now appears at the bottom when
</div>
<div>
pressing F1, which is different behaviour to previous, where a form was
</div>
<div>
displayed when pressing F1 and where it was possible to select the
</div>
<div>
'profiler' to be able to access instance viewer etc.
</div>
<div>
</div>
<div>
The 'debugger' console at the bottom appears to be waiting for input, but
</div>
<div>
I am unsure what can be entered; especially related to inspecting or
</div>
<div>
getting a copy of the xml document as one could do with the instance
</div>
<div>
viewer.
</div>
<div>
</div>
<div>
It is all a bit unfamiliar to me, sorry. Any insight would be great.
</div>
<div>
</div>
<div>
Thank you
</div>
<div>
Habs
</div>
<div>
</div>
<div>
</div>
<div>
</div>
<div>
---------- Forwarded message ----------
</div>
<div>
Date: Sat, 26 Nov 2022 17:15:52 +0000 (GMT)
</div>
<div>
From: Habs <<a href="mailto:ge...@us...">ge...@us...</a>>
</div>
<div>
To: <a href="mailto:xsl...@li...">xsl...@li...</a>
</div>
<div>
Subject: xsltforms 1.6 - F1 does not display the console
</div>
<div>
</div>
<div>
</div>
<div>
Hello List/Alain
</div>
<div>
</div>
<div>
with xsltforms (1.6) from here (and tried on lastest Chromium and Firefox):
</div>
<div>
</div>
<div>
<a href="https://github.com/AlainCouthures/declarative4all/blob/master/public/direct/xsltforms.zip" target="_blank" rel="noopener">https://github.com/AlainCouthures/declarative4all/blob/master/public/direct/xsltforms.zip</a>
</div>
<div>
</div>
<div>
</div>
<div>
When pressing F1 for the 'console' (to access instance viewer etc) does not
</div>
<div>
reveal anything.
</div>
<div>
</div>
<div>
The previous version (1.5) is fine.
</div>
<div>
</div>
<div>
Incidentally, what/where is the fleur mechanism/code used (or that could be
</div>
<div>
used) to access the instance xml content (that appears in the viewer) ?
</div>
<div>
</div>
<div>
</div>
<div>
Thank you, regards
</div>
<div>
Habs
</div>
<div>
UK
</div>
<div>
</div>
<div>
--- Sent using Alpine/Pine, probably the best MUA ---
</div>
<div>
</div>
<div>
</div>
<div>
</div>
<div>
_______________________________________________
</div>
<div>
Xsltforms-support mailing list
</div>
<div>
<a href="mailto:Xsl...@li...">Xsl...@li...</a>
</div>
<div>
<a href="https://lists.sourceforge.net/lists/listinfo/xsltforms-support" target="_blank" rel="noopener">https://lists.sourceforge.net/lists/listinfo/xsltforms-support</a>
</div>
<div>
</div>
<div>
</div>
</blockquote>
<div>
</div>
<div>
--- Sent using Alpine/Pine, probably the best MUA ---
</div>
</blockquote>
</body>
</html>
|
|
From: Robert K. <ro...@er...> - 2022-11-28 16:24:19
|
Hello list, The basic test here-attached fails to trap the event and run the JScript. Using v1.6 via chrome. TIA for any help. Robert. |
|
From: Habs <ge...@us...> - 2022-11-27 19:25:27
|
Hello Alain, List
Thank you for the reply Alain (to both quesions) and for your detailed
info ... most helpful.
I understand better now as a result and will explore some more.
Entering such as this: instance('myinstance') in the debugger console,
indeed does reveal the xml (unformatted).
Now I know that the debigger is an XPath type query engine, I can play
around with it.
Before I 'disappear' for a while to have play, do you have any comment on
whether namespaces are handled and if so, how one might enter and XPath
for a particular node please ?
For example, when entering:
instance('myinstance')/personname
... this error is produced:
Error: nsresolver.lookupNamespaceURI is not a function
How would one select 'personname' if the xml instance employs a namespace
eg. for the error above, this is the xml:
<root xmlns="somenamespace">
<personname>anon</personname>
</root>
Regards
Habs
On Sun, 27 Nov 2022, Alain Couthures wrote:
> Hello Habs,
>
> The new debugger console allows you to dynamically evaluate any XPath expressions such as "instance()".
>
> Extra XPath functions might help debugging (for example, the next XPath/XQuery engine will come with a "instance-ids()" function...). Any idea?
>
> Kind regards,
>
> --Alain
> Le 26/11/2022 18:35 CET, Habs <ge...@us...> a écrit :
>
>
> sorry List,
>
> A bit of an update to the last (below) regarding v1.6
>
> I have noticed that the console/debugger now appears at the bottom when
> pressing F1, which is different behaviour to previous, where a form was
> displayed when pressing F1 and where it was possible to select the
> 'profiler' to be able to access instance viewer etc.
>
> The 'debugger' console at the bottom appears to be waiting for input, but
> I am unsure what can be entered; especially related to inspecting or
> getting a copy of the xml document as one could do with the instance
> viewer.
>
> It is all a bit unfamiliar to me, sorry. Any insight would be great.
>
> Thank you
> Habs
>
>
>
> ---------- Forwarded message ----------
> Date: Sat, 26 Nov 2022 17:15:52 +0000 (GMT)
> From: Habs <ge...@us...>
> To: xsl...@li...
> Subject: xsltforms 1.6 - F1 does not display the console
>
>
> Hello List/Alain
>
> with xsltforms (1.6) from here (and tried on lastest Chromium and Firefox):
>
> https://github.com/AlainCouthures/declarative4all/blob/master/public/direct/xsltforms.zip
>
>
> When pressing F1 for the 'console' (to access instance viewer etc) does not
> reveal anything.
>
> The previous version (1.5) is fine.
>
> Incidentally, what/where is the fleur mechanism/code used (or that could be
> used) to access the instance xml content (that appears in the viewer) ?
>
>
> Thank you, regards
> Habs
> UK
>
> --- Sent using Alpine/Pine, probably the best MUA ---
>
>
>
> _______________________________________________
> Xsltforms-support mailing list
> Xsl...@li...
> https://lists.sourceforge.net/lists/listinfo/xsltforms-support
>
>
>
--- Sent using Alpine/Pine, probably the best MUA ---
|
|
From: Alain C. <ala...@ag...> - 2022-11-27 10:47:31
|
<!doctype html>
<html>
<head>
<meta charset="UTF-8">
</head>
<body>
<div>
Hello Habs,
</div>
<div class="default-style">
</div>
<div class="default-style">
The new debugger console allows you to dynamically evaluate any XPath expressions such as "instance()".
</div>
<div class="default-style">
</div>
<div class="default-style">
Extra XPath functions might help debugging (for example, the next XPath/XQuery engine will come with a "instance-ids()" function...). Any idea?
</div>
<div class="default-style">
</div>
<div class="default-style">
Kind regards,
</div>
<div class="default-style">
</div>
<div class="default-style">
--Alain
</div>
<blockquote type="cite">
<div>
Le 26/11/2022 18:35 CET, Habs <<a href="mailto:ge...@us...">ge...@us...</a>> a écrit :
</div>
<div>
</div>
<div>
</div>
<div>
sorry List,
</div>
<div>
</div>
<div>
A bit of an update to the last (below) regarding v1.6
</div>
<div>
</div>
<div>
I have noticed that the console/debugger now appears at the bottom when
</div>
<div>
pressing F1, which is different behaviour to previous, where a form was
</div>
<div>
displayed when pressing F1 and where it was possible to select the
</div>
<div>
'profiler' to be able to access instance viewer etc.
</div>
<div>
</div>
<div>
The 'debugger' console at the bottom appears to be waiting for input, but
</div>
<div>
I am unsure what can be entered; especially related to inspecting or
</div>
<div>
getting a copy of the xml document as one could do with the instance
</div>
<div>
viewer.
</div>
<div>
</div>
<div>
It is all a bit unfamiliar to me, sorry. Any insight would be great.
</div>
<div>
</div>
<div>
Thank you
</div>
<div>
Habs
</div>
<div>
</div>
<div>
</div>
<div>
</div>
<div>
---------- Forwarded message ----------
</div>
<div>
Date: Sat, 26 Nov 2022 17:15:52 +0000 (GMT)
</div>
<div>
From: Habs <<a href="mailto:ge...@us...">ge...@us...</a>>
</div>
<div>
To: <a href="mailto:xsl...@li...">xsl...@li...</a>
</div>
<div>
Subject: xsltforms 1.6 - F1 does not display the console
</div>
<div>
</div>
<div>
</div>
<div>
Hello List/Alain
</div>
<div>
</div>
<div>
with xsltforms (1.6) from here (and tried on lastest Chromium and Firefox):
</div>
<div>
</div>
<div>
<a href="https://github.com/AlainCouthures/declarative4all/blob/master/public/direct/xsltforms.zip" target="_blank" rel="noopener">https://github.com/AlainCouthures/declarative4all/blob/master/public/direct/xsltforms.zip</a>
</div>
<div>
</div>
<div>
</div>
<div>
When pressing F1 for the 'console' (to access instance viewer etc) does not
</div>
<div>
reveal anything.
</div>
<div>
</div>
<div>
The previous version (1.5) is fine.
</div>
<div>
</div>
<div>
Incidentally, what/where is the fleur mechanism/code used (or that could be
</div>
<div>
used) to access the instance xml content (that appears in the viewer) ?
</div>
<div>
</div>
<div>
</div>
<div>
Thank you, regards
</div>
<div>
Habs
</div>
<div>
UK
</div>
<div>
</div>
<div>
--- Sent using Alpine/Pine, probably the best MUA ---
</div>
<div>
</div>
<div>
</div>
<div>
</div>
<div>
_______________________________________________
</div>
<div>
Xsltforms-support mailing list
</div>
<div>
<a href="mailto:Xsl...@li...">Xsl...@li...</a>
</div>
<div>
<a href="https://lists.sourceforge.net/lists/listinfo/xsltforms-support" target="_blank" rel="noopener">https://lists.sourceforge.net/lists/listinfo/xsltforms-support</a>
</div>
</blockquote>
</body>
</html>
|
|
From: Alain C. <ala...@ag...> - 2022-11-27 10:37:38
|
<!doctype html>
<html>
<head>
<meta charset="UTF-8">
</head>
<body>
<div>
Hello Habs,
</div>
<div class="default-style">
</div>
<div class="default-style">
First, please let me explain what made a standalone form possible:
</div>
<div class="default-style">
</div>
<div class="default-style">
Because XForms Specifications define their own elements to be mixed within some host language such as HTML, any XForms implementation to be used within a web browser has to HTML elements and attributes. Since XSLTForms 1.5, HTML5 custom elements have replaced plenty of DIVs and SPANs. Such custom elements are immediate images of XForms ones ("xf:*" becoming "xforms-*") but various sub elements had to be been introduced (such as "xforms-body", "xforms-repeat-item", ...) and extra attributes too (such as "xf-bound" which allows CSS styling without Javascript instructions). These sub elements and extra attributes are XSLTForms specific and they are added automatically when constructing the form with Javascript.
</div>
<div class="default-style">
</div>
<div class="default-style">
As a consequence, the new XSLT stylesheet is much lighter and, because XPath parsing is now also performed in Javascript, it is even faster. Because NodeJS is currently used to develop XSLTForms, a Javascript function was easily written to mimic the new transformation from XHTML+XForms to HTML5.
</div>
<div class="default-style">
</div>
<div class="default-style">
This new approach also allows authors to directly write forms in HTML5 pages with an XForms-like syntax so the initial XSLT transformation has not to be performed at client-side (there is always a blank page effect when the browser XSLT engine is running and some browsers don't support XSLT 1.0!) nor at server-side (which has always to be powerful enough for all its clients).
</div>
<div class="default-style">
</div>
<div class="default-style">
BTW, it is now also possible, with Javascript only, to read and write local files with file pickers. So, any machine can store files and open them with a browser. With embedded minified "xsltforms.css" and "xsltforms.js", within an HTML5 page with XSLTForms custom elements, a form can be fully executed locally with its own data. Saving modified instances in local files is an option but it could be required to load them back when using the form again. XSLTForms comes with a specific function named "form-source()" to save the source elements of the form with modified instance data into a standalone file to be reopened later.
</div>
<div class="default-style">
</div>
<div class="default-style">
XSLTForms 1.6 does not include a simple form to load an XForms file, transform it to (X)HTML5+custom elements, and save it as a standalone file. Is it what you are looking for?
</div>
<div class="default-style">
</div>
<div class="default-style">
About your questions:
</div>
<div class="default-style">
</div>
<div class="default-style">
1) A standalone form could, as well, be written in XHTML5. It appears that "document.documentElement.outerHTML" (used by the "form-source()" function) is returning serialized well-formed XML for an XHTML5 page: this should work (not tested)!
</div>
<div class="default-style">
</div>
<div class="default-style">
2) Minified "xsltforms.js" and "xsltforms.css" are, of source, lighter but they could be replaced by original ones. If they are in separate local files, it means that the browser has to load them itself. This has not been tested yet but there might security issues blocking this.
<br>These minified sources have not yet been tested for XHTML insertion and issues about <, > and & characters, or CDATA separators, are surely to be fixed.
</div>
<div class="default-style">
</div>
<div class="default-style">
3) Instance data can be saved, as well, using "resource='file:'" (the Javascript File API does not allow to provide a filename to be used but forces use of file pickers).
</div>
<div class="default-style">
</div>
<div class="default-style">
Kind regards,
</div>
<div class="default-style">
</div>
<div class="default-style">
--Alain
</div>
<blockquote type="cite">
<div>
Le 23/11/2022 20:44 CET, Habs <<a href="mailto:ge...@us...">ge...@us...</a>> a écrit :
</div>
<div>
</div>
<div>
</div>
<div>
hello supportlist, Alain
</div>
<div>
</div>
<div>
re: hello-standalone.htm
</div>
<div>
</div>
<div>
At the moment, I am not understanding well enough the method(s) and
</div>
<div>
technology used to save the whole form in the above example form supplied
</div>
<div>
with 1.6, so please forgive me when I ask the following.
</div>
<div>
</div>
<div>
The example standalone form is HTML (html5).
</div>
<div>
</div>
<div>
The forms I tend to use are XHTML forms (1.0 strict), using the v1.6
</div>
<div>
xsltforms.xsl in a processing instruction at the top (client side
</div>
<div>
transformation) and with the data instance and the styles pulled in from
</div>
<div>
externally linked files. These forms work well.
</div>
<div>
</div>
<div>
1) is it possible to replicate the standalone html form example in an
</div>
<div>
xhtml based form ie. saving the whole xhtml form ?
</div>
<div>
</div>
<div>
2) if the answer to 1) is yes, then is it possible to put the script and
</div>
<div>
style sections in separate files (rather than in the xhtml form file) and
</div>
<div>
if someone has a quick and dirty example that would be excellent ?
</div>
<div>
</div>
<div>
3) out of interest, is it possible to save just the instance data and not
</div>
<div>
the whole form in either the standalone example or in the xhtml ?
</div>
<div>
</div>
<div>
As a test so far, I pinched the 'submission' from the standalone example
</div>
<div>
and hooked it up in an existing xhtml form to a submit button. I was
</div>
<div>
expecting that the necessary functionality used directly coded in the
</div>
<div>
standalone form header, would be in the xsltforms.js via the xsltforms.xsl
</div>
<div>
transform and would therefore work without much alteration of the existing
</div>
<div>
xhtml forms used.
</div>
<div>
</div>
<div>
</div>
<div>
It did not work out, with this error prior to the 'file save' dialogue
</div>
<div>
being shown, where 'saving' saved nothing:
</div>
<div>
</div>
<div>
</div>
<div>
XSLTForms Exception
</div>
<div>
--------------------------
</div>
<div>
</div>
<div>
Error evaluating the following XPath expression :
</div>
<div>
</div>
<div>
form-Source()
</div>
<div>
</div>
<div>
TypeError
</div>
<div>
</div>
<div>
this.compiled is undefined
</div>
<div>
</div>
<div>
</div>
<div>
</div>
<div>
In the interim from sending this message, I will create a simplified
</div>
<div>
bare-bones xhtml and test to see if I can get it to work.
</div>
<div>
</div>
<div>
What I do know already is that the style and script content in the
</div>
<div>
standalone example form, leave the xhtml based form as not well-formed ...
</div>
<div>
even when enclosed in a CDATA block.
</div>
<div>
</div>
<div>
</div>
<div>
Regards
</div>
<div>
Habs
</div>
<div>
</div>
<div>
</div>
<div>
</div>
<div>
--- Sent using Alpine/Pine, probably the best MUA ---
</div>
<div>
</div>
<div>
</div>
<div>
</div>
<div>
_______________________________________________
</div>
<div>
Xsltforms-support mailing list
</div>
<div>
<a href="mailto:Xsl...@li...">Xsl...@li...</a>
</div>
<div>
<a href="https://lists.sourceforge.net/lists/listinfo/xsltforms-support" target="_blank" rel="noopener">https://lists.sourceforge.net/lists/listinfo/xsltforms-support</a>
</div>
</blockquote>
</body>
</html>
|
|
From: Habs <ge...@us...> - 2022-11-26 17:42:15
|
Hello List/Alain with xsltforms (1.6) from here (and tried on lastest Chromium and Firefox): https://github.com/AlainCouthures/declarative4all/blob/master/public/direct/xsltforms.zip When pressing F1 for the 'console' (to access instance viewer etc) does not reveal anything. The previous version (1.5) is fine. Incidentally, what/where is the fleur mechanism/code used (or that could be used) to access the instance xml content (that appears in the viewer) ? Thank you, regards Habs UK --- Sent using Alpine/Pine, probably the best MUA --- |
|
From: Habs <ge...@us...> - 2022-11-26 17:36:10
|
sorry List, A bit of an update to the last (below) regarding v1.6 I have noticed that the console/debugger now appears at the bottom when pressing F1, which is different behaviour to previous, where a form was displayed when pressing F1 and where it was possible to select the 'profiler' to be able to access instance viewer etc. The 'debugger' console at the bottom appears to be waiting for input, but I am unsure what can be entered; especially related to inspecting or getting a copy of the xml document as one could do with the instance viewer. It is all a bit unfamiliar to me, sorry. Any insight would be great. Thank you Habs ---------- Forwarded message ---------- Date: Sat, 26 Nov 2022 17:15:52 +0000 (GMT) From: Habs <ge...@us...> To: xsl...@li... Subject: xsltforms 1.6 - F1 does not display the console Hello List/Alain with xsltforms (1.6) from here (and tried on lastest Chromium and Firefox): https://github.com/AlainCouthures/declarative4all/blob/master/public/direct/xsltforms.zip When pressing F1 for the 'console' (to access instance viewer etc) does not reveal anything. The previous version (1.5) is fine. Incidentally, what/where is the fleur mechanism/code used (or that could be used) to access the instance xml content (that appears in the viewer) ? Thank you, regards Habs UK --- Sent using Alpine/Pine, probably the best MUA --- |
|
From: Habs <ge...@us...> - 2022-11-23 20:14:40
|
hello supportlist, Alain re: hello-standalone.htm At the moment, I am not understanding well enough the method(s) and technology used to save the whole form in the above example form supplied with 1.6, so please forgive me when I ask the following. The example standalone form is HTML (html5). The forms I tend to use are XHTML forms (1.0 strict), using the v1.6 xsltforms.xsl in a processing instruction at the top (client side transformation) and with the data instance and the styles pulled in from externally linked files. These forms work well. 1) is it possible to replicate the standalone html form example in an xhtml based form ie. saving the whole xhtml form ? 2) if the answer to 1) is yes, then is it possible to put the script and style sections in separate files (rather than in the xhtml form file) and if someone has a quick and dirty example that would be excellent ? 3) out of interest, is it possible to save just the instance data and not the whole form in either the standalone example or in the xhtml ? As a test so far, I pinched the 'submission' from the standalone example and hooked it up in an existing xhtml form to a submit button. I was expecting that the necessary functionality used directly coded in the standalone form header, would be in the xsltforms.js via the xsltforms.xsl transform and would therefore work without much alteration of the existing xhtml forms used. It did not work out, with this error prior to the 'file save' dialogue being shown, where 'saving' saved nothing: XSLTForms Exception -------------------------- Error evaluating the following XPath expression : form-Source() TypeError this.compiled is undefined In the interim from sending this message, I will create a simplified bare-bones xhtml and test to see if I can get it to work. What I do know already is that the style and script content in the standalone example form, leave the xhtml based form as not well-formed ... even when enclosed in a CDATA block. Regards Habs --- Sent using Alpine/Pine, probably the best MUA --- |
|
From: Alain C. <ala...@ag...> - 2022-11-13 08:53:00
|
<!doctype html>
<html>
<head>
<meta charset="UTF-8">
</head>
<body>
<div>
Hello Robert,
</div>
<div class="default-style">
</div>
<div class="default-style">
This mailing list has not been replaced. It is effectively not very active currently...
</div>
<div class="default-style">
</div>
<div class="default-style">
--Alain
</div>
<blockquote type="cite">
<div>
Le 10/11/2022 11:41 CET, Robert Kirkpatrick <ro...@er...> a écrit :
</div>
<div>
</div>
<div>
</div>
<div dir="ltr">
This mailing list looks inactive..
<div>
Has it been somehow replaced?
</div>
<div>
Kr,
</div>
<div>
Robert.
</div>
</div> _______________________________________________ Xsltforms-support mailing list Xsl...@li... https://lists.sourceforge.net/lists/listinfo/xsltforms-support
</blockquote>
</body>
</html>
|
|
From: Robert K. <ro...@er...> - 2022-11-10 10:41:46
|
This mailing list looks inactive.. Has it been somehow replaced? Kr, Robert. |
|
From: Robert K. <ro...@er...> - 2022-10-11 09:21:26
|
Sorry, wrong email address.
---------- Forwarded message ---------
From: Robert Kirkpatrick <rob...@gm...>
Date: Tue, Oct 11, 2022 at 11:16 AM
Subject: xforms-repeat-item { display: table-row; }
To: Alain Couthures <ala...@ag...>
Cc: <xsl...@li...>
Hello,
Thank you for your reply to my previous post.
I have updated my case according to your indications (here-attached).
The repeat works now, but the presentation fails to produce the table
layout.
I found the above css directive in xsltforms.css, which prevents the
table-cell display.
I tested by commenting it out, but other issues arise..
Best regards,
TIA,
Robert.
|
|
From: Alain C. <ala...@ag...> - 2022-10-07 13:47:24
|
<!doctype html>
<html>
<head>
<meta charset="UTF-8">
</head>
<body>
<div>
Robert,
</div>
<div class="default-style">
</div>
<div class="default-style">
The attributes @repeat-* are not yet supported in XSLTForms 1.6.
</div>
<div class="default-style">
</div>
<div class="default-style">
As a workaround, it is possible to use xforms:repeat controls and DIV elements instead, with display set to table, table-row or table-cell.
</div>
<div class="default-style">
</div>
<div class="default-style">
Concerning your example, the XPath expression "game/row" is not returning any node because the evaluation context is "game".
</div>
<div class="default-style">
</div>
<div class="default-style">
Best regards,
</div>
<div class="default-style">
</div>
<div class="default-style">
--Alain
</div>
<blockquote type="cite">
<div>
Le 27/09/2022 16:44 CEST, Robert Kirkpatrick <ro...@er...> a écrit :
</div>
<div>
</div>
<div>
</div>
<div dir="ltr">
The attached sample does not process xf tags: repeat ignored, empty submit button.
<div>
</div>
<div>
I include the xslt result caught by Chrome. It seems that some generated scripts are missing (by comparison to agencexml <em>hello world</em>).
</div>
<div>
</div>
<div>
TIA,
</div>
<div>
Robert.
</div>
</div> _______________________________________________ Xsltforms-support mailing list Xsl...@li... https://lists.sourceforge.net/lists/listinfo/xsltforms-support
</blockquote>
</body>
</html>
|
|
From: Robert K. <ro...@er...> - 2022-09-27 15:47:42
|
Retry in text format, sorry. On Tue, Sep 27, 2022 at 5:25 PM Robert Kirkpatrick <ro...@er...> wrote: > I repost the second attachment, missing. > > On Tue, Sep 27, 2022 at 4:44 PM Robert Kirkpatrick <ro...@er...> > wrote: > >> The attached sample does not process xf tags: repeat ignored, empty >> submit button. >> >> I include the xslt result caught by Chrome. It seems that some generated >> scripts are missing (by comparison to agencexml *hello world*). >> >> TIA, >> Robert. >> > |
|
From: Robert K. <ro...@er...> - 2022-09-27 15:28:07
|
I repost the second attachment, missing. On Tue, Sep 27, 2022 at 4:44 PM Robert Kirkpatrick <ro...@er...> wrote: > The attached sample does not process xf tags: repeat ignored, empty submit > button. > > I include the xslt result caught by Chrome. It seems that some generated > scripts are missing (by comparison to agencexml *hello world*). > > TIA, > Robert. > |
|
From: Robert K. <ro...@er...> - 2022-09-27 15:16:30
|
The attached sample does not process xf tags: repeat ignored, empty submit button. I include the xslt result caught by Chrome. It seems that some generated scripts are missing (by comparison to agencexml *hello world*). TIA, Robert. |
|
From: Alain C. <ala...@ag...> - 2022-08-16 18:10:50
|
<!doctype html>
<html>
<head>
<meta charset="UTF-8">
</head>
<body>
<div>
Hello Tim,
</div>
<div class="default-style">
</div>
<div class="default-style">
As usual, events are not fired similarly in these browsers.
</div>
<div class="default-style">
</div>
<div class="default-style">
I already have a possible fix but for Firefox only.
</div>
<div class="default-style">
</div>
<div class="default-style">
I will investigate some CSS trick to detect autofill for Chromium browsers.
</div>
<div class="default-style">
</div>
<div class="default-style">
It would also be nice if the browser could suggest by itself to save user/password for next times...
</div>
<div class="default-style">
</div>
<div class="default-style">
Are you in a hurry? Are you already using the latest XSLTForms release?
</div>
<div class="default-style">
</div>
<div class="default-style">
--Alain
</div>
<blockquote type="cite">
<div>
Le 06/08/2022 03:00 CEST, Tim Thompson <tim...@gm...> a écrit :
</div>
<div>
</div>
<div>
</div>
<div dir="ltr">
<div>
Hello,
</div>
<div>
</div>
<div>
I have a form with login and password fields. Using Firefox, if I save the login information in the browser password manager and then reload the form, the saved login information--which is prepopulated in the input fields--is not automatically bound to my XForms instance.
</div>
<div>
</div>
<div>
Using Chrome, the prepopulated login information becomes bound once I click into the page.
</div>
<div>
</div>
<div>
Is it possible to force a refresh of the saved login information, or to achieve a consistent cross-browser behavior?
</div>
<div>
</div>
<div>
Thanks in advance,
</div>
<div>
Tim
</div>
<div>
</div>
<div>
</div>
<div>
<div>
<div class="gmail_signature" dir="ltr" data-smartmail="gmail_signature">
<div dir="ltr">
--
<br>Tim A. Thompson (he, him)
<br>Librarian for Applied Metadata Research
<br>Yale University Library
<br>
<br>
</div>
</div>
</div>
</div>
</div> _______________________________________________ Xsltforms-support mailing list Xsl...@li... https://lists.sourceforge.net/lists/listinfo/xsltforms-support
</blockquote>
</body>
</html>
|
|
From: Tim T. <tim...@gm...> - 2022-08-06 01:00:43
|
Hello, I have a form with login and password fields. Using Firefox, if I save the login information in the browser password manager and then reload the form, the saved login information--which is prepopulated in the input fields--is not automatically bound to my XForms instance. Using Chrome, the prepopulated login information becomes bound once I click into the page. Is it possible to force a refresh of the saved login information, or to achieve a consistent cross-browser behavior? Thanks in advance, Tim -- Tim A. Thompson (he, him) Librarian for Applied Metadata Research Yale University Library |
|
From: Josselin M. <mor...@gm...> - 2022-05-23 17:28:43
|
Hi Winona,
Did you try the serialize() function with the xf:ouput element ? You could also add a xf:dialog with the serialized view before saving (see sample below)
Best,
Josselin
<?xml-stylesheet href="xsltforms.xsl" type="text/xsl"?>
<html
xmlns="http://www.w3.org/1999/xhtml"
xmlns:xf="http://www.w3.org/2002/xforms"
xmlns:ev="http://www.w3.org/2001/xml-events"
lang="en">
<head>
<title>serialize() with XForms</title>
<xf:model>
<xf:instance>
<foo xmlns="">
<bar/>
</foo>
</xf:instance>
</xf:model>
</head>
<body>
<xf:input ref="bar">
<xf:label>Enter your name</xf:label>
</xf:input>
<xf:trigger>
<xf:label>Save</xf:label>
<xf:action ev:event="DOMActivate">
<xf:show dialog="serializedView"/>
</xf:action>
</xf:trigger>
<xf:dialog id="serializedView">
<xf:output value="serialize(/foo)"/>
<xf:trigger>
<xf:label>Cancel</xf:label>
<xf:hide ev:event="DOMActivate" dialog="serializedView"/>
</xf:trigger>
<xf:submit submission="submit">
<xf:label>Save</xf:label>
</xf:submit>
</xf:dialog>
</body>
</html>
> Le 23 mai 2022 à 15:05, Winona Salesky <wsa...@gm...> a écrit :
>
> Does anyone here have clever way to preview the working XML instance? I would like users to be able to see what the XML content looks like before saving it.
> Thanks!
> -Winona
>
> _______________________________________________
> Xsltforms-support mailing list
> Xsl...@li...
> https://lists.sourceforge.net/lists/listinfo/xsltforms-support
|
|
From: Habs <ge...@us...> - 2022-05-23 15:13:22
|
On Mon, 23 May 2022, Winona Salesky wrote: > Does anyone here have clever way to preview the working XML instance? I > would like users to be able to see what the XML content looks like before > saving it. > Thanks! > -Winona > Hello I'm presuming you have tried 'F1' toggle key when on a form; on which is a button to open the 'profiler' which allows viewing of the 'instance(s)' and shows other bits and pieces. May be in the code that Alain used for it, is the mechanism you could try implement for your use case, if that F1 profiler was a bit too much so to speak. Regards Habs --- Sent using Alpine/Pine, probably the best MUA --- My Tox Messaging Id: 9F10AC64260ADEBAEA017ACB71B7CD2E962596FC4293025C0F79D77FFEB4CE5C7B0BED41D925 Get a client here: https://tox.chat/clients.html |
|
From: Winona S. <wsa...@gm...> - 2022-05-23 13:06:11
|
Does anyone here have clever way to preview the working XML instance? I would like users to be able to see what the XML content looks like before saving it. Thanks! -Winona |
|
From: Alain C. <ala...@ag...> - 2022-02-08 17:17:19
|
<!doctype html> <html> <head> <meta charset="UTF-8"> </head> <body> <div style="" class="default-style"> Hello, </div> <div style="" class="default-style"> <br> </div> <div style="" class="default-style"> XSLTForms 1.6 can now be downloaded at https://github.com/AlainCouthures/declarative4all/raw/master/public/direct/xsltforms.zip. </div> <div style="" class="default-style"> <br> </div> <div style="" class="default-style"> The "file:" scheme is supported in submissions to read and write files locally, thanks to Javascript File System Access API <a href="https://wicg.github.io/file-system-access">https://wicg.github.io/file-system-access</a>. Using this API, XSLTForms will always render File Pickers so providing a filename is useless with it. For browsers not supporting this API, file saving will be similar to file downloading (in Downloads folder by default) and the saved file can be named in the submission. </div> <div style="" class="default-style"> <br> </div> <div style="" class="default-style"> This feature has enabled a new one: a fully functional form can be stored in a single HTML file with minified versions of xsltforms.js an xsltforms.css files embedded. In this situation, config files are not accessed and a internal JSON object is used instead for language translations.The image files have been serialized for the data: scheme. Finally, a new XPath function, named form-source(), is serializing the current form with effective XML instances. </div> <div style="" class="default-style"> <br> </div> <div style="" class="default-style"> As a result, a standalone form can save itself, or in another file, with modified data embedded: it acts as a standalone local web app with just a browser to run it (hello-standalone.htm example). </div> <div style="" class="default-style"> <br> </div> <div style="" class="default-style"> Thank you for your feedback! </div> <div style="" class="default-style"> <br> </div> <div style="" class="default-style"> --Alain </div> </body> </html> |
|
From: Ralph C. <ra...@ra...> - 2021-12-10 00:46:53
|
Hi all, a note on an issue and resolution I've had over the last 24 hours, just for people's info (I know Alain was looking at it earlier as he replied to my Stackoverflow question - I thought it wasn't an XSLTforms issue at the time, but it turns out it sort of is...) I've been operating in an exist-db environment that I have no control of (it's hosted on a Docker and administered - very helpfully - by a university IT department). I was having problems with the v.652 downloaded from sourceforge and was pointed towards the newer stuff going on Alain's Git. For the last few months I have been running v.661 (without problem). However, following an upgrade to my browser yesterday, Chrome stopped rendering all the forms (just white-screen, stalling at the xsl load). It also turned out that Edge and Firefox (both of which had previously worked) had the same behaviour. I know that the upgrade was the main cause, because my laptop (which hadn't updated) continued to render the forms until this morning. However, I suspected the issue lay more with exist-db than with xsltforms directly, but to make sure I covered all bases I upgraded all the docs to v.662. Instantly everything started working again. I'm not familiar enough with the changes between versions to know what has changed and why it suddenly made such a difference, but hopefully this will help some others. Cheers Ralph |
|
From: Ralph C. <ra...@ra...> - 2021-12-06 11:19:45
|
That explains it, thanks! Ralph On 06/12/2021 09:57, Steven Pemberton wrote: > On Sun, 05 Dec 2021 22:02:50 +0100, Ralph Corrigan <ra...@ra...> wrote: > >> You're absolutely right about the dummy namespace: I can't think of any reason why that would be a useful feature to introduce. > > So it will work in Firefox is the answer I believe. > > Steven |
97 messages has been excluded from this view by a project administrator.
