xsltforms-support Mailing List for XSLTForms (Page 22)
Brought to you by:
alain-couthures
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...> - 2015-05-26 20:06:13
|
Hello Kristian, Converting HTML into XHTML is not very difficult and I have already coded this in Javascript sometimes ago. After that, the parse() XPath function can be used to integrate the result from the RTE into an instance. Please don't hesitate to contact me back if you need this after all. --Alain Le 21/05/2015 21:38, Kristian Kankainen a écrit : > I now removed the TinyMCE fields from my production code and moved it > to a development branch. Thus it is unclear when I can give you > further feedback. Since the html I got from the tinymce editor isn't > xhtml I need to solve the problem of having html as textual data in my > xml. Right now I got tired of the problem and reverted back to pure > text instead. The text get's converted into <p>aragraphs in my xml > database, thus searching for example a string in the second paragraph > is easily done with XPath. With the html it became a nightmare :( > > If anyone has good pointers for best practices on handling (non-xml) > html inside xml, I'm eager to read and learn. > > Thank you very much, Alain. I will try to get back to TinyMCE, it > would help my users but now it seriously impacted and started to tear > on my XRX design. > > Kristian > > 19.05.2015 23:14, Alain Couthures kirjutas: >> Hello Kristian, >> >> I think that I have just found a workaround for the getContent() >> issue with TinyMCE4 when adding a line: I have added a test to avoid >> useless setContent() call when value is actually unchanged... >> >> Please have a look at latest revision (rev.615). >> >> Thank you for your feedback! >> >> --Alain >> >> Le 19/05/2015 10:12, Kristian Kankainen a écrit : >>> The thing that irritate me the most with these bogus elements, is >>> that they seem not be valid according to my TinyMCE settings. Since >>> I keep getting <br> instead of <br /> I can't parse the input as XML. >>> >>> My current solution is to delete (in the serialised string) the >>> bogus elements, convert <br> to <br/> and then parse the (hopefully >>> valid) xml and delete all the rest of the @data-mce* attributes. >>> >>> This is very fragile and I would insist in using the API method >>> since that is what it is there for... What is the major issue using >>> it in XSLTForms? Looking at the TinyMCE4 API documentation it >>> doesn't seem to have changed and is still the supposed way of >>> getting "clean" content from the editor. >>> >>> Kristian >>> >>> 18.05.2015 23:26, Alain Couthures kirjutas: >>>> Hello Kristian, >>>> >>>> This forum post seems too old to be related to TinyMCE4. With >>>> TinyMCE3, the getContent() method worked perfectly for each event >>>> that XSLTForms has to capture. Unfortunately, with TinyMCE4, there >>>> is a major issue using this method as soon as a new line is entered... >>>> >>>> That is why I had to search for an alternative solution and the >>>> innerHTML property seems good enough except for some extra >>>> attributes that you have noticed. Do you think that some regular >>>> expression could remove them? >>>> >>>> --Alain >>>> >>>> Le 14/05/2015 23:39, Kristian Kankainen a écrit : >>>>> Hello again! >>>>> >>>>> Okey, I now understood and accepted that the content has to be >>>>> serialized. But I now get un-clean input from the TinyMCE equipped >>>>> fields. >>>>> >>>>> I get (serialized) <br data-mce-bogus="1"> elements saved in my >>>>> database. I understand TinyMCE uses these elements internally so >>>>> that users can put the cursor inside empty elements when clicking. >>>>> But these bogus elements should be automatically cleaned away >>>>> before the form data gets sent to the server! >>>>> Reading the whole thread about the problem, this post [1] by the >>>>> main developer says that: >>>>>> Use the proper API:s tinymce.activeEditor.getContent() or save >>>>>> etc. Raw HTML should never be stored or extracted. TinyMCE never >>>>>> produces any internal data-mce-bogus output if you use our >>>>>> methods for content extraction. >>>>> >>>>> Could this be the problem in XSLTForms, that the proper API isn't >>>>> used? I'm sorry I can't look at the code myself. This is my >>>>> TinyMCE config in XSLTForms: >>>>>> <schema xmlns="http://www.w3.org/2001/XMLSchema" >>>>>> targetNamespace="http://www.agencexml.com/xsltforms/rte"> >>>>>> <simpleType name="standardHTML"> >>>>>> <restriction base="xf:HTMLFragment" >>>>>> xsltforms:rte="TinyMCE"/> >>>>>> <annotation> >>>>>> <appinfo> >>>>>> { >>>>>> element_format : "xhtml", >>>>>> browser_spellcheck: true, >>>>>> entity_encoding: "numeric", >>>>>> cleanup: true, >>>>>> plugins: [ >>>>>> "autolink lists link charmap", >>>>>> "searchreplace code fullscreen", >>>>>> "insertdatetime paste" >>>>>> ], >>>>>> toolbar: "undo redo | bold italic underline | >>>>>> alignleft aligncenter alignright alignjustify | bullist numlist >>>>>> outdent indent | link | charmap", >>>>>> statusbar : false >>>>>> } >>>>>> </appinfo> >>>>>> </annotation> >>>>>> </simpleType> >>>>>> </schema> >>>>> I use version 4.1.9 of TinyMCE and I think the XSLTForms code is >>>>> version 614. >>>>> >>>>> Can I send some more information for reproducing this? >>>>> >>>>> Thank you in advance >>>>> Kristian K >>>>> >>>>> [1] http://www.tinymce.com/forum/viewtopic.php?pid=109291#p109291 >>>>> >>>> >>> >> > |
From: Kristian K. <kri...@ek...> - 2015-05-21 19:38:44
|
I now removed the TinyMCE fields from my production code and moved it to a development branch. Thus it is unclear when I can give you further feedback. Since the html I got from the tinymce editor isn't xhtml I need to solve the problem of having html as textual data in my xml. Right now I got tired of the problem and reverted back to pure text instead. The text get's converted into <p>aragraphs in my xml database, thus searching for example a string in the second paragraph is easily done with XPath. With the html it became a nightmare :( If anyone has good pointers for best practices on handling (non-xml) html inside xml, I'm eager to read and learn. Thank you very much, Alain. I will try to get back to TinyMCE, it would help my users but now it seriously impacted and started to tear on my XRX design. Kristian 19.05.2015 23:14, Alain Couthures kirjutas: > Hello Kristian, > > I think that I have just found a workaround for the getContent() issue > with TinyMCE4 when adding a line: I have added a test to avoid useless > setContent() call when value is actually unchanged... > > Please have a look at latest revision (rev.615). > > Thank you for your feedback! > > --Alain > > Le 19/05/2015 10:12, Kristian Kankainen a écrit : >> The thing that irritate me the most with these bogus elements, is >> that they seem not be valid according to my TinyMCE settings. Since I >> keep getting <br> instead of <br /> I can't parse the input as XML. >> >> My current solution is to delete (in the serialised string) the bogus >> elements, convert <br> to <br/> and then parse the (hopefully valid) >> xml and delete all the rest of the @data-mce* attributes. >> >> This is very fragile and I would insist in using the API method since >> that is what it is there for... What is the major issue using it in >> XSLTForms? Looking at the TinyMCE4 API documentation it doesn't seem >> to have changed and is still the supposed way of getting "clean" >> content from the editor. >> >> Kristian >> >> 18.05.2015 23:26, Alain Couthures kirjutas: >>> Hello Kristian, >>> >>> This forum post seems too old to be related to TinyMCE4. With >>> TinyMCE3, the getContent() method worked perfectly for each event >>> that XSLTForms has to capture. Unfortunately, with TinyMCE4, there >>> is a major issue using this method as soon as a new line is entered... >>> >>> That is why I had to search for an alternative solution and the >>> innerHTML property seems good enough except for some extra >>> attributes that you have noticed. Do you think that some regular >>> expression could remove them? >>> >>> --Alain >>> >>> Le 14/05/2015 23:39, Kristian Kankainen a écrit : >>>> Hello again! >>>> >>>> Okey, I now understood and accepted that the content has to be >>>> serialized. But I now get un-clean input from the TinyMCE equipped >>>> fields. >>>> >>>> I get (serialized) <br data-mce-bogus="1"> elements saved in my >>>> database. I understand TinyMCE uses these elements internally so >>>> that users can put the cursor inside empty elements when clicking. >>>> But these bogus elements should be automatically cleaned away >>>> before the form data gets sent to the server! >>>> Reading the whole thread about the problem, this post [1] by the >>>> main developer says that: >>>>> Use the proper API:s tinymce.activeEditor.getContent() or save >>>>> etc. Raw HTML should never be stored or extracted. TinyMCE never >>>>> produces any internal data-mce-bogus output if you use our methods >>>>> for content extraction. >>>> >>>> Could this be the problem in XSLTForms, that the proper API isn't >>>> used? I'm sorry I can't look at the code myself. This is my TinyMCE >>>> config in XSLTForms: >>>>> <schema xmlns="http://www.w3.org/2001/XMLSchema" >>>>> targetNamespace="http://www.agencexml.com/xsltforms/rte"> >>>>> <simpleType name="standardHTML"> >>>>> <restriction base="xf:HTMLFragment" >>>>> xsltforms:rte="TinyMCE"/> >>>>> <annotation> >>>>> <appinfo> >>>>> { >>>>> element_format : "xhtml", >>>>> browser_spellcheck: true, >>>>> entity_encoding: "numeric", >>>>> cleanup: true, >>>>> plugins: [ >>>>> "autolink lists link charmap", >>>>> "searchreplace code fullscreen", >>>>> "insertdatetime paste" >>>>> ], >>>>> toolbar: "undo redo | bold italic underline | >>>>> alignleft aligncenter alignright alignjustify | bullist numlist >>>>> outdent indent | link | charmap", >>>>> statusbar : false >>>>> } >>>>> </appinfo> >>>>> </annotation> >>>>> </simpleType> >>>>> </schema> >>>> I use version 4.1.9 of TinyMCE and I think the XSLTForms code is >>>> version 614. >>>> >>>> Can I send some more information for reproducing this? >>>> >>>> Thank you in advance >>>> Kristian K >>>> >>>> [1] http://www.tinymce.com/forum/viewtopic.php?pid=109291#p109291 >>>> >>> >> > |
From: Alain C. <ala...@ag...> - 2015-05-19 20:14:25
|
Hello Kristian, I think that I have just found a workaround for the getContent() issue with TinyMCE4 when adding a line: I have added a test to avoid useless setContent() call when value is actually unchanged... Please have a look at latest revision (rev.615). Thank you for your feedback! --Alain Le 19/05/2015 10:12, Kristian Kankainen a écrit : > The thing that irritate me the most with these bogus elements, is that > they seem not be valid according to my TinyMCE settings. Since I keep > getting <br> instead of <br /> I can't parse the input as XML. > > My current solution is to delete (in the serialised string) the bogus > elements, convert <br> to <br/> and then parse the (hopefully valid) > xml and delete all the rest of the @data-mce* attributes. > > This is very fragile and I would insist in using the API method since > that is what it is there for... What is the major issue using it in > XSLTForms? Looking at the TinyMCE4 API documentation it doesn't seem > to have changed and is still the supposed way of getting "clean" > content from the editor. > > Kristian > > 18.05.2015 23:26, Alain Couthures kirjutas: >> Hello Kristian, >> >> This forum post seems too old to be related to TinyMCE4. With >> TinyMCE3, the getContent() method worked perfectly for each event >> that XSLTForms has to capture. Unfortunately, with TinyMCE4, there is >> a major issue using this method as soon as a new line is entered... >> >> That is why I had to search for an alternative solution and the >> innerHTML property seems good enough except for some extra attributes >> that you have noticed. Do you think that some regular expression >> could remove them? >> >> --Alain >> >> Le 14/05/2015 23:39, Kristian Kankainen a écrit : >>> Hello again! >>> >>> Okey, I now understood and accepted that the content has to be >>> serialized. But I now get un-clean input from the TinyMCE equipped >>> fields. >>> >>> I get (serialized) <br data-mce-bogus="1"> elements saved in my >>> database. I understand TinyMCE uses these elements internally so >>> that users can put the cursor inside empty elements when clicking. >>> But these bogus elements should be automatically cleaned away before >>> the form data gets sent to the server! >>> Reading the whole thread about the problem, this post [1] by the >>> main developer says that: >>>> Use the proper API:s tinymce.activeEditor.getContent() or save etc. >>>> Raw HTML should never be stored or extracted. TinyMCE never >>>> produces any internal data-mce-bogus output if you use our methods >>>> for content extraction. >>> >>> Could this be the problem in XSLTForms, that the proper API isn't >>> used? I'm sorry I can't look at the code myself. This is my TinyMCE >>> config in XSLTForms: >>>> <schema xmlns="http://www.w3.org/2001/XMLSchema" >>>> targetNamespace="http://www.agencexml.com/xsltforms/rte"> >>>> <simpleType name="standardHTML"> >>>> <restriction base="xf:HTMLFragment" xsltforms:rte="TinyMCE"/> >>>> <annotation> >>>> <appinfo> >>>> { >>>> element_format : "xhtml", >>>> browser_spellcheck: true, >>>> entity_encoding: "numeric", >>>> cleanup: true, >>>> plugins: [ >>>> "autolink lists link charmap", >>>> "searchreplace code fullscreen", >>>> "insertdatetime paste" >>>> ], >>>> toolbar: "undo redo | bold italic underline | >>>> alignleft aligncenter alignright alignjustify | bullist numlist >>>> outdent indent | link | charmap", >>>> statusbar : false >>>> } >>>> </appinfo> >>>> </annotation> >>>> </simpleType> >>>> </schema> >>> I use version 4.1.9 of TinyMCE and I think the XSLTForms code is >>> version 614. >>> >>> Can I send some more information for reproducing this? >>> >>> Thank you in advance >>> Kristian K >>> >>> [1] http://www.tinymce.com/forum/viewtopic.php?pid=109291#p109291 >>> >> > |
From: Kristian K. <kri...@ek...> - 2015-05-19 11:56:57
|
The thing that irritate me the most with these bogus elements, is that they seem not be valid according to my TinyMCE settings. Since I keep getting <br> instead of <br /> I can't parse the input as XML. My current solution is to delete (in the serialised string) the bogus elements, convert <br> to <br/> and then parse the (hopefully valid) xml and delete all the rest of the @data-mce* attributes. This is very fragile and I would insist in using the API method since that is what it is there for... What is the major issue using it in XSLTForms? Looking at the TinyMCE4 API documentation it doesn't seem to have changed and is still the supposed way of getting "clean" content from the editor. Kristian 18.05.2015 23:26, Alain Couthures kirjutas: > Hello Kristian, > > This forum post seems too old to be related to TinyMCE4. With > TinyMCE3, the getContent() method worked perfectly for each event that > XSLTForms has to capture. Unfortunately, with TinyMCE4, there is a > major issue using this method as soon as a new line is entered... > > That is why I had to search for an alternative solution and the > innerHTML property seems good enough except for some extra attributes > that you have noticed. Do you think that some regular expression could > remove them? > > --Alain > > Le 14/05/2015 23:39, Kristian Kankainen a écrit : >> Hello again! >> >> Okey, I now understood and accepted that the content has to be >> serialized. But I now get un-clean input from the TinyMCE equipped >> fields. >> >> I get (serialized) <br data-mce-bogus="1"> elements saved in my >> database. I understand TinyMCE uses these elements internally so that >> users can put the cursor inside empty elements when clicking. But >> these bogus elements should be automatically cleaned away before the >> form data gets sent to the server! >> Reading the whole thread about the problem, this post [1] by the main >> developer says that: >>> Use the proper API:s tinymce.activeEditor.getContent() or save etc. >>> Raw HTML should never be stored or extracted. TinyMCE never produces >>> any internal data-mce-bogus output if you use our methods for >>> content extraction. >> >> Could this be the problem in XSLTForms, that the proper API isn't >> used? I'm sorry I can't look at the code myself. This is my TinyMCE >> config in XSLTForms: >>> <schema xmlns="http://www.w3.org/2001/XMLSchema" >>> targetNamespace="http://www.agencexml.com/xsltforms/rte"> >>> <simpleType name="standardHTML"> >>> <restriction base="xf:HTMLFragment" xsltforms:rte="TinyMCE"/> >>> <annotation> >>> <appinfo> >>> { >>> element_format : "xhtml", >>> browser_spellcheck: true, >>> entity_encoding: "numeric", >>> cleanup: true, >>> plugins: [ >>> "autolink lists link charmap", >>> "searchreplace code fullscreen", >>> "insertdatetime paste" >>> ], >>> toolbar: "undo redo | bold italic underline | >>> alignleft aligncenter alignright alignjustify | bullist numlist >>> outdent indent | link | charmap", >>> statusbar : false >>> } >>> </appinfo> >>> </annotation> >>> </simpleType> >>> </schema> >> I use version 4.1.9 of TinyMCE and I think the XSLTForms code is >> version 614. >> >> Can I send some more information for reproducing this? >> >> Thank you in advance >> Kristian K >> >> [1] http://www.tinymce.com/forum/viewtopic.php?pid=109291#p109291 >> > |
From: Alain C. <ala...@ag...> - 2015-05-18 20:26:39
|
Hello Kristian, This forum post seems too old to be related to TinyMCE4. With TinyMCE3, the getContent() method worked perfectly for each event that XSLTForms has to capture. Unfortunately, with TinyMCE4, there is a major issue using this method as soon as a new line is entered... That is why I had to search for an alternative solution and the innerHTML property seems good enough except for some extra attributes that you have noticed. Do you think that some regular expression could remove them? --Alain Le 14/05/2015 23:39, Kristian Kankainen a écrit : > Hello again! > > Okey, I now understood and accepted that the content has to be > serialized. But I now get un-clean input from the TinyMCE equipped fields. > > I get (serialized) <br data-mce-bogus="1"> elements saved in my > database. I understand TinyMCE uses these elements internally so that > users can put the cursor inside empty elements when clicking. But > these bogus elements should be automatically cleaned away before the > form data gets sent to the server! > Reading the whole thread about the problem, this post [1] by the main > developer says that: >> Use the proper API:s tinymce.activeEditor.getContent() or save etc. >> Raw HTML should never be stored or extracted. TinyMCE never produces >> any internal data-mce-bogus output if you use our methods for content >> extraction. > > Could this be the problem in XSLTForms, that the proper API isn't > used? I'm sorry I can't look at the code myself. This is my TinyMCE > config in XSLTForms: >> <schema xmlns="http://www.w3.org/2001/XMLSchema" >> targetNamespace="http://www.agencexml.com/xsltforms/rte"> >> <simpleType name="standardHTML"> >> <restriction base="xf:HTMLFragment" xsltforms:rte="TinyMCE"/> >> <annotation> >> <appinfo> >> { >> element_format : "xhtml", >> browser_spellcheck: true, >> entity_encoding: "numeric", >> cleanup: true, >> plugins: [ >> "autolink lists link charmap", >> "searchreplace code fullscreen", >> "insertdatetime paste" >> ], >> toolbar: "undo redo | bold italic underline | >> alignleft aligncenter alignright alignjustify | bullist numlist >> outdent indent | link | charmap", >> statusbar : false >> } >> </appinfo> >> </annotation> >> </simpleType> >> </schema> > I use version 4.1.9 of TinyMCE and I think the XSLTForms code is > version 614. > > Can I send some more information for reproducing this? > > Thank you in advance > Kristian K > > [1] http://www.tinymce.com/forum/viewtopic.php?pid=109291#p109291 > |
From: Kristian K. <kri...@ek...> - 2015-05-14 21:39:37
|
Hello again! Okey, I now understood and accepted that the content has to be serialized. But I now get un-clean input from the TinyMCE equipped fields. I get (serialized) <br data-mce-bogus="1"> elements saved in my database. I understand TinyMCE uses these elements internally so that users can put the cursor inside empty elements when clicking. But these bogus elements should be automatically cleaned away before the form data gets sent to the server! Reading the whole thread about the problem, this post [1] by the main developer says that: > Use the proper API:s tinymce.activeEditor.getContent() or save etc. > Raw HTML should never be stored or extracted. TinyMCE never produces > any internal data-mce-bogus output if you use our methods for content > extraction. Could this be the problem in XSLTForms, that the proper API isn't used? I'm sorry I can't look at the code myself. This is my TinyMCE config in XSLTForms: > <schema xmlns="http://www.w3.org/2001/XMLSchema" > targetNamespace="http://www.agencexml.com/xsltforms/rte"> > <simpleType name="standardHTML"> > <restriction base="xf:HTMLFragment" xsltforms:rte="TinyMCE"/> > <annotation> > <appinfo> > { > element_format : "xhtml", > browser_spellcheck: true, > entity_encoding: "numeric", > cleanup: true, > plugins: [ > "autolink lists link charmap", > "searchreplace code fullscreen", > "insertdatetime paste" > ], > toolbar: "undo redo | bold italic underline | > alignleft aligncenter alignright alignjustify | bullist numlist > outdent indent | link | charmap", > statusbar : false > } > </appinfo> > </annotation> > </simpleType> > </schema> I use version 4.1.9 of TinyMCE and I think the XSLTForms code is version 614. Can I send some more information for reproducing this? Thank you in advance Kristian K [1] http://www.tinymce.com/forum/viewtopic.php?pid=109291#p109291 06.05.2015 22:39, Alain Couthures kirjutas: > Hello Kristian, > > Could you please post an explicit test case? Textarea content should > be a serialization (with < and >), not effective tags (with < > and >). > > Regards, > > --Alain > > Le 05/05/2015 08:39, Kristian Kankainen a écrit : >> Thank you Alain! >> >> I got it working now with the latest code from the repository and the >> latest stable tinymce. >> >> What I don't understand is why TinyMCE doesn't interpret the <p> tags >> I have in my nodeset that is bound to the textarea? >> >> The XML is read in to the instance using <xforms:instance >> src="myfile.xml"> and looking at the element that the nodeset bound >> to TinyMCE it does include several <p> elements, but only the text >> nodes are copied to the editor. Is this because of XPath and how >> should I get around it? >> >> All the best wishes >> Kristian >> >> 04.05.2015 20:47, Alain Couthures kirjutas: >>> Hello Kristian, >>> >>> I will add a supported version of TinyMCE in repositories soon. >>> >>> If you look at source of >>> http://www.agencexml.com/xsltforms/tinymce.xml, you will see this line: >>> >>> <script type="text/javascript" >>> src="xsltforms/scripts/tinymce_4.0.21/tinymce.min.js >>> <http://www.agencexml.com/xsltforms/xsltforms/scripts/tinymce_4.0.21/tinymce.min.js>" >>> data-uri="http://www.tinymce.com" data-version="4.0.21">/* */</script> >>> >>> I am confident that latest TinyMCE version should work with >>> XSLTForms as 4.0.21 does. >>> >>> Thank you for your feedback! >>> >>> --Alain >>> >>> Le 04/05/2015 07:54, Kristian Kankainen a écrit : >>>> Hello! >>>> >>>> I wanted to try out TinyMCE but I can't find the new version in the >>>> repositories. I have struggled quite some hours now going through the >>>> files I get from Git clone and SVN checkout of the SourceForge >>>> repository[1]. Still I can't find anything else than version 3.4.6 of >>>> TinyMCE. I also set up the tXs building system and built the three main >>>> components but this didn't do the trick, obviously perhaps. >>>> >>>> How can I find the latest build in the source repository? >>>> >>>> Greetings >>>> Kristian K >>>> >>>> [1]http://sourceforge.net/p/xsltforms/code/ci/master/tree/ and >>>> http://sourceforge.net/p/xsltforms/svn/HEAD/tree/ >>>> >>>> >>> >> > |
From: Alain C. <ala...@ag...> - 2015-05-06 19:39:29
|
Hello Kristian, Could you please post an explicit test case? Textarea content should be a serialization (with < and >), not effective tags (with < and >). Regards, --Alain Le 05/05/2015 08:39, Kristian Kankainen a écrit : > Thank you Alain! > > I got it working now with the latest code from the repository and the > latest stable tinymce. > > What I don't understand is why TinyMCE doesn't interpret the <p> tags > I have in my nodeset that is bound to the textarea? > > The XML is read in to the instance using <xforms:instance > src="myfile.xml"> and looking at the element that the nodeset bound to > TinyMCE it does include several <p> elements, but only the text nodes > are copied to the editor. Is this because of XPath and how should I > get around it? > > All the best wishes > Kristian > > 04.05.2015 20:47, Alain Couthures kirjutas: >> Hello Kristian, >> >> I will add a supported version of TinyMCE in repositories soon. >> >> If you look at source of >> http://www.agencexml.com/xsltforms/tinymce.xml, you will see this line: >> >> <script type="text/javascript" >> src="xsltforms/scripts/tinymce_4.0.21/tinymce.min.js >> <http://www.agencexml.com/xsltforms/xsltforms/scripts/tinymce_4.0.21/tinymce.min.js>" >> data-uri="http://www.tinymce.com" data-version="4.0.21">/* */</script> >> >> I am confident that latest TinyMCE version should work with XSLTForms >> as 4.0.21 does. >> >> Thank you for your feedback! >> >> --Alain >> >> Le 04/05/2015 07:54, Kristian Kankainen a écrit : >>> Hello! >>> >>> I wanted to try out TinyMCE but I can't find the new version in the >>> repositories. I have struggled quite some hours now going through the >>> files I get from Git clone and SVN checkout of the SourceForge >>> repository[1]. Still I can't find anything else than version 3.4.6 of >>> TinyMCE. I also set up the tXs building system and built the three main >>> components but this didn't do the trick, obviously perhaps. >>> >>> How can I find the latest build in the source repository? >>> >>> Greetings >>> Kristian K >>> >>> [1]http://sourceforge.net/p/xsltforms/code/ci/master/tree/ and >>> http://sourceforge.net/p/xsltforms/svn/HEAD/tree/ >>> >>> >> > |
From: Kristian K. <kri...@ek...> - 2015-05-05 06:39:23
|
Thank you Alain! I got it working now with the latest code from the repository and the latest stable tinymce. What I don't understand is why TinyMCE doesn't interpret the <p> tags I have in my nodeset that is bound to the textarea? The XML is read in to the instance using <xforms:instance src="myfile.xml"> and looking at the element that the nodeset bound to TinyMCE it does include several <p> elements, but only the text nodes are copied to the editor. Is this because of XPath and how should I get around it? All the best wishes Kristian 04.05.2015 20:47, Alain Couthures kirjutas: > Hello Kristian, > > I will add a supported version of TinyMCE in repositories soon. > > If you look at source of > http://www.agencexml.com/xsltforms/tinymce.xml, you will see this line: > > <script type="text/javascript" > src="xsltforms/scripts/tinymce_4.0.21/tinymce.min.js > <http://www.agencexml.com/xsltforms/xsltforms/scripts/tinymce_4.0.21/tinymce.min.js>" > data-uri="http://www.tinymce.com" data-version="4.0.21">/* */</script> > > I am confident that latest TinyMCE version should work with XSLTForms > as 4.0.21 does. > > Thank you for your feedback! > > --Alain > > Le 04/05/2015 07:54, Kristian Kankainen a écrit : >> Hello! >> >> I wanted to try out TinyMCE but I can't find the new version in the >> repositories. I have struggled quite some hours now going through the >> files I get from Git clone and SVN checkout of the SourceForge >> repository[1]. Still I can't find anything else than version 3.4.6 of >> TinyMCE. I also set up the tXs building system and built the three main >> components but this didn't do the trick, obviously perhaps. >> >> How can I find the latest build in the source repository? >> >> Greetings >> Kristian K >> >> [1]http://sourceforge.net/p/xsltforms/code/ci/master/tree/ and >> http://sourceforge.net/p/xsltforms/svn/HEAD/tree/ >> >> > |
From: Alain C. <ala...@ag...> - 2015-05-04 17:47:58
|
Hello Kristian, I will add a supported version of TinyMCE in repositories soon. If you look at source of http://www.agencexml.com/xsltforms/tinymce.xml, you will see this line: <script type="text/javascript" src="xsltforms/scripts/tinymce_4.0.21/tinymce.min.js <http://www.agencexml.com/xsltforms/xsltforms/scripts/tinymce_4.0.21/tinymce.min.js>" data-uri="http://www.tinymce.com" data-version="4.0.21">/* */</script> I am confident that latest TinyMCE version should work with XSLTForms as 4.0.21 does. Thank you for your feedback! --Alain Le 04/05/2015 07:54, Kristian Kankainen a écrit : > Hello! > > I wanted to try out TinyMCE but I can't find the new version in the > repositories. I have struggled quite some hours now going through the > files I get from Git clone and SVN checkout of the SourceForge > repository[1]. Still I can't find anything else than version 3.4.6 of > TinyMCE. I also set up the tXs building system and built the three main > components but this didn't do the trick, obviously perhaps. > > How can I find the latest build in the source repository? > > Greetings > Kristian K > > [1] http://sourceforge.net/p/xsltforms/code/ci/master/tree/ and > http://sourceforge.net/p/xsltforms/svn/HEAD/tree/ > > |
From: Kristian K. <kri...@ek...> - 2015-05-04 05:54:58
|
Hello! I wanted to try out TinyMCE but I can't find the new version in the repositories. I have struggled quite some hours now going through the files I get from Git clone and SVN checkout of the SourceForge repository[1]. Still I can't find anything else than version 3.4.6 of TinyMCE. I also set up the tXs building system and built the three main components but this didn't do the trick, obviously perhaps. How can I find the latest build in the source repository? Greetings Kristian K [1] http://sourceforge.net/p/xsltforms/code/ci/master/tree/ and http://sourceforge.net/p/xsltforms/svn/HEAD/tree/ 25.03.2015 22:53, Alain Couthures kirjutas: > Hello Mark, > > I have now added support for TinyMCE 4.X in latest build on source > repositories and I have updated www.agencexml.com accordingly. > > Thank you for your feed back! > > --Alain > > Le 24/03/2015 12:14, Mark Barratt a écrit : >> Apologies if the following reflects the fact that I don’t follow this list closely. >> >> Returning to xsltforms to update an old site, I find that TinyMCE in our site is very broken, and the example at http://www.agencexml.com/xsltforms/tinymce.xml (r595) shows the same symptoms. The first carriage return generates an extra <p> </p> and each subsequent keystroke generates the character keyed together with a <p> tag. This is true in Safari, Chrome and Firefox. >> >> This doesn’t seem to be in the issues list in GitHub or SourceForge (which is canonical?). >> >> Thanks for any help. >> >> -- >> Mark Barratt >> >> ------------------------------------------------------------------------------ >> Dive into the World of Parallel Programming The Go Parallel Website, sponsored >> by Intel and developed in partnership with Slashdot Media, is your hub for all >> things parallel software development, from weekly thought leadership blogs to >> news, videos, case studies, tutorials and more. Take a look and join the >> conversation now. http://goparallel.sourceforge.net/ >> _______________________________________________ >> Xsltforms-support mailing list >> Xsl...@li... >> https://lists.sourceforge.net/lists/listinfo/xsltforms-support > > ------------------------------------------------------------------------------ > Dive into the World of Parallel Programming The Go Parallel Website, sponsored > by Intel and developed in partnership with Slashdot Media, is your hub for all > things parallel software development, from weekly thought leadership blogs to > news, videos, case studies, tutorials and more. Take a look and join the > conversation now. http://goparallel.sourceforge.net/ > _______________________________________________ > Xsltforms-support mailing list > Xsl...@li... > https://lists.sourceforge.net/lists/listinfo/xsltforms-support > |
From: Kristian K. <kri...@ek...> - 2015-04-20 13:56:35
|
Hello! I recently tried and failed setting up a working XSLTForms environment using the client-side javascript XSLT 2.0 engine SaxonCE [1]. Sorry for not describing my case further, but I would be interested in finding people trying the same thing first. Has anyone tried? Succeeded? Cheers Kristian Kankainen [1] http://www.saxonica.com/ce/user-doc/1.1/ |
From: Alain C. <ala...@ag...> - 2015-04-19 16:34:21
|
Hi Mats! Please have a look at my own test case: <html xmlns:xf="http://www.w3.org/2002/xforms" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://www.w3.org/1999/xhtml" xmlns:xhtml="http://www.w3.org/1999/xhtml" xmlns:ev="http://www.w3.org/2001/xml-events" xmlns:xsd="http://www.w3.org/2001/XMLSchema"> <head> <title>Last upload</title> <xf:model> <xf:instance xmlns=""> <data> <files> <file xsi:type="xsd:hexBinary"/> <file xsi:type="xsd:hexBinary"/> </files> </data> </xf:instance> </xf:model> </head> <body> <xf:upload ref="files/file[last()]" incremental="true"> <xf:label>Upload: </xf:label> <xf:insert ev:event="xforms-value-changed" ref="../file" position="after" origin="../file[1]"/> </xf:upload> <br/> <xf:repeat ref="files/file"> <xf:output value="position()"/> <xf:output value="."> <xf:label> Value: </xf:label> </xf:output> </xf:repeat> </body> </html> This is probably quite different from your own form but it allowed me to find an issue within the upload control: with a browser automatically displaying the file name of the selected file, the last selected name was still displayed even after the binding change due to the insert. It did not alter the resulting instance. I have wrapped the corresponding HTML input with an HTML form to allow to reset it each time the upload control has a different binding. Please give a try to the latest revision (rev.613) I have just committed. Is it what you are looking for? Thanks! --Alain Le 17/04/2015 11:37, Mats Eklund a écrit : > Hi! > > Making progress with the use of XSLTForms, again, great tool!! > > Question: does XSLTForms support dynamic UI binding expressions > (XForms 1.1 specification chapter 7.4.3)? > > Background for my question is that I have an xf:upload control that is > bound to the last file element in a files list (i.e. > ref="files/file[last()]"). When a file has been uploaded with the > control, an xf:insert action inserts a new file to the end of the > list. Even after an explicit call to xf:rebuild/xf:refresh after the > xf:insert, the xf:upload control remains bound to the original file > element, even though this element is no longer last in the list! I > would need it however to bind to the new last element in order for my > form to work! > > Grateful for any clarification and help! > > Thanks, > Mats > > > ------------------------------------------------------------------------------ > BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT > Develop your own process in accordance with the BPMN 2 standard > Learn Process modeling best practices with Bonita BPM through live exercises > http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual- event?utm_ > source=Sourceforge_BPM_Camp_5_6_15&utm_medium=email&utm_campaign=VA_SF > > > _______________________________________________ > Xsltforms-support mailing list > Xsl...@li... > https://lists.sourceforge.net/lists/listinfo/xsltforms-support |
From: Alain C. <ala...@ag...> - 2015-04-19 16:22:15
|
Hello Tim, I have tested xf:message within a subform and it works for me: main form: <html xmlns="http://www.w3.org/1999/xhtml" xmlns:xforms="http://www.w3.org/2002/xforms" xmlns:ev="http://www.w3.org/2001/xml-events"> <head> <title>Main Form</title> <xforms:model> <xforms:instance> <data xmlns=""/> </xforms:instance> </xforms:model> </head> <body> <xforms:trigger> <xforms:label>Main Form</xforms:label> <xforms:action ev:event="DOMActivate"> <xforms:message>DOMActivate in Main Form</xforms:message> <xforms:load targetid="subform" resource="message-subform.xhtml"/> </xforms:action> </xforms:trigger> <xforms:group id="subform"/> </body> </html> subform: <html xmlns="http://www.w3.org/1999/xhtml" xmlns:xforms="http://www.w3.org/2002/xforms" xmlns:ev="http://www.w3.org/2001/xml-events"> <head> <title>Subform</title> <xforms:model> <xforms:instance> <data xmlns=""/> </xforms:instance> </xforms:model> </head> <body> <xforms:trigger> <xforms:label>Subform</xforms:label> <xforms:action ev:event="DOMActivate"> <xforms:message>DOMActivate in Subform</xforms:message> <xforms:unload targetid="subform"/> </xforms:action> </xforms:trigger> </body> </html> Could you please send me a minimal test case for this issue? Thanks! --Alain Le 13/04/2015 16:49, Tim Thompson a écrit : > Hello, > > An additional question: I have started using subforms and noticed that > my <xf:message> elements are now no longer being alerted. I can see > that they are output to the DOM (inspecting with Firebug), but the > alert notification does not appear. I've tried declaring the messages > in the subform as well, but that didn't work. I'm sure I'm missing > something here, but don't know what. > > Thank you, > Tim > > > On Mon, Apr 13, 2015 at 1:59 AM, Tim Thompson <tim...@gm... > <mailto:tim...@gm...>> wrote: > > Hello, > > I am running into an issue with repeat indexes when instance data > has been replaced by a submission (running XSLTForms 609 in eXist > 2.2). > > I send a query to the database: > > <xf:inputid="query"ref="instance('search')/query"incremental="true"> > <xf:label>Search</xf:label> > <xf:actionev:event="xforms-value-changed"> > <xf:sendsubmission="submit-search"/> > </xf:action> > </xf:input> > > The submission that handles this replaces the instance data: > > <xf:submissionid="submit-search"resource="/exist/restxq/query"method="get" > > serialization="application/x-www-form-urlencoded"ref="instance('search')/query" > targetref="instance('search-results')"replace="instance"/> > > I then output the results to a table: > > <tableid="results-table"> > <thead> > <th>Field</th> > <th>Value</th> > </thead> > <tbody> > <xf:repeatnodeset="instance('search-results')/*"id="search-results-repeat"> > <tr> > <td> > <xf:outputvalue="substring-after(name(.), ':')"></xf:output> > </td> > <td> > <xf:outputref="."/> > </td> > </tr> > </xf:repeat> > </tbody> > </table> > > I want to be able to click on a table row and set a value, based > on the current index, to send back to the server: > > <xf:trigger> > <xf:label>Select</xf:label> > <xf:actionev:event="DOMActivate"> > <xf:setvalue ref="instance('search')/selected"value="instance('search-results')/*[position() > = index('search-results-repeat')]/@rdf:about"/> > <xf:sendsubmission="select"/> > </xf:action> > </xf:trigger> > > However, when I replace the instance data with my first > submission, the repeat index does not reset. My question is, is it > possible to rebind the data so that the repeat index becomes > active again, without having to do a "@replace = 'all'" on submission? > > Thank you! > > Tim > > > > > ------------------------------------------------------------------------------ > BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT > Develop your own process in accordance with the BPMN 2 standard > Learn Process modeling best practices with Bonita BPM through live exercises > http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual- event?utm_ > source=Sourceforge_BPM_Camp_5_6_15&utm_medium=email&utm_campaign=VA_SF > > > _______________________________________________ > Xsltforms-support mailing list > Xsl...@li... > https://lists.sourceforge.net/lists/listinfo/xsltforms-support |
From: Alain C. <ala...@ag...> - 2015-04-19 16:15:46
|
Hello Tim, The index() function requires a special dependencies processing which was not fully implemented when initializing a repeat. Please try again with rev. 613 which has now been committed. Thanks! --Alain Le 13/04/2015 07:59, Tim Thompson a écrit : > Hello, > > I am running into an issue with repeat indexes when instance data has > been replaced by a submission (running XSLTForms 609 in eXist 2.2). > > I send a query to the database: > > <xf:inputid="query"ref="instance('search')/query"incremental="true"> > <xf:label>Search</xf:label> > <xf:actionev:event="xforms-value-changed"> > <xf:sendsubmission="submit-search"/> > </xf:action> > </xf:input> > > The submission that handles this replaces the instance data: > > <xf:submissionid="submit-search"resource="/exist/restxq/query"method="get" > > serialization="application/x-www-form-urlencoded"ref="instance('search')/query" > targetref="instance('search-results')"replace="instance"/> > > I then output the results to a table: > > <tableid="results-table"> > <thead> > <th>Field</th> > <th>Value</th> > </thead> > <tbody> > <xf:repeatnodeset="instance('search-results')/*"id="search-results-repeat"> > <tr> > <td> > <xf:outputvalue="substring-after(name(.), ':')"></xf:output> > </td> > <td> > <xf:outputref="."/> > </td> > </tr> > </xf:repeat> > </tbody> > </table> > > I want to be able to click on a table row and set a value, based on > the current index, to send back to the server: > > <xf:trigger> > <xf:label>Select</xf:label> > <xf:actionev:event="DOMActivate"> > <xf:setvalue ref="instance('search')/selected"value="instance('search-results')/*[position() > = index('search-results-repeat')]/@rdf:about"/> > <xf:sendsubmission="select"/> > </xf:action> > </xf:trigger> > > However, when I replace the instance data with my first submission, > the repeat index does not reset. My question is, is it possible to > rebind the data so that the repeat index becomes active again, without > having to do a "@replace = 'all'" on submission? > > Thank you! > > Tim > > > > ------------------------------------------------------------------------------ > BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT > Develop your own process in accordance with the BPMN 2 standard > Learn Process modeling best practices with Bonita BPM through live exercises > http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual- event?utm_ > source=Sourceforge_BPM_Camp_5_6_15&utm_medium=email&utm_campaign=VA_SF > > > _______________________________________________ > Xsltforms-support mailing list > Xsl...@li... > https://lists.sourceforge.net/lists/listinfo/xsltforms-support |
From: Mats E. <mat...@ya...> - 2015-04-17 09:50:07
|
Hi! Making progress with the use of XSLTForms, again, great tool!! Question: does XSLTForms support dynamic UI binding expressions (XForms 1.1 specification chapter 7.4.3)? Background for my question is that I have an xf:upload control that is bound to the last file element in a files list (i.e. ref="files/file[last()]"). When a file has been uploaded with the control, an xf:insert action inserts a new file to the end of the list. Even after an explicit call to xf:rebuild/xf:refresh after the xf:insert, the xf:upload control remains bound to the original file element, even though this element is no longer last in the list! I would need it however to bind to the new last element in order for my form to work! Grateful for any clarification and help! Thanks,Mats |
From: Tim T. <tim...@gm...> - 2015-04-13 14:49:19
|
Hello, An additional question: I have started using subforms and noticed that my <xf:message> elements are now no longer being alerted. I can see that they are output to the DOM (inspecting with Firebug), but the alert notification does not appear. I've tried declaring the messages in the subform as well, but that didn't work. I'm sure I'm missing something here, but don't know what. Thank you, Tim On Mon, Apr 13, 2015 at 1:59 AM, Tim Thompson <tim...@gm...> wrote: > Hello, > > I am running into an issue with repeat indexes when instance data has been > replaced by a submission (running XSLTForms 609 in eXist 2.2). > > I send a query to the database: > > <xf:input id="query" ref="instance('search')/query" incremental="true"> > <xf:label>Search</xf:label> > <xf:action ev:event="xforms-value-changed"> > <xf:send submission="submit-search"/> > </xf:action> > </xf:input> > > The submission that handles this replaces the instance data: > > <xf:submission id="submit-search" resource="/exist/restxq/query" method= > "get" > serialization="application/x-www-form-urlencoded" ref= > "instance('search')/query" > targetref="instance('search-results')" replace="instance"/> > > I then output the results to a table: > > <table id="results-table"> > <thead> > <th>Field</th> > <th>Value</th> > </thead> > <tbody> > <xf:repeat nodeset="instance('search-results')/*" id= > "search-results-repeat"> > <tr> > <td> > <xf:output value="substring-after(name(.), ':')" > ></xf:output> > </td> > <td> > <xf:output ref="."/> > </td> > </tr> > </xf:repeat> > </tbody> > </table> > > I want to be able to click on a table row and set a value, based on the > current index, to send back to the server: > > <xf:trigger> > <xf:label>Select</xf:label> > <xf:action ev:event="DOMActivate"> > <xf:setvalue ref="instance('search')/selected" value="instance('search-results')/*[position() > = index('search-results-repeat')]/@rdf:about"/> > <xf:send submission="select"/> > </xf:action> > </xf:trigger> > > However, when I replace the instance data with my first submission, the > repeat index does not reset. My question is, is it possible to rebind the > data so that the repeat index becomes active again, without having to do a > "@replace = 'all'" on submission? > > Thank you! > > Tim > |
From: Tim T. <tim...@gm...> - 2015-04-13 05:59:09
|
Hello, I am running into an issue with repeat indexes when instance data has been replaced by a submission (running XSLTForms 609 in eXist 2.2). I send a query to the database: <xf:input id="query" ref="instance('search')/query" incremental="true"> <xf:label>Search</xf:label> <xf:action ev:event="xforms-value-changed"> <xf:send submission="submit-search"/> </xf:action> </xf:input> The submission that handles this replaces the instance data: <xf:submission id="submit-search" resource="/exist/restxq/query" method= "get" serialization="application/x-www-form-urlencoded" ref= "instance('search')/query" targetref="instance('search-results')" replace="instance"/> I then output the results to a table: <table id="results-table"> <thead> <th>Field</th> <th>Value</th> </thead> <tbody> <xf:repeat nodeset="instance('search-results')/*" id= "search-results-repeat"> <tr> <td> <xf:output value="substring-after(name(.), ':')" ></xf:output> </td> <td> <xf:output ref="."/> </td> </tr> </xf:repeat> </tbody> </table> I want to be able to click on a table row and set a value, based on the current index, to send back to the server: <xf:trigger> <xf:label>Select</xf:label> <xf:action ev:event="DOMActivate"> <xf:setvalue ref="instance('search')/selected" value="instance('search-results')/*[position() = index('search-results-repeat')]/@rdf:about"/> <xf:send submission="select"/> </xf:action> </xf:trigger> However, when I replace the instance data with my first submission, the repeat index does not reset. My question is, is it possible to rebind the data so that the repeat index becomes active again, without having to do a "@replace = 'all'" on submission? Thank you! Tim |
From: Alain C. <ala...@ag...> - 2015-04-10 12:47:40
|
Hello Kristian, Currently, only xf:select/xf:itemset/xf:label/@ref and xf:select/xf:item/xf:label/text() are supported in XSLTForms. According to XForms 1.1 Recommendation, xf:label/xf:output should also be supported in both xf:item and xf:itemset. I will have a look at how to implement them. I already have my own test case for that but would be glad to have another one from you. Thanks! --Alain Le 10/04/2015 08:59, Kristian Kankainen a écrit : > Hello! > > Before posting any code, I want to quicklyl ask: Does the itext > functionality not work with the select1 element? > > I use translations in my xforms model. They are contained within the > xf:itext element in the model and for outputting I use xf:output with > xf:value="itext('localised-text-id')". > > Everything works fine elsewhere in my forms, all the localised text are > outputted correctly. But the moment I try adding an xf:output element > (that does work elsewhere) in a xf:label of a xf:select1 element, I get > an error: XSLTForms Exception Error initializing : TypeError > this.element is null > > If you can verify that itext *should work* with select1 elements, then I > am happy to post you some code. I use XSLTForms.xsl created at 2012-10-09. > > Kind regards > Kristian K > > ------------------------------------------------------------------------------ > BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT > Develop your own process in accordance with the BPMN 2 standard > Learn Process modeling best practices with Bonita BPM through live exercises > http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual- event?utm_ > source=Sourceforge_BPM_Camp_5_6_15&utm_medium=email&utm_campaign=VA_SF > _______________________________________________ > Xsltforms-support mailing list > Xsl...@li... > https://lists.sourceforge.net/lists/listinfo/xsltforms-support > |
From: Kristian K. <kri...@ek...> - 2015-04-10 07:27:58
|
Hello! Before posting any code, I want to quicklyl ask: Does the itext functionality not work with the select1 element? I use translations in my xforms model. They are contained within the xf:itext element in the model and for outputting I use xf:output with xf:value="itext('localised-text-id')". Everything works fine elsewhere in my forms, all the localised text are outputted correctly. But the moment I try adding an xf:output element (that does work elsewhere) in a xf:label of a xf:select1 element, I get an error: XSLTForms Exception Error initializing : TypeError this.element is null If you can verify that itext *should work* with select1 elements, then I am happy to post you some code. I use XSLTForms.xsl created at 2012-10-09. Kind regards Kristian K |
From: <ala...@ag...> - 2015-04-08 06:26:18
|
Hi Mark, This behavior is conform to W3C Specifications: the context attribute redefines the current context for other attributes. If you want to clone the selected item at the end of the repeat, please have a look at this test case: <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:xsi="http://www.w3.org/2001/XMLSchema-instance"> <head> <title>Repeat Select1</title> <xf:model> <xf:instance xmlns=""> <items> <item> <date xsi:type="xsd:date">2015-04-01</date> <status>A</status> </item> <item> <date xsi:type="xsd:date">2015-04-02</date> <status>A</status> </item> </items> </xf:instance> </xf:model> </head> <body> <xf:repeat id="repeat-id" ref="item"> <xf:output ref="date"> <xf:label>Date: </xf:label> </xf:output> <span>   </span> <xf:select1 ref="status"> <xf:label>Status: </xf:label> <xf:item> <xf:label>A</xf:label> <xf:value>A</xf:value> </xf:item> <xf:item> <xf:label>B</xf:label> <xf:value>B</xf:value> </xf:item> <xf:action ev:event="xforms-value-changed"> <xf:message><xf:output value="index('repeat-id')"/></xf:message> <xf:insert ref="../../item" position="after" origin=".."/> </xf:action> </xf:select1> </xf:repeat> </body> </html> Thank you for your feedback! --Alain > Le 7 avril 2015 à 00:54, Mark Lawson <tin...@gm...> a écrit : > > Hi, > > I'm using an insert inside an action that's inside an xf:repeat. What it's > meant to do is insert a new copy of the current node as a sibling. like so: > > <xf:action ev:event="xforms-value-changed"> > <xf:insert context="context()/.." at="last()" position="after" > origin="context()" /> > The problem is that context() returns the node I'm currently working with in > all cases but when I use it in origin. In that case it's returning the parent > of the current node. > > The background to this is I'm logging control changes, and using insert as a > way to get event context to an observer, so ideally I need the origin of the > insert to be generic. > > Rgds, > > Mark Lawson > > > ------------------------------------------------------------------------------ > BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT > Develop your own process in accordance with the BPMN 2 standard > Learn Process modeling best practices with Bonita BPM through live exercises > http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual- event?utm_ > > source=Sourceforge_BPM_Camp_5_6_15&utm_medium=email&utm_campaign=VA_SF_______________________________________________ > Xsltforms-support mailing list > Xsl...@li... > https://lists.sourceforge.net/lists/listinfo/xsltforms-support > |
From: Mark L. <tin...@gm...> - 2015-04-06 22:54:56
|
Hi, I'm using an insert inside an action that's inside an xf:repeat. What it's meant to do is insert a new copy of the current node as a sibling. like so: <xf:action ev:event="xforms-value-changed"> <xf:insert context="context()/.." at="last()" position="after" origin="context()" /> The problem is that context() returns the node I'm currently working with in all cases but when I use it in origin. In that case it's returning the parent of the current node. The background to this is I'm logging control changes, and using insert as a way to get event context to an observer, so ideally I need the origin of the insert to be generic. Rgds, Mark Lawson |
From: Mark B. <ma...@te...> - 2015-03-26 11:32:58
|
Thank you, Alain This community is really lucky to have you. We do realise and appreciate it. best Mark > On 25 Mar 2015, at 20:53, Alain Couthures <ala...@ag...> wrote: > > Hello Mark, > > I have now added support for TinyMCE 4.X in latest build on source repositories and I have updated www.agencexml.com accordingly. > > Thank you for your feed back! > > --Alain > > Le 24/03/2015 12:14, Mark Barratt a écrit : >> Apologies if the following reflects the fact that I don’t follow this list closely. >> >> Returning to xsltforms to update an old site, I find that TinyMCE in our site is very broken, and the example at http://www.agencexml.com/xsltforms/tinymce.xml (r595) shows the same symptoms. The first carriage return generates an extra <p> </p> and each subsequent keystroke generates the character keyed together with a <p> tag. This is true in Safari, Chrome and Firefox. >> >> This doesn’t seem to be in the issues list in GitHub or SourceForge (which is canonical?). >> >> Thanks for any help. >> >> -- >> Mark Barratt >> >> ------------------------------------------------------------------------------ >> Dive into the World of Parallel Programming The Go Parallel Website, sponsored >> by Intel and developed in partnership with Slashdot Media, is your hub for all >> things parallel software development, from weekly thought leadership blogs to >> news, videos, case studies, tutorials and more. Take a look and join the >> conversation now. http://goparallel.sourceforge.net/ >> _______________________________________________ >> Xsltforms-support mailing list >> Xsl...@li... >> https://lists.sourceforge.net/lists/listinfo/xsltforms-support > -- Mark Barratt Text Matters We help explain things using design | language | systems | process improvement ma...@te... | +44 (0)118 986 8313 http://www.textmatters.com | Twitter @mark_barratt | Skype mark_barratt |
From: Alain C. <ala...@ag...> - 2015-03-25 21:08:26
|
Hello Javier, Thank you for this fix! It has now been committed in latest revision. --Alain Le 11/03/2015 13:22, Javier Díaz a écrit : > Hello, > > I have been testing required-position="left" option, and I have > detected an error. > > Using 'upload' control in a form with this option, a javascript error > appears. > > To solve it, it is necesary to add this line it is in input control to > upload control: > > <xsl:when test="xforms:label/node() and $required-position = > 'left'">3</xsl:when> > > I suppose it is also necessary in 'range' and 'component' control, as > it as a similar logic. > > Best Regards, > Javier > > El 20/11/12 a las 12:26, Alex Bozhenko escribió: >> Dear Alain, Thank you for improving xforms. >> The option which you have added into xfoms works fine! >> With best regards, Alexander >> >> >> 2012/11/11 Alain Couthures <ala...@ag... >> <mailto:ala...@ag...>> >> >> Hi Alex, >> >> I have now added a new option for that: >> >> <?xsltforms-options required-position="left"?> >> >> It will be effective for all required controls with a label in >> the current form. >> >> As for other options, this one can be added in a config.xsl file. >> >> Thank you for your feedbacks! >> >> -Alain >> >> Le 12/10/2012 15:32, Alain Couthures a écrit : >> >> Hi Alex and all, >> >> This can probably be managed by a config option. Would it be an >> interesting way to proceed? >> >> Thank you for your point of views! >> >> -Alain >> >> Le 10/10/2012 13:15, Alex Bozhenko a écrit : >> >> Does it possible to put >> <span class="xforms-required-icon">*</span> >> after >> <label class="xforms-label"> >> (if label exist for this input), but not after >> <span class="value"> >> ? >> >> >> ------------------------------------------------------------------------------ >> Don't let slow site performance ruin your business. Deploy >> New Relic APM >> Deploy New Relic app performance management and know exactly >> what is happening inside your Ruby, Python, PHP, Java, and >> .NET app >> Try New Relic at no cost today and get our sweet Data Nerd >> shirt too! >> http://p.sf.net/sfu/newrelic-dev2dev >> _______________________________________________ >> Xsltforms-support mailing list >> Xsl...@li... >> <mailto:Xsl...@li...> >> https://lists.sourceforge.net/lists/listinfo/xsltforms-support >> >> >> >> >> >> ------------------------------------------------------------------------------ >> Monitor your physical, virtual and cloud infrastructure from a single >> web console. Get in-depth insight into apps, servers, databases, vmware, >> SAP, cloud infrastructure, etc. Download 30-day Free Trial. >> Pricing starts from $795 for 25 servers or applications! >> http://p.sf.net/sfu/zoho_dev2dev_nov >> >> >> _______________________________________________ >> Xsltforms-support mailing list >> Xsl...@li... >> https://lists.sourceforge.net/lists/listinfo/xsltforms-support > |
From: Alain C. <ala...@ag...> - 2015-03-25 21:06:07
|
Hello Mark, I have now added support for TinyMCE 4.X in latest build on source repositories and I have updated www.agencexml.com accordingly. Thank you for your feed back! --Alain Le 24/03/2015 12:14, Mark Barratt a écrit : > Apologies if the following reflects the fact that I don’t follow this list closely. > > Returning to xsltforms to update an old site, I find that TinyMCE in our site is very broken, and the example at http://www.agencexml.com/xsltforms/tinymce.xml (r595) shows the same symptoms. The first carriage return generates an extra <p> </p> and each subsequent keystroke generates the character keyed together with a <p> tag. This is true in Safari, Chrome and Firefox. > > This doesn’t seem to be in the issues list in GitHub or SourceForge (which is canonical?). > > Thanks for any help. > > -- > Mark Barratt > > ------------------------------------------------------------------------------ > Dive into the World of Parallel Programming The Go Parallel Website, sponsored > by Intel and developed in partnership with Slashdot Media, is your hub for all > things parallel software development, from weekly thought leadership blogs to > news, videos, case studies, tutorials and more. Take a look and join the > conversation now. http://goparallel.sourceforge.net/ > _______________________________________________ > Xsltforms-support mailing list > Xsl...@li... > https://lists.sourceforge.net/lists/listinfo/xsltforms-support |
From: Mark B. <ma...@te...> - 2015-03-24 11:38:07
|
Apologies if the following reflects the fact that I don’t follow this list closely. Returning to xsltforms to update an old site, I find that TinyMCE in our site is very broken, and the example at http://www.agencexml.com/xsltforms/tinymce.xml (r595) shows the same symptoms. The first carriage return generates an extra <p> </p> and each subsequent keystroke generates the character keyed together with a <p> tag. This is true in Safari, Chrome and Firefox. This doesn’t seem to be in the issues list in GitHub or SourceForge (which is canonical?). Thanks for any help. -- Mark Barratt |