xsltforms-support — XSLTForms support list

Re: [Xsltforms-support] Preceding axis

[COUTHURES A. <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

Re: [Xsltforms-support] Preceding axis

[<fr...@fl...>]

Hi Alain,

Yes, you are right, many thanks.
The problem was that I had not included the empty namespace  
declaration xmlns="" in the Search instance.

Which brings me to another short question: does that empty namespace  
declaration also show up in the submitted instance? If so, how can it  
be suppressed?

Thanks again!

Fred



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

>
>> The | operator however not
>> yet. In my selection list I should see four entries: the three
>> TradeItemGroupNames and 'All'. I don't see the 'All'.
>>
>> Fred
> Actually, I fixed some problems in your test case to compare with EMC
> Formula and Mozilla XForms. Please have a look at the attached file.
>
> I tested it successfully with IE8 and IE9beta: the 'All' value appears!
>
> Thanks!
>
> -Alain

Re: [Xsltforms-support] Preceding axis

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

> The | operator however not
> yet. In my selection list I should see four entries: the three
> TradeItemGroupNames and 'All'. I don't see the 'All'.
>
> Fred
Actually, I fixed some problems in your test case to compare with EMC 
Formula and Mozilla XForms. Please have a look at the attached file.

I tested it successfully with IE8 and IE9beta: the 'All' value appears!

Thanks!

-Alain

Re: [Xsltforms-support] Preceding axis

[<fr...@fl...>]

Hi Alain,

Thanks for the quick fix!!

The preceding axis indeed now works OK. The | operator however not  
yet. In my selection list I should see four entries: the three  
TradeItemGroupNames and 'All'. I don't see the 'All'.

Fred


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

> Hello Fred,
> There was an old typo (inherited from AJAXForms!) in a function used
> for the preceding axis evaluation.
>> Also, the | operator to combine two node sets seems not to work.
> Well, at least, it now seems to work in your test case...
>
> Please test again with the latest build in the SVN repository.
>
> Thanks!
>
> -Alain

Re: [Xsltforms-support] Preceding axis

[COUTHURES A. <ala...@fr...>]

Hello Fred,
> I use a selection list that is populated with unique 
> TradeItemGroupNames taken from a list of items that contains duplicate 
> TradeItemGroupNames. To filter out duplicates I use:
>
> TradeItemGroupName[not(preceding::TradeItemGroupName=.)]
>
> This works in Formsplayer but seems not to work in XSLTForms.
There was an old typo (inherited from AJAXForms!) in a function used for 
the preceding axis evaluation.
> Also, the | operator to combine two node sets seems not to work.
Well, at least, it now seems to work in your test case...

Please test again with the latest build in the SVN repository.

Thanks!

-Alain

Re: [Xsltforms-support] Preceding axis

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

Hello Fred,
> I use a selection list that is populated with unique 
> TradeItemGroupNames taken from a list of items that contains duplicate 
> TradeItemGroupNames. To filter out duplicates I use:
>
> TradeItemGroupName[not(preceding::TradeItemGroupName=.)]
>
> This works in Formsplayer but seems not to work in XSLTForms.
There was an old typo (inherited from AJAXForms!) in a function called 
for the preceding axis evaluation.
> Also, the | operator to combine two node sets seems not to work.
>
Well, it now seems to work for your test case.

Please test again with the latest build in the SVN repository.

Thanks!

-Alain

Re: [Xsltforms-support] IE8 Performance on XSLTForms beta-3

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

Hi Kostis,
> i think the definitive guide to disigning the xforms recalculation
> algorithm is this paper of John Boyer:
> http://citeseerx.ist.psu.edu/viewdoc/summary?doi=10.1.1.75.9333
>
> It really worthed the time i spent to read it.
>
> It refers to the same family of algorithms firsly described by Knuth,
> used (and i think developed for) initially for spreadsheet's cell
> re-calculations.
 From recent discussions in the XForms W3C WorkGroup, I learned that 
this kind of algorithm is not implemented in the different XForms 
implementations.

XSLTForms only detects situations when calculations are not performed in 
the right order: calculations are iterated until there is no order problem.

I didn't understand that Ubiquity XForms (John Boyer's project) 
succeeded in implementing this efficiently.

-Alain

Re: [Xsltforms-support] IE8 Performance on XSLTForms beta-3

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

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 toXpath 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

Re: [Xsltforms-support] IE8 Performance on XSLTForms beta-3

[Kostis A. <ank...@gm...>]

Hi,

i think the definitive guide to disigning the xforms recalculation
algorithm is this paper of John Boyer:
http://citeseerx.ist.psu.edu/viewdoc/summary?doi=10.1.1.75.9333

It really worthed the time i spent to read it.

It refers to the same family of algorithms firsly described by Knuth,
used (and i think developed for) initially for spreadsheet's cell
re-calculations.

Regards,
  Kostis Anagnostopoulos

On Thu, Dec 16, 2010 at 2:20 PM, Santosh Chandak
<san...@gm...> wrote:
> Thanks Alain, I think reducing use of // and using multiple models might be
> able to help but would not resolve the issue when form 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 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.
>
>
>
>
>
> 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
>
>
>
> 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.
>
>
>
> Let me know your thoughts on the same.
>
> Regards,
> Santosh
>
>
> ---------- Forwarded message ----------
> From: COUTHURES Alain <ala...@ag...>
> Date: Thu, Dec 16, 2010 at 2:25 AM
> Subject: Re: IE8 Performance on XSLTForms beta-3
> To: Santosh Chandak <san...@gm...>
> Cc: XSLTForms support <xsl...@li...>
>
>
> Hi Santosh,
>>
>>
>> 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
>
>

Re: [Xsltforms-support] IE8 Performance on XSLTForms beta-3

[Santosh C. <san...@gm...>]

Thanks Alain, I think reducing use of // and using multiple models might be
able to help but would not resolve the issue when form 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 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.





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



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.



Let me know your thoughts on the same.

Regards,
Santosh


---------- Forwarded message ----------
From: COUTHURES Alain <ala...@ag...>
Date: Thu, Dec 16, 2010 at 2:25 AM
Subject: Re: IE8 Performance on XSLTForms beta-3
To: Santosh Chandak <san...@gm...>
Cc: XSLTForms support <xsl...@li...>


Hi Santosh,


>
> 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

[Xsltforms-support] Preceding axis

[<fr...@fl...>]

Dear all,

I am converting my application from Ubiquity Formsplayer to XSLTForms  
and hit the following problem. I use a selection list that is  
populated with unique TradeItemGroupNames taken from a list of items  
that contains duplicate TradeItemGroupNames. To filter out duplicates  
I use:

TradeItemGroupName[not(preceding::TradeItemGroupName=.)]

This works in Formsplayer but seems not to work in XSLTForms.
Also, the | operator to combine two node sets seems not to work.

Have a look at the attached code. I would be grateful for any tip to  
modify my code or work around.

My app runs locally client side on IE8.

Fred van Blommestein

Re: [Xsltforms-support] IE8 Performance on XSLTForms beta-3

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

Hi Santosh,
>
>
> 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

Re: [Xsltforms-support] bug: 4096-char limit in xsltforms branchdataisland 466

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

Hello Leigh,

Thank you for proposing this fix.

I have improved it using .text (or .textContent) property and I have 
tested it with the usual examples. This is now committed.

Can you please validate this new build with your own test cases?

Thanks!

-Alain

Le 29/11/2010 20:48, Leigh L Klotz Jr a écrit :
> Oops, the description of the test-patch for setValue I pasted in was
> missing an "else" before an "if".
> For clarity, here's the straight code, not the diff.
>
> Leigh.
>
>
> function getValue(node, format, serialize) {
>           assert(node);
>           if (serialize) {
>                   return node.nodeType == NodeType.ATTRIBUTE ?
> node.nodeValue : Core.saveXML(node);
>           }
>           var value = "";
>           if (node.nodeType == NodeType.ATTRIBUTE) {
>             value = node.nodeValue;
>           } else if (node.firstChild == null) {
>             // already ""
>           } else if (node.firstChild.nodeType == NodeType.TEXT) {
>             var childNodes = node.childNodes;
>             var len = childNodes.length;
>             // TODO: What if not all nodes are TEXT?
>             for (var i = 0; i<  len; i++) {
>               value = value + childNodes[i].nodeValue;
>             }
>           } else {
>             value = node.firstChild.nodeValue;
>           }
>
>           if (value&&  format) {
>                   var schtyp = Schema.getType(Core.getType(node) ||
> "xsd_:string");
>                   if (schtyp.format) {
>                           try { value = schtyp.format(value); } catch(e) { }
>                   }
>           }
>
>           return value;
> }
>
>
> function setValue(node, value) {
>           assert(node);
>           if (node.nodeType == NodeType.ATTRIBUTE) {
>                   node.nodeValue = value;
>           } else if (Core.isIE&&  node.innerHTML) {
>                   node.innerHTML = value;
>           } else if (node.firstChild) {
>                   node.firstChild.nodeValue = value;
>           } else if (value != null&&  value.length>  4095) {
>                  for (var i = 0; i<  value.length + 4095; i += 4095) {
>                      var chunk = value.substr(i, 4095);
>                      if (chunk.length>  0) {
>
> node.appendChild(node.ownerDocument.createTextNode(chunk));
>                      }
>                  }
>           } else if (value != null) {
>                  node.appendChild(node.ownerDocument.createTextNode(value));
>           }
> }
>
>
>
>
> ------------------------------------------------------------------------------
> Increase Visibility of Your 3D Game App&  Earn a Chance To Win $500!
> Tap into the largest installed PC base&  get more eyes on your game by
> optimizing for Intel(R) Graphics Technology. Get started today with the
> Intel(R) Software Partner Program. Five $500 cash prizes are up for grabs.
> http://p.sf.net/sfu/intelisp-dev2dev
> _______________________________________________
> Xsltforms-support mailing list
> Xsl...@li...
> https://lists.sourceforge.net/lists/listinfo/xsltforms-support
>

Re: [Xsltforms-support] What's this error means

[Joe W. <jo...@gm...>]

Srinivasan,

This is an error from eXist about the xmldb:get-child-resources()
function in your letter_pdf.xq.  This function requires a single
parameter: the uri of the database collection you want to get the
child resources of.  The error is quite clear in saying that for some
reason it's not receiving anything for that parameter.  Without seeing
the relevant portion of letter_pdf.xq, it's impossible for me to
suggest why the parameter is empty.

If you get errors that look like this in the future (this is eXist's
format for reporting errors), it's probably a good idea to post the
report to the exist-open list and not xsltforms-support.

Cheers,
Joe


On Mon, Dec 13, 2010 at 12:55 AM, srinivasan krishnamoorthy
<sri...@gm...> wrote:
>
> When i am executing my pdf query i am facing following error message in
> browser...........
>
>
> <exception>
> <path>//db/vserve/main/letter_pdf.xq</path>
> −
> <message>
> Error checking function parameter 1 in call
> xmldb:get-child-resources(collection(untyped-value-check[xs:string,
> $path])): The actual cardinality for parameter 1 does not match the
> cardinality declared in the function's signature:
> xmldb:get-child-resources($collection-uri as item()) xs:string*. Expected
> cardinality: exactly one, got 0.
> </message>
> </exception>
>
> --
> - yours
>
>          Srinivasan Krishnamoorthy
>
>
> ------------------------------------------------------------------------------
> Oracle to DB2 Conversion Guide: Learn learn about native support for PL/SQL,
> new data types, scalar functions, improved concurrency, built-in packages,
> OCI, SQL*Plus, data movement tools, best practices and more.
> http://p.sf.net/sfu/oracle-sfdev2dev
> _______________________________________________
> Xsltforms-support mailing list
> Xsl...@li...
> https://lists.sourceforge.net/lists/listinfo/xsltforms-support
>
>

[Xsltforms-support] Date problem in XSLTForms-beta3 - server side transformation -reg

[Raja <m.r...@ni...>]

<div style="font-family: 'Times New Roman'; font-size: 16px;">Hi Alain !!!<br _moz_dirty="" />
Date Problem ::<br _moz_dirty="" />
<br _moz_dirty="" />Date widget is working and displaying the date perfectly in client side transformation. But, not working in server side transformation . Pls find the attached sample code for reference ..<br _moz_dirty="" /><br _moz_dirty="" />
I tested the sample code with client side transformation, that is 
working perfectly. So, problem is in the server side transformation. Pls 
check the attached sample xq file for the testing and tell me the 
possible solution..<br _moz_dirty="" />
<br _moz_dirty="" />
Ps : use exist-db for the testing ..<br _moz_dirty="" />
<br _moz_dirty="" />
thanks and reagrds<br _moz_dirty="" />
Rajamani marimuthu<br _moz_dirty="" />
XRX Team(Lead)</div><br /><br />

[Xsltforms-support] What's this error means

[srinivasan k. <sri...@gm...>]

When i am executing my pdf query i am facing following error message in
browser...........


*<exception>
<path>//db/vserve/main/letter_pdf.xq</path>
-
<message>
Error checking function parameter 1 in call
xmldb:get-child-resources(collection(untyped-value-check[xs:string,
$path])): The actual cardinality for parameter 1 does not match the
cardinality declared in the function's signature:
xmldb:get-child-resources($collection-uri as item()) xs:string*. Expected
cardinality: exactly one, got 0.
</message>
</exception>*

-- 
- yours

         *Srinivasan Krishnamoorthy*

Re: [Xsltforms-support] date control locale

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

Hi,

xf:date format is based on 'format.date' property in config.xsl file. 
The value 'navigator' in the 'language' property allows to load another 
config_##.xsl file from the browser configuration.

If you change these properties in the config.xsl file, you can always 
have the format you want. DC.language is not interpreted for automatic 
switching and Content-Language neither but this might be considered as 
an improvement. The browser cannot directly access Windows system locale.

Thanks!

-Alain

Le 11/12/2010 10:22, ac a écrit :
> Hi,
>
> Sorry for such a newbee question for which I did not manage to find an
> answer in the archive or anywhere else.
>
> I use xf:date controls (the same is true for xsd:date) and I get a date
> in mm-dd-format, despite the fact that my Windows system locale is
> set-up for yyyy-mm-dd, for the fact that the XML date default (e.g.
> ISO8601) is yyyy-mm-dd, and for whatever value in the @content attribute
> of the DC.language and http-equiv="Content-language" meta tags in the
> form header.  How can I get the control to display in yyyy-mm-dd,
> without having to hide its content and specifically replace it with the
> result of a concatenated string?
>
> I am sure that it is something I have overlooked, but what?
>
> Any help would be appreciated.
>
> Thank you
> ac
>
>
> ------------------------------------------------------------------------------
> Oracle to DB2 Conversion Guide: Learn learn about native support for PL/SQL,
> new data types, scalar functions, improved concurrency, built-in packages,
> OCI, SQL*Plus, data movement tools, best practices and more.
> http://p.sf.net/sfu/oracle-sfdev2dev
> _______________________________________________
> Xsltforms-support mailing list
> Xsl...@li...
> https://lists.sourceforge.net/lists/listinfo/xsltforms-support
>

Re: [Xsltforms-support] am trying but not working properly

[Dan M. <dan...@gm...>]

Hello Srinivasan,

I have now updated the Wikibook XQuery XSL-FO section on how to convert your
XML forms to PDF:

http://en.wikibooks.org/wiki/XQuery/Generating_PDF_from_XSL-FO_files#Notes_on_Installing_XSL-FO

This new Wikibook article will walk you through all the steps of configuring
eXist to use the new 1.0 version of the Apache FOP 1.0 libraries.

In the future we hope to make the process of using new versions of extension
libraries a little bit easier.

Please let me know if you have any further questions.

- Dan

On Thu, Dec 9, 2010 at 11:35 PM, srinivasan krishnamoorthy <
sri...@gm...> wrote:

> here i tried to create one pdf when click the button in xsltforms. instead
> of pdf i got some unreadable code give me solution...
>
> i send complete code to you test it in eXist database.....
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> --
> - yours
>
>          *Srinivasan Krishnamoorthy*
>
>
>
> ------------------------------------------------------------------------------
>
> _______________________________________________
> 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

[Xsltforms-support] date control locale

[ac <ac...@hy...>]

Hi,

Sorry for such a newbee question for which I did not manage to find an 
answer in the archive or anywhere else.

I use xf:date controls (the same is true for xsd:date) and I get a date 
in mm-dd-format, despite the fact that my Windows system locale is 
set-up for yyyy-mm-dd, for the fact that the XML date default (e.g. 
ISO8601) is yyyy-mm-dd, and for whatever value in the @content attribute 
of the DC.language and http-equiv="Content-language" meta tags in the 
form header.  How can I get the control to display in yyyy-mm-dd, 
without having to hide its content and specifically replace it with the 
result of a concatenated string?

I am sure that it is something I have overlooked, but what?

Any help would be appreciated.

Thank you
ac

Re: [Xsltforms-support] am trying but not working properly

[Dan M. <dan...@gm...>]

Hello Srinivasan,

