xsltforms-support Mailing List for XSLTForms (Page 70)

SourceForge Headquarters 225 Broadway Suite 1600 San Diego, CA 92101 +1 (858) 422-6466

It would be nice if you'd offer a different way for us to give AgenceXML 
credit.
It's fairly intrusive for a library to take over double click and F1.

Leigh.

Hi,

I am new to XSLTForms and I am not able to generate XForms from a XQuery, the
eXist db complains with the following error code :

2010-12-21 22:52:42,561 [P1-10] DEBUG (XQueryServlet.java [process]:430) -
org.exist.xquery.XPathException: err:XPST0003 in line 18, column 7: unexpected
token: xmlns

Although I have seen this problem raised in previous discussions (1) :  I am not
able to make it work with my configuration which is the following one :
OS : Mac OS 10.5.8
eXist DB : 1.4.0 (build 20091111)

It seems that the following line has no effect on my setup :
declare option exist:serialize "method=xhtml media-type=text/xml
process-xsl-pi=no";

What could I have missed ?

My XQuery file :

xquery version "1.0";

(: data_model_update.xql :)

declare namespace xmldb="http://exist-db.org/xquery/xmldb";
declare namespace request="http://exist-db.org/xquery/request";
declare option exist:serialize "method=xhtml media-type=text/xml
process-xsl-pi=no";

let $table := request:get-data()
let $fichier := concat(data($table/@name),'.xml')

return
(
<?xml-stylesheet href="xsltforms/xsltforms.xsl" type="text/xsl"?>
<html xmlns="http://www.w3.org/1999/xhtml"
xmlns:xf="http://www.w3.org/2002/xforms"
	xmlns:ev="http://www.w3.org/2001/xml-events"
xmlns:xsd="http://www.w3.org/2001/XMLSchema">

	<head>
		<title>Table</title>
		<xf:model>
			<xf:instance id="moninstance" src="../rest/db/{$fichier}">

			</xf:instance>

(1)
http://exist.2174344.n4.nabble.com/Getting-XSLTForms-to-work-with-dynamic-XForms-td2192959.html

-- 
Sylvain PERCHAUD
Tel : +33 643 181 482

Srinivasan,

Try 'separator' instead of 'seperator'?

Fred

Citeren srinivasan krishnamoorthy <sri...@gm...>:

> today am trying to use seperators in xslt forms i face some problem that the
> secon parameter value didnt get by destination form......
>
>
> i use the code shown below...
>
>
> <!--for next button-->
>         <xf:submission id="submit2" resource="samp.xq?start={$start +
> $cnt}&amp;num={$num + $cnt}" seperator="&amp;" method="post">
>         </xf:submission>
>
> how am use seperators in xsltforms.....
>
>
> --
> - yours
>
>          *Srinivasan Krishnamoorthy*
>

today am trying to use seperators in xslt forms i face some problem that the
secon parameter value didnt get by destination form......

i use the code shown below...

<!--for next button-->
        <xf:submission id="submit2" resource="samp.xq?start={$start +
$cnt}&amp;num={$num + $cnt}" seperator="&amp;" method="post">
        </xf:submission>

how am use seperators in xsltforms.....

-- 
- yours

         *Srinivasan Krishnamoorthy*

Hi!

I've read the discussion but cannot sort this out in my mind : is this
performance issue, that you are talking about, due to the fact that we
cannot refresh a single model? I mean the emptiness of the
"XFModel.prototype.refresh"  function at the moment. Or is it not related?

Thanks!
Grégoire

Le 21/12/2010 11:37, Santosh Chandak a écrit :
> Thanks Alain. For our form, we can not remove // from all the places
> because we have nested xml.
> Regarding the solution to refresh select part of the page, I could
> implement it by passing hint on selecting the parent node for a
> particular form control and it is working great. I simply pass a
> number (depending on all the dependencies) on focus event which would
> help in determining the parent node to be refreshed.
> Below is the code snippet -
> A trigger on form has -
> <xf:setvalue ev:event="DOMActivate"
> ref="instance('datapad')/@parentIndex" value="4"/>
>
> And in xsltforms.js -
> XFControl.prototype.focus has -
> xforms.selectedElement = this.element;
>
> refresh method has -
>
> var parentIndex = Util.getParentIndex();         // returns
> instance('datapad')/@parentIndex
>         if(!this.selectedElement || parentIndex == "-1")  {
>             this.selectedElement = this.body; // Can be optimized further
>         } else {
>               for(var i = 0; i < parentIndex; i++) {
>                 this.selectedElement = this.selectedElement.parentNode;
>               }
>         }
>         this.build(this.selectedElement,
> (this.defaultModel.getInstanceDocument() ?
> this.defaultModel.getInstanceDocument().documentElement : null), true);
>         Util.setParentIndex("-1");
>
>
> All we need to do is pass appropriate parentIndex from the form and it
> should resolve the performance issues caused by refreshing the entire
> page. I hope something on these lines can be added to the xsltforms
> library.
>
>
>
>
>
> On Fri, Dec 17, 2010 at 1:00 AM, COUTHURES Alain
> <ala...@ag... <mailto:ala...@ag...>>
> wrote:
>
>     Hi Santosh,
>
>>     I think reducing use of // and using multiple models might be
>>     able to help but would not resolve the issue when form is big.
>>
>     This can resolve this issue when data is big...
>
>>     In our case, we might not be able to test with multiple models
>>     unless nested models are supported (I think nested models are not
>>     supported in Xforms 1.1)
>>
>     I don't understand what you mean with nested models but nested
>     forms are considered for next XForms versions.
>
>>      
>>
>>     I debugged the code and came to know the main reason for
>>     XSLTForms being slow is because for every change, it tries to
>>     refresh all the elements on the page. The exact location of
>>     problem is below line in the refresh method  -
>>
>>     this.build(this.body, (this.defaultModel.getInstanceDocument() ?
>>     this.defaultModel.getInstanceDocument().documentElement : null),
>>     true);
>>
>>      
>>
>>     Refresh method passes the entire HTMLBodyElement (this.body =
>>     xforms.body = HTMLBodyElement ) every time anything is changed.
>>     The build method gives recursive calls on all its children.
>>
>>     For a big form, for simple operations like change in data of a
>>     textbox, I am seeing lots of recursive calls to the build method
>>     and thousands of calls to  Xpath methods etc.
>>
>     Yes, there is no list of elements to be checked and refreshed when
>     necessary. This can be added but this is not an easy change. The
>     number of XPath methods calls should be reduced when reducing the
>     use of //: I should check it myself but I'm almost sure that it's
>     very bad for dependencies and, probably, every expression is
>     reevaluated each time. Don't ever use //, this is my most precious
>     advice...
>
>>      
>>
>>      
>>
>>     I think this problem can be solved with selecting the right HTML
>>     Element every time we give call to refresh method
>>
>>      
>>
>>         * Refresh HTMLBodyElement only when entire form is loaded
>>         * For every action, we know where the Focus/blur happened,
>>           refresh only its appropriate parent HTML element
>>         * Binds can be handled separately. Cases where we need to
>>           refresh other elements can be handled separately
>>
>     There might be reverse lists of dependencies to directly point
>     elements to be refreshed but they wouldn't be easy to store with
>     the native XML architecture.
>
>>      
>>
>>     This should guarantee that only a select part of the page is
>>     considered for refresh. I have tried to do it and in fact I can
>>     see that it can be achieved, just need to determine how many
>>     levels to go up and select the appropriate HTML parent Element.
>>
>     Sorry, I don't think that it would be a correct approach. This
>     might work for your form but not for all.
>
>     Maybe declaring, with extra attributes, some sort of groups of
>     elements to be refreshed together or allowing to declare that this
>     element has to be refreshed only when a user-defined event is
>     dispatched might help.
>
>     Thanks!
>
>     -Alain
>
>
>
> ------------------------------------------------------------------------------
> Lotusphere 2011
> Register now for Lotusphere 2011 and learn how
> to connect the dots, take your collaborative environment
> to the next level, and enter the era of Social Business.
> http://p.sf.net/sfu/lotusphere-d2d
>
>
> _______________________________________________
> Xsltforms-support mailing list
> Xsl...@li...
> https://lists.sourceforge.net/lists/listinfo/xsltforms-support

Thanks Alain. For our form, we can not remove // from all the places because
we have nested xml.
Regarding the solution to refresh select part of the page, I could implement
it by passing hint on selecting the parent node for a particular form
control and it is working great. I simply pass a number (depending on all
the dependencies) on focus event which would help in determining the parent
node to be refreshed.
Below is the code snippet -
A trigger on form has -
<xf:setvalue ev:event="DOMActivate" ref="instance('datapad')/@parentIndex"
value="4"/>

And in xsltforms.js -
XFControl.prototype.focus has -
xforms.selectedElement = this.element;

refresh method has -

var parentIndex = Util.getParentIndex();         // returns
instance('datapad')/@parentIndex
        if(!this.selectedElement || parentIndex == "-1")  {
            this.selectedElement = this.body; // Can be optimized further
        } else {
              for(var i = 0; i < parentIndex; i++) {
                this.selectedElement = this.selectedElement.parentNode;
              }
        }
        this.build(this.selectedElement,
(this.defaultModel.getInstanceDocument() ?
this.defaultModel.getInstanceDocument().documentElement : null), true);
        Util.setParentIndex("-1");

All we need to do is pass appropriate parentIndex from the form and it
should resolve the performance issues caused by refreshing the entire page.
I hope something on these lines can be added to the xsltforms library.

On Fri, Dec 17, 2010 at 1:00 AM, COUTHURES Alain <
ala...@ag...> wrote:

>  Hi Santosh,
>
>  I think reducing use of // and using multiple models might be able to
> help but would not resolve the issue when form is big.
>
> This can resolve this issue when data is big...
>
>  In our case, we might not be able to test with multiple models unless
> nested models are supported (I think nested models are not supported in
> Xforms 1.1)
>
> I don't understand what you mean with nested models but nested forms are
> considered for next XForms versions.
>
>
>
> I debugged the code and came to know the main reason for XSLTForms being
> slow is because for every change, it tries to refresh all the elements on
> the page. The exact location of problem is below line in the refresh method
> -
>
> this.build(this.body, (this.defaultModel.getInstanceDocument() ?
> this.defaultModel.getInstanceDocument().documentElement : null), true);
>
>
>
> Refresh method passes the entire HTMLBodyElement (this.body = xforms.body =
> HTMLBodyElement ) every time anything is changed. The build method gives
> recursive calls on all its children.
>
> For a big form, for simple operations like change in data of a textbox, I
> am seeing lots of recursive calls to the build method and thousands of calls
> to  Xpath methods etc.
>
> Yes, there is no list of elements to be checked and refreshed when
> necessary. This can be added but this is not an easy change. The number of
> XPath methods calls should be reduced when reducing the use of //: I should
> check it myself but I'm almost sure that it's very bad for dependencies and,
> probably, every expression is reevaluated each time. Don't ever use //, this
> is my most precious advice...
>
>
>
>
>
> I think this problem can be solved with selecting the right HTML Element
> every time we give call to refresh method
>
>
>
>    - Refresh HTMLBodyElement only when entire form is loaded
>    - For every action, we know where the Focus/blur happened, refresh only
>    its appropriate parent HTML element
>    - Binds can be handled separately. Cases where we need to refresh other
>    elements can be handled separately
>
>  There might be reverse lists of dependencies to directly point elements to
> be refreshed but they wouldn't be easy to store with the native XML
> architecture.
>
>
>
> This should guarantee that only a select part of the page is considered for
> refresh. I have tried to do it and in fact I can see that it can be
> achieved, just need to determine how many levels to go up and select the
> appropriate HTML parent Element.
>
> Sorry, I don't think that it would be a correct approach. This might work
> for your form but not for all.
>
> Maybe declaring, with extra attributes, some sort of groups of elements to
> be refreshed together or allowing to declare that this element has to be
> refreshed only when a user-defined event is dispatched might help.
>
> Thanks!
>
> -Alain
>

<div style="font-family: 'Times New Roman'; font-size: 16px;">Hi Stephen Cameron!!! Yes, You are correct the single line is enough.. As per the XForms 1.1 recommendation it should work, but may be that is implementation specific feature .. XSLTForms-beta3 version doing the job.. Keep in touch for further quries .. Ps: &lt;xf:message ev:event=&quot;xforms-invalid&quot;
level=&quot;modal&quot;
if=&quot;string-length(.)
&amp;gt; 50&quot;&gt;maximum length is 50 characters&lt;/xf:message&gt; working well. On 12/21/10, Stephen Cameron &lt;Ste...@ut...&gt; wrote:<blockquote cite="mid:A62...@MB...ernal" class="iwcQuote" style="border-left: 1px solid rgb(0, 0, 255); padding-left: 13px; margin-left: 0pt;" type="cite"><div class="mimepart text html"><span xmlns="http://www.w3.org/TR/REC-html40" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:v="urn:schemas-microsoft-com:vml" xmlns:w="urn:schemas-microsoft-com:office:word">

<style>
&amp;lt;!--
 /* Font Definitions */
 @font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:&amp;quot;Times New Roman&amp;quot;,&amp;quot;serif&amp;quot;;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p
	{mso-style-priority:99;
	mso-margin-top-alt:auto;
	margin-right:0cm;
	mso-margin-bottom-alt:auto;
	margin-left:0cm;
	font-size:12.0pt;
	font-family:&amp;quot;Times New Roman&amp;quot;,&amp;quot;serif&amp;quot;;}
span.EmailStyle18
	{mso-style-type:personal-reply;
	font-family:&amp;quot;Calibri&amp;quot;,&amp;quot;sans-serif&amp;quot;;
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
	{page:WordSection1;}
--&amp;gt;
</style>
<!--[if gte mso 9]&amp;gt;&amp;lt;xml&amp;gt;
 &amp;lt;o:shapedefaults v:ext=&amp;quot;edit&amp;quot; spidmax=&amp;quot;1026&amp;quot; /&amp;gt;
&amp;lt;/xml&amp;gt;&amp;lt;![endif]--><!--[if gte mso 9]&amp;gt;&amp;lt;xml&amp;gt;
 &amp;lt;o:shapelayout v:ext=&amp;quot;edit&amp;quot;&amp;gt;
  &amp;lt;o:idmap v:ext=&amp;quot;edit&amp;quot; data=&amp;quot;1&amp;quot; /&amp;gt;
 &amp;lt;/o:shapelayout&amp;gt;&amp;lt;/xml&amp;gt;&amp;lt;![endif]-->
<table><tbody><tr><td lang="EN-US" link="blue" vlink="purple"><p>

</p><div class="WordSection1">

<p class="MsoNormal" style=""><span style="font-size: 10pt; font-family: &quot;Courier New&quot;; color: teal;">Hi Again Raga,<o:p></o:p></span></p>

<p class="MsoNormal" style=""><span style="font-size: 10pt; font-family: &quot;Courier New&quot;; color: teal;"><o:p> </o:p></span></p>

<p class="MsoNormal" style=""><span style="font-size: 10pt; font-family: &quot;Courier New&quot;; color: teal;">I think the following is enough though,
then it won’t be checking the length twice each time I enter a character (once
for the bind constraint and once for the action fired by xforms-value-changed):<o:p></o:p></span></p>

<p class="MsoNormal" style=""><span style="font-size: 10pt; font-family: &quot;Courier New&quot;; color: teal;"><o:p> </o:p></span></p>

<p class="MsoNormal" style=""><span style="font-size: 10pt; font-family: &quot;Courier New&quot;; color: teal;">&lt;</span><span style="font-size: 10pt; font-family: &quot;Courier New&quot;; color: rgb(63, 127, 127);">xf:action </span><span style="font-size: 10pt; font-family: &quot;Courier New&quot;; color: rgb(127, 0, 127);">ev:event</span><span style="font-size: 10pt; font-family: &quot;Courier New&quot;; color: black;">=</span><span style="font-size: 10pt; font-family: &quot;Courier New&quot;; color: rgb(42, 0, 255);">&quot;xforms-invalid&quot;
</span><span style="font-size: 10pt; font-family: &quot;Courier New&quot;; color: rgb(127, 0, 127);">if</span><span style="font-size: 10pt; font-family: &quot;Courier New&quot;; color: black;">=</span><span style="font-size: 10pt; font-family: &quot;Courier New&quot;; color: rgb(42, 0, 255);">&quot;string-length(.)
&amp;gt; 50&quot;</span><span style="font-size: 10pt; font-family: &quot;Courier New&quot;; color: teal;">&gt;</span><span style="font-size: 10pt; font-family: &quot;Courier New&quot;;"><o:p></o:p></span></p>

<p class="MsoNormal" style=""><span style="font-size: 10pt; font-family: &quot;Courier New&quot;; color: black;">      </span><span style="font-size: 10pt; font-family: &quot;Courier New&quot;; color: teal;">&lt;</span><span style="font-size: 10pt; font-family: &quot;Courier New&quot;; color: rgb(63, 127, 127);">xf:message </span><span style="font-size: 10pt; font-family: &quot;Courier New&quot;; color: rgb(127, 0, 127);">level</span><span style="font-size: 10pt; font-family: &quot;Courier New&quot;; color: black;">=</span><span style="font-size: 10pt; font-family: &quot;Courier New&quot;; color: rgb(42, 0, 255);">&quot;modal&quot;</span><span style="font-size: 10pt; font-family: &quot;Courier New&quot;; color: teal;">&gt;</span><span style="font-size: 10pt; font-family: &quot;Courier New&quot;; color: black;">maximum length
is 50 characters</span><span style="font-size: 10pt; font-family: &quot;Courier New&quot;; color: teal;">&lt;/</span><span style="font-size: 10pt; font-family: &quot;Courier New&quot;; color: rgb(63, 127, 127);">xf:message</span><span style="font-size: 10pt; font-family: &quot;Courier New&quot;; color: teal;">&gt;</span><span style="font-size: 10pt; font-family: &quot;Courier New&quot;;"><o:p></o:p></span></p>

<p class="MsoNormal"><span style="font-size: 10pt; font-family: &quot;Courier New&quot;; color: teal;">&lt;/</span><span style="font-size: 10pt; font-family: &quot;Courier New&quot;; color: rgb(63, 127, 127);">xf:action</span><span style="font-size: 10pt; font-family: &quot;Courier New&quot;; color: teal;">&gt;<o:p></o:p></span></p>

<p class="MsoNormal"><span style="font-size: 10pt; font-family: &quot;Courier New&quot;; color: teal;"><o:p> </o:p></span></p>

<p class="MsoNormal"><span style="font-size: 10pt; font-family: &quot;Courier New&quot;; color: teal;">However, when I read the Xforms 1.1 standard, I see that a xf:message
is actually a kind of xf:action and so it too should be able to have an ‘if’
attribute, then it would become even more simple (as below), but this does not
work in my older version of XSLTForms.</span><b><span style="font-size: 11pt; font-family: &quot;Calibri&quot;,&quot;sans-serif&quot;; color: rgb(31, 73, 125);"><o:p></o:p></span></b></p>

<p class="MsoNormal"><span style="font-size: 11pt; font-family: &quot;Calibri&quot;,&quot;sans-serif&quot;; color: rgb(31, 73, 125);"><o:p> </o:p></span></p>

<p class="MsoNormal" style=""><span style="font-size: 10pt; font-family: &quot;Courier New&quot;; color: teal;">&lt;</span><span style="font-size: 10pt; font-family: &quot;Courier New&quot;; color: rgb(63, 127, 127);">xf:message </span><span style="font-size: 10pt; font-family: &quot;Courier New&quot;; color: rgb(127, 0, 127);">ev:event</span><span style="font-size: 10pt; font-family: &quot;Courier New&quot;; color: black;">=</span><span style="font-size: 10pt; font-family: &quot;Courier New&quot;; color: rgb(42, 0, 255);">&quot;xforms-invalid&quot;
</span><span style="font-size: 10pt; font-family: &quot;Courier New&quot;; color: rgb(127, 0, 127);">level</span><span style="font-size: 10pt; font-family: &quot;Courier New&quot;; color: black;">=</span><span style="font-size: 10pt; font-family: &quot;Courier New&quot;; color: rgb(42, 0, 255);">&quot;modal&quot;
</span><span style="font-size: 10pt; font-family: &quot;Courier New&quot;; color: rgb(127, 0, 127);">if</span><span style="font-size: 10pt; font-family: &quot;Courier New&quot;; color: black;">=</span><span style="font-size: 10pt; font-family: &quot;Courier New&quot;; color: rgb(42, 0, 255);">&quot;string-length(.)
&amp;gt; 50&quot;</span><span style="font-size: 10pt; font-family: &quot;Courier New&quot;; color: teal;">&gt;</span><span style="font-size: 10pt; font-family: &quot;Courier New&quot;; color: black;">maximum length is 50 characters</span><span style="font-size: 10pt; font-family: &quot;Courier New&quot;; color: teal;">&lt;/</span><span style="font-size: 10pt; font-family: &quot;Courier New&quot;; color: rgb(63, 127, 127);">xf:message</span><span style="font-size: 10pt; font-family: &quot;Courier New&quot;; color: teal;">&gt;</span><span style="font-size: 10pt; font-family: &quot;Courier New&quot;;"><o:p></o:p></span></p>

<p class="MsoNormal"><span style="font-size: 11pt; font-family: &quot;Calibri&quot;,&quot;sans-serif&quot;; color: rgb(31, 73, 125);"><o:p> </o:p></span></p>

P.S. I am about to change to the data-island branch!<o:p></o:p>

<p class="MsoNormal"><span style="font-size: 11pt; font-family: &quot;Calibri&quot;,&quot;sans-serif&quot;; color: rgb(31, 73, 125);"><o:p> </o:p></span></p>

<div style="border-width: 1pt medium medium; border-style: solid none none; border-color: rgb(181, 196, 223) -moz-use-text-color -moz-use-text-color; padding: 3pt 0cm 0cm;">

<p class="MsoNormal"><b><span style="font-size: 10pt; font-family: &quot;Tahoma&quot;,&quot;sans-serif&quot;;">From:</span></b><span style="font-size: 10pt; font-family: &quot;Tahoma&quot;,&quot;sans-serif&quot;;"> Raja
[mailto:m.r...@ni...] <br />
<b>Sent:</b> Tuesday, 21 December 2010 3:34 PM<br />
<b>To:</b> Stephen Cameron<br />
<b>Cc:</b> XSLTForms<br />
<b>Subject:</b> Re: [Xsltforms-support] message with string maximum length exceeded<o:p></o:p></span></p>

</div>

<p class="MsoNormal"><o:p> </o:p></p>

<div>

Hi Stephen Cameron!!! 
 
the problem is in the bind &quot;required&quot;  and
&quot;constraint&quot; attribute. So, Just you split that and use the
constraint in if condition of value changed event, like 
...... 
&lt;xf:bind nodeset=&quot;test&quot; required=&quot;true()&quot;
type=&quot;xf:string&quot;/&gt; 
..... 
&lt;xf:textarea ref=&quot;test&quot; incremental=&quot;true()&quot;&gt;

&lt;xf:label&gt;Name&lt;/xf:label&gt;<br />
<br />

&lt;xf:action ev:event=&quot;xforms-value-changed&quot;
if=&quot;string-length(.) &amp;gt;= 50&quot;&gt;<br />

&lt;xf:message ev:event=&quot;xforms-invalid&quot;
level=&quot;modal&quot;&gt;maximum length is 50 characters&lt;/xf:message&gt;<br />
      &lt;/xf:action&gt;<br />
<br />
&lt;/xf:textarea&gt;<span style="color: rgb(31, 73, 125);"><o:p></o:p></span></b></p>

<p class="MsoNormal"><b><span style="font-size: 11pt; font-family: &quot;Calibri&quot;,&quot;sans-serif&quot;; color: rgb(31, 73, 125);"><o:p> </o:p></span></b></p>

<p class="MsoNormal"><b><br />
<br />
This is working fine ...<br />
<br />
By<br />
rajamani marimuthu<br />
XRX Team(Lead)<br />
India <br />
</b><br />
On 12/21/10, <b>Stephen Cameron </b>&lt;Ste...@ut...&gt; wrote:<o:p></o:p></p>

</div>

</div>

</td></tr></tbody></table>

</p></span>
</div></blockquote></div><br />-- <br />Rajamani Marimuthu<br />Junior Research Fellow-JRF<br />NIC -Open Technology Centre<br />Rajaji Bhavan<br />Besant Nagar,<br />Chennai - 90<br />Cell : 9791125383<br /><br />

Hi Again Raga,

I think the following is enough though, then it won't be checking the length twice each time I enter a character (once for the bind constraint and once for the action fired by xforms-value-changed):

<xf:action ev:event="xforms-invalid" if="string-length(.) &gt; 50">
      <xf:message level="modal">maximum length is 50 characters</xf:message>
</xf:action>

However, when I read the Xforms 1.1 standard, I see that a xf:message is actually a kind of xf:action and so it too should be able to have an 'if' attribute, then it would become even more simple (as below), but this does not work in my older version of XSLTForms.

<xf:message ev:event="xforms-invalid" level="modal" if="string-length(.) &gt; 50">maximum length is 50 characters</xf:message>

P.S. I am about to change to the data-island branch!

From: Raja [mailto:m.r...@ni...]
Sent: Tuesday, 21 December 2010 3:34 PM
To: Stephen Cameron
Cc: XSLTForms
Subject: Re: [Xsltforms-support] message with string maximum length exceeded

Hi Stephen Cameron!!!

the problem is in the bind "required" and "constraint" attribute. So, Just you split that and use the constraint in if condition of value changed event, like
......
<xf:bind nodeset="test" required="true()" type="xf:string"/>
.....
<xf:textarea ref="test" incremental="true()">

            <xf:label>Name</xf:label>

            <xf:action ev:event="xforms-value-changed" if="string-length(.) &gt;= 50">
            <xf:message ev:event="xforms-invalid" level="modal">maximum length is 50 characters</xf:message>
      </xf:action>

</xf:textarea>

This is working fine ...

By
rajamani marimuthu
XRX Team(Lead)
India

On 12/21/10, Stephen Cameron <Ste...@ut...> wrote:

<div style="font-family: 'Times New Roman'; font-size: 16px;">Hi Stephen Cameron!!! the problem is in the bind &quot;required&quot;  and &quot;constraint&quot; attribute. So, Just you split that and use the constraint in if condition of value changed event, like ...... &lt;xf:bind nodeset=&quot;test&quot; required=&quot;true()&quot; type=&quot;xf:string&quot;/&gt; ..... &lt;xf:textarea ref=&quot;test&quot; incremental=&quot;true()&quot;&gt;             &lt;xf:label&gt;Name&lt;/xf:label&gt;             &lt;xf:action ev:event=&quot;xforms-value-changed&quot; if=&quot;string-length(.) &amp;gt;= 50&quot;&gt;             &lt;xf:message ev:event=&quot;xforms-invalid&quot; level=&quot;modal&quot;&gt;maximum length is 50 characters&lt;/xf:message&gt;       &lt;/xf:action&gt; &lt;/xf:textarea&gt; This is working fine ... By rajamani marimuthu XRX Team(Lead) India On 12/21/10, Stephen Cameron &lt;Ste...@ut...&gt; wrote:<blockquote cite="mid:A62...@MB...ernal" class="iwcQuote" style="border-left: 1px solid rgb(0, 0, 255); padding-left: 13px; margin-left: 0pt;" type="cite"><div class="mimepart text html"><span xmlns="http://www.w3.org/TR/REC-html40" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:v="urn:schemas-microsoft-com:vml" xmlns:w="urn:schemas-microsoft-com:office:word">

<style>
&amp;lt;!--
 /* Font Definitions */
 @font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:&amp;quot;Calibri&amp;quot;,&amp;quot;sans-serif&amp;quot;;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:&amp;quot;Calibri&amp;quot;,&amp;quot;sans-serif&amp;quot;;
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
	{page:WordSection1;}
--&amp;gt;
</style>
<!--[if gte mso 9]&amp;gt;&amp;lt;xml&amp;gt;
 &amp;lt;o:shapedefaults v:ext=&amp;quot;edit&amp;quot; spidmax=&amp;quot;1026&amp;quot; /&amp;gt;
&amp;lt;/xml&amp;gt;&amp;lt;![endif]--><!--[if gte mso 9]&amp;gt;&amp;lt;xml&amp;gt;
 &amp;lt;o:shapelayout v:ext=&amp;quot;edit&amp;quot;&amp;gt;
  &amp;lt;o:idmap v:ext=&amp;quot;edit&amp;quot; data=&amp;quot;1&amp;quot; /&amp;gt;
 &amp;lt;/o:shapelayout&amp;gt;&amp;lt;/xml&amp;gt;&amp;lt;![endif]-->
<table><tbody><tr><td lang="EN-US" link="blue" vlink="purple"><p>

</p><div class="WordSection1">

<p class="MsoNormal">Hi All,<o:p></o:p></p>

<p class="MsoNormal"><o:p> </o:p></p>

<p class="MsoNormal">I have a simple question which someone may have solved.<o:p></o:p></p>

<p class="MsoNormal"><o:p> </o:p></p>

<p class="MsoNormal">I’m controlling the amount of text that a user can
input using a bind constraint: <o:p></o:p></p>

<p class="MsoNormal"><o:p> </o:p></p>

<p class="MsoNormal"><span style="font-size: 10pt; font-family: &quot;Courier New&quot;; color: black;">      </span><span style="font-size: 10pt; font-family: &quot;Courier New&quot;; color: teal;">&lt;</span><span style="font-size: 10pt; font-family: &quot;Courier New&quot;; color: rgb(63, 127, 127);">xf:bind </span><span style="font-size: 10pt; font-family: &quot;Courier New&quot;; color: rgb(127, 0, 127);">id</span><span style="font-size: 10pt; font-family: &quot;Courier New&quot;; color: black;">=</span><span style="font-size: 10pt; font-family: &quot;Courier New&quot;; color: rgb(42, 0, 255);">&quot;installation_name&quot;
</span><span style="font-size: 10pt; font-family: &quot;Courier New&quot;; color: rgb(127, 0, 127);">nodeset</span><span style="font-size: 10pt; font-family: &quot;Courier New&quot;; color: black;">=</span><span style="font-size: 10pt; font-family: &quot;Courier New&quot;; color: rgb(42, 0, 255);">&quot;*/*/*/*/aatams:name&quot;
</span><span style="font-size: 10pt; font-family: &quot;Courier New&quot;; color: rgb(127, 0, 127);">required</span><span style="font-size: 10pt; font-family: &quot;Courier New&quot;; color: black;">=</span><span style="font-size: 10pt; font-family: &quot;Courier New&quot;; color: rgb(42, 0, 255);">&quot;true()&quot;
</span><span style="font-size: 10pt; font-family: &quot;Courier New&quot;; color: rgb(127, 0, 127);">type</span><span style="font-size: 10pt; font-family: &quot;Courier New&quot;; color: black;">=</span><span style="font-size: 10pt; font-family: &quot;Courier New&quot;; color: rgb(42, 0, 255);">&quot;xf:string&quot;
</span><span style="font-size: 10pt; font-family: &quot;Courier New&quot;; color: rgb(127, 0, 127);">constraint</span><span style="font-size: 10pt; font-family: &quot;Courier New&quot;; color: black;">=</span><span style="font-size: 10pt; font-family: &quot;Courier New&quot;; color: rgb(42, 0, 255);">&quot;string-length(.)
&amp;lt;= 50&quot; </span><span style="font-size: 10pt; font-family: &quot;Courier New&quot;; color: teal;">/&gt;</span><o:p></o:p></p>

<p class="MsoNormal"><o:p> </o:p></p>

<p class="MsoNormal">Also I have a message  fired on the xforms-invalid
event:<o:p></o:p></p>

<p class="MsoNormal"><o:p> </o:p></p>

<p class="MsoNormal" style=""><span style="font-size: 10pt; font-family: &quot;Courier New&quot;; color: black;">      </span><span style="font-size: 10pt; font-family: &quot;Courier New&quot;; color: teal;">&lt;</span><span style="font-size: 10pt; font-family: &quot;Courier New&quot;; color: rgb(63, 127, 127);">xf:textarea </span><span style="font-size: 10pt; font-family: &quot;Courier New&quot;; color: rgb(127, 0, 127);">ref</span><span style="font-size: 10pt; font-family: &quot;Courier New&quot;; color: black;">=</span><span style="font-size: 10pt; font-family: &quot;Courier New&quot;; color: rgb(42, 0, 255);">&quot;aatams:name&quot;
</span><span style="font-size: 10pt; font-family: &quot;Courier New&quot;; color: rgb(127, 0, 127);">incremental</span><span style="font-size: 10pt; font-family: &quot;Courier New&quot;; color: black;">=</span><span style="font-size: 10pt; font-family: &quot;Courier New&quot;; color: rgb(42, 0, 255);">&quot;true()&quot;</span><span style="font-size: 10pt; font-family: &quot;Courier New&quot;; color: teal;">&gt;</span><span style="font-size: 10pt; font-family: &quot;Courier New&quot;;"><o:p></o:p></span></p>

<p class="MsoNormal" style=""><span style="font-size: 10pt; font-family: &quot;Courier New&quot;; color: black;">            </span><span style="font-size: 10pt; font-family: &quot;Courier New&quot;; color: teal;">&lt;</span><span style="font-size: 10pt; font-family: &quot;Courier New&quot;; color: rgb(63, 127, 127);">xf:label</span><span style="font-size: 10pt; font-family: &quot;Courier New&quot;; color: teal;">&gt;</span><span style="font-size: 10pt; font-family: &quot;Courier New&quot;; color: black;">Name</span><span style="font-size: 10pt; font-family: &quot;Courier New&quot;; color: teal;">&lt;/</span><span style="font-size: 10pt; font-family: &quot;Courier New&quot;; color: rgb(63, 127, 127);">xf:label</span><span style="font-size: 10pt; font-family: &quot;Courier New&quot;; color: teal;">&gt;</span><span style="font-size: 10pt; font-family: &quot;Courier New&quot;;"><o:p></o:p></span></p>

<p class="MsoNormal" style=""><span style="font-size: 10pt; font-family: &quot;Courier New&quot;; color: black;">            </span><span style="font-size: 10pt; font-family: &quot;Courier New&quot;; color: teal;">&lt;</span><span style="font-size: 10pt; font-family: &quot;Courier New&quot;; color: rgb(63, 127, 127);">xf:message </span><span style="font-size: 10pt; font-family: &quot;Courier New&quot;; color: rgb(127, 0, 127);">ev:event</span><span style="font-size: 10pt; font-family: &quot;Courier New&quot;; color: black;">=</span><span style="font-size: 10pt; font-family: &quot;Courier New&quot;; color: rgb(42, 0, 255);">&quot;xforms-invalid&quot;
</span><span style="font-size: 10pt; font-family: &quot;Courier New&quot;; color: rgb(127, 0, 127);">level</span><span style="font-size: 10pt; font-family: &quot;Courier New&quot;; color: black;">=</span><span style="font-size: 10pt; font-family: &quot;Courier New&quot;; color: rgb(42, 0, 255);">&quot;modal&quot;</span><span style="font-size: 10pt; font-family: &quot;Courier New&quot;; color: teal;">&gt;</span><span style="font-size: 10pt; font-family: &quot;Courier New&quot;; color: black;">maximum length
is 50 characters</span><span style="font-size: 10pt; font-family: &quot;Courier New&quot;; color: teal;">&lt;/</span><span style="font-size: 10pt; font-family: &quot;Courier New&quot;; color: rgb(63, 127, 127);">xf:message</span><span style="font-size: 10pt; font-family: &quot;Courier New&quot;; color: teal;">&gt;</span><span style="font-size: 10pt; font-family: &quot;Courier New&quot;;"><o:p></o:p></span></p>

<p class="MsoNormal"><span style="font-size: 10pt; font-family: &quot;Courier New&quot;; color: black;">      </span><span style="font-size: 10pt; font-family: &quot;Courier New&quot;; color: teal;">&lt;/</span><span style="font-size: 10pt; font-family: &quot;Courier New&quot;; color: rgb(63, 127, 127);">xf:textarea</span><span style="font-size: 10pt; font-family: &quot;Courier New&quot;; color: teal;">&gt;<o:p></o:p></span></p>

<p class="MsoNormal"><span style="font-size: 10pt; font-family: &quot;Courier New&quot;; color: teal;"><o:p> </o:p></span></p>

My problem
is that the invalid message appears when the user removes all text from the
input, but the message that appears is irrelevant in that situation. I’d
like the message to appear only when the text exceeds the limit set in the
constraint.<o:p></o:p>

<p class="MsoNormal"><span style="font-size: 10pt; font-family: &quot;Courier New&quot;;"><o:p> </o:p></span></p>

<p class="MsoNormal"><span style="font-size: 10pt; font-family: &quot;Courier New&quot;;">Is
there a standard Xforms ‘pattern’ for this situation, (it seems to
me that explaining to the user that they have exceeded the permissible text length
is one situation where a popup message is really useful).<o:p></o:p></span></p>

<p class="MsoNormal"><span style="font-size: 10pt; font-family: &quot;Courier New&quot;;"><o:p> </o:p></span></p>

If
I cannot get the invalid message to work as I want, an alternative is to set
the background of the input to another color if the value entered is invalid
(too long). If incremental=”true()” then the color change provides
immediate feed-back to the user, which is almost good enough.<o:p></o:p>

<p class="MsoNormal"><span style="font-size: 10pt; font-family: &quot;Courier New&quot;;"><o:p> </o:p></span></p>

<p class="MsoNormal"><span style="font-size: 10pt; font-family: &quot;Courier New&quot;;">I
suspect that there actually needs to be some way to check the source of the invalidity
as either being due to the type definition or the constraint in the bind, is
this possible?<o:p></o:p></span></p>

<p class="MsoNormal"><span style="font-size: 10pt; font-family: &quot;Courier New&quot;;"><o:p> </o:p></span></p>

<p class="MsoNormal"><span style="font-size: 10pt; font-family: &quot;Courier New&quot;;">Of
course it is possible to define maximum length via an XML Schema but perhaps
this results in the same kind of problem.<o:p></o:p></span></p>

<p class="MsoNormal"><span style="font-size: 10pt; font-family: &quot;Courier New&quot;;"><o:p> </o:p></span></p>

<p class="MsoNormal"><span style="font-size: 10pt; font-family: &quot;Courier New&quot;;">Thanks
for your thoughts.<o:p></o:p></span></p>

<p class="MsoNormal"><span style="font-size: 10pt; font-family: &quot;Courier New&quot;;"><o:p> </o:p></span></p>

<p class="MsoNormal"><span style="font-size: 10pt; font-family: &quot;Courier New&quot;;"><o:p> </o:p></span></p>

</div>

</td></tr></tbody></table>

</p></span>
</div></blockquote></div><br />-- <br />Rajamani Marimuthu<br />Junior Research Fellow-JRF<br />NIC -Open Technology Centre<br />Rajaji Bhavan<br />Besant Nagar,<br />Chennai - 90<br />Cell : 9791125383<br /><br />

Hi All,

I have a simple question which someone may have solved.

I'm controlling the amount of text that a user can input using a bind constraint:

      <xf:bind id="installation_name" nodeset="*/*/*/*/aatams:name" required="true()" type="xf:string" constraint="string-length(.) &lt;= 50" />

Also I have a message  fired on the xforms-invalid event:

      <xf:textarea ref="aatams:name" incremental="true()">
            <xf:label>Name</xf:label>
            <xf:message ev:event="xforms-invalid" level="modal">maximum length is 50 characters</xf:message>
      </xf:textarea>

My problem is that the invalid message appears when the user removes all text from the input, but the message that appears is irrelevant in that situation. I'd like the message to appear only when the text exceeds the limit set in the constraint.

Is there a standard Xforms 'pattern' for this situation, (it seems to me that explaining to the user that they have exceeded the permissible text length is one situation where a popup message is really useful).

If I cannot get the invalid message to work as I want, an alternative is to set the background of the input to another color if the value entered is invalid (too long). If incremental="true()" then the color change provides immediate feed-back to the user, which is almost good enough.

I suspect that there actually needs to be some way to check the source of the invalidity as either being due to the type definition or the constraint in the bind, is this possible?

Of course it is possible to define maximum length via an XML Schema but perhaps this results in the same kind of problem.

Thanks for your thoughts.

Hi Alain,

> Can you please send me the corresponding files?

Yes, I'll send them directly.

> Just after reading an instance, XSLTForms is validating it: it is in
> fact the longest step and there are still possibilities to optimize it.
>> Is there any way to read part of a large XML file without scanning the
>> entire file, as I suspect that is what is happening?
> Sorry, an XML 1.0 file has to be completely parsed before any other
> processing...
>>  By the way,
>> performance under Ubiquity Formsplayer is (just) acceptable.
> Formsplayer is a plug-in: it is a compiled product.

Yes, I know. I was hoping that XSLTForms, being less  
browser-dependent, could meet my minimum performance requirements.

Thanks,

Fred

Hello Fred,
> I read a large XML (catalog) file with some 1000 articles
> or 10000 lines as an input instance. Part of it (say, 10 articles) is
> presented at a time in the form. The selection is coded (now) as a
> position() range, or as repeat/@number, but the latter seems not to
> work in XSLTForms.
Can you please send me the corresponding files?
> In any case the reading of the instance takes far too long. The
> browser (IE8) meets its scripting time-out.
Just after reading an instance, XSLTForms is validating it: it is in 
fact the longest step and there are still possibilities to optimize it.
> Is there any way to read part of a large XML file without scanning the
> entire file, as I suspect that is what is happening?
Sorry, an XML 1.0 file has to be completely parsed before any other 
processing...
>   By the way,
> performance under Ubiquity Formsplayer is (just) acceptable.
Formsplayer is a plug-in: it is a compiled product.

Thanks!

-Alain

Hello Grégoire,

Don't worry about this message box. It won't be attached to double click 
in Beta 3 but to, probably, the F1 key.

This could be useful to display statistics about loading and refreshing 
times, instances sizes... Do you have suggestions?

Thanks!

-Alain

Le 18/12/2010 19:32, Grégoire COLBERT a écrit :
> Hi,
>
> I upgraded from 466 to 469 and now, when I double click, there is a
> "copyright notice" saying:
>
> ===
> XSLTForms version id: Rev. 469
>
> http://www.agencexml.com/xsltforms
>
> (c) Alain Couthures - agenceXML - 2010
> ===
>
> I intend to give XSLTForms the credit and link it deserves but frankly,
> this popup window IS annoying (imagine when you have a map in your page,
> each time you want to zoon, it doesn't work and you get this annoying box…).
>
> Regards,
> Grégoire
>
> ------------------------------------------------------------------------------
> Lotusphere 2011
> Register now for Lotusphere 2011 and learn how
> to connect the dots, take your collaborative environment
> to the next level, and enter the era of Social Business.
> http://p.sf.net/sfu/lotusphere-d2d
> _______________________________________________
> Xsltforms-support mailing list
> Xsl...@li...
> https://lists.sourceforge.net/lists/listinfo/xsltforms-support
>

Hi,

I upgraded from 466 to 469 and now, when I double click, there is a
"copyright notice" saying:

===
XSLTForms version id: Rev. 469

http://www.agencexml.com/xsltforms

(c) Alain Couthures - agenceXML - 2010
===

I intend to give XSLTForms the credit and link it deserves but frankly,
this popup window IS annoying (imagine when you have a map in your page,
each time you want to zoon, it doesn't work and you get this annoying box…).

Regards,
Grégoire

Hi Alain,

Citeren COUTHURES Alain <ala...@ag...>:
>> The button does not completely disappear though, in the minimal   
>> appearance a border is created around the image.
> This can be fixed with CSS...

Indeed it can, Sorry I reacted too quick.

Fred

Hi Alain,

Citeren COUTHURES Alain <ala...@ag...>:
> This issue is due to the lack of label for the trigger in your form.
> The XSLT stylesheet is generating an empty button element: IE doesn't
> accept this and all the following tags are messed up.
> I have added a test for this situation.

Aaah, so this is related to my "button" question. As I use images, I  
thought labels are not needed, but the image goes into the label.

Thanks so much!

Fred

Hello Alain and Fred,

I might be the cause of this. In my example when I used the FireFox
plugin my example worked if <img> was inside the trigger but outside
the label.

http://en.wikibooks.org/wiki/XForms/Controlling_Button_Appearance

But as Alain suggests, if you just put the img tag INSIDE the <label>
it works fine.

Here is my sample:

http://184.72.253.206/rest/db/test/xforms/trigger/01-test.xq

Note that the images work perfectly when they are inside the label tag.

- Dan

On Fri, Dec 17, 2010 at 2:17 PM, COUTHURES Alain
<ala...@ag...> wrote:
> Hi Fred,
>> Does anyone know how to replace standard buttons by customised images
>> in XSLTForms?<img>  under<trigger>  seems not to work.
> You can use <xf:trigger><xf:label><img
> src="mybutton.gif"/></xf:label>... to have this image in the button.
>
> Thank you for your feedbacks!
>
> -Alain
>
> ------------------------------------------------------------------------------
> Lotusphere 2011
> Register now for Lotusphere 2011 and learn how
> to connect the dots, take your collaborative environment
> to the next level, and enter the era of Social Business.
> http://p.sf.net/sfu/lotusphere-d2d
> _______________________________________________
> Xsltforms-support mailing list
> Xsl...@li...
> https://lists.sourceforge.net/lists/listinfo/xsltforms-support
>

-- 
Dan McCreary
Semantic Solutions Architect
office: (952) 931-9198
cell: (612) 986-1552

> The button does not completely disappear though, in the minimal 
> appearance a border is created around the image.
This can be fixed with CSS...

-Alain

Thanks, Alain,

Didn't think of that...
The button does not completely disappear though, in the minimal  
appearance a border is created around the image.

Cheers,

Fred

Citeren COUTHURES Alain <ala...@ag...>:

> Hi Fred,
>> Does anyone know how to replace standard buttons by customised images
>> in XSLTForms?<img>  under<trigger>  seems not to work.
> You can use <xf:trigger><xf:label><img
> src="mybutton.gif"/></xf:label>... to have this image in the button.
>
> Thank you for your feedbacks!
>
> -Alain

Hi Fred,
> I have two Repeats, one with Catalog TradeItems from which the other 
> one, OrderLines, is populated. Putting a Trigger alongside the Catalog 
> TradeItems however causes strange results, see attached screen shot. 
> If I put the Trigger outside the Repeat loop it behaves as expected. 
> Am I doing something wrong?
>
> I use IE8, locally.
This issue is due to the lack of label for the trigger in your form. The 
XSLT stylesheet is generating an empty button element: IE doesn't accept 
this and all the following tags are messed up.

I have added a test for this situation.

Thanks!

-Alain

Hi Fred,
> Does anyone know how to replace standard buttons by customised images
> in XSLTForms?<img>  under<trigger>  seems not to work.
You can use <xf:trigger><xf:label><img 
src="mybutton.gif"/></xf:label>... to have this image in the button.

Thank you for your feedbacks!

-Alain

Hi,

Does anyone know how to replace standard buttons by customised images 
in XSLTForms? <img> under <trigger> seems not to work.

Thanks,

Fred van Blommestein

Santosh, Alain,

I have a similar performance problem. I don't have a form with many  
fields, but I read a large XML (catalog) file with some 1000 articles  
or 10000 lines as an input instance. Part of it (say, 10 articles) is  
presented at a time in the form. The selection is coded (now) as a  
position() range, or as repeat/@number, but the latter seems not to  
work in XSLTForms.

In any case the reading of the instance takes far too long. The  
browser (IE8) meets its scripting time-out.

Is there any way to read part of a large XML file without scanning the  
entire file, as I suspect that is what is happening? By the way,  
performance under Ubiquity Formsplayer is (just) acceptable.

Thanks for your views,

Fred

>>
>>
>> We have integrated the XSLTForms beta-3 version in our application
>>
> Don't hesitate to test also with the latest build in the SVN repository.
>>
>> and IE's performance has drastically improved, still its not usable
>> when the form goes big.
>>
> Instance loading is much more improved but metadata has to be stored as
> extra attributes and access to them is slower than to properties of
> Javascript objects.
>>
>> Interestingly, Fiefox's performance is reduced slightly indicating
>> that IE's DOM implementation is better.
>>
> Yes, I noticed that too...
>>
>> We noted that there is difference in performance when we add an
>> element to an empty form versus if the form has lot of data. It seems
>> XSLTForms does lot of XPATH processing/binding calls on many other
>> elements which are not needed in our case.
>>
> I see that, in your form, there are a lot of XPath expressions starting
> with //. That's always very bad for performance and it would be much
> better with the full path, even if it is a long one.
>>
>> In order to improve the performance further, we are thinking of
>> modifying the library and reducing this processing.Can you please give
>> some pointers around it?
>>
> Profiling with a browser debugger can point to Javascript functions to
> optimize.
>
> Did you think of using different models to reduce refresh time?
>>
>> One more idea is move the XPATH code to java applets and call that
>> from javascript (We have already implemented loading/saving local file
>> using applets ) .
>>
> This would need to rewrite a lot in Java (functions and operators
> evaluation) and sounds impossible because of the dependency mechanism.
>>
>> I have also attached our form just to give an idea about the size. Can
>> you please share your thoughts/ideas around it?
>>
> Good to see that you're using eXSLTForms too and that you defined your
> own XPath functions (array-get() and others...).
>>
>> PS : I would also like to be member of the XSLTForms support group and
>> also post requests, answers directly there. Can you please let me know
>> how this can be done?
>>
> Feel free to post requests and answers at this list. Your feedbacks are
> surely valuable.
>
> Thanks!
>
> -Alain
>
>
> ------------------------------------------------------------------------------
> Lotusphere 2011
> Register now for Lotusphere 2011 and learn how
> to connect the dots, take your collaborative environment
> to the next level, and enter the era of Social Business.
> http://p.sf.net/sfu/lotusphere-d2d
> _______________________________________________
> Xsltforms-support mailing list
> Xsl...@li...
> https://lists.sourceforge.net/lists/listinfo/xsltforms-support
>

Hi,

I have two Repeats, one with Catalog TradeItems from which the other  
one, OrderLines, is populated. Putting a Trigger alongside the Catalog  
TradeItems however causes strange results, see attached screen shot.  
If I put the Trigger outside the Repeat loop it behaves as expected.  
Am I doing something wrong?

I use IE8, locally.

Thanks,

Fred van Blommestein

Hi Alain,

Thanks, I'll try that.

My forms are to send standard (GS1, UBL) XML messages. I found in the  
pilot we are running that receiving systems (typically middleware such  
as SAP XI) are very specific on compliance to such standard. Even if  
namespace prefixes do not totally comply with the schema construct  
(different include structures lead to different prefix presence) they  
refuse the message.

Fred

Citeren COUTHURES Alain <ala...@ag...>:

>
>> does that empty namespace declaration also show up in the submitted  
>>  instance? If so, how can it be suppressed?
> XSLTForms is now using native serialization of the XSLT 1.0 engine so
> the empty namespace declaration might be omitted with
> exclude-result-prefixes="#default" but I'm not sure this is supported
> by every XSLT engine...
>
> This shouldn't be a problem for a regular XML parser. Do you have
> special constraints at server-side??
>
> Thanks!
>
> -Alain

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

xsltforms-support Mailing List for XSLTForms (Page 70)

xsltforms-support — XSLTForms support list