xsltforms-support Mailing List for XSLTForms (Page 6)
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
(2) |
Dec
(1) |
|
From: Javier Diazestebaranz(UST,ES) <Jav...@us...> - 2021-06-11 00:54:21
|
Hi again,
forget my previous email, I have read in a previous Alain's email in this list the following : "HTML5 also considers that custom elements cannot be written with the auto-close notation." and I have realized that the problem is that instead putting: <xforms-label xf-ref="elm[1]"/> it should be '<xforms-label xf-ref="elm[1]"></xforms-label>'
We generate the html pages executing xslt in server side, using xsltforms.xsl and then sending html to server, so the problem was in that transformation.
I have solved the problem doing the following change in xsltforms.xsl
@@ -363,7 +363,12 @@
</xsl:when>
</xsl:choose>
</xsl:for-each>
+ <xsl:choose>
+ <xsl:when test="node()">
<xsl:apply-templates select="node()"/>
+ </xsl:when>
+ <xsl:otherwise> </xsl:otherwise>
+ </xsl:choose>
</xsl:element>
</xsl:when>
<xsl:when test="contains('.setvalue.insert.delete.update.dispatch.property.targetid.name.action.load.toggle.send.setfocus.wrap.setselection.setindex.setnode.reset.retain.return.renew.refresh.rebuild.recalculate.revalidate.unload.hint.alert.help.value.item.itemset.copy.choices.filename.show.hide.method.resource.header.mediatype.message.control.', concat('.', local-name(), '.'))">
@@ -404,7 +409,12 @@
</xsl:when>
</xsl:choose>
</xsl:for-each>
+ <xsl:choose>
+ <xsl:when test="node()">
<xsl:apply-templates select="node()"/>
+ </xsl:when>
+ <xsl:otherwise> </xsl:otherwise>
+ </xsl:choose>
</xsl:element>
</xsl:when>
<xsl:otherwise>
So I force to insert at least a blank space to guarantee that there isn't any auto-close notation and all the previously mentioned problems have been solved!.
Best Regards,
Javier
El 10/6/21 a las 19:21, Javier Diazestebaranz(UST, ES) via Xsltforms-support escribió:
EXTERNAL EMAIL - Do not click any links or open any attachments unless you trust the sender and know the content is safe.
Hello Steven,
thanks a lot for your help.
First of all, I have realized that I sent a wrong test case. In the setvalue 'error' I sent you the following: '<xforms-setvalue xf-ref="instance('salida')/datosTarea/numeroOrden" xf-value="aa"/>' instead '<xforms-setvalue xf-ref="instance('salida')/datosTarea/numeroOrden" xf-value=""/>. The original XForms source was as you thought, '<setvalue ref="foo" value=""/>'. It seems that older version ignored that emtpy value and cleared the value of the element in that case. We have corrected it (with <setvalue ref="foo"/>) and now it doesn't fail.
The other problem related with 'bind', I also sent a bad test case. We have discovered that it only fails when 'bind' elements are not at the end of model part. So, if you put:
(..)
<xforms-submission id="enviar" xf-method="get" xf-mode="synchronous" xf-ref="instance('salida')/datosTarea" xf-resource="fake">
<xforms-action ev-event="xforms-submit-error">
<xforms-setvalue xf-ref="instance('salida')/datosTarea/numeroOrden"/>
</xforms-action>
</xforms-submission>
<xforms-bind id="bind_numeroOrden" xf-ref="instance('salida')/datosTarea/numeroOrden" xf-required="true()" xf-type="xsd:string"/>
</xforms-model>
(...)
It works ok, but if you put:
(...)
<xforms-bind id="bind_numeroOrden" xf-ref="instance('salida')/datosTarea/numeroOrden" xf-required="true()" xf-type="xsd:string"/>
<xforms-submission id="enviar" xf-method="get" xf-mode="synchronous" xf-ref="instance('salida')/datosTarea" xf-resource="fake">
<xforms-action ev-event="xforms-submit-error">
<xforms-setvalue xf-ref="instance('salida')/datosTarea/numeroOrden"/>
</xforms-action>
</xforms-submission>
</xforms-model>
(...)
It fails. Is there any rule about the order of the model elements? In older version we mixed them and there wasn't any error.
We have also found another problem, regarding select1 and itemset, recovering the values from other instance (I send a testcase about this problem). If I put:
<xforms-itemset xf-ref="instance('inst_tarea')/vct">
<xforms-label xf-ref="elm[1]"/>
<xforms-value xf-ref="elm[2]"/>
</xforms-itemset>
Label is shown but value it is not processed and a 'undefined' value appears if I choose some element. If I change the order of the elements:
<xforms-itemset xf-ref="instance('inst_tarea')/vct">
<xforms-value xf-ref="elm[2]"/>
<xforms-label xf-ref="elm[1]"/>
</xforms-itemset>
There is no label shown, but the value is selected correctly. We have tried to change it in another way, but we had no luck.
Thank you,
Javier
El 10/6/21 a las 10:29, Steven Pemberton escribió:
On Thu, 10 Jun 2021 01:19:45 +0200, Javier Diazestebaranz(UST, ES) via Xsltforms-support <xsl...@li...><mailto:xsl...@li...> wrote:
Hello,
we are using a very ,very old Xsltforms implementation (r574, more than 8 years ago) with some local changes, and we want to migrate to last stable version.
Before starting the migration, I have been testing some of our xforms pages with last version (downloaded from here: https://github.com/AlainCouthures/declarative4all/blob/master/public/direct/xsltforms.zip , I m not sure if it is a stable one), and I came across some problems.
I have made a small test case, to check if we have some error in our code, there have been some syntax changes in xforms and we have to modify our code, or there is some error in last xsltform version, I hope somebody can help us.
I send attached the code (submission.html). We use the .xml version (we don't want to rewrite all our old code), but i think is easier to analyse the problem with .html version.
* The first error that appears when the form load is:
XSLTForms Exception
--------------------------
Error parsing the following XPath expression :
Unexpected char at ''
It seems this line have some problem, because when I comment out it, the error dissapears:
<xforms-setvalue xf-ref="instance('salida')/datosTarea/numeroOrden" xf-value=""/>
So this is the generated code, not your original XForms source, so I'm guessing here, but to set a value to the empty string, you use either
<setvalue ref="foo" value="''"/>
or equally good
<setvalue ref="foo"/>
This is not good:
<setvalue ref="foo" value=""/>
because @value has to be an expression.
Steven
_______________________________________________
Xsltforms-support mailing list
Xsl...@li...<mailto:Xsl...@li...>
https://lists.sourceforge.net/lists/listinfo/xsltforms-support
|
|
From: Javier Diazestebaranz(UST,ES) <Jav...@us...> - 2021-06-10 17:21:30
|
Hello Steven,
thanks a lot for your help.
First of all, I have realized that I sent a wrong test case. In the setvalue 'error' I sent you the following: '<xforms-setvalue xf-ref="instance('salida')/datosTarea/numeroOrden" xf-value="aa"/>' instead '<xforms-setvalue xf-ref="instance('salida')/datosTarea/numeroOrden" xf-value=""/>. The original XForms source was as you thought, '<setvalue ref="foo" value=""/>'. It seems that older version ignored that emtpy value and cleared the value of the element in that case. We have corrected it (with <setvalue ref="foo"/>) and now it doesn't fail.
The other problem related with 'bind', I also sent a bad test case. We have discovered that it only fails when 'bind' elements are not at the end of model part. So, if you put:
(..)
<xforms-submission id="enviar" xf-method="get" xf-mode="synchronous" xf-ref="instance('salida')/datosTarea" xf-resource="fake">
<xforms-action ev-event="xforms-submit-error">
<xforms-setvalue xf-ref="instance('salida')/datosTarea/numeroOrden"/>
</xforms-action>
</xforms-submission>
<xforms-bind id="bind_numeroOrden" xf-ref="instance('salida')/datosTarea/numeroOrden" xf-required="true()" xf-type="xsd:string"/>
</xforms-model>
(...)
It works ok, but if you put:
(...)
<xforms-bind id="bind_numeroOrden" xf-ref="instance('salida')/datosTarea/numeroOrden" xf-required="true()" xf-type="xsd:string"/>
<xforms-submission id="enviar" xf-method="get" xf-mode="synchronous" xf-ref="instance('salida')/datosTarea" xf-resource="fake">
<xforms-action ev-event="xforms-submit-error">
<xforms-setvalue xf-ref="instance('salida')/datosTarea/numeroOrden"/>
</xforms-action>
</xforms-submission>
</xforms-model>
(...)
It fails. Is there any rule about the order of the model elements? In older version we mixed them and there wasn't any error.
We have also found another problem, regarding select1 and itemset, recovering the values from other instance (I send a testcase about this problem). If I put:
<xforms-itemset xf-ref="instance('inst_tarea')/vct">
<xforms-label xf-ref="elm[1]"/>
<xforms-value xf-ref="elm[2]"/>
</xforms-itemset>
Label is shown but value it is not processed and a 'undefined' value appears if I choose some element. If I change the order of the elements:
<xforms-itemset xf-ref="instance('inst_tarea')/vct">
<xforms-value xf-ref="elm[2]"/>
<xforms-label xf-ref="elm[1]"/>
</xforms-itemset>
There is no label shown, but the value is selected correctly. We have tried to change it in another way, but we had no luck.
Thank you,
Javier
El 10/6/21 a las 10:29, Steven Pemberton escribió:
On Thu, 10 Jun 2021 01:19:45 +0200, Javier Diazestebaranz(UST, ES) via Xsltforms-support <xsl...@li...><mailto:xsl...@li...> wrote:
Hello,
we are using a very ,very old Xsltforms implementation (r574, more than 8 years ago) with some local changes, and we want to migrate to last stable version.
Before starting the migration, I have been testing some of our xforms pages with last version (downloaded from here: https://github.com/AlainCouthures/declarative4all/blob/master/public/direct/xsltforms.zip , I m not sure if it is a stable one), and I came across some problems.
I have made a small test case, to check if we have some error in our code, there have been some syntax changes in xforms and we have to modify our code, or there is some error in last xsltform version, I hope somebody can help us.
I send attached the code (submission.html). We use the .xml version (we don't want to rewrite all our old code), but i think is easier to analyse the problem with .html version.
* The first error that appears when the form load is:
XSLTForms Exception
--------------------------
Error parsing the following XPath expression :
Unexpected char at ''
It seems this line have some problem, because when I comment out it, the error dissapears:
<xforms-setvalue xf-ref="instance('salida')/datosTarea/numeroOrden" xf-value=""/>
So this is the generated code, not your original XForms source, so I'm guessing here, but to set a value to the empty string, you use either
<setvalue ref="foo" value="''"/>
or equally good
<setvalue ref="foo"/>
This is not good:
<setvalue ref="foo" value=""/>
because @value has to be an expression.
Steven
|
|
From: Steven P. <ste...@cw...> - 2021-06-10 08:29:24
|
On Thu, 10 Jun 2021 01:19:45 +0200, Javier Diazestebaranz(UST, ES) via Xsltforms-support <xsl...@li...> wrote: > Hello, > > we are using a very ,very old Xsltforms implementation (r574, more than > 8 years ago) with some local changes, and we want to >migrate to last > stable version. > > Before starting the migration, I have been testing some of our xforms > pages with last version (downloaded from here: > https://>github.com/AlainCouthures/declarative4all/blob/master/public/direct/xsltforms.zip > , I m not sure if it is a stable one), and >I came across some problems. > > I have made a small test case, to check if we have some error in our > code, there have been some syntax changes in xforms and >we have to > modify our code, or there is some error in last xsltform version, I hope > somebody can help us. > > I send attached the code (submission.html). We use the .xml version (we > don't want to rewrite all our old code), but i think >is easier to > analyse the problem with .html version. > > * The first error that appears when the form load is: > > XSLTForms Exception > -------------------------- > > Error parsing the following XPath expression : > > > > Unexpected char at '' > > It seems this line have some problem, because when I comment out it, the > error dissapears: > > <xforms-setvalue xf-ref="instance('salida')/datosTarea/numeroOrden" > xf-value=""/> So this is the generated code, not your original XForms source, so I'm guessing here, but to set a value to the empty string, you use either <setvalue ref="foo" value="''"/> or equally good <setvalue ref="foo"/> This is not good: <setvalue ref="foo" value=""/> because @value has to be an expression. Steven |
|
From: Javier Diazestebaranz(UST,ES) <Jav...@us...> - 2021-06-09 23:35:42
|
Hello, we are using a very ,very old Xsltforms implementation (r574, more than 8 years ago) with some local changes, and we want to migrate to last stable version. Before starting the migration, I have been testing some of our xforms pages with last version (downloaded from here: https://github.com/AlainCouthures/declarative4all/blob/master/public/direct/xsltforms.zip , I m not sure if it is a stable one), and I came across some problems. I have made a small test case, to check if we have some error in our code, there have been some syntax changes in xforms and we have to modify our code, or there is some error in last xsltform version, I hope somebody can help us. I send attached the code (submission.html). We use the .xml version (we don't want to rewrite all our old code), but i think is easier to analyse the problem with .html version. * The first error that appears when the form load is: XSLTForms Exception -------------------------- Error parsing the following XPath expression : Unexpected char at '' It seems this line have some problem, because when I comment out it, the error dissapears: <xforms-setvalue xf-ref="instance('salida')/datosTarea/numeroOrden" xf-value=""/> * The second error that appears is: XSLTForms Exception -------------------------- Error dispatching event 'xforms-model-construct' : XsltForms_bind.prototype.recalculate@http://localhost/xsltforms1.5/xsltforms.js:10603:29<mailto:XsltForms_bind.prototype.recalculate@http://localhost/xsltforms1.5/xsltforms.js:10603:29> XsltForms_browser.forEach@http://localhost/xsltforms1.5/xsltforms.js:5115:11<mailto:XsltForms_browser.forEach@http://localhost/xsltforms1.5/xsltforms.js:5115:11> XsltForms_model.prototype.recalculate@http://localhost/xsltforms1.5/xsltforms.js:9477:20<mailto:XsltForms_model.prototype.recalculate@http://localhost/xsltforms1.5/xsltforms.js:9477:20> XsltForms_model.prototype.rebuild@http://localhost/xsltforms1.5/xsltforms.js:9473:8<mailto:XsltForms_model.prototype.rebuild@http://localhost/xsltforms1.5/xsltforms.js:9473:8> XsltForms_model.prototype.construct@http://localhost/xsltforms1.5/xsltforms.js:9453:8<mailto:XsltForms_model.prototype.construct@http://localhost/xsltforms1.5/xsltforms.js:9453:8> @http://localhost/xsltforms1.5/xsltforms.js:6101:85 XsltForms_xmlevents.dispatch@http://localhost/xsltforms1.5/xsltforms.js:6049:19<mailto:XsltForms_xmlevents.dispatch@http://localhost/xsltforms1.5/xsltforms.js:6049:19> XsltForms_xmlevents.dispatchList@http://localhost/xsltforms1.5/xsltforms.js:6018:23<mailto:XsltForms_xmlevents.dispatchList@http://localhost/xsltforms1.5/xsltforms.js:6018:23> init@http://localhost/xsltforms1.5/xsltforms.js:2381:23<mailto:init@http://localhost/xsltforms1.5/xsltforms.js:2381:23> func@http://localhost/xsltforms1.5/xsltforms.js:3040:5<mailto:func@http://localhost/xsltforms1.5/xsltforms.js:3040:5> TypeError el.children[j].xfElement.recalculate is not a function And in this case the problem I think is in line: <xforms-bind id="bind_numeroOrden" xf-ref="instance('salida')/datosTarea/numeroOrden" xf-required="true()" xf-type="xsd:string"/> Because it doesn't appear without it. Best Regards, Javier |
|
From: Steven P. <ste...@cw...> - 2021-05-25 20:07:45
|
On Mon, 24 May 2021 16:41:31 +0200, Joe Wicentowski <jo...@gm...> wrote: > Hi all, > > I'm not sure if videos of the presentations will be posted or not, but > for anyone who missed them, Alain's paper is part of >the proceedings: The talks were not alas recorded. > > https://markupuk.org/webhelp/index.html#ar03.html > > ... and Steven's talk about his XForms tutorials discuss his use of > XSLTForms: > > https://markupuk.org/webhelp/index.html#helloder.html My slides are here: https://homepages.cwi.nl/~steven/Talks/2021/05-22-markupuk/ Steven > > And if you haven't seen Steven's tutorial, you can find it here: > > https://homepages.cwi.nl/~steven/xforms/xforms-hands-on/ > > Joe |
|
From: Joe W. <jo...@gm...> - 2021-05-24 14:41:56
|
Hi all, I'm not sure if videos of the presentations will be posted or not, but for anyone who missed them, Alain's paper is part of the proceedings: https://markupuk.org/webhelp/index.html#ar03.html ... and Steven's talk about his XForms tutorials discuss his use of XSLTForms: https://markupuk.org/webhelp/index.html#helloder.html And if you haven't seen Steven's tutorial, you can find it here: https://homepages.cwi.nl/~steven/xforms/xforms-hands-on/ Joe |
|
From: Alain C. <ala...@ag...> - 2021-05-24 12:05:12
|
<!doctype html>
<html>
<head>
<meta charset="UTF-8">
</head>
<body>
<div>
Hi Alessandro,
</div>
<div class="default-style">
<br>
</div>
<div class="default-style">
Since XSLTForms 1.5, CSS styling is to be based on custom elements.
</div>
<div class="default-style">
<br>
</div>
<div class="default-style">
The easiest way to determine what is possible, is to look at the elements with the browser debugger.
</div>
<div class="default-style">
<br>
</div>
<div class="default-style">
In this case, the selected repeat item has an xf-selected attribute set to true. So, a CSS rule like this one should be the one you are look for:
</div>
<div class="default-style">
<br>
</div>
<div class="default-style">
<div>
#files-repeat > xforms-repeat-item[xf-selected = "true"] {
</div>
<div>
color: red;
</div>
<div>
}
</div>
<div>
<br>
</div>
<div class="default-style">
Thank you for your feedback!
</div>
<div class="default-style">
<br>
</div>
<div class="default-style">
--Alain
</div>
</div>
<blockquote type="cite">
<div>
Le 24/05/2021 13:27, Alessandro via Xsltforms-support <xsl...@li...> a écrit :
</div>
<div>
<br>
</div>
<div>
<br>
</div>
<div>
Steven and Ralph, thanks, but as I'm still not able to obtain the desired style effect, I give you a wider sight on my code.
<br>
</div>
<div>
<br>
</div>
<div>
I'm currently using XSLTForms 1.5.2 with exist-db. After extracting my data I put them within a variable, just to have the possibility of adjusting the date format for an easier Italian reading. Then I create an instance to contain the data. The displaying table enclosed within a repeat is intended to present the user with links to be used for opening the correlated files.
<br>
</div>
<div>
<br>
</div>
<div>
let $form :=
<br>
</div>
<div>
<html xmlns="<a href="http://www.w3.org/1999/xhtml">http://www.w3.org/1999/xhtml</a>" xmlns:xf="<a href="http://www.w3.org/2002/xforms">http://www.w3.org/2002/xforms</a>" xmlns:ev="<a href="http://www.w3.org/2001/xml-events">http://www.w3.org/2001/xml-events</a>" xmlns:xs="<a href="http://www.w3.org/2001/XMLSchema">http://www.w3.org/2001/XMLSchema</a>" xmlns:xsi="<a href="http://www.w3.org/2001/XMLSchema-instance">http://www.w3.org/2001/XMLSchema-instance</a>">
<br>
</div>
<div>
<head>
<br>
</div>
<div>
<link rel="stylesheet" type="text/css" href="resources/css/xsltforms_style.css" />
<br>
</div>
<div>
<script src="resources/data/my_javascripts.js"/>
<br>
</div>
<div>
<br>
</div>
<div>
<style type="text/css">
<br>
</div>
<div>
<!--/*--><css><![CDATA[/**/
<br>
</div>
<div>
/*]]>*/<!--/*--></css><!--*/-->
<br>
</div>
<div>
</style>
<br>
</div>
<div>
<br>
</div>
<div>
<xf:model>
<br>
</div>
<div>
<br>
</div>
<div>
<xf:instance id="files">
<br>
</div>
<div>
<data xmlns="">{$directory_files}</data>
<br>
</div>
<div>
</xf:instance>
<br>
</div>
<div>
<br>
</div>
<div>
<xf:instance id="URL-container" xmlns="">
<br>
</div>
<div>
<URL />
<br>
</div>
<div>
</xf:instance>
<br>
</div>
<div>
<br>
</div>
<div>
<xf:instance id="del-row-data" xmlns="">
<br>
</div>
<div>
<data>
<br>
</div>
<div>
<file_name/>
<br>
</div>
<div>
<row_num/>
<br>
</div>
<div>
</data>
<br>
</div>
<div>
</xf:instance>
<br>
</div>
<div>
<br>
</div>
<div>
<!-- DELETE ACTION -->
<br>
</div>
<div>
<xf:submission ref="instance('del-row-data')" id="delete" method="post" action="action_confirmation_1.xq?action=deldirfiles&amp;arch_id={$arch_id}&amp;f_id={$cart_id}&amp;t_id={$tab_id}&amp;r_id={$row_id}&amp;alert_text=Si è sicuri di voler eliminare la riga selezionata?" instance="" replace=""/>
<br>
</div>
<div>
<br>
</div>
<div>
</xf:model>
<br>
</div>
<div>
</head>
<br>
</div>
<div>
<body>
<br>
</div>
<div>
<center>
<br>
</div>
<div>
<h2 style="color:red">File contenuti nella cartella: «{$directory}»</h2>
<br>
</div>
<div>
<br>
</div>
<div>
<br/>
<br>
</div>
<div>
<br>
</div>
<div>
<xf:group ref="instance('files')">
<br>
</div>
<div>
<fieldset id="">
<br>
</div>
<div>
<div class="header-directory-files">
<br>
</div>
<div>
<table border="0">
<br>
</div>
<div>
<tr>
<br>
</div>
<div>
<td>
<br>
</div>
<div>
<div class="leftColumn">Apri file</div>
<br>
</div>
<div>
</td>
<br>
</div>
<div>
<td style="width: 348px;"/>
<br>
</div>
<div>
<td>
<br>
</div>
<div>
<div class="leftColumn">Ubi</div>
<br>
</div>
<div>
</td>
<br>
</div>
<div>
<td style="width: 3px;"/>
<br>
</div>
<div>
<td>
<br>
</div>
<div>
<div class="leftColumn">Data doc.</div>
<br>
</div>
<div>
</td>
<br>
</div>
<div>
<td>
<br>
</div>
<div>
<div class="leftColumn">Res.</div>
<br>
</div>
<div>
</td>
<br>
</div>
<div>
</tr>
<br>
</div>
<div>
</table>
<br>
</div>
<div>
</div>
<br>
</div>
<div>
<xf:repeat nodeset="files/file" id="files-repeat">
<br>
</div>
<div>
<table border="0" >
<br>
</div>
<div>
<tr>
<br>
</div>
<div>
<td>
<br>
</div>
<div>
<xf:trigger submission="replace-form-with" appearance="minimal" class="url">
<br>
</div>
<div>
<xf:label>
<br>
</div>
<div>
<xf:output class="url" ref="link-text" style="width:400px;"/>
<br>
</div>
<div>
</xf:label>
<br>
</div>
<div>
<br>
</div>
<div>
<xf:action ev:event="DOMActivate">
<br>
</div>
<div>
<xf:setvalue class="url" ref="instance('URL-container')" value="concat('{$host}','exist/apps/DATI/', '{$trow_storage}','/',instance('files')/files/file[index('files-repeat')]/link-file-name,'.',instance('files')/files/file[index('files-repeat')]/link-est)" />
<br>
</div>
<div>
<br>
</div>
<div>
<xf:load ref="instance('URL-container')" />
<br>
</div>
<div>
</xf:action>
<br>
</div>
<div>
</xf:trigger>
<br>
</div>
<div>
</td>
<br>
</div>
<div>
<td style="width: 20px;"/>
<br>
</div>
<div>
<td>
<br>
</div>
<div>
<xf:output style="width:10px;" ref="ubi"/>
<br>
</div>
<div>
</td>
<br>
</div>
<div>
<td style="width: 20px;"/>
<br>
</div>
<div>
<td>
<br>
</div>
<div>
<xf:output style="width:60px;" ref="data1"/>
<br>
</div>
<div>
</td>
<br>
</div>
<div>
<td style="width: 20px;"/>
<br>
</div>
<div>
<td>
<br>
</div>
<div>
<xf:output ref="resp"/>
<br>
</div>
<div>
</td>
<br>
</div>
<div>
</tr>
<br>
</div>
<div>
</table>
<br>
</div>
<div>
<br>
</div>
<div>
</xf:repeat>
<br>
</div>
<div>
</fieldset>
<br>
</div>
<div>
<br>
</div>
<div>
<br/>
<br>
</div>
<div>
<br>
</div>
<div>
<table border="0">
<br>
</div>
<div>
<tr>
<br>
</div>
<div>
<td style="width: 15px;"/>
<br>
</div>
<div>
<td>
<br>
</div>
<div>
<xf:submit submission="delete">
<br>
</div>
<div>
<xf:label><div class="my_special_button" style="width: 150px;">Elimina riga selezionata</div></xf:label>
<br>
</div>
<div>
<xf:action ev:event="DOMActivate">
<br>
</div>
<div>
<xf:setvalue ref="instance('del-row-data')/file_name/text()" value="instance('files')/files/file[index('files-repeat')]/link-file-name" />
<br>
</div>
<div>
<xf:setvalue ref="instance('del-row-data')/row_num/text()" value="instance('files')/files/file[index('files-repeat')]/tr-id" />
<br>
</div>
<div>
</xf:action>
<br>
</div>
<div>
<xf:delete ev:event="DOMActivate" nodeset="."/>
<br>
</div>
<div>
</xf:submit>
<br>
</div>
<div>
</td>
<br>
</div>
<div>
</tr>
<br>
</div>
<div>
</table>
<br>
</div>
<div>
<br>
</div>
<div>
</xf:group>
<br>
</div>
<div>
</center>
<br>
</div>
<div>
</body>
<br>
</div>
<div>
</html>
<br>
</div>
<div>
let $xslt-pi := processing-instruction xml-stylesheet {'type="text/xsl" href="../xsltforms/xsltforms.xsl"'}
<br>
</div>
<div>
return ($xslt-pi,$form)
<br>
</div>
<div>
<br>
</div>
<div>
Many thanks
<br>
</div>
<div>
Alex
<br>
</div>
<div>
<br>
</div>
<div>
--
<br>
</div>
<div>
Inviato in modo sicuro con Tutanota. Ottieni la tua casella di posta elettronica crittografata e senza pubblicità:
<br>
</div>
<div>
https://tutanota.com
<br>
</div>
<div>
<br>
</div>
<div>
<br>
</div>
<div>
24 mag 2021, 11:16 da xsl...@li...:
<br>
</div>
<blockquote>
<div>
Hi all!
<br>
</div>
<div>
I'm probably not able to find the right CSS syntax for highlighting the current selected row within a repeat...
<br>
</div>
<div>
The only indications I can find are the following, but no matter where I write them (inside an external css file or directly within the xsltform) I'm not able to obtain any positive result.
<br>
</div>
<div>
<br>
</div>
<div>
.xforms-repeat-item-selected > * {
<br>
</div>
<div>
color: red; background-color: white; font-weight:bold; border-bottom:solid 5px #f2f0fb;
<br>
</div>
<div>
}
<br>
</div>
<div>
or:
<br>
</div>
<div>
.xforms-repeat-item-selected {color: blue; background-color: white;}
<br>
</div>
<div>
<br>
</div>
<div>
Thanks
<br>
</div>
<div>
Alex
<br>
</div>
<div>
<br>
</div>
<div>
--
<br>
</div>
<div>
Inviato in modo sicuro con Tutanota. Ottieni la tua casella di posta elettronica crittografata e senza pubblicità:
<br>
</div>
<div>
https://tutanota.com
<br>
</div>
</blockquote>
<div>
<br>
</div>_______________________________________________ Xsltforms-support mailing list Xsl...@li... https://lists.sourceforge.net/lists/listinfo/xsltforms-support
</blockquote>
</body>
</html>
|
|
From: Alessandro <ca...@tu...> - 2021-05-24 11:28:01
|
Steven and Ralph, thanks, but as I'm still not able to obtain the desired style effect, I give you a wider sight on my code. I'm currently using XSLTForms 1.5.2 with exist-db. After extracting my data I put them within a variable, just to have the possibility of adjusting the date format for an easier Italian reading. Then I create an instance to contain the data. The displaying table enclosed within a repeat is intended to present the user with links to be used for opening the correlated files. let $form := <html xmlns="http://www.w3.org/1999/xhtml" xmlns:xf="http://www.w3.org/2002/xforms" xmlns:ev="http://www.w3.org/2001/xml-events" 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/xsltforms_style.css" /> <script src="resources/data/my_javascripts.js"/> <style type="text/css"> <!--/*--><css><![CDATA[/**/ /*]]>*/<!--/*--></css><!--*/--> </style> <xf:model> <xf:instance id="files"> <data xmlns="">{$directory_files}</data> </xf:instance> <xf:instance id="URL-container" xmlns=""> <URL /> </xf:instance> <xf:instance id="del-row-data" xmlns=""> <data> <file_name/> <row_num/> </data> </xf:instance> <!-- DELETE ACTION --> <xf:submission ref="instance('del-row-data')" id="delete" method="post" action="action_confirmation_1.xq?action=deldirfiles&arch_id={$arch_id}&f_id={$cart_id}&t_id={$tab_id}&r_id={$row_id}&alert_text=Si è sicuri di voler eliminare la riga selezionata?" instance="" replace=""/> </xf:model> </head> <body> <center> <h2 style="color:red">File contenuti nella cartella: «{$directory}»</h2> <br/> <xf:group ref="instance('files')"> <fieldset id=""> <div class="header-directory-files"> <table border="0"> <tr> <td> <div class="leftColumn">Apri file</div> </td> <td style="width: 348px;"/> <td> <div class="leftColumn">Ubi</div> </td> <td style="width: 3px;"/> <td> <div class="leftColumn">Data doc.</div> </td> <td> <div class="leftColumn">Res.</div> </td> </tr> </table> </div> <xf:repeat nodeset="files/file" id="files-repeat"> <table border="0" > <tr> <td> <xf:trigger submission="replace-form-with" appearance="minimal" class="url"> <xf:label> <xf:output class="url" ref="link-text" style="width:400px;"/> </xf:label> <xf:action ev:event="DOMActivate"> <xf:setvalue class="url" ref="instance('URL-container')" value="concat('{$host}','exist/apps/DATI/', '{$trow_storage}','/',instance('files')/files/file[index('files-repeat')]/link-file-name,'.',instance('files')/files/file[index('files-repeat')]/link-est)" /> <xf:load ref="instance('URL-container')" /> </xf:action> </xf:trigger> </td> <td style="width: 20px;"/> <td> <xf:output style="width:10px;" ref="ubi"/> </td> <td style="width: 20px;"/> <td> <xf:output style="width:60px;" ref="data1"/> </td> <td style="width: 20px;"/> <td> <xf:output ref="resp"/> </td> </tr> </table> </xf:repeat> </fieldset> <br/> <table border="0"> <tr> <td style="width: 15px;"/> <td> <xf:submit submission="delete"> <xf:label><div class="my_special_button" style="width: 150px;">Elimina riga selezionata</div></xf:label> <xf:action ev:event="DOMActivate"> <xf:setvalue ref="instance('del-row-data')/file_name/text()" value="instance('files')/files/file[index('files-repeat')]/link-file-name" /> <xf:setvalue ref="instance('del-row-data')/row_num/text()" value="instance('files')/files/file[index('files-repeat')]/tr-id" /> </xf:action> <xf:delete ev:event="DOMActivate" nodeset="."/> </xf:submit> </td> </tr> </table> </xf:group> </center> </body> </html> let $xslt-pi := processing-instruction xml-stylesheet {'type="text/xsl" href="../xsltforms/xsltforms.xsl"'} return ($xslt-pi,$form) Many thanks Alex -- Inviato in modo sicuro con Tutanota. Ottieni la tua casella di posta elettronica crittografata e senza pubblicità: https://tutanota.com 24 mag 2021, 11:16 da xsl...@li...: > Hi all! > I'm probably not able to find the right CSS syntax for highlighting the current selected row within a repeat... > The only indications I can find are the following, but no matter where I write them (inside an external css file or directly within the xsltform) I'm not able to obtain any positive result. > > .xforms-repeat-item-selected > * { > color: red; background-color: white; font-weight:bold; border-bottom:solid 5px #f2f0fb; > } > or: > .xforms-repeat-item-selected {color: blue; background-color: white;} > > Thanks > Alex > > -- > Inviato in modo sicuro con Tutanota. Ottieni la tua casella di posta elettronica crittografata e senza pubblicità: > https://tutanota.com > |
|
From: Ralph C. <ra...@ra...> - 2021-05-24 09:56:35
|
Hi Alessandro,
I'm using a simple setup with the key CSS as follows that seems to work:
<head>
...
<style>.xforms-repeat-item-selected {background-color: grey;}</style>
</head>
Ralph
(and I fear my own question is heading this way shortly...)
On 24/05/2021 10:16, Alessandro via Xsltforms-support wrote:
> Hi all!
> I'm probably not able to find the right CSS syntax for highlighting the current selected row within a repeat...
> The only indications I can find are the following, but no matter where I write them (inside an external css file or directly within the xsltform) I'm not able to obtain any positive result.
>
> .xforms-repeat-item-selected > * {
> color: red; background-color: white; font-weight:bold; border-bottom:solid 5px #f2f0fb;
> }
> or:
> .xforms-repeat-item-selected {color: blue; background-color: white;}
>
> Thanks
> Alex
>
> --
> Inviato in modo sicuro con Tutanota. Ottieni la tua casella di posta elettronica crittografata e senza pubblicità:
> https://tutanota.com
> _______________________________________________
> Xsltforms-support mailing list
> Xsl...@li...
> https://lists.sourceforge.net/lists/listinfo/xsltforms-support |
|
From: Steven P. <ste...@cw...> - 2021-05-24 09:51:30
|
https://homepages.cwi.nl/~steven/xforms11-for-html-authors/todo.xml Part of https://homepages.cwi.nl/~steven/xforms11-for-html-authors/part2.html Steven On Mon, 24 May 2021 11:16:27 +0200, Alessandro via Xsltforms-support <xsl...@li...> wrote: > Hi all! > I'm probably not able to find the right CSS syntax for highlighting the > current selected row within a repeat... > The only indications I can find are the following, but no matter where I > write them (inside an external css file or directly >within the > xsltform) I'm not able to obtain any positive result. > > .xforms-repeat-item-selected > * { > color: red; background-color: white; font-weight:bold; > border-bottom:solid 5px #f2f0fb; > } > or: > .xforms-repeat-item-selected {color: blue; background-color: white;} > > Thanks > Alex > > --Inviato in modo sicuro con Tutanota. Ottieni la tua casella di posta > elettronica crittografata e senza pubblicità:https://tutanota.com |
|
From: Alessandro <ca...@tu...> - 2021-05-24 09:16:44
|
Hi all!
I'm probably not able to find the right CSS syntax for highlighting the current selected row within a repeat...
The only indications I can find are the following, but no matter where I write them (inside an external css file or directly within the xsltform) I'm not able to obtain any positive result.
.xforms-repeat-item-selected > * {
color: red; background-color: white; font-weight:bold; border-bottom:solid 5px #f2f0fb;
}
or:
.xforms-repeat-item-selected {color: blue; background-color: white;}
Thanks
Alex
--
Inviato in modo sicuro con Tutanota. Ottieni la tua casella di posta elettronica crittografata e senza pubblicità:
https://tutanota.com
|
|
From: Tim T. <tim...@gm...> - 2021-03-31 00:54:24
|
Gary, My perspective as an XForms user: XQuery is designed for querying and working with document structures, which makes it a great fit for declarative client-side DOM manipulation--as I recall, the XQuery implementation in Fleur.js lets users manipulate the HTML5 DOM directly (even though it's not well-formed XML). XQuery is a superset of XPath, so client-side XQuery is the pathway to adding support for XPath 3.0 and XForms 2.0 features to XSLTForms. Tim -- Tim A. Thompson Metadata Librarian Yale University Library On Tue, Mar 30, 2021 at 2:00 PM Gary Kopp <ge...@ru...> wrote: > Thanks, Alain. Your explanation is very helpful, and thought-provoking. I > imagine other new outsiders will also find it helpful. > > > > A question, if you will indulge someone that doesn’t fully understand the > XForms technology landscape yet. Why do we need a new XQuery engine? I > believe XQuery on the server side is already well supported (but I could be > misunderstanding something). It seems Fleur.js will allow also XQuery on > the browser side, but I personally don’t see a use case for that. I’m sure > I’m missing something… > > > > --Gary > > > > *From:* Alain Couthures <ala...@ag...> > *Sent:* Tuesday, March 30, 2021 11:20 AM > *To:* Gary Kopp <ge...@ru...>; > xsl...@li... > *Subject:* Re: [Xsltforms-support] Declarative4all Overview? > > > > When developing web applications, XForms, because it has been specified to > be implemented in browsers, is not enough. > > > > XSLTForms is a client-side XForms implementation using XSLT 1.0 as a trick > to transform XForms pages into HTML pages with CSS and Javascript. It works > within browsers... > > > > XSLT 1.0 is still supported in major browsers, but vendors would like to > get the corresponding memory space for new features instead... XSLTForms > must evolve... > > > > Since 1.5, XSLTForms uses its own HTML5 notation for XForms. It allows > authors, if they prefer this, to write forms directly without the XSLT step > being required, which, is now also available in Javascript for Nodejs! BTW, > Cordova supports this HTML5 notation, too. > > > > The XPath engine of XSLTForms is also evolving. The corresponding parser > has been rewritten from XSLT 1.0 to Javascript. This parser has been > extended to support XQuery 3.1. Then, a new XQuery engine has been created, > named Fleur.js, for both browsers and Nodejs. > > > > We, also, have Nodejs to easily develop and run light HTTP servers. It > allows XQuery at server-side (with Fleur.js) to access files, query other > web servers, ... and XForms at client-side (with XSLTForms) to render and > modify data. > > > > Next step: Fleur.js for XSLTForms is now in alpha... > > > > So, Declarative4all is a project to host all that stuff and more... It is > the not-private part of the dev environment, actually... > > > > --Alain > > Le 29/03/2021 20:22, Gary Kopp <ge...@ru...> a écrit : > > > > > > I’m new to XForms with eXist and quickly realized I needed XSLTForms to > get started. I found XSLTForms 1.3 on Github and thought I was done, > although I was concerned that it hadn’t been updated for years. Then I was > given a link to Declarative4all and now see that XSLTForms is alive and > quite well. But I’m a little confused – is Declarative4all just an > xsltforms.js upgrade, or is there more to it from a functional standpoint? > Is there a summary statement somewhere of what Declarative4all actually is? > > > > --Gary Kopp > > _______________________________________________ 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 > |
|
From: Gary K. <ge...@ru...> - 2021-03-30 17:59:34
|
Thanks, Alain. Your explanation is very helpful, and thought-provoking. I imagine other new outsiders will also find it helpful. A question, if you will indulge someone that doesn’t fully understand the XForms technology landscape yet. Why do we need a new XQuery engine? I believe XQuery on the server side is already well supported (but I could be misunderstanding something). It seems Fleur.js will allow also XQuery on the browser side, but I personally don’t see a use case for that. I’m sure I’m missing something… --Gary From: Alain Couthures <ala...@ag...> Sent: Tuesday, March 30, 2021 11:20 AM To: Gary Kopp <ge...@ru...>; xsl...@li... Subject: Re: [Xsltforms-support] Declarative4all Overview? When developing web applications, XForms, because it has been specified to be implemented in browsers, is not enough. XSLTForms is a client-side XForms implementation using XSLT 1.0 as a trick to transform XForms pages into HTML pages with CSS and Javascript. It works within browsers... XSLT 1.0 is still supported in major browsers, but vendors would like to get the corresponding memory space for new features instead... XSLTForms must evolve... Since 1.5, XSLTForms uses its own HTML5 notation for XForms. It allows authors, if they prefer this, to write forms directly without the XSLT step being required, which, is now also available in Javascript for Nodejs! BTW, Cordova supports this HTML5 notation, too. The XPath engine of XSLTForms is also evolving. The corresponding parser has been rewritten from XSLT 1.0 to Javascript. This parser has been extended to support XQuery 3.1. Then, a new XQuery engine has been created, named Fleur.js, for both browsers and Nodejs. We, also, have Nodejs to easily develop and run light HTTP servers. It allows XQuery at server-side (with Fleur.js) to access files, query other web servers, ... and XForms at client-side (with XSLTForms) to render and modify data. Next step: Fleur.js for XSLTForms is now in alpha... So, Declarative4all is a project to host all that stuff and more... It is the not-private part of the dev environment, actually... --Alain Le 29/03/2021 20:22, Gary Kopp <ge...@ru... <mailto:ge...@ru...> > a écrit : I’m new to XForms with eXist and quickly realized I needed XSLTForms to get started. I found XSLTForms 1.3 on Github and thought I was done, although I was concerned that it hadn’t been updated for years. Then I was given a link to Declarative4all and now see that XSLTForms is alive and quite well. But I’m a little confused – is Declarative4all just an xsltforms.js upgrade, or is there more to it from a functional standpoint? Is there a summary statement somewhere of what Declarative4all actually is? --Gary Kopp _______________________________________________ Xsltforms-support mailing list Xsl...@li... <mailto:Xsl...@li...> https://lists.sourceforge.net/lists/listinfo/xsltforms-support |
|
From: Alain C. <ala...@ag...> - 2021-03-30 17:29:49
|
<!doctype html>
<html>
<head>
<meta charset="UTF-8">
</head>
<body>
<div>
Tim,
</div>
<div class="default-style">
<br>
</div>
<div class="default-style">
Since XSLTForms 1.5, repeats within tables are converted into attributes ("xf-repeat-ref" or "xf-repeat-bind") without adding potentially missing tbody elements.
</div>
<div class="default-style">
<br>
</div>
<div class="default-style">
XSLTForms 1.5.4 now supports table/xf:repeat, not just tbody/xf:repeat.
</div>
<div class="default-style">
<br>
</div>
<div class="default-style">
Nevertheless, browsers add tbody element when not present. It does not seem to disturb XSLTForms in small test cases... Explicit tbody element sounds more secure...
</div>
<div class="default-style">
<br>
</div>
<div class="default-style">
Thank you for your feedback!
</div>
<div class="default-style">
<br>
</div>
<div class="default-style">
--Alain
</div>
<blockquote type="cite">
<div>
Le 29/03/2021 19:36, Tim Thompson <tim...@gm...> a écrit :
</div>
<div>
<br>
</div>
<div>
<br>
</div>
<div dir="ltr">
<div>
Thank you, Alain!
<br>
</div>
<div>
<br>
</div>
<div>
Is it possible to generate a table without a "tbody" element? With 1.5.3, removing "tbody" in my sample form still throws a "TypeError: Cannot read property 'localName' of null" in Chrome, but works in Firefox.
<br>
</div>
<div>
<br>
</div>
<div>
Best regards,
</div>
<div>
Tim
</div>
<div>
<br>
</div>
<div>
<br>
</div>
<div>
<div data-smartmail="gmail_signature" class="gmail_signature" dir="ltr">
<div dir="ltr">
--
<br>Tim A. Thompson
<br>Metadata Librarian
<br>Yale University Library
<br>
<br>
</div>
</div>
</div>
<br>
</div>
<br>
<div class="gmail_quote">
<div class="gmail_attr" dir="ltr">
On Mon, Mar 29, 2021 at 1:25 PM Alain Couthures <<a href="mailto:ala...@ag...">ala...@ag...</a>> wrote:
<br>
</div>
<blockquote>
<u></u>
<div>
<div>
Hello Tim,
</div>
<div>
<br>
</div>
<div>
There was a missing initialization in XSLTForms 1.5.2 for table repeats within a repeat.
</div>
<div>
<br>
</div>
<div>
This has been added as XSLTForms 1.5.3 at <a target="_blank" href="https://github.com/AlainCouthures/declarative4all/raw/master/public/direct/xsltforms.zip" rel="noopener">https://github.com/AlainCouthures/declarative4all/raw/master/public/direct/xsltforms.zip</a>
<br>
</div>
<div>
<br>
</div>
<div>
Because of XPath 3 support to be committed in next major release, XSLTForms 1.5.3 can use both current and future XPath engines. It is just an intermediate release. Please check all your forms!
</div>
<div>
<br>
</div>
<div>
Kind regards,
</div>
<div>
<br>
</div>
<div>
--Alain
</div>
<blockquote type="cite">
<div>
Le 28/03/2021 23:03, Tim Thompson <<a target="_blank" href="mailto:tim...@gm..." rel="noopener">tim...@gm...</a>> a écrit :
</div>
<div>
<br>
</div>
<div>
<br>
</div>
<div dir="ltr">
<div>
Thanks again, Josselin, Habs. Yes, I was using the latest version of XSLTForms, 1.5.2. If I remove the "tbody" element, the form works in Firefox, but throws an error in Chrome. However, if I revert to version 1.4, then it works both with and without "tbody," in both Firefox and Chrome. The issue seems to arise starting with version 1.5beta (655).
<br>
</div>
<div>
<br>
</div>
<div>
Best regards,
</div>
<div>
Tim
</div>
<div>
<br>
</div>
<div>
<br>
</div>
<div>
<div dir="ltr">
<div dir="ltr">
--
<br>Tim A. Thompson
<br>Metadata Librarian
<br>Yale University Library
<br>
</div>
</div>
</div>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">
On Sun, Mar 28, 2021 at 3:44 PM Habs <<a target="_blank" href="mailto:ge...@us..." rel="noopener">ge...@us...</a>> wrote:
<br>
</div>
<blockquote>
On Sun, 28 Mar 2021, Tim Thompson wrote:
<br>
<br>> Thanks, Habs! Where you say the "tbody" tags are removed, do you mean in the XForm itself, or from the rendered HTML? If I remove them from the XForm, I
<br>> still get an error.
<br>>
<br>> However, if I copy the rendered content of the form, save it, and open it in the browser, then the table displays correctly. (See attached.) So, there must
<br>> be something in the XSLTForms JavaScript that is hiding the content?
<br>>
<br>
<br>Hi Tim
<br>
<br>Yes I removed the tbody from the Xform and it worked on my setup with
<br>latest xsltforms series (not sure what revision though sorry).
<br>
<br>I took your stripped (of anything but essential?!) Xform and plugged it
<br>into my goto basic xhtml document format (headers etc) on my test server.
<br>
<br>I simplify xforms to the absolute basics in problem cases I've had - see
<br>if that works and then build back up from there.
<br>
<br>I'll have another play and see if I can spot anything else.
<br>
<br>If you want my test version of your form let me know.
<br>
<br>Regards
<br>
<br>--- Sent using Alpine/Pine, probably the best MUA ---
<br>
</blockquote>
</div>_______________________________________________ Xsltforms-support mailing list <a target="_blank" href="mailto:Xsl...@li..." rel="noopener">Xsl...@li...</a> <a target="_blank" href="https://lists.sourceforge.net/lists/listinfo/xsltforms-support" rel="noopener">https://lists.sourceforge.net/lists/listinfo/xsltforms-support</a>
</blockquote>
</div>
</blockquote>
</div>
</blockquote>
</body>
</html>
|
|
From: Alain C. <ala...@ag...> - 2021-03-30 17:20:50
|
<!doctype html>
<html>
<head>
<meta charset="UTF-8">
</head>
<body>
<div>
When developing web applications, XForms, because it has been specified to be implemented in browsers, is not enough.
</div>
<div class="default-style">
<br>
</div>
<div class="default-style">
XSLTForms is a client-side XForms implementation using XSLT 1.0 as a trick to transform XForms pages into HTML pages with CSS and Javascript. It works within browsers...
</div>
<div class="default-style">
<br>
</div>
<div class="default-style">
XSLT 1.0 is still supported in major browsers, but vendors would like to get the corresponding memory space for new features instead... XSLTForms must evolve...
</div>
<div class="default-style">
<br>
</div>
<div class="default-style">
Since 1.5, XSLTForms uses its own HTML5 notation for XForms. It allows authors, if they prefer this, to write forms directly without the XSLT step being required, which, is now also available in Javascript for Nodejs! BTW, Cordova supports this HTML5 notation, too.
</div>
<div class="default-style">
<br>
</div>
<div class="default-style">
The XPath engine of XSLTForms is also evolving. The corresponding parser has been rewritten from XSLT 1.0 to Javascript. This parser has been extended to support XQuery 3.1. Then, a new XQuery engine has been created, named Fleur.js, for both browsers and Nodejs.
</div>
<div class="default-style">
<div class="default-style">
<br>
</div>
<div class="default-style">
We, also, have Nodejs to easily develop and run light HTTP servers. It allows XQuery at server-side (with Fleur.js) to access files, query other web servers, ... and XForms at client-side (with XSLTForms) to render and modify data.
</div>
</div>
<div class="default-style">
<br>
</div>
<div class="default-style">
Next step: Fleur.js for XSLTForms is now in alpha...
</div>
<div class="default-style">
<br>
</div>
<div class="default-style">
So, Declarative4all is a project to host all that stuff and more... It is the not-private part of the dev environment, actually...
</div>
<div class="default-style">
<br>
</div>
<div class="default-style">
--Alain
</div>
<blockquote type="cite">
<div>
Le 29/03/2021 20:22, Gary Kopp <ge...@ru...> a écrit :
</div>
<div>
<br>
</div>
<div>
<br>
</div>
<div class="WordSection1">
<p class="MsoNormal">I’m new to XForms with eXist and quickly realized I needed XSLTForms to get started. I found XSLTForms 1.3 on Github and thought I was done, although I was concerned that it hadn’t been updated for years. Then I was given a link to Declarative4all and now see that XSLTForms is alive and quite well. But I’m a little confused – is Declarative4all just an xsltforms.js upgrade, or is there more to it from a functional standpoint? Is there a summary statement somewhere of what Declarative4all actually is?</p>
<p class="MsoNormal"><br></p>
<p class="MsoNormal">--Gary Kopp</p>
</div>_______________________________________________ Xsltforms-support mailing list Xsl...@li... https://lists.sourceforge.net/lists/listinfo/xsltforms-support
</blockquote>
</body>
</html>
|
|
From: Steven P. <ste...@cw...> - 2021-03-30 12:53:07
|
It's heading in the direction of XForms 2, adding new features at each release I guess. The most important one implemented is Attribute Value Templates. Steven On Monday 29 March 2021 23:00:43 (+02:00), Gary Kopp wrote: Does xsltforms 1.5.x support the XForms 2.0 spec, or am I still limited to XForms 1.0 functionality? Which would be OK with me, but I just need to know. --Gary |
|
From: Tim T. <tim...@gm...> - 2021-03-29 21:51:24
|
Hi, Gary, Not to speak for Alain (the developer of the XSLTForms), but 1.5.x does implement some features of XForms 2.0 (which has not yet been finalized), but is currently described as "XForms 1.1+ with XPath 1.0+ Engine." In the next major version of XSLTForms, I believe Alain plans to include support for XPath 3.0. XSLTForms also has some additional features that are not part of the spec. Are there particular 2.0 features that you were looking for? All best, Tim -- Tim A. Thompson Metadata Librarian Yale University Library On Mon, Mar 29, 2021 at 5:01 PM Gary Kopp <ge...@ru...> wrote: > Does xsltforms 1.5.x support the XForms 2.0 spec, or am I still limited to > XForms 1.0 functionality? Which would be OK with me, but I just need to > know. > > > > --Gary > _______________________________________________ > Xsltforms-support mailing list > Xsl...@li... > https://lists.sourceforge.net/lists/listinfo/xsltforms-support > |
|
From: Gary K. <ge...@ru...> - 2021-03-29 21:01:33
|
Does xsltforms 1.5.x support the XForms 2.0 spec, or am I still limited to XForms 1.0 functionality? Which would be OK with me, but I just need to know. --Gary |
|
From: Gary K. <ge...@ru...> - 2021-03-29 18:22:54
|
I'm new to XForms with eXist and quickly realized I needed XSLTForms to get started. I found XSLTForms 1.3 on Github and thought I was done, although I was concerned that it hadn't been updated for years. Then I was given a link to Declarative4all and now see that XSLTForms is alive and quite well. But I'm a little confused - is Declarative4all just an xsltforms.js upgrade, or is there more to it from a functional standpoint? Is there a summary statement somewhere of what Declarative4all actually is? --Gary Kopp |
|
From: Alain C. <ala...@ag...> - 2021-03-29 17:38:18
|
<!doctype html> <html> <head> <meta charset="UTF-8"> </head> <body> <div> Hello Tim, </div> <div class="default-style"> <br> </div> <div class="default-style"> There was a missing initialization in XSLTForms 1.5.2 for table repeats within a repeat. </div> <div class="default-style"> <br> </div> <div class="default-style"> This has been added as XSLTForms 1.5.3 at <a href="https://github.com/AlainCouthures/declarative4all/raw/master/public/direct/xsltforms.zip">https://github.com/AlainCouthures/declarative4all/raw/master/public/direct/xsltforms.zip</a> <br> </div> <div class="default-style"> <br> </div> <div class="default-style"> Because of XPath 3 support to be committed in next major release, XSLTForms 1.5.3 can use both current and future XPath engines. It is just an intermediate release. Please check all your forms! </div> <div class="default-style"> <br> </div> <div class="default-style"> Kind regards, </div> <div class="default-style"> <br> </div> <div class="default-style"> --Alain </div> <blockquote type="cite"> <div> Le 28/03/2021 23:03, Tim Thompson <tim...@gm...> a écrit : </div> <div> <br> </div> <div> <br> </div> <div dir="ltr"> <div> Thanks again, Josselin, Habs. Yes, I was using the latest version of XSLTForms, 1.5.2. If I remove the "tbody" element, the form works in Firefox, but throws an error in Chrome. However, if I revert to version 1.4, then it works both with and without "tbody," in both Firefox and Chrome. The issue seems to arise starting with version 1.5beta (655). <br> </div> <div> <br> </div> <div> Best regards, </div> <div> Tim </div> <div> <br> </div> <div> <br> </div> <div> <div data-smartmail="gmail_signature" class="gmail_signature" dir="ltr"> <div dir="ltr"> -- <br>Tim A. Thompson <br>Metadata Librarian <br>Yale University Library <br> </div> </div> </div> </div> <br> <div class="gmail_quote"> <div class="gmail_attr" dir="ltr"> On Sun, Mar 28, 2021 at 3:44 PM Habs <<a href="mailto:ge...@us...">ge...@us...</a>> wrote: <br> </div> <blockquote> On Sun, 28 Mar 2021, Tim Thompson wrote: <br> <br>> Thanks, Habs! Where you say the "tbody" tags are removed, do you mean in the XForm itself, or from the rendered HTML? If I remove them from the XForm, I <br>> still get an error. <br>> <br>> However, if I copy the rendered content of the form, save it, and open it in the browser, then the table displays correctly. (See attached.) So, there must <br>> be something in the XSLTForms JavaScript that is hiding the content? <br>> <br> <br>Hi Tim <br> <br>Yes I removed the tbody from the Xform and it worked on my setup with <br>latest xsltforms series (not sure what revision though sorry). <br> <br>I took your stripped (of anything but essential?!) Xform and plugged it <br>into my goto basic xhtml document format (headers etc) on my test server. <br> <br>I simplify xforms to the absolute basics in problem cases I've had - see <br>if that works and then build back up from there. <br> <br>I'll have another play and see if I can spot anything else. <br> <br>If you want my test version of your form let me know. <br> <br>Regards <br> <br>--- Sent using Alpine/Pine, probably the best MUA --- <br> </blockquote> </div>_______________________________________________ Xsltforms-support mailing list Xsl...@li... https://lists.sourceforge.net/lists/listinfo/xsltforms-support </blockquote> </body> </html> |
|
From: Tim T. <tim...@gm...> - 2021-03-29 17:37:10
|
Thank you, Alain! Is it possible to generate a table without a "tbody" element? With 1.5.3, removing "tbody" in my sample form still throws a "TypeError: Cannot read property 'localName' of null" in Chrome, but works in Firefox. Best regards, Tim -- Tim A. Thompson Metadata Librarian Yale University Library On Mon, Mar 29, 2021 at 1:25 PM Alain Couthures < ala...@ag...> wrote: > Hello Tim, > > There was a missing initialization in XSLTForms 1.5.2 for table repeats > within a repeat. > > This has been added as XSLTForms 1.5.3 at > https://github.com/AlainCouthures/declarative4all/raw/master/public/direct/xsltforms.zip > > Because of XPath 3 support to be committed in next major release, > XSLTForms 1.5.3 can use both current and future XPath engines. It is just > an intermediate release. Please check all your forms! > > Kind regards, > > --Alain > > Le 28/03/2021 23:03, Tim Thompson <tim...@gm...> a écrit : > > > Thanks again, Josselin, Habs. Yes, I was using the latest version of > XSLTForms, 1.5.2. If I remove the "tbody" element, the form works in > Firefox, but throws an error in Chrome. However, if I revert to version > 1.4, then it works both with and without "tbody," in both Firefox and > Chrome. The issue seems to arise starting with version 1.5beta (655). > > Best regards, > Tim > > > -- > Tim A. Thompson > Metadata Librarian > Yale University Library > > On Sun, Mar 28, 2021 at 3:44 PM Habs <ge...@us...> wrote: > > On Sun, 28 Mar 2021, Tim Thompson wrote: > > > Thanks, Habs! Where you say the "tbody" tags are removed, do you mean in > the XForm itself, or from the rendered HTML? If I remove them from the > XForm, I > > still get an error. > > > > However, if I copy the rendered content of the form, save it, and open > it in the browser, then the table displays correctly. (See attached.) So, > there must > > be something in the XSLTForms JavaScript that is hiding the content? > > > > Hi Tim > > Yes I removed the tbody from the Xform and it worked on my setup with > latest xsltforms series (not sure what revision though sorry). > > I took your stripped (of anything but essential?!) Xform and plugged it > into my goto basic xhtml document format (headers etc) on my test server. > > I simplify xforms to the absolute basics in problem cases I've had - see > if that works and then build back up from there. > > I'll have another play and see if I can spot anything else. > > If you want my test version of your form let me know. > > Regards > > --- Sent using Alpine/Pine, probably the best MUA --- > > _______________________________________________ Xsltforms-support mailing > list Xsl...@li... > https://lists.sourceforge.net/lists/listinfo/xsltforms-support > > |
|
From: Tim T. <tim...@gm...> - 2021-03-28 21:04:05
|
Thanks again, Josselin, Habs. Yes, I was using the latest version of XSLTForms, 1.5.2. If I remove the "tbody" element, the form works in Firefox, but throws an error in Chrome. However, if I revert to version 1.4, then it works both with and without "tbody," in both Firefox and Chrome. The issue seems to arise starting with version 1.5beta (655). Best regards, Tim -- Tim A. Thompson Metadata Librarian Yale University Library On Sun, Mar 28, 2021 at 3:44 PM Habs <ge...@us...> wrote: > On Sun, 28 Mar 2021, Tim Thompson wrote: > > > Thanks, Habs! Where you say the "tbody" tags are removed, do you mean in > the XForm itself, or from the rendered HTML? If I remove them from the > XForm, I > > still get an error. > > > > However, if I copy the rendered content of the form, save it, and open > it in the browser, then the table displays correctly. (See attached.) So, > there must > > be something in the XSLTForms JavaScript that is hiding the content? > > > > Hi Tim > > Yes I removed the tbody from the Xform and it worked on my setup with > latest xsltforms series (not sure what revision though sorry). > > I took your stripped (of anything but essential?!) Xform and plugged it > into my goto basic xhtml document format (headers etc) on my test server. > > I simplify xforms to the absolute basics in problem cases I've had - see > if that works and then build back up from there. > > I'll have another play and see if I can spot anything else. > > If you want my test version of your form let me know. > > Regards > > --- Sent using Alpine/Pine, probably the best MUA --- > |
|
From: Habs <ge...@us...> - 2021-03-28 20:15:17
|
On Sun, 28 Mar 2021, Tim Thompson wrote: > Thanks, Habs! Where you say the "tbody" tags are removed, do you mean in the XForm itself, or from the rendered HTML? If I remove them from the XForm, I > still get an error. > > However, if I copy the rendered content of the form, save it, and open it in the browser, then the table displays correctly. (See attached.) So, there must > be something in the XSLTForms JavaScript that is hiding the content? > Hi Tim Yes I removed the tbody from the Xform and it worked on my setup with latest xsltforms series (not sure what revision though sorry). I took your stripped (of anything but essential?!) Xform and plugged it into my goto basic xhtml document format (headers etc) on my test server. I simplify xforms to the absolute basics in problem cases I've had - see if that works and then build back up from there. I'll have another play and see if I can spot anything else. If you want my test version of your form let me know. Regards --- Sent using Alpine/Pine, probably the best MUA --- |
|
From: Josselin M. <mor...@gm...> - 2021-03-28 19:40:14
|
Hi Tim, Which version of xsltforms are you running ? With 1.3 your form is running without error, with 1.5 I have the same issue than you, but like Habs, if I remove the tbody tag from sample_form.xml everything works perfectly (see the screenshot below) and the modified sample_form.xml attached. If it doesn’t work think about cleaning the browser cache. Note that you should use @nodeset with xf:repeat instead of @ref (even if it doesn’t fix the problem) Best, Josselin. |
|
From: Habs <ge...@us...> - 2021-03-28 19:12:50
|
On Sun, 28 Mar 2021, Tim Thompson wrote: > Hello, Alain, all, > > I have some data that I want to present in a table. The data has one or > more groups, each with a key and related entries. When I try to iterate > over the data in xf:repeat, only the data from the first group is being > output (see screenshot). Sample data and form are below (and attached). > > Thanks in advance, > Tim Hello folks - this may already be known and not much help - it is not a fix - so sorry for the noise if that is the case. This is all I was able to deduce from limited testing If the 'tbody' tags are removed, the form appears to display fine. With 'tbody' tags, looking at the default css applied, it seems the second group's 'tbody' has a display property set to 'none'. Regards Habs --- Sent using Alpine/Pine, probably the best MUA --- Tox Chat Id: 9F10AC64260ADEBAEA017ACB71B7CD2E962596FC4293025C0F79D77FFEB4CE5C7B0BED41D925 https://tox.chat/ |
97 messages has been excluded from this view by a project administrator.
