xsltforms-support Mailing List for XSLTForms
Brought to you by:
alain-couthures
Menu
▾
▴
xsltforms-support — XSLTForms support list
You can subscribe to this list here.
| 2009 |
Jan
|
Feb
|
Mar
|
Apr
(1) |
May
(6) |
Jun
(9) |
Jul
(16) |
Aug
(5) |
Sep
(43) |
Oct
(36) |
Nov
(58) |
Dec
(43) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2010 |
Jan
(79) |
Feb
(81) |
Mar
(107) |
Apr
(93) |
May
(85) |
Jun
(54) |
Jul
(64) |
Aug
(54) |
Sep
(45) |
Oct
(53) |
Nov
(34) |
Dec
(77) |
| 2011 |
Jan
(56) |
Feb
(53) |
Mar
(52) |
Apr
(66) |
May
(44) |
Jun
(16) |
Jul
(28) |
Aug
(5) |
Sep
(15) |
Oct
(21) |
Nov
(51) |
Dec
(46) |
| 2012 |
Jan
(16) |
Feb
(38) |
Mar
(47) |
Apr
(45) |
May
(41) |
Jun
(41) |
Jul
(72) |
Aug
(17) |
Sep
(10) |
Oct
(16) |
Nov
(29) |
Dec
(30) |
| 2013 |
Jan
(25) |
Feb
(13) |
Mar
(20) |
Apr
(25) |
May
(34) |
Jun
(8) |
Jul
(12) |
Aug
(9) |
Sep
(21) |
Oct
(19) |
Nov
(6) |
Dec
(2) |
| 2014 |
Jan
(14) |
Feb
(8) |
Mar
(7) |
Apr
(13) |
May
(33) |
Jun
(13) |
Jul
(6) |
Aug
(5) |
Sep
(5) |
Oct
(34) |
Nov
(7) |
Dec
|
| 2015 |
Jan
(1) |
Feb
(6) |
Mar
(17) |
Apr
(12) |
May
(10) |
Jun
(18) |
Jul
(31) |
Aug
(9) |
Sep
(3) |
Oct
(6) |
Nov
(19) |
Dec
(1) |
| 2016 |
Jan
(18) |
Feb
(4) |
Mar
(13) |
Apr
(19) |
May
|
Jun
(17) |
Jul
(7) |
Aug
|
Sep
(3) |
Oct
(6) |
Nov
(3) |
Dec
|
| 2017 |
Jan
(5) |
Feb
(17) |
Mar
(4) |
Apr
(8) |
May
(3) |
Jun
|
Jul
(8) |
Aug
(2) |
Sep
|
Oct
(5) |
Nov
(6) |
Dec
(4) |
| 2018 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(6) |
Nov
|
Dec
(1) |
| 2019 |
Jan
|
Feb
|
Mar
(4) |
Apr
(2) |
May
(4) |
Jun
|
Jul
|
Aug
(2) |
Sep
(7) |
Oct
|
Nov
|
Dec
|
| 2020 |
Jan
(13) |
Feb
(17) |
Mar
(8) |
Apr
(11) |
May
(15) |
Jun
(11) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(6) |
| 2021 |
Jan
(9) |
Feb
(26) |
Mar
(17) |
Apr
|
May
(7) |
Jun
(18) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(10) |
| 2022 |
Jan
|
Feb
(1) |
Mar
|
Apr
|
May
(3) |
Jun
|
Jul
|
Aug
(2) |
Sep
(3) |
Oct
(2) |
Nov
(10) |
Dec
(1) |
| 2023 |
Jan
(10) |
Feb
|
Mar
(7) |
Apr
(8) |
May
(3) |
Jun
|
Jul
|
Aug
|
Sep
(8) |
Oct
(11) |
Nov
(8) |
Dec
(5) |
| 2024 |
Jan
(7) |
Feb
(3) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2025 |
Jan
(4) |
Feb
(2) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Alessandro <ca...@tu...> - 2025-02-06 12:26:25
|
Dear Alain, many thaks for your answer (by the way, if I remember well, I was the one, some years ago, who sent you the Italian config file ;-)) and sorry for the waste of time I've caused to you (see below). As a matter of fact the problem consisted simply in my misunderstanding concerning the right settings of the browser (both Firefox and LibbreWolf). As you can see from the attached screenshot, there are three level for the language settigs and it is not enought to check the last one (as nonetheless would appear to be more logical), because one should also set the "preferred language for displaying pages"... My best regards Alex -- Protetto con Tuta Mail: https://tuta.com/free-email 1 feb 2025, 10:16 da ala...@ag...: > Hi Alex, > > XSLTForms v1.7 includes two mechanisms for internationalization: the legacy one based on config_XXX.xsl files and the new embedded one (Javascript config_data object) for a form to be a standalone HTML file. > > When no language is specified within the form, in legacy mode, XSLTForms gets the navigator language and loads the corresponding config_XXX.xsl file. Using the browser debugger, you should see the HTTP request for it. > > You can force the language using the regular HTML declaration: html/@lang attribute. > > Please find the standard Italian confile file attached. > > If it still does not work for you, I could enhance the new mechanism so it could fix file issues with the legacy one. > > Thank you for your feedback! > > --Alain > >> Le 30/01/2025 15:51 CET, Alessandro via Xsltforms-support <xsl...@li...> a écrit : >> >> >> Sorry, I've forgotten the screenshot... >> >> -- >> Protetto con Tuta Mail: >> https://tuta.com/free-email >> >> >> 25 gen 2025, 08:18 da ala...@ag...: >> > Hi Alex, >> > >> > I cannot yet reproduce this issue with the date picker. It works as expected with my own test forms. >> > >> > Could you please post a minimal test form and corresponding screen captures? >> > >> > Thanks! >> > >> > --Alain >> > > Le 21/01/2025 16:51 CET, Alessandro via Xsltforms-support <xsl...@li...> a écrit : >> > > >> > > >> > > Hi all, >> > > even following what suggested here (https://sourceforge.net/p/xsltforms/mailman/xsltforms-support/thread/4D0342CF.4040600%40hyperbase.com/#msg26735692) and here (https://sourceforge.net/p/xsltforms/mailman/message/26203855/) the date picker on an input field remains always set with the American format... I'm using the last xsltforms release 1.7... >> > > >> > > Many thanks >> > > Alex >> > > >> > > -- >> > > Protetto con Tuta Mail: >> > > https://tuta.com/free-email >> > > _______________________________________________ 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: Alain C. <ala...@ag...> - 2025-02-01 09:16:40
|
Hi Alex, XSLTForms v1.7 includes two mechanisms for internationalization: the legacy one based on config_XXX.xsl files and the new embedded one (Javascript config_data object) for a form to be a standalone HTML file. When no language is specified within the form, in legacy mode, XSLTForms gets the navigator language and loads the corresponding config_XXX.xsl file. Using the browser debugger, you should see the HTTP request for it. You can force the language using the regular HTML declaration: html/@lang attribute. Please find the standard Italian confile file attached. If it still does not work for you, I could enhance the new mechanism so it could fix file issues with the legacy one. Thank you for your feedback! --Alain > Le 30/01/2025 15:51 CET, Alessandro via Xsltforms-support <xsl...@li...> a écrit : > > > Sorry, I've forgotten the screenshot... > > -- > Protetto con Tuta Mail: > https://tuta.com/free-email > > > 25 gen 2025, 08:18 da ala...@ag...: > > Hi Alex, > > > > I cannot yet reproduce this issue with the date picker. It works as expected with my own test forms. > > > > Could you please post a minimal test form and corresponding screen captures? > > > > Thanks! > > > > --Alain > > > Le 21/01/2025 16:51 CET, Alessandro via Xsltforms-support <xsl...@li...> a écrit : > > > > > > > > > Hi all, > > > even following what suggested here (https://sourceforge.net/p/xsltforms/mailman/xsltforms-support/thread/4D0342CF.4040600%40hyperbase.com/#msg26735692) and here (https://sourceforge.net/p/xsltforms/mailman/message/26203855/) the date picker on an input field remains always set with the American format... I'm using the last xsltforms release 1.7... > > > > > > Many thanks > > > Alex > > > > > > -- > > > Protetto con Tuta Mail: > > > https://tuta.com/free-email > > > _______________________________________________ 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: Alessandro <ca...@tu...> - 2025-01-30 14:52:05
|
Sorry, I've forgotten the screenshot... -- Protetto con Tuta Mail: https://tuta.com/free-email 25 gen 2025, 08:18 da ala...@ag...: > Hi Alex, > > I cannot yet reproduce this issue with the date picker. It works as expected with my own test forms. > > Could you please post a minimal test form and corresponding screen captures? > > Thanks! > > --Alain > >> Le 21/01/2025 16:51 CET, Alessandro via Xsltforms-support <xsl...@li...> a écrit : >> >> >> Hi all, >> even following what suggested here (https://sourceforge.net/p/xsltforms/mailman/xsltforms-support/thread/4D0342CF.4040600%40hyperbase.com/#msg26735692) and here (https://sourceforge.net/p/xsltforms/mailman/message/26203855/) the date picker on an input field remains always set with the American format... I'm using the last xsltforms release 1.7... >> >> Many thanks >> Alex >> >> -- >> Protetto con Tuta Mail: >> https://tuta.com/free-email >> _______________________________________________ Xsltforms-support mailing list Xsl...@li... https://lists.sourceforge.net/lists/listinfo/xsltforms-support >> |
|
From: Alessandro <ca...@tu...> - 2025-01-30 14:44:30
|
Bonjour Alain, here it is a minimal example of one of the form (displaying the personal data of our workers) and attached you can find the relative screeshot. Mercì beaucoup Alex xquery version "3.1"; import module namespace my_funcs="http://www.my_funcs.net" at "modules/my_app_functions_2.xql"; declare variable $app_collection := '../DATI/XML_DB_files'; declare variable $id_dip := request:get-parameter("id_dip", ""); (: logs into the collection :) let $login := xmldb:login($app_collection, 'admin', 'tom1274') let $dati_personali := doc(concat($app_collection, '/', $my_funcs:my_employees_archive))/dipendenti/dipendente[@id=$id_dip] 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/xforms_fonts.css" media="screen,projection"/> <link rel="stylesheet" type="text/css" href="resources/css/schede_dipendenti_2.css" /> <script src="../DATI/XML_DB_files/my_javascripts.js"/> <style type="text/css"> <!--/*--><css><![CDATA[/**/ /*]]>*/<!--/*--></css><!--*/--> </style> <xf:model> <xf:instance id="dati-modificati"> <data xmlns="">{$dati_personali}</data> </xf:instance> <xf:instance id="changes-conf" xmlns=""> <data> <attesa_salvataggio>0</attesa_salvataggio> </data> </xf:instance> <xf:submission ref="instance('dati-modificati')" id="save-dati" method="post" action="query_save_dati_dipendenti.xq?id_dip={$id_dip}"> <xf:action ev:event="xforms-submit-done"> <xf:message level="modal">Dati correttamente aggiornati!</xf:message> </xf:action> <xf:action ev:event="xforms-submit-error"> <xf:message level="modal">Si è verificato un errore in fase di salvataggio!</xf:message> </xf:action> </xf:submission> <!-- BINDS PER CAMPI DATA --> <xf:bind nodeset="instance('dati-modificati')/dipendente/dati/dati_professionali/dta_assunz" type="xs:date"/> <xf:bind nodeset="instance('dati-modificati')/dipendente/dati/dati_personali/d_nascita" type="xs:date" /> </xf:model> </head> <body> <center> <h1>Visualizza e/o modifica dati dipendente</h1> <!-- TABELLA DEI DATI PERSONALI --> <br/> <fieldset id="fieldset-800"> <legend>DATI PERSONALI E PROFESSIONALI</legend> <table border="0" id=""> <tr> <td> <xf:output ref="instance('dati-modificati')/dipendente/@id" class="super-short-input" style="color: red;"> <xf:label><b>ID:</b><br/></xf:label> </xf:output> </td> <td style="width: 20px;"/> <td> <xf:input ref="instance('dati-modificati')/dipendente/dati/dati_personali/nome" class="long-input"> <xf:label>Nome:<br/></xf:label> </xf:input> </td> <td style="width: 10px;"/> <td> <xf:input ref="instance('dati-modificati')/dipendente/dati/dati_personali/cognome" class="super-long-input"> <xf:label>Cognome:<br/></xf:label> </xf:input> </td> </tr> </table> <br/> <table border="0" id=""> <tr> <td> <xf:input ref="instance('dati-modificati')/dipendente/dati/dati_personali/cf" class="mid-input"> <xf:label>Codice Fiscale:<br/></xf:label> </xf:input> </td> <td style="width: 10px;"/> <td> <xf:input ref="instance('dati-modificati')/dipendente/dati/dati_personali/d_nascita" class="short-input"> <xf:label>Data nascita:<br/></xf:label> </xf:input> </td> <td style="width: 10px;"/> <td> <xf:input ref="instance('dati-modificati')/dipendente/dati/dati_personali/l_nascita" class="mid-input"> <xf:label>Luogo nascita:<br/></xf:label> </xf:input> </td> <td style="width: 10px;"/> <td> <xf:input ref="instance('dati-modificati')/dipendente/dati/dati_professionali/tit_studio" class="mid-input"> <xf:label>Tit. studio:<br/></xf:label> </xf:input> </td> </tr> </table> <table border="0" id=""> <tr> <td> <xf:input ref="instance('dati-modificati')/dipendente/dati/dati_personali/indirizzo" class="long-input"> <xf:label>Indirizzo:<br/></xf:label> </xf:input> </td> <td style="width: 10px;"/> <td> <xf:input ref="instance('dati-modificati')/dipendente/dati/dati_personali/cap" class="short-input"> <xf:label>CAP:<br/></xf:label> </xf:input> </td> <td style="width: 10px;"/> <td> <xf:input ref="instance('dati-modificati')/dipendente/dati/dati_personali/citta" class="mid-input"> <xf:label>Città:<br/></xf:label> </xf:input> </td> <td style="width: 10px;"/> <td> <xf:input ref="instance('dati-modificati')/dipendente/dati/dati_personali/provincia" class="super-short-input"> <xf:label>Provincia:<br/></xf:label> </xf:input> </td> </tr> </table> <br/> <table border="0" id=""> <tr> <td> <xf:input ref="instance('dati-modificati')/dipendente/dati/dati_personali/tel/num[@id='1']" class="mid-input"> <xf:label>Telefono 1:<br/></xf:label> </xf:input> </td> <td style="width: 10px;"/> <td> <xf:input ref="instance('dati-modificati')/dipendente/dati/dati_personali/tel/num[@id='2']" class="mid-input"> <xf:label>Telefono 2:<br/></xf:label> </xf:input> </td> <td style="width: 10px;"/> <td> <xf:input ref="instance('dati-modificati')/dipendente/dati/dati_personali/tel/num[@id='3']" class="mid-input"> <xf:label>Telefono 3:<br/></xf:label> </xf:input> </td> </tr> </table> <table border="0" id=""> <tr> <td> <xf:input ref="instance('dati-modificati')/dipendente/dati/dati_personali/cell/num[@id='1']" class="mid-input"> <xf:label>Cellulare 1:<br/></xf:label> </xf:input> </td> <td style="width: 10px;"/> <td> <xf:input ref="instance('dati-modificati')/dipendente/dati/dati_personali/cell/num[@id='2']" class="mid-input"> <xf:label>Cellulare 2:<br/></xf:label> </xf:input> </td> <td style="width: 10px;"/> <td> <xf:input ref="instance('dati-modificati')/dipendente/dati/dati_personali/cell/num[@id='3']" class="mid-input"> <xf:label>Cellulare 3:<br/></xf:label> </xf:input> </td> </tr> </table> <br/> <br/> <table border="0" id=""> <tr> <td> <xf:input ref="instance('dati-modificati')/dipendente/dati/dati_professionali/qualifica" class="long-input"> <xf:label>Qualifica:<br/></xf:label> </xf:input> </td> <td style="width: 10px;"/> <td> <!--<xf:input ref="/dipendenti/dipendente[@id='{$id_dip}']/dati/dati_professionali/livello" class="super-short-input">--> <xf:input ref="instance('dati-modificati')/dipendente/dati/dati_professionali/livello" class="super-short-input"> <xf:label>Livello:<br/></xf:label> </xf:input> </td> <td style="width: 10px;"/> <td> <xf:input ref="instance('dati-modificati')/dipendente/dati/dati_professionali/matr" class="short-input"> <xf:label>Matr:<br/></xf:label> </xf:input> </td> <td style="width: 10px;"/> <td> <xf:input ref="instance('dati-modificati')/dipendente/dati/dati_professionali/dta_assunz" class="short-input" incremental="true" data-bf-params="date:'dd/MM/yyyy'"> <xf:label>Data assunzione:<br/></xf:label> </xf:input> </td> <td style="width: 10px;"/> <td> <xf:select1 ref="instance('dati-modificati')/dipendente/dati/dati_professionali/stato" appearance="minimal" class="select-mid-input"> <xf:label>Stato:<br/></xf:label> <xf:item> <xf:label>Attivo</xf:label> <xf:value>attivo</xf:value> </xf:item> <xf:item> <xf:label>Pensionato</xf:label> <xf:value>pensionato</xf:value> </xf:item> <xf:item> <xf:label>Speciale</xf:label> <xf:value>speciale</xf:value> </xf:item> <xf:item> <xf:label>Cessato</xf:label> <xf:value>cessato</xf:value> </xf:item> </xf:select1> </td> </tr> </table> <br/> <table border="0" id=""> <tr> <td> <xf:input ref="instance('dati-modificati')/dipendente/dati/dati_professionali/mansioni/mansione[@id='1']" class="mid-input-plus"> <xf:label>Mansione/corso 1:<br/></xf:label> </xf:input> </td> <td style="width: 10px;"/> <td> <xf:input ref="instance('dati-modificati')/dipendente/dati/dati_professionali/mansioni/mansione[@id='2']" class="mid-input-plus"> <xf:label>Mansione/corso 2:<br/></xf:label> </xf:input> </td> <td style="width: 10px;"/> <td> <xf:input ref="instance('dati-modificati')/dipendente/dati/dati_professionali/mansioni/mansione[@id='3']" class="mid-input-plus"> <xf:label>Mansione/corso 3:<br/></xf:label> </xf:input> </td> </tr> </table> <table border="0" id=""> <tr> <td> <xf:input ref="instance('dati-modificati')/dipendente/dati/dati_professionali/mansioni/mansione[@id='4']" class="mid-input-plus"> <xf:label>Mansione/corso 4:<br/></xf:label> </xf:input> </td> <td style="width: 10px;"/> <td> <xf:input ref="instance('dati-modificati')/dipendente/dati/dati_professionali/mansioni/mansione[@id='5']" class="mid-input-plus"> <xf:label>Mansione/corso 5:<br/></xf:label> </xf:input> </td> <td style="width: 10px;"/> <td> <xf:input ref="instance('dati-modificati')/dipendente/dati/dati_professionali/mansioni/mansione[@id='6']" class="mid-input-plus"> <xf:label>Mansione/corso 6:<br/></xf:label> </xf:input> </td> </tr> </table> <table border="0" id=""> <tr> <td> <xf:input ref="instance('dati-modificati')/dipendente/dati/dati_professionali/mansioni/mansione[@id='7']" class="mid-input-plus"> <xf:label>Mansione/corso 7:<br/></xf:label> </xf:input> </td> <td style="width: 10px;"/> <td> <xf:input ref="instance('dati-modificati')/dipendente/dati/dati_professionali/mansioni/mansione[@id='8']" class="mid-input-plus"> <xf:label>Mansione/corso 8:<br/></xf:label> </xf:input> </td> <td style="width: 10px;"/> <td> <xf:input ref="instance('dati-modificati')/dipendente/dati/dati_professionali/mansioni/mansione[@id='9']" class="mid-input-plus"> <xf:label>Mansione/corso 9:<br/></xf:label> </xf:input> </td> </tr> </table> <br/> </fieldset> <br/> <table border="0"> <tr> <td style="height: 40px;"/> <td> <!-- style="padding-top: 15pt;" --> <xf:submit submission="save-dati" > <xf:label class="my_button_2" style="width: 210px;"><b>Salva</b> modifiche ai dati personali</xf:label> </xf:submit> </td> </tr> </table> </center> <br/> <br/> </body> </html> let $xslt-pi := processing-instruction xml-stylesheet {'type="text/xsl" href="../xsltforms/xsltforms.xsl"'} return ($xslt-pi,$form) -- Protetto con Tuta Mail: https://tuta.com/free-email 25 gen 2025, 08:18 da ala...@ag...: Hi Alex, I cannot yet reproduce this issue with the date picker. It works as expected with my own test forms. Could you please post a minimal test form and corresponding screen captures? Thanks! --Alain Le 21/01/2025 16:51 CET, Alessandro via Xsltforms-support <xsl...@li...> a écrit : Hi all, even following what suggested here (https://sourceforge.net/p/xsltforms/mailman/xsltforms-support/thread/4D0342CF.4040600%40hyperbase.com/#msg26735692) and here (https://sourceforge.net/p/xsltforms/mailman/message/26203855/) the date picker on an input field remains always set with the American format... I'm using the last xsltforms release 1.7... Many thanks Alex -- Protetto con Tuta Mail: https://tuta.com/free-email _______________________________________________ Xsltforms-support mailing list Xsl...@li... https://lists.sourceforge.net/lists/listinfo/xsltforms-support -- Protetto con Tuta Mail: https://tuta.com/free-email 25 gen 2025, 08:18 da ala...@ag...: > Hi Alex, > > I cannot yet reproduce this issue with the date picker. It works as expected with my own test forms. > > Could you please post a minimal test form and corresponding screen captures? > > Thanks! > > --Alain > >> Le 21/01/2025 16:51 CET, Alessandro via Xsltforms-support <xsl...@li...> a écrit : >> >> >> Hi all, >> even following what suggested here (https://sourceforge.net/p/xsltforms/mailman/xsltforms-support/thread/4D0342CF.4040600%40hyperbase.com/#msg26735692) and here (https://sourceforge.net/p/xsltforms/mailman/message/26203855/) the date picker on an input field remains always set with the American format... I'm using the last xsltforms release 1.7... >> >> Many thanks >> Alex >> >> -- >> Protetto con Tuta Mail: >> https://tuta.com/free-email >> _______________________________________________ Xsltforms-support mailing list Xsl...@li... https://lists.sourceforge.net/lists/listinfo/xsltforms-support >> |
|
From: Alain C. <ala...@ag...> - 2025-01-25 08:18:29
|
Hi Alex, I cannot yet reproduce this issue with the date picker. It works as expected with my own test forms. Could you please post a minimal test form and corresponding screen captures? Thanks! --Alain > Le 21/01/2025 16:51 CET, Alessandro via Xsltforms-support <xsl...@li...> a écrit : > > > Hi all, > even following what suggested here (https://sourceforge.net/p/xsltforms/mailman/xsltforms-support/thread/4D0342CF.4040600%40hyperbase.com/#msg26735692) and here (https://sourceforge.net/p/xsltforms/mailman/message/26203855/) the date picker on an input field remains always set with the American format... I'm using the last xsltforms release 1.7... > > Many thanks > Alex > > -- > Protetto con Tuta Mail: > https://tuta.com/free-email > _______________________________________________ Xsltforms-support mailing list Xsl...@li... https://lists.sourceforge.net/lists/listinfo/xsltforms-support |
|
From: Alessandro <ca...@tu...> - 2025-01-21 16:07:32
|
Hi all, even following what suggested here (https://sourceforge.net/p/xsltforms/mailman/xsltforms-support/thread/4D0342CF.4040600%40hyperbase.com/#msg26735692) and here (https://sourceforge.net/p/xsltforms/mailman/message/26203855/) the date picker on an input field remains always set with the American format... I'm using the last xsltforms release 1.7... Many thanks Alex -- Protetto con Tuta Mail: https://tuta.com/free-email |
|
From: Winona S. <wsa...@gm...> - 2024-02-12 12:25:25
|
Hi Alain, Just checking in on this issue. You said you already had a fix? Any chance I can get a patched xsltforms.js? Thanks for your help, -Winona On Mon, Jan 22, 2024 at 10:07 AM Winona Salesky <wsa...@gm...> wrote: > > Hi Alain, > Thanks for getting back to me and for working on a fix, that will be so helpful. > I did try the latest version of XSLTForms, but it required a lot of rewriting of the forms I already had and I was pressed for time. I hope to have time in the near future to take another look. > -Winona > > > On Sun, Jan 21, 2024 at 3:13 PM Alain Couthures <ala...@ag...> wrote: >> >> Hi Winona, >> >> This issue is due to remaining ids in dependencies which should have been removed when unloading the subform. >> >> I have already a workaround for preventing the exception. I will look for a fix as soon as possible. >> >> I will probably not release some 1.3.1 release but I will send you a patched xsltforms.js instead. >> >> Please give a try to latest XSLTForms release to help me to locate other issues. >> >> --Alain >> >> Le 15/01/2024 17:19 CET, Winona Salesky <wsa...@gm...> a écrit : >> >> >> Hi Alain, >> Thank you so much for all your help with my XForms. I'm having some trouble integrating the TinyMCE example into my much more complex forms set up. I have tried to create a simplified example that still produces the error I am getting. Any chance you could help me debug this? >> Example here: https://gist.github.com/wsalesky/d24ce3ebcbc00f673b3d4a44202cb83b >> >> If I choose the msContents subform from the menu, the TinyMCE text editor works as expected, I can then toggle to my other subform (msIdentifier), but if I then attempt to toggle back to the msContents form again I get the following error (XSLTForms v 1.3): >> >> XSLTForms Exception >> Error dispatching event 'forms-revalidate' : >> TypeError: Cannot read properties of undefined (reading 'length') at new XsltForms_exprContext(../xsltforms.js:4121:43) >> >> >> Toggling between these subforms without the TinyMCE additions work without error, but I'm unsure what exactly is causing the error with the addition of the TinyMCE code. Do you have any suggestions or insights? >> Thank you again for your help, >> -Winona >> >> >> >> >> >> On Wed, Jan 3, 2024 at 9:13 AM Winona Salesky <wsa...@gm...> wrote: >> >> Hi Alain, >> That did fix the example. Thank you. I think I have misunderstood the use of the XForms binding. So I will do a little research and see if I can get them working correctly on my more complex version of the form, which has the summary element at many different levels in the TEI record. >> >> -Winona >> >> >> On Wed, Jan 3, 2024 at 5:13 AM Alain Couthures <ala...@ag...> wrote: >> >> Hi Winona, >> >> Looking at the simplified example, it appears that the new record does not have the very same structure: the document root is named "TEI" with a child named "data" whilst the pre-loaded document has the "data" element as root. >> >> XForms bindings are context dependant, they are not like XSLT template match attribute values. >> >> Whether subforms are used should not interfere with bindings. >> >> Thank you for your feedback! >> >> --Alain >> >> Le 03/01/2024 00:54 CET, Winona Salesky <wsa...@gm...> a écrit : >> >> >> Hi Alain, >> This sort of works. Here is an example of multiple text editors working: https://gist.github.com/wsalesky/00b872cd91c99344a030f0e667cb9e35 >> >> However, when I try to use this in my actual forms I run into issue. I think it is because my data is loaded after the form is loaded. The user is presented with a main form that allows them to search for records or load a 'template' record into the form. If the data is pre-loaded, the tinyMCE editor works, once I select and load a new record, the textarea are displayed a regular textareas, not as tinyMCE editors. >> Here is a simplified example: https://gist.github.com/wsalesky/bf6b25b50b082c8f0bd8dcf7e7b1eaf2 >> >> Any thoughts on how to solve this issue? Also, many of my textareas that I want editable will be in subforms. Not sure if that adds another layer of complication or not. >> Thanks! >> -Winona >> >> >> On Sun, Dec 31, 2023 at 8:00 AM Alain Couthures <ala...@ag...> wrote: >> >> Hi Winona, >> >> Sorry for the delay. >> >> Please have a look at the tinymce.xml sample (https://github.com/AlainCouthures/declarative4all/blob/master/public/samples/tinymce.xml). >> >> Because of compatibility issues between tinymce versions, it is required to add data-uri and data-version attributes to allow XSLTForms to properly manage the rich text editors. In the sample: >> <script type="text/javascript" src="js/tinymce_4.5.3/tinymce.min.js" data-uri="http://www.tinymce.com" data-version="4.5.3">/* */</script> >> >> In next release, XSLTForms will also check "tinymce.majorVersion + '.' + tinymce.minorVersion", as suggested by ChatGPT ;-) >> >> After upgrading the repeat test case accordingly, it works as expected for me! >> >> Thank you for your feedback! >> >> --Alain >> >> Le 17/12/2023 19:30 CET, Winona Salesky <wsa...@gm...> a écrit : >> >> >> Hi All, >> I'm looking into adding a rich text editor to my textarea's. I was trying to experiment with this example: >> http://www.agencexml.com/xsltforms/tinymce.xml >> >> But have had some trouble getting it working. My use case would include multiple textarea's almost all of them appearing in a nested repeat structure. I found this on the list (https://sourceforge.net/p/xsltforms/mailman/xsltforms-support/thread/A6AB89C8-E8E0-49C3-965F-65464934B94D%40basex.org/#msg30316903) which suggests repeats could be a problem. Has this been solved? Has anyone integrated a text editor into their XForms? I can mock up a simplified example of what I am trying to do if that would be useful, but I'm mostly looking for examples for how someone else may have solved this issue. >> >> Thanks! >> -Winona >> >> _______________________________________________ Xsltforms-support mailing list Xsl...@li... https://lists.sourceforge.net/lists/listinfo/xsltforms-support |
|
From: Winona S. <wsa...@gm...> - 2024-02-02 17:41:28
|
Great news, thanks for the update and the example.
-Winona
On Fri, Feb 2, 2024 at 10:56 AM Steven Pemberton <ste...@cw...>
wrote:
> Winona,
>
> We have discussed this in the WG, and resolved to add @dir to the Common
> set of attributes.
>
> In the meantime, as Alain has already pointed out, you can legally use
> html:dir anywhere in XForms, as foreign namespaced attributes are allowable
> everywhere, and furthermore, you can use CSS properties for the same
> effect. For instance:
>
> *[class="ltr"] { unicode-bidi: embed; direction: ltr}
> *[class="rtl"] { unicode-bidi: embed; direction: rtl}
> *[class="lro"] { unicode-bidi: bidi-override; direction: ltr}
> *[class="rlo"] { unicode-bidi: bidi-override; direction: rtl}
>
> I show a quick example at https://cwi.nl/~steven/forms/tests/bidi.xhtml
>
> Best wishes,
>
> Steven
>
> On Thursday 07 December 2023 17:11:16 (+01:00), Winona Salesky wrote:
>
> Hi All,
> I need to support both rtl and ltr text input in my forms. Reading up on
> this online, it sounds like the best way to do this is to include the
> following attribute on the input/textarea elements: dir="auto"
>
> What do you think the best way to get this working in XSLTForms is? Edit
> the XSLTForms javascript? Write my own Javascript to amend the output?
> Something else?
>
> Thanks for any thoughts or suggestions.
> -Winona
>
>
|
|
From: Steven P. <ste...@cw...> - 2024-02-02 16:14:09
|
Winona,
We have discussed this in the WG, and resolved to add @dir to the Common
set of attributes.
In the meantime, as Alain has already pointed out, you can legally use
html:dir anywhere in XForms, as foreign namespaced attributes are allowable
everywhere, and furthermore, you can use CSS properties for the same
effect. For instance:
*[class="ltr"] { unicode-bidi: embed; direction: ltr}
*[class="rtl"] { unicode-bidi: embed; direction: rtl}
*[class="lro"] { unicode-bidi: bidi-override; direction: ltr}
*[class="rlo"] { unicode-bidi: bidi-override; direction: rtl}
I show a quick example at https://cwi.nl/~steven/forms/tests/bidi.xhtml
Best wishes,
Steven
On Thursday 07 December 2023 17:11:16 (+01:00), Winona Salesky wrote:
Hi All,
I need to support both rtl and ltr text input in my forms. Reading up on
this online, it sounds like the best way to do this is to include the
following attribute on the input/textarea elements: dir="auto"
What do you think the best way to get this working in XSLTForms is? Edit
the XSLTForms javascript? Write my own Javascript to amend the output?
Something else?
Thanks for any thoughts or suggestions.
-Winona |
|
From: Winona S. <wsa...@gm...> - 2024-01-24 19:37:36
|
Hi All, I'm running XSLTForms in eXist-db and experiencing some caching issues that prevent my forms from reloading, for example: I edit one record. Save it, and open a new record (same form) but the new record does not show up, I get a cached version of the form. Anyone else running into this and have a good solution? Thanks for the help, -Winona |
|
From: Winona S. <wsa...@gm...> - 2024-01-22 15:07:40
|
Hi Alain, Thanks for getting back to me and for working on a fix, that will be so helpful. I did try the latest version of XSLTForms, but it required a lot of rewriting of the forms I already had and I was pressed for time. I hope to have time in the near future to take another look. -Winona On Sun, Jan 21, 2024 at 3:13 PM Alain Couthures < ala...@ag...> wrote: > Hi Winona, > > This issue is due to remaining ids in dependencies which should have been > removed when unloading the subform. > > I have already a workaround for preventing the exception. I will look for > a fix as soon as possible. > > I will probably not release some 1.3.1 release but I will send you a > patched xsltforms.js instead. > > Please give a try to latest XSLTForms release to help me to locate other > issues. > > --Alain > > Le 15/01/2024 17:19 CET, Winona Salesky <wsa...@gm...> a écrit : > > > Hi Alain, > Thank you so much for all your help with my XForms. I'm having some > trouble integrating the TinyMCE example into my much more complex forms set > up. I have tried to create a simplified example that still produces the > error I am getting. Any chance you could help me debug this? > Example here: > https://gist.github.com/wsalesky/d24ce3ebcbc00f673b3d4a44202cb83b > > If I choose the msContents subform from the menu, the TinyMCE text editor > works as expected, I can then toggle to my other subform (msIdentifier), > but if I then attempt to toggle back to the msContents form again I get the > following error (XSLTForms v 1.3): > > XSLTForms Exception > Error dispatching event 'forms-revalidate' : > TypeError: Cannot read properties of undefined (reading 'length') at new > XsltForms_exprContext(../xsltforms.js:4121:43) > > > Toggling between these subforms without the TinyMCE additions work without > error, but I'm unsure what exactly is causing the error with the addition > of the TinyMCE code. Do you have any suggestions or insights? > Thank you again for your help, > -Winona > > > > > > On Wed, Jan 3, 2024 at 9:13 AM Winona Salesky <wsa...@gm...> wrote: > > Hi Alain, > That did fix the example. Thank you. I think I have misunderstood the use > of the XForms binding. So I will do a little research and see if I can get > them working correctly on my more complex version of the form, which has > the summary element at many different levels in the TEI record. > > -Winona > > > On Wed, Jan 3, 2024 at 5:13 AM Alain Couthures < > ala...@ag...> wrote: > > Hi Winona, > > Looking at the simplified example, it appears that the new record does not > have the very same structure: the document root is named "TEI" with a child > named "data" whilst the pre-loaded document has the "data" element as root. > > XForms bindings are context dependant, they are not like XSLT template > match attribute values. > > Whether subforms are used should not interfere with bindings. > > Thank you for your feedback! > > --Alain > > Le 03/01/2024 00:54 CET, Winona Salesky <wsa...@gm...> a écrit : > > > Hi Alain, > This sort of works. Here is an example of multiple text editors working: > https://gist.github.com/wsalesky/00b872cd91c99344a030f0e667cb9e35 > > However, when I try to use this in my actual forms I run into issue. I > think it is because my data is loaded after the form is loaded. The user is > presented with a main form that allows them to search for records or load a > 'template' record into the form. If the data is pre-loaded, the tinyMCE > editor works, once I select and load a new record, the textarea are > displayed a regular textareas, not as tinyMCE editors. > Here is a simplified example: > https://gist.github.com/wsalesky/bf6b25b50b082c8f0bd8dcf7e7b1eaf2 > > Any thoughts on how to solve this issue? Also, many of my textareas that I > want editable will be in subforms. Not sure if that adds another layer of > complication or not. > Thanks! > -Winona > > > On Sun, Dec 31, 2023 at 8:00 AM Alain Couthures < > ala...@ag...> wrote: > > Hi Winona, > > Sorry for the delay. > > Please have a look at the tinymce.xml sample ( > https://github.com/AlainCouthures/declarative4all/blob/master/public/samples/tinymce.xml). > > > Because of compatibility issues between tinymce versions, it is required > to add data-uri and data-version attributes to allow XSLTForms to properly > manage the rich text editors. In the sample: > <script type="text/javascript" src="js/tinymce_4.5.3/tinymce.min.js" > data-uri="http://www.tinymce.com" data-version="4.5.3">/* */</script> > > In next release, XSLTForms will also check "tinymce.majorVersion + '.' + > tinymce.minorVersion", as suggested by ChatGPT ;-) > > After upgrading the repeat test case accordingly, it works as expected for > me! > > Thank you for your feedback! > > --Alain > > Le 17/12/2023 19:30 CET, Winona Salesky <wsa...@gm...> a écrit : > > > Hi All, > I'm looking into adding a rich text editor to my textarea's. I was trying > to experiment with this example: > http://www.agencexml.com/xsltforms/tinymce.xml > > But have had some trouble getting it working. My use case would include > multiple textarea's almost all of them appearing in a nested repeat > structure. I found this on the list ( > https://sourceforge.net/p/xsltforms/mailman/xsltforms-support/thread/A6AB89C8-E8E0-49C3-965F-65464934B94D%40basex.org/#msg30316903) > which suggests repeats could be a problem. Has this been solved? Has anyone > integrated a text editor into their XForms? I can mock up a > simplified example of what I am trying to do if that would be useful, but > I'm mostly looking for examples for how someone else may have solved this > issue. > > Thanks! > -Winona > > _______________________________________________ Xsltforms-support mailing > list Xsl...@li... > https://lists.sourceforge.net/lists/listinfo/xsltforms-support > > |
|
From: Alain C. <ala...@ag...> - 2024-01-21 20:14:14
|
<!doctype html>
<html>
<head>
<meta charset="UTF-8">
</head>
<body>
<div>
Hi Winona,
</div>
<div class="default-style">
</div>
<div class="default-style">
This issue is due to remaining ids in dependencies which should have been removed when unloading the subform.
</div>
<div class="default-style">
</div>
<div class="default-style">
I have already a workaround for preventing the exception. I will look for a fix as soon as possible.
</div>
<div class="default-style">
</div>
<div class="default-style">
I will probably not release some 1.3.1 release but I will send you a patched xsltforms.js instead.
</div>
<div class="default-style">
</div>
<div class="default-style">
Please give a try to latest XSLTForms release to help me to locate other issues.
</div>
<div class="default-style">
</div>
<div class="default-style">
--Alain
</div>
<blockquote type="cite">
<div>
Le 15/01/2024 17:19 CET, Winona Salesky <wsa...@gm...> a écrit :
</div>
<div>
</div>
<div>
</div>
<div dir="ltr">
Hi Alain,
<div>
Thank you so much for all your help with my XForms. I'm having some trouble integrating the TinyMCE example into my much more complex forms set up. I have tried to create a simplified example that still produces the error I am getting. Any chance you could help me debug this?
<br>Example here: <a href="https://gist.github.com/wsalesky/d24ce3ebcbc00f673b3d4a44202cb83b">https://gist.github.com/wsalesky/d24ce3ebcbc00f673b3d4a44202cb83b</a>
<br>
<br>If I choose the msContents subform from the menu, the TinyMCE text editor works as expected, I can then toggle to my other subform (msIdentifier), but if I then attempt to toggle back to the msContents form again I get the following error (XSLTForms v 1.3):
<br>
<br><span style="font-family: monospace;">XSLTForms Exception<br>Error dispatching event 'forms-revalidate' :<br>TypeError: Cannot read properties of undefined (reading 'length') at new XsltForms_exprContext(../xsltforms.js:4121:43)<br><br></span>
<br>Toggling between these subforms without the TinyMCE additions work without error, but I'm unsure what exactly is causing the error with the addition of the TinyMCE code. Do you have any suggestions or insights?
<br>Thank you again for your help,
</div>
<div>
-Winona
<br>
<br>
<br>
<br>
<br>
</div>
</div>
<br>
<div class="gmail_quote">
<div class="gmail_attr" dir="ltr">
On Wed, Jan 3, 2024 at 9:13 AM Winona Salesky <<a href="mailto:wsa...@gm...">wsa...@gm...</a>> wrote:
</div>
<blockquote>
<div dir="ltr">
Hi Alain,
<div>
That did fix the example. Thank you. I think I have misunderstood the use of the XForms binding. So I will do a little research and see if I can get them working correctly on my more complex version of the form, which has the summary element at many different levels in the TEI record.
</div>
<div>
</div>
<div>
-Winona
</div>
<div>
</div>
</div>
<br>
<div class="gmail_quote">
<div class="gmail_attr" dir="ltr">
On Wed, Jan 3, 2024 at 5:13 AM Alain Couthures <<a href="mailto:ala...@ag..." target="_blank" rel="noopener">ala...@ag...</a>> wrote:
</div>
<blockquote>
<u></u>
<div>
<div>
Hi Winona,
</div>
<div>
</div>
<div>
Looking at the simplified example, it appears that the new record does not have the very same structure: the document root is named "TEI" with a child named "data" whilst the pre-loaded document has the "data" element as root.
</div>
<div>
</div>
<div>
XForms bindings are context dependant, they are not like XSLT template match attribute values.
</div>
<div>
</div>
<div>
Whether subforms are used should not interfere with bindings.
</div>
<div>
</div>
<div>
Thank you for your feedback!
</div>
<div>
</div>
<div>
--Alain
</div>
<blockquote type="cite">
<div>
Le 03/01/2024 00:54 CET, Winona Salesky <<a href="mailto:wsa...@gm..." target="_blank" rel="noopener">wsa...@gm...</a>> a écrit :
</div>
<div>
</div>
<div>
</div>
<div dir="ltr">
Hi Alain,
<div>
This sort of works. Here is an example of multiple text editors working: <a href="https://gist.github.com/wsalesky/00b872cd91c99344a030f0e667cb9e35" target="_blank" rel="noopener">https://gist.github.com/wsalesky/00b872cd91c99344a030f0e667cb9e35</a>
</div>
<div>
</div>
<div>
However, when I try to use this in my actual forms I run into issue. I think it is because my data is loaded after the form is loaded. The user is presented with a main form that allows them to search for records or load a 'template' record into the form. If the data is pre-loaded, the tinyMCE editor works, once I select and load a new record, the textarea are displayed a regular textareas, not as tinyMCE editors.
</div>
<div>
Here is a simplified example: <a href="https://gist.github.com/wsalesky/bf6b25b50b082c8f0bd8dcf7e7b1eaf2" target="_blank" rel="noopener">https://gist.github.com/wsalesky/bf6b25b50b082c8f0bd8dcf7e7b1eaf2</a>
<br>
<br>Any thoughts on how to solve this issue? Also, many of my textareas that I want editable will be in subforms. Not sure if that adds another layer of complication or not.
</div>
<div>
Thanks!
</div>
<div>
-Winona
</div>
<div>
</div>
</div>
<br>
<div class="gmail_quote">
<div class="gmail_attr" dir="ltr">
On Sun, Dec 31, 2023 at 8:00 AM Alain Couthures <<a href="mailto:ala...@ag..." target="_blank" rel="noopener">ala...@ag...</a>> wrote:
</div>
<blockquote>
<u></u>
<div>
<div>
Hi Winona,
</div>
<div>
<div>
</div>
<div>
Sorry for the delay.
</div>
<div>
</div>
</div>
<div>
Please have a look at the tinymce.xml sample (<a href="https://github.com/AlainCouthures/declarative4all/blob/master/public/samples/tinymce.xml)" target="_blank" rel="noopener">https://github.com/AlainCouthures/declarative4all/blob/master/public/samples/tinymce.xml)</a>.
</div>
<div>
</div>
<div>
Because of compatibility issues between tinymce versions, it is required to add data-uri and data-version attributes to allow XSLTForms to properly manage the rich text editors. In the sample:
<br><script type="text/javascript" src="js/tinymce_4.5.3/tinymce.min.js" data-uri="<a href="http://www.tinymce.com" target="_blank" rel="noopener">http://www.tinymce.com</a>" data-version="4.5.3">/* */</script>
</div>
<div>
</div>
<div>
In next release, XSLTForms will also check "tinymce.majorVersion + '.' + tinymce.minorVersion", as suggested by ChatGPT ;-)
</div>
<div>
</div>
<div>
After upgrading the repeat test case accordingly, it works as expected for me!
</div>
<div>
</div>
<div>
Thank you for your feedback!
</div>
<div>
</div>
<div>
--Alain
</div>
<blockquote type="cite">
<div>
Le 17/12/2023 19:30 CET, Winona Salesky <<a href="mailto:wsa...@gm..." target="_blank" rel="noopener">wsa...@gm...</a>> a écrit :
</div>
<div>
</div>
<div>
</div>
<div dir="ltr">
Hi All,
<br>
<div>
I'm looking into adding a rich text editor to my textarea's. I was trying to experiment with this example:
</div>
<div>
<a href="http://www.agencexml.com/xsltforms/tinymce.xml" target="_blank" rel="noopener">http://www.agencexml.com/xsltforms/tinymce.xml</a>
</div>
<div>
</div>
<div>
But have had some trouble getting it working. My use case would include multiple textarea's almost all of them appearing in a nested repeat structure. I found this on the list (<a href="https://sourceforge.net/p/xsltforms/mailman/xsltforms-support/thread/A6AB89C8-E8E0-49C3-965F-65464934B94D%40basex.org/#msg30316903" target="_blank" rel="noopener">https://sourceforge.net/p/xsltforms/mailman/xsltforms-support/thread/A6AB89C8-E8E0-49C3-965F-65464934B94D%40basex.org/#msg30316903</a>) which suggests repeats could be a problem. Has this been solved? Has anyone integrated a text editor into their XForms? I can mock up a simplified example of what I am trying to do if that would be useful, but I'm mostly looking for examples for how someone else may have solved this issue.
</div>
<div>
</div>
<div>
Thanks!
</div>
<div>
-Winona
</div>
<div>
</div>
</div> _______________________________________________ Xsltforms-support mailing list <a href="mailto:Xsl...@li..." target="_blank" rel="noopener">Xsl...@li...</a> <a href="https://lists.sourceforge.net/lists/listinfo/xsltforms-support" target="_blank" rel="noopener">https://lists.sourceforge.net/lists/listinfo/xsltforms-support</a>
</blockquote>
</div>
</blockquote>
</div>
</blockquote>
</div>
</blockquote>
</div>
</blockquote>
</div>
</blockquote>
</body>
</html>
|
|
From: Winona S. <wsa...@gm...> - 2024-01-15 16:19:46
|
Hi Alain, Thank you so much for all your help with my XForms. I'm having some trouble integrating the TinyMCE example into my much more complex forms set up. I have tried to create a simplified example that still produces the error I am getting. Any chance you could help me debug this? Example here: https://gist.github.com/wsalesky/d24ce3ebcbc00f673b3d4a44202cb83b If I choose the msContents subform from the menu, the TinyMCE text editor works as expected, I can then toggle to my other subform (msIdentifier), but if I then attempt to toggle back to the msContents form again I get the following error (XSLTForms v 1.3): XSLTForms Exception Error dispatching event 'forms-revalidate' : TypeError: Cannot read properties of undefined (reading 'length') at new XsltForms_exprContext(../xsltforms.js:4121:43) Toggling between these subforms without the TinyMCE additions work without error, but I'm unsure what exactly is causing the error with the addition of the TinyMCE code. Do you have any suggestions or insights? Thank you again for your help, -Winona On Wed, Jan 3, 2024 at 9:13 AM Winona Salesky <wsa...@gm...> wrote: > Hi Alain, > That did fix the example. Thank you. I think I have misunderstood the use > of the XForms binding. So I will do a little research and see if I can get > them working correctly on my more complex version of the form, which has > the summary element at many different levels in the TEI record. > > -Winona > > > On Wed, Jan 3, 2024 at 5:13 AM Alain Couthures < > ala...@ag...> wrote: > >> Hi Winona, >> >> Looking at the simplified example, it appears that the new record does >> not have the very same structure: the document root is named "TEI" with a >> child named "data" whilst the pre-loaded document has the "data" element as >> root. >> >> XForms bindings are context dependant, they are not like XSLT template >> match attribute values. >> >> Whether subforms are used should not interfere with bindings. >> >> Thank you for your feedback! >> >> --Alain >> >> Le 03/01/2024 00:54 CET, Winona Salesky <wsa...@gm...> a écrit : >> >> >> Hi Alain, >> This sort of works. Here is an example of multiple text editors working: >> https://gist.github.com/wsalesky/00b872cd91c99344a030f0e667cb9e35 >> >> However, when I try to use this in my actual forms I run into issue. I >> think it is because my data is loaded after the form is loaded. The user is >> presented with a main form that allows them to search for records or load a >> 'template' record into the form. If the data is pre-loaded, the tinyMCE >> editor works, once I select and load a new record, the textarea are >> displayed a regular textareas, not as tinyMCE editors. >> Here is a simplified example: >> https://gist.github.com/wsalesky/bf6b25b50b082c8f0bd8dcf7e7b1eaf2 >> >> Any thoughts on how to solve this issue? Also, many of my textareas that >> I want editable will be in subforms. Not sure if that adds another layer of >> complication or not. >> Thanks! >> -Winona >> >> >> On Sun, Dec 31, 2023 at 8:00 AM Alain Couthures < >> ala...@ag...> wrote: >> >> Hi Winona, >> >> Sorry for the delay. >> >> Please have a look at the tinymce.xml sample ( >> https://github.com/AlainCouthures/declarative4all/blob/master/public/samples/tinymce.xml). >> >> >> Because of compatibility issues between tinymce versions, it is required >> to add data-uri and data-version attributes to allow XSLTForms to properly >> manage the rich text editors. In the sample: >> <script type="text/javascript" src="js/tinymce_4.5.3/tinymce.min.js" >> data-uri="http://www.tinymce.com" data-version="4.5.3">/* */</script> >> >> In next release, XSLTForms will also check "tinymce.majorVersion + '.' + >> tinymce.minorVersion", as suggested by ChatGPT ;-) >> >> After upgrading the repeat test case accordingly, it works as expected >> for me! >> >> Thank you for your feedback! >> >> --Alain >> >> Le 17/12/2023 19:30 CET, Winona Salesky <wsa...@gm...> a écrit : >> >> >> Hi All, >> I'm looking into adding a rich text editor to my textarea's. I was trying >> to experiment with this example: >> http://www.agencexml.com/xsltforms/tinymce.xml >> >> But have had some trouble getting it working. My use case would include >> multiple textarea's almost all of them appearing in a nested repeat >> structure. I found this on the list ( >> https://sourceforge.net/p/xsltforms/mailman/xsltforms-support/thread/A6AB89C8-E8E0-49C3-965F-65464934B94D%40basex.org/#msg30316903) >> which suggests repeats could be a problem. Has this been solved? Has anyone >> integrated a text editor into their XForms? I can mock up a >> simplified example of what I am trying to do if that would be useful, but >> I'm mostly looking for examples for how someone else may have solved this >> issue. >> >> Thanks! >> -Winona >> >> _______________________________________________ Xsltforms-support mailing >> list Xsl...@li... >> https://lists.sourceforge.net/lists/listinfo/xsltforms-support >> >> |
|
From: Winona S. <wsa...@gm...> - 2024-01-03 14:14:04
|
Hi Alain, That did fix the example. Thank you. I think I have misunderstood the use of the XForms binding. So I will do a little research and see if I can get them working correctly on my more complex version of the form, which has the summary element at many different levels in the TEI record. -Winona On Wed, Jan 3, 2024 at 5:13 AM Alain Couthures < ala...@ag...> wrote: > Hi Winona, > > Looking at the simplified example, it appears that the new record does not > have the very same structure: the document root is named "TEI" with a child > named "data" whilst the pre-loaded document has the "data" element as root. > > XForms bindings are context dependant, they are not like XSLT template > match attribute values. > > Whether subforms are used should not interfere with bindings. > > Thank you for your feedback! > > --Alain > > Le 03/01/2024 00:54 CET, Winona Salesky <wsa...@gm...> a écrit : > > > Hi Alain, > This sort of works. Here is an example of multiple text editors working: > https://gist.github.com/wsalesky/00b872cd91c99344a030f0e667cb9e35 > > However, when I try to use this in my actual forms I run into issue. I > think it is because my data is loaded after the form is loaded. The user is > presented with a main form that allows them to search for records or load a > 'template' record into the form. If the data is pre-loaded, the tinyMCE > editor works, once I select and load a new record, the textarea are > displayed a regular textareas, not as tinyMCE editors. > Here is a simplified example: > https://gist.github.com/wsalesky/bf6b25b50b082c8f0bd8dcf7e7b1eaf2 > > Any thoughts on how to solve this issue? Also, many of my textareas that I > want editable will be in subforms. Not sure if that adds another layer of > complication or not. > Thanks! > -Winona > > > On Sun, Dec 31, 2023 at 8:00 AM Alain Couthures < > ala...@ag...> wrote: > > Hi Winona, > > Sorry for the delay. > > Please have a look at the tinymce.xml sample ( > https://github.com/AlainCouthures/declarative4all/blob/master/public/samples/tinymce.xml). > > > Because of compatibility issues between tinymce versions, it is required > to add data-uri and data-version attributes to allow XSLTForms to properly > manage the rich text editors. In the sample: > <script type="text/javascript" src="js/tinymce_4.5.3/tinymce.min.js" > data-uri="http://www.tinymce.com" data-version="4.5.3">/* */</script> > > In next release, XSLTForms will also check "tinymce.majorVersion + '.' + > tinymce.minorVersion", as suggested by ChatGPT ;-) > > After upgrading the repeat test case accordingly, it works as expected for > me! > > Thank you for your feedback! > > --Alain > > Le 17/12/2023 19:30 CET, Winona Salesky <wsa...@gm...> a écrit : > > > Hi All, > I'm looking into adding a rich text editor to my textarea's. I was trying > to experiment with this example: > http://www.agencexml.com/xsltforms/tinymce.xml > > But have had some trouble getting it working. My use case would include > multiple textarea's almost all of them appearing in a nested repeat > structure. I found this on the list ( > https://sourceforge.net/p/xsltforms/mailman/xsltforms-support/thread/A6AB89C8-E8E0-49C3-965F-65464934B94D%40basex.org/#msg30316903) > which suggests repeats could be a problem. Has this been solved? Has anyone > integrated a text editor into their XForms? I can mock up a > simplified example of what I am trying to do if that would be useful, but > I'm mostly looking for examples for how someone else may have solved this > issue. > > Thanks! > -Winona > > _______________________________________________ Xsltforms-support mailing > list Xsl...@li... > https://lists.sourceforge.net/lists/listinfo/xsltforms-support > > |
|
From: Alain C. <ala...@ag...> - 2024-01-03 10:14:14
|
<!doctype html>
<html>
<head>
<meta charset="UTF-8">
</head>
<body>
<div>
Hi Winona,
</div>
<div class="default-style">
</div>
<div class="default-style">
Looking at the simplified example, it appears that the new record does not have the very same structure: the document root is named "TEI" with a child named "data" whilst the pre-loaded document has the "data" element as root.
</div>
<div class="default-style">
</div>
<div class="default-style">
XForms bindings are context dependant, they are not like XSLT template match attribute values.
</div>
<div class="default-style">
</div>
<div class="default-style">
Whether subforms are used should not interfere with bindings.
</div>
<div class="default-style">
</div>
<div class="default-style">
Thank you for your feedback!
</div>
<div class="default-style">
</div>
<div class="default-style">
--Alain
</div>
<blockquote type="cite">
<div>
Le 03/01/2024 00:54 CET, Winona Salesky <wsa...@gm...> a écrit :
</div>
<div>
</div>
<div>
</div>
<div dir="ltr">
Hi Alain,
<div>
This sort of works. Here is an example of multiple text editors working: <a href="https://gist.github.com/wsalesky/00b872cd91c99344a030f0e667cb9e35">https://gist.github.com/wsalesky/00b872cd91c99344a030f0e667cb9e35</a>
</div>
<div>
</div>
<div>
However, when I try to use this in my actual forms I run into issue. I think it is because my data is loaded after the form is loaded. The user is presented with a main form that allows them to search for records or load a 'template' record into the form. If the data is pre-loaded, the tinyMCE editor works, once I select and load a new record, the textarea are displayed a regular textareas, not as tinyMCE editors.
</div>
<div>
Here is a simplified example: <a href="https://gist.github.com/wsalesky/bf6b25b50b082c8f0bd8dcf7e7b1eaf2">https://gist.github.com/wsalesky/bf6b25b50b082c8f0bd8dcf7e7b1eaf2</a>
<br>
<br>Any thoughts on how to solve this issue? Also, many of my textareas that I want editable will be in subforms. Not sure if that adds another layer of complication or not.
</div>
<div>
Thanks!
</div>
<div>
-Winona
</div>
<div>
</div>
</div>
<br>
<div class="gmail_quote">
<div class="gmail_attr" dir="ltr">
On Sun, Dec 31, 2023 at 8:00 AM Alain Couthures <<a href="mailto:ala...@ag...">ala...@ag...</a>> wrote:
</div>
<blockquote>
<u></u>
<div>
<div>
Hi Winona,
</div>
<div>
<div>
</div>
<div>
Sorry for the delay.
</div>
<div>
</div>
</div>
<div>
Please have a look at the tinymce.xml sample (<a href="https://github.com/AlainCouthures/declarative4all/blob/master/public/samples/tinymce.xml)" target="_blank" rel="noopener">https://github.com/AlainCouthures/declarative4all/blob/master/public/samples/tinymce.xml)</a>.
</div>
<div>
</div>
<div>
Because of compatibility issues between tinymce versions, it is required to add data-uri and data-version attributes to allow XSLTForms to properly manage the rich text editors. In the sample:
<br><script type="text/javascript" src="js/tinymce_4.5.3/tinymce.min.js" data-uri="<a href="http://www.tinymce.com" target="_blank" rel="noopener">http://www.tinymce.com</a>" data-version="4.5.3">/* */</script>
</div>
<div>
</div>
<div>
In next release, XSLTForms will also check "tinymce.majorVersion + '.' + tinymce.minorVersion", as suggested by ChatGPT ;-)
</div>
<div>
</div>
<div>
After upgrading the repeat test case accordingly, it works as expected for me!
</div>
<div>
</div>
<div>
Thank you for your feedback!
</div>
<div>
</div>
<div>
--Alain
</div>
<blockquote type="cite">
<div>
Le 17/12/2023 19:30 CET, Winona Salesky <<a href="mailto:wsa...@gm..." target="_blank" rel="noopener">wsa...@gm...</a>> a écrit :
</div>
<div>
</div>
<div>
</div>
<div dir="ltr">
Hi All,
<br>
<div>
I'm looking into adding a rich text editor to my textarea's. I was trying to experiment with this example:
</div>
<div>
<a href="http://www.agencexml.com/xsltforms/tinymce.xml" target="_blank" rel="noopener">http://www.agencexml.com/xsltforms/tinymce.xml</a>
</div>
<div>
</div>
<div>
But have had some trouble getting it working. My use case would include multiple textarea's almost all of them appearing in a nested repeat structure. I found this on the list (<a href="https://sourceforge.net/p/xsltforms/mailman/xsltforms-support/thread/A6AB89C8-E8E0-49C3-965F-65464934B94D%40basex.org/#msg30316903" target="_blank" rel="noopener">https://sourceforge.net/p/xsltforms/mailman/xsltforms-support/thread/A6AB89C8-E8E0-49C3-965F-65464934B94D%40basex.org/#msg30316903</a>) which suggests repeats could be a problem. Has this been solved? Has anyone integrated a text editor into their XForms? I can mock up a simplified example of what I am trying to do if that would be useful, but I'm mostly looking for examples for how someone else may have solved this issue.
</div>
<div>
</div>
<div>
Thanks!
</div>
<div>
-Winona
</div>
<div>
</div>
</div> _______________________________________________ Xsltforms-support mailing list <a href="mailto:Xsl...@li..." target="_blank" rel="noopener">Xsl...@li...</a> <a href="https://lists.sourceforge.net/lists/listinfo/xsltforms-support" target="_blank" rel="noopener">https://lists.sourceforge.net/lists/listinfo/xsltforms-support</a>
</blockquote>
</div>
</blockquote>
</div>
</blockquote>
</body>
</html>
|
|
From: Winona S. <wsa...@gm...> - 2024-01-02 23:54:43
|
Hi Alain, This sort of works. Here is an example of multiple text editors working: https://gist.github.com/wsalesky/00b872cd91c99344a030f0e667cb9e35 However, when I try to use this in my actual forms I run into issue. I think it is because my data is loaded after the form is loaded. The user is presented with a main form that allows them to search for records or load a 'template' record into the form. If the data is pre-loaded, the tinyMCE editor works, once I select and load a new record, the textarea are displayed a regular textareas, not as tinyMCE editors. Here is a simplified example: https://gist.github.com/wsalesky/bf6b25b50b082c8f0bd8dcf7e7b1eaf2 Any thoughts on how to solve this issue? Also, many of my textareas that I want editable will be in subforms. Not sure if that adds another layer of complication or not. Thanks! -Winona On Sun, Dec 31, 2023 at 8:00 AM Alain Couthures < ala...@ag...> wrote: > Hi Winona, > > Sorry for the delay. > > Please have a look at the tinymce.xml sample ( > https://github.com/AlainCouthures/declarative4all/blob/master/public/samples/tinymce.xml). > > > Because of compatibility issues between tinymce versions, it is required > to add data-uri and data-version attributes to allow XSLTForms to properly > manage the rich text editors. In the sample: > <script type="text/javascript" src="js/tinymce_4.5.3/tinymce.min.js" > data-uri="http://www.tinymce.com" data-version="4.5.3">/* */</script> > > In next release, XSLTForms will also check "tinymce.majorVersion + '.' + > tinymce.minorVersion", as suggested by ChatGPT ;-) > > After upgrading the repeat test case accordingly, it works as expected for > me! > > Thank you for your feedback! > > --Alain > > Le 17/12/2023 19:30 CET, Winona Salesky <wsa...@gm...> a écrit : > > > Hi All, > I'm looking into adding a rich text editor to my textarea's. I was trying > to experiment with this example: > http://www.agencexml.com/xsltforms/tinymce.xml > > But have had some trouble getting it working. My use case would include > multiple textarea's almost all of them appearing in a nested repeat > structure. I found this on the list ( > https://sourceforge.net/p/xsltforms/mailman/xsltforms-support/thread/A6AB89C8-E8E0-49C3-965F-65464934B94D%40basex.org/#msg30316903) > which suggests repeats could be a problem. Has this been solved? Has anyone > integrated a text editor into their XForms? I can mock up a > simplified example of what I am trying to do if that would be useful, but > I'm mostly looking for examples for how someone else may have solved this > issue. > > Thanks! > -Winona > > _______________________________________________ Xsltforms-support mailing > list Xsl...@li... > https://lists.sourceforge.net/lists/listinfo/xsltforms-support > > |
|
From: Alain C. <ala...@ag...> - 2023-12-31 13:00:47
|
<!doctype html>
<html>
<head>
<meta charset="UTF-8">
</head>
<body>
<div>
Hi Winona,
</div>
<div class="default-style">
<div class="default-style">
</div>
<div class="default-style">
Sorry for the delay.
</div>
<div class="default-style">
</div>
</div>
<div class="default-style">
Please have a look at the tinymce.xml sample (<a href="https://github.com/AlainCouthures/declarative4all/blob/master/public/samples/tinymce.xml)">https://github.com/AlainCouthures/declarative4all/blob/master/public/samples/tinymce.xml)</a>.
</div>
<div class="default-style">
</div>
<div class="default-style">
Because of compatibility issues between tinymce versions, it is required to add data-uri and data-version attributes to allow XSLTForms to properly manage the rich text editors. In the sample:
<br><script type="text/javascript" src="js/tinymce_4.5.3/tinymce.min.js" data-uri="http://www.tinymce.com" data-version="4.5.3">/* */</script>
</div>
<div class="default-style">
</div>
<div class="default-style">
In next release, XSLTForms will also check "tinymce.<span class="hljs-property">majorVersion</span> + <span class="hljs-string">'.'</span> + tinymce.<span class="hljs-property">minorVersion", as suggested by ChatGPT ;-)</span>
</div>
<div class="default-style">
</div>
<div class="default-style">
<span class="hljs-property">After upgrading the repeat test case accordingly, it works as expected for me!</span>
</div>
<div class="default-style">
</div>
<div class="default-style">
Thank you for your feedback!
</div>
<div class="default-style">
</div>
<div class="default-style">
--Alain
</div>
<blockquote type="cite">
<div>
Le 17/12/2023 19:30 CET, Winona Salesky <wsa...@gm...> a écrit :
</div>
<div>
</div>
<div>
</div>
<div dir="ltr">
Hi All,
<br>
<div>
I'm looking into adding a rich text editor to my textarea's. I was trying to experiment with this example:
</div>
<div>
<a href="http://www.agencexml.com/xsltforms/tinymce.xml">http://www.agencexml.com/xsltforms/tinymce.xml</a>
</div>
<div>
</div>
<div>
But have had some trouble getting it working. My use case would include multiple textarea's almost all of them appearing in a nested repeat structure. I found this on the list (<a href="https://sourceforge.net/p/xsltforms/mailman/xsltforms-support/thread/A6AB89C8-E8E0-49C3-965F-65464934B94D%40basex.org/#msg30316903">https://sourceforge.net/p/xsltforms/mailman/xsltforms-support/thread/A6AB89C8-E8E0-49C3-965F-65464934B94D%40basex.org/#msg30316903</a>) which suggests repeats could be a problem. Has this been solved? Has anyone integrated a text editor into their XForms? I can mock up a simplified example of what I am trying to do if that would be useful, but I'm mostly looking for examples for how someone else may have solved this issue.
</div>
<div>
</div>
<div>
Thanks!
</div>
<div>
-Winona
</div>
<div>
</div>
</div> _______________________________________________ Xsltforms-support mailing list Xsl...@li... https://lists.sourceforge.net/lists/listinfo/xsltforms-support
</blockquote>
</body>
</html>
|
|
From: Winona S. <wsa...@gm...> - 2023-12-17 18:30:38
|
Hi All, I'm looking into adding a rich text editor to my textarea's. I was trying to experiment with this example: http://www.agencexml.com/xsltforms/tinymce.xml But have had some trouble getting it working. My use case would include multiple textarea's almost all of them appearing in a nested repeat structure. I found this on the list ( https://sourceforge.net/p/xsltforms/mailman/xsltforms-support/thread/A6AB89C8-E8E0-49C3-965F-65464934B94D%40basex.org/#msg30316903) which suggests repeats could be a problem. Has this been solved? Has anyone integrated a text editor into their XForms? I can mock up a simplified example of what I am trying to do if that would be useful, but I'm mostly looking for examples for how someone else may have solved this issue. Thanks! -Winona |
|
From: Winona S. <wsa...@gm...> - 2023-12-11 13:03:37
|
Hi Alain,
That is great to hear, I will give it a try. I have also found a CSS
solution that seems to work pretty well:
input {
text-align: start !important;
unicode-bidi: plaintext !important;
}
In terms of dir=auto on other elements I would think labels and outputs
would be the most useful.
Thanks for your continued help!
-Winona
On Sun, Dec 10, 2023 at 6:02 AM Alain Couthures <
ala...@ag...> wrote:
> Hi Winona,
>
> XSLTForms now allows to add HTML attributes to input/textarea elements
> given they are in HTML namespace such as <xf:input ref="."
> html:dir="auto"/>.
>
> Whether dir="auto" should be systematically added by XSLTForms is a good
> question. For inputs, this should be added within Javascript
> XsltForms_input.prototype.initBody() method. Actually, more elements could
> also be considered: labels and outputs, at least.
>
> What do you think?
>
> --Alain
>
> Le 07/12/2023 17:11 CET, Winona Salesky <wsa...@gm...> a écrit :
>
>
> Hi All,
> I need to support both rtl and ltr text input in my forms. Reading up on
> this online, it sounds like the best way to do this is to include the
> following attribute on the input/textarea elements: dir="auto"
>
> What do you think the best way to get this working in XSLTForms is? Edit
> the XSLTForms javascript? Write my own Javascript to amend the output?
> Something else?
>
> Thanks for any thoughts or suggestions.
> -Winona
>
> _______________________________________________ Xsltforms-support mailing
> list Xsl...@li...
> https://lists.sourceforge.net/lists/listinfo/xsltforms-support
>
>
|
|
From: Alain C. <ala...@ag...> - 2023-12-10 11:03:16
|
<!doctype html>
<html>
<head>
<meta charset="UTF-8">
</head>
<body>
<div>
Hi Winona,
</div>
<div class="default-style">
</div>
<div class="default-style">
XSLTForms now allows to add HTML attributes to input/textarea elements given they are in HTML namespace such as <xf:input ref="." html:dir="auto"/>.
</div>
<div class="default-style">
</div>
<div class="default-style">
Whether dir="auto" should be systematically added by XSLTForms is a good question. For inputs, this should be added within Javascript XsltForms_input.prototype.initBody() method. Actually, more elements could also be considered: labels and outputs, at least.
</div>
<div class="default-style">
</div>
<div class="default-style">
What do you think?
</div>
<div class="default-style">
</div>
<div class="default-style">
--Alain
</div>
<blockquote type="cite">
<div>
Le 07/12/2023 17:11 CET, Winona Salesky <wsa...@gm...> a écrit :
</div>
<div>
</div>
<div>
</div>
<div dir="ltr">
Hi All,
<br>
<div>
I need to support both rtl and ltr text input in my forms. Reading up on this online, it sounds like the best way to do this is to include the following attribute on the input/textarea elements: <span class="gmail-hljs-built_in" style="background-color: transparent; font-family: inherit; font-style: inherit; font-variant: inherit; font-weight: inherit; white-space: inherit; color: #0c0d0e; margin: 0px; padding: 0px; border: 0px; font-stretch: inherit; line-height: inherit; font-kerning: inherit; font-feature-settings: inherit; font-size: 13px; vertical-align: baseline; box-sizing: inherit;">dir</span><span style="background-color: transparent; font-family: inherit; font-style: inherit; font-variant-ligatures: inherit; font-variant-caps: inherit; font-weight: inherit; white-space: inherit; color: #0c0d0e;">=</span><span class="gmail-hljs-string" style="background-color: transparent; font-family: inherit; font-style: inherit; font-variant: inherit; font-weight: inherit; white-space: inherit; color: #0c0d0e; margin: 0px; padding: 0px; border: 0px; font-stretch: inherit; line-height: inherit; font-kerning: inherit; font-feature-settings: inherit; font-size: 13px; vertical-align: baseline; box-sizing: inherit;">"auto"</span>
</div>
<div>
<span class="gmail-hljs-string" style="background-color: transparent; font-family: inherit; font-style: inherit; font-variant: inherit; font-weight: inherit; white-space: inherit; color: #0c0d0e; margin: 0px; padding: 0px; border: 0px; font-stretch: inherit; line-height: inherit; font-kerning: inherit; font-feature-settings: inherit; font-size: 13px; vertical-align: baseline; box-sizing: inherit;"> </span>
</div>
<div>
<span class="gmail-hljs-string" style="background-color: transparent; font-family: inherit; font-style: inherit; font-variant: inherit; font-weight: inherit; white-space: inherit; color: #0c0d0e; margin: 0px; padding: 0px; border: 0px; font-stretch: inherit; line-height: inherit; font-kerning: inherit; font-feature-settings: inherit; font-size: 13px; vertical-align: baseline; box-sizing: inherit;">What do you think the best way to get this working in XSLTForms is? Edit the XSLTForms javascript? Write my own Javascript to amend the output? Something else? </span>
</div>
<div>
<span class="gmail-hljs-string" style="background-color: transparent; font-family: inherit; font-style: inherit; font-variant: inherit; font-weight: inherit; white-space: inherit; color: #0c0d0e; margin: 0px; padding: 0px; border: 0px; font-stretch: inherit; line-height: inherit; font-kerning: inherit; font-feature-settings: inherit; font-size: 13px; vertical-align: baseline; box-sizing: inherit;"> </span>
</div>
<div>
<span class="gmail-hljs-string" style="background-color: transparent; font-family: inherit; font-style: inherit; font-variant: inherit; font-weight: inherit; white-space: inherit; color: #0c0d0e; margin: 0px; padding: 0px; border: 0px; font-stretch: inherit; line-height: inherit; font-kerning: inherit; font-feature-settings: inherit; font-size: 13px; vertical-align: baseline; box-sizing: inherit;">Thanks for any thoughts or suggestions. </span>
</div>
<div>
<span class="gmail-hljs-string" style="background-color: transparent; font-family: inherit; font-style: inherit; font-variant: inherit; font-weight: inherit; white-space: inherit; color: #0c0d0e; margin: 0px; padding: 0px; border: 0px; font-stretch: inherit; line-height: inherit; font-kerning: inherit; font-feature-settings: inherit; font-size: 13px; vertical-align: baseline; box-sizing: inherit;">-Winona</span>
</div>
<div>
<span class="gmail-hljs-string" style="background-color: transparent; font-family: inherit; font-style: inherit; font-variant: inherit; font-weight: inherit; white-space: inherit; color: #0c0d0e; margin: 0px; padding: 0px; border: 0px; font-stretch: inherit; line-height: inherit; font-kerning: inherit; font-feature-settings: inherit; font-size: 13px; vertical-align: baseline; box-sizing: inherit;"> </span>
</div>
</div> _______________________________________________ Xsltforms-support mailing list Xsl...@li... https://lists.sourceforge.net/lists/listinfo/xsltforms-support
</blockquote>
</body>
</html>
|
|
From: Winona S. <wsa...@gm...> - 2023-12-07 16:11:41
|
Hi All, I need to support both rtl and ltr text input in my forms. Reading up on this online, it sounds like the best way to do this is to include the following attribute on the input/textarea elements: dir="auto" What do you think the best way to get this working in XSLTForms is? Edit the XSLTForms javascript? Write my own Javascript to amend the output? Something else? Thanks for any thoughts or suggestions. -Winona |
|
From: Alain C. <ala...@ag...> - 2023-11-27 17:46:44
|
<!doctype html>
<html>
<head>
<meta charset="UTF-8">
</head>
<body>
<div>
Hi Mark,
</div>
<div class="default-style">
</div>
<div class="default-style">
Thanks you for this hint: it appears that the drop-down list is only refreshed by an iPad with iPadOS 17.1.1 when the focus on it is lost by the select element.
</div>
<div class="default-style">
</div>
<div class="default-style">
As a workaround, a Javascript blur() call, followed by a delayed focus() call, sounds enough.
</div>
<div class="default-style">
</div>
<div class="default-style">
Are you in a hurry about this fix?
</div>
<div class="default-style">
</div>
<div class="default-style">
--Alain
</div>
<blockquote type="cite">
<div>
Le 21/11/2023 11:14 CET, Mark Seaborne via Xsltforms-support <<a href="mailto:xsl...@li...">xsl...@li...</a>> a écrit :
</div>
<div>
</div>
<div>
</div>
<div>
Hi again,
</div>
<div>
</div>
<div>
I just noticed that if I just run instance() for the node whose value is set by the select1 from the debug command line, the dropdown select1 refreshes and works normally.
</div>
<div>
</div>
<div>
Mark
</div>
<div>
</div>
<blockquote type="cite">
<div>
On 21 Nov 2023, at 09:23, Mark Seaborne <<a href="mailto:m_s...@ma...">m_s...@ma...</a>> wrote:
</div>
<div>
</div>
<div>
Hi,
</div>
<div>
</div>
<div>
I have recently noticed that select1 as a dropdown list doesn't quite work in iPad browsers with XSLTForms 1.7 (using iPadOS 17.1.1).
</div>
<div>
</div>
<div>
Where the node bound to the selected value starts empty, an initial selection works. However, the empty value row of the dropdown list isn't removed after the initial selection, which messes up the mapping between the index of the selected node in the itemset and the selected row of the dropdown list.
</div>
<div>
</div>
<div>
The attached form can be used to demonstrate the problem on an iPad. Interestingly the form works fine on my old iPhone (iOS 15.8).
</div>
<div>
</div>
<div>
My understanding is that all iPad Web browsers are built on WebKit and certainly those that I have tried (Vivaldi and Firefox) show the same behaviour.
</div>
<div>
</div>
<div>
Best wishes
</div>
<div>
</div>
<div>
Mark
</div>
<div>
</div>
<div>
<select1.xml>
</div>
<div>
</div>
<div>
</div>
<div>
</div>
</blockquote>
<div>
</div>
<div>
</div>
<div>
_______________________________________________
</div>
<div>
Xsltforms-support mailing list
</div>
<div>
<a href="mailto:Xsl...@li...">Xsl...@li...</a>
</div>
<div>
<a href="https://lists.sourceforge.net/lists/listinfo/xsltforms-support" target="_blank" rel="noopener">https://lists.sourceforge.net/lists/listinfo/xsltforms-support</a>
</div>
</blockquote>
</body>
</html>
|
|
From: Steven P. <ste...@cw...> - 2023-11-23 21:18:56
|
What you have to realise is that <instance src="..." .../> is done during
XForms initialisation, while other instances are also being initialised. So
if you are depending on the other instances in order to get your values to
initialise an instance, you're going to be in trouble.
What you need to do is allow your static instances to be initialised, and
then initialise your dynamic instances.
You do that with a submission:
<submission id="initfiles" resource="{SearchResultsUrl}"
replace="instance" instance="files"/>
(Or on older XForms systems
<submission id="initfiles" replace="instance" instance="files"><resource
value="SearchResultsUrl"/></submission>
)
and cause this to be done when initialisation is finished:
<action ev:event="xforms-ready">
<send submission="initfiles"/>
</action>
(or the shorter version
<send submission="initfiles" ev:event="xforms-ready"/>
)
Hope this helps.
Steven
On Thursday 23 November 2023 17:15:18 (+01:00), Richard Light wrote:
Thanks, Steven.
Dumb follow-up question: if I have the URL I want to load as a data item,
what syntax do I use in the src attribute to specify that I want to use the
value of that data item as the URL to load? Or do I use ref? This is what
I have:
Whatever syntax I use for line 58, I get an xforms-link-exception when I
load the form. (I'm also trying to prevent the "indexes" instance from
being used until File is specified. That attribute doesn't seem to be
making any difference either.)
Thanks,
Richard
On 22/11/2023 20:28, Steven Pemberton wrote:
Attribute value templates work in XForms too, and allow you to build up a
URL, but you can also use <bind/> with a calculate, see for instance the
section on maps in the XForms advanced tutorial:
http://www.cwi.nl/~steven/xforms/advanced/
Best wishes,
Steven
On Wednesday 22 November 2023 18:18:29 (+01:00), Richard Light wrote:
Hi,
I have an XForms scenario where I am interacting with an API, so every item
of data is fetched via a URL. I want to start with the selection of a file.
That's straightforward, because I can quote the complete URL to get a list
of possible values:
The problem occurs when I then want to include the selected file name in
the URL for the next stage of the query, which is to select the index to
search. This is the sort of thing I would do in XSLT, using an AVT:
What is the equivalent XForms/XsltForms syntax for including an entered
value within a string?
Thanks,
Richard
--
Richard Light
ric...@gm... <mailto:ric...@gm...>
@richardofsussex
--
Richard Light
ric...@gm... <mailto:ric...@gm...>
@richardofsussex |
|
From: Richard L. <ric...@gm...> - 2023-11-23 16:15:39
|
Thanks, Steven. Dumb follow-up question: if I have the URL I want to load as a data item, what syntax do I use in the src attribute to specify that I want to use the /value /of that data item as the URL to load? Or do I use ref? This is what I have: Whatever syntax I use for line 58, I get an xforms-link-exception when I load the form. (I'm also trying to prevent the "indexes" instance from being used until File is specified. That attribute doesn't seem to be making any difference either.) Thanks, Richard On 22/11/2023 20:28, Steven Pemberton wrote: > Attribute value templates work in XForms too, and allow you to build > up a URL, but you can also use <bind/> with a calculate, see for > instance the section on maps in the XForms advanced tutorial: > http://www.cwi.nl/~steven/xforms/advanced/ > > Best wishes, > > Steven > > On Wednesday 22 November 2023 18:18:29 (+01:00), Richard Light wrote: > > Hi, > > I have an XForms scenario where I am interacting with an API, so > every item of data is fetched via a URL. I want to start with the > selection of a file. That's straightforward, because I can quote > the complete URL to get a list of possible values: > > The problem occurs when I then want to include the selected file > name in the URL for the next stage of the query, which is to > select the index to search. This is the sort of thing I would do > in XSLT, using an AVT: > > What is the equivalent XForms/XsltForms syntax for including an > entered value within a string? > > Thanks, > > Richard > > -- > ------------------------------------------------------------------------ > *Richard Light* > ric...@gm... > /@richardofsussex/ > -- ------------------------------------------------------------------------ *Richard Light* ric...@gm... /@richardofsussex/ |
|
From: Steven P. <ste...@cw...> - 2023-11-22 20:44:42
|
Attribute value templates work in XForms too, and allow you to build up a URL, but you can also use <bind/> with a calculate, see for instance the section on maps in the XForms advanced tutorial: http://www.cwi.nl/~steven/xforms/advanced/ Best wishes, Steven On Wednesday 22 November 2023 18:18:29 (+01:00), Richard Light wrote: Hi, I have an XForms scenario where I am interacting with an API, so every item of data is fetched via a URL. I want to start with the selection of a file. That's straightforward, because I can quote the complete URL to get a list of possible values: The problem occurs when I then want to include the selected file name in the URL for the next stage of the query, which is to select the index to search. This is the sort of thing I would do in XSLT, using an AVT: What is the equivalent XForms/XsltForms syntax for including an entered value within a string? Thanks, Richard -- Richard Light ric...@gm... <mailto:ric...@gm...> @richardofsussex |
97 messages has been excluded from this view by a project administrator.
