xsltforms-support — XSLTForms support list

Re: [Xsltforms-support] Accessing items withing xf:repeat

[Tim T. <tim...@gm...>]

I was able to achieve this with the following bit of jQuery[1] and XForms
structure:

jQuery:

$('#results-table').on('click', 'tbody tr', function(event) {
    $(this).addClass('highlight').siblings().removeClass('highlight');
});

XForms:

<xf:group ref="instance('search-results')">
    <table id="results-table">
        <tbody>
            <xf:repeat nodeset="*" id="search-results-repeat">
                <tr>
                    <td>
                        <xf:trigger appearance="minimal">
                            <xf:label>
                                <xf:output value="name(.)"></xf:output>
                            </xf:label>
                            <xf:output ref="."></xf:output>
                        </xf:trigger>
                    </td>
                </tr>
            </xf:repeat>
        </tbody>
    </table>
</xf:group>

[1] http://jsfiddle.net/iambriansreed/xu2AH/9/


On Tue, Mar 17, 2015 at 4:01 PM, Tim Thompson <tim...@gm...> wrote:

> Hello,
>
> I would like to be able to add some simple styling to the items within an
> <xf:repeat> element. Specifically, I would like to use jQuery to attach a
> click listener to each div that has an "xforms-repeat-item" class. When a
> user clicks on a div within the repeat, for example, a "highlight" class
> would be added in order to generate a background color for the div.
> However, I find that within the <xf:repeat> I am only able to modify the
> first item (which has an "xforms-repeat-item-selected" class).
>
> Is there a way to achieve this functionality in XSLTForms?
>
> Thank you,
> Tim
>

[Xsltforms-support] Accessing items withing xf:repeat

[Tim T. <tim...@gm...>]

Hello,

I would like to be able to add some simple styling to the items within an
<xf:repeat> element. Specifically, I would like to use jQuery to attach a
click listener to each div that has an "xforms-repeat-item" class. When a
user clicks on a div within the repeat, for example, a "highlight" class
would be added in order to generate a background color for the div.
However, I find that within the <xf:repeat> I am only able to modify the
first item (which has an "xforms-repeat-item-selected" class).

Is there a way to achieve this functionality in XSLTForms?

Thank you,
Tim

[Xsltforms-support] Error in option: required-position = 'left'

[Javier D. <jd...@tc...>]

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

Re: [Xsltforms-support] RDF/XML support

[Tim T. <tim...@gm...>]

Sorry, please disregard. I had failed to change the file extension from
".rdf" to ".xml".

Thanks,
Tim

On Sun, Mar 8, 2015 at 4:03 PM, Tim Thompson <tim...@gm...> wrote:

> Hello,
>
> I am trying to load an RDF/XML ontology as an instance document, but am
> receiving an error message of "unsupported mediatype
> 'application/rdf+xml'."
>
> I see the part in xsltforms.js that is checking for valid mediatypes, but
> I'm not sure how to modify it to accept this as valid XML.
>
> Thank you,
> Tim
>

[Xsltforms-support] RDF/XML support

[Tim T. <tim...@gm...>]

Hello,

I am trying to load an RDF/XML ontology as an instance document, but am
receiving an error message of "unsupported mediatype
'application/rdf+xml'."

I see the part in xsltforms.js that is checking for valid mediatypes, but
I'm not sure how to modify it to accept this as valid XML.

Thank you,
Tim

Re: [Xsltforms-support] Xsltforms minor bug since r560

[Alain C. <ala...@ag...>]

Hello Javier,

Because this new parameter is not the last one when @if, @while or 
@iterate are provided, every function call needs it.

I have updated these 3 function calls.

Thanks a lot!

-Alain

Le 05/03/2015 08:58, Javier Díaz a écrit :
> Hello,
>
> I have noticed that in change r560, new parameter 'properties' was
> included in javascript function 'XsltForms_dispatch', but in some
> invocations no new parameter was added. Nothing fails to me, but i think
> it should be corrected changing the following:
>
> $ svn diff -x -ubw xsltforms.xsl
> Index: xsltforms.xsl
> ===================================================================
> --- xsltforms.xsl       (revisión: 610)
> +++ xsltforms.xsl       (copia de trabajo)
> @@ -4306,7 +4306,7 @@
>                                                  <xsl:value-of
> select="local-name()"/>
>                                                  <xsl:text>",</xsl:text>
>                                                  <xsl:call-template
> name="toScriptParam"><xsl:with-param name="p"
> select="@model"/></xsl:call-template>
> -                                               <xsl:text>,</xsl:text>
> +                                               <xsl:text>,null,</xsl:text>
>                                                  <xsl:call-template
> name="toScriptParam"><xsl:with-param name="p"
> select="@if"/></xsl:call-template>
>                                                  <xsl:text>,</xsl:text>
>                                                  <xsl:call-template
> name="toScriptParam"><xsl:with-param name="p"
> select="@while"/></xsl:call-template>
> @@ -4468,7 +4468,7 @@
>                                                  <xsl:call-template
> name="toScriptParam"><xsl:with-param name="p"
> select="$control"/></xsl:call-template>
>                                          </xsl:otherwise>
>                                  </xsl:choose>
> -                               <xsl:text>,</xsl:text>
> +                               <xsl:text>,null,</xsl:text>
>                                  <xsl:call-template
> name="toScriptParam"><xsl:with-param name="p"
> select="@if"/></xsl:call-template>
>                                  <xsl:text>,</xsl:text>
>                                  <xsl:call-template
> name="toScriptParam"><xsl:with-param name="p"
> select="@while"/></xsl:call-template>
> @@ -4867,7 +4867,7 @@
>                                  <xsl:value-of select="$vn_subform"/>
>                                  <xsl:text>,"xforms-submit",</xsl:text>
>                                  <xsl:call-template
> name="toScriptParam"><xsl:with-param name="p"
> select="@submission"/></xsl:call-template>
> -                               <xsl:text>,</xsl:text>
> +                               <xsl:text>,null,</xsl:text>
>                                  <xsl:call-template
> name="toScriptParam"><xsl:with-param name="p"
> select="@if"/></xsl:call-template>
>                                  <xsl:text>,</xsl:text>
>                                  <xsl:call-template
> name="toScriptParam"><xsl:with-param name="p"
> select="@while"/></xsl:call-template>
>
>
> ------------------------------------------------------------------------------
> 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

Re: [Xsltforms-support] Xsltforms minor fix

[Alain C. <ala...@ag...>]

Hello Javier,

Thank you very much for this minor fix which will be committed in next 
revision!

--Alain

Le 05/03/2015 09:20, Javier Díaz a écrit :
> Hello,
>
> another change (i don't know if it is a better way to share this than
> using this maillist).
>
> When a get submission is done where instance parameters are passed in
> url, if xsltforms instance is empty (because form is still empty), no
> data is appended to url but the separator is always included at the end
> of url.
>
> It is necessary to validate if there is any data to avoid include the
> separator when it isn't needed:
>
> $ svn diff xsltforms.js
> Index: xsltforms.js
> ===================================================================
> --- xsltforms.js        (revisión: 610)
> +++ xsltforms.js        (copia de trabajo)
> @@ -8090,8 +8090,10 @@
>                  }
>                  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) +
> +                       if (tourl.length > 0) {
> +                           action += (action.indexOf('?') === -1? '?' :
> this.separator) +
>                                  tourl.substr(0, tourl.length -
> this.separator.length);
> +                       }
>                  }
>          }
>          var ser = "";
>
>
> ------------------------------------------------------------------------------
> 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

Re: [Xsltforms-support] Mediatype and Output Element

[Alain C. <ala...@ag...>]

Hello Greg,
> Hi,
>
> I'm trying to use some Xforms-based pages for a little project at my 
> job place. However,  I'm having some trouble with the output element.
>
> The Setup:
>
> I have a set of elements in my instance data that contain (x)HTML markup.
>
> I want to conditionally show these elements (with their markup 
> rendered) in the Xform based on some form selections.
>
> Getting an output element to show plain text is a snap. But I'm having 
> trouble getting HTML to come through.
>
> The Questions:
>
> - Does support the mediatype attribute for output elements?
>
application/xhtml+xml, image/svg+xml and image/* are supported by XSLTForms.
>
> - Is XsltForms an Xform 1.0 or 1.1 implementation?
>
XSLTForms is an XForms 1.1 implementation with some XForms 2.0 features. 
XSLTForms is not 100% compliant because of restrictions due to 
client-side limitations or, just, lack of time for "minor" features and 
higher-priority extensions (RTE,...).
>
> - What do I need to do to the markup content in the instance to make 
> it compatible for display (CDATA, encode HTML entities, etc...)?
>
XSLTForms, previously, was able to produce XHTML or HTML. Since XHTML is 
not well appreciated by browsers, it now generates HTML. As a 
consequence, output control is implemented using .innerHTML property:

  * application/xhtml+xml can also be used for HTML tags soup (XSLTForms
    does not check whether the content is valid or not)
  * content is treated as serialized (X)HTML which means that it is just
    text (not CDATA) from the XML point of view to be serialized with
    < and > entities for tags
  * an instance element has to be serialized with serialize(node) XPath
    function

What do you think?

Thanks!

--Alain

[Xsltforms-support] Xsltforms minor fix

[Javier D. <jd...@tc...>]

Hello,

another change (i don't know if it is a better way to share this than
using this maillist).

When a get submission is done where instance parameters are passed in
url, if xsltforms instance is empty (because form is still empty), no
data is appended to url but the separator is always included at the end
of url.

It is necessary to validate if there is any data to avoid include the
separator when it isn't needed:

$ svn diff xsltforms.js
Index: xsltforms.js
===================================================================
--- xsltforms.js        (revisión: 610)
+++ xsltforms.js        (copia de trabajo)
@@ -8090,8 +8090,10 @@
                }
                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) +
+                       if (tourl.length > 0) {
+                           action += (action.indexOf('?') === -1? '?' :
this.separator) +
                                tourl.substr(0, tourl.length -
this.separator.length);
+                       }
                }
        }
        var ser = "";

[Xsltforms-support] Xsltforms minor bug since r560

[Javier D. <jd...@tc...>]

Hello,

I have noticed that in change r560, new parameter 'properties' was
included in javascript function 'XsltForms_dispatch', but in some
invocations no new parameter was added. Nothing fails to me, but i think
it should be corrected changing the following:

$ svn diff -x -ubw xsltforms.xsl
Index: xsltforms.xsl
===================================================================
--- xsltforms.xsl       (revisión: 610)
+++ xsltforms.xsl       (copia de trabajo)
@@ -4306,7 +4306,7 @@
                                                <xsl:value-of
select="local-name()"/>
                                                <xsl:text>",</xsl:text>
                                                <xsl:call-template
name="toScriptParam"><xsl:with-param name="p"
select="@model"/></xsl:call-template>
-                                               <xsl:text>,</xsl:text>
+                                               <xsl:text>,null,</xsl:text>
                                                <xsl:call-template
name="toScriptParam"><xsl:with-param name="p"
select="@if"/></xsl:call-template>
                                                <xsl:text>,</xsl:text>
                                                <xsl:call-template
name="toScriptParam"><xsl:with-param name="p"
select="@while"/></xsl:call-template>
@@ -4468,7 +4468,7 @@
                                                <xsl:call-template
name="toScriptParam"><xsl:with-param name="p"
select="$control"/></xsl:call-template>
                                        </xsl:otherwise>
                                </xsl:choose>
-                               <xsl:text>,</xsl:text>
+                               <xsl:text>,null,</xsl:text>
                                <xsl:call-template
name="toScriptParam"><xsl:with-param name="p"
select="@if"/></xsl:call-template>
                                <xsl:text>,</xsl:text>
                                <xsl:call-template
name="toScriptParam"><xsl:with-param name="p"
select="@while"/></xsl:call-template>
@@ -4867,7 +4867,7 @@
                                <xsl:value-of select="$vn_subform"/>
                                <xsl:text>,"xforms-submit",</xsl:text>
                                <xsl:call-template
name="toScriptParam"><xsl:with-param name="p"
select="@submission"/></xsl:call-template>
-                               <xsl:text>,</xsl:text>
+                               <xsl:text>,null,</xsl:text>
                                <xsl:call-template
name="toScriptParam"><xsl:with-param name="p"
select="@if"/></xsl:call-template>
                                <xsl:text>,</xsl:text>
                                <xsl:call-template
name="toScriptParam"><xsl:with-param name="p"
select="@while"/></xsl:call-template>

[Xsltforms-support] Mediatype and Output Element

[Gregory R. <gra...@ou...>]

Hi,
I'm trying to use some Xforms-based pages for a 
little project at my job place. However,  I'm having some trouble with 
the output element.
 
The Setup:
I have a set of elements in my instance data that contain (x)HTML markup.

 
I want to conditionally show these elements (with their markup rendered) in the Xform based on some form selections.

 
Getting an output element to show plain text is a snap. But I'm having trouble getting HTML to come through.

 
The Questions:
- Does support the mediatype attribute for output elements?
- Is XsltForms an Xform 1.0 or 1.1 implementation?
- What do I need to do to the markup content in 
the instance to make it compatible for display (CDATA, encode HTML 
entities, etc...)?

 
Thanks,
Greg R

 		 	   		  

Re: [Xsltforms-support] In IE11 in secure mode (https) a call to document.write fails

[Javier D. <jd...@tc...>]

Hello,

although I use an old xsltforms version (r574) I have the same error
using IE10 (we are tring to support IE10 in our xsltforms web): "HTTPS
security is compromised by (null)". I think this problem still appears
in newest version.

I have no problem with IE8, Firefox and Chrome. All the web is using
https, and no http request is done.

We have the problem in two situations:
* Using asynchronous submissions. To avoid the problem I have change js
code to force synchronous request in IE10:

        isIE9 : navigator.userAgent.match(/\bMSIE\b/) &&
!navigator.userAgent.match(/\bOpera\b/) && window.addEventListener,
+       isIE10 : navigator.userAgent.match(/\bMSIE\b/) && window.FileReader,
        isIE6 : navigator.userAgent.match(/\bMSIE 6\.0/),

-------
        this.synchr = synchr;
+       //jde - Tenemos problemas con el modo asíncrono en Explorer 10,
lo hacemos siempre síncrono
+       if (XsltForms_browser.isIE10) {
+           this.synchr = true;
+       }
        this.show = show;

I don't know if it is a better way to solve this problem, it works for me.

* Using triggers to make submissions that replace form:

I have in model:

<xf:submission id="ver_detalle" method="get" validate="false()"
ref="instance('tareaSeleccionada')" replace="all"
resource="WGOLIATH/TAREAS/detalleTarea.xml">

And in view:

<xf:action ev:event="DOMActivate">
    <xf:setvalue ref="instance('tareaSeleccionada')/tareaSeleccionada"
model="datos" value="instance('tareas')/tarea
s_generadas/vct[index('lista-tareas-generadas')]/elm[1]"/>
    <xf:send submission="ver_detalle"/>
</xf:action>

Debugging code, when new html replaces old one with document.write
method, error SEC7111 appears. When using a submit control it works ok:

<xf:submit submission="enviar">
     <xf:label>Generar</xf:label>
</xf:submit>

Unfortunately, not always it is possible to use it, when some aditional
logic it is necessary.

To solve this problem, I forced to open the result in a new window. It
is not a good solution, but at least, web page is usable.

+       if (XsltForms_browser.isIE10 && this.replace === "all") {
+           this.show = "new";
+       }

Another way to solve the problem is to force IE8 compatibility using the
following:

<meta http-equiv="X-UA-Compatible" content="IE=EmulateIE8"/>

But it causes not being able to use FileReader API to upload files.

Do you know any other better way to solve this problems?

Best Regards,
Javier

El 17/11/14 a las 23:24, lk...@li... escribió:
> Alain,
> I saw the MS docs on SEC7111, but in this particular case it's not
> mixed content. As a matter of fact, the error displayed does not have
> a reference to offending resource (as it should) It shows: "|HTTPS
> security is compromised by (null)"|
>
> The content that server returns, and that document.write fails on is
> <script type="text/javascript"> window.location.href="FULL URL HERE
> WITH HTTPS protocol"; </script>. We did try writing out a full HTML
> page - same results
>
> The only mention of similar problem I could find was in BIG-IP support
> forum, listing a similar
> error:https://support.f5.com/kb/en-us/products/big-ip_apm/manuals/product/windows-81-ki-suppl-doc.html
> (Issue 437652)
>
> Hope this helps.
>
> --Leonid
>
> ------------------------------------------------------------------------
> *From: *"alain couthures" <ala...@ag...>
> *To: *lk...@li..., xsl...@li...
> *Sent: *Monday, November 17, 2014 2:39:15 PM
> *Subject: *Re: [Xsltforms-support] In IE11 in secure mode (https) a
> call to document.write fails
>
> Leonid,
>  
> Apparently, it might be due to mixed content HTTP/HTTPS
> (http://forums.asp.net/t/1777899.aspx?SEC7111+HTTPS+security+is+compromised).
>
>  
> What do you think?
>  
> --Alain
>
>     Le 17 novembre 2014 à 16:43, lk...@li... a écrit :
>
>     Alain,
>     As we tested our application that uses XSLTForms 1.0 RC2 we
>     discovered a really bad bug. I'm pretty sure that is a bug with
>     IE11, and not with XSLTForms, but the result is that forms
>     submissions under IE11 in HTTPS mode do not work.
>     Here is what happens. A form in the synchronous mode gets
>     submitted to the back-end, processed, and a new page is returned
>     successfully. At this time xsltforms.js executes function defined
>     on line 8120. Then, after some checks it gets to line 8178 which
>     replaces content of the form page with whatever the server
>     returned. In all browsers, except IE11 it works fine. IE11 throws
>     a security error SEC7111, and stops JavaScript processing.
>
>     I'm not sure if you can do anything about it, but thought it would
>     be a good idea to let other people know about it. We temporarily
>     added specific code to use window.open() for IE11 to bypass the
>     issue, but it is not a generic solution as we know what URL is the
>     next page.
>
>     Thanks for your work!
>
>     Leonid Kagan, CTO
>     Life Data Systems,Inc.
>     Confidentiality Note: This message is intended for use only by the
>     individual or entity to which it is addressed and may contain
>     information that is privileged, confidential, and exempt from
>     disclosure under applicable law.
>
>
>  
>
>     ------------------------------------------------------------------------------
>
>     Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
>     from Actuate! Instantly Supercharge Your Business Reports and
>     Dashboards
>     with Interactivity, Sharing, Native Excel Exports, App Integration
>     & more
>     Get technology previously reserved for billion-dollar
>     corporations, FREE
>     http://pubads.g.doubleclick.net/gampad/clk?id=157005751&iu=/4140/ostg.clktrk_______________________________________________
>
>     Xsltforms-support mailing list
>     Xsl...@li...
>     https://lists.sourceforge.net/lists/listinfo/xsltforms-support 
>
>
>  
>
>
>
> ------------------------------------------------------------------------------
> Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
> from Actuate! Instantly Supercharge Your Business Reports and Dashboards
> with Interactivity, Sharing, Native Excel Exports, App Integration & more
> Get technology previously reserved for billion-dollar corporations, FREE
> http://pubads.g.doubleclick.net/gampad/clk?id=157005751&iu=/4140/ostg.clktrk
>
>
> _______________________________________________
> Xsltforms-support mailing list
> Xsl...@li...
> https://lists.sourceforge.net/lists/listinfo/xsltforms-support

[Xsltforms-support] XSLTForms server-side in eXist 2.2

[Tim T. <tim...@gm...>]

Hello,

I am attempting to run XSLTForms (r609) using a server-side controller
pipeline[1] in eXist 2.2 with submissions to RESTXQ.

My main XForms loads correctly, but when I submit data to my RESTXQ
function and return the response, the transformation does not fire again. I
am generating a new XForms document in XQuery and returning it to the
XForms, with a value of @replace = "all" on the xf:submission element.

Is there a way to get server-side processing to work when returning a new
XForms document like this? It works if I use a transformation function, but
I would prefer to follow a uniform approach. I was using the client-side
transformation, but was experience some minor performance issues: my XForms
submission is querying a Web API and pulling in data, and there seemed to
be a noticeable lag when the page reloaded using the client-side
transformation.

Thanks in advance,
Tim

[1] Following the documentation at <
http://www.exist-db.org/exist/apps/doc/xforms.xml#D1.2.5.3>, though it
seems to be for an earlier version of eXist.

Re: [Xsltforms-support] Editing dynamically imported data

[<ala...@ag...>]

Hello Tim,
 
This alert has been removed recently.
 
Could you please give a try to latest build rev.609 which can be downloaded from
both Sourceforge and GitHub repositories?
 
Thank you for your feedback!
 
--Alain

> Le 16 février 2015 à 14:04, Tim Thompson <tim...@gm...> a écrit :
> 
>  Hello,
> 
>  With XSLTForms in eXist 2.2, I am trying to load data from a Web service and
> edit it in XForms. In my model, I have an empty instance that gets populated
> with the imported data:
> 
>  <xf:instance xmlns="" id="results">
>  <results></results>
>  </xf:instance>
> 
>  In the form body, I have some controls that reference the data to be
> imported:
> 
>  <xf:group ref="instance('results')" id="import">
>  <xf:repeat
> nodeset="oclc-sru:record/oclc-sru:recordData/marc:record/marc:datafield[@tag =
> '245']"
>  appearance="compact" bind="marcBind">
>  <xf:input ref="marc:subfield[@code = 'a']">
>  <xf:label>Title </xf:label>
>  </xf:input>
>  </xf:repeat>
>  </xf:group>
> 
>  However, when I import the data and the new <xf:input> control appears, I am
> not able to edit it successfully. When the focus changes from the new
> <xf:input> control, I get a JavaScript error and an alert message stating,
> "Blur?". How should I address this error?
> 
>  Thank you,
>  Tim
> 
> ------------------------------------------------------------------------------
>  Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
>  from Actuate! Instantly Supercharge Your Business Reports and Dashboards
>  with Interactivity, Sharing, Native Excel Exports, App Integration & more
>  Get technology previously reserved for billion-dollar corporations, FREE
> 
> http://pubads.g.doubleclick.net/gampad/clk?id=190641631&iu=/4140/ostg.clktrk_______________________________________________
>  Xsltforms-support mailing list
>  Xsl...@li...
>  https://lists.sourceforge.net/lists/listinfo/xsltforms-support
> 

Re: [Xsltforms-support] Editing dynamically imported data

[Tim T. <tim...@gm...>]

Maybe this is the same issue that was raised in a previous thread:
http://sourceforge.net/p/xsltforms/mailman/message/32330761/ regarding r595?

The orginal post mentioned Safari, but I'm getting the "Blur?" alert in
Firefox and Chrome as well.

Tim


On Mon, Feb 16, 2015 at 8:04 AM, Tim Thompson <tim...@gm...> wrote:

> Hello,
>
> With XSLTForms in eXist 2.2, I am trying to load data from a Web service
> and edit it in XForms. In my model, I have an empty instance that gets
> populated with the imported data:
>
> <xf:instance xmlns="" id="results">
>     <results></results>
> </xf:instance>
>
> In the form body, I have some controls that reference the data to be
> imported:
>
> <xf:group ref="instance('results')" id="import">
>     <xf:repeat
> nodeset="oclc-sru:record/oclc-sru:recordData/marc:record/marc:datafield[@tag
> = '245']"
>     appearance="compact" bind="marcBind">
>         <xf:input ref="marc:subfield[@code = 'a']">
>             <xf:label>Title </xf:label>
>         </xf:input>
>     </xf:repeat>
> </xf:group>
>
> However, when I import the data and the new <xf:input> control appears, I
> am not able to edit it successfully. When the focus changes from the new
> <xf:input> control, I get a JavaScript error and an alert message stating,
> "Blur?". How should I address this error?
>
> Thank you,
> Tim
>

[Xsltforms-support] Editing dynamically imported data

[Tim T. <tim...@gm...>]

Hello,

With XSLTForms in eXist 2.2, I am trying to load data from a Web service
and edit it in XForms. In my model, I have an empty instance that gets
populated with the imported data:

<xf:instance xmlns="" id="results">
    <results></results>
</xf:instance>

In the form body, I have some controls that reference the data to be
imported:

<xf:group ref="instance('results')" id="import">
    <xf:repeat
nodeset="oclc-sru:record/oclc-sru:recordData/marc:record/marc:datafield[@tag
= '245']"
    appearance="compact" bind="marcBind">
        <xf:input ref="marc:subfield[@code = 'a']">
            <xf:label>Title </xf:label>
        </xf:input>
    </xf:repeat>
</xf:group>

However, when I import the data and the new <xf:input> control appears, I
am not able to edit it successfully. When the focus changes from the new
<xf:input> control, I get a JavaScript error and an alert message stating,
"Blur?". How should I address this error?

Thank you,
Tim

Re: [Xsltforms-support] Incorrect event sequencing for xf:input?

[Alain C. <ala...@ag...>]

Hello Mats,

I have investigated: this timer is inherited from AjaxForms.

I cannot say why it was added but I guess it was due to very old 
browsers support.

Event management is still difficult and it is interesting to have a more 
compliant behavior removing this timer.

Thanks!

--Alain

Le 30/01/2015 23:05, Mats Eklund a écrit :
> Hi,
>
> I'm trying to implement a form with an input field that has a hint 
> text shown within the field. The hint text should disappear when the 
> field is given focus by the user, and reappear upon loosing focus if 
> the field is left empty by the user.
>
> Here's an example form.
>
> <?xml version="1.0" encoding="UTF-8"?>
> <?xml-stylesheet href="xsltforms/xsltforms.xsl" type="text/xsl"?>
> <?xsltforms-options debug="yes"?>
> <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">
>     <head>
>         <title>Testing xf:input field with hint inline</title>
>         <xf:model>
>             <xf:instance>
>                 <myfields xmlns="">
>                     <search hint="Type here..."/>
>                 </myfields>
>             </xf:instance>
>             <xf:setvalue ev:event="xforms-model-construct-done" 
> ref="search" value="@hint"/>
>         </xf:model>
>     </head>
>     <body>
>         <xf:input ref="search">
>             <xf:label/>
>             <xf:setvalue ev:event="DOMFocusIn"  ref="." if=".=@hint"  
> value="''"/>
>             <xf:setvalue ev:event="DOMFocusOut" ref="." if=".=''"     
> value="@hint"/>
>         </xf:input>
>     </body>
> </html>
>
> I don't get this to work though. The hint reappears whenever the field 
> looses focus, whether user leaves it empty or not. I suspect this is 
> because XSLTForms seems to trigger the xforms-value-changed event and 
> updates the instance data only after triggering the DOMFocusOut event. 
> This seems not to be in accordance with the XForms spec 
> (http://www.w3.org/TR/2003/REC-xforms-20031014/slice4.html#rpm-event-seq-vcwfc). 
>
>
> I had a look within xsltforms.js, and noticed a deferred call 
> (setTimeout()) within XsltForms_control.blurHandler(), and suspect 
> this may be the problem. If I unwrapped the setTimeout() call, the 
> form worked fine. But I'm not sure if this has other side-effects, or 
> why there was a setTimeout() in the first place.
>
> Thanks in advance for any suggestions!
>
> Mats
>
>
>
>
> ------------------------------------------------------------------------------
> 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

Re: [Xsltforms-support] Problem with checkboxes in xf:repeat

[<ala...@ag...>]

Hello Tim,
 
XForms allows to have the same node being bound to many controls and all of
these controls, as a consequence, are synchronized on updates.
 
In your example, there is just one off element in a distinct instance. When an
input control is bound to this element within a repeat, the XForms engine is
rendering as many identical controls as nodes in the repeat node set.
 
I guess that you want to check records: for this, you need, for example, a
dedicated attribute within each record. This can be done with XForms actions:
each time the records instance is retrieved from the server, an associated
action can insert such an attribute. With eXistdb, it might be easier to ask the
server to generate the records instance with this extra attribute.
 
Thank you for your feedback!
 
--Alain

> Le 7 février 2015 à 16:02, Tim Thompson <tim...@gm...> a écrit :
> 
>  Hello,
> 
>  I am new to XForms and am using XSLTForms in eXist 2.2 to work on an XRX app
> with RESTXQ.
> 
>  I have a search form that lets users query a remote API, which responds with
> a set of XML records if the query is matched. I am using xf:repeat to output
> content from the records, and I want to be able to provide a checkbox at the
> start of each record, so that the user can choose. However, when I place a
> checkbox inside the repeat (using xf:input bound to a boolean), I don't get
> the desired functionality. Instead of being independent of each other, the
> checkboxes get activated as a group. When I click the first box, the second
> box is activated as well, etc.
> 
>  Model:
> 
>  <xf:instance xmlns="" id="test">
>  <data>
>  <off>false</off>
>  </data>
>  </xf:instance>
> 
>  <xf:bind nodeset="instance('test')/off" id="offVal" type="xs:boolean"/>
>   
>  Form:
> 
>  <div>
>  <xf:repeat
> nodeset="instance('default')/sru:searchRetrieveResponse/sru:records/sru:record"
> id="marc-repeat" appearance="full">
>  <div class="checkbox">
>  <xf:input incremental="true" ref="instance('test')/off">
>  <xf:label>Select</xf:label>
>  </xf:input>
>  </div>
>  ...
>  </xf:repeat>
>  </div>
>   
>  Thanks in advance,
>  Tim
>   
> 
> ------------------------------------------------------------------------------
>  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
> 

[Xsltforms-support] Problem with checkboxes in xf:repeat

[Tim T. <tim...@gm...>]

Hello,

I am new to XForms and am using XSLTForms in eXist 2.2 to work on an XRX
app with RESTXQ.

I have a search form that lets users query a remote API, which responds
with a set of XML records if the query is matched. I am using xf:repeat to
output content from the records, and I want to be able to provide a
checkbox at the start of each record, so that the user can choose. However,
when I place a checkbox inside the repeat (using xf:input bound to a
boolean), I don't get the desired functionality. Instead of being
independent of each other, the checkboxes get activated as a group. When I
click the first box, the second box is activated as well, etc.

Model:

<xf:instance xmlns="" id="test">
    <data>
        <off>false</off>
    </data>
</xf:instance>

<xf:bind nodeset="instance('test')/off" id="offVal" type="xs:boolean"/>

Form:

<div>
    <xf:repeat
nodeset="instance('default')/sru:searchRetrieveResponse/sru:records/sru:record"
id="marc-repeat" appearance="full">
        <div class="checkbox">
            <xf:input incremental="true" ref="instance('test')/off">

<xf:label>Select</xf:label>
            </xf:input>
        </div>
        ...
    </xf:repeat>
</div>

Thanks in advance,
Tim

[Xsltforms-support] Incorrect event sequencing for xf:input?

[Mats E. <mat...@ya...>]

Hi,
I'm trying to implement a form with an input field that has a hint text shown within the field. The hint text should disappear when the field is given focus by the user, and reappear upon loosing focus if the field is left empty by the user.

Here's an example form.

<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet href="xsltforms/xsltforms.xsl" type="text/xsl"?>
<?xsltforms-options debug="yes"?>
<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">
    <head>
        <title>Testing xf:input field with hint inline</title>
        <xf:model> 
            <xf:instance>
                <myfields xmlns="">
                    <search hint="Type here..."/>
                </myfields>
            </xf:instance>
            <xf:setvalue ev:event="xforms-model-construct-done" ref="search" value="@hint"/>
        </xf:model>
    </head>
    <body>
        <xf:input ref="search">
            <xf:label/>
            <xf:setvalue ev:event="DOMFocusIn"  ref="." if=".=@hint"  value="''"/>
            <xf:setvalue ev:event="DOMFocusOut" ref="." if=".=''"     value="@hint"/>
        </xf:input>
    </body>
</html>

I don't get this to work though. The hint reappears whenever the field looses focus, whether user leaves it empty or not. I suspect this is because XSLTForms seems to trigger the xforms-value-changed event and updates the instance data only after triggering the DOMFocusOut event. This seems not to be in accordance with the XForms spec (http://www.w3.org/TR/2003/REC-xforms-20031014/slice4.html#rpm-event-seq-vcwfc). 

I had a look within xsltforms.js, and noticed a deferred call (setTimeout()) within XsltForms_control.blurHandler(), and suspect this may be the problem. If I unwrapped the setTimeout() call, the form worked fine. But I'm not sure if this has other side-effects, or why there was a setTimeout() in the first place.

Thanks in advance for any suggestions!
Mats

Re: [Xsltforms-support] In IE11 in secure mode (https) a call to document.write fails

[<lk...@li...>]

Alain, 
I saw the MS docs on SEC7111, but in this particular case it's not mixed content. As a matter of fact, the error displayed does not have a reference to offending resource (as it should) It shows: " HTTPS security is compromised by (null)" 

The content that server returns, and that document.write fails on is <script type="text/javascript"> window.location.href=" FULL URL HERE WITH HTTPS protocol "; </script> . We did try writing out a full HTML page - same results 

The only mention of similar problem I could find was in BIG-IP support forum, listing a similar error: https://support.f5.com/kb/en-us/products/big-ip_apm/manuals/product/windows-81-ki-suppl-doc.html (Issue 437652 ) 

Hope this helps. 

--Leonid 

----- Original Message -----

From: "alain couthures" <ala...@ag...> 
To: lk...@li..., xsl...@li... 
Sent: Monday, November 17, 2014 2:39:15 PM 
Subject: Re: [Xsltforms-support] In IE11 in secure mode (https) a call to document.write fails 


Leonid, 

Apparently, it might be due to mixed content HTTP/HTTPS (http://forums.asp.net/t/1777899.aspx?SEC7111+HTTPS+security+is+compromised). 

What do you think? 

--Alain 

Le 17 novembre 2014 à 16:43, lk...@li... a écrit : 


Alain, 
As we tested our application that uses XSLTForms 1.0 RC2 we discovered a really bad bug. I'm pretty sure that is a bug with IE11, and not with XSLTForms, but the result is that forms submissions under IE11 in HTTPS mode do not work. 
Here is what happens. A form in the synchronous mode gets submitted to the back-end, processed, and a new page is returned successfully. At this time xsltforms.js executes function defined on line 8120. Then, after some checks it gets to line 8178 which replaces content of the form page with whatever the server returned. In all browsers, except IE11 it works fine. IE11 throws a security error SEC7111, and stops JavaScript processing. 

I'm not sure if you can do anything about it, but thought it would be a good idea to let other people know about it. We temporarily added specific code to use window.open() for IE11 to bypass the issue, but it is not a generic solution as we know what URL is the next page. 

Thanks for your work! 


Leonid Kagan, CTO 
Life Data Systems,Inc. 
Confidentiality Note: This message is intended for use only by the individual or entity to which it is addressed and may contain information that is privileged, confidential, and exempt from disclosure under applicable law. 





<blockquote>
------------------------------------------------------------------------------ 
Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server 
from Actuate! Instantly Supercharge Your Business Reports and Dashboards 
with Interactivity, Sharing, Native Excel Exports, App Integration & more 
Get technology previously reserved for billion-dollar corporations, FREE 
http://pubads.g.doubleclick.net/gampad/clk?id=157005751&iu=/4140/ostg.clktrk_______________________________________________ 
Xsltforms-support mailing list 
Xsl...@li... 
https://lists.sourceforge.net/lists/listinfo/xsltforms-support 
</blockquote>

Re: [Xsltforms-support] In IE11 in secure mode (https) a call to document.write fails

[<ala...@ag...>]

Leonid,
 
Apparently, it might be due to mixed content HTTP/HTTPS
(http://forums.asp.net/t/1777899.aspx?SEC7111+HTTPS+security+is+compromised).
 
What do you think?
 
--Alain

> Le 17 novembre 2014 à 16:43, lk...@li... a écrit :
> 
>  Alain,
>  As we tested our application that uses XSLTForms 1.0 RC2 we discovered a
> really bad bug. I'm pretty sure that is a bug with IE11, and not with
> XSLTForms, but the result is that forms submissions under IE11 in HTTPS mode
> do not work.
>  Here is what happens. A form in the synchronous mode gets submitted to the
> back-end, processed, and a new page is returned successfully. At this time
> xsltforms.js executes function defined on line 8120. Then, after some checks
> it gets to line 8178 which replaces content of the form page with whatever the
> server returned. In all browsers, except IE11 it works fine. IE11 throws a
> security error SEC7111, and stops JavaScript processing.
> 
>  I'm not sure if you can do anything about it, but thought it would be a good
> idea to let other people know about it. We temporarily added specific code to
> use window.open() for IE11 to bypass the issue, but it is not a generic
> solution as we know what URL is the next page.
> 
>  Thanks for your work!
> 
>  Leonid Kagan, CTO
>  Life Data Systems,Inc.
>  Confidentiality Note: This message is intended for use only by the individual
> or entity to which it is addressed and may contain information that is
> privileged, confidential, and exempt from disclosure under applicable law.
> 

 

> ------------------------------------------------------------------------------
>  Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
>  from Actuate! Instantly Supercharge Your Business Reports and Dashboards
>  with Interactivity, Sharing, Native Excel Exports, App Integration & more
>  Get technology previously reserved for billion-dollar corporations, FREE
> 
> http://pubads.g.doubleclick.net/gampad/clk?id=157005751&iu=/4140/ostg.clktrk_______________________________________________
>  Xsltforms-support mailing list
>  Xsl...@li...
>  https://lists.sourceforge.net/lists/listinfo/xsltforms-support
> 

[Xsltforms-support] In IE11 in secure mode (https) a call to document.write fails

[<lk...@li...>]

Alain, 
As we tested our application that uses XSLTForms 1.0 RC2 we discovered a really bad bug. I'm pretty sure that is a bug with IE11, and not with XSLTForms, but the result is that forms submissions under IE11 in HTTPS mode do not work. 
Here is what happens. A form in the synchronous mode gets submitted to the back-end, processed, and a new page is returned successfully. At this time xsltforms.js executes function defined on line 8120. Then, after some checks it gets to line 8178 which replaces content of the form page with whatever the server returned. In all browsers, except IE11 it works fine. IE11 throws a security error SEC7111, and stops JavaScript processing. 

I'm not sure if you can do anything about it, but thought it would be a good idea to let other people know about it. We temporarily added specific code to use window.open() for IE11 to bypass the issue, but it is not a generic solution as we know what URL is the next page. 

Thanks for your work! 


Leonid Kagan, CTO 
Life Data Systems,Inc. 
Confidentiality Note: This message is intended for use only by the individual or entity to which it is addressed and may contain information that is privileged, confidential, and exempt from disclosure under applicable law. 

Re: [Xsltforms-support] Fwd: select1 selection="open"

[<bvi...@la...>]

Hi Alain, 

I wouldn't say that I'm hurry because I use efficiently XSLTForms since 3 years without this option but now I start designing new forms with fields like tags or symbols. They allow users to type any existing (or new) keyword but open select1 could help to auto-complete values and avoid typos. 
I also tried to activate browsers internal auto-complete feature but since input controls are not inside <form/> markup it doesn't works. 

Thank you for your interest. 

Benoit 


Le 10/11/2014 19:06, ala...@ag... a écrit : 



Hi Benoit, 
This is an interesting suggestion and browser support does not sound bad with IE10, for example. 
I need some time for implementing and testing this. Are you in a hurry? 
Thanks! 
--Alain 

> Le 8 novembre 2014 à 12:10, Benoit VINCENT <bvi...@la...> a écrit : 
> 
> 
> 
> Hi Alain, 
> 
> It would be very useful for our application to have the <xf:select1 
> selection="open" /> implemented in XSLTForms. I searched on the web 
> and found that, now, with HTML 5 it's very easy to have a combobox 
> without coding anything in javascript : 
> 
> example : 
> 
> <input type="text" list="browsers" /> 
> <datalist id="browsers" > 
> <option> Google </option> 
> <option> IE9 </option> 
> </datalist> 
> 
> I think it could be possible to implement <xf:select1 selection="open" /> in XSLTForms by merging the existing code of xf:input (for the field) 
> and the xf:select1 (for the options list). I tried some quick and dirty tests and it seems to work for modern browsers. 
> I try to generate the HTML with a template like this : 
> 
> <xsl:template xmlns:xsl= "http://www.w3.org/1999/XSL/Transform" match="xforms:select1[@selection='open']" priority="3"> 
> <xsl:param name="appearance" select="false()"/> 
> <xsl:param name="parentworkid"/> 
> <xsl:param name="workid" select="concat(position(),'_',$parentworkid)"/> 
> <xsl:call-template name="field"> 
> <xsl:with-param name="workid" select="$workid"/> 
> <xsl:with-param name="appearance" select="$appearance"/> 
> <xsl:with-param name="body"> 
> <input type="text" list="datalist-{$workid}"> 
> <xsl:call-template name="comun"/> 
> </input> 
> <datalist id="datalist-{$workid}"> 
> <xsl:apply-templates select="node()" mode="item"> 
> <xsl:with-param name="parentworkid" select="$workid"/> 
> </xsl:apply-templates> 
> </datalist> 
> </xsl:with-param> 
> </xsl:call-template> 
> </xsl:template> 
> 
> 
> but I have not enough skills to modify the javascript generation code. I'm stuck ! 
> 
> Do you think that it would be possible to have this feature in XSLTForms (at least for HTML 5 browser)? 
> 
> Thank you for your help. 
> 
> Benoit 
> 
> 
> 
> 
> 
> ------------------------------------------------------------------------------ 
> _______________________________________________ 
> Xsltforms-support mailing list 
> Xsl...@li... 
> https://lists.sourceforge.net/lists/listinfo/xsltforms-support 

Re: [Xsltforms-support] Fwd: select1 selection="open"

[<ala...@ag...>]

Hi Benoit,
 
This is an interesting suggestion and browser support does not sound bad with
IE10, for example.
 
I need some time for implementing and testing this. Are you in a hurry?
 
Thanks!
 
--Alain

> Le 8 novembre 2014 à 12:10, Benoit VINCENT <bvi...@la...> a
> écrit :
>
>
>
> Hi Alain,
>
> It would be very useful for our application to have the <xf:select1
> selection="open" /> implemented in XSLTForms. I searched on the web
> and found that, now, with HTML 5 it's very easy to have a combobox
> without coding anything in javascript :
>
> example :
>
> <input type="text" list="browsers" />
> <datalist id="browsers" >
> <option> Google </option>
> <option> IE9 </option>
> </datalist>
>
> I think it could be possible to implement <xf:select1 selection="open" /> in
> XSLTForms by merging the existing code of xf:input (for the field)
> and the xf:select1 (for the options list). I tried some quick and dirty tests
> and it seems to work for modern browsers.
> I try to generate the HTML with a template like this :
>
> <xsl:template xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
> match="xforms:select1[@selection='open']" priority="3">
> <xsl:param name="appearance" select="false()"/>
> <xsl:param name="parentworkid"/>
> <xsl:param name="workid" select="concat(position(),'_',$parentworkid)"/>
> <xsl:call-template name="field">
> <xsl:with-param name="workid" select="$workid"/>
> <xsl:with-param name="appearance" select="$appearance"/>
> <xsl:with-param name="body">
> <input type="text" list="datalist-{$workid}">
> <xsl:call-template name="comun"/>
> </input>
> <datalist id="datalist-{$workid}">
> <xsl:apply-templates select="node()" mode="item">
> <xsl:with-param name="parentworkid" select="$workid"/>
> </xsl:apply-templates>
> </datalist>
> </xsl:with-param>
> </xsl:call-template>
> </xsl:template>
>
>
> but I have not enough skills to modify the javascript generation code. I'm
> stuck !
>
> Do you think that it would be possible to have this feature in XSLTForms (at
> least for HTML 5 browser)?
>
> Thank you for your help.
>
> Benoit
>
>
>
>
>
> ------------------------------------------------------------------------------
> _______________________________________________
> Xsltforms-support mailing list
> Xsl...@li...
> https://lists.sourceforge.net/lists/listinfo/xsltforms-support