xsltforms-support Mailing List for XSLTForms (Page 12)
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: Alain C. <ala...@ag...> - 2019-03-30 10:40:54
|
Hi Emmanuel, Actually, HTML5 datalist does really sound like XForms open select, because the associated input allows to enter a new value! I will experiment this soon in XSLTForms. Thank you for pointing at this! --Alain Le 22/03/2019 à 05:52, Chateau Dutier Emmanuel a écrit : > Thanks a lot for your kind answer. > > Do you ask if I’m in a hurry considering the fact I’would have to wait > for HTML6 ? ;) > > I’ve seen the WikipediaSearch for autocompletion, didn’t get all the > details. By the way, what would be the recommend way to deal with > autocompletion in XForms since HTML5 introduced it ? > > Best regards, > Emmanuel > > * > Emmanuel Château-Dutier* > Professeur adjoint > > *Faculté des arts et sciences,* > Département d’histoire de l’art et d’études cinématographiques > > *Université de Montréal* > Pavillon Lionel-Groulx, Bureau C-2067 > 3200, av. Jean-Brillant, Montréal QC > C.P. 6128, succursale Centre-ville, Montréal QC H3C 3J7 > > Tél. +1 514 343-6026 > emm...@um... > <mailto:emm...@um...> | @emchateau > >> Le 18 mars 2019 à 04:29, Alain Couthures >> <ala...@ag... >> <mailto:ala...@ag...>> a écrit : >> >> Hello Emmanuel, >> >> Unfortunately, HTML5 is not providing a native solution for some open >> selection ready to be used by XSLTForms. >> >> It is still possible to add this to XSLTForms with multiple HTML >> elements and CSS classes. Did you already have a look at this >> example: http://www.agencexml.com/xsltforms/wikipediasearch.xml? As >> you can see, I am not a CSS expert... >> >> Are you in a hurry for open selection? >> >> Thanks! >> >> --Alain >> >> Le 15/03/2019 à 19:29, Chateau Dutier Emmanuel a écrit : >>> Hi, >>> >>> We are currently working avec XForms and we really enjoy it ! Thanks >>> a lot. >>> >>> We couldn’t manage to use the open selection. Is it that we >>> didn’t declare it properly or is it not supported ? >>> In 2010, you answered that it wasn’t supported yet >>> https://sourceforge.net/p/xsltforms/mailman/message/24465876/ >>> >>> Best regards, >>> >>> * >>> Emmanuel Château-Dutier* >>> Professeur adjoint >>> >>> *Faculté des arts et sciences,* >>> Département d’histoire de l’art et d’études cinématographiques >>> >>> *Université de Montréal* >>> Pavillon Lionel-Groulx, Bureau C-2067 >>> 3200, av. Jean-Brillant, Montréal QC >>> C.P. 6128, succursale Centre-ville, Montréal QC H3C 3J7 >>> >>> >>> >>> _______________________________________________ >>> Xsltforms-support mailing list >>> Xsl...@li... >>> https://lists.sourceforge.net/lists/listinfo/xsltforms-support >> >> >> _______________________________________________ >> Xsltforms-support mailing list >> Xsl...@li... >> <mailto:Xsl...@li...> >> https://lists.sourceforge.net/lists/listinfo/xsltforms-support > |
|
From: Chateau D. E. <emm...@um...> - 2019-03-22 04:53:06
|
Thanks a lot for your kind answer. Do you ask if I’m in a hurry considering the fact I’would have to wait for HTML6 ? ;) I’ve seen the WikipediaSearch for autocompletion, didn’t get all the details. By the way, what would be the recommend way to deal with autocompletion in XForms since HTML5 introduced it ? Best regards, Emmanuel Emmanuel Château-Dutier Professeur adjoint Faculté des arts et sciences, Département d’histoire de l’art et d’études cinématographiques Université de Montréal Pavillon Lionel-Groulx, Bureau C-2067 3200, av. Jean-Brillant, Montréal QC C.P. 6128, succursale Centre-ville, Montréal QC H3C 3J7 Tél. +1 514 343-6026 emm...@um...<mailto:emm...@um...> | @emchateau Le 18 mars 2019 à 04:29, Alain Couthures <ala...@ag...<mailto:ala...@ag...>> a écrit : Hello Emmanuel, Unfortunately, HTML5 is not providing a native solution for some open selection ready to be used by XSLTForms. It is still possible to add this to XSLTForms with multiple HTML elements and CSS classes. Did you already have a look at this example: http://www.agencexml.com/xsltforms/wikipediasearch.xml? As you can see, I am not a CSS expert... Are you in a hurry for open selection? Thanks! --Alain Le 15/03/2019 à 19:29, Chateau Dutier Emmanuel a écrit : Hi, We are currently working avec XForms and we really enjoy it ! Thanks a lot. We couldn’t manage to use the open selection. Is it that we didn’t declare it properly or is it not supported ? In 2010, you answered that it wasn’t supported yet https://sourceforge.net/p/xsltforms/mailman/message/24465876/ Best regards, Emmanuel Château-Dutier Professeur adjoint Faculté des arts et sciences, Département d’histoire de l’art et d’études cinématographiques Université de Montréal Pavillon Lionel-Groulx, Bureau C-2067 3200, av. Jean-Brillant, Montréal QC C.P. 6128, succursale Centre-ville, Montréal QC H3C 3J7 _______________________________________________ Xsltforms-support mailing list Xsl...@li...<mailto:Xsl...@li...> https://lists.sourceforge.net/lists/listinfo/xsltforms-support _______________________________________________ Xsltforms-support mailing list Xsl...@li...<mailto:Xsl...@li...> https://lists.sourceforge.net/lists/listinfo/xsltforms-support |
|
From: Alain C. <ala...@ag...> - 2019-03-18 08:42:52
|
Hello Emmanuel, Unfortunately, HTML5 is not providing a native solution for some open selection ready to be used by XSLTForms. It is still possible to add this to XSLTForms with multiple HTML elements and CSS classes. Did you already have a look at this example: http://www.agencexml.com/xsltforms/wikipediasearch.xml? As you can see, I am not a CSS expert... Are you in a hurry for open selection? Thanks! --Alain Le 15/03/2019 à 19:29, Chateau Dutier Emmanuel a écrit : > Hi, > > We are currently working avec XForms and we really enjoy it ! Thanks a > lot. > > We couldn’t manage to use the open selection. Is it that we > didn’t declare it properly or is it not supported ? > In 2010, you answered that it wasn’t supported yet > https://sourceforge.net/p/xsltforms/mailman/message/24465876/ > <https://sourceforge.net/p/xsltforms/mailman/message/24465876/> > > Best regards, > > * > Emmanuel Château-Dutier* > Professeur adjoint > > *Faculté des arts et sciences,* > Département d’histoire de l’art et d’études cinématographiques > > *Université de Montréal* > Pavillon Lionel-Groulx, Bureau C-2067 > 3200, av. Jean-Brillant, Montréal QC > C.P. 6128, succursale Centre-ville, Montréal QC H3C 3J7 > > > > _______________________________________________ > Xsltforms-support mailing list > Xsl...@li... > https://lists.sourceforge.net/lists/listinfo/xsltforms-support |
|
From: Chateau D. E. <emm...@um...> - 2019-03-15 18:44:33
|
Hi, We are currently working avec XForms and we really enjoy it ! Thanks a lot. We couldn’t manage to use the open selection. Is it that we didn’t declare it properly or is it not supported ? In 2010, you answered that it wasn’t supported yet https://sourceforge.net/p/xsltforms/mailman/message/24465876/ Best regards, Emmanuel Château-Dutier Professeur adjoint Faculté des arts et sciences, Département d’histoire de l’art et d’études cinématographiques Université de Montréal Pavillon Lionel-Groulx, Bureau C-2067 3200, av. Jean-Brillant, Montréal QC C.P. 6128, succursale Centre-ville, Montréal QC H3C 3J7 |
|
From: Tim T. <tim...@gm...> - 2018-12-19 19:25:06
|
Alain, I was looking forward to incorporating the expand/collapse feature into an XSLTForms project, but it looks as though this has not yet been added to the XSLTForms code repository on GitHub. Is this correct? Best regards, Tim -- Tim A. Thompson Discovery Metadata Librarian Yale University Library On Sun, Sep 2, 2018 at 3:31 PM Alain Couthures < ala...@ag...> wrote: > Owen, > > I have now implemented expand/collapse appearance for groups in XSLTForms > for evaluation. Please have a look at > http://www.agencexml.com/collapse/collapse.xml > > Adding appearance="expand" or appearance="collapse" is just required! Up > and down triangle arrows are inserted with CSS so rendering can be adjusted > rather easily. > > --Alain > > Le 22/08/2018 à 16:07, Owen Ambur a écrit : > > Steven, here's the text of the law I mentioned on the XForms call a few > minutes ago: > https://www.linkedin.com/pulse/open-machine-readable-government-owen-ambur/ > > > > > My StratML colleagues and I are trying to remove as many obstacles as > possible so that U.S. federal agencies are left with few excuses for > failing to comply with the law ... which, incidentally, establishes good > practice for the plans and reports of all organizations, worldwide, whose > activities should be matters of public record. See the use cases > documented thus far at http://stratml.us/carmel/iso/UC4SwStyle.xml > > > > Internationally speaking, the **Open** Government Partnership (OGP) is an > egregious example: https://www.opengovpartnership.org/participants The > national action plans as well as the OGP’s own report are still being > published in PDF: > https://www.opengovpartnership.org/sites/default/files/OGP_Year-Review_20180504.pdf > Assuming good faith on their part, they simply don’t understand the concept > of “openness” in terms of XML/XSD validity. So it is up to us to show them > the benefits of well-structured and semantically well-defined content. > > > > In the meantime, being able to expand and collapse sections of lengthy > plans and reports will help to remove one excuse for failure to publish > plans and reports in open, standard, machine-readable format. Unless and > until public agencies begin to comply with the law, citizens and taxpayers > will have little cause to consider them credible and trustworthy. > > > > Owen Ambur > > Chair, StratML <http://stratml.us/> Working Group > > Co-Chair Emeritus, xml.gov CoP <http://xml.govwebs.net/> > > Webmaster, FIRM <http://firmcouncil.org/> > > Profile <https://www.linkedin.com/in/owenambur> on LinkedIn | Personal Home > Page <http://ambur.net/> > > > > > > -----Original Message----- > From: Steven Pemberton <ste...@cw...> <ste...@cw...> > Sent: Wednesday, August 22, 2018 7:15 AM > To: XForms <pub...@w3...> <pub...@w3...> > Subject: Collapsing sections > > > > Someone asked me about doing collapsing sections in XForms, so I wrote an > > article: > > > > https://homepages.cwi.nl/~steven/xforms/techniques/collapsing.html > > > > Comments gratefully received. > > > > Steven > > > > > |
|
From: Tim T. <tim...@gm...> - 2018-10-08 21:32:04
|
Alain, Thanks for the latest update to XSLTForms! It looks as though Markdown documents are now supported as XForms instance data, is that correct? I look forward to trying this feature. I just cloned the latest build and tested a form. I noticed a new warning in the Firebox debugging console: "Empty string passed to getElementById()," which points to this line of code added in the latest commit: https://github.com/AlainCouthures/xsltforms/blob/6e8fa26939252fd7b1bff777bbee28fa6b0d1476/build/xsltforms.js#L3769 Best regards, Tim -- Tim A. Thompson Discovery Metadata Librarian Yale University Library |
|
From: Alain C. <ala...@ag...> - 2018-10-05 16:44:49
|
Tim, In XForms 1.1, at https://www.w3.org/TR/xforms11/#ui-selection-commonelems-itemset, "The node-set that holds the available choices is specified via the Node Set Binding.". In XForms 2.0, at https://www.w3.org/community/xformsusers/wiki/XForms_2.0#The_item_Element, "The sequence that holds the available choices is specified via the Sequence Binding.". So, xf:itemset/xf:label/xf:output/@value is not valid XForms from my point of view. With XPath 2.0 at least, xf:itemset/xf:label/@ref="title/substring(., 1, 50)" would generate the correct sequence for your example. Sorry but Fleur engine is not yet supported in XSLTForms... --Alain Le 04/10/2018 à 00:25, Tim Thompson a écrit : > Alain, > > I would like to use xf:output/@value with an XPath expression to > generate the contents of an xf:itemset label inside an xf:select1. > This should be valid in XForms, unless I am mistaken. However, in > XSLTForms 1.0, I get an error when I try to do this: > > TypeError: Cannot read property 'xfElement' of null > at XsltForms_output.XsltForms_element.init (xsltforms.js:9319) > at new XsltForms_output (xsltforms.js:10565) > at xsltforms_initImpl (itemset-label-test.xhtml:42) > at xsltforms_init (itemset-label-test.xhtml:76) > > See attached form and data file (also pasted below) to reproduce the > issue. Thanks in advance. > > Form: > > <?xml-stylesheet href="xsltforms/build/xsltforms.xsl" type="text/xsl"?> > <?xsltforms-options debug="yes"?> > <?css-conversion no?> > <html xmlns="http://www.w3.org/1999/xhtml" > xmlns:xf="http://www.w3.org/2002/xforms"> > <head> > <title>Itemset test</title> > <meta http-equiv="Content-Type" content="text/html; > charset=utf-8" /> > > <xf:model> > <xf:instance> > <data xmlns=""> > <current/> > </data> > </xf:instance> > </xf:model> > > <xf:model id="entries"> > <xf:instance src="entries.xml"/> > </xf:model> > > </head> > <body> > <div class="container-fluid wrapper"> > <xf:select1 ref="/data/current" appearance="minimal" > incremental="true"> > <xf:label>Select a title to compare: </xf:label> > <xf:itemset model="entries" ref="/data/entry"> > <!-- Works with xf:label/@ref --> > <!-- <xf:label ref="title"/> --> > <!-- But not with nested xf:label/xf:output/@value --> > <xf:label> > <xf:output value="substring(title, 1, 50)"/> > </xf:label> > <xf:value ref="identifier"/> > </xf:itemset> > </xf:select1> > <xf:output ref="/data/current"> > <xf:label>Current title: </xf:label> > </xf:output> > </div> > <br /> > </body> > </html> > > Data: > > <?xml version="1.0" encoding="UTF-8"?> > <data> > <entry> > <identifier>2017387103</identifier> > <title>Una famiglia tra Siena e l'Europa : i Montucci, > 1762-1877 /famiglia tra Siena e l'Europa : i Montucc...</title> > </entry> > <entry> > <identifier>2017452585</identifier> > <title>Tipologie e modalità della mediazione nella Grecia > antica : le fonti letterarie /Tipologie e modalit...</title> > </entry> > <entry> > <identifier>2017452511</identifier> > <title>Identità sotto chiave : lingua e stile nel teatro di > Saverio La Ruina /Identità sotto chiave : lingu...</title> > </entry> > </data> > > > Best regards, > Tim > > -- > Tim A. Thompson > Discovery Metadata Librarian > Yale University Library > > > > > > _______________________________________________ > Xsltforms-support mailing list > Xsl...@li... > https://lists.sourceforge.net/lists/listinfo/xsltforms-support |
|
From: Ihe O. <ihe...@gm...> - 2018-10-04 03:05:51
|
I use it on Chrome. On Wed, Oct 3, 2018 at 10:42 PM Tim Thompson <tim...@gm...> wrote: > Apologies, but one additional question: is the XSLTForms Debugger still > available? When I try to open it with the F1 shortcut, as before (on Ubuntu > 18.04 Firefox and Chrome), nothing happens. > > Best, > Tim > > > -- > Tim A. Thompson > Discovery Metadata Librarian > Yale University Library > > _______________________________________________ > Xsltforms-support mailing list > Xsl...@li... > https://lists.sourceforge.net/lists/listinfo/xsltforms-support > |
|
From: Tim T. <tim...@gm...> - 2018-10-04 02:42:42
|
Apologies, but one additional question: is the XSLTForms Debugger still available? When I try to open it with the F1 shortcut, as before (on Ubuntu 18.04 Firefox and Chrome), nothing happens. Best, Tim -- Tim A. Thompson Discovery Metadata Librarian Yale University Library |
|
From: Tim T. <tim...@gm...> - 2018-10-03 22:28:59
|
Sorry--"entries.xml" in the test form should be changed to "data.xml" to match the sample file (this does not affect the error). -- Tim A. Thompson Discovery Metadata Librarian Yale University Library On Wed, Oct 3, 2018 at 6:25 PM Tim Thompson <tim...@gm...> wrote: > Alain, > > I would like to use xf:output/@value with an XPath expression to generate > the contents of an xf:itemset label inside an xf:select1. This should be > valid in XForms, unless I am mistaken. However, in XSLTForms 1.0, I get an > error when I try to do this: > > TypeError: Cannot read property 'xfElement' of null > at XsltForms_output.XsltForms_element.init (xsltforms.js:9319) > at new XsltForms_output (xsltforms.js:10565) > at xsltforms_initImpl (itemset-label-test.xhtml:42) > at xsltforms_init (itemset-label-test.xhtml:76) > > See attached form and data file (also pasted below) to reproduce the > issue. Thanks in advance. > > Form: > > <?xml-stylesheet href="xsltforms/build/xsltforms.xsl" type="text/xsl"?> > <?xsltforms-options debug="yes"?> > <?css-conversion no?> > <html xmlns="http://www.w3.org/1999/xhtml" xmlns:xf=" > http://www.w3.org/2002/xforms"> > <head> > <title>Itemset test</title> > <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> > > <xf:model> > <xf:instance> > <data xmlns=""> > <current/> > </data> > </xf:instance> > </xf:model> > > <xf:model id="entries"> > <xf:instance src="entries.xml"/> > </xf:model> > > </head> > <body> > <div class="container-fluid wrapper"> > <xf:select1 ref="/data/current" appearance="minimal" > incremental="true"> > <xf:label>Select a title to compare: </xf:label> > <xf:itemset model="entries" ref="/data/entry"> > <!-- Works with xf:label/@ref --> > <!-- <xf:label ref="title"/> --> > <!-- But not with nested xf:label/xf:output/@value --> > <xf:label> > <xf:output value="substring(title, 1, 50)"/> > </xf:label> > <xf:value ref="identifier"/> > </xf:itemset> > </xf:select1> > <xf:output ref="/data/current"> > <xf:label>Current title: </xf:label> > </xf:output> > </div> > <br /> > </body> > </html> > > Data: > > <?xml version="1.0" encoding="UTF-8"?> > <data> > <entry> > <identifier>2017387103</identifier> > <title>Una famiglia tra Siena e l'Europa : i Montucci, 1762-1877 > /famiglia tra Siena e l'Europa : i Montucc...</title> > </entry> > <entry> > <identifier>2017452585</identifier> > <title>Tipologie e modalità della mediazione nella Grecia antica : > le fonti letterarie /Tipologie e modalit...</title> > </entry> > <entry> > <identifier>2017452511</identifier> > <title>Identità sotto chiave : lingua e stile nel teatro di > Saverio La Ruina /Identità sotto chiave : lingu...</title> > </entry> > </data> > > > Best regards, > Tim > > -- > Tim A. Thompson > Discovery Metadata Librarian > Yale University Library > > |
|
From: Tim T. <tim...@gm...> - 2018-10-03 22:26:28
|
Alain,
I would like to use xf:output/@value with an XPath expression to generate
the contents of an xf:itemset label inside an xf:select1. This should be
valid in XForms, unless I am mistaken. However, in XSLTForms 1.0, I get an
error when I try to do this:
TypeError: Cannot read property 'xfElement' of null
at XsltForms_output.XsltForms_element.init (xsltforms.js:9319)
at new XsltForms_output (xsltforms.js:10565)
at xsltforms_initImpl (itemset-label-test.xhtml:42)
at xsltforms_init (itemset-label-test.xhtml:76)
See attached form and data file (also pasted below) to reproduce the issue.
Thanks in advance.
Form:
<?xml-stylesheet href="xsltforms/build/xsltforms.xsl" type="text/xsl"?>
<?xsltforms-options debug="yes"?>
<?css-conversion no?>
<html xmlns="http://www.w3.org/1999/xhtml" xmlns:xf="
http://www.w3.org/2002/xforms">
<head>
<title>Itemset test</title>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<xf:model>
<xf:instance>
<data xmlns="">
<current/>
</data>
</xf:instance>
</xf:model>
<xf:model id="entries">
<xf:instance src="entries.xml"/>
</xf:model>
</head>
<body>
<div class="container-fluid wrapper">
<xf:select1 ref="/data/current" appearance="minimal"
incremental="true">
<xf:label>Select a title to compare: </xf:label>
<xf:itemset model="entries" ref="/data/entry">
<!-- Works with xf:label/@ref -->
<!-- <xf:label ref="title"/> -->
<!-- But not with nested xf:label/xf:output/@value -->
<xf:label>
<xf:output value="substring(title, 1, 50)"/>
</xf:label>
<xf:value ref="identifier"/>
</xf:itemset>
</xf:select1>
<xf:output ref="/data/current">
<xf:label>Current title: </xf:label>
</xf:output>
</div>
<br />
</body>
</html>
Data:
<?xml version="1.0" encoding="UTF-8"?>
<data>
<entry>
<identifier>2017387103</identifier>
<title>Una famiglia tra Siena e l'Europa : i Montucci, 1762-1877
/famiglia tra Siena e l'Europa : i Montucc...</title>
</entry>
<entry>
<identifier>2017452585</identifier>
<title>Tipologie e modalità della mediazione nella Grecia antica :
le fonti letterarie /Tipologie e modalit...</title>
</entry>
<entry>
<identifier>2017452511</identifier>
<title>Identità sotto chiave : lingua e stile nel teatro di Saverio
La Ruina /Identità sotto chiave : lingu...</title>
</entry>
</data>
Best regards,
Tim
--
Tim A. Thompson
Discovery Metadata Librarian
Yale University Library
|
|
From: Tim T. <tim...@gm...> - 2017-12-18 21:54:27
|
Just to add, one of the great features of XSLTForms is that it is possible to call arbitrary JavaScript functions from XForms expressions. Here is an updated version of your form, with a UUID function that I found quickly on GitHub ( https://gist.githubusercontent.com/mlhaufe/2055524/raw/439bbf7914655c681d5d0ef62ae87a9ef6ca7560/uuid.js ): <?xml-stylesheet href="xsltforms/build/xsltforms.xsl" type="text/xsl"?> <!--?xsltforms-options debug="yes"?--> <html xmlns="http://www.w3.org/1999/xhtml" xmlns:jr=" http://openrosa.org/javarosa" xmlns:dummy="dummy"> <head> <title>Hello World in XForms</title> <model xmlns="http://www.w3.org/2002/xforms"> <instance> <test_form1 xmlns=""> <today/> <gender/> <age/> <meta> <instanceID/> </meta> </test_form1> </instance> <bind jr:preload="date" jr:preloadParams="today" nodeset="/test_form1/today" type="date"/> <bind nodeset="/test_form1/gender" type="select1"/> <bind nodeset="/test_form1/age" type="int"/> <bind calculate="concat('uuid:', uuid())" nodeset="/test_form1/meta/instanceID" readonly="true()" type="string"/> </model> </head> <body xmlns:xf="http://www.w3.org/2002/xforms"> <xf:select1 ref="/test_form1/gender"> <xf:label>Respondent's gender</xf:label> <xf:item> <xf:label>Male</xf:label> <xf:value>male</xf:value> </xf:item> <xf:item> <xf:label>Female</xf:label> <xf:value>female</xf:value> </xf:item> </xf:select1> <xf:input ref="/test_form1/age"> <xf:label>Respondent's age</xf:label> </xf:input> <script type="text/javascript"> <![CDATA[ // https://gist.githubusercontent.com/mlhaufe/2055524/raw/439bbf7914655c681d5d0ef62ae87a9ef6ca7560/uuid.js // Uses Version 4 // < https://en.wikipedia.org/wiki/Universally_unique_identifier#Version_4_.28random.29 > // RFC 4122 var uuid = (function(){ var re = /[xy]/g; function fn(c){ var r = Math.random()*16|0, v = (c == 'x') ? r : (r&0x3|0x8); return v.toString(16); } return function(){ return 'xxxxxxxx-xxxx-4xxx-yxxx-xxxxxxxxxxxx'.replace(re,fn); } })(); ]]> </script> </body> </html> -- Tim A. Thompson Discovery Metadata Librarian Yale University Library On Mon, Dec 18, 2017 at 4:43 PM, pedro winstley via Xsltforms-support < xsl...@li...> wrote: > HI Alain > > Thank you for your helpful reply. I have also been in touch with the > XSLForms development team about the "select1" issue as a nodeset type, and > the appropriate action is to correct that application. I will see what can > be done with them. I will cover the default namespace for instances there > too. > > The uuid() function would be helpful. This is included as an > application-specific function in Orbeon, under their xxf: namespace afaik, > and it would be a common convenience function between XSLTForms, Orbeon and > the ODK XSLForms. > > I think that the XSLForms ( https://github.com/XLSForm/pyxform ) > approach could be very helpful to introduce teams gently into XForms. The > graphical interface in PurcForms (https://github.com/dkayiwa/purcforms) > is another helpful tool that can serve a similar purpose. > > Many thanks for your amazing work > > Peter > > > On 18 December 2017 at 21:31, Alain Couthures < > ala...@ag...> wrote: > >> Hi Peter, >> >> Adding support for uuid() in XSLTForms was not difficult, it will be >> committed as soon as possible. >> >> Yet, "select1" is not a valid type: as a workaround, it can be defined as >> a synonym for "string"... >> >> Then, there is still a namespace issue in the generated form: xmlns="" >> has to be added to the root element of the instance. >> >> Finally, "form-data-post" is not yet implemented in XSLTForms but it >> would be possible... >> >> What do you think? >> >> Alain >> >> >> Le 18/12/2017 à 16:17, pedro winstley via Xsltforms-support a écrit : >> >> Dear colleagues >> >> I realise that we can use the XLSForms ( http://xlsform.org/ ) editor to >> create XForms that will work with XSLTForms (there is going to be acronym >> hell here), but the XSLForms automatically creates a bind for a uuid >> element and uses a function "uuid()". How can this best be implemented in >> XSLTForms so that I can bring in an XLSForm XForm without any editing? >> >> I show an illustration of XLSForms output below >> >> Many thanks >> >> Peter >> >> <?xml version="1.0"?> >> <h:html xmlns="http://www.w3.org/2002/xforms" xmlns:ev=" >> http://www.w3.org/2001/xml-events" xmlns:h="http://www.w3.org/1999/xhtml" >> xmlns:jr="http://openrosa.org/javarosa" xmlns:orx="http://openrosa.org >> /xforms" xmlns:xsd="http://www.w3.org/2001/XMLSchema"> >> <h:head> >> <h:title>test_form1</h:title> >> <model> >> <submission action="http://xformstest.org/cgi-bin/echoinstance.sh" >> method="form-data-post"/> >> <instance> >> <test_form1 id="test_form1"> >> <today/> >> <gender/> >> <age/> >> <meta> >> <instanceID/> >> </meta> >> </test_form1> >> </instance> >> <bind jr:preload="date" jr:preloadParams="today" >> nodeset="/test_form1/today" type="date"/> >> <bind nodeset="/test_form1/gender" type="select1"/> >> <bind nodeset="/test_form1/age" type="int"/> >> <bind calculate="concat('uuid:', uuid())" >> nodeset="/test_form1/meta/instanceID" readonly="true()" type="string"/> >> </model> >> </h:head> >> <h:body> >> <select1 ref="/test_form1/gender"> >> <label>Respondent's gender</label> >> <item> >> <label>Male</label> >> <value>male</value> >> </item> >> <item> >> <label>Female</label> >> <value>female</value> >> </item> >> </select1> >> <input ref="/test_form1/age"> >> <label>Respondent's age</label> >> </input> >> </h:body> >> </h:html> >> >> >> >> ------------------------------------------------------------------------------ >> Check out the vibrant tech community on one of the world's most >> engaging tech sites, Slashdot.org! http://sdm.link/slashdot >> >> >> >> _______________________________________________ >> Xsltforms-support mailing lis...@li...https://lists.sourceforge.net/lists/listinfo/xsltforms-support >> >> >> > > ------------------------------------------------------------ > ------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > Xsltforms-support mailing list > Xsl...@li... > https://lists.sourceforge.net/lists/listinfo/xsltforms-support > > |
|
From: Alain C. <ala...@ag...> - 2017-12-18 21:44:55
|
Hi Peter, Adding support for uuid() in XSLTForms was not difficult, it will be committed as soon as possible. Yet, "select1" is not a valid type: as a workaround, it can be defined as a synonym for "string"... Then, there is still a namespace issue in the generated form: xmlns="" has to be added to the root element of the instance. Finally, "form-data-post" is not yet implemented in XSLTForms but it would be possible... What do you think? Alain Le 18/12/2017 à 16:17, pedro winstley via Xsltforms-support a écrit : > Dear colleagues > > I realise that we can use the XLSForms ( http://xlsform.org/ ) editor > to create XForms that will work with XSLTForms (there is going to be > acronym hell here), but the XSLForms automatically creates a bind for > a uuid element and uses a function "uuid()". How can this best be > implemented in XSLTForms so that I can bring in an XLSForm XForm > without any editing? > > I show an illustration of XLSForms output below > > Many thanks > > Peter > > <?xml version="1.0"?> > <h:html xmlns="http://www.w3.org/2002/xforms" > xmlns:ev="http://www.w3.org/2001/xml-events" > xmlns:h="http://www.w3.org/1999/xhtml" > xmlns:jr="http://openrosa.org/javarosa" > xmlns:orx="http://openrosa.org/xforms" > xmlns:xsd="http://www.w3.org/2001/XMLSchema"> > <h:head> > <h:title>test_form1</h:title> > <model> > <submission > action="http://xformstest.org/cgi-bin/echoinstance.sh" > method="form-data-post"/> > <instance> > <test_form1 id="test_form1"> > <today/> > <gender/> > <age/> > <meta> > <instanceID/> > </meta> > </test_form1> > </instance> > <bind jr:preload="date" jr:preloadParams="today" > nodeset="/test_form1/today" type="date"/> > <bind nodeset="/test_form1/gender" type="select1"/> > <bind nodeset="/test_form1/age" type="int"/> > <bind calculate="concat('uuid:', uuid())" > nodeset="/test_form1/meta/instanceID" readonly="true()" type="string"/> > </model> > </h:head> > <h:body> > <select1 ref="/test_form1/gender"> > <label>Respondent's gender</label> > <item> > <label>Male</label> > <value>male</value> > </item> > <item> > <label>Female</label> > <value>female</value> > </item> > </select1> > <input ref="/test_form1/age"> > <label>Respondent's age</label> > </input> > </h:body> > </h:html> > > > > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > > > _______________________________________________ > Xsltforms-support mailing list > Xsl...@li... > https://lists.sourceforge.net/lists/listinfo/xsltforms-support |
|
From: pedro w. <ped...@go...> - 2017-12-18 21:43:35
|
HI Alain Thank you for your helpful reply. I have also been in touch with the XSLForms development team about the "select1" issue as a nodeset type, and the appropriate action is to correct that application. I will see what can be done with them. I will cover the default namespace for instances there too. The uuid() function would be helpful. This is included as an application-specific function in Orbeon, under their xxf: namespace afaik, and it would be a common convenience function between XSLTForms, Orbeon and the ODK XSLForms. I think that the XSLForms ( https://github.com/XLSForm/pyxform ) approach could be very helpful to introduce teams gently into XForms. The graphical interface in PurcForms (https://github.com/dkayiwa/purcforms) is another helpful tool that can serve a similar purpose. Many thanks for your amazing work Peter On 18 December 2017 at 21:31, Alain Couthures <ala...@ag... > wrote: > Hi Peter, > > Adding support for uuid() in XSLTForms was not difficult, it will be > committed as soon as possible. > > Yet, "select1" is not a valid type: as a workaround, it can be defined as > a synonym for "string"... > > Then, there is still a namespace issue in the generated form: xmlns="" has > to be added to the root element of the instance. > > Finally, "form-data-post" is not yet implemented in XSLTForms but it would > be possible... > > What do you think? > > Alain > > > Le 18/12/2017 à 16:17, pedro winstley via Xsltforms-support a écrit : > > Dear colleagues > > I realise that we can use the XLSForms ( http://xlsform.org/ ) editor to > create XForms that will work with XSLTForms (there is going to be acronym > hell here), but the XSLForms automatically creates a bind for a uuid > element and uses a function "uuid()". How can this best be implemented in > XSLTForms so that I can bring in an XLSForm XForm without any editing? > > I show an illustration of XLSForms output below > > Many thanks > > Peter > > <?xml version="1.0"?> > <h:html xmlns="http://www.w3.org/2002/xforms" xmlns:ev="http://www.w3.org/ > 2001/xml-events" xmlns:h="http://www.w3.org/1999/xhtml" xmlns:jr=" > http://openrosa.org/javarosa" xmlns:orx="http://openrosa.org/xforms" > xmlns:xsd="http://www.w3.org/2001/XMLSchema"> > <h:head> > <h:title>test_form1</h:title> > <model> > <submission action="http://xformstest.org/cgi-bin/echoinstance.sh" > method="form-data-post"/> > <instance> > <test_form1 id="test_form1"> > <today/> > <gender/> > <age/> > <meta> > <instanceID/> > </meta> > </test_form1> > </instance> > <bind jr:preload="date" jr:preloadParams="today" > nodeset="/test_form1/today" type="date"/> > <bind nodeset="/test_form1/gender" type="select1"/> > <bind nodeset="/test_form1/age" type="int"/> > <bind calculate="concat('uuid:', uuid())" nodeset="/test_form1/meta/instanceID" > readonly="true()" type="string"/> > </model> > </h:head> > <h:body> > <select1 ref="/test_form1/gender"> > <label>Respondent's gender</label> > <item> > <label>Male</label> > <value>male</value> > </item> > <item> > <label>Female</label> > <value>female</value> > </item> > </select1> > <input ref="/test_form1/age"> > <label>Respondent's age</label> > </input> > </h:body> > </h:html> > > > > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > > > > _______________________________________________ > Xsltforms-support mailing lis...@li...https://lists.sourceforge.net/lists/listinfo/xsltforms-support > > > |
|
From: pedro w. <ped...@go...> - 2017-12-18 15:17:50
|
Dear colleagues I realise that we can use the XLSForms ( http://xlsform.org/ ) editor to create XForms that will work with XSLTForms (there is going to be acronym hell here), but the XSLForms automatically creates a bind for a uuid element and uses a function "uuid()". How can this best be implemented in XSLTForms so that I can bring in an XLSForm XForm without any editing? I show an illustration of XLSForms output below Many thanks Peter <?xml version="1.0"?> <h:html xmlns="http://www.w3.org/2002/xforms" xmlns:ev=" http://www.w3.org/2001/xml-events" xmlns:h="http://www.w3.org/1999/xhtml" xmlns:jr="http://openrosa.org/javarosa" xmlns:orx=" http://openrosa.org/xforms" xmlns:xsd="http://www.w3.org/2001/XMLSchema"> <h:head> <h:title>test_form1</h:title> <model> <submission action="http://xformstest.org/cgi-bin/echoinstance.sh" method="form-data-post"/> <instance> <test_form1 id="test_form1"> <today/> <gender/> <age/> <meta> <instanceID/> </meta> </test_form1> </instance> <bind jr:preload="date" jr:preloadParams="today" nodeset="/test_form1/today" type="date"/> <bind nodeset="/test_form1/gender" type="select1"/> <bind nodeset="/test_form1/age" type="int"/> <bind calculate="concat('uuid:', uuid())" nodeset="/test_form1/meta/instanceID" readonly="true()" type="string"/> </model> </h:head> <h:body> <select1 ref="/test_form1/gender"> <label>Respondent's gender</label> <item> <label>Male</label> <value>male</value> </item> <item> <label>Female</label> <value>female</value> </item> </select1> <input ref="/test_form1/age"> <label>Respondent's age</label> </input> </h:body> </h:html> |
|
From: Habs <ge...@us...> - 2017-11-24 20:33:52
|
Hello Alain Thank you for the reply and insight. On Fri, 24 Nov 2017 19:17:13 +0100 Alain Couthures <ala...@ag...> wrote: > ... > As a consequence, it cannot be guaranteed by XSLTForms 1.0 that > namespace declarations will be precisely at the same locations in the > submitted XML data. > Ah ! That explains it a bit better for me. > Why is it a problem for you? > Obviously there is nothing structurally or semantically wrong etc with any submitted results. The resultant xml can be visually untidy and as I said, one would like to think the document arriving is the one that is created and in that, one can control namespaces exposure, rather than have things added by software when not required in the xml document. It is just a personal observation. Having said that, I will have a think some more about it and in relation to your comments. Thank you again for your insight. Much appreciated. Habs |
|
From: Alain C. <ala...@ag...> - 2017-11-24 18:22:35
|
Hello Habs, Inline instances are first serialized by the XSLT engine then parsed in the browser then, finally, serialized by the browser. There is a known issue in Firefox: namespace axis has never been implemented in its XSLT engine (Transformiix). By default, XSLTForms 1.0 uses the native XML engine for each browser. As a consequence, it cannot be guaranteed by XSLTForms 1.0 that namespace declarations will be precisely at the same locations in the submitted XML data. Why is it a problem for you? --Alain Le 17/11/2017 à 15:49, Habs a écrit : > Hello xsltforms-support > > Question: how to control namespace exposure when submitting an > instance, so that the instance arriving at the sumbission endpoint > reflects exactly the original instance as in the xform ? > > > Considering this snippet from a xform: > > > <html xmlns="http://www.w3.org/1999/xhtml" > xmlns:my="http://thisdefaultnamespace" > xmlns:another="http://anothernamespace" > xmlns:xf="http://www.w3.org/2002/xforms" > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" > xmlns:ev="http://www.w3.org/2001/xml-events" > xmlns:xs="http://www.w3.org/2001/XMLSchema" > my:dummy="whyisthisneeded"> > . > . > . > <xf:instance id="thisinstance"> > <root xmlns="http://thisdefaultnamespace" > xmlns:another="http://anothernamespace" > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" > xsi:type="aRootType"> > <child1/> > <child2/> > <section xsi:type="aSectionType"> > <another:child1 /> > <another:child2 /> > </section> > </root> > </xf:instance> > <xf:submission id="submitinstance" method="post" replace="all" > resource="echoitback.script"/> > . > . > . > </html> > > > It would seem that the instance above is a well-formed and valid > document (correct in its namespaces and their exposure etc) when > checked in an accurate xml editor program (xmlspy & editix). > > It seems that the instance document arriving at the specified > destination [submission] resource, has 'xmlns' attributes included > throughout the document in relation to xmlns:another and xmlns:xsi > namespace - e.g. : > > > <root xmlns="http://thisdefaultnamespace" > xmlns:another="http://anothernamespace" > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" > xsi:type="aRootType"> > <child1/> > <child2/> > <section xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="aSectionType"> > <another:child1 xmlns:another="http://anothernamespace" /> > <another:child2 xmlns:another="http://anothernamespace"/> > </section> > </root> > > > These added namespace attributes are not required, therefore how is > namespace exposure controlled to prevent this and indeed, is this > too complicated for current xforms I wonder. > > Thank you for any comments, observations, corrections and so forth ? > > Regards > Habs > > > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > Xsltforms-support mailing list > Xsl...@li... > https://lists.sourceforge.net/lists/listinfo/xsltforms-support > |
|
From: Habs <ge...@us...> - 2017-11-17 14:49:54
|
Hello xsltforms-support Question: how to control namespace exposure when submitting an instance, so that the instance arriving at the sumbission endpoint reflects exactly the original instance as in the xform ? Considering this snippet from a xform: <html xmlns="http://www.w3.org/1999/xhtml" xmlns:my="http://thisdefaultnamespace" xmlns:another="http://anothernamespace" xmlns:xf="http://www.w3.org/2002/xforms" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:ev="http://www.w3.org/2001/xml-events" xmlns:xs="http://www.w3.org/2001/XMLSchema" my:dummy="whyisthisneeded"> . . . <xf:instance id="thisinstance"> <root xmlns="http://thisdefaultnamespace" xmlns:another="http://anothernamespace" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="aRootType"> <child1/> <child2/> <section xsi:type="aSectionType"> <another:child1 /> <another:child2 /> </section> </root> </xf:instance> <xf:submission id="submitinstance" method="post" replace="all" resource="echoitback.script"/> . . . </html> It would seem that the instance above is a well-formed and valid document (correct in its namespaces and their exposure etc) when checked in an accurate xml editor program (xmlspy & editix). It seems that the instance document arriving at the specified destination [submission] resource, has 'xmlns' attributes included throughout the document in relation to xmlns:another and xmlns:xsi namespace - e.g. : <root xmlns="http://thisdefaultnamespace" xmlns:another="http://anothernamespace" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="aRootType"> <child1/> <child2/> <section xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:type="aSectionType"> <another:child1 xmlns:another="http://anothernamespace" /> <another:child2 xmlns:another="http://anothernamespace"/> </section> </root> These added namespace attributes are not required, therefore how is namespace exposure controlled to prevent this and indeed, is this too complicated for current xforms I wonder. Thank you for any comments, observations, corrections and so forth ? Regards Habs |
|
From: Mats E. <mat...@li...> - 2017-11-05 23:34:26
|
Hi Alain,
Want to share an observation and possible improvement to the xsltforms code.
In XsltForms v1.0, when a binding expression on a bound element X in the form references no node(s), descendant bound elements seem to be evaluated with the same in-scope evaluation context as that of X, whereas according to the XForms spec, binding expressions of descendant bound elements should not be evaluated at all in such situations.
While it may seem that this is not an important issue, since element X and descendant elements will be marked as disabled anyway, it may happen (and it did so in my form) that XsltForms throws errors/exceptions during build/refresh processing of nested bound elements when their binding expressions are evaluated in an unexpected in-scope evaluation context.
I found that it may be possible to fix this issue with the following modifications in the definition of the function XsltForms_globals.build():
1) replace the line:
var newctx = element.node || ctx;
with:
var newctx = (hasXFElement && xf.hasBinding && !element.node ? null : element.node || ctx);
... in order to pass an in-scope evaluation context with no context item instead of the current context item to the processing of descendant controls if the current element's binding expressions references no node.
2) insert the lines:
if (hasXFElement && xf.hasBinding && !ctx) {
return {ctx: ctx, hasXFElement: hasXFElement};
}
...towards the top of the function body in order to skip build processing of bound elements whose in-scope evaluation context contains no context item.
/ Mats
|
|
From: Habs <ge...@us...> - 2017-11-01 22:23:45
|
Hi Alain, everyone On Wed, 1 Nov 2017 21:18:29 +0100 Alain Couthures <ala...@ag...> wrote: > > What do you think? > In the between time from me posting about this, I've spent a lot of time digging around using 'web-inspector' tools and I think I've got a grip on it now. It is making more sense. There are one or two things still giving me a headache, but even then I think I've sorted out my issues that prompted me to ask. Thank you for the links sent and I came across some other bits and bats to add to that. XSLTForms is a really useful tool...long may it exist and be supported. Thank you for it. Habs |
|
From: Alain C. <ala...@ag...> - 2017-11-01 21:00:44
|
Hello Habs, No voluntary change in CSS support have been made for quiet a long time... The XSL transformation should still be trying to parse STYLE and LINK elements. It implies that external files have to be in well-formed XML format as explained at https://en.wikibooks.org/wiki/XRX/XSLTForms_and_eXist#Modifying_your_CSS_to_work_with_XSLTForms What do you think? --Alain Le 31/10/2017 à 15:20, Habs a écrit : > > Hello Alain - please will you, or any one else with good knowledge, > comment on how CSS is applied within XSLTForms application. > > - is *all* the CSS applied from external .css files ? > > - is any CSS applied from within any javascript used and/or from > within the xsl transformation (.xsl) file ? > > - can the CSS applied by XSLTForms be full overridden for bespoke > formatting? > > - is there a priority/order to the application of CSS ? > > The reason I ask is because I have an older verions of XSLTForms and > my custom CSS file applies as expected with the form. Without any > change to the form and CSS, but using the latest release of XSLTForms, > there are some oddities and changes to the form; the CSS is not being > applied as it was before. > > Thank you for your answers to my questions above, your comments and > insight on how and where XSLTForms applies CSS. > > Regards > Habs > > --- Sent using Alpine/Pine MUA --- > > ------------------------------------------------------------------------------ > > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > Xsltforms-support mailing list > Xsl...@li... > https://lists.sourceforge.net/lists/listinfo/xsltforms-support > |
|
From: Habs <ge...@us...> - 2017-10-31 14:44:11
|
Hello Alain - please will you, or any one else with good knowledge, comment on how CSS is applied within XSLTForms application. - is *all* the CSS applied from external .css files ? - is any CSS applied from within any javascript used and/or from within the xsl transformation (.xsl) file ? - can the CSS applied by XSLTForms be full overridden for bespoke formatting? - is there a priority/order to the application of CSS ? The reason I ask is because I have an older verions of XSLTForms and my custom CSS file applies as expected with the form. Without any change to the form and CSS, but using the latest release of XSLTForms, there are some oddities and changes to the form; the CSS is not being applied as it was before. Thank you for your answers to my questions above, your comments and insight on how and where XSLTForms applies CSS. Regards Habs --- Sent using Alpine/Pine MUA --- |
|
From: Alain C. <ala...@ag...> - 2017-10-27 16:45:19
|
Interesting! It appears that the XForms control was deleted before yet another event was sent to it. Adding a test to avoid the exception sounds enough in this situation but it is currently not possible for me to check this... It will be committed in the next revision. Thanks! --Alain Le 27/10/2017 à 17:59, Tim Thompson a écrit : > Alain, > > I believe I was able to reproduce this error in Chrome 61. See the > attached screenshot, which references line 3614 in xsltforms.js. > > Best, > Tim > > -- > Tim A. Thompson > Discovery Metadata Librarian > Yale University Library > > > On Fri, Oct 27, 2017 at 10:32 AM, Alain Couthures > <ala...@ag... > <mailto:ala...@ag...>> wrote: > > Hi Mats, > > I have not been able to reproduce this issue: I have tested > with Chrome 61, Chrome 62, Chrome Beta 62 and Chrome Canary 64 > but no exception appeared... > > Could you please send me the line number you saw so I could > check its validity? > > Thanks! > > --Alain > > > Le 23/10/2017 à 14:36, Mats Eklund a écrit : >> Hi Alan, >> >> By chance stumbled upon a potential bug in the xsltforms >> library recently. The attached simple test case shows how an >> exception is thrown when user clicks Delete trigger on the >> last item in a repeat list. Only in Chrome it seems. >> >> It is possible to avoid the exception by putting an extra >> null check in the if() statement on the line where the >> exception is thrown, however, it looks like the issue may >> reveal a deeper issue, whose effects could sometimes be more >> subtle. >> >> / Mats >> >> >> >> >> ------------------------------------------------------------------------------ >> Check out the vibrant tech community on one of the world's most >> engaging tech sites, Slashdot.org!http://sdm.link/slashdot >> >> >> _______________________________________________ >> Xsltforms-support mailing list >> Xsl...@li... >> <mailto:Xsl...@li...> >> https://lists.sourceforge.net/lists/listinfo/xsltforms-support >> <https://lists.sourceforge.net/lists/listinfo/xsltforms-support> > > > > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > Xsltforms-support mailing list > Xsl...@li... > <mailto:Xsl...@li...> > https://lists.sourceforge.net/lists/listinfo/xsltforms-support > <https://lists.sourceforge.net/lists/listinfo/xsltforms-support> > > > > > > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > > > _______________________________________________ > Xsltforms-support mailing list > Xsl...@li... > https://lists.sourceforge.net/lists/listinfo/xsltforms-support |
|
From: Tim T. <tim...@gm...> - 2017-10-27 15:59:51
|
Alain, I believe I was able to reproduce this error in Chrome 61. See the attached screenshot, which references line 3614 in xsltforms.js. Best, Tim -- Tim A. Thompson Discovery Metadata Librarian Yale University Library On Fri, Oct 27, 2017 at 10:32 AM, Alain Couthures < > ala...@ag...> wrote: > >> Hi Mats, >> >> I have not been able to reproduce this issue: I have tested with Chrome >> 61, Chrome 62, Chrome Beta 62 and Chrome Canary 64 but no exception >> appeared... >> >> Could you please send me the line number you saw so I could check its >> validity? >> >> Thanks! >> >> --Alain >> >> >> Le 23/10/2017 à 14:36, Mats Eklund a écrit : >> >> Hi Alan, >> >> By chance stumbled upon a potential bug in the xsltforms >> library recently. The attached simple test case shows how an exception is >> thrown when user clicks Delete trigger on the last item in a repeat >> list. Only in Chrome it seems. >> >> It is possible to avoid the exception by putting an extra null check in >> the if() statement on the line where the exception is thrown, however, it >> looks like the issue may reveal a deeper issue, whose effects >> could sometimes be more subtle. >> >> / Mats >> >> >> >> >> ------------------------------------------------------------------------------ >> Check out the vibrant tech community on one of the world's most >> engaging tech sites, Slashdot.org! http://sdm.link/slashdot >> >> >> >> _______________________________________________ >> Xsltforms-support mailing lis...@li...https://lists.sourceforge.net/lists/listinfo/xsltforms-support >> >> >> >> ------------------------------------------------------------ >> ------------------ >> Check out the vibrant tech community on one of the world's most >> engaging tech sites, Slashdot.org! http://sdm.link/slashdot >> _______________________________________________ >> Xsltforms-support mailing list >> Xsl...@li... >> https://lists.sourceforge.net/lists/listinfo/xsltforms-support >> >> > |
|
From: Alain C. <ala...@ag...> - 2017-10-27 14:45:49
|
Hi Mats, I have not been able to reproduce this issue: I have tested with Chrome 61, Chrome 62, Chrome Beta 62 and Chrome Canary 64 but no exception appeared... Could you please send me the line number you saw so I could check its validity? Thanks! --Alain Le 23/10/2017 à 14:36, Mats Eklund a écrit : > Hi Alan, > > By chance stumbled upon a potential bug in the xsltforms > library recently. The attached simple test case shows how an exception > is thrown when user clicks Delete trigger on the last item in a repeat > list. Only in Chrome it seems. > > It is possible to avoid the exception by putting an extra null > check in the if() statement on the line where the exception is thrown, > however, it looks like the issue may reveal a deeper issue, whose > effects could sometimes be more subtle. > > / Mats > > > > > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > > > _______________________________________________ > 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.
