xsltforms-support Mailing List for XSLTForms (Page 10)
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: Alessandro <ca...@tu...> - 2020-03-12 16:25:48
|
Dear all, in passing from betterforms to xsltforms, now I have a very nice xsltform obtained through an xquery file of the following structure: xquery version "3.0"; let $form := <html xmlns="http://www.w3.org/1999/xhtml" xmlns:xf="http://www.w3.org/2002/xforms"> ....... </html> let $xslt-pi := processing-instruction xml-stylesheet {'type="text/xsl" href="../xsltforms/xsltforms.xsl"'} return ($xslt-pi,$form) I use the form for displaying a list inside a table which new rows can be added to (or deleted from). Everything works the right way, except that after changes have been applied, there's no way of obtaining a working refresh of the form (not even by closing and re-starting the browser!). A problem that by contrast does not arise with .html files... As an alternative I have tryed to put the whole xq file code inside an Xquery function, in order to call the fanction from within an html file which could take advantage of exist-db templating system. But things do not work either (I guess it is not possible to create an xsltform inside an html file). It might be this is an issue that should be more properly reported to the exist-db mailing list, but for sure with betterforms the refresh was not a problem while using .xq files for creating forms.Best regardsAlex -- Inviato in modo sicuro con Tutanota. Ottieni la tua mailbox crittografata e senza pubblicità: https://tutanota.com |
|
From: Alessandro <ca...@tu...> - 2020-03-11 19:54:14
|
Hi Tim, many thanks, you were right! It was enough to substitute "node" with "ref" and data appeared. I was misguided by porting code from working betterforms to xsltforms... Cheers Alex -- Inviato in modo sicuro con Tutanota. Ottieni la tua mailbox crittografata e senza pubblicità: https://tutanota.com |
|
From: Tim T. <tim...@gm...> - 2020-03-11 16:09:06
|
Hi, Alex,
Are you sure that the data is not being loaded at all into the
xforms:instance? The xforms:group element takes a single-node binding, so
@nodeset is not a valid attribute for xforms:group (should be @ref or
@bind).
If you're able to share sample data, I'd be happy to test the form (I don't
have eXist set up, but could try in BaseX).
Best,
Tim
--
Tim A. Thompson
Discovery Metadata Librarian
Yale University Library
On Wed, Mar 11, 2020 at 9:12 AM Alessandro via Xsltforms-support <
xsl...@li...> wrote:
> Hi all,
> in passing from eXist-db 3.6 to 5.2 I'm adapting the code of my previous
> BetterFORMS to XSLTForms. At the moment I'm trying to use xsltforms1.3, but
> also the following minimal code does not seem to work. Data are not loaded,
> despite any attempt of modifying the syntax of scr="" or node=""...
>
> After referencing the data xml file through $file within the model, a list
> of "categorie" should be listed by referencing the parent node ("legenda")
> containing the list (within the "xforms:group") and the final single nodes
> "categoria" (within the "xforms:repeat"). What's wrong with this structure?
> Many thanks
> Alex
>
> xquery version "3.0";
>
> import module namespace my_funcs="http://www.my_funcs.net" at
> "modules/my_app_functions_2.xql";
>
> declare variable $app_collection := 'resources/data';
>
> declare variable $fold_id := request:get-parameter("f_id", "");
> declare variable $tab_id := request:get-parameter("t_id", "");
> declare variable $table_title := request:get-parameter('t_title', '');
> declare variable $arch_id := request:get-parameter("arch_id", "");
>
> let $login := xmldb:login($app_collection, 'admin', 'XXX')
>
> let $file := concat($app_collection, '/', $my_funcs:my_archive)
>
> let $form :=
> <html xmlns="http://www.w3.org/1999/xhtml" xmlns:xforms="
> http://www.w3.org/2002/xforms" xmlns:ev="http://www.w3.org/2001/xml-events"
> xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:xsi="
> http://www.w3.org/2001/XMLSchema-instance">
> <head>
> <link rel="stylesheet" type="text/css"
> href="resources/css/list_forms.css"/>
> <style type="text/css">
> <![CDATA[
>
> ]]>
> </style>
>
> <xforms:model>
> <xforms:instance id="my-category-list" src="{$file}" xmlns="" />
> </xforms:model>
> </head>
> <body>
> <h1>Categorie per la tabella {$table_title}</h1>
>
> <xforms:group
> nodeset="/archivi/archivio[@id='{$arch_id}']/cartella[@id='{$fold_id}']/tabella[@id='{$tab_id}']/legenda">
> <fieldset>
> <legend>Lista delle categorie attualmente disponibili</legend>
> <div class="header">
> <table border="0">
> <tr>
> <td>
> <div class="leftColumn">Abbreviazione</div>
> </td>
> <td style="width: 220px;"/>
> <td>
> <div class="rightColumn">Nome categoria per
> esteso</div>
> </td>
> </tr>
> </table>
> </div>
>
> <xforms:repeat id="list" nodeset="categoria">
> <table border="0">
> <tr>
> <td>
> <xforms:input ref="@id" class="leftColumn" />
> </td>
> <td style="width: 10px;"/>
> <td>
> <xforms:input ref="text()" class="rightColumn" />
> </td>
> </tr>
> </table>
> </xforms:repeat>
> </fieldset>
>
> </xforms:group>
> </body>
> </html>
> let $xslt-pi := processing-instruction xml-stylesheet {'type="text/xsl"
> href="../xsltforms/xsltforms.xsl"'}
> return ($xslt-pi,$form)
>
>
>
> --
> Inviato in modo sicuro con Tutanota. Ottieni la tua mailbox crittografata
> e senza pubblicità:
> https://tutanota.com
> _______________________________________________
> Xsltforms-support mailing list
> Xsl...@li...
> https://lists.sourceforge.net/lists/listinfo/xsltforms-support
>
|
|
From: Alessandro <ca...@tu...> - 2020-03-11 13:11:32
|
Hi all,
in passing from eXist-db 3.6 to 5.2 I'm adapting the code of my previous BetterFORMS to XSLTForms. At the moment I'm trying to use xsltforms1.3, but also the following minimal code does not seem to work. Data are not loaded, despite any attempt of modifying the syntax of scr="" or node=""...
After referencing the data xml file through $file within the model, a list of "categorie" should be listed by referencing the parent node ("legenda") containing the list (within the "xforms:group") and the final single nodes "categoria" (within the "xforms:repeat"). What's wrong with this structure?
Many thanks
Alex
xquery version "3.0";
import module namespace my_funcs="http://www.my_funcs.net" at "modules/my_app_functions_2.xql";
declare variable $app_collection := 'resources/data';
declare variable $fold_id := request:get-parameter("f_id", "");
declare variable $tab_id := request:get-parameter("t_id", "");
declare variable $table_title := request:get-parameter('t_title', '');
declare variable $arch_id := request:get-parameter("arch_id", "");
let $login := xmldb:login($app_collection, 'admin', 'XXX')
let $file := concat($app_collection, '/', $my_funcs:my_archive)
let $form :=
<html xmlns="http://www.w3.org/1999/xhtml" xmlns:xforms="http://www.w3.org/2002/xforms" xmlns:ev="http://www.w3.org/2001/xml-events" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<head>
<link rel="stylesheet" type="text/css" href="resources/css/list_forms.css"/>
<style type="text/css">
<![CDATA[
]]>
</style>
<xforms:model>
<xforms:instance id="my-category-list" src="{$file}" xmlns="" />
</xforms:model>
</head>
<body>
<h1>Categorie per la tabella {$table_title}</h1>
<xforms:group nodeset="/archivi/archivio[@id='{$arch_id}']/cartella[@id='{$fold_id}']/tabella[@id='{$tab_id}']/legenda">
<fieldset>
<legend>Lista delle categorie attualmente disponibili</legend>
<div class="header">
<table border="0">
<tr>
<td>
<div class="leftColumn">Abbreviazione</div>
</td>
<td style="width: 220px;"/>
<td>
<div class="rightColumn">Nome categoria per esteso</div>
</td>
</tr>
</table>
</div>
<xforms:repeat id="list" nodeset="categoria">
<table border="0">
<tr>
<td>
<xforms:input ref="@id" class="leftColumn" />
</td>
<td style="width: 10px;"/>
<td>
<xforms:input ref="text()" class="rightColumn" />
</td>
</tr>
</table>
</xforms:repeat>
</fieldset>
</xforms:group>
</body>
</html>
let $xslt-pi := processing-instruction xml-stylesheet {'type="text/xsl" href="../xsltforms/xsltforms.xsl"'}
return ($xslt-pi,$form)
--
Inviato in modo sicuro con Tutanota. Ottieni la tua mailbox crittografata e senza pubblicità:
https://tutanota.com
|
|
From: Alain C. <ala...@ag...> - 2020-03-02 14:51:54
|
Hello Tim, Yet another 1.5beta build at www.agencexml.com/1.5beta/xsltforms.zip <http://www.agencexml.com/1.5beta/xsltforms.zip> The main fix in it is about replace=all. There was also an issue about duplicated labels for xf:choices. Thank you again for your contributions! --Alain Le 28/02/2020 à 18:50, Tim Thompson a écrit : > Ah, I see--my mistake. I think I was confused by assuming that the > xf:refresh would inherit a DOMActivate event from the xf:submit button. > > Thanks, > Tim > > -- > Tim A. Thompson > Discovery Metadata Librarian > Yale University Library > > On Fri, Feb 28, 2020 at 11:54 AM Alain Couthures > <ala...@ag... <mailto:ala...@ag...>> > wrote: > > Hello Tim, > > It appears that there is actually no event attached to this > refresh action. The latest 1.5beta build does not support this > situation so a Javascript error occurs (I don't know whether a > warning should be displayed or if it better just to ignore > "unreachable" actions). > > Please try again with an embedding xf:action for xf:setvalue > followed by xf:refresh (which might be useless BTW). > > The next build should just ignore this. > > Thanks! > > --Alain > > > Le 28/02/2020 à 04:16, Tim Thompson a écrit : >> Hello, Alain, >> >> Thanks again for the latest updates! I have another test for you. >> >> Here is my use case: I want to display an ephemeral "Loading" >> message when I trigger a submission. To achieve this, I have an >> instance: >> >> <instance id="state"> >> <data xmlns=""> >> <status loading="false" ready="false">...Loading...</status> >> </data> >> </instance> >> >> When the submission is triggered, I call xf:setvalue to change >> the @loading attribute to "true." This causes the loading message >> to display. When the submission completes, the @loading attribute >> is set to "false" again. >> >> For the value change to take effect, I find that I have to call >> xf:refresh, or else the binding won't be registered. >> >> In the latest version of beta1.5, if I call xf:refresh from >> within an xf:submit element, the following error is thrown. This >> does not occur in XSLTForms 1.4. >> >> XSLTForms Exception >> -------------------------- >> >> Incorrect Javascript code generation: >> >> XsltForms_abstractAction.prototype.init@https://www.tat2.io/basex2/static/xsltforms.js:11252:35 >> XsltForms_dispatch@https://www.tat2.io/basex2/static/xsltforms.js:11462:7 >> anonymous@https://www.tat2.io/basex2/static/xsltforms.js line >> 5740 > Function:3:181 >> schback/<@https://www.tat2.io/basex2/static/xsltforms.js:5759:125 >> schback@https://www.tat2.io/basex2/static/xsltforms.js:5759:66 >> schloader@https://www.tat2.io/basex2/static/xsltforms.js:5780:11 >> XsltForms_class.activateAll@https://www.tat2.io/basex2/static/xsltforms.js:5815:11 >> xsltforms_init@https://www.tat2.io/basex2/static/xsltforms.js:16516:22 >> >> >> TypeError >> >> mainaction.hasAttribute is not a function >> >> However, if I call xf:refresh from within an xforms-submit >> action, no error is thrown. >> >> See examples: >> >> *1. xf:setvalue with xf:refresh inside xf:submit (1.5beta)*: >> https://www.tat2.io/basex2/static/xsltforms_setvalue_refresh_test_2020-02-27_1.5beta.xml >> >> *2. xf:setvalue inside xf:submit, xf:refresh inside xforms-submit >> action (1.5beta):* >> https://www.tat2.io/basex2/static/xsltforms_setvalue_refresh_test_2020-02-27_1.5beta_v2.xml >> >> *3. xf:setvalue with xf:refresh inside xf:submit (1.4):* >> https://www.tat2.io/basex2/static/xsltforms_setvalue_refresh_test_2020-02-27_1.4.xml >> >> >> Best regards, >> Tim >> >> >> -- >> Tim A. Thompson >> Discovery Metadata Librarian >> Yale University Library >> >> On Mon, Feb 17, 2020 at 4:56 PM Tim Thompson <tim...@gm... >> <mailto:tim...@gm...>> wrote: >> >> Thank you, Alain! >> >> If you don't mind, I have another test form that works in >> XSLTForms 1.4 but not 1.5beta. >> >> This one is testing xf:var again. >> >> In 1.5beta, an error is thrown: >> Assertion failed: Binding evaluation didn't returned a >> nodeset but '1' for XPath expression: count(ancestor::item) >> https://www.tat2.io/basex2/static/xsltforms_var_test_2020-02-17_with_var_1.5beta.xml >> >> In 1.4, the form works as expected: >> https://www.tat2.io/basex2/static/xsltforms_var_test_2020-02-17_with_var_1.4.xml >> >> Best regards, >> Tim >> >> >> -- >> Tim A. Thompson >> Discovery Metadata Librarian >> Yale University Library >> >> >> On Mon, Feb 17, 2020 at 3:54 PM Alain Couthures >> <ala...@ag... >> <mailto:ala...@ag...>> wrote: >> >> Hello Tim, >> >> This issue is now fixed (and some more actually...). >> >> The new build can be downloaded at the same URL: >> www.agencexml.com/1.5beta/xsltforms.zip >> <http://www.agencexml.com/1.5beta/xsltforms.zip> >> >> Thank you again for your contributions! >> >> --Alain >> >> Le 15/02/2020 à 01:15, Tim Thompson a écrit : >>> Hello, Alain, >>> >>> Another test for you: >>> >>> In XSLTForms 1.5beta, the DOMActivate event is not being >>> evoked for input controls. See this test form: >>> >>> https://www.tat2.io/basex2/static/xsltforms_DOMActivate_test_2020-02-14_1-5beta.xml >>> >>> Pressing "enter" in the input field does nothing, >>> whereas clicking the button triggers the event. >>> >>> Compare this to a form running XSLTForms 1.4: >>> >>> https://www.tat2.io/basex2/static/xsltforms_DOMActivate_test_2020-02-14_1-4.xml >>> >>> Here, the DOMActivate enter works in both the input >>> field with the "enter" key and with the button. >>> >>> All best, >>> Tim >>> >>> -- >>> Tim A. Thompson >>> Discovery Metadata Librarian >>> Yale University Library >>> >>> On Wed, Feb 12, 2020 at 5:51 PM Tim Thompson >>> <tim...@gm... <mailto:tim...@gm...>> wrote: >>> >>> Great! Works perfectly now. Looking forward to the >>> XML Prague proceedings and video for your >>> presentation with Steven Pemberton. >>> >>> Thanks again, >>> Tim >>> >>> >>> -- >>> Tim A. Thompson >>> Discovery Metadata Librarian >>> Yale University Library >>> >>> >>> >>> On Wed, Feb 12, 2020 at 4:00 PM Alain Couthures >>> <ala...@ag... >>> <mailto:ala...@ag...>> wrote: >>> >>> Hello Tim, >>> >>> (1) The xf:group processing was not correct: in >>> the new approach, an xf-bound attribute has to >>> be automatically added to each xforms-* element >>> when xf-ref (or xf-bind) is evaluated as a non >>> empty nodeset. CSS attribute selectors are, >>> then, used to display/hide xforms-* elements >>> accordingly. >>> >>> (2) The xf:var processing was not functional: it >>> should now work, at least, outside of actions. >>> >>> (3) The profiler is actually just another >>> external form: I have added the corresponding >>> file into the updated .zip file at >>> www.agencexml.com/1.5beta/xsltforms.zip >>> <http://www.agencexml.com/1.5beta/xsltforms.zip> >>> >>> Thank you very much for your contributions! >>> >>> --Alain >>> >>> Le 09/02/2020 à 20:51, Tim Thompson a écrit : >>>> Hello, Alain, >>>> >>>> I've been testing an existing form with the new >>>> release and have some feedback. First, the >>>> performance improvement seems impressive, and >>>> CSS styling with Bootstrap now seems much >>>> easier. Thank you! >>>> >>>> I did notice some issues after testing, however. >>>> >>>> (1) >>>> There seems to be a bug with XPath predicate >>>> filtering in xf:group elements. For example, a >>>> group binding such as <xf:group >>>> ref="instance('response')/response[*]">...</xf:group>, >>>> where the response element should initially be >>>> empty (before a submission is executed) does >>>> not seem to work. >>>> >>>> See the test form copied below. Example form >>>> at: >>>> https://www.tat2.io/basex2/static/xsltforms_test_2020-02-09.xml >>>> >>>> (2) >>>> I see that the xforms:var element is not >>>> currently supported. When loading a form with >>>> an XForms variable defined, I get an error message: >>>> >>>> Error initializing: >>>> >>>> xforms:var is not supported >>>> >>>> (3) >>>> I also see that the XSLTForms Profiler does not >>>> seem to be available. When I try to open it, I >>>> get an error: >>>> >>>> File not found (404): >>>> https://www.tat2.io/basex2/static/xsltforms_profiler.xhtml >>>> >>>> * >>>> * >>>> *--Test form for XPath predicate bug--* >>>> * >>>> * >>>> <?xml-stylesheet type="text/xsl" href="..."?> >>>> <html >>>> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" >>>> xmlns:xsd="http://www.w3.org/2001/XMLSchema" >>>> xmlns:xf="http://www.w3.org/2002/xforms" >>>> xmlns:h="http://www.w3.org/1999/xhtml" >>>> xmlns:ev="http://www.w3.org/2001/xml-events" >>>> xmlns="http://www.w3.org/1999/xhtml"> >>>> <head> >>>> <meta http-equiv="Content-Type" >>>> content="text/html; charset=UTF-8" /> >>>> <title>XForms/XPath Predicate Test</title> >>>> <style type="text/css"/> >>>> <model >>>> xmlns="http://www.w3.org/2002/xforms" id="m"> >>>> <instance id="default"> >>>> <data xmlns=""> >>>> <default/> >>>> </data> >>>> </instance> >>>> <instance id="response"> >>>> <data xmlns=""> >>>> <response/> >>>> </data> >>>> </instance> >>>> <instance id="response-test"> >>>> <data xmlns=""> >>>> <response> >>>> <testing>Testing</testing> >>>> </response> >>>> </data> >>>> </instance> >>>> </model> >>>> </head> >>>> <body> >>>> <div class="container-fluid"> >>>> <hr class="blue" /> >>>> <h1>XForms/XPath predicate test</h1> >>>> <xf:group >>>> ref="instance('response')/response[*]"> >>>> <h2 style="color: red;">This should not >>>> display!</h2> >>>> <xf:output value="concat('Value of >>>> "serialize(.)": ', serialize(.))"/> >>>> </xf:group> >>>> <xf:group >>>> ref="instance('response-test')/response[*]"> >>>> <h2 style="color: blue;">This should >>>> display.</h2> >>>> <xf:output value="concat('Value of >>>> "serialize(.)": ', serialize(.))"/> >>>> </xf:group> >>>> </div> >>>> </body> >>>> </html> >>>> >>>> >>>> >>>> -- >>>> Tim A. Thompson >>>> Discovery Metadata Librarian >>>> Yale University Library >>>> >>>> On Sun, Feb 9, 2020 at 11:06 AM Tim Thompson >>>> <tim...@gm... >>>> <mailto:tim...@gm...>> wrote: >>>> >>>> Hello, Alain, >>>> >>>> Congratulations on this milestone! I am >>>> very eager to try and test the new release. >>>> Is XSLTForms now using Fleur for XPath >>>> parsing? Does this mean that XPath 3.0 >>>> functions are now supported? I guess I can >>>> test this myself :) >>>> >>>> It's quite amazing to see the xsltforms.xsl >>>> file down to just over 500 lines. >>>> >>>> Thanks again for all your work. >>>> >>>> Best regards, >>>> Tim >>>> >>>> >>>> -- >>>> Tim A. Thompson >>>> Discovery Metadata Librarian >>>> Yale University Library >>>> >>>> On Wed, Feb 5, 2020 at 3:16 PM Alain >>>> Couthures <ala...@ag... >>>> <mailto:ala...@ag...>> wrote: >>>> >>>> Hello, >>>> >>>> Please find a new release for XSLTForms >>>> at >>>> www.agencexml.com/1.5beta/xsltforms.zip >>>> <http://www.agencexml.com/1.5beta/xsltforms.zip> >>>> >>>> It has not yet been fully tested >>>> because a lot of changes have been made >>>> and you are welcome to locate remaining >>>> issues with your own forms. >>>> >>>> The XSLT part has been reduced to >>>> minimal for better performance. Instead >>>> of parsing the XPath expressions and >>>> transforming all the XForms elements >>>> into HTML elements, it basically just >>>> transposes the non-HTML elements into >>>> sort-of custom elements: xforms:* >>>> elements become xforms-* elements with >>>> xf-* and ev-* attributes. >>>> >>>> Have a look with your favorite browser >>>> debugger! Actually, authors could even >>>> prefer to directly write/generate forms >>>> with this new notation and forget about >>>> the XSLT step. You can compare two >>>> sources for the same form: hello.xml >>>> and hello.htm >>>> >>>> XSLTForms Javascript classes >>>> constructors are obtaining their >>>> properties directly from xf-* >>>> attributes and XPath parsing is then >>>> performed. >>>> >>>> No ids are automatically added as >>>> previously. >>>> >>>> Extra xf-* attributes and extra >>>> xforms-* elements are used to embed >>>> effective HTML rendering elements, for >>>> example, xforms-body or >>>> xforms-repeat-item while, before, span >>>> or div elements where used. >>>> >>>> XSLTForms classes for xforms:select and >>>> xforms:itemset had to be partially >>>> rewritten. >>>> >>>> SVG support has been basically tested too. >>>> >>>> CSS styling is not anymore based on >>>> xforms-* classes but on custom element >>>> names and attribute selectors. For >>>> example, the extra xf-bound attribute, >>>> when present, says that the XForms >>>> control is bound to a node, eventually >>>> a not relevant one, and the extra >>>> xf-notrelevant attribute can, then, be >>>> checked... >>>> >>>> Thank you for your contribution! >>>> >>>> --Alain >>>> _______________________________________________ >>>> Xsltforms-support mailing list >>>> Xsl...@li... >>>> <mailto:Xsl...@li...> >>>> https://lists.sourceforge.net/lists/listinfo/xsltforms-support >>>> >>> >> > |
|
From: Tim T. <tim...@gm...> - 2020-02-28 17:50:47
|
Ah, I see--my mistake. I think I was confused by assuming that the xf:refresh would inherit a DOMActivate event from the xf:submit button. Thanks, Tim -- Tim A. Thompson Discovery Metadata Librarian Yale University Library On Fri, Feb 28, 2020 at 11:54 AM Alain Couthures < ala...@ag...> wrote: > Hello Tim, > > It appears that there is actually no event attached to this refresh > action. The latest 1.5beta build does not support this situation so a > Javascript error occurs (I don't know whether a warning should be displayed > or if it better just to ignore "unreachable" actions). > > Please try again with an embedding xf:action for xf:setvalue followed by > xf:refresh (which might be useless BTW). > > The next build should just ignore this. > > Thanks! > > --Alain > > > Le 28/02/2020 à 04:16, Tim Thompson a écrit : > > Hello, Alain, > > Thanks again for the latest updates! I have another test for you. > > Here is my use case: I want to display an ephemeral "Loading" message when > I trigger a submission. To achieve this, I have an instance: > > <instance id="state"> > <data xmlns=""> > <status loading="false" ready="false">...Loading...</status> > </data> > </instance> > > When the submission is triggered, I call xf:setvalue to change the > @loading attribute to "true." This causes the loading message to display. > When the submission completes, the @loading attribute is set to "false" > again. > > For the value change to take effect, I find that I have to call > xf:refresh, or else the binding won't be registered. > > In the latest version of beta1.5, if I call xf:refresh from within an > xf:submit element, the following error is thrown. This does not occur in > XSLTForms 1.4. > > XSLTForms Exception > -------------------------- > > Incorrect Javascript code generation: > > XsltForms_abstractAction.prototype.init@ > https://www.tat2.io/basex2/static/xsltforms.js:11252:35 > XsltForms_dispatch@https://www.tat2.io/basex2/static/xsltforms.js:11462:7 > anonymous@https://www.tat2.io/basex2/static/xsltforms.js line 5740 > > Function:3:181 > schback/<@https://www.tat2.io/basex2/static/xsltforms.js:5759:125 > schback@https://www.tat2.io/basex2/static/xsltforms.js:5759:66 > schloader@https://www.tat2.io/basex2/static/xsltforms.js:5780:11 > XsltForms_class.activateAll@ > https://www.tat2.io/basex2/static/xsltforms.js:5815:11 > xsltforms_init@https://www.tat2.io/basex2/static/xsltforms.js:16516:22 > > > TypeError > > mainaction.hasAttribute is not a function > > However, if I call xf:refresh from within an xforms-submit action, no > error is thrown. > > See examples: > > *1. xf:setvalue with xf:refresh inside xf:submit (1.5beta)*: > > https://www.tat2.io/basex2/static/xsltforms_setvalue_refresh_test_2020-02-27_1.5beta.xml > > *2. xf:setvalue inside xf:submit, xf:refresh inside xforms-submit action > (1.5beta):* > > https://www.tat2.io/basex2/static/xsltforms_setvalue_refresh_test_2020-02-27_1.5beta_v2.xml > > *3. xf:setvalue with xf:refresh inside xf:submit (1.4):* > > https://www.tat2.io/basex2/static/xsltforms_setvalue_refresh_test_2020-02-27_1.4.xml > > > Best regards, > Tim > > > -- > Tim A. Thompson > Discovery Metadata Librarian > Yale University Library > > On Mon, Feb 17, 2020 at 4:56 PM Tim Thompson <tim...@gm...> wrote: > >> Thank you, Alain! >> >> If you don't mind, I have another test form that works in XSLTForms 1.4 >> but not 1.5beta. >> >> This one is testing xf:var again. >> >> In 1.5beta, an error is thrown: >> Assertion failed: Binding evaluation didn't returned a nodeset but '1' >> for XPath expression: count(ancestor::item) >> >> https://www.tat2.io/basex2/static/xsltforms_var_test_2020-02-17_with_var_1.5beta.xml >> >> In 1.4, the form works as expected: >> >> https://www.tat2.io/basex2/static/xsltforms_var_test_2020-02-17_with_var_1.4.xml >> >> Best regards, >> Tim >> >> >> -- >> Tim A. Thompson >> Discovery Metadata Librarian >> Yale University Library >> >> >> On Mon, Feb 17, 2020 at 3:54 PM Alain Couthures < >> ala...@ag...> wrote: >> >>> Hello Tim, >>> >>> This issue is now fixed (and some more actually...). >>> >>> The new build can be downloaded at the same URL: >>> www.agencexml.com/1.5beta/xsltforms.zip >>> >>> Thank you again for your contributions! >>> >>> --Alain >>> >>> Le 15/02/2020 à 01:15, Tim Thompson a écrit : >>> >>> Hello, Alain, >>> >>> Another test for you: >>> >>> In XSLTForms 1.5beta, the DOMActivate event is not being evoked for >>> input controls. See this test form: >>> >>> >>> https://www.tat2.io/basex2/static/xsltforms_DOMActivate_test_2020-02-14_1-5beta.xml >>> >>> Pressing "enter" in the input field does nothing, whereas clicking the >>> button triggers the event. >>> >>> Compare this to a form running XSLTForms 1.4: >>> >>> >>> https://www.tat2.io/basex2/static/xsltforms_DOMActivate_test_2020-02-14_1-4.xml >>> >>> Here, the DOMActivate enter works in both the input field with the >>> "enter" key and with the button. >>> >>> All best, >>> Tim >>> >>> -- >>> Tim A. Thompson >>> Discovery Metadata Librarian >>> Yale University Library >>> >>> On Wed, Feb 12, 2020 at 5:51 PM Tim Thompson <tim...@gm...> wrote: >>> >>>> Great! Works perfectly now. Looking forward to the XML Prague >>>> proceedings and video for your presentation with Steven Pemberton. >>>> >>>> Thanks again, >>>> Tim >>>> >>>> >>>> -- >>>> Tim A. Thompson >>>> Discovery Metadata Librarian >>>> Yale University Library >>>> >>>> >>>> >>>> On Wed, Feb 12, 2020 at 4:00 PM Alain Couthures < >>>> ala...@ag...> wrote: >>>> >>>>> Hello Tim, >>>>> >>>>> (1) The xf:group processing was not correct: in the new approach, an >>>>> xf-bound attribute has to be automatically added to each xforms-* element >>>>> when xf-ref (or xf-bind) is evaluated as a non empty nodeset. CSS attribute >>>>> selectors are, then, used to display/hide xforms-* elements accordingly. >>>>> >>>>> (2) The xf:var processing was not functional: it should now work, at >>>>> least, outside of actions. >>>>> >>>>> (3) The profiler is actually just another external form: I have added >>>>> the corresponding file into the updated .zip file at >>>>> www.agencexml.com/1.5beta/xsltforms.zip >>>>> >>>>> Thank you very much for your contributions! >>>>> >>>>> --Alain >>>>> >>>>> Le 09/02/2020 à 20:51, Tim Thompson a écrit : >>>>> >>>>> Hello, Alain, >>>>> >>>>> I've been testing an existing form with the new release and have some >>>>> feedback. First, the performance improvement seems impressive, and CSS >>>>> styling with Bootstrap now seems much easier. Thank you! >>>>> >>>>> I did notice some issues after testing, however. >>>>> >>>>> (1) >>>>> There seems to be a bug with XPath predicate filtering in xf:group >>>>> elements. For example, a group binding such as <xf:group >>>>> ref="instance('response')/response[*]">...</xf:group>, where the response >>>>> element should initially be empty (before a submission is executed) does >>>>> not seem to work. >>>>> >>>>> See the test form copied below. Example form at: >>>>> https://www.tat2.io/basex2/static/xsltforms_test_2020-02-09.xml >>>>> >>>>> (2) >>>>> I see that the xforms:var element is not currently supported. When >>>>> loading a form with an XForms variable defined, I get an error message: >>>>> >>>>> Error initializing: >>>>> >>>>> xforms:var is not supported >>>>> >>>>> (3) >>>>> I also see that the XSLTForms Profiler does not seem to be available. >>>>> When I try to open it, I get an error: >>>>> >>>>> File not found (404): >>>>> https://www.tat2.io/basex2/static/xsltforms_profiler.xhtml >>>>> >>>>> >>>>> *--Test form for XPath predicate bug--* >>>>> >>>>> <?xml-stylesheet type="text/xsl" href="..."?> >>>>> <html xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" >>>>> xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xf=" >>>>> http://www.w3.org/2002/xforms" xmlns:h="http://www.w3.org/1999/xhtml" >>>>> xmlns:ev="http://www.w3.org/2001/xml-events" xmlns=" >>>>> http://www.w3.org/1999/xhtml"> >>>>> <head> >>>>> <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" >>>>> /> >>>>> <title>XForms/XPath Predicate Test</title> >>>>> <style type="text/css"/> >>>>> <model xmlns="http://www.w3.org/2002/xforms" id="m"> >>>>> <instance id="default"> >>>>> <data xmlns=""> >>>>> <default/> >>>>> </data> >>>>> </instance> >>>>> <instance id="response"> >>>>> <data xmlns=""> >>>>> <response/> >>>>> </data> >>>>> </instance> >>>>> <instance id="response-test"> >>>>> <data xmlns=""> >>>>> <response> >>>>> <testing>Testing</testing> >>>>> </response> >>>>> </data> >>>>> </instance> >>>>> </model> >>>>> </head> >>>>> <body> >>>>> <div class="container-fluid"> >>>>> <hr class="blue" /> >>>>> <h1>XForms/XPath predicate test</h1> >>>>> <xf:group ref="instance('response')/response[*]"> >>>>> <h2 style="color: red;">This should not display!</h2> >>>>> <xf:output value="concat('Value of "serialize(.)": >>>>> ', serialize(.))"/> >>>>> </xf:group> >>>>> <xf:group ref="instance('response-test')/response[*]"> >>>>> <h2 style="color: blue;">This should display.</h2> >>>>> <xf:output value="concat('Value of "serialize(.)": >>>>> ', serialize(.))"/> >>>>> </xf:group> >>>>> </div> >>>>> </body> >>>>> </html> >>>>> >>>>> >>>>> >>>>> -- >>>>> Tim A. Thompson >>>>> Discovery Metadata Librarian >>>>> Yale University Library >>>>> >>>>> On Sun, Feb 9, 2020 at 11:06 AM Tim Thompson <tim...@gm...> >>>>> wrote: >>>>> >>>>>> Hello, Alain, >>>>>> >>>>>> Congratulations on this milestone! I am very eager to try and test >>>>>> the new release. Is XSLTForms now using Fleur for XPath parsing? Does this >>>>>> mean that XPath 3.0 functions are now supported? I guess I can test this >>>>>> myself :) >>>>>> >>>>>> It's quite amazing to see the xsltforms.xsl file down to just over >>>>>> 500 lines. >>>>>> >>>>>> Thanks again for all your work. >>>>>> >>>>>> Best regards, >>>>>> Tim >>>>>> >>>>>> >>>>>> -- >>>>>> Tim A. Thompson >>>>>> Discovery Metadata Librarian >>>>>> Yale University Library >>>>>> >>>>>> On Wed, Feb 5, 2020 at 3:16 PM Alain Couthures < >>>>>> ala...@ag...> wrote: >>>>>> >>>>>>> Hello, >>>>>>> >>>>>>> Please find a new release for XSLTForms at >>>>>>> www.agencexml.com/1.5beta/xsltforms.zip >>>>>>> >>>>>>> It has not yet been fully tested because a lot of changes have been >>>>>>> made and you are welcome to locate remaining issues with your own forms. >>>>>>> >>>>>>> The XSLT part has been reduced to minimal for better performance. >>>>>>> Instead of parsing the XPath expressions and transforming all the XForms >>>>>>> elements into HTML elements, it basically just transposes the non-HTML >>>>>>> elements into sort-of custom elements: xforms:* elements become xforms-* >>>>>>> elements with xf-* and ev-* attributes. >>>>>>> >>>>>>> Have a look with your favorite browser debugger! Actually, authors >>>>>>> could even prefer to directly write/generate forms with this new notation >>>>>>> and forget about the XSLT step. You can compare two sources for the same >>>>>>> form: hello.xml and hello.htm >>>>>>> >>>>>>> XSLTForms Javascript classes constructors are obtaining their >>>>>>> properties directly from xf-* attributes and XPath parsing is then >>>>>>> performed. >>>>>>> >>>>>>> No ids are automatically added as previously. >>>>>>> >>>>>>> Extra xf-* attributes and extra xforms-* elements are used to embed >>>>>>> effective HTML rendering elements, for example, xforms-body or >>>>>>> xforms-repeat-item while, before, span or div elements where used. >>>>>>> >>>>>>> XSLTForms classes for xforms:select and xforms:itemset had to be >>>>>>> partially rewritten. >>>>>>> >>>>>>> SVG support has been basically tested too. >>>>>>> >>>>>>> CSS styling is not anymore based on xforms-* classes but on custom >>>>>>> element names and attribute selectors. For example, the extra xf-bound >>>>>>> attribute, when present, says that the XForms control is bound to a node, >>>>>>> eventually a not relevant one, and the extra xf-notrelevant attribute can, >>>>>>> then, be checked... >>>>>>> >>>>>>> Thank you for your contribution! >>>>>>> >>>>>>> --Alain >>>>>>> _______________________________________________ >>>>>>> Xsltforms-support mailing list >>>>>>> Xsl...@li... >>>>>>> https://lists.sourceforge.net/lists/listinfo/xsltforms-support >>>>>>> >>>>>> >>>>> >>> > |
|
From: Alain C. <ala...@ag...> - 2020-02-28 16:54:20
|
Hello Tim, It appears that there is actually no event attached to this refresh action. The latest 1.5beta build does not support this situation so a Javascript error occurs (I don't know whether a warning should be displayed or if it better just to ignore "unreachable" actions). Please try again with an embedding xf:action for xf:setvalue followed by xf:refresh (which might be useless BTW). The next build should just ignore this. Thanks! --Alain Le 28/02/2020 à 04:16, Tim Thompson a écrit : > Hello, Alain, > > Thanks again for the latest updates! I have another test for you. > > Here is my use case: I want to display an ephemeral "Loading" message > when I trigger a submission. To achieve this, I have an instance: > > <instance id="state"> > <data xmlns=""> > <status loading="false" ready="false">...Loading...</status> > </data> > </instance> > > When the submission is triggered, I call xf:setvalue to change the > @loading attribute to "true." This causes the loading message to > display. When the submission completes, the @loading attribute is set > to "false" again. > > For the value change to take effect, I find that I have to call > xf:refresh, or else the binding won't be registered. > > In the latest version of beta1.5, if I call xf:refresh from within an > xf:submit element, the following error is thrown. This does not occur > in XSLTForms 1.4. > > XSLTForms Exception > -------------------------- > > Incorrect Javascript code generation: > > XsltForms_abstractAction.prototype.init@https://www.tat2.io/basex2/static/xsltforms.js:11252:35 > XsltForms_dispatch@https://www.tat2.io/basex2/static/xsltforms.js:11462:7 > anonymous@https://www.tat2.io/basex2/static/xsltforms.js line 5740 > > Function:3:181 > schback/<@https://www.tat2.io/basex2/static/xsltforms.js:5759:125 > schback@https://www.tat2.io/basex2/static/xsltforms.js:5759:66 > schloader@https://www.tat2.io/basex2/static/xsltforms.js:5780:11 > XsltForms_class.activateAll@https://www.tat2.io/basex2/static/xsltforms.js:5815:11 > xsltforms_init@https://www.tat2.io/basex2/static/xsltforms.js:16516:22 > > > TypeError > > mainaction.hasAttribute is not a function > > However, if I call xf:refresh from within an xforms-submit action, no > error is thrown. > > See examples: > > *1. xf:setvalue with xf:refresh inside xf:submit (1.5beta)*: > https://www.tat2.io/basex2/static/xsltforms_setvalue_refresh_test_2020-02-27_1.5beta.xml > > *2. xf:setvalue inside xf:submit, xf:refresh inside xforms-submit > action (1.5beta):* > https://www.tat2.io/basex2/static/xsltforms_setvalue_refresh_test_2020-02-27_1.5beta_v2.xml > > *3. xf:setvalue with xf:refresh inside xf:submit (1.4):* > https://www.tat2.io/basex2/static/xsltforms_setvalue_refresh_test_2020-02-27_1.4.xml > > > Best regards, > Tim > > > -- > Tim A. Thompson > Discovery Metadata Librarian > Yale University Library > > On Mon, Feb 17, 2020 at 4:56 PM Tim Thompson <tim...@gm... > <mailto:tim...@gm...>> wrote: > > Thank you, Alain! > > If you don't mind, I have another test form that works in > XSLTForms 1.4 but not 1.5beta. > > This one is testing xf:var again. > > In 1.5beta, an error is thrown: > Assertion failed: Binding evaluation didn't returned a nodeset but > '1' for XPath expression: count(ancestor::item) > https://www.tat2.io/basex2/static/xsltforms_var_test_2020-02-17_with_var_1.5beta.xml > > In 1.4, the form works as expected: > https://www.tat2.io/basex2/static/xsltforms_var_test_2020-02-17_with_var_1.4.xml > > Best regards, > Tim > > > -- > Tim A. Thompson > Discovery Metadata Librarian > Yale University Library > > > On Mon, Feb 17, 2020 at 3:54 PM Alain Couthures > <ala...@ag... > <mailto:ala...@ag...>> wrote: > > Hello Tim, > > This issue is now fixed (and some more actually...). > > The new build can be downloaded at the same URL: > www.agencexml.com/1.5beta/xsltforms.zip > <http://www.agencexml.com/1.5beta/xsltforms.zip> > > Thank you again for your contributions! > > --Alain > > Le 15/02/2020 à 01:15, Tim Thompson a écrit : >> Hello, Alain, >> >> Another test for you: >> >> In XSLTForms 1.5beta, the DOMActivate event is not being >> evoked for input controls. See this test form: >> >> https://www.tat2.io/basex2/static/xsltforms_DOMActivate_test_2020-02-14_1-5beta.xml >> >> Pressing "enter" in the input field does nothing, whereas >> clicking the button triggers the event. >> >> Compare this to a form running XSLTForms 1.4: >> >> https://www.tat2.io/basex2/static/xsltforms_DOMActivate_test_2020-02-14_1-4.xml >> >> Here, the DOMActivate enter works in both the input field >> with the "enter" key and with the button. >> >> All best, >> Tim >> >> -- >> Tim A. Thompson >> Discovery Metadata Librarian >> Yale University Library >> >> On Wed, Feb 12, 2020 at 5:51 PM Tim Thompson >> <tim...@gm... <mailto:tim...@gm...>> wrote: >> >> Great! Works perfectly now. Looking forward to the XML >> Prague proceedings and video for your presentation with >> Steven Pemberton. >> >> Thanks again, >> Tim >> >> >> -- >> Tim A. Thompson >> Discovery Metadata Librarian >> Yale University Library >> >> >> >> On Wed, Feb 12, 2020 at 4:00 PM Alain Couthures >> <ala...@ag... >> <mailto:ala...@ag...>> wrote: >> >> Hello Tim, >> >> (1) The xf:group processing was not correct: in the >> new approach, an xf-bound attribute has to be >> automatically added to each xforms-* element when >> xf-ref (or xf-bind) is evaluated as a non empty >> nodeset. CSS attribute selectors are, then, used to >> display/hide xforms-* elements accordingly. >> >> (2) The xf:var processing was not functional: it >> should now work, at least, outside of actions. >> >> (3) The profiler is actually just another external >> form: I have added the corresponding file into the >> updated .zip file at >> www.agencexml.com/1.5beta/xsltforms.zip >> <http://www.agencexml.com/1.5beta/xsltforms.zip> >> >> Thank you very much for your contributions! >> >> --Alain >> >> Le 09/02/2020 à 20:51, Tim Thompson a écrit : >>> Hello, Alain, >>> >>> I've been testing an existing form with the new >>> release and have some feedback. First, the >>> performance improvement seems impressive, and CSS >>> styling with Bootstrap now seems much easier. Thank you! >>> >>> I did notice some issues after testing, however. >>> >>> (1) >>> There seems to be a bug with XPath predicate >>> filtering in xf:group elements. For example, a group >>> binding such as <xf:group >>> ref="instance('response')/response[*]">...</xf:group>, >>> where the response element should initially be empty >>> (before a submission is executed) does not seem to >>> work. >>> >>> See the test form copied below. Example form at: >>> https://www.tat2.io/basex2/static/xsltforms_test_2020-02-09.xml >>> >>> (2) >>> I see that the xforms:var element is not currently >>> supported. When loading a form with an XForms >>> variable defined, I get an error message: >>> >>> Error initializing: >>> >>> xforms:var is not supported >>> >>> (3) >>> I also see that the XSLTForms Profiler does not seem >>> to be available. When I try to open it, I get an error: >>> >>> File not found (404): >>> https://www.tat2.io/basex2/static/xsltforms_profiler.xhtml >>> >>> * >>> * >>> *--Test form for XPath predicate bug--* >>> * >>> * >>> <?xml-stylesheet type="text/xsl" href="..."?> >>> <html >>> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" >>> xmlns:xsd="http://www.w3.org/2001/XMLSchema" >>> xmlns:xf="http://www.w3.org/2002/xforms" >>> xmlns:h="http://www.w3.org/1999/xhtml" >>> xmlns:ev="http://www.w3.org/2001/xml-events" >>> xmlns="http://www.w3.org/1999/xhtml"> >>> <head> >>> <meta http-equiv="Content-Type" >>> content="text/html; charset=UTF-8" /> >>> <title>XForms/XPath Predicate Test</title> >>> <style type="text/css"/> >>> <model xmlns="http://www.w3.org/2002/xforms" id="m"> >>> <instance id="default"> >>> <data xmlns=""> >>> <default/> >>> </data> >>> </instance> >>> <instance id="response"> >>> <data xmlns=""> >>> <response/> >>> </data> >>> </instance> >>> <instance id="response-test"> >>> <data xmlns=""> >>> <response> >>> <testing>Testing</testing> >>> </response> >>> </data> >>> </instance> >>> </model> >>> </head> >>> <body> >>> <div class="container-fluid"> >>> <hr class="blue" /> >>> <h1>XForms/XPath predicate test</h1> >>> <xf:group ref="instance('response')/response[*]"> >>> <h2 style="color: red;">This should not >>> display!</h2> >>> <xf:output value="concat('Value of >>> "serialize(.)": ', serialize(.))"/> >>> </xf:group> >>> <xf:group >>> ref="instance('response-test')/response[*]"> >>> <h2 style="color: blue;">This should >>> display.</h2> >>> <xf:output value="concat('Value of >>> "serialize(.)": ', serialize(.))"/> >>> </xf:group> >>> </div> >>> </body> >>> </html> >>> >>> >>> >>> -- >>> Tim A. Thompson >>> Discovery Metadata Librarian >>> Yale University Library >>> >>> On Sun, Feb 9, 2020 at 11:06 AM Tim Thompson >>> <tim...@gm... <mailto:tim...@gm...>> wrote: >>> >>> Hello, Alain, >>> >>> Congratulations on this milestone! I am very >>> eager to try and test the new release. Is >>> XSLTForms now using Fleur for XPath parsing? >>> Does this mean that XPath 3.0 functions are now >>> supported? I guess I can test this myself :) >>> >>> It's quite amazing to see the xsltforms.xsl file >>> down to just over 500 lines. >>> >>> Thanks again for all your work. >>> >>> Best regards, >>> Tim >>> >>> >>> -- >>> Tim A. Thompson >>> Discovery Metadata Librarian >>> Yale University Library >>> >>> On Wed, Feb 5, 2020 at 3:16 PM Alain Couthures >>> <ala...@ag... >>> <mailto:ala...@ag...>> wrote: >>> >>> Hello, >>> >>> Please find a new release for XSLTForms at >>> www.agencexml.com/1.5beta/xsltforms.zip >>> <http://www.agencexml.com/1.5beta/xsltforms.zip> >>> >>> It has not yet been fully tested because a >>> lot of changes have been made and you are >>> welcome to locate remaining issues with your >>> own forms. >>> >>> The XSLT part has been reduced to minimal >>> for better performance. Instead of parsing >>> the XPath expressions and transforming all >>> the XForms elements into HTML elements, it >>> basically just transposes the non-HTML >>> elements into sort-of custom elements: >>> xforms:* elements become xforms-* elements >>> with xf-* and ev-* attributes. >>> >>> Have a look with your favorite browser >>> debugger! Actually, authors could even >>> prefer to directly write/generate forms with >>> this new notation and forget about the XSLT >>> step. You can compare two sources for the >>> same form: hello.xml and hello.htm >>> >>> XSLTForms Javascript classes constructors >>> are obtaining their properties directly from >>> xf-* attributes and XPath parsing is then >>> performed. >>> >>> No ids are automatically added as previously. >>> >>> Extra xf-* attributes and extra xforms-* >>> elements are used to embed effective HTML >>> rendering elements, for example, xforms-body >>> or xforms-repeat-item while, before, span or >>> div elements where used. >>> >>> XSLTForms classes for xforms:select and >>> xforms:itemset had to be partially rewritten. >>> >>> SVG support has been basically tested too. >>> >>> CSS styling is not anymore based on xforms-* >>> classes but on custom element names and >>> attribute selectors. For example, the extra >>> xf-bound attribute, when present, says that >>> the XForms control is bound to a node, >>> eventually a not relevant one, and the extra >>> xf-notrelevant attribute can, then, be >>> checked... >>> >>> Thank you for your contribution! >>> >>> --Alain >>> _______________________________________________ >>> Xsltforms-support mailing list >>> Xsl...@li... >>> <mailto:Xsl...@li...> >>> https://lists.sourceforge.net/lists/listinfo/xsltforms-support >>> >> > |
|
From: Tim T. <tim...@gm...> - 2020-02-28 03:16:39
|
Hello, Alain,
Thanks again for the latest updates! I have another test for you.
Here is my use case: I want to display an ephemeral "Loading" message when
I trigger a submission. To achieve this, I have an instance:
<instance id="state">
<data xmlns="">
<status loading="false" ready="false">...Loading...</status>
</data>
</instance>
When the submission is triggered, I call xf:setvalue to change the @loading
attribute to "true." This causes the loading message to display. When the
submission completes, the @loading attribute is set to "false" again.
For the value change to take effect, I find that I have to call xf:refresh,
or else the binding won't be registered.
In the latest version of beta1.5, if I call xf:refresh from within an
xf:submit element, the following error is thrown. This does not occur in
XSLTForms 1.4.
XSLTForms Exception
--------------------------
Incorrect Javascript code generation:
XsltForms_abstractAction.prototype.init@
https://www.tat2.io/basex2/static/xsltforms.js:11252:35
XsltForms_dispatch@https://www.tat2.io/basex2/static/xsltforms.js:11462:7
anonymous@https://www.tat2.io/basex2/static/xsltforms.js line 5740 >
Function:3:181
schback/<@https://www.tat2.io/basex2/static/xsltforms.js:5759:125
schback@https://www.tat2.io/basex2/static/xsltforms.js:5759:66
schloader@https://www.tat2.io/basex2/static/xsltforms.js:5780:11
XsltForms_class.activateAll@
https://www.tat2.io/basex2/static/xsltforms.js:5815:11
xsltforms_init@https://www.tat2.io/basex2/static/xsltforms.js:16516:22
TypeError
mainaction.hasAttribute is not a function
However, if I call xf:refresh from within an xforms-submit action, no error
is thrown.
See examples:
*1. xf:setvalue with xf:refresh inside xf:submit (1.5beta)*:
https://www.tat2.io/basex2/static/xsltforms_setvalue_refresh_test_2020-02-27_1.5beta.xml
*2. xf:setvalue inside xf:submit, xf:refresh inside xforms-submit action
(1.5beta):*
https://www.tat2.io/basex2/static/xsltforms_setvalue_refresh_test_2020-02-27_1.5beta_v2.xml
*3. xf:setvalue with xf:refresh inside xf:submit (1.4):*
https://www.tat2.io/basex2/static/xsltforms_setvalue_refresh_test_2020-02-27_1.4.xml
Best regards,
Tim
--
Tim A. Thompson
Discovery Metadata Librarian
Yale University Library
On Mon, Feb 17, 2020 at 4:56 PM Tim Thompson <tim...@gm...> wrote:
> Thank you, Alain!
>
> If you don't mind, I have another test form that works in XSLTForms 1.4
> but not 1.5beta.
>
> This one is testing xf:var again.
>
> In 1.5beta, an error is thrown:
> Assertion failed: Binding evaluation didn't returned a nodeset but '1' for
> XPath expression: count(ancestor::item)
>
> https://www.tat2.io/basex2/static/xsltforms_var_test_2020-02-17_with_var_1.5beta.xml
>
> In 1.4, the form works as expected:
>
> https://www.tat2.io/basex2/static/xsltforms_var_test_2020-02-17_with_var_1.4.xml
>
> Best regards,
> Tim
>
>
> --
> Tim A. Thompson
> Discovery Metadata Librarian
> Yale University Library
>
>
> On Mon, Feb 17, 2020 at 3:54 PM Alain Couthures <
> ala...@ag...> wrote:
>
>> Hello Tim,
>>
>> This issue is now fixed (and some more actually...).
>>
>> The new build can be downloaded at the same URL:
>> www.agencexml.com/1.5beta/xsltforms.zip
>>
>> Thank you again for your contributions!
>>
>> --Alain
>>
>> Le 15/02/2020 à 01:15, Tim Thompson a écrit :
>>
>> Hello, Alain,
>>
>> Another test for you:
>>
>> In XSLTForms 1.5beta, the DOMActivate event is not being evoked for input
>> controls. See this test form:
>>
>>
>> https://www.tat2.io/basex2/static/xsltforms_DOMActivate_test_2020-02-14_1-5beta.xml
>>
>> Pressing "enter" in the input field does nothing, whereas clicking the
>> button triggers the event.
>>
>> Compare this to a form running XSLTForms 1.4:
>>
>>
>> https://www.tat2.io/basex2/static/xsltforms_DOMActivate_test_2020-02-14_1-4.xml
>>
>> Here, the DOMActivate enter works in both the input field with the
>> "enter" key and with the button.
>>
>> All best,
>> Tim
>>
>> --
>> Tim A. Thompson
>> Discovery Metadata Librarian
>> Yale University Library
>>
>> On Wed, Feb 12, 2020 at 5:51 PM Tim Thompson <tim...@gm...> wrote:
>>
>>> Great! Works perfectly now. Looking forward to the XML Prague
>>> proceedings and video for your presentation with Steven Pemberton.
>>>
>>> Thanks again,
>>> Tim
>>>
>>>
>>> --
>>> Tim A. Thompson
>>> Discovery Metadata Librarian
>>> Yale University Library
>>>
>>>
>>>
>>> On Wed, Feb 12, 2020 at 4:00 PM Alain Couthures <
>>> ala...@ag...> wrote:
>>>
>>>> Hello Tim,
>>>>
>>>> (1) The xf:group processing was not correct: in the new approach, an
>>>> xf-bound attribute has to be automatically added to each xforms-* element
>>>> when xf-ref (or xf-bind) is evaluated as a non empty nodeset. CSS attribute
>>>> selectors are, then, used to display/hide xforms-* elements accordingly.
>>>>
>>>> (2) The xf:var processing was not functional: it should now work, at
>>>> least, outside of actions.
>>>>
>>>> (3) The profiler is actually just another external form: I have added
>>>> the corresponding file into the updated .zip file at
>>>> www.agencexml.com/1.5beta/xsltforms.zip
>>>>
>>>> Thank you very much for your contributions!
>>>>
>>>> --Alain
>>>>
>>>> Le 09/02/2020 à 20:51, Tim Thompson a écrit :
>>>>
>>>> Hello, Alain,
>>>>
>>>> I've been testing an existing form with the new release and have some
>>>> feedback. First, the performance improvement seems impressive, and CSS
>>>> styling with Bootstrap now seems much easier. Thank you!
>>>>
>>>> I did notice some issues after testing, however.
>>>>
>>>> (1)
>>>> There seems to be a bug with XPath predicate filtering in xf:group
>>>> elements. For example, a group binding such as <xf:group
>>>> ref="instance('response')/response[*]">...</xf:group>, where the response
>>>> element should initially be empty (before a submission is executed) does
>>>> not seem to work.
>>>>
>>>> See the test form copied below. Example form at:
>>>> https://www.tat2.io/basex2/static/xsltforms_test_2020-02-09.xml
>>>>
>>>> (2)
>>>> I see that the xforms:var element is not currently supported. When
>>>> loading a form with an XForms variable defined, I get an error message:
>>>>
>>>> Error initializing:
>>>>
>>>> xforms:var is not supported
>>>>
>>>> (3)
>>>> I also see that the XSLTForms Profiler does not seem to be available.
>>>> When I try to open it, I get an error:
>>>>
>>>> File not found (404):
>>>> https://www.tat2.io/basex2/static/xsltforms_profiler.xhtml
>>>>
>>>>
>>>> *--Test form for XPath predicate bug--*
>>>>
>>>> <?xml-stylesheet type="text/xsl" href="..."?>
>>>> <html xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="
>>>> http://www.w3.org/2001/XMLSchema" xmlns:xf="
>>>> http://www.w3.org/2002/xforms" xmlns:h="http://www.w3.org/1999/xhtml"
>>>> xmlns:ev="http://www.w3.org/2001/xml-events" xmlns="
>>>> http://www.w3.org/1999/xhtml">
>>>> <head>
>>>> <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"
>>>> />
>>>> <title>XForms/XPath Predicate Test</title>
>>>> <style type="text/css"/>
>>>> <model xmlns="http://www.w3.org/2002/xforms" id="m">
>>>> <instance id="default">
>>>> <data xmlns="">
>>>> <default/>
>>>> </data>
>>>> </instance>
>>>> <instance id="response">
>>>> <data xmlns="">
>>>> <response/>
>>>> </data>
>>>> </instance>
>>>> <instance id="response-test">
>>>> <data xmlns="">
>>>> <response>
>>>> <testing>Testing</testing>
>>>> </response>
>>>> </data>
>>>> </instance>
>>>> </model>
>>>> </head>
>>>> <body>
>>>> <div class="container-fluid">
>>>> <hr class="blue" />
>>>> <h1>XForms/XPath predicate test</h1>
>>>> <xf:group ref="instance('response')/response[*]">
>>>> <h2 style="color: red;">This should not display!</h2>
>>>> <xf:output value="concat('Value of "serialize(.)": ',
>>>> serialize(.))"/>
>>>> </xf:group>
>>>> <xf:group ref="instance('response-test')/response[*]">
>>>> <h2 style="color: blue;">This should display.</h2>
>>>> <xf:output value="concat('Value of "serialize(.)": ',
>>>> serialize(.))"/>
>>>> </xf:group>
>>>> </div>
>>>> </body>
>>>> </html>
>>>>
>>>>
>>>>
>>>> --
>>>> Tim A. Thompson
>>>> Discovery Metadata Librarian
>>>> Yale University Library
>>>>
>>>> On Sun, Feb 9, 2020 at 11:06 AM Tim Thompson <tim...@gm...>
>>>> wrote:
>>>>
>>>>> Hello, Alain,
>>>>>
>>>>> Congratulations on this milestone! I am very eager to try and test the
>>>>> new release. Is XSLTForms now using Fleur for XPath parsing? Does this mean
>>>>> that XPath 3.0 functions are now supported? I guess I can test this myself
>>>>> :)
>>>>>
>>>>> It's quite amazing to see the xsltforms.xsl file down to just over 500
>>>>> lines.
>>>>>
>>>>> Thanks again for all your work.
>>>>>
>>>>> Best regards,
>>>>> Tim
>>>>>
>>>>>
>>>>> --
>>>>> Tim A. Thompson
>>>>> Discovery Metadata Librarian
>>>>> Yale University Library
>>>>>
>>>>> On Wed, Feb 5, 2020 at 3:16 PM Alain Couthures <
>>>>> ala...@ag...> wrote:
>>>>>
>>>>>> Hello,
>>>>>>
>>>>>> Please find a new release for XSLTForms at
>>>>>> www.agencexml.com/1.5beta/xsltforms.zip
>>>>>>
>>>>>> It has not yet been fully tested because a lot of changes have been
>>>>>> made and you are welcome to locate remaining issues with your own forms.
>>>>>>
>>>>>> The XSLT part has been reduced to minimal for better performance.
>>>>>> Instead of parsing the XPath expressions and transforming all the XForms
>>>>>> elements into HTML elements, it basically just transposes the non-HTML
>>>>>> elements into sort-of custom elements: xforms:* elements become xforms-*
>>>>>> elements with xf-* and ev-* attributes.
>>>>>>
>>>>>> Have a look with your favorite browser debugger! Actually, authors
>>>>>> could even prefer to directly write/generate forms with this new notation
>>>>>> and forget about the XSLT step. You can compare two sources for the same
>>>>>> form: hello.xml and hello.htm
>>>>>>
>>>>>> XSLTForms Javascript classes constructors are obtaining their
>>>>>> properties directly from xf-* attributes and XPath parsing is then
>>>>>> performed.
>>>>>>
>>>>>> No ids are automatically added as previously.
>>>>>>
>>>>>> Extra xf-* attributes and extra xforms-* elements are used to embed
>>>>>> effective HTML rendering elements, for example, xforms-body or
>>>>>> xforms-repeat-item while, before, span or div elements where used.
>>>>>>
>>>>>> XSLTForms classes for xforms:select and xforms:itemset had to be
>>>>>> partially rewritten.
>>>>>>
>>>>>> SVG support has been basically tested too.
>>>>>>
>>>>>> CSS styling is not anymore based on xforms-* classes but on custom
>>>>>> element names and attribute selectors. For example, the extra xf-bound
>>>>>> attribute, when present, says that the XForms control is bound to a node,
>>>>>> eventually a not relevant one, and the extra xf-notrelevant attribute can,
>>>>>> then, be checked...
>>>>>>
>>>>>> Thank you for your contribution!
>>>>>>
>>>>>> --Alain
>>>>>> _______________________________________________
>>>>>> Xsltforms-support mailing list
>>>>>> Xsl...@li...
>>>>>> https://lists.sourceforge.net/lists/listinfo/xsltforms-support
>>>>>>
>>>>>
>>>>
>>
|
|
From: Steven P. <ste...@cw...> - 2020-02-25 21:18:04
|
Thanks. When you select1 an item from an itemset, the value you select gets displayed as a label. Example form: https://homepages.cwi.nl/~steven/forms/examples/suggest/suggest1.xhtml Steven On Tue, 25 Feb 2020 19:23:25 +0100, Alain Couthures <ala...@ag...> wrote: > Steven and Tim, > > A new build with more fixes can now be downloaded at > www.agencexml.com/1.5beta/xsltforms.zip > > Thank you for your contributions! > > --Alain > > Le 24/02/2020 à 14:39, Tim Thompson a écrit : >> Steven, >> >> You'll want to download the .zip file again. This bug seems to have >> been resolved (see >> https://sourceforge.net/>>p/xsltforms/mailman/message/36926131/). >> >> Cheers, >> Tim >> >> -- >> Tim A. Thompson >> Discovery Metadata Librarian >> Yale University Library >> >> >> >> On Mon, Feb 24, 2020 at 8:31 AM Steven Pemberton >> <ste...@cw...> wrote: >>> Exciting to be testing the new implementation. >>> >>> I'll start simple. >>> >>> [Enter] in an <input/> doesn't seem to dispatch a DOMActivate. >>> For instance, >>> https://homepages.cwi.nl/~steven/forms/examples/lists/list3.xhtml >>> >>> Steven >>> >>> >>> >>> On Wed, 05 Feb 2020 21:15:57 +0100, Alain Couthures >>> <ala...@ag...> wrote: >>> >>>> Hello, >>>> >>>> Please find a new release for XSLTForms at >>>> www.agencexml.com/1.5beta/xsltforms.zip >>>> >>>> It has not yet been fully tested because a lot of changes have been >>>> made and you are welcome to locate remaining issues with >>>>your own >>>> forms. >>>> >>>> The XSLT part has been reduced to minimal for better performance. >>>> Instead of parsing the XPath expressions and transforming all >>>>the >>>> XForms elements into HTML elements, it basically just transposes the >>>> non-HTML elements into sort-of custom elements: >>>>xforms:* elements >>>> become xforms-* elements with xf-* and ev-* attributes. >>>> >>>> Have a look with your favorite browser debugger! Actually, authors >>>> could even prefer to directly write/generate forms with this new >>>> >>>>notation and forget about the XSLT step. You can compare two >>>> sources for the same form: hello.xml and hello.htm >>>> >>>> XSLTForms Javascript classes constructors are obtaining their >>>> properties directly from xf-* attributes and XPath parsing is then >>>> >>>>performed. >>>> >>>> No ids are automatically added as previously. >>>> >>>> Extra xf-* attributes and extra xforms-* elements are used to embed >>>> effective HTML rendering elements, for example, xforms-body >>>>or >>>> xforms-repeat-item while, before, span or div elements where used. >>>> >>>> XSLTForms classes for xforms:select and xforms:itemset had to be >>>> partially rewritten. >>>> >>>> SVG support has been basically tested too. >>>> >>>> CSS styling is not anymore based on xforms-* classes but on custom >>>> element names and attribute selectors. For example, the >>>>extra >>>> xf-bound attribute, when present, says that the XForms control is >>>> bound to a node, eventually a not relevant one, and the >>>>extra >>>> xf-notrelevant attribute can, then, be checked... >>>> >>>> Thank you for your contribution! >>>> >>>> --Alain >>> >>> >>> >>> _______________________________________________ >>> Xsltforms-support mailing list >>> Xsl...@li... >>> https://lists.sourceforge.net/lists/listinfo/xsltforms-support |
|
From: Alain C. <ala...@ag...> - 2020-02-25 18:23:41
|
Steven and Tim, A new build with more fixes can now be downloaded at www.agencexml.com/1.5beta/xsltforms.zip <http://www.agencexml.com/1.5beta/xsltforms.zip> Thank you for your contributions! --Alain Le 24/02/2020 à 14:39, Tim Thompson a écrit : > Steven, > > You'll want to download the .zip file again. This bug seems to have > been resolved (see > https://sourceforge.net/p/xsltforms/mailman/message/36926131/). > > Cheers, > Tim > > -- > Tim A. Thompson > Discovery Metadata Librarian > Yale University Library > > > > On Mon, Feb 24, 2020 at 8:31 AM Steven Pemberton > <ste...@cw... <mailto:ste...@cw...>> wrote: > > Exciting to be testing the new implementation. > > I'll start simple. > > [Enter] in an <input/> doesn't seem to dispatch a DOMActivate. > For instance, > https://homepages.cwi.nl/~steven/forms/examples/lists/list3.xhtml > > Steven > > > > On Wed, 05 Feb 2020 21:15:57 +0100, Alain Couthures > <ala...@ag... > <mailto:ala...@ag...>> wrote: > > Hello, > > Please find a new release for XSLTForms at > www.agencexml.com/1.5beta/xsltforms.zip > <http://www.agencexml.com/1.5beta/xsltforms.zip> > > It has not yet been fully tested because a lot of changes have > been made and you are welcome to locate remaining issues with > your own forms. > > The XSLT part has been reduced to minimal for better > performance. Instead of parsing the XPath expressions and > transforming all the XForms elements into HTML elements, it > basically just transposes the non-HTML elements into sort-of > custom elements: xforms:* elements become xforms-* elements > with xf-* and ev-* attributes. > > Have a look with your favorite browser debugger! Actually, > authors could even prefer to directly write/generate forms > with this new notation and forget about the XSLT step. You can > compare two sources for the same form: hello.xml and hello.htm > > XSLTForms Javascript classes constructors are obtaining their > properties directly from xf-* attributes and XPath parsing is > then performed. > > No ids are automatically added as previously. > > Extra xf-* attributes and extra xforms-* elements are used to > embed effective HTML rendering elements, for example, > xforms-body or xforms-repeat-item while, before, span or div > elements where used. > > XSLTForms classes for xforms:select and xforms:itemset had to > be partially rewritten. > > SVG support has been basically tested too. > > CSS styling is not anymore based on xforms-* classes but on > custom element names and attribute selectors. For example, the > extra xf-bound attribute, when present, says that the XForms > control is bound to a node, eventually a not relevant one, and > the extra xf-notrelevant attribute can, then, be checked... > > Thank you for your contribution! > > --Alain > > > > > _______________________________________________ > Xsltforms-support mailing list > Xsl...@li... > <mailto:Xsl...@li...> > https://lists.sourceforge.net/lists/listinfo/xsltforms-support > |
|
From: Alain C. <ala...@ag...> - 2020-02-24 13:44:19
|
<!doctype html>
<html>
<head>
<meta charset="UTF-8">
</head>
<body>
<div>
This has been fixed recently and I cannot reproduce this bug with your own test page: please clear browser cache.
</div>
<div>
<br>
</div>
<div>
--Alain
</div>
<blockquote type="cite">
Le 24 février 2020 à 14:19, Steven Pemberton <ste...@cw...> a écrit :
<br>
<br>
<div>
Exciting to be testing the new implementation.
</div>
<div>
<br>
</div>
<div>
I'll start simple.
</div>
<div>
<br>
</div>
<div>
[Enter] in an <input/> doesn't seem to dispatch a DOMActivate.
</div>
<div>
For instance, https://homepages.cwi.nl/~steven/forms/examples/lists/list3.xhtml
</div>
<div>
<br>
</div>
<div>
Steven
</div>
<div>
<br>
</div>
<div>
<br>
</div>
<div>
<br>
</div>
<div>
On Wed, 05 Feb 2020 21:15:57 +0100, Alain Couthures <ala...@ag...> wrote:
<br>
</div>
<br>
<blockquote>
<div style="color: #000000; font-family: Arial, Helvetica,; font-size: 13px; font-style: normal; font-weight: 400; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px;">
Hello,
</div>
<div style="color: #000000; font-family: Arial, Helvetica,; font-size: 13px; font-style: normal; font-weight: 400; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px;">
<br>
</div>
<div style="color: #000000; font-family: Arial, Helvetica,; font-size: 13px; font-style: normal; font-weight: 400; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px;">
Please find a new release for XSLTForms at
<a href="http://www.agencexml.com/1.5beta/xsltforms.zip" class="ox-c64a9ada08-moz-txt-link-abbreviated">www.agencexml.com/1.5beta/xsltforms.zip</a>
</div>
<div style="color: #000000; font-family: Arial, Helvetica,; font-size: 13px; font-style: normal; font-weight: 400; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px;">
<br>
</div>
<div style="color: #000000; font-family: Arial, Helvetica,; font-size: 13px; font-style: normal; font-weight: 400; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px;">
It has not yet been fully tested because a lot of changes have been made and you are welcome to locate remaining issues with your own forms.
</div>
<div style="color: #000000; font-family: Arial, Helvetica,; font-size: 13px; font-style: normal; font-weight: 400; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px;">
<br>
</div>
<div style="color: #000000; font-family: Arial, Helvetica,; font-size: 13px; font-style: normal; font-weight: 400; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px;">
The XSLT part has been reduced to minimal for better performance. Instead of parsing the XPath expressions and transforming all the XForms elements into HTML elements, it basically just transposes the non-HTML elements into sort-of custom elements: xforms:* elements become xforms-* elements with xf-* and ev-* attributes.
</div>
<div style="color: #000000; font-family: Arial, Helvetica,; font-size: 13px; font-style: normal; font-weight: 400; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px;">
<br>
</div>
<div style="color: #000000; font-family: Arial, Helvetica,; font-size: 13px; font-style: normal; font-weight: 400; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px;">
Have a look with your favorite browser debugger! Actually, authors could even prefer to directly write/generate forms with this new notation and forget about the XSLT step. You can compare two sources for the same form: hello.xml and hello.htm
</div>
<div style="color: #000000; font-family: Arial, Helvetica,; font-size: 13px; font-style: normal; font-weight: 400; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px;">
<br>
</div>
<div style="color: #000000; font-family: Arial, Helvetica,; font-size: 13px; font-style: normal; font-weight: 400; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px;">
XSLTForms Javascript classes constructors are obtaining their properties directly from xf-* attributes and XPath parsing is then performed.
</div>
<div style="color: #000000; font-family: Arial, Helvetica,; font-size: 13px; font-style: normal; font-weight: 400; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px;">
<br>
</div>
<div style="color: #000000; font-family: Arial, Helvetica,; font-size: 13px; font-style: normal; font-weight: 400; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px;">
No ids are automatically added as previously.
</div>
<div style="color: #000000; font-family: Arial, Helvetica,; font-size: 13px; font-style: normal; font-weight: 400; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px;">
<br>
</div>
<div style="color: #000000; font-family: Arial, Helvetica,; font-size: 13px; font-style: normal; font-weight: 400; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px;">
Extra xf-* attributes and extra xforms-* elements are used to embed effective HTML rendering elements, for example, xforms-body or xforms-repeat-item while, before, span or div elements where used.
</div>
<div style="color: #000000; font-family: Arial, Helvetica,; font-size: 13px; font-style: normal; font-weight: 400; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px;">
<br>
</div>
<div style="color: #000000; font-family: Arial, Helvetica,; font-size: 13px; font-style: normal; font-weight: 400; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px;">
XSLTForms classes for xforms:select and xforms:itemset had to be partially rewritten.
</div>
<div style="color: #000000; font-family: Arial, Helvetica,; font-size: 13px; font-style: normal; font-weight: 400; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px;">
<br>
</div>
<div style="color: #000000; font-family: Arial, Helvetica,; font-size: 13px; font-style: normal; font-weight: 400; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px;">
SVG support has been basically tested too.
</div>
<div style="color: #000000; font-family: Arial, Helvetica,; font-size: 13px; font-style: normal; font-weight: 400; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px;">
<br>
</div>
<div style="color: #000000; font-family: Arial, Helvetica,; font-size: 13px; font-style: normal; font-weight: 400; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px;">
CSS styling is not anymore based on xforms-* classes but on custom element names and attribute selectors. For example, the extra xf-bound attribute, when present, says that the XForms control is bound to a node, eventually a not relevant one, and the extra xf-notrelevant attribute can, then, be checked...
</div>
<div style="color: #000000; font-family: Arial, Helvetica,; font-size: 13px; font-style: normal; font-weight: 400; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px;">
<br>
</div>
<div style="color: #000000; font-family: Arial, Helvetica,; font-size: 13px; font-style: normal; font-weight: 400; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px;">
Thank you for your contribution!
</div>
<div style="color: #000000; font-family: Arial, Helvetica,; font-size: 13px; font-style: normal; font-weight: 400; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px;">
<br>
</div>
<div style="color: #000000; font-family: Arial, Helvetica,; font-size: 13px; font-style: normal; font-weight: 400; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px;">
--Alain
</div>
</blockquote>
<br>
<br>
<br>
</blockquote>
<div class="default-style">
<br>
</div>
</body>
</html>
|
|
From: Tim T. <tim...@gm...> - 2020-02-24 13:40:13
|
Steven, You'll want to download the .zip file again. This bug seems to have been resolved (see https://sourceforge.net/p/xsltforms/mailman/message/36926131/ ). Cheers, Tim -- Tim A. Thompson Discovery Metadata Librarian Yale University Library On Mon, Feb 24, 2020 at 8:31 AM Steven Pemberton <ste...@cw...> wrote: > Exciting to be testing the new implementation. > > I'll start simple. > > [Enter] in an <input/> doesn't seem to dispatch a DOMActivate. > For instance, > https://homepages.cwi.nl/~steven/forms/examples/lists/list3.xhtml > > Steven > > > > On Wed, 05 Feb 2020 21:15:57 +0100, Alain Couthures < > ala...@ag...> wrote: > > Hello, > > Please find a new release for XSLTForms at > www.agencexml.com/1.5beta/xsltforms.zip > > It has not yet been fully tested because a lot of changes have been made > and you are welcome to locate remaining issues with your own forms. > > The XSLT part has been reduced to minimal for better performance. Instead > of parsing the XPath expressions and transforming all the XForms elements > into HTML elements, it basically just transposes the non-HTML elements into > sort-of custom elements: xforms:* elements become xforms-* elements with > xf-* and ev-* attributes. > > Have a look with your favorite browser debugger! Actually, authors could > even prefer to directly write/generate forms with this new notation and > forget about the XSLT step. You can compare two sources for the same form: > hello.xml and hello.htm > > XSLTForms Javascript classes constructors are obtaining their properties > directly from xf-* attributes and XPath parsing is then performed. > > No ids are automatically added as previously. > > Extra xf-* attributes and extra xforms-* elements are used to embed > effective HTML rendering elements, for example, xforms-body or > xforms-repeat-item while, before, span or div elements where used. > > XSLTForms classes for xforms:select and xforms:itemset had to be partially > rewritten. > > SVG support has been basically tested too. > > CSS styling is not anymore based on xforms-* classes but on custom element > names and attribute selectors. For example, the extra xf-bound attribute, > when present, says that the XForms control is bound to a node, eventually a > not relevant one, and the extra xf-notrelevant attribute can, then, be > checked... > > Thank you for your contribution! > > --Alain > > > > > _______________________________________________ > Xsltforms-support mailing list > Xsl...@li... > https://lists.sourceforge.net/lists/listinfo/xsltforms-support > |
|
From: Steven P. <ste...@cw...> - 2020-02-24 13:39:21
|
OK thanks. New one: operator mod not recognised? Steven On Mon, 24 Feb 2020 14:30:56 +0100, Alain Couthures <ala...@ag...> wrote: > This has been fixed recently and I cannot reproduce this bug with your > own test page: please clear browser cache. > --Alain >> Le 24 février 2020 à 14:19, Steven Pemberton <ste...@cw...> >> a écrit : >> Exciting to be testing the new implementation. >> I'll start simple. >> [Enter] in an <input/> doesn't seem to dispatch a DOMActivate.For >> instance, >> https://homepages.cwi.nl/~steven/forms/examples/lists/list3.xhtml >> Steven >> >> >> On Wed, 05 Feb 2020 21:15:57 +0100, Alain Couthures >> <ala...@ag...> wrote: >>> Hello, >>> Please find a new release for XSLTForms at >>> www.agencexml.com/1.5beta/xsltforms.zip >>> It has not yet been fully tested because a lot of changes have been >>> made and you are >>>welcome to locate remaining issues with your own >>> forms. >>> The XSLT part has been reduced to minimal for better performance. >>> Instead of parsing the >>>XPath expressions and transforming all the >>> XForms elements into HTML elements, it >>>basically just transposes >>> the non-HTML elements into sort-of custom elements: xforms:* >>> >>>elements become xforms-* elements with xf-* and ev-* attributes. >>> Have a look with your favorite browser debugger! Actually, authors >>> could even prefer to >>>directly write/generate forms with this new >>> notation and forget about the XSLT step. You >>>can compare two >>> sources for the same form: hello.xml and hello.htm >>> XSLTForms Javascript classes constructors are obtaining their >>> properties directly from >>>xf-* attributes and XPath parsing is then >>> performed. >>> No ids are automatically added as previously. >>> Extra xf-* attributes and extra xforms-* elements are used to embed >>> effective HTML >>>rendering elements, for example, xforms-body or >>> xforms-repeat-item while, before, span >>>or div elements where used. >>> XSLTForms classes for xforms:select and xforms:itemset had to be >>> partially rewritten. >>> SVG support has been basically tested too. >>> CSS styling is not anymore based on xforms-* classes but on custom >>> element names and >>>attribute selectors. For example, the extra >>> xf-bound attribute, when present, says that >>>the XForms control is >>> bound to a node, eventually a not relevant one, and the extra >>> xf->>>notrelevant attribute can, then, be checked... >>> Thank you for your contribution! >>> --Alain >> >> >> > |
|
From: Steven P. <ste...@cw...> - 2020-02-24 13:31:33
|
Exciting to be testing the new implementation. I'll start simple. [Enter] in an <input/> doesn't seem to dispatch a DOMActivate. For instance, https://homepages.cwi.nl/~steven/forms/examples/lists/list3.xhtml Steven On Wed, 05 Feb 2020 21:15:57 +0100, Alain Couthures <ala...@ag...> wrote: > Hello, > > Please find a new release for XSLTForms at > www.agencexml.com/1.5beta/xsltforms.zip > > It has not yet been fully tested because a lot of changes have been made > and you are welcome to locate remaining issues with your own forms. > > The XSLT part has been reduced to minimal for better performance. > Instead of parsing the XPath expressions and transforming all the XForms > >elements into HTML elements, it basically just transposes the non-HTML > elements into sort-of custom elements: xforms:* elements become xforms-* > >elements with xf-* and ev-* attributes. > > Have a look with your favorite browser debugger! Actually, authors could > even prefer to directly write/generate forms with this new notation and > forget >about the XSLT step. You can compare two sources for the same > form: hello.xml and hello.htm > > XSLTForms Javascript classes constructors are obtaining their properties > directly from xf-* attributes and XPath parsing is then performed. > > No ids are automatically added as previously. > > Extra xf-* attributes and extra xforms-* elements are used to embed > effective HTML rendering elements, for example, xforms-body or > xforms-repeat->item while, before, span or div elements where used. > > XSLTForms classes for xforms:select and xforms:itemset had to be > partially rewritten. > > SVG support has been basically tested too. > > CSS styling is not anymore based on xforms-* classes but on custom > element names and attribute selectors. For example, the extra xf-bound > >attribute, when present, says that the XForms control is bound to a > node, eventually a not relevant one, and the extra xf-notrelevant > attribute can, then, >be checked... > > Thank you for your contribution! > > --Alain |
|
From: Tim T. <tim...@gm...> - 2020-02-17 21:57:04
|
Thank you, Alain! If you don't mind, I have another test form that works in XSLTForms 1.4 but not 1.5beta. This one is testing xf:var again. In 1.5beta, an error is thrown: Assertion failed: Binding evaluation didn't returned a nodeset but '1' for XPath expression: count(ancestor::item) https://www.tat2.io/basex2/static/xsltforms_var_test_2020-02-17_with_var_1.5beta.xml In 1.4, the form works as expected: https://www.tat2.io/basex2/static/xsltforms_var_test_2020-02-17_with_var_1.4.xml Best regards, Tim -- Tim A. Thompson Discovery Metadata Librarian Yale University Library On Mon, Feb 17, 2020 at 3:54 PM Alain Couthures < ala...@ag...> wrote: > Hello Tim, > > This issue is now fixed (and some more actually...). > > The new build can be downloaded at the same URL: > www.agencexml.com/1.5beta/xsltforms.zip > > Thank you again for your contributions! > > --Alain > > Le 15/02/2020 à 01:15, Tim Thompson a écrit : > > Hello, Alain, > > Another test for you: > > In XSLTForms 1.5beta, the DOMActivate event is not being evoked for input > controls. See this test form: > > > https://www.tat2.io/basex2/static/xsltforms_DOMActivate_test_2020-02-14_1-5beta.xml > > Pressing "enter" in the input field does nothing, whereas clicking the > button triggers the event. > > Compare this to a form running XSLTForms 1.4: > > > https://www.tat2.io/basex2/static/xsltforms_DOMActivate_test_2020-02-14_1-4.xml > > Here, the DOMActivate enter works in both the input field with the "enter" > key and with the button. > > All best, > Tim > > -- > Tim A. Thompson > Discovery Metadata Librarian > Yale University Library > > On Wed, Feb 12, 2020 at 5:51 PM Tim Thompson <tim...@gm...> wrote: > >> Great! Works perfectly now. Looking forward to the XML Prague proceedings >> and video for your presentation with Steven Pemberton. >> >> Thanks again, >> Tim >> >> >> -- >> Tim A. Thompson >> Discovery Metadata Librarian >> Yale University Library >> >> >> >> On Wed, Feb 12, 2020 at 4:00 PM Alain Couthures < >> ala...@ag...> wrote: >> >>> Hello Tim, >>> >>> (1) The xf:group processing was not correct: in the new approach, an >>> xf-bound attribute has to be automatically added to each xforms-* element >>> when xf-ref (or xf-bind) is evaluated as a non empty nodeset. CSS attribute >>> selectors are, then, used to display/hide xforms-* elements accordingly. >>> >>> (2) The xf:var processing was not functional: it should now work, at >>> least, outside of actions. >>> >>> (3) The profiler is actually just another external form: I have added >>> the corresponding file into the updated .zip file at >>> www.agencexml.com/1.5beta/xsltforms.zip >>> >>> Thank you very much for your contributions! >>> >>> --Alain >>> >>> Le 09/02/2020 à 20:51, Tim Thompson a écrit : >>> >>> Hello, Alain, >>> >>> I've been testing an existing form with the new release and have some >>> feedback. First, the performance improvement seems impressive, and CSS >>> styling with Bootstrap now seems much easier. Thank you! >>> >>> I did notice some issues after testing, however. >>> >>> (1) >>> There seems to be a bug with XPath predicate filtering in xf:group >>> elements. For example, a group binding such as <xf:group >>> ref="instance('response')/response[*]">...</xf:group>, where the response >>> element should initially be empty (before a submission is executed) does >>> not seem to work. >>> >>> See the test form copied below. Example form at: >>> https://www.tat2.io/basex2/static/xsltforms_test_2020-02-09.xml >>> >>> (2) >>> I see that the xforms:var element is not currently supported. When >>> loading a form with an XForms variable defined, I get an error message: >>> >>> Error initializing: >>> >>> xforms:var is not supported >>> >>> (3) >>> I also see that the XSLTForms Profiler does not seem to be available. >>> When I try to open it, I get an error: >>> >>> File not found (404): >>> https://www.tat2.io/basex2/static/xsltforms_profiler.xhtml >>> >>> >>> *--Test form for XPath predicate bug--* >>> >>> <?xml-stylesheet type="text/xsl" href="..."?> >>> <html xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd=" >>> http://www.w3.org/2001/XMLSchema" xmlns:xf=" >>> http://www.w3.org/2002/xforms" xmlns:h="http://www.w3.org/1999/xhtml" >>> xmlns:ev="http://www.w3.org/2001/xml-events" xmlns=" >>> http://www.w3.org/1999/xhtml"> >>> <head> >>> <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /> >>> <title>XForms/XPath Predicate Test</title> >>> <style type="text/css"/> >>> <model xmlns="http://www.w3.org/2002/xforms" id="m"> >>> <instance id="default"> >>> <data xmlns=""> >>> <default/> >>> </data> >>> </instance> >>> <instance id="response"> >>> <data xmlns=""> >>> <response/> >>> </data> >>> </instance> >>> <instance id="response-test"> >>> <data xmlns=""> >>> <response> >>> <testing>Testing</testing> >>> </response> >>> </data> >>> </instance> >>> </model> >>> </head> >>> <body> >>> <div class="container-fluid"> >>> <hr class="blue" /> >>> <h1>XForms/XPath predicate test</h1> >>> <xf:group ref="instance('response')/response[*]"> >>> <h2 style="color: red;">This should not display!</h2> >>> <xf:output value="concat('Value of "serialize(.)": ', >>> serialize(.))"/> >>> </xf:group> >>> <xf:group ref="instance('response-test')/response[*]"> >>> <h2 style="color: blue;">This should display.</h2> >>> <xf:output value="concat('Value of "serialize(.)": ', >>> serialize(.))"/> >>> </xf:group> >>> </div> >>> </body> >>> </html> >>> >>> >>> >>> -- >>> Tim A. Thompson >>> Discovery Metadata Librarian >>> Yale University Library >>> >>> On Sun, Feb 9, 2020 at 11:06 AM Tim Thompson <tim...@gm...> wrote: >>> >>>> Hello, Alain, >>>> >>>> Congratulations on this milestone! I am very eager to try and test the >>>> new release. Is XSLTForms now using Fleur for XPath parsing? Does this mean >>>> that XPath 3.0 functions are now supported? I guess I can test this myself >>>> :) >>>> >>>> It's quite amazing to see the xsltforms.xsl file down to just over 500 >>>> lines. >>>> >>>> Thanks again for all your work. >>>> >>>> Best regards, >>>> Tim >>>> >>>> >>>> -- >>>> Tim A. Thompson >>>> Discovery Metadata Librarian >>>> Yale University Library >>>> >>>> On Wed, Feb 5, 2020 at 3:16 PM Alain Couthures < >>>> ala...@ag...> wrote: >>>> >>>>> Hello, >>>>> >>>>> Please find a new release for XSLTForms at >>>>> www.agencexml.com/1.5beta/xsltforms.zip >>>>> >>>>> It has not yet been fully tested because a lot of changes have been >>>>> made and you are welcome to locate remaining issues with your own forms. >>>>> >>>>> The XSLT part has been reduced to minimal for better performance. >>>>> Instead of parsing the XPath expressions and transforming all the XForms >>>>> elements into HTML elements, it basically just transposes the non-HTML >>>>> elements into sort-of custom elements: xforms:* elements become xforms-* >>>>> elements with xf-* and ev-* attributes. >>>>> >>>>> Have a look with your favorite browser debugger! Actually, authors >>>>> could even prefer to directly write/generate forms with this new notation >>>>> and forget about the XSLT step. You can compare two sources for the same >>>>> form: hello.xml and hello.htm >>>>> >>>>> XSLTForms Javascript classes constructors are obtaining their >>>>> properties directly from xf-* attributes and XPath parsing is then >>>>> performed. >>>>> >>>>> No ids are automatically added as previously. >>>>> >>>>> Extra xf-* attributes and extra xforms-* elements are used to embed >>>>> effective HTML rendering elements, for example, xforms-body or >>>>> xforms-repeat-item while, before, span or div elements where used. >>>>> >>>>> XSLTForms classes for xforms:select and xforms:itemset had to be >>>>> partially rewritten. >>>>> >>>>> SVG support has been basically tested too. >>>>> >>>>> CSS styling is not anymore based on xforms-* classes but on custom >>>>> element names and attribute selectors. For example, the extra xf-bound >>>>> attribute, when present, says that the XForms control is bound to a node, >>>>> eventually a not relevant one, and the extra xf-notrelevant attribute can, >>>>> then, be checked... >>>>> >>>>> Thank you for your contribution! >>>>> >>>>> --Alain >>>>> _______________________________________________ >>>>> Xsltforms-support mailing list >>>>> Xsl...@li... >>>>> https://lists.sourceforge.net/lists/listinfo/xsltforms-support >>>>> >>>> >>> > |
|
From: Alain C. <ala...@ag...> - 2020-02-17 20:54:14
|
Hello Tim, This issue is now fixed (and some more actually...). The new build can be downloaded at the same URL: www.agencexml.com/1.5beta/xsltforms.zip <http://www.agencexml.com/1.5beta/xsltforms.zip> Thank you again for your contributions! --Alain Le 15/02/2020 à 01:15, Tim Thompson a écrit : > Hello, Alain, > > Another test for you: > > In XSLTForms 1.5beta, the DOMActivate event is not being evoked for > input controls. See this test form: > > https://www.tat2.io/basex2/static/xsltforms_DOMActivate_test_2020-02-14_1-5beta.xml > > Pressing "enter" in the input field does nothing, whereas clicking the > button triggers the event. > > Compare this to a form running XSLTForms 1.4: > > https://www.tat2.io/basex2/static/xsltforms_DOMActivate_test_2020-02-14_1-4.xml > > Here, the DOMActivate enter works in both the input field with the > "enter" key and with the button. > > All best, > Tim > > -- > Tim A. Thompson > Discovery Metadata Librarian > Yale University Library > > On Wed, Feb 12, 2020 at 5:51 PM Tim Thompson <tim...@gm... > <mailto:tim...@gm...>> wrote: > > Great! Works perfectly now. Looking forward to the XML Prague > proceedings and video for your presentation with Steven Pemberton. > > Thanks again, > Tim > > > -- > Tim A. Thompson > Discovery Metadata Librarian > Yale University Library > > > > On Wed, Feb 12, 2020 at 4:00 PM Alain Couthures > <ala...@ag... > <mailto:ala...@ag...>> wrote: > > Hello Tim, > > (1) The xf:group processing was not correct: in the new > approach, an xf-bound attribute has to be automatically added > to each xforms-* element when xf-ref (or xf-bind) is evaluated > as a non empty nodeset. CSS attribute selectors are, then, > used to display/hide xforms-* elements accordingly. > > (2) The xf:var processing was not functional: it should now > work, at least, outside of actions. > > (3) The profiler is actually just another external form: I > have added the corresponding file into the updated .zip file > at www.agencexml.com/1.5beta/xsltforms.zip > <http://www.agencexml.com/1.5beta/xsltforms.zip> > > Thank you very much for your contributions! > > --Alain > > Le 09/02/2020 à 20:51, Tim Thompson a écrit : >> Hello, Alain, >> >> I've been testing an existing form with the new release and >> have some feedback. First, the performance improvement seems >> impressive, and CSS styling with Bootstrap now seems much >> easier. Thank you! >> >> I did notice some issues after testing, however. >> >> (1) >> There seems to be a bug with XPath predicate filtering in >> xf:group elements. For example, a group binding such as >> <xf:group >> ref="instance('response')/response[*]">...</xf:group>, where >> the response element should initially be empty (before a >> submission is executed) does not seem to work. >> >> See the test form copied below. Example form at: >> https://www.tat2.io/basex2/static/xsltforms_test_2020-02-09.xml >> >> (2) >> I see that the xforms:var element is not currently supported. >> When loading a form with an XForms variable defined, I get an >> error message: >> >> Error initializing: >> >> xforms:var is not supported >> >> (3) >> I also see that the XSLTForms Profiler does not seem to be >> available. When I try to open it, I get an error: >> >> File not found (404): >> https://www.tat2.io/basex2/static/xsltforms_profiler.xhtml >> >> * >> * >> *--Test form for XPath predicate bug--* >> * >> * >> <?xml-stylesheet type="text/xsl" href="..."?> >> <html xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" >> xmlns:xsd="http://www.w3.org/2001/XMLSchema" >> xmlns:xf="http://www.w3.org/2002/xforms" >> xmlns:h="http://www.w3.org/1999/xhtml" >> xmlns:ev="http://www.w3.org/2001/xml-events" >> xmlns="http://www.w3.org/1999/xhtml"> >> <head> >> <meta http-equiv="Content-Type" content="text/html; >> charset=UTF-8" /> >> <title>XForms/XPath Predicate Test</title> >> <style type="text/css"/> >> <model xmlns="http://www.w3.org/2002/xforms" id="m"> >> <instance id="default"> >> <data xmlns=""> >> <default/> >> </data> >> </instance> >> <instance id="response"> >> <data xmlns=""> >> <response/> >> </data> >> </instance> >> <instance id="response-test"> >> <data xmlns=""> >> <response> >> <testing>Testing</testing> >> </response> >> </data> >> </instance> >> </model> >> </head> >> <body> >> <div class="container-fluid"> >> <hr class="blue" /> >> <h1>XForms/XPath predicate test</h1> >> <xf:group ref="instance('response')/response[*]"> >> <h2 style="color: red;">This should not display!</h2> >> <xf:output value="concat('Value of >> "serialize(.)": ', serialize(.))"/> >> </xf:group> >> <xf:group ref="instance('response-test')/response[*]"> >> <h2 style="color: blue;">This should display.</h2> >> <xf:output value="concat('Value of >> "serialize(.)": ', serialize(.))"/> >> </xf:group> >> </div> >> </body> >> </html> >> >> >> >> -- >> Tim A. Thompson >> Discovery Metadata Librarian >> Yale University Library >> >> On Sun, Feb 9, 2020 at 11:06 AM Tim Thompson >> <tim...@gm... <mailto:tim...@gm...>> wrote: >> >> Hello, Alain, >> >> Congratulations on this milestone! I am very eager to try >> and test the new release. Is XSLTForms now using Fleur >> for XPath parsing? Does this mean that XPath 3.0 >> functions are now supported? I guess I can test this >> myself :) >> >> It's quite amazing to see the xsltforms.xsl file down to >> just over 500 lines. >> >> Thanks again for all your work. >> >> Best regards, >> Tim >> >> >> -- >> Tim A. Thompson >> Discovery Metadata Librarian >> Yale University Library >> >> On Wed, Feb 5, 2020 at 3:16 PM Alain Couthures >> <ala...@ag... >> <mailto:ala...@ag...>> wrote: >> >> Hello, >> >> Please find a new release for XSLTForms at >> www.agencexml.com/1.5beta/xsltforms.zip >> <http://www.agencexml.com/1.5beta/xsltforms.zip> >> >> It has not yet been fully tested because a lot of >> changes have been made and you are welcome to locate >> remaining issues with your own forms. >> >> The XSLT part has been reduced to minimal for better >> performance. Instead of parsing the XPath expressions >> and transforming all the XForms elements into HTML >> elements, it basically just transposes the non-HTML >> elements into sort-of custom elements: xforms:* >> elements become xforms-* elements with xf-* and ev-* >> attributes. >> >> Have a look with your favorite browser debugger! >> Actually, authors could even prefer to directly >> write/generate forms with this new notation and >> forget about the XSLT step. You can compare two >> sources for the same form: hello.xml and hello.htm >> >> XSLTForms Javascript classes constructors are >> obtaining their properties directly from xf-* >> attributes and XPath parsing is then performed. >> >> No ids are automatically added as previously. >> >> Extra xf-* attributes and extra xforms-* elements are >> used to embed effective HTML rendering elements, for >> example, xforms-body or xforms-repeat-item while, >> before, span or div elements where used. >> >> XSLTForms classes for xforms:select and >> xforms:itemset had to be partially rewritten. >> >> SVG support has been basically tested too. >> >> CSS styling is not anymore based on xforms-* classes >> but on custom element names and attribute selectors. >> For example, the extra xf-bound attribute, when >> present, says that the XForms control is bound to a >> node, eventually a not relevant one, and the extra >> xf-notrelevant attribute can, then, be checked... >> >> Thank you for your contribution! >> >> --Alain >> _______________________________________________ >> Xsltforms-support mailing list >> Xsl...@li... >> <mailto:Xsl...@li...> >> https://lists.sourceforge.net/lists/listinfo/xsltforms-support >> > |
|
From: Tim T. <tim...@gm...> - 2020-02-15 00:16:31
|
Hello, Alain, Another test for you: In XSLTForms 1.5beta, the DOMActivate event is not being evoked for input controls. See this test form: https://www.tat2.io/basex2/static/xsltforms_DOMActivate_test_2020-02-14_1-5beta.xml Pressing "enter" in the input field does nothing, whereas clicking the button triggers the event. Compare this to a form running XSLTForms 1.4: https://www.tat2.io/basex2/static/xsltforms_DOMActivate_test_2020-02-14_1-4.xml Here, the DOMActivate enter works in both the input field with the "enter" key and with the button. All best, Tim -- Tim A. Thompson Discovery Metadata Librarian Yale University Library On Wed, Feb 12, 2020 at 5:51 PM Tim Thompson <tim...@gm...> wrote: > Great! Works perfectly now. Looking forward to the XML Prague proceedings > and video for your presentation with Steven Pemberton. > > Thanks again, > Tim > > > -- > Tim A. Thompson > Discovery Metadata Librarian > Yale University Library > > > > On Wed, Feb 12, 2020 at 4:00 PM Alain Couthures < > ala...@ag...> wrote: > >> Hello Tim, >> >> (1) The xf:group processing was not correct: in the new approach, an >> xf-bound attribute has to be automatically added to each xforms-* element >> when xf-ref (or xf-bind) is evaluated as a non empty nodeset. CSS attribute >> selectors are, then, used to display/hide xforms-* elements accordingly. >> >> (2) The xf:var processing was not functional: it should now work, at >> least, outside of actions. >> >> (3) The profiler is actually just another external form: I have added the >> corresponding file into the updated .zip file at >> www.agencexml.com/1.5beta/xsltforms.zip >> >> Thank you very much for your contributions! >> >> --Alain >> >> Le 09/02/2020 à 20:51, Tim Thompson a écrit : >> >> Hello, Alain, >> >> I've been testing an existing form with the new release and have some >> feedback. First, the performance improvement seems impressive, and CSS >> styling with Bootstrap now seems much easier. Thank you! >> >> I did notice some issues after testing, however. >> >> (1) >> There seems to be a bug with XPath predicate filtering in xf:group >> elements. For example, a group binding such as <xf:group >> ref="instance('response')/response[*]">...</xf:group>, where the response >> element should initially be empty (before a submission is executed) does >> not seem to work. >> >> See the test form copied below. Example form at: >> https://www.tat2.io/basex2/static/xsltforms_test_2020-02-09.xml >> >> (2) >> I see that the xforms:var element is not currently supported. When >> loading a form with an XForms variable defined, I get an error message: >> >> Error initializing: >> >> xforms:var is not supported >> >> (3) >> I also see that the XSLTForms Profiler does not seem to be available. >> When I try to open it, I get an error: >> >> File not found (404): >> https://www.tat2.io/basex2/static/xsltforms_profiler.xhtml >> >> >> *--Test form for XPath predicate bug--* >> >> <?xml-stylesheet type="text/xsl" href="..."?> >> <html xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd=" >> http://www.w3.org/2001/XMLSchema" xmlns:xf="http://www.w3.org/2002/xforms" >> xmlns:h="http://www.w3.org/1999/xhtml" xmlns:ev=" >> http://www.w3.org/2001/xml-events" xmlns="http://www.w3.org/1999/xhtml"> >> <head> >> <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /> >> <title>XForms/XPath Predicate Test</title> >> <style type="text/css"/> >> <model xmlns="http://www.w3.org/2002/xforms" id="m"> >> <instance id="default"> >> <data xmlns=""> >> <default/> >> </data> >> </instance> >> <instance id="response"> >> <data xmlns=""> >> <response/> >> </data> >> </instance> >> <instance id="response-test"> >> <data xmlns=""> >> <response> >> <testing>Testing</testing> >> </response> >> </data> >> </instance> >> </model> >> </head> >> <body> >> <div class="container-fluid"> >> <hr class="blue" /> >> <h1>XForms/XPath predicate test</h1> >> <xf:group ref="instance('response')/response[*]"> >> <h2 style="color: red;">This should not display!</h2> >> <xf:output value="concat('Value of "serialize(.)": ', >> serialize(.))"/> >> </xf:group> >> <xf:group ref="instance('response-test')/response[*]"> >> <h2 style="color: blue;">This should display.</h2> >> <xf:output value="concat('Value of "serialize(.)": ', >> serialize(.))"/> >> </xf:group> >> </div> >> </body> >> </html> >> >> >> >> -- >> Tim A. Thompson >> Discovery Metadata Librarian >> Yale University Library >> >> On Sun, Feb 9, 2020 at 11:06 AM Tim Thompson <tim...@gm...> wrote: >> >>> Hello, Alain, >>> >>> Congratulations on this milestone! I am very eager to try and test the >>> new release. Is XSLTForms now using Fleur for XPath parsing? Does this mean >>> that XPath 3.0 functions are now supported? I guess I can test this myself >>> :) >>> >>> It's quite amazing to see the xsltforms.xsl file down to just over 500 >>> lines. >>> >>> Thanks again for all your work. >>> >>> Best regards, >>> Tim >>> >>> >>> -- >>> Tim A. Thompson >>> Discovery Metadata Librarian >>> Yale University Library >>> >>> On Wed, Feb 5, 2020 at 3:16 PM Alain Couthures < >>> ala...@ag...> wrote: >>> >>>> Hello, >>>> >>>> Please find a new release for XSLTForms at >>>> www.agencexml.com/1.5beta/xsltforms.zip >>>> >>>> It has not yet been fully tested because a lot of changes have been >>>> made and you are welcome to locate remaining issues with your own forms. >>>> >>>> The XSLT part has been reduced to minimal for better performance. >>>> Instead of parsing the XPath expressions and transforming all the XForms >>>> elements into HTML elements, it basically just transposes the non-HTML >>>> elements into sort-of custom elements: xforms:* elements become xforms-* >>>> elements with xf-* and ev-* attributes. >>>> >>>> Have a look with your favorite browser debugger! Actually, authors >>>> could even prefer to directly write/generate forms with this new notation >>>> and forget about the XSLT step. You can compare two sources for the same >>>> form: hello.xml and hello.htm >>>> >>>> XSLTForms Javascript classes constructors are obtaining their >>>> properties directly from xf-* attributes and XPath parsing is then >>>> performed. >>>> >>>> No ids are automatically added as previously. >>>> >>>> Extra xf-* attributes and extra xforms-* elements are used to embed >>>> effective HTML rendering elements, for example, xforms-body or >>>> xforms-repeat-item while, before, span or div elements where used. >>>> >>>> XSLTForms classes for xforms:select and xforms:itemset had to be >>>> partially rewritten. >>>> >>>> SVG support has been basically tested too. >>>> >>>> CSS styling is not anymore based on xforms-* classes but on custom >>>> element names and attribute selectors. For example, the extra xf-bound >>>> attribute, when present, says that the XForms control is bound to a node, >>>> eventually a not relevant one, and the extra xf-notrelevant attribute can, >>>> then, be checked... >>>> >>>> Thank you for your contribution! >>>> >>>> --Alain >>>> _______________________________________________ >>>> Xsltforms-support mailing list >>>> Xsl...@li... >>>> https://lists.sourceforge.net/lists/listinfo/xsltforms-support >>>> >>> >> |
|
From: Tim T. <tim...@gm...> - 2020-02-12 22:51:44
|
Great! Works perfectly now. Looking forward to the XML Prague proceedings and video for your presentation with Steven Pemberton. Thanks again, Tim -- Tim A. Thompson Discovery Metadata Librarian Yale University Library On Wed, Feb 12, 2020 at 4:00 PM Alain Couthures < ala...@ag...> wrote: > Hello Tim, > > (1) The xf:group processing was not correct: in the new approach, an > xf-bound attribute has to be automatically added to each xforms-* element > when xf-ref (or xf-bind) is evaluated as a non empty nodeset. CSS attribute > selectors are, then, used to display/hide xforms-* elements accordingly. > > (2) The xf:var processing was not functional: it should now work, at > least, outside of actions. > > (3) The profiler is actually just another external form: I have added the > corresponding file into the updated .zip file at > www.agencexml.com/1.5beta/xsltforms.zip > > Thank you very much for your contributions! > > --Alain > > Le 09/02/2020 à 20:51, Tim Thompson a écrit : > > Hello, Alain, > > I've been testing an existing form with the new release and have some > feedback. First, the performance improvement seems impressive, and CSS > styling with Bootstrap now seems much easier. Thank you! > > I did notice some issues after testing, however. > > (1) > There seems to be a bug with XPath predicate filtering in xf:group > elements. For example, a group binding such as <xf:group > ref="instance('response')/response[*]">...</xf:group>, where the response > element should initially be empty (before a submission is executed) does > not seem to work. > > See the test form copied below. Example form at: > https://www.tat2.io/basex2/static/xsltforms_test_2020-02-09.xml > > (2) > I see that the xforms:var element is not currently supported. When loading > a form with an XForms variable defined, I get an error message: > > Error initializing: > > xforms:var is not supported > > (3) > I also see that the XSLTForms Profiler does not seem to be available. When > I try to open it, I get an error: > > File not found (404): > https://www.tat2.io/basex2/static/xsltforms_profiler.xhtml > > > *--Test form for XPath predicate bug--* > > <?xml-stylesheet type="text/xsl" href="..."?> > <html xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd=" > http://www.w3.org/2001/XMLSchema" xmlns:xf="http://www.w3.org/2002/xforms" > xmlns:h="http://www.w3.org/1999/xhtml" xmlns:ev=" > http://www.w3.org/2001/xml-events" xmlns="http://www.w3.org/1999/xhtml"> > <head> > <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /> > <title>XForms/XPath Predicate Test</title> > <style type="text/css"/> > <model xmlns="http://www.w3.org/2002/xforms" id="m"> > <instance id="default"> > <data xmlns=""> > <default/> > </data> > </instance> > <instance id="response"> > <data xmlns=""> > <response/> > </data> > </instance> > <instance id="response-test"> > <data xmlns=""> > <response> > <testing>Testing</testing> > </response> > </data> > </instance> > </model> > </head> > <body> > <div class="container-fluid"> > <hr class="blue" /> > <h1>XForms/XPath predicate test</h1> > <xf:group ref="instance('response')/response[*]"> > <h2 style="color: red;">This should not display!</h2> > <xf:output value="concat('Value of "serialize(.)": ', > serialize(.))"/> > </xf:group> > <xf:group ref="instance('response-test')/response[*]"> > <h2 style="color: blue;">This should display.</h2> > <xf:output value="concat('Value of "serialize(.)": ', > serialize(.))"/> > </xf:group> > </div> > </body> > </html> > > > > -- > Tim A. Thompson > Discovery Metadata Librarian > Yale University Library > > On Sun, Feb 9, 2020 at 11:06 AM Tim Thompson <tim...@gm...> wrote: > >> Hello, Alain, >> >> Congratulations on this milestone! I am very eager to try and test the >> new release. Is XSLTForms now using Fleur for XPath parsing? Does this mean >> that XPath 3.0 functions are now supported? I guess I can test this myself >> :) >> >> It's quite amazing to see the xsltforms.xsl file down to just over 500 >> lines. >> >> Thanks again for all your work. >> >> Best regards, >> Tim >> >> >> -- >> Tim A. Thompson >> Discovery Metadata Librarian >> Yale University Library >> >> On Wed, Feb 5, 2020 at 3:16 PM Alain Couthures < >> ala...@ag...> wrote: >> >>> Hello, >>> >>> Please find a new release for XSLTForms at >>> www.agencexml.com/1.5beta/xsltforms.zip >>> >>> It has not yet been fully tested because a lot of changes have been made >>> and you are welcome to locate remaining issues with your own forms. >>> >>> The XSLT part has been reduced to minimal for better performance. >>> Instead of parsing the XPath expressions and transforming all the XForms >>> elements into HTML elements, it basically just transposes the non-HTML >>> elements into sort-of custom elements: xforms:* elements become xforms-* >>> elements with xf-* and ev-* attributes. >>> >>> Have a look with your favorite browser debugger! Actually, authors could >>> even prefer to directly write/generate forms with this new notation and >>> forget about the XSLT step. You can compare two sources for the same form: >>> hello.xml and hello.htm >>> >>> XSLTForms Javascript classes constructors are obtaining their properties >>> directly from xf-* attributes and XPath parsing is then performed. >>> >>> No ids are automatically added as previously. >>> >>> Extra xf-* attributes and extra xforms-* elements are used to embed >>> effective HTML rendering elements, for example, xforms-body or >>> xforms-repeat-item while, before, span or div elements where used. >>> >>> XSLTForms classes for xforms:select and xforms:itemset had to be >>> partially rewritten. >>> >>> SVG support has been basically tested too. >>> >>> CSS styling is not anymore based on xforms-* classes but on custom >>> element names and attribute selectors. For example, the extra xf-bound >>> attribute, when present, says that the XForms control is bound to a node, >>> eventually a not relevant one, and the extra xf-notrelevant attribute can, >>> then, be checked... >>> >>> Thank you for your contribution! >>> >>> --Alain >>> _______________________________________________ >>> Xsltforms-support mailing list >>> Xsl...@li... >>> https://lists.sourceforge.net/lists/listinfo/xsltforms-support >>> >> > |
|
From: Alain C. <ala...@ag...> - 2020-02-12 21:13:47
|
Hello Tim, (1) The xf:group processing was not correct: in the new approach, an xf-bound attribute has to be automatically added to each xforms-* element when xf-ref (or xf-bind) is evaluated as a non empty nodeset. CSS attribute selectors are, then, used to display/hide xforms-* elements accordingly. (2) The xf:var processing was not functional: it should now work, at least, outside of actions. (3) The profiler is actually just another external form: I have added the corresponding file into the updated .zip file at www.agencexml.com/1.5beta/xsltforms.zip Thank you very much for your contributions! --Alain Le 09/02/2020 à 20:51, Tim Thompson a écrit : > Hello, Alain, > > I've been testing an existing form with the new release and have some > feedback. First, the performance improvement seems impressive, and CSS > styling with Bootstrap now seems much easier. Thank you! > > I did notice some issues after testing, however. > > (1) > There seems to be a bug with XPath predicate filtering in xf:group > elements. For example, a group binding such as <xf:group > ref="instance('response')/response[*]">...</xf:group>, where the > response element should initially be empty (before a submission is > executed) does not seem to work. > > See the test form copied below. Example form at: > https://www.tat2.io/basex2/static/xsltforms_test_2020-02-09.xml > > (2) > I see that the xforms:var element is not currently supported. When > loading a form with an XForms variable defined, I get an error message: > > Error initializing: > > xforms:var is not supported > > (3) > I also see that the XSLTForms Profiler does not seem to be available. > When I try to open it, I get an error: > > File not found (404): > https://www.tat2.io/basex2/static/xsltforms_profiler.xhtml > > * > * > *--Test form for XPath predicate bug--* > * > * > <?xml-stylesheet type="text/xsl" href="..."?> > <html xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" > xmlns:xsd="http://www.w3.org/2001/XMLSchema" > xmlns:xf="http://www.w3.org/2002/xforms" > xmlns:h="http://www.w3.org/1999/xhtml" > xmlns:ev="http://www.w3.org/2001/xml-events" > xmlns="http://www.w3.org/1999/xhtml"> > <head> > <meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /> > <title>XForms/XPath Predicate Test</title> > <style type="text/css"/> > <model xmlns="http://www.w3.org/2002/xforms" id="m"> > <instance id="default"> > <data xmlns=""> > <default/> > </data> > </instance> > <instance id="response"> > <data xmlns=""> > <response/> > </data> > </instance> > <instance id="response-test"> > <data xmlns=""> > <response> > <testing>Testing</testing> > </response> > </data> > </instance> > </model> > </head> > <body> > <div class="container-fluid"> > <hr class="blue" /> > <h1>XForms/XPath predicate test</h1> > <xf:group ref="instance('response')/response[*]"> > <h2 style="color: red;">This should not display!</h2> > <xf:output value="concat('Value of "serialize(.)": > ', serialize(.))"/> > </xf:group> > <xf:group ref="instance('response-test')/response[*]"> > <h2 style="color: blue;">This should display.</h2> > <xf:output value="concat('Value of "serialize(.)": > ', serialize(.))"/> > </xf:group> > </div> > </body> > </html> > > > > -- > Tim A. Thompson > Discovery Metadata Librarian > Yale University Library > > On Sun, Feb 9, 2020 at 11:06 AM Tim Thompson <tim...@gm... > <mailto:tim...@gm...>> wrote: > > Hello, Alain, > > Congratulations on this milestone! I am very eager to try and test > the new release. Is XSLTForms now using Fleur for XPath parsing? > Does this mean that XPath 3.0 functions are now supported? I guess > I can test this myself :) > > It's quite amazing to see the xsltforms.xsl file down to just over > 500 lines. > > Thanks again for all your work. > > Best regards, > Tim > > > -- > Tim A. Thompson > Discovery Metadata Librarian > Yale University Library > > On Wed, Feb 5, 2020 at 3:16 PM Alain Couthures > <ala...@ag... > <mailto:ala...@ag...>> wrote: > > Hello, > > Please find a new release for XSLTForms at > www.agencexml.com/1.5beta/xsltforms.zip > <http://www.agencexml.com/1.5beta/xsltforms.zip> > > It has not yet been fully tested because a lot of changes have > been made and you are welcome to locate remaining issues with > your own forms. > > The XSLT part has been reduced to minimal for better > performance. Instead of parsing the XPath expressions and > transforming all the XForms elements into HTML elements, it > basically just transposes the non-HTML elements into sort-of > custom elements: xforms:* elements become xforms-* elements > with xf-* and ev-* attributes. > > Have a look with your favorite browser debugger! Actually, > authors could even prefer to directly write/generate forms > with this new notation and forget about the XSLT step. You can > compare two sources for the same form: hello.xml and hello.htm > > XSLTForms Javascript classes constructors are obtaining their > properties directly from xf-* attributes and XPath parsing is > then performed. > > No ids are automatically added as previously. > > Extra xf-* attributes and extra xforms-* elements are used to > embed effective HTML rendering elements, for example, > xforms-body or xforms-repeat-item while, before, span or div > elements where used. > > XSLTForms classes for xforms:select and xforms:itemset had to > be partially rewritten. > > SVG support has been basically tested too. > > CSS styling is not anymore based on xforms-* classes but on > custom element names and attribute selectors. For example, the > extra xf-bound attribute, when present, says that the XForms > control is bound to a node, eventually a not relevant one, and > the extra xf-notrelevant attribute can, then, be checked... > > Thank you for your contribution! > > --Alain > _______________________________________________ > Xsltforms-support mailing list > Xsl...@li... > <mailto:Xsl...@li...> > https://lists.sourceforge.net/lists/listinfo/xsltforms-support > |
|
From: Tim T. <tim...@gm...> - 2020-02-09 19:51:59
|
Hello, Alain,
I've been testing an existing form with the new release and have some
feedback. First, the performance improvement seems impressive, and CSS
styling with Bootstrap now seems much easier. Thank you!
I did notice some issues after testing, however.
(1)
There seems to be a bug with XPath predicate filtering in xf:group
elements. For example, a group binding such as <xf:group
ref="instance('response')/response[*]">...</xf:group>, where the response
element should initially be empty (before a submission is executed) does
not seem to work.
See the test form copied below. Example form at:
https://www.tat2.io/basex2/static/xsltforms_test_2020-02-09.xml
(2)
I see that the xforms:var element is not currently supported. When loading
a form with an XForms variable defined, I get an error message:
Error initializing:
xforms:var is not supported
(3)
I also see that the XSLTForms Profiler does not seem to be available. When
I try to open it, I get an error:
File not found (404):
https://www.tat2.io/basex2/static/xsltforms_profiler.xhtml
*--Test form for XPath predicate bug--*
<?xml-stylesheet type="text/xsl" href="..."?>
<html xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="
http://www.w3.org/2001/XMLSchema" xmlns:xf="http://www.w3.org/2002/xforms"
xmlns:h="http://www.w3.org/1999/xhtml" xmlns:ev="
http://www.w3.org/2001/xml-events" xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
<title>XForms/XPath Predicate Test</title>
<style type="text/css"/>
<model xmlns="http://www.w3.org/2002/xforms" id="m">
<instance id="default">
<data xmlns="">
<default/>
</data>
</instance>
<instance id="response">
<data xmlns="">
<response/>
</data>
</instance>
<instance id="response-test">
<data xmlns="">
<response>
<testing>Testing</testing>
</response>
</data>
</instance>
</model>
</head>
<body>
<div class="container-fluid">
<hr class="blue" />
<h1>XForms/XPath predicate test</h1>
<xf:group ref="instance('response')/response[*]">
<h2 style="color: red;">This should not display!</h2>
<xf:output value="concat('Value of "serialize(.)": ',
serialize(.))"/>
</xf:group>
<xf:group ref="instance('response-test')/response[*]">
<h2 style="color: blue;">This should display.</h2>
<xf:output value="concat('Value of "serialize(.)": ',
serialize(.))"/>
</xf:group>
</div>
</body>
</html>
--
Tim A. Thompson
Discovery Metadata Librarian
Yale University Library
On Sun, Feb 9, 2020 at 11:06 AM Tim Thompson <tim...@gm...> wrote:
> Hello, Alain,
>
> Congratulations on this milestone! I am very eager to try and test the new
> release. Is XSLTForms now using Fleur for XPath parsing? Does this mean
> that XPath 3.0 functions are now supported? I guess I can test this myself
> :)
>
> It's quite amazing to see the xsltforms.xsl file down to just over 500
> lines.
>
> Thanks again for all your work.
>
> Best regards,
> Tim
>
>
> --
> Tim A. Thompson
> Discovery Metadata Librarian
> Yale University Library
>
> On Wed, Feb 5, 2020 at 3:16 PM Alain Couthures <
> ala...@ag...> wrote:
>
>> Hello,
>>
>> Please find a new release for XSLTForms at
>> www.agencexml.com/1.5beta/xsltforms.zip
>>
>> It has not yet been fully tested because a lot of changes have been made
>> and you are welcome to locate remaining issues with your own forms.
>>
>> The XSLT part has been reduced to minimal for better performance. Instead
>> of parsing the XPath expressions and transforming all the XForms elements
>> into HTML elements, it basically just transposes the non-HTML elements into
>> sort-of custom elements: xforms:* elements become xforms-* elements with
>> xf-* and ev-* attributes.
>>
>> Have a look with your favorite browser debugger! Actually, authors could
>> even prefer to directly write/generate forms with this new notation and
>> forget about the XSLT step. You can compare two sources for the same form:
>> hello.xml and hello.htm
>>
>> XSLTForms Javascript classes constructors are obtaining their properties
>> directly from xf-* attributes and XPath parsing is then performed.
>>
>> No ids are automatically added as previously.
>>
>> Extra xf-* attributes and extra xforms-* elements are used to embed
>> effective HTML rendering elements, for example, xforms-body or
>> xforms-repeat-item while, before, span or div elements where used.
>>
>> XSLTForms classes for xforms:select and xforms:itemset had to be
>> partially rewritten.
>>
>> SVG support has been basically tested too.
>>
>> CSS styling is not anymore based on xforms-* classes but on custom
>> element names and attribute selectors. For example, the extra xf-bound
>> attribute, when present, says that the XForms control is bound to a node,
>> eventually a not relevant one, and the extra xf-notrelevant attribute can,
>> then, be checked...
>>
>> Thank you for your contribution!
>>
>> --Alain
>> _______________________________________________
>> Xsltforms-support mailing list
>> Xsl...@li...
>> https://lists.sourceforge.net/lists/listinfo/xsltforms-support
>>
>
|
|
From: Tim T. <tim...@gm...> - 2020-02-09 16:06:42
|
Hello, Alain, Congratulations on this milestone! I am very eager to try and test the new release. Is XSLTForms now using Fleur for XPath parsing? Does this mean that XPath 3.0 functions are now supported? I guess I can test this myself :) It's quite amazing to see the xsltforms.xsl file down to just over 500 lines. Thanks again for all your work. Best regards, Tim -- Tim A. Thompson Discovery Metadata Librarian Yale University Library On Wed, Feb 5, 2020 at 3:16 PM Alain Couthures < ala...@ag...> wrote: > Hello, > > Please find a new release for XSLTForms at > www.agencexml.com/1.5beta/xsltforms.zip > > It has not yet been fully tested because a lot of changes have been made > and you are welcome to locate remaining issues with your own forms. > > The XSLT part has been reduced to minimal for better performance. Instead > of parsing the XPath expressions and transforming all the XForms elements > into HTML elements, it basically just transposes the non-HTML elements into > sort-of custom elements: xforms:* elements become xforms-* elements with > xf-* and ev-* attributes. > > Have a look with your favorite browser debugger! Actually, authors could > even prefer to directly write/generate forms with this new notation and > forget about the XSLT step. You can compare two sources for the same form: > hello.xml and hello.htm > > XSLTForms Javascript classes constructors are obtaining their properties > directly from xf-* attributes and XPath parsing is then performed. > > No ids are automatically added as previously. > > Extra xf-* attributes and extra xforms-* elements are used to embed > effective HTML rendering elements, for example, xforms-body or > xforms-repeat-item while, before, span or div elements where used. > > XSLTForms classes for xforms:select and xforms:itemset had to be partially > rewritten. > > SVG support has been basically tested too. > > CSS styling is not anymore based on xforms-* classes but on custom element > names and attribute selectors. For example, the extra xf-bound attribute, > when present, says that the XForms control is bound to a node, eventually a > not relevant one, and the extra xf-notrelevant attribute can, then, be > checked... > > Thank you for your contribution! > > --Alain > _______________________________________________ > Xsltforms-support mailing list > Xsl...@li... > https://lists.sourceforge.net/lists/listinfo/xsltforms-support > |
|
From: Alain C. <ala...@ag...> - 2020-02-05 20:16:13
|
Hello, Please find a new release for XSLTForms at www.agencexml.com/1.5beta/xsltforms.zip It has not yet been fully tested because a lot of changes have been made and you are welcome to locate remaining issues with your own forms. The XSLT part has been reduced to minimal for better performance. Instead of parsing the XPath expressions and transforming all the XForms elements into HTML elements, it basically just transposes the non-HTML elements into sort-of custom elements: xforms:* elements become xforms-* elements with xf-* and ev-* attributes. Have a look with your favorite browser debugger! Actually, authors could even prefer to directly write/generate forms with this new notation and forget about the XSLT step. You can compare two sources for the same form: hello.xml and hello.htm XSLTForms Javascript classes constructors are obtaining their properties directly from xf-* attributes and XPath parsing is then performed. No ids are automatically added as previously. Extra xf-* attributes and extra xforms-* elements are used to embed effective HTML rendering elements, for example, xforms-body or xforms-repeat-item while, before, span or div elements where used. XSLTForms classes for xforms:select and xforms:itemset had to be partially rewritten. SVG support has been basically tested too. CSS styling is not anymore based on xforms-* classes but on custom element names and attribute selectors. For example, the extra xf-bound attribute, when present, says that the XForms control is bound to a node, eventually a not relevant one, and the extra xf-notrelevant attribute can, then, be checked... Thank you for your contribution! --Alain |
|
From: <ch...@el...> - 2020-01-23 01:23:55
|
<html><body><span style="font-family:Verdana; color:#000000; font-size:10pt;"><div>The name of the zip file is xsltforms-1.3.zip</div><div><br></div><div>Chris</div><div><br></div>
<blockquote id="replyBlockquote" webmail="1" style="border-left: 2px solid blue; margin-left: 8px; padding-left: 8px; font-size:10pt; color:black; font-family:verdana;">
<div id="wmQuoteWrapper">
-------- Original Message --------<br>
Subject: Re: [Xsltforms-support] question about conversion from ubiquity<br>
From: Alain Couthures <<a href="mailto:ala...@ag...">ala...@ag...</a>><br>
Date: Wed, January 22, 2020 10:55 am<br>
To: <a href="mailto:ch...@el...">ch...@el...</a>, "<a href="mailto:xsl...@li...">xsl...@li...</a>"<br>
<<a href="mailto:xsl...@li...">xsl...@li...</a>><br>
<br>
<div class="moz-cite-prefix">Hi Chris,</div> <div class="moz-cite-prefix"><br> </div> <div class="moz-cite-prefix">Could it be that the targeted resource is not in the same domain as the form itself (cross-domain restriction)?</div> <div class="moz-cite-prefix"><br> </div> <div class="moz-cite-prefix">What is the release of XSLTForms you are using?<br> </div> <div class="moz-cite-prefix"><br> </div> <div class="moz-cite-prefix">Thank you for your feedback!</div> <div class="moz-cite-prefix"><br> </div> <div class="moz-cite-prefix">--Alain<br> </div> <div class="moz-cite-prefix"><br> </div> <div class="moz-cite-prefix">Le 22/01/2020 à 14:04, <a target="_blank" class="moz-txt-link-abbreviated" href="mailto:ch...@el...">ch...@el...</a> a écrit :<br> </div> <blockquote type="cite" cite="mid:202...@em..."> <span style="font-family:Verdana; color:#000000; font-size:10pt;"> <div><br> </div> <div>I'm still working on this off and on without success.</div> <div>POST doesn't seem to be sending anything at all.</div> <div><br> </div> <div>I only need a couple of pieces of information, maybe I will switch to GET.</div> <div><br> </div> <div>Here is my submission block:<br> </div> <div><br> </div> <div> <xf:submission resource=<a target="_blank" class="moz-txt-link-rfc2396E" href="https://xxxx.yyyy.zzz/cgi-bin/XMLSave1">"https://xxxx.yyyy.zzz/cgi-bin/XMLSave1"</a> method="post" id="sendStuff"><br> <xf:action ev:event="xforms-submit"><br> </xf:action><br> </xf:submission><br> <br> </div> <blockquote id="replyBlockquote" webmail="1" style="border-left: 2px solid blue; margin-left: 8px; padding-left: 8px; font-size:10pt; color:black; font-family:verdana;"> <div id="wmQuoteWrapper"> -------- Original Message --------<br> Subject: Re: [Xsltforms-support] question about conversion from ubiquity<br> From: Alain Couthures <<a target="_blank" href="mailto:ala...@ag..." moz-do-not-send="true">ala...@ag...</a>><br> Date: Thu, January 16, 2020 10:54 am<br> To: Chris Howard <<a target="_blank" href="mailto:ch...@el..." moz-do-not-send="true">ch...@el...</a>>,<br> <a target="_blank" href="mailto:xsl...@li..." moz-do-not-send="true">xsl...@li...</a><br> <br> <div> Hello Chris, </div> <div> <br> </div> <div> Did you check the HTTP request body with the browser network debugger? </div> <div> <br> </div> <div> --Alain </div> <div> <br> </div> <blockquote type="cite" style="border-left: blue 2px solid; margin-left: 8px; padding-left: 8px;"> <div> Le 16 janvier 2020 à 13:09, Chris Howard < <a target="_blank" href="mailto:ch...@el..." moz-do-not-send="true">ch...@el...</a>> a écrit : </div> <div> <br> </div> <div> <br> </div> <div> Hello, </div> <div> <br> </div> <div> I have run into another issue: </div> <div> <br> </div> <div> I am using a CGI perl script and a submission button which calls the script. </div> <div> The script gets some data from the POSTDATA and does some actions. </div> <div> <br> </div> <div> My forms using xsltforms library are not sending any POST data. </div> <div> The script is being called, but no data. </div> <div> <br> </div> <div> I tried also with one of the sample forms, substituting in my own perl </div> <div> CGI as the action, </div> <div> still no POST data showing up. </div> <div> <br> </div> <div> Can you give me some pointers as to where I should be looking? </div> <div> Is this an issue with the web server config? I am not seeing any errors </div> <div> in the </div> <div> log files, just no POST data coming through. </div> <div> <br> </div> <div> Thanks </div> <div> <br> </div> <div> Chris Howard </div> <div> <br> </div> <div> <br> </div> <div> <br> </div> <div> <br> </div> <div> On 1/12/20 7:06 AM, Chris Howard wrote: </div> <blockquote type="cite" style="border-left: blue 2px solid; margin-left: 8px; padding-left: 8px;"> <div> Hi, </div> <div> <br> </div> <div> I spent some time with the samples and sorted it out. </div> <div> The big first item was adding xmlns="" in the top-level instance data </div> <div> tag. </div> <div> Then I started seeing my instance data. </div> <div> <br> </div> <div> Then I worked out some issues with stylesheet (also covered in the </div> <div> examples). </div> <div> <br> </div> <div> I very much appreciate your help! </div> <div> <br> </div> <div> Chris </div> <div> <br> </div> <div> <br> </div> <div> On 1/11/20 8:41 AM, Alain Couthures wrote: </div> <blockquote type="cite" style="border-left: blue 2px solid; margin-left: 8px; padding-left: 8px;"> <div> Hello Chris, </div> <div> <br> </div> <div> As far as I remember, Ubiquity had a limitation about models not to </div> <div> be declared in head section but in body section. </div> <div> <br> </div> <div> I suggest you to first check that XSLTForms samples are OK for you. </div> <div> Then, to compare with Ubiquity. </div> <div> <br> </div> <div> If possible, please don't hesitate to send a full form source. </div> <div> <br> </div> <div> Thank you for your feedback! </div> <div> <br> </div> <div> --Alain </div> <div> <br> </div> <div> <br> </div> <div> Le 11/01/2020 à 15:04, Chris Howard a écrit : </div> <div> > </div> <blockquote type="cite" style="border-left: blue 2px solid; margin-left: 8px; padding-left: 8px;"> <div> Update, </div> <div> <br> </div> <div> I have been simplifying my form this morning and even with all of </div> <div> the triggers </div> <div> and events stripped out, I still don't see any of my data. </div> <div> <br> </div> <div> <br> </div> <div> <br> </div> <div> On 1/11/20 7:17 AM, Chris Howard wrote: </div> <blockquote type="cite" style="border-left: blue 2px solid; margin-left: 8px; padding-left: 8px;"> <div> Hi, </div> <div> <br> </div> <div> Many years ago I worked on a xform which would allow editing of </div> <div> an XML file. I didn't know a lot about XSLT or XForms but I was </div> <div> able to cook up something that worked. </div> <div> <br> </div> <div> We used the ubiquity library. </div> <div> <br> </div> <div> Recently the form quit working. </div> <div> I am remote from the situation such that I cannot directly debug </div> <div> the problem. </div> <div> There are other people working on that. </div> <div> <br> </div> <div> I've been given the task of researching a replacement for the </div> <div> ancient ubiquity library. </div> <div> <br> </div> <div> I have the xsltforms package installed on our web server and I can </div> <div> run some sample forms. </div> <div> It looks like the xsltforms content is being sent to the browser, </div> <div> so I think my </div> <div> basic plumbing is working ok. </div> <div> <br> </div> <div> My problem is that our form never seems to activate. I get the </div> <div> screen drawn </div> <div> but none of my DOMActivate events seem to perform. Also my submit </div> <div> buttons </div> <div> do not work. None of my instance data is showing up in the form. </div> <div> <br> </div> <div> I am looking for any help or advise that might be available </div> <div> <br> </div> <div> My triggers look like this: </div> <div> <br> </div> <div> <xf:trigger bind="detailSpecial"> </div> <div> <br> </div> <div> <xf:label>Insert tax/total Item</xf:label> </div> <div> <br> </div> <div> <xf:action ev:event="DOMActivate"> </div> <div> <br> </div> <div> <xf:insert </div> <div> nodeset="/bill/billDetail/detailSpecialSet/detailSpecial" </div> <div> at="index('repeat-detailSpecial')" position="before"/> </div> <div> <br> </div> <div> <xf:setvalue </div> <div> ref="/bill/billDetail/detailSpecialSet/detailSpecial[index('repeat-detailSpecial')]/specialDescription"></xf:setvalue> </div> <div> <br> </div> <div> <xf:setvalue </div> <div> ref="/bill/billDetail/detailSpecialSet/detailSpecial[index('repeat-detailSpecial')]/charge"></xf:setvalue> </div> <div> <br> </div> <div> </xf:action> </div> <div> <br> </div> <div> </xf:trigger> </div> <div> <br> </div> <div> <xf:trigger bind="detailSpecial"> </div> <div> <br> </div> <div> <xf:label>Delete tax/total Item</xf:label> </div> <div> <br> </div> <div> <xf:delete ev:event="DOMActivate" </div> <div> nodeset="/bill/billDetail/detailSpecialSet/detailSpecial" </div> <div> at="index('repeat-detailSpecial')"/> </div> <div> <br> </div> <div> </xf:trigger> </div> <div> <br> </div> <div> <br> </div> <div> <br> </div> <div> _______________________________________________ </div> <div> Xsltforms-support mailing list </div> <div> <a target="_blank" href="mailto:Xsl...@li..." moz-do-not-send="true">Xsl...@li...</a> </div> <div> <a href="https://lists.sourceforge.net/lists/listinfo/xsltforms-support" rel="noopener" target="_blank" moz-do-not-send="true">https://lists.sourceforge.net/lists/listinfo/xsltforms-support</a> </div> </blockquote> <div> <br> </div> <div> <br> </div> <div> <br> </div> <div> _______________________________________________ </div> <div> Xsltforms-support mailing list </div> <div> <a target="_blank" href="mailto:Xsl...@li..." moz-do-not-send="true">Xsl...@li...</a> </div> <div> <a href="https://lists.sourceforge.net/lists/listinfo/xsltforms-support" rel="noopener" target="_blank" moz-do-not-send="true">https://lists.sourceforge.net/lists/listinfo/xsltforms-support</a> </div> </blockquote> <div> <br> </div> <div> <br> </div> <div> <br> </div> </blockquote> <div> <br> </div> <div> <br> </div> <div> <br> </div> <div> _______________________________________________ </div> <div> Xsltforms-support mailing list </div> <div> <a target="_blank" href="mailto:Xsl...@li..." moz-do-not-send="true">Xsl...@li...</a> </div> <div> <a href="https://lists.sourceforge.net/lists/listinfo/xsltforms-support" rel="noopener" target="_blank" moz-do-not-send="true">https://lists.sourceforge.net/lists/listinfo/xsltforms-support</a> </div> </blockquote> <div> <br> </div> <div> <br> </div> <div> <br> </div> <div> _______________________________________________ </div> <div> Xsltforms-support mailing list </div> <div> <a target="_blank" href="mailto:Xsl...@li..." moz-do-not-send="true">Xsl...@li...</a> </div> <div> <a href="https://lists.sourceforge.net/lists/listinfo/xsltforms-support" rel="noopener" target="_blank" moz-do-not-send="true">https://lists.sourceforge.net/lists/listinfo/xsltforms-support</a> </div> </blockquote> </div> </blockquote> </span> </blockquote> <div><br> </div>
</div>
</blockquote></span></body></html>
|
|
From: <ch...@el...> - 2020-01-23 01:22:12
|
<html><body><span style="font-family:Verdana; color:#000000; font-size:10pt;"><div><br></div><div>Hi, I am sending you a sample by direct email.</div><div><br></div><div>I was mistaken about only needing two pieces of data.</div><div>This is a billing application and the form is used to edit bill fields.</div><div>Most of the fields can be edited. The there are three submission actions,</div><div>one is to save the bill changes, one is to do a preview of what the</div><div>new data looks like in our bill format, and the last one is to </div><div>do a print of the bill. All use post and call CGI scripts to</div><div>do the work.<br></div><div><br></div><div>Thanks!</div><div><br></div><div>Chris Howard</div><div><br></div><div><br></div><blockquote id="replyBlockquote" webmail="1" style="border-left: 2px solid blue; margin-left: 8px; padding-left: 8px; font-size:10pt; color:black; font-family:verdana;">
<div id="wmQuoteWrapper">
-------- Original Message --------<br>
Subject: Re: [Xsltforms-support] question about conversion from ubiquity<br>
From: Tim Thompson <<a href="mailto:tim...@gm...">tim...@gm...</a>><br>
Date: Wed, January 22, 2020 12:59 pm<br>
To: <a href="mailto:ch...@el...">ch...@el...</a><br>
Cc: "<a href="mailto:xsl...@li...">xsl...@li...</a>"<br>
<<a href="mailto:xsl...@li...">xsl...@li...</a>><br>
<br>
<div dir="ltr"><div>Chris,</div><div><br></div><div>You said that the form is not sending POST data, right? From your snippet, it looks as though you haven't defined a source (or target) instance for the data. What do your XForms instances look like? If you're able to provide a complete example of the form, that would be helpful in troubleshooting. <br></div><div><br></div><div>Best regards,</div><div>Tim<br></div><div><br></div><div><div dir="ltr" class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr">--<br>Tim A. Thompson<br>Discovery Metadata Librarian<br>Yale University Library<br></div></div></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Wed, Jan 22, 2020 at 8:05 AM <<a target="_blank" href="mailto:ch...@el...">ch...@el...</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div><span style="font-family:Verdana;color:rgb(0,0,0);font-size:10pt"><div><br></div><div>I'm still working on this off and on without success.</div><div>POST doesn't seem to be sending anything at all.</div><div><br></div><div>I only need a couple of pieces of information, maybe I will switch to GET.</div><div><br></div><div>Here is my submission block:<br></div><div><br></div><div> <xf:submission resource="<a href="https://xxxx.yyyy.zzz/cgi-bin/XMLSave1" target="_blank">https://xxxx.yyyy.zzz/cgi-bin/XMLSave1</a>" method="post" id="sendStuff"><br> <xf:action ev:event="xforms-submit"><br> </xf:action><br> </xf:submission><br><br></div><blockquote id="gmail-m_7663966487183015384replyBlockquote" style="border-left:2px solid blue;margin-left:8px;padding-left:8px;font-size:10pt;color:black;font-family:verdana"> <div id="gmail-m_7663966487183015384wmQuoteWrapper"> -------- Original Message --------<br> Subject: Re: [Xsltforms-support] question about conversion from ubiquity<br> From: Alain Couthures <<a href="mailto:ala...@ag..." target="_blank">ala...@ag...</a>><br> Date: Thu, January 16, 2020 10:54 am<br> To: Chris Howard <<a href="mailto:ch...@el..." target="_blank">ch...@el...</a>>,<br> <a href="mailto:xsl...@li..." target="_blank">xsl...@li...</a><br> <br> <div> Hello Chris, </div> <div> <br> </div> <div> Did you check the HTTP request body with the browser network debugger? </div> <div> <br> </div> <div> --Alain </div> <div> <br> </div> <blockquote type="cite" style="border-left:2px solid blue;margin-left:8px;padding-left:8px"> <div> Le 16 janvier 2020 à 13:09, Chris Howard < <a href="mailto:ch...@el..." target="_blank">ch...@el...</a>> a écrit : </div> <div> <br> </div> <div> <br> </div> <div> Hello, </div> <div> <br> </div> <div> I have run into another issue: </div> <div> <br> </div> <div> I am using a CGI perl script and a submission button which calls the script. </div> <div> The script gets some data from the POSTDATA and does some actions. </div> <div> <br> </div> <div> My forms using xsltforms library are not sending any POST data. </div> <div> The script is being called, but no data. </div> <div> <br> </div> <div> I tried also with one of the sample forms, substituting in my own perl </div> <div> CGI as the action, </div> <div> still no POST data showing up. </div> <div> <br> </div> <div> Can you give me some pointers as to where I should be looking? </div> <div> Is this an issue with the web server config? I am not seeing any errors </div> <div> in the </div> <div> log files, just no POST data coming through. </div> <div> <br> </div> <div> Thanks </div> <div> <br> </div> <div> Chris Howard </div> <div> <br> </div> <div> <br> </div> <div> <br> </div> <div> <br> </div> <div> On 1/12/20 7:06 AM, Chris Howard wrote: </div> <blockquote type="cite" style="border-left:2px solid blue;margin-left:8px;padding-left:8px"> <div> Hi, </div> <div> <br> </div> <div> I spent some time with the samples and sorted it out. </div> <div> The big first item was adding xmlns="" in the top-level instance data </div> <div> tag. </div> <div> Then I started seeing my instance data. </div> <div> <br> </div> <div> Then I worked out some issues with stylesheet (also covered in the </div> <div> examples). </div> <div> <br> </div> <div> I very much appreciate your help! </div> <div> <br> </div> <div> Chris </div> <div> <br> </div> <div> <br> </div> <div> On 1/11/20 8:41 AM, Alain Couthures wrote: </div> <blockquote type="cite" style="border-left:2px solid blue;margin-left:8px;padding-left:8px"> <div> Hello Chris, </div> <div> <br> </div> <div> As far as I remember, Ubiquity had a limitation about models not to </div> <div> be declared in head section but in body section. </div> <div> <br> </div> <div> I suggest you to first check that XSLTForms samples are OK for you. </div> <div> Then, to compare with Ubiquity. </div> <div> <br> </div> <div> If possible, please don't hesitate to send a full form source. </div> <div> <br> </div> <div> Thank you for your feedback! </div> <div> <br> </div> <div> --Alain </div> <div> <br> </div> <div> <br> </div> <div> Le 11/01/2020 à 15:04, Chris Howard a écrit : </div> <div> > </div> <blockquote type="cite" style="border-left:2px solid blue;margin-left:8px;padding-left:8px"> <div> Update, </div> <div> <br> </div> <div> I have been simplifying my form this morning and even with all of </div> <div> the triggers </div> <div> and events stripped out, I still don't see any of my data. </div> <div> <br> </div> <div> <br> </div> <div> <br> </div> <div> On 1/11/20 7:17 AM, Chris Howard wrote: </div> <blockquote type="cite" style="border-left:2px solid blue;margin-left:8px;padding-left:8px"> <div> Hi, </div> <div> <br> </div> <div> Many years ago I worked on a xform which would allow editing of </div> <div> an XML file. I didn't know a lot about XSLT or XForms but I was </div> <div> able to cook up something that worked. </div> <div> <br> </div> <div> We used the ubiquity library. </div> <div> <br> </div> <div> Recently the form quit working. </div> <div> I am remote from the situation such that I cannot directly debug </div> <div> the problem. </div> <div> There are other people working on that. </div> <div> <br> </div> <div> I've been given the task of researching a replacement for the </div> <div> ancient ubiquity library. </div> <div> <br> </div> <div> I have the xsltforms package installed on our web server and I can </div> <div> run some sample forms. </div> <div> It looks like the xsltforms content is being sent to the browser, </div> <div> so I think my </div> <div> basic plumbing is working ok. </div> <div> <br> </div> <div> My problem is that our form never seems to activate. I get the </div> <div> screen drawn </div> <div> but none of my DOMActivate events seem to perform. Also my submit </div> <div> buttons </div> <div> do not work. None of my instance data is showing up in the form. </div> <div> <br> </div> <div> I am looking for any help or advise that might be available </div> <div> <br> </div> <div> My triggers look like this: </div> <div> <br> </div> <div> <xf:trigger bind="detailSpecial"> </div> <div> <br> </div> <div> <xf:label>Insert tax/total Item</xf:label> </div> <div> <br> </div> <div> <xf:action ev:event="DOMActivate"> </div> <div> <br> </div> <div> <xf:insert </div> <div> nodeset="/bill/billDetail/detailSpecialSet/detailSpecial" </div> <div> at="index('repeat-detailSpecial')" position="before"/> </div> <div> <br> </div> <div> <xf:setvalue </div> <div> ref="/bill/billDetail/detailSpecialSet/detailSpecial[index('repeat-detailSpecial')]/specialDescription"></xf:setvalue> </div> <div> <br> </div> <div> <xf:setvalue </div> <div> ref="/bill/billDetail/detailSpecialSet/detailSpecial[index('repeat-detailSpecial')]/charge"></xf:setvalue> </div> <div> <br> </div> <div> </xf:action> </div> <div> <br> </div> <div> </xf:trigger> </div> <div> <br> </div> <div> <xf:trigger bind="detailSpecial"> </div> <div> <br> </div> <div> <xf:label>Delete tax/total Item</xf:label> </div> <div> <br> </div> <div> <xf:delete ev:event="DOMActivate" </div> <div> nodeset="/bill/billDetail/detailSpecialSet/detailSpecial" </div> <div> at="index('repeat-detailSpecial')"/> </div> <div> <br> </div> <div> </xf:trigger> </div> <div> <br> </div> <div> <br> </div> <div> <br> </div> <div> _______________________________________________ </div> <div> Xsltforms-support mailing list </div> <div> <a href="mailto:Xsl...@li..." target="_blank">Xsl...@li...</a> </div> <div> <a href="https://lists.sourceforge.net/lists/listinfo/xsltforms-support" rel="noopener" target="_blank">https://lists.sourceforge.net/lists/listinfo/xsltforms-support</a> </div> </blockquote> <div> <br> </div> <div> <br> </div> <div> <br> </div> <div> _______________________________________________ </div> <div> Xsltforms-support mailing list </div> <div> <a href="mailto:Xsl...@li..." target="_blank">Xsl...@li...</a> </div> <div> <a href="https://lists.sourceforge.net/lists/listinfo/xsltforms-support" rel="noopener" target="_blank">https://lists.sourceforge.net/lists/listinfo/xsltforms-support</a> </div> </blockquote> <div> <br> </div> <div> <br> </div> <div> <br> </div> </blockquote> <div> <br> </div> <div> <br> </div> <div> <br> </div> <div> _______________________________________________ </div> <div> Xsltforms-support mailing list </div> <div> <a href="mailto:Xsl...@li..." target="_blank">Xsl...@li...</a> </div> <div> <a href="https://lists.sourceforge.net/lists/listinfo/xsltforms-support" rel="noopener" target="_blank">https://lists.sourceforge.net/lists/listinfo/xsltforms-support</a> </div> </blockquote> <div> <br> </div> <div> <br> </div> <div> <br> </div> <div> _______________________________________________ </div> <div> Xsltforms-support mailing list </div> <div> <a href="mailto:Xsl...@li..." target="_blank">Xsl...@li...</a> </div> <div> <a href="https://lists.sourceforge.net/lists/listinfo/xsltforms-support" rel="noopener" target="_blank">https://lists.sourceforge.net/lists/listinfo/xsltforms-support</a> </div> </blockquote> </div> </blockquote></span></div> _______________________________________________<br> Xsltforms-support mailing list<br> <a href="mailto:Xsl...@li..." target="_blank">Xsl...@li...</a><br> <a href="https://lists.sourceforge.net/lists/listinfo/xsltforms-support" rel="noreferrer" target="_blank">https://lists.sourceforge.net/lists/listinfo/xsltforms-support</a><br> </blockquote></div>
</div>
</blockquote></span></body></html>
|
|
From: Tim T. <tim...@gm...> - 2020-01-22 20:00:26
|
Chris,
You said that the form is not sending POST data, right? From your snippet,
it looks as though you haven't defined a source (or target) instance for
the data. What do your XForms instances look like? If you're able to
provide a complete example of the form, that would be helpful in
troubleshooting.
Best regards,
Tim
--
Tim A. Thompson
Discovery Metadata Librarian
Yale University Library
On Wed, Jan 22, 2020 at 8:05 AM <ch...@el...> wrote:
>
> I'm still working on this off and on without success.
> POST doesn't seem to be sending anything at all.
>
> I only need a couple of pieces of information, maybe I will switch to GET.
>
> Here is my submission block:
>
> <xf:submission resource="https://xxxx.yyyy.zzz/cgi-bin/XMLSave1"
> method="post" id="sendStuff">
> <xf:action ev:event="xforms-submit">
> </xf:action>
> </xf:submission>
>
> -------- Original Message --------
> Subject: Re: [Xsltforms-support] question about conversion from ubiquity
> From: Alain Couthures <ala...@ag...>
> Date: Thu, January 16, 2020 10:54 am
> To: Chris Howard <ch...@el...>,
> xsl...@li...
>
> Hello Chris,
>
> Did you check the HTTP request body with the browser network debugger?
>
> --Alain
>
> Le 16 janvier 2020 à 13:09, Chris Howard < ch...@el...> a écrit :
>
>
> Hello,
>
> I have run into another issue:
>
> I am using a CGI perl script and a submission button which calls the
> script.
> The script gets some data from the POSTDATA and does some actions.
>
> My forms using xsltforms library are not sending any POST data.
> The script is being called, but no data.
>
> I tried also with one of the sample forms, substituting in my own perl
> CGI as the action,
> still no POST data showing up.
>
> Can you give me some pointers as to where I should be looking?
> Is this an issue with the web server config? I am not seeing any errors
> in the
> log files, just no POST data coming through.
>
> Thanks
>
> Chris Howard
>
>
>
>
> On 1/12/20 7:06 AM, Chris Howard wrote:
>
> Hi,
>
> I spent some time with the samples and sorted it out.
> The big first item was adding xmlns="" in the top-level instance data
> tag.
> Then I started seeing my instance data.
>
> Then I worked out some issues with stylesheet (also covered in the
> examples).
>
> I very much appreciate your help!
>
> Chris
>
>
> On 1/11/20 8:41 AM, Alain Couthures wrote:
>
> Hello Chris,
>
> As far as I remember, Ubiquity had a limitation about models not to
> be declared in head section but in body section.
>
> I suggest you to first check that XSLTForms samples are OK for you.
> Then, to compare with Ubiquity.
>
> If possible, please don't hesitate to send a full form source.
>
> Thank you for your feedback!
>
> --Alain
>
>
> Le 11/01/2020 à 15:04, Chris Howard a écrit :
> >
>
> Update,
>
> I have been simplifying my form this morning and even with all of
> the triggers
> and events stripped out, I still don't see any of my data.
>
>
>
> On 1/11/20 7:17 AM, Chris Howard wrote:
>
> Hi,
>
> Many years ago I worked on a xform which would allow editing of
> an XML file. I didn't know a lot about XSLT or XForms but I was
> able to cook up something that worked.
>
> We used the ubiquity library.
>
> Recently the form quit working.
> I am remote from the situation such that I cannot directly debug
> the problem.
> There are other people working on that.
>
> I've been given the task of researching a replacement for the
> ancient ubiquity library.
>
> I have the xsltforms package installed on our web server and I can
> run some sample forms.
> It looks like the xsltforms content is being sent to the browser,
> so I think my
> basic plumbing is working ok.
>
> My problem is that our form never seems to activate. I get the
> screen drawn
> but none of my DOMActivate events seem to perform. Also my submit
> buttons
> do not work. None of my instance data is showing up in the form.
>
> I am looking for any help or advise that might be available
>
> My triggers look like this:
>
> <xf:trigger bind="detailSpecial">
>
> <xf:label>Insert tax/total Item</xf:label>
>
> <xf:action ev:event="DOMActivate">
>
> <xf:insert
> nodeset="/bill/billDetail/detailSpecialSet/detailSpecial"
> at="index('repeat-detailSpecial')" position="before"/>
>
> <xf:setvalue
> ref="/bill/billDetail/detailSpecialSet/detailSpecial[index('repeat-detailSpecial')]/specialDescription"></xf:setvalue>
>
>
> <xf:setvalue
> ref="/bill/billDetail/detailSpecialSet/detailSpecial[index('repeat-detailSpecial')]/charge"></xf:setvalue>
>
>
> </xf:action>
>
> </xf:trigger>
>
> <xf:trigger bind="detailSpecial">
>
> <xf:label>Delete tax/total Item</xf:label>
>
> <xf:delete ev:event="DOMActivate"
> nodeset="/bill/billDetail/detailSpecialSet/detailSpecial"
> at="index('repeat-detailSpecial')"/>
>
> </xf:trigger>
>
>
>
> _______________________________________________
> Xsltforms-support mailing list
> Xsl...@li...
> https://lists.sourceforge.net/lists/listinfo/xsltforms-support
>
>
>
>
> _______________________________________________
> Xsltforms-support mailing list
> Xsl...@li...
> https://lists.sourceforge.net/lists/listinfo/xsltforms-support
>
>
>
>
>
>
>
> _______________________________________________
> Xsltforms-support mailing list
> Xsl...@li...
> https://lists.sourceforge.net/lists/listinfo/xsltforms-support
>
>
>
>
> _______________________________________________
> Xsltforms-support mailing list
> Xsl...@li...
> https://lists.sourceforge.net/lists/listinfo/xsltforms-support
>
> _______________________________________________
> Xsltforms-support mailing list
> Xsl...@li...
> https://lists.sourceforge.net/lists/listinfo/xsltforms-support
>
|
97 messages has been excluded from this view by a project administrator.