I just realized that the old eXist 1.4 build script references the FOP .95
libraries and Apache has now release the FOP 1.0 version.

I would suggest you manually download Apache FOP 1.0 and then put the
following three files in your lib/exteions:

fop.jar
batik-all-1.7.jar
xmlgraphics-commons-1.4.jar

Then you can uncomment out the ant task that tries to do the web get and
rebuild.

I just tested this on a eXist 1.4 and the hello world works fine.

- Dan


On Fri, Dec 10, 2010 at 9:42 AM, Dan McCreary <dan...@gm...>wrote:

> Srinivasan,
>
> Perhaps you should post these questions on the exist-open list since your
> problems are not really related to XSLTForms.
>
> Since you have not sent us the exact error message I can only guess what is
> wrong.  Just a few hints:
>
> The following line:
>
>     declare option exist:serialize "method=xhtml media-type=text/html
> indent=no";
>
> Should not be used when you are sending PDF binaries to the client from
> eXist.  This only applies when you are sending XML to the client.
>
> Here are some things to check.
>
> Have you edited your eXist $EXIST_HOME/config file to load the OPTIONAL
> XSL-FO Module?  To do this you must copy it from the commented area to the
> uncommitted area.
>
> Have you enable the XSL-FO extenion in your $EXIST_HOME/build.properties
>
> include.module.xslfo = *false*
>
> to be
>
> include.module.xslfo = true
>
> Make SURE you change false to be true
>
> See
>
> http://demo.exist-db.org/exist/configuration.xml
>
> Have you downloaded the latest XSL FO binary?  You will need to make SURE
> you have fo.jar in your CLASSPATH when eXist starts up.
>
> Have you checked the log files for error messages?
>
> The most important thing for you to know that this does work if the eXist
> server is configured correctly.
>
> Make sure you get the "hello world" demo working first and keep detailed
> notes of all the functions you do and post a note to the exist-open mailing
> list.
>
> Good Luck Srinivasan!
>
>  - Dan
>
> On Thu, Dec 9, 2010 at 11:35 PM, srinivasan krishnamoorthy <
> sri...@gm...> wrote:
>
>> here i tried to create one pdf when click the button in xsltforms. instead
>> of pdf i got some unreadable code give me solution...
>>
>> i send complete code to you test it in eXist database.....
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> --
>> - yours
>>
>>          *Srinivasan Krishnamoorthy*
>>
>>
>>
>> ------------------------------------------------------------------------------
>>
>> _______________________________________________
>> 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
>



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

Re: [Xsltforms-support] am trying but not working properly

[Dan M. <dan...@gm...>]

Srinivasan,

Perhaps you should post these questions on the exist-open list since your
problems are not really related to XSLTForms.

Since you have not sent us the exact error message I can only guess what is
wrong.  Just a few hints:

The following line:

    declare option exist:serialize "method=xhtml media-type=text/html
indent=no";

Should not be used when you are sending PDF binaries to the client from
eXist.  This only applies when you are sending XML to the client.

Here are some things to check.

Have you edited your eXist $EXIST_HOME/config file to load the OPTIONAL
XSL-FO Module?  To do this you must copy it from the commented area to the
uncommitted area.

Have you enable the XSL-FO extenion in your $EXIST_HOME/build.properties

include.module.xslfo = *false*

to be

include.module.xslfo = true

Make SURE you change false to be true

See

http://demo.exist-db.org/exist/configuration.xml

Have you downloaded the latest XSL FO binary?  You will need to make SURE
you have fo.jar in your CLASSPATH when eXist starts up.

Have you checked the log files for error messages?

The most important thing for you to know that this does work if the eXist
server is configured correctly.

Make sure you get the "hello world" demo working first and keep detailed
notes of all the functions you do and post a note to the exist-open mailing
list.

Good Luck Srinivasan!

 - Dan

On Thu, Dec 9, 2010 at 11:35 PM, srinivasan krishnamoorthy <
sri...@gm...> wrote:

> here i tried to create one pdf when click the button in xsltforms. instead
> of pdf i got some unreadable code give me solution...
>
> i send complete code to you test it in eXist database.....
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> --
> - yours
>
>          *Srinivasan Krishnamoorthy*
>
>
>
> ------------------------------------------------------------------------------
>
> _______________________________________________
> 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

Re: [Xsltforms-support] creating pdf using xsltforms

[Dan M. <dan...@gm...>]

Hello Srinivasan,

Here is the way that I do it:

http://en.wikibooks.org/wiki/XQuery/Generating_PDF_from_XSL-FO_files

I transform the XML into XSL-FO on the server using XQuery typeswich
transform.  I don't use XSLT on the server any more.  See this article:

http://en.wikibooks.org/wiki/XQuery/Typeswitch_Transformations

- Dan

On Thu, Dec 9, 2010 at 6:53 AM, srinivasan krishnamoorthy <
sri...@gm...> wrote:

>
> I need sample code for generating pdf using xsltforms...... anybody help
> me...
>
> the flow of genrate pdf is
>
>
>
>  *sample.xq ( from here i submit some values to pdf generating query )
> ------->
>
>           pdfgenrating query ( samp.xsl + <xml>get values from previous
> form</xml>) ------->
>
>                      Final output pdf
> *
>
>
> --
> - yours
>
>          *Srinivasan Krishnamoorthy*
>
>
>
> ------------------------------------------------------------------------------
> This SF Dev2Dev email is sponsored by:
>
> WikiLeaks The End of the Free Internet
> http://p.sf.net/sfu/therealnews-com
> _______________________________________________
> 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

[Xsltforms-support] creating pdf using xsltforms

[srinivasan k. <sri...@gm...>]

I need sample code for generating pdf using xsltforms...... anybody help
me...

the flow of genrate pdf is



 *sample.xq ( from here i submit some values to pdf generating query )
------->

          pdfgenrating query ( samp.xsl + <xml>get values from previous
form</xml>) ------->

                     Final output pdf
*


-- 
- yours

         *Srinivasan Krishnamoorthy*

Re: [Xsltforms-support] date issue in XSLTForms-beta3 -reg

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

Hello Raja,

Apparently the config.xsl file is not received by the browser after 
refreshing. That's why there is no text in the widget.

Can you use a browser debugger to trace HTTP requests and responses? Can 
you post a link?

Thanks!

-Alain

Le 08/12/2010 10:09, Raja a écrit :
> Hi XSLTForms members !!!
>
> We facing date widget display problem in XSLTForms-beta3 version, 
> while using with eXis-db the very first time it's rendering the date 
> widget but, once u refreshed the page it's not showing the widget 
> properly. pls see the attached image .. How will i avoid this problem ..
>
> By
> -- 
> Rajamani Marimuthu
> Junior Research Fellow-JRF
> NIC -Open Technology Centre
> Rajaji Bhavan
> Besant Nagar,
> Chennai - 90
> Cell : 9791125383
>

Re: [Xsltforms-support] labels for empty values in select1

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

Hello Jens,

XForms W3C Working Group  actually discussed today about expected 
behavior with an empty value in select1 and how to interpret this 
sentence: "For both closed and open selections, any selection item with 
a storage value which is empty or which contains only white space 
characters must remain deselected."

Comparing to XSLTForms Beta 2, XSLTForms Beta 3 RC is adding itself an 
empty value in the HTML select/option elements and it is probably 
interfering now.

Can you please post your own test case?

Thanks!

-Alain

Le 08/12/2010 21:01, Jens Østergaard Petersen a écrit :
> Hi,
>
> XSLTForms Beta 2 has a feature that Beta 3 RC is lacking: if the instance has an empty value for an item in a select1 drop-down, one cannot display a label for it.
>
> My instance has "<titleInfo lang="" type="">" and with Beta 2 I can show "Basic Title Information" for the empty @type and "(no language selected)" for the empty @lang attribute, with:
>
> <item>
> 	<label>Basic Title Information</label>
> 	<value/>
> </item>
>
> and
>
> <item>
> 	<label>(no language selected)</label>
> 	<value/>
> </item>
>
> With Beta 3 RC one gets a blank select1.
>
> Is there a way to get back this feature? Or was there a reason to discard it? I need Beta 3 RC for other things, so I can't revert to Beta 2.
>
> Best,
>
> Jens
>
>
> ------------------------------------------------------------------------------
> This SF Dev2Dev email is sponsored by:
>
> WikiLeaks The End of the Free Internet
> http://p.sf.net/sfu/therealnews-com
>
>
> _______________________________________________
> Xsltforms-support mailing list
> Xsl...@li...
> https://lists.sourceforge.net/lists/listinfo/xsltforms-support