xsltforms-support Mailing List for XSLTForms (Page 34)
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: <fr...@fl...> - 2013-04-23 09:06:17
|
Thanks, Alain, > The rendering for the first one and the second one are different > because the corresponding labels are not located identically. For > the first one, the corresponding label is located in the > grand-parent group. For the second one, the corresponding label is > located in the parent group. > Did you try to associate the label directly to the corresponding > input control? XForms 2.0 does not yet specify xforms:label/@for and > this is not implemented in latest build of XSLTForms. The point is that the 'grandfather' label allocation styles right and the more correct direct (or parent) label allocation styles wrong. I guess it is a CSS issue rather than an XSLTForms one. Why does the <div class="xforms-group-content"> get only 50% width and not the full space available? I found a solution by assigning different classes to the div's that are parent of the <div class="xforms-group-content"> and define the width of the XSLTForms generated divs through those. Examples of well-styled complex forms would probably help many implementers. Does a place exist to upload and view such solutions? Kind regards, Fred van Blommestein |
|
From: Alain C. <ala...@ag...> - 2013-04-23 08:58:35
|
> I was trying to use a client-side transformation. > > > Yes, I did check that out, but I thought it would not apply since I > want to use a client side transformation. Parameters cannot be set when the transformation is launched by a processing instruction. Did you check with a browser debugger, such as FireBug for FireFox or native debuggers for IE and Chrome, in the network profiler, whether the HTTP request for config.xsl is correct? Can you get it manually? -Alain |
|
From: Ingrid F. <if...@un...> - 2013-04-23 08:50:00
|
On 23/04/13 10:42, Alain Couthures wrote: > Hi Ingrid, >> How could I set $xsltforms_home (within the eXist framework)? > Are you using a server-side transformation? > I was trying to use a client-side transformation. > Did you have a look at > http://en.wikibooks.org/wiki/XRX/XSLTForms_and_eXist#Server-side_Transformation_using_the_transform_Function > ? Yes, I did check that out, but I thought it would not apply since I want to use a client side transformation. Ingrid -- Ingrid Falk Ingénieur de Recherche Logoscope @ LiLPa (Linguistique, Langue, Paroles) Université de Strasbourg |
|
From: Alain C. <ala...@ag...> - 2013-04-23 08:42:17
|
Hi Ingrid, > How could I set $xsltforms_home (within the eXist framework)? Are you using a server-side transformation? Did you have a look at http://en.wikibooks.org/wiki/XRX/XSLTForms_and_eXist#Server-side_Transformation_using_the_transform_Function ? -Alain |
|
From: Ingrid F. <if...@un...> - 2013-04-23 08:38:08
|
Hi Alain, Thanks for the reply. On 21/04/13 15:47, Alain Couthures wrote: > Hello Ingrid, >> I looked into xsltforms.xsl and I think the problem stems from this >> snippet: >> >> <xsl:variable name="configdoc" >> select="document(concat($xsltforms_home,'config.xsl'))/xsl:stylesheet/xsl:template[@name='config']"/> >> >> >> More specifically I suppose $xsltforms_home is not set correctly and I >> can't figure out where and how to set it. > $xsltforms_home is a global parameter with the empty string as default > value. So, the config.xsl file has, by default, to be at the same > location as the xsltforms.xsl file. It is there, I checked. How could I set $xsltforms_home (within the eXist framework)? Thank you & best regards, Ingrid -- Ingrid Falk Ingénieur de Recherche Logoscope @ LiLPa (Linguistique, Langue, Paroles) Université de Strasbourg |
|
From: C. M. Sperberg-M. <cm...@bl...> - 2013-04-22 19:25:39
|
A quick reminder - April 26, this Friday, is the early-bird registration deadline for the XForms course being offered by Black Mesa Technologies on 22-23 May 2013 in Rockville, Maryland. Those who register by this Friday get 10% off the normal registration price for the course. Full information about the course is at http://blackmesatech.com/2013/05/xforms/ -- **************************************************************** * C. M. Sperberg-McQueen, Black Mesa Technologies LLC * http://www.blackmesatech.com * http://cmsmcq.com/mib * http://balisage.net **************************************************************** |
|
From: Alain C. <ala...@ag...> - 2013-04-21 15:51:59
|
Hello Fred, > However, in some cases XSLTForms drops a <div > class="xforms-group-content"> around the input+caption, that gets half > as wide as the container div, so the input shows under the caption > instead of next to it. I cannot style <div > class="xforms-group-content">, because they are all over the place. > Defining their width as 100% screws up the form. For each group, a <div class="xforms-group-content"> is always created. I check with your test case and it sounds OK for me. > > In the example are two inputs, the first one styles OK, the second one > not. The rendering for the first one and the second one are different because the corresponding labels are not located identically. For the first one, the corresponding label is located in the grand-parent group. For the second one, the corresponding label is located in the parent group. > > Did any of you hit a similar problem? Any suggestions for a solution? > Did you try to associate the label directly to the corresponding input control? XForms 2.0 does not yet specify xforms:label/@for and this is not implemented in latest build of XSLTForms. Thank you for your feedbacks! -Alain |
|
From: Alain C. <ala...@ag...> - 2013-04-21 13:48:02
|
Hello Ingrid, > I looked into xsltforms.xsl and I think the problem stems from this snippet: > > <xsl:variable name="configdoc" > select="document(concat($xsltforms_home,'config.xsl'))/xsl:stylesheet/xsl:template[@name='config']"/> > > More specifically I suppose $xsltforms_home is not set correctly and I > can't figure out where and how to set it. $xsltforms_home is a global parameter with the empty string as default value. So, the config.xsl file has, by default, to be at the same location as the xsltforms.xsl file. Hope it helps. -Alain |
|
From: Ingrid F. <if...@un...> - 2013-04-19 14:13:56
|
On 19/04/13 13:27, Dan McCreary wrote: > I am not sure if I understand clearly but the following looks like it > might be the problem: > > <?xml-stylesheet type="text/xsl" href="../xsltforms/xsltforms.xsl"?> > > On eXist 2.0 the xsltforms.xsl file is located here: > > http://localhost:8080/exist/rest/db/apps/xsltforms/xsltforms.xsl > > Note that it is in the database, not the file system. > > If you put the following absolute paths in: > > > <?xml-stylesheet type="text/xsl" > href="/exist/rest/db/apps/xsltforms/xsltforms.xsl"?> > or > <?xml-stylesheet type="text/xsl" href="/rest/db/apps/xsltforms/xsltforms.xsl"?> > > if you change the jetty.xml to use "/" as the "context" > > then this should work. No, I'm afraid it doesn't. Apparently xsltforms.xsl is located correctly. When it is not (that is for example when using another path in the processing instruction) I get the error: stylesheet not found: /db/apps/logoscope/xsltforms/xsltforms.xsl I looked into xsltforms.xsl and I think the problem stems from this snippet: <xsl:variable name="configdoc" select="document(concat($xsltforms_home,'config.xsl'))/xsl:stylesheet/xsl:template[@name='config']"/> More specifically I suppose $xsltforms_home is not set correctly and I can't figure out where and how to set it. Best, Ingrid > > You can also load the XSLTForms demos app and see how they are done, > but you will need to understand the concepts around URL rewriting to > see how they work. > > - Dan > > > On Fri, Apr 19, 2013 at 3:10 AM, Ingrid Falk <if...@un...> wrote: >> Hi, >> >> I would like to use xforms inside eXist-db, client side. >> >> Currently, when I load the hello.xhtml xform from the eXist-db xsltforms >> demo application into my own application >> and then try to display it in the browser, I get the following error: >> >> Error while serializing XML: java.io.FileNotFoundException: >> /home/falk/eXist-db/config.xsl (No such file or directory) >> >> The setting is as follows: >> >> - I use the latest stable eXist-db release with Linux/Ubuntu >> It is installed in /home/falk/eXist-db >> >> - The processing instruction in the xform is: >> >> <?xml-stylesheet type="text/xsl" href="../xsltforms/xsltforms.xsl"?> >> >> - the path of hello.xhtml in eXist-db is: /db/apps/logoscope/hello.xhtml >> - the path of the xsltforms application is: /db/apps/xsltforms >> >> Apparently xsltforms.xsl is applied but it does not find the proper path for >> xsltforms to prepend to the config.xsl file. >> >> Any idea how I could go about to fix this? >> >> I could use xsltforms via my local http server - I couldn't figure out how >> to make it work with the file:// URI though. >> >> Is there an easy way to allow writing to files via the local http server or >> file:// URIs? >> >> What I would like to do is to display an xform in the browser, let a user on >> the local machine fill in some fields and then, when "submitting" save the >> outcome to a file on the local file system. >> >> Thank you & best regards, >> >> Ingrid Falk >> >> >> >> -- >> Ingrid Falk >> Ingénieur de Recherche >> Logoscope @ LiLPa (Linguistique, Langue, Paroles) >> Université de Strasbourg >> >> >> ------------------------------------------------------------------------------ >> Precog is a next-generation analytics platform capable of advanced >> analytics on semi-structured data. The platform includes APIs for building >> apps and a phenomenal toolset for data science. Developers can use >> our toolset for easy data analysis & visualization. Get a free account! >> http://www2.precog.com/precogplatform/slashdotnewsletter >> _______________________________________________ >> Xsltforms-support mailing list >> Xsl...@li... >> https://lists.sourceforge.net/lists/listinfo/xsltforms-support >> > > > -- Ingrid Falk Ingénieur de Recherche Logoscope @ LiLPa (Linguistique, Langue, Paroles) Université de Strasbourg |
|
From: Ingrid F. <if...@un...> - 2013-04-19 08:10:36
|
Hi, I would like to use xforms inside eXist-db, client side. Currently, when I load the hello.xhtml xform from the eXist-db xsltforms demo application into my own application and then try to display it in the browser, I get the following error: Error while serializing XML: java.io.FileNotFoundException: /home/falk/eXist-db/config.xsl (No such file or directory) The setting is as follows: - I use the latest stable eXist-db release with Linux/Ubuntu It is installed in /home/falk/eXist-db - The processing instruction in the xform is: <?xml-stylesheet type="text/xsl" href="../xsltforms/xsltforms.xsl"?> - the path of hello.xhtml in eXist-db is: /db/apps/logoscope/hello.xhtml - the path of the xsltforms application is: /db/apps/xsltforms Apparently xsltforms.xsl is applied but it does not find the proper path for xsltforms to prepend to the config.xsl file. Any idea how I could go about to fix this? I could use xsltforms via my local http server - I couldn't figure out how to make it work with the file:// URI though. Is there an easy way to allow writing to files via the local http server or file:// URIs? What I would like to do is to display an xform in the browser, let a user on the local machine fill in some fields and then, when "submitting" save the outcome to a file on the local file system. Thank you & best regards, Ingrid Falk -- Ingrid Falk Ingénieur de Recherche Logoscope @ LiLPa (Linguistique, Langue, Paroles) Université de Strasbourg |
|
From: <fr...@fl...> - 2013-04-17 19:41:35
|
Dear all,
I hit a problem on styling an XSLT form. I would like to position the
input box next to the caption. However, in some cases XSLTForms drops
a <div class="xforms-group-content"> around the input+caption, that
gets half as wide as the container div, so the input shows under the
caption instead of next to it. I cannot style <div
class="xforms-group-content">, because they are all over the place.
Defining their width as 100% screws up the form.
In the example are two inputs, the first one styles OK, the second one not.
Did any of you hit a similar problem? Any suggestions for a solution?
Thanks,
Fred van Blommestein
XML:
<xf:group ref="instance( 'Catalogue-1' )" model="Catalogue">
<xf:group class="W24 ABIE" ref="ebcac:ReceiverParty">
<xf:label class="W12 caption-big-left">Customer</xf:label>
<xf:group class="W24 BBIE" ref="ebcac:PartyName">
<xf:label class="W12 caption">Name</xf:label>
<xf:group class="W24 BBIE">
<xf:input ref="ebcbc:Name" incremental="true"></xf:input>
</xf:group>
</xf:group>
<xf:group class="W24" ref="ebcac:PostalAddress">
<xf:group class="W24 BBIE">
<xf:label class="W12 caption">City</xf:label>
<xf:input ref="ebcbc:CityName" incremental="true"></xf:input>
</xf:group>
</xf:group>
</xf:group>
</xf:group>
HTML:
<div id="xsltforms-mainform-group-2_2_4_4_1_" class="xforms-disabled
xforms-group">
<div class="xforms-group-content">
<div id="xsltforms-mainform-group-4_2_2_4_4_1_" class="W24 ABIE
xforms-disabled xforms-group">
<div xmlns="http://www.w3.org/1999/xhtml"
id="xsltforms-mainform-label-2_4_2_2_4_4_1_" class="W12
caption-big-left xforms-label xforms-group-label">Customer</div>
<div class="xforms-group-content">
<div id="xsltforms-mainform-group-4_4_2_2_4_4_1_" class="W24 BBIE
xforms-disabled xforms-group">
<div xmlns="http://www.w3.org/1999/xhtml"
id="xsltforms-mainform-label-2_4_4_2_2_4_4_1_" class="W12 caption
xforms-label xforms-group-label">Name</div>
<div class="xforms-group-content">
<div id="xsltforms-mainform-group-4_4_4_2_2_4_4_1_" class="W24
BBIE xforms-disabled xforms-group">
<div class="xforms-group-content">
<span xmlns="http://www.w3.org/1999/xhtml"
id="xsltforms-mainform-input-2_4_4_4_2_2_4_4_1_"
class="xforms-disabled xforms-control xforms-input
xforms-appearance-minimal">
<span class="value">
<input type="text" class="xforms-value" />
</span>
<span class="xforms-required-icon">*</span>
<span class="xforms-alert">
<span class="xforms-alert-icon"> </span>
</span>
</span>
</div>
</div>
</div>
</div>
<div id="xsltforms-mainform-group-6_4_2_2_4_4_1_" class="W24
xforms-disabled xforms-group">
<div class="xforms-group-content">
<div id="xsltforms-mainform-group-2_6_4_2_2_4_4_1_" class="W24
BBIE xforms-disabled xforms-group">
<div xmlns="http://www.w3.org/1999/xhtml"
id="xsltforms-mainform-label-2_2_6_4_2_2_4_4_1_" class="W12 caption
xforms-label xforms-group-label">City</div>
<div class="xforms-group-content">
<span xmlns="http://www.w3.org/1999/xhtml"
id="xsltforms-mainform-input-4_2_6_4_2_2_4_4_1_"
class="xforms-disabled xforms-control xforms-input
xforms-appearance-minimal">
<span class="value">
<input type="text" class="xforms-value" />
</span>
<span class="xforms-required-icon">*</span>
<span class="xforms-alert">
<span class="xforms-alert-icon"> </span>
</span>
</span>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
CSS:
.BBIE {
display: inline;
float: left;
min-height: 30px;
vertical-align: middle;
padding: 0px 5px 0px 5px;
margin: 3px 3px 3px 3px;
border: solid 1px red;
}
.xforms-group-content {
border: solid 1px blue;
}
.W12 {
width: 47%;
}
.W24 {
width: 95.7%;
}
.caption {
font-family: 'Lucida Grande', Helvetica, Arial, Verdana, sans-serif;
font-size: 14px;
font-weight:200;
display: inline;
}
|
|
From: Elias M. <eli...@gm...> - 2013-04-08 01:12:21
|
Hi Alain. The data types are defined as xsd:date and the date picker shows fine. I know the format of the date that shows in the browser is controlled by the local language config file (in my case config_en_us.xsl). All works fine and the date is written as YYYY-MM-DD in the XML. My problem is that the schema I'm using to validate the XML generated expects the date in the format "YYYYMMDD". I tried to modify config.xsl but it did not work. I need to be able to tell XSLTForms to write the date in the YYYYMMDD format, not the default YYYY-MM-DD. Thanks. Elias On Sun, Apr 7, 2013 at 2:14 PM, Alain Couthures < ala...@ag...> wrote: > Hello Elias, > > There are clearly may ways to serialize a date, not only as a string but > also as a number (number of time units since a specific date). > > The date picker in XSLTForms is rendered for the xsd:date type but, to > render it for other data types, it should be associated to a parent of it > (to be defined). Then, new date types could be defined with a regular > expression having named capture for parsing/serializing. > > All of this is not yet implemented (but should not require too much > work...) and using XSLT 1.0 stylesheets before/after submission is > currently the unique possibility. > > What do you think? > > -Alain > > Le 05/04/2013 18:32, Elias Mazur a écrit : > > >> Hi. >> >> I need to have the XForms display the date as "MM/dd/yyyy" but need to >> have it written to the XML as "yyyyMMdd". I know of the format.date on the >> config.xsl, but how can I configure to have it so the value displayed is >> MMdd/yyyy and the internal value that is held in the instance is "yyyyMMdd" >> >> Thanks. >> Elias >> >> > |
|
From: Alain C. <ala...@ag...> - 2013-04-07 18:14:45
|
Hello Elias, There are clearly may ways to serialize a date, not only as a string but also as a number (number of time units since a specific date). The date picker in XSLTForms is rendered for the xsd:date type but, to render it for other data types, it should be associated to a parent of it (to be defined). Then, new date types could be defined with a regular expression having named capture for parsing/serializing. All of this is not yet implemented (but should not require too much work...) and using XSLT 1.0 stylesheets before/after submission is currently the unique possibility. What do you think? -Alain Le 05/04/2013 18:32, Elias Mazur a écrit : > > Hi. > > I need to have the XForms display the date as "MM/dd/yyyy" but need to > have it written to the XML as "yyyyMMdd". I know of the format.date > on the config.xsl, but how can I configure to have it so the value > displayed is MMdd/yyyy and the internal value that is held in the > instance is "yyyyMMdd" > > Thanks. > Elias > |
|
From: Elias M. <eli...@gm...> - 2013-04-05 16:32:19
|
Hi. I need to have the XForms display the date as "MM/dd/yyyy" but need to have it written to the XML as "yyyyMMdd". I know of the format.date on the config.xsl, but how can I configure to have it so the value displayed is MMdd/yyyy and the internal value that is held in the instance is "yyyyMMdd" Thanks. Elias |
|
From: Javier D. <jd...@tc...> - 2013-04-05 12:50:38
|
Hello, we are using in xsltforms upload control and we found a performance issue when uploading big files (with ~100000 lines). Examining applet code, we have found a botteneck creating string in base64 encoding. We have solved the problem using StringBuilders instead of Strings in for loops (I send you our changes attached in this email). Using Strings in for loops is discouraged because in each iteration it is created a new String with all the content. In previous version, it lasted more than hour to load file, and now it is almost immediate. Regards, Javier ************************************************************************************************************************************************ *La información contenida en este mensaje de correo electrónico es confidencial y puede revestir el carácter de reservada. * *Está dirigida exclusivamente a la persona destinataria. * *El acceso o cualquier uso por parte de cualquier otra persona de este mensaje no están autorizados y pueden ser ilegales.* *Si no es Ud. la persona destinataria, le rogamos que proceda a borrarlo. * *The information in this e-mail is confidential and may be legally privileged. * *It is intended solely for the addressee. * *Access or any use by any other person to this Internet e-mail is not authorised and may be unlawful. * *If you are not the intended recipient, please delete this e-mail. * ************************************************************************************************************************************************ |
|
From: Alain C. <ala...@ag...> - 2013-04-02 17:45:20
|
Hello Elias, > Scenario: user opens the xforms and enters some data. after that it > submits that data and the xquery detects an error condition before > writing to the database and gives the user a back button (or the user > clicks on the back button of the browser). > > - When that happens all the entered data is lost and the original > data is displayed. I think this happens because xforms > recalculate/revalidates everything. > > Is there a way to disable that so the user does not loose the entered > data? > > If you need to validate some data at server-side, you should better use the AJAX approach: the form is not fully replaced since the validation is not OK. After that, the form can ask for the next one, maybe with the same values or from the returned status from the previous AJAX call. The browser navigation is not safe when mixed with AJAX... -Alain |
|
From: Elias M. <eli...@gm...> - 2013-03-28 21:21:45
|
Hi. Setup: xforms with submission to an xquery that stores the data into the database in an XML file Scenario: user opens the xforms and enters some data. after that it submits that data and the xquery detects an error condition before writing to the database and gives the user a back button (or the user clicks on the back button of the browser). - When that happens all the entered data is lost and the original data is displayed. I think this happens because xforms recalculate/revalidates everything. Is there a way to disable that so the user does not loose the entered data? Thanks. Elias |
|
From: Alain C. <ala...@ag...> - 2013-03-28 20:04:23
|
Hello Elias, The incremental mode was easier to implement and this cannot be disabled yet. There is a lot of possible event handlers in TinyMCE (for example: http://www.tinymce.com/wiki.php/API3:event.tinymce.Editor.onSubmit) and there might be a good combination for implementing the non-incremental mode. Actually, TinyMCE is a nightmare for me and I wish I had time to write my own RichText Editor... -Alain Le 28/03/2013 19:07, Elias Mazur a écrit : > Hi. > > I have an xform that has TinyMCE and it works fine. I used the > example from XSLTForms distribution that updates the <div> that > displays the text entered incrementally. How can I disable that so > that the div is only updated after I'm done with TinyMCE? > > I tried incremental=false in several places with no luck. > > Thanks > Elias > > > ------------------------------------------------------------------------------ > Own the Future-Intel® Level Up Game Demo Contest 2013 > Rise to greatness in Intel's independent game demo contest. > Compete for recognition, cash, and the chance to get your game > on Steam. $5K grand prize plus 10 genre and skill prizes. > Submit your demo by 6/6/13. http://p.sf.net/sfu/intel_levelupd2d > > > _______________________________________________ > Xsltforms-support mailing list > Xsl...@li... > https://lists.sourceforge.net/lists/listinfo/xsltforms-support |
|
From: Elias M. <eli...@gm...> - 2013-03-28 18:07:28
|
Hi. I have an xform that has TinyMCE and it works fine. I used the example from XSLTForms distribution that updates the <div> that displays the text entered incrementally. How can I disable that so that the div is only updated after I'm done with TinyMCE? I tried incremental=false in several places with no luck. Thanks Elias |
|
From: Alain C. <ala...@ag...> - 2013-03-27 21:33:07
|
Hi Alexander, This is all about deferred actions: the refresh is performed only after the submission being completely done. I can test a small improvement based on the use of the mode attribute for submission to show the status panel during all the submission when set to "synchronous", the default value being "asynchronous". It means that the customizable "... Loading ..." message will automatically appear and disappear. What do you think? Thanks! -Alain Le 21/03/2013 15:01, Alexander Holupirek a écrit : > Hi all, > > i have a problem showing the user that a submission is in progress. > > A trigger is fireing a submission that takes ~2sec. > xforms-submit event is dispatched and an info string 'Submitting ...' is set as a value to be displayed to the user. > xforms-select is choosing the xforms-case that should display the info string. > > However, what works for xforms-submit-done and xforms-submit-error is not working for the xforms-submit event. > > Interestingly, it works if an xf:message is used to display the 'Submission in progress' string as an action registered on xforms-submit, so the xforms-submit event should not be the problem. > > Here is a running example: > > This works using an message: > > http://phobos103.inf.uni-konstanz.de/xforms/submit2.xml > > This doesn't work as expected (showing the string in an output): > > http://phobos103.inf.uni-konstanz.de/xforms/submit1.xml > > Thanks for your help, > Alex > > Here is the trace log: > > 2013-03-21T14:40:02+01:00 -> Dispatching event xforms-model-construct on <SPAN class="xforms-model" id="model-submission"/> > 2013-03-21T14:40:02+01:00 -> Dispatching event xforms-model-construct-done on <SPAN class="xforms-model" id="model-submission"/> > 2013-03-21T14:40:02+01:00 -> Dispatching event xforms-model-construct on <SPAN class="xforms-model" id="xsltforms-mainform-model-config"/> > 2013-03-21T14:40:02+01:00 -> Dispatching event xforms-model-construct-done on <SPAN class="xforms-model" id="xsltforms-mainform-model-config"/> > 2013-03-21T14:40:02+01:00 -> Dispatching event xforms-select on <DIV class="xforms-case" id="info-default"/> > 2013-03-21T14:40:02+01:00 -> Dispatching event xforms-ready on <SPAN class="xforms-model" id="model-submission"/> > 2013-03-21T14:40:02+01:00 -> Dispatching event xforms-ready on <SPAN class="xforms-model" id="xsltforms-mainform-model-config"/> > 2013-03-21T14:40:06+01:00 -> Dispatching event DOMFocusIn on <SPAN class=" xforms-control xforms-trigger xforms-appearance-minimal xforms-focus" id="xsltforms-mainform-trigger-2_4_3_"/> > 2013-03-21T14:40:06+01:00 -> Dispatching event DOMActivate on <SPAN class=" xforms-control xforms-trigger xforms-appearance-minimal xforms-focus" id="xsltforms-mainform-trigger-2_4_3_"/> > 2013-03-21T14:40:06+01:00 -> Dispatching event fire-submission on <SPAN class="xforms-model" id="model-submission"/> > 2013-03-21T14:40:06+01:00 -> Dispatching event xforms-submit on <SPAN class="xforms-submission" id="submission-get-response"/> > 2013-03-21T14:40:06+01:00 -> Setvalue info = Submitting ... > 2013-03-21T14:40:06+01:00 -> Dispatching event xforms-deselect on <DIV class="xforms-case" id="info-default"/> > 2013-03-21T14:40:06+01:00 -> Dispatching event xforms-select on <DIV class="xforms-case" id="info-submission"/> > 2013-03-21T14:40:06+01:00 -> Dispatching event xforms-submit-serialize on <SPAN class="xforms-submission" id="submission-get-response"/> > 2013-03-21T14:40:06+01:00 -> Submit get - application/xml - /xforms/response.php?id=0001 - true > 2013-03-21T14:40:08+01:00 -> Dispatching event xforms-rebuild on <SPAN class="xforms-model" id="model-submission"/> > 2013-03-21T14:40:08+01:00 -> Dispatching event xforms-recalculate on <SPAN class="xforms-model" id="model-submission"/> > 2013-03-21T14:40:08+01:00 -> Dispatching event xforms-revalidate on <SPAN class="xforms-model" id="model-submission"/> > 2013-03-21T14:40:08+01:00 -> Dispatching event xforms-refresh on <SPAN class="xforms-model" id="model-submission"/> > 2013-03-21T14:40:08+01:00 -> Dispatching event xforms-optional on <SPAN class=" xforms-control xforms-output xforms-appearance xforms-optional xforms-enabled xforms-readwrite xforms-valid" id="xsltforms-mainform-output-4_4_4_4_3_"/> > 2013-03-21T14:40:08+01:00 -> Dispatching event xforms-enabled on <SPAN class=" xforms-control xforms-output xforms-appearance xforms-optional xforms-enabled xforms-readwrite xforms-valid" id="xsltforms-mainform-output-4_4_4_4_3_"/> > 2013-03-21T14:40:08+01:00 -> Dispatching event xforms-readwrite on <SPAN class=" xforms-control xforms-output xforms-appearance xforms-optional xforms-enabled xforms-readwrite xforms-valid" id="xsltforms-mainform-output-4_4_4_4_3_"/> > 2013-03-21T14:40:08+01:00 -> Dispatching event xforms-valid on <SPAN class=" xforms-control xforms-output xforms-appearance xforms-optional xforms-enabled xforms-readwrite xforms-valid" id="xsltforms-mainform-output-4_4_4_4_3_"/> > 2013-03-21T14:40:08+01:00 -> Dispatching event xforms-value-changed on <SPAN class=" xforms-control xforms-output xforms-appearance xforms-optional xforms-enabled xforms-readwrite xforms-valid" id="xsltforms-mainform-output-4_4_4_4_3_"/> > 2013-03-21T14:40:08+01:00 -> Dispatching event xforms-submit-done on <SPAN class="xforms-submission" id="submission-get-response"/> > 2013-03-21T14:40:08+01:00 -> Setvalue info = Submission done > 2013-03-21T14:40:08+01:00 -> Dispatching event xforms-deselect on <DIV class="xforms-case" id="info-default"/> > 2013-03-21T14:40:08+01:00 -> Dispatching event xforms-select on <DIV class="xforms-case" id="info-submission"/> > 2013-03-21T14:40:08+01:00 -> Dispatching event xforms-recalculate on <SPAN class="xforms-model" id="model-submission"/> > 2013-03-21T14:40:08+01:00 -> Dispatching event xforms-revalidate on <SPAN class="xforms-model" id="model-submission"/> > 2013-03-21T14:40:08+01:00 -> Dispatching event xforms-refresh on <SPAN class="xforms-model" id="model-submission"/> > 2013-03-21T14:40:08+01:00 -> Dispatching event xforms-optional on <SPAN class=" xforms-control xforms-output xforms-appearance xforms-optional xforms-enabled xforms-readwrite xforms-valid" id="xsltforms-mainform-output-4_4_4_4_3_"/> > 2013-03-21T14:40:08+01:00 -> Dispatching event xforms-enabled on <SPAN class=" xforms-control xforms-output xforms-appearance xforms-optional xforms-enabled xforms-readwrite xforms-valid" id="xsltforms-mainform-output-4_4_4_4_3_"/> > 2013-03-21T14:40:08+01:00 -> Dispatching event xforms-readwrite on <SPAN class=" xforms-control xforms-output xforms-appearance xforms-optional xforms-enabled xforms-readwrite xforms-valid" id="xsltforms-mainform-output-4_4_4_4_3_"/> > 2013-03-21T14:40:08+01:00 -> Dispatching event xforms-valid on <SPAN class=" xforms-control xforms-output xforms-appearance xforms-optional xforms-enabled xforms-readwrite xforms-valid" id="xsltforms-mainform-output-4_4_4_4_3_"/> > 2013-03-21T14:40:08+01:00 -> Dispatching event xforms-value-changed on <SPAN class=" xforms-control xforms-output xforms-appearance xforms-optional xforms-enabled xforms-readwrite xforms-valid" id="xsltforms-mainform-output-4_4_4_4_3_"/> > > > ------------------------------------------------------------------------------ > Everyone hates slow websites. So do we. > Make your web apps faster with AppDynamics > Download AppDynamics Lite for free today: > http://p.sf.net/sfu/appdyn_d2d_mar > _______________________________________________ > Xsltforms-support mailing list > Xsl...@li... > https://lists.sourceforge.net/lists/listinfo/xsltforms-support > |
|
From: Alain C. <ala...@ag...> - 2013-03-27 17:55:39
|
Hello Paul, Thank you very much for contributing and improving XSLTForms! I have integrated this patch in the latest build: http://svn.code.sf.net/p/xsltforms/svn or https://github.com/AlainCouthures/xsltforms.git -Alain Le 14/03/2013 22:38, Paul Vanderveen a écrit : > > TerraXML has an XSLTForms 1.0RC based search form that has an > onkeydown event that uses the enter key to submit the search request > (see form image) > > When you press the enter key to perform the search in IE9, the website > would reload. > > Turns out the keypress event was getting handled by XSLTForms, but it > was propagating to other windows in the app. > > The following change to xsltforms.js seems to have fixed this > behavior. I have not identified any ill-effects from doing this so far. > > (xsltforms.js, line 5300) > > XsltForms_input.keyPressActivate = function(a) { > > this.keyPressCode = a.keyCode; > > /** Change put in by PV TerraXML to prevent ENTER key bleedthrough > on IE9 (See TV-238) */ > > if (a.keyCode === 13) { > > if (a.stopPropagation) { > > a.stopPropagation(); > > a.preventDefault(); > > } > > else { > > a.cancelBubble = true; > > } > > } > > /* END */ > > }; > > */Paul Vanderveen/* > > Chief Architect, Research and Development > > Description: TerraXML-Logo-BIG > > /1380 Forest Park Circle, Suite 100/ > > /Lafayette, CO 80026/ > > p: 888-707-7846 x 221 > > |
|
From: Adam M. <Ada...@gm...> - 2013-03-27 09:23:56
|
Hi Alain,
> The test condition could be extended for Javascript: && action.substr(0,11) !== "javascript:"
> Could you please test with this?
I did try that code change and it fixes the problem for me. The
work-around I use is OK, but it's still nicer to avoid such tricks of
course.
> I think that some XSLTForms users have already mixed it with jQuery. Do you have a test case which
> doesn't work?
It's been awhile since I tried to use jQuery with XSLTForms. I'm glad
to hear they may co-exist now. I was only curious & probably won't
try it for awhile. If I have trouble when I do try it, I'll share a
test case with you of course.
Thanks for your help!
/Adam
On Mon, Mar 25, 2013 at 3:15 PM, Alain Couthures
<ala...@ag...> wrote:
> Hi Adam,
>
>> Looking at xsltforms.js, the line in
>> XsltForms_submission.prototype.submit that invokes JS is this one:
>>
>> eval("ser = (" + action.substr(11) + ");");
>>
>> So my work-around is to make the garbage appended to the action
>> harmless by making it a comment:
>>
>> <xf:submission
>> id='submit'
>> method='get'
>> relevant='true'
>> replace='instance'
>> serialization='application/xml'
>> action='javascript:submit(ser));//'
>> />
>>
>> The line of JS eval'd might be something like:
>>
>> ser = (submit(ser));//?var1=val1&var2=val2...
>
> By default, XSLTForms is serializing the current instance with a get method
> in the query string:
>
> if ((method === "get" || method === "delete") && this.serialization
> !== "none" && action.substr(0, 9) !== "opener://" && action.substr(0, 8) !==
> "local://") {
> var tourl = XsltForms_submission.toUrl_(node, this.separator);
> action += (action.indexOf('?') === -1? '?' : this.separator) +
> tourl.substr(0, tourl.length - this.separator.length);
> }
>
> The test condition could be extended for Javascript: && action.substr(0,11)
> !== "javascript:"
>
> Could you please test with this?
>
>> Also, can XSLTForms co-exist with jQuery now? Currently I put my
>> forms into iframes, which is mostly OK, but it would be nice in future
>> to have everything in one integrated page.
>>
> I think that some XSLTForms users have already mixed it with jQuery. Do you
> have a test case which doesn't work?
>
> Thanks!
>
> -Alain
|
|
From: Alain C. <ala...@ag...> - 2013-03-25 21:15:45
|
Hi Adam,
> Looking at xsltforms.js, the line in
> XsltForms_submission.prototype.submit that invokes JS is this one:
>
> eval("ser = (" + action.substr(11) + ");");
>
> So my work-around is to make the garbage appended to the action
> harmless by making it a comment:
>
> <xf:submission
> id='submit'
> method='get'
> relevant='true'
> replace='instance'
> serialization='application/xml'
> action='javascript:submit(ser));//'
> />
>
> The line of JS eval'd might be something like:
>
> ser = (submit(ser));//?var1=val1&var2=val2...
By default, XSLTForms is serializing the current instance with a get
method in the query string:
if ((method === "get" || method === "delete") &&
this.serialization !== "none" && action.substr(0, 9) !== "opener://" &&
action.substr(0, 8) !== "local://") {
var tourl = XsltForms_submission.toUrl_(node, this.separator);
action += (action.indexOf('?') === -1? '?' : this.separator) +
tourl.substr(0, tourl.length - this.separator.length);
}
The test condition could be extended for Javascript: &&
action.substr(0,11) !== "javascript:"
Could you please test with this?
> Also, can XSLTForms co-exist with jQuery now? Currently I put my
> forms into iframes, which is mostly OK, but it would be nice in future
> to have everything in one integrated page.
>
I think that some XSLTForms users have already mixed it with jQuery. Do
you have a test case which doesn't work?
Thanks!
-Alain
|
|
From: Adam M. <Ada...@gm...> - 2013-03-24 13:40:24
|
Hi,
<< This time I'm posting in plain text, which should work better! >>
A few months ago I asked for some advice about invoking JavaScript to
handle form submission. I'd like to restate the problem I
encountered, share my work-around, and ask again for input. I wanted
to pass the instance data (serialized as xml) to a JavaScript
function, and let it handle the submission from there. The problem I
encountered is that I could only use the 'get' submission method with
JavaScript, and with 'get' the instance data would be URL-encoded and
appended to the 'action', which is a problem if the action is
'javascript:submit(ser);'.
Looking at xsltforms.js, the line in
XsltForms_submission.prototype.submit that invokes JS is this one:
eval("ser = (" + action.substr(11) + ");");
So my work-around is to make the garbage appended to the action
harmless by making it a comment:
<xf:submission
id='submit'
method='get'
relevant='true'
replace='instance'
serialization='application/xml'
action='javascript:submit(ser));//'
/>
The line of JS eval'd might be something like:
ser = (submit(ser));//?var1=val1&var2=val2...
Would it be OK to change the code so it never appends URL-encoded
instance data to an action that starts with 'javascript:' ?
Also, can XSLTForms co-exist with jQuery now? Currently I put my
forms into iframes, which is mostly OK, but it would be nice in future
to have everything in one integrated page.
Thanks very much!
/A
|
|
From: Alexander H. <al...@ho...> - 2013-03-21 14:13:46
|
Hi all, i have a problem showing the user that a submission is in progress. A trigger is fireing a submission that takes ~2sec. xforms-submit event is dispatched and an info string 'Submitting ...' is set as a value to be displayed to the user. xforms-select is choosing the xforms-case that should display the info string. However, what works for xforms-submit-done and xforms-submit-error is not working for the xforms-submit event. Interestingly, it works if an xf:message is used to display the 'Submission in progress' string as an action registered on xforms-submit, so the xforms-submit event should not be the problem. Here is a running example: This works using an message: http://phobos103.inf.uni-konstanz.de/xforms/submit2.xml This doesn't work as expected (showing the string in an output): http://phobos103.inf.uni-konstanz.de/xforms/submit1.xml Thanks for your help, Alex Here is the trace log: 2013-03-21T14:40:02+01:00 -> Dispatching event xforms-model-construct on <SPAN class="xforms-model" id="model-submission"/> 2013-03-21T14:40:02+01:00 -> Dispatching event xforms-model-construct-done on <SPAN class="xforms-model" id="model-submission"/> 2013-03-21T14:40:02+01:00 -> Dispatching event xforms-model-construct on <SPAN class="xforms-model" id="xsltforms-mainform-model-config"/> 2013-03-21T14:40:02+01:00 -> Dispatching event xforms-model-construct-done on <SPAN class="xforms-model" id="xsltforms-mainform-model-config"/> 2013-03-21T14:40:02+01:00 -> Dispatching event xforms-select on <DIV class="xforms-case" id="info-default"/> 2013-03-21T14:40:02+01:00 -> Dispatching event xforms-ready on <SPAN class="xforms-model" id="model-submission"/> 2013-03-21T14:40:02+01:00 -> Dispatching event xforms-ready on <SPAN class="xforms-model" id="xsltforms-mainform-model-config"/> 2013-03-21T14:40:06+01:00 -> Dispatching event DOMFocusIn on <SPAN class=" xforms-control xforms-trigger xforms-appearance-minimal xforms-focus" id="xsltforms-mainform-trigger-2_4_3_"/> 2013-03-21T14:40:06+01:00 -> Dispatching event DOMActivate on <SPAN class=" xforms-control xforms-trigger xforms-appearance-minimal xforms-focus" id="xsltforms-mainform-trigger-2_4_3_"/> 2013-03-21T14:40:06+01:00 -> Dispatching event fire-submission on <SPAN class="xforms-model" id="model-submission"/> 2013-03-21T14:40:06+01:00 -> Dispatching event xforms-submit on <SPAN class="xforms-submission" id="submission-get-response"/> 2013-03-21T14:40:06+01:00 -> Setvalue info = Submitting ... 2013-03-21T14:40:06+01:00 -> Dispatching event xforms-deselect on <DIV class="xforms-case" id="info-default"/> 2013-03-21T14:40:06+01:00 -> Dispatching event xforms-select on <DIV class="xforms-case" id="info-submission"/> 2013-03-21T14:40:06+01:00 -> Dispatching event xforms-submit-serialize on <SPAN class="xforms-submission" id="submission-get-response"/> 2013-03-21T14:40:06+01:00 -> Submit get - application/xml - /xforms/response.php?id=0001 - true 2013-03-21T14:40:08+01:00 -> Dispatching event xforms-rebuild on <SPAN class="xforms-model" id="model-submission"/> 2013-03-21T14:40:08+01:00 -> Dispatching event xforms-recalculate on <SPAN class="xforms-model" id="model-submission"/> 2013-03-21T14:40:08+01:00 -> Dispatching event xforms-revalidate on <SPAN class="xforms-model" id="model-submission"/> 2013-03-21T14:40:08+01:00 -> Dispatching event xforms-refresh on <SPAN class="xforms-model" id="model-submission"/> 2013-03-21T14:40:08+01:00 -> Dispatching event xforms-optional on <SPAN class=" xforms-control xforms-output xforms-appearance xforms-optional xforms-enabled xforms-readwrite xforms-valid" id="xsltforms-mainform-output-4_4_4_4_3_"/> 2013-03-21T14:40:08+01:00 -> Dispatching event xforms-enabled on <SPAN class=" xforms-control xforms-output xforms-appearance xforms-optional xforms-enabled xforms-readwrite xforms-valid" id="xsltforms-mainform-output-4_4_4_4_3_"/> 2013-03-21T14:40:08+01:00 -> Dispatching event xforms-readwrite on <SPAN class=" xforms-control xforms-output xforms-appearance xforms-optional xforms-enabled xforms-readwrite xforms-valid" id="xsltforms-mainform-output-4_4_4_4_3_"/> 2013-03-21T14:40:08+01:00 -> Dispatching event xforms-valid on <SPAN class=" xforms-control xforms-output xforms-appearance xforms-optional xforms-enabled xforms-readwrite xforms-valid" id="xsltforms-mainform-output-4_4_4_4_3_"/> 2013-03-21T14:40:08+01:00 -> Dispatching event xforms-value-changed on <SPAN class=" xforms-control xforms-output xforms-appearance xforms-optional xforms-enabled xforms-readwrite xforms-valid" id="xsltforms-mainform-output-4_4_4_4_3_"/> 2013-03-21T14:40:08+01:00 -> Dispatching event xforms-submit-done on <SPAN class="xforms-submission" id="submission-get-response"/> 2013-03-21T14:40:08+01:00 -> Setvalue info = Submission done 2013-03-21T14:40:08+01:00 -> Dispatching event xforms-deselect on <DIV class="xforms-case" id="info-default"/> 2013-03-21T14:40:08+01:00 -> Dispatching event xforms-select on <DIV class="xforms-case" id="info-submission"/> 2013-03-21T14:40:08+01:00 -> Dispatching event xforms-recalculate on <SPAN class="xforms-model" id="model-submission"/> 2013-03-21T14:40:08+01:00 -> Dispatching event xforms-revalidate on <SPAN class="xforms-model" id="model-submission"/> 2013-03-21T14:40:08+01:00 -> Dispatching event xforms-refresh on <SPAN class="xforms-model" id="model-submission"/> 2013-03-21T14:40:08+01:00 -> Dispatching event xforms-optional on <SPAN class=" xforms-control xforms-output xforms-appearance xforms-optional xforms-enabled xforms-readwrite xforms-valid" id="xsltforms-mainform-output-4_4_4_4_3_"/> 2013-03-21T14:40:08+01:00 -> Dispatching event xforms-enabled on <SPAN class=" xforms-control xforms-output xforms-appearance xforms-optional xforms-enabled xforms-readwrite xforms-valid" id="xsltforms-mainform-output-4_4_4_4_3_"/> 2013-03-21T14:40:08+01:00 -> Dispatching event xforms-readwrite on <SPAN class=" xforms-control xforms-output xforms-appearance xforms-optional xforms-enabled xforms-readwrite xforms-valid" id="xsltforms-mainform-output-4_4_4_4_3_"/> 2013-03-21T14:40:08+01:00 -> Dispatching event xforms-valid on <SPAN class=" xforms-control xforms-output xforms-appearance xforms-optional xforms-enabled xforms-readwrite xforms-valid" id="xsltforms-mainform-output-4_4_4_4_3_"/> 2013-03-21T14:40:08+01:00 -> Dispatching event xforms-value-changed on <SPAN class=" xforms-control xforms-output xforms-appearance xforms-optional xforms-enabled xforms-readwrite xforms-valid" id="xsltforms-mainform-output-4_4_4_4_3_"/> |
97 messages has been excluded from this view by a project administrator.
