xsltforms-support — XSLTForms support list

Re: [Xsltforms-support] Form data modification with Javascript

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

Hello Ivan,
> Hello,
>
> We are using xsltForms for quite a while. Great idea and a great
> implementation. Still our developers constantly face several problems
> that I can't solve.
Can you tell me how many developers are using XSLTForms?
> We sometimes need to select value from a huge list, stored in the
> database. Traditional comboboxes and scrollboxes is not a solution in
> this case, because the whole list of values (tens of thousands of
> records) can't be placed in a webpage source. We have written special
> Javascript (GWT) code, that shows a dialogue that allows one to filter
> and pick a value from a huge list using AJAX techniques. The dialogue
> saves chosen value (id and name) into the instance and refreshes the
> whole form (xforms.ready = false; xforms.refresh(); xforms.ready =
> true;). The problem of such an approach is that this type of refresh
> sometimes fails to refresh constraints. The question is: what is the
> most reliable way to automate insertion of data into form fields using
> Javascript?
Have a look at XFControl.prototype.valueChanged method: each time a node 
value is modified by a control, it is added in a list maintained for 
each model. This list is then read when refreshing.

Thank you for your feedbacks!

-Alain

Re: [Xsltforms-support] Output image/svg+xml

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

> I think I understand what the "data:" scheme is about (never used it
> before). I thought the "ref" attribute was used to resolve an URI (just
> like with<output mediatype="image/jpeg">), but it seems that, in the
> case of "image/svg+xml", XSLTForms uses this attribute to get an «SVG
> instance». Am I right?
>
> If so, is there a way to display a non-embedded SVG file whose URL is
> computed by XForms?
According to XForms 1.1 specifications at 
http://www.w3.org/TR/xforms/#ui-output, this can be forced with a 
binding to xsd:anyURI.

Sorry, this is not yet implemented in XSLTForms...

-Alain

Re: [Xsltforms-support] Output image/svg+xml

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

> I want to call a web-service that returns an SVG image. So I use :
>
> <xf:output
>    mediatype="image/svg+xml"
>    ref="concat('/services/charts/' , instance('test')/value)"
>    model="some-model"
> />
Apparently, you're trying to create a dynamic XPath expression!!!

I'm more and more considering adding an eval() function, specially for 
debugging but it seems that you should first try with something like this:

ref="/services/charts/*[name() = instance('test')/value]"

SVG support in XSLTForms is still experimental and you might have to 
adjust sizes manually.

Thank you for your feedbacks!

-Alain

Re: [Xsltforms-support] updated demo WFS 'paging' page

[Stephen C. <Ste...@ut...>]

-----Original Message-----
From: C. M. Sperberg-McQueen [mailto:cm...@bl...] 
Sent: Monday, 17 January 2011 6:34 AM
To: Stephen Cameron
Cc: C. M. Sperberg-McQueen
Subject: Re: [Xsltforms-support] updated demo WFS 'paging' page

[offline]

On Jan 13, 2011, at 12:20 AM, Stephen Cameron wrote:

> http://preview.emii.org.au/aatams/test/view_all_receiver_deployments_paged.xml
>  
> Hi All,
>  
> This is my demo 'paging table' now working with the data-island branch of XSLTForms (thanks Alain).
>  
> Also there is a Filter/Sort button added at the bottom taking you to a prototype filtering and sorting parameters interface. This has some bugs presently and does not actually filter or sort (as I'm looking for a cleaner way of building the filter model instance). Once this is working I will have a fully functional CRUD framework using Xforms and a Web Feature Service (WFS) for managing spatial data.
>  
> This is slow in IE but I don't actually show this version to IE users now, just a full set of data in a table with no paging.
>  
> It works fine in most other browsers, so....
>  
> The one thing lacking is something to indicate (e.g. spinning wheel) when a request is in progress getting the next set of pages from the server.

> Looks great in all the browsers I've tried (Opera, Firefox, Safari, Chrome),
though somewhat slow to load (I started this note to tell you Safari was
failing to display anything more than the headings, but in the meantime
the rest of the data has arrived).

This is running on a test server and will be a little quicker to generate the data on the server side once moved. Also, I have the strong notion that XSLTForms will continue to improve performance wise. 

Currently the server is limited to generating complex XML via 'composition' from a relational database, a new version of the WFS server (see below) offers the possibility to avoid this, not quite an XML database but close.


> If I show this to students, I'd like to have some idea of what the page is 
about.

> So: one question about the information being shown.  If I'm understanding
things correctly (I should read the pages on the eMII and IMOS sites more 
carefully, obviously), the AATAMS program has a lot of (acoustic?) receivers
at fixed locations, which collect data from transmitters attached to marine
animals, allowing their movements to be tracked at some level of 
granularity.  And the page you point to is showing information on all
the currently deployed receivers.  Is that roughly correct?

Yes, but current and past deployed receivers, the data is not real time as the receivers must be recovered to download the data. The data visible (on a test system) is not up to date but one of the IMOS project aims are to make all data collected publicly available as soon as practical.

The idea behind using Xforms (and XSLTForms specifically) was to have a simple two tier client server system to manage the data. The server tier is the Open Geospatial Consortium (OGC) 'Web Feature Service' (WFS), a general-purpose spatial data web service standard. My main interest being schema generated forms with the idea that you can quickly create a web-interface for common 'scientific data' collection and access, mainly for so-called metadata purposes, which is where XML is most useful (somewhat inspired by XRX). WFS mainly builds on Geographic Markup Language (GML) for representing spatial properties of 'features', but this spatial aspect is optional.

The 'deegree' implementation of the WFS 1.0 standard is what I am using as it supports 'complex' features, that is features having subfeatures. Unfortunately the ability to update such subfeatures is not presently available, which has proved to be a significant limitation in the kind a use I am attempting to put it too. However, the WFS 2.0 standard addresses this problem and is close to being implemented in deegree WFS v3.0.

I intend to make the schema generated XForms XSLT templates available very soon, when the filter and sort interface is working. These are presently specific to WFS, but I'm very interested (at some stage) to make them general, or someone else might like to try.

> Oh, and one other question:  is it the Australian Animal 
Tagging and Monitoring System? or the Australian Acoustic 
Tagging and Monitoring System? or are they the same thing 
under two names?

Should be "Animal Tagging" there was a name change about a year ago, when the project broadened its scope.

> Nice work!

Thanks for your interest.

-- 
****************************************************************
* C. M. Sperberg-McQueen, Black Mesa Technologies LLC
* http://www.blackmesatech.com 
* http://cmsmcq.com/mib                 
* http://balisage.net
****************************************************************

Re: [Xsltforms-support] Setting decimal separator in input fields

[C. M. Sperberg-M. <cm...@bl...>]

On Jan 16, 2011, at 10:06 AM, Ivan Ponomarev wrote:

> Hello again,
> 
> another question:
> 
> 2. Is there some direct way to set comma as decimal separator for number 
> input fields? Comma is the the standard for decimal separator in Russia 
> and for end users of the form, in XML file there should still be dot.

For this and for any other kind of localization, one simple approach
is this:  instead of binding the user-interface widget to the element
in the main document instance, calculate its (string) value by some
XPath expression - and when the widget is changed by the user,
perform the opposite calculation.  

It may be simpler if you create an auxiliary document to hold
an element with the localized value.  Then the value of the
localized element may be calculated from the 'standard' value
by an expression like

   translate(instance('main')/std-num, '.', ',')

and conversely, the value of the standard element can be
calculated from the localized element by

  translate(instance('localized')/localized-num, ',', '.')

Of course, you'll have to enforce the constraints on the
lexical form of the number yourself, and you'll also have to
do your own constraints for things like minimum and maximum
value.  But it's not really too hard.

The W3C i18n working group pushed hard for XSD datatypes
to have formats that are standardized and very simple; one
reason was that they hoped to ensure that almost everyone
would have to write a localization layer into their software to
show the data to the user in a form the user would find natural.
(They were disappointed that the date format took the form 
specified by ISO 8601; they would have preferred a simple
integer indicating the number of days since some epoch.)

It might be a helpful enhancement of XForms to build some
localization layer into the spec.  But in the meantime, it should
not be too hard to do it yourself in the form.

I hope this helps.

Michael Sperberg-McQueen


-- 
****************************************************************
* C. M. Sperberg-McQueen, Black Mesa Technologies LLC
* http://www.blackmesatech.com 
* http://cmsmcq.com/mib                 
* http://balisage.net
****************************************************************

[Xsltforms-support] Patch suggestion for xsltforms.js

[Ivan P. <ipo...@ma...>]

Hello, Alain,

maybe you will find it reasonable to include the following patch for 
xforms.close() procedure in the next versions of XSLTforms.

After

xforms.dispose(document.documentElement);

there should be a call to

dropHasXFElement(document.documentElement);


where dropHasXFElement is implemented as follows:

function dropHasXFElement(element){
	element.hasXFElement = null;
	var subelement = element.firstChild;
	while(subelement){
		if (subelement.nodeType == NodeType.ELEMENT)
				dropHasXFElement(subelement);
		subelement = subelement.nextSibling;
	}
}


The rationale for this patch is following. We are using xsltforms in GWT 
environment, which means that we cannot reload the HTML page each time 
we have to show another form for the user. So we just

1) call xsltforms.close() to clean up everything,
2) remove <div>  with the old form from page,
3) generate another portion of HTML+Javascript using xlstform.xsl,
4) put all this on page DYNAMICALLY in <div> and <script>s,
5) and then call init() procedure.

The problem we faced was the unstable behavior of some forms starting 
from the second call of xsltforms.close(). I spent half a day in Firebug 
stepping through xlstforms.js and found out that the problem was in fact 
that Firefox uses OLD VALUES of hasXFElement attribute for DOM elements 
that were dynamically recreated. I think the code above is quite clear 
and it solves our problem.

Regards,

Ivan Ponomarev

[Xsltforms-support] Calculation depends on the order of binds -- is it how it was meant to be?

[Ivan P. <ipo...@ma...>]

5. Calculation depends on the order of binds. It's OK if this behavior 
is going to remain the same. But I'm afraid, it might fail some day.

The model is

<fs:schema><fs:test1/><fs:test2/><fs:test3/></fs:schema>

this works

<xf:bind nodeset= "/fs:schema/fs:test2" calculate = "/fs:schema/fs:test1"/>
<xf:bind nodeset= "/fs:schema/fs:test3" calculate = "/fs:schema/fs:test2"/>

this doesn't work

<xf:bind nodeset= "/fs:schema/fs:test3" calculate = "/fs:schema/fs:test2"/>
<xf:bind nodeset= "/fs:schema/fs:test2" calculate = "/fs:schema/fs:test1"/>

Regards,

Ivan Ponomarev

[Xsltforms-support] Problems with Calendar control

[Ivan P. <ipo...@ma...>]

Hello,

here is a couple of problems related to date picker:

3. Every second time Calendar control tends just to remain on screen 
after selecting date. This happens in Chrome, Firefox, ie7 & ie8.

4. Another problem with calendar:  we live in time zone GMT +3 (Moscow)
If we try to work with form from 0 to 3am (yeah, sometimes we work at 
night:))), then each exit from date control (by mouse clicking on any 
other control) will increase date by +1.

Regards,

Ivan Ponomarev

[Xsltforms-support] Setting decimal separator in input fields

[Ivan P. <ipo...@ma...>]

Hello again,

another question:

2. Is there some direct way to set comma as decimal separator for number 
input fields? Comma is the the standard for decimal separator in Russia 
and for end users of the form, in XML file there should still be dot.

Regards,

Ivan Ponomarev

[Xsltforms-support] Form data modification with Javascript

[Ivan P. <ipo...@ma...>]

Hello,

We are using xsltForms for quite a while. Great idea and a great 
implementation. Still our developers constantly face several problems 
that I can't solve. Probably someone has already overcome them. Help for 
any of these issues will be appreciated, and we'll be glad to provide 
further information, if needed.

Instead of putting the whole list in one email, I decided to break it 
into several separate emails to make it easier to maintain separate 
conversations.

1. We sometimes need to select value from a huge list, stored in the 
database. Traditional comboboxes and scrollboxes is not a solution in 
this case, because the whole list of values (tens of thousands of 
records) can't be placed in a webpage source. We have written special 
Javascript (GWT) code, that shows a dialogue that allows one to filter 
and pick a value from a huge list using AJAX techniques. The dialogue 
saves chosen value (id and name) into the instance and refreshes the 
whole form (xforms.ready = false; xforms.refresh(); xforms.ready = 
true;). The problem of such an approach is that this type of refresh 
sometimes fails to refresh constraints. The question is: what is the 
most reliable way to automate insertion of data into form fields using 
Javascript?


Regards,

Ivan Ponomarev

Re: [Xsltforms-support] Output image/svg+xml

[Grégoire C. <gco...@gm...>]

Hi,

I think I understand what the "data:" scheme is about (never used it
before). I thought the "ref" attribute was used to resolve an URI (just
like with <output mediatype="image/jpeg">), but it seems that, in the
case of "image/svg+xml", XSLTForms uses this attribute to get an «SVG
instance». Am I right?

If so, is there a way to display a non-embedded SVG file whose URL is
computed by XForms?

Thanks!
Grégoire

Le 16/01/2011 14:48, Grégoire COLBERT a écrit :
> Hi Alain,
>
> I want to call a web-service that returns an SVG image. So I use :
>
> <xf:output
>   mediatype="image/svg+xml"
>   ref="concat('/services/charts/' , instance('test')/value)"
>   model="some-model"
> />
>
> XSLTForms generates something like this :
>
>   data:image/svg+xml,/services/charts/310
>
> and the browser complains about an empty document where the image should
> appear :
>
> «
>   This page contains the following errors:
>
>   error on line 1 at column 1: Document is empty
>
>   Below is a rendering of the page up to the first error.
> »
>
> When I use the same URL directly with a <img> tag, the image is ok
> (obviously I test with a browser that accepts an SVG image in a <img>
> tag, e.g. Firefox 4 or Chrome, but not Firefox 3).
>
> Is there an issue with the way XSLTForms displays SVG pictures? Or is
> this a misunderstanding an my side?
>
> Thank you for your help!
>
> Grégoire

[Xsltforms-support] Output image/svg+xml

[Grégoire C. <gco...@gm...>]

Hi Alain,

I want to call a web-service that returns an SVG image. So I use :

<xf:output
  mediatype="image/svg+xml"
  ref="concat('/services/charts/' , instance('test')/value)"
  model="some-model"
/>

XSLTForms generates something like this :

  data:image/svg+xml,/services/charts/310

and the browser complains about an empty document where the image should
appear :

«
  This page contains the following errors:

  error on line 1 at column 1: Document is empty

  Below is a rendering of the page up to the first error.
»

When I use the same URL directly with a <img> tag, the image is ok
(obviously I test with a browser that accepts an SVG image in a <img>
tag, e.g. Firefox 4 or Chrome, but not Firefox 3).

Is there an issue with the way XSLTForms displays SVG pictures? Or is
this a misunderstanding an my side?

Thank you for your help!

Grégoire

Re: [Xsltforms-support] XSLTForms and for(var i in list) construct

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

Le 11/01/2011 20:43, Leigh L Klotz Jr a écrit :
> In a few places, XSLTForms uses for(var i in list).
> This construct is not recommended for iteration over arrays.
>
> See
> https://developer.mozilla.org/en/JavaScript/Reference/Statements/for...in
> and other sources.
>
>
> This JavaScript idiom fail when prototype.js is loaded.
>
> Below is my best guess at which lines are in error.  I've not tested
> them all, but at least dispatchList works now.
I have checked them all and fixed some typos. I didn't find other 
instructions to be changed. I haven't performed specific tests but 
general ones.

Thank you for your feedbacks!

-Alain

Re: [Xsltforms-support] XSLTForms name conflict: Event

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

Le 11/01/2011 20:40, Leigh L Klotz Jr a écrit :
> XSLTForms defines a number of top-level variables, some of which have
> generic names.
>
> The Event object, in particular, conflicts with other libraries.
>
> It would be best to put all of XSLTForms in a single top-level object
> named XSLTForms.
> However, it may be OK for now to rename "var Event" to "var XSLTFormsEvent".
>
> Otherwise, you can't use XSLTForms with external widget libraries.
>
> Leigh.
>
Thank you for pointing at this name conflict!

I agree with you about use of a unique top-level object. A subforms 
mechanism would also require this.

Before that, I renamed "Event" into "XSLTFormsEvent" as you suggested.

Can you give the name(s) of those external widget libraries you would 
like to use?

Thanks!

-Alain

[Xsltforms-support] Using Saxon to process XSLTForms in eXist

[Jens Ø. P. <oe...@gm...>]

Hi,

I would like to ask if there are any issues connected with using Saxon instead of Xalan as the XSLT processor in eXist 1.5 when using XSLTForms? Does the change from an XSLT 1.0 to an XSLT 2.0 processor give rise to any problems?

I find that this makes processing much faster.

Best,

Jens

[Xsltforms-support] updated demo WFS 'paging' page

[Stephen C. <Ste...@ut...>]

http://preview.emii.org.au/aatams/test/view_all_receiver_deployments_paged.xml

Hi All,

This is my demo 'paging table' now working with the data-island branch of XSLTForms (thanks Alain).

Also there is a Filter/Sort button added at the bottom taking you to a prototype filtering and sorting parameters interface. This has some bugs presently and does not actually filter or sort (as I'm looking for a cleaner way of building the filter model instance). Once this is working I will have a fully functional CRUD framework using Xforms and a Web Feature Service (WFS) for managing spatial data.

This is slow in IE but I don't actually show this version to IE users now, just a full set of data in a table with no paging.

It works fine in most other browsers, so....

The one thing lacking is something to indicate (e.g. spinning wheel) when a request is in progress getting the next set of pages from the server.

Regards

Steve Cameron

[Xsltforms-support] Huge performance improvement using Tabs!

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

We could achieve significant performance improvements with the help of tabs.
We know that most of the time is spent in the refresh method where xsltforms
iterates through all the elements in topdown manner. We made changes to
xsltforms with the help of which only the selected tab is refreshed. The
changes done in the tab have localized effect. If anything is changed within
that tab, only that tab is refreshed.
If having multiple tabs suits for your application, you can get away without
having to deal with the refresh/slow xpath evaluations.

Next amazing thing would be generating tabs at runtime, when an object is
added it should be seen in a new tab.

Re: [Xsltforms-support] FW: Load Time Performance improvement - It works!

[Christian M. <chr...@mu...>]

interesting idea
Thanks.

On Wed, Jan 12, 2011 at 9:56 AM, Stephen Cameron
<Ste...@ut...> wrote:
> I don't use exist so cannot comment on that aspect.
>
> However, resorting to parsing the whole generated javascript sounds like a bad idea, there is usually a way forward within the standard XForms functionality.
>
> A GET request can be built from within the form and then sent off to load another instance with dynamic query key-value pairs.
>
> I think I have discussed Alain at one time, to put GET request parameters of the form request into a default model instance, so that they can be accessed from within the form to then load another 'real' instance using "xforms-model-construct-done" event.
>
>
>
>
>
> -----Original Message-----
> From: ch...@gm... [mailto:ch...@gm...] On Behalf Of Christian Meisenbichler
> Sent: Wednesday, 12 January 2011 7:35 PM
> To: Stephen Cameron
> Subject: Re: [Xsltforms-support] FW: Load Time Performance improvement - It works!
>
> Concerning caching of xsltforms transform. I was forced to do caching
> of the transform as well because the transform takes about 2 min! the
> caching is fine because I only need to update the location of the
> model and the post URI. That said the search and replace operation to
> do so is very slow with the xquery functions provided by eXistdb. It
> is the major part of the load time now. If I only had to parse a
> smaller piece of text than the whole generated javascript, or maybe
> set the values in a separate piece of code. I think I could improve
> load times dramatically.
>
> I would need a way to replace or modify the submission and instance
> objects created by
>
> "new XFSubmission" and "new XFInstance"
>
> Are there methods to do this? I am not very experienced in javascript,
> so digging trough the javascript code is a bit over my head. Any
> ideas?
>
> On Wed, Jan 12, 2011 at 12:22 AM, Stephen Cameron
> <Ste...@ut...> wrote:
>>
>>
>>
>> I do this pre-transformation (compilation) as well using Saxon, the result has never given me any problems in the browser.
>>
>>
>>
>> From: Dan McCreary [mailto:dan...@gm...]
>> Sent: Wednesday, 12 January 2011 3:45 AM
>> To: Santosh Chandak
>> Cc: XSLTForms support
>> Subject: Re: [Xsltforms-support] Load Time Performance improvement - It works!
>>
>>
>>
>> This sounds like a very useful result.
>>
>> Thank you for sharing.
>>
>> - Dan
>>
>> On Tue, Jan 11, 2011 at 7:53 AM, Santosh Chandak <san...@gm...> wrote:
>>
>> A simple trick has helped our form to reduce load time from 30 seconds to 4 seconds. If form is big, XSLTForms transform takes some time to create the HTML elements. If we create the output HTML beforehand, the time spent in transforming the xml to html can be saved. I used java saxon8 xslt transformer for our 104 K size form. Result is saved to a HTML page, which can be loaded directly.
>>
>> I hope this will help others as well!
>>
>>
>> ------------------------------------------------------------------------------
>> Gaining the trust of online customers is vital for the success of any company
>> that requires sensitive data to be transmitted over the Web.   Learn how to
>> best implement a security strategy that keeps consumers' information secure
>> and instills the confidence they need to proceed with transactions.
>> http://p.sf.net/sfu/oracle-sfdevnl
>> _______________________________________________
>> 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
>>
>> ------------------------------------------------------------------------------
>> Protect Your Site and Customers from Malware Attacks
>> Learn about various malware tactics and how to avoid them. Understand
>> malware threats, the impact they can have on your business, and how you
>> can protect your company and customers by using code signing.
>> http://p.sf.net/sfu/oracle-sfdevnl
>> _______________________________________________
>> Xsltforms-support mailing list
>> Xsl...@li...
>> https://lists.sourceforge.net/lists/listinfo/xsltforms-support
>>
>
> ------------------------------------------------------------------------------
> Protect Your Site and Customers from Malware Attacks
> Learn about various malware tactics and how to avoid them. Understand
> malware threats, the impact they can have on your business, and how you
> can protect your company and customers by using code signing.
> http://p.sf.net/sfu/oracle-sfdevnl
> _______________________________________________
> Xsltforms-support mailing list
> Xsl...@li...
> https://lists.sourceforge.net/lists/listinfo/xsltforms-support
>

Re: [Xsltforms-support] FW: Load Time Performance improvement - It works!

[Stephen C. <Ste...@ut...>]

I don't use exist so cannot comment on that aspect.

However, resorting to parsing the whole generated javascript sounds like a bad idea, there is usually a way forward within the standard XForms functionality. 

A GET request can be built from within the form and then sent off to load another instance with dynamic query key-value pairs.

I think I have discussed Alain at one time, to put GET request parameters of the form request into a default model instance, so that they can be accessed from within the form to then load another 'real' instance using "xforms-model-construct-done" event.





-----Original Message-----
From: ch...@gm... [mailto:ch...@gm...] On Behalf Of Christian Meisenbichler
Sent: Wednesday, 12 January 2011 7:35 PM
To: Stephen Cameron
Subject: Re: [Xsltforms-support] FW: Load Time Performance improvement - It works!

Concerning caching of xsltforms transform. I was forced to do caching
of the transform as well because the transform takes about 2 min! the
caching is fine because I only need to update the location of the
model and the post URI. That said the search and replace operation to
do so is very slow with the xquery functions provided by eXistdb. It
is the major part of the load time now. If I only had to parse a
smaller piece of text than the whole generated javascript, or maybe
set the values in a separate piece of code. I think I could improve
load times dramatically.

I would need a way to replace or modify the submission and instance
objects created by

"new XFSubmission" and "new XFInstance"

Are there methods to do this? I am not very experienced in javascript,
so digging trough the javascript code is a bit over my head. Any
ideas?

On Wed, Jan 12, 2011 at 12:22 AM, Stephen Cameron
<Ste...@ut...> wrote:
>
>
>
> I do this pre-transformation (compilation) as well using Saxon, the result has never given me any problems in the browser.
>
>
>
> From: Dan McCreary [mailto:dan...@gm...]
> Sent: Wednesday, 12 January 2011 3:45 AM
> To: Santosh Chandak
> Cc: XSLTForms support
> Subject: Re: [Xsltforms-support] Load Time Performance improvement - It works!
>
>
>
> This sounds like a very useful result.
>
> Thank you for sharing.
>
> - Dan
>
> On Tue, Jan 11, 2011 at 7:53 AM, Santosh Chandak <san...@gm...> wrote:
>
> A simple trick has helped our form to reduce load time from 30 seconds to 4 seconds. If form is big, XSLTForms transform takes some time to create the HTML elements. If we create the output HTML beforehand, the time spent in transforming the xml to html can be saved. I used java saxon8 xslt transformer for our 104 K size form. Result is saved to a HTML page, which can be loaded directly.
>
> I hope this will help others as well!
>
>
> ------------------------------------------------------------------------------
> Gaining the trust of online customers is vital for the success of any company
> that requires sensitive data to be transmitted over the Web.   Learn how to
> best implement a security strategy that keeps consumers' information secure
> and instills the confidence they need to proceed with transactions.
> http://p.sf.net/sfu/oracle-sfdevnl
> _______________________________________________
> 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
>
> ------------------------------------------------------------------------------
> Protect Your Site and Customers from Malware Attacks
> Learn about various malware tactics and how to avoid them. Understand
> malware threats, the impact they can have on your business, and how you
> can protect your company and customers by using code signing.
> http://p.sf.net/sfu/oracle-sfdevnl
> _______________________________________________
> Xsltforms-support mailing list
> Xsl...@li...
> https://lists.sourceforge.net/lists/listinfo/xsltforms-support
>

[Xsltforms-support] FW: Load Time Performance improvement - It works!

[Stephen C. <Ste...@ut...>]

I do this pre-transformation (compilation) as well using Saxon, the result has never given me any problems in the browser.

From: Dan McCreary [mailto:dan...@gm...]
Sent: Wednesday, 12 January 2011 3:45 AM
To: Santosh Chandak
Cc: XSLTForms support
Subject: Re: [Xsltforms-support] Load Time Performance improvement - It works!

This sounds like a very useful result.

Thank you for sharing.

- Dan
On Tue, Jan 11, 2011 at 7:53 AM, Santosh Chandak <san...@gm...<mailto:san...@gm...>> wrote:
A simple trick has helped our form to reduce load time from 30 seconds to 4 seconds. If form is big, XSLTForms transform takes some time to create the HTML elements. If we create the output HTML beforehand, the time spent in transforming the xml to html can be saved. I used java saxon8 xslt transformer for our 104 K size form. Result is saved to a HTML page, which can be loaded directly.

I hope this will help others as well!


------------------------------------------------------------------------------
Gaining the trust of online customers is vital for the success of any company
that requires sensitive data to be transmitted over the Web.   Learn how to
best implement a security strategy that keeps consumers' information secure
and instills the confidence they need to proceed with transactions.
http://p.sf.net/sfu/oracle-sfdevnl
_______________________________________________
Xsltforms-support mailing list
Xsl...@li...<mailto: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] F1 message box and double click in svn r470

[Leigh L K. Jr <lei...@xe...>]

On 12/21/2010 10:31 PM, COUTHURES Alain wrote:
> Le 21/12/2010 23:37, Leigh L Klotz Jr a écrit :
>> 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.
>>
> Double click is not mentioned in XForms specifications but was 
> probably too intrusive because it might happen accidentally so I 
> changed it to F1 instead.
>
> Browsers already intercept F1 for their own help/credits and some 
> analysis I fund said that it usually was involuntary. The other 
> function keys seem more useful and Opera is defining all of them!
>
> What else? A splash box wouldn't be nice, of course... Neither a 
> static line at the end of each page...
>
> BTW, this message box shouldn't only display credits but also specific 
> debug statistics such as:
>
>     * size of instances
>     * Javascript loading time
>     * cumulative refresh time
>     * longest XPath expression evaluation times
>
> XSLTForms has an LGPL license and I'm sure just few developers will 
> hesitate to comment the corresponding Javascript instruction or change 
> the interception again if they need to. Beginners probably won't 
> change anything but won't press F1 either unless they're looking for 
> help/credits!
>
> Donations for XSLTForms are inexistent and, except in Steven 
> Pemberton's and Kurt Cagle's papers and in your own personal site, I 
> never see any publicity or credits for it. If XSLTForms is just used 
> for prototyping, F1 shouldn't be a problem at all.
>
> Do you have another suggestion?
>
> Thanks!
>
> -Alain

Yes, I have a few suggestions:

1. As Gregoire said, output the "powered by" info in a comment.
2. Enable F1 only when Debug is on.
3. We can't and won't make donations.  However, we've paid for support, 
and I know others have as well.  We're happy to pay for support.  I 
suspect if you put an option on your page for a support agreement, you'd 
attract more.
4. As for more intrusive stuff, it's my opinion that one of the reasons 
that FormsPlayer wasn't more widely adopted is that it put big icons 
with "powered by FormsPlayer" next to each form control.  Those too had 
debug info in them, and if you bought a paid copy you could remove them, 
but I believe their presence caused many to simply abandon interest long 
before that point came.

Leigh.

[Xsltforms-support] XSLTForms and for(var i in list) construct

[Leigh L K. Jr <lei...@xe...>]

In a few places, XSLTForms uses for(var i in list).
This construct is not recommended for iteration over arrays.

See
https://developer.mozilla.org/en/JavaScript/Reference/Statements/for...in
and other sources.


This JavaScript idiom fail when prototype.js is loaded.

Below is my best guess at which lines are in error.  I've not tested 
them all, but at least dispatchList works now.


$ diff -u xsltforms.js.orig xsltforms.js.new
--- xsltforms.js.orig    2011-01-05 14:29:26.000000000 -0800
+++ xsltforms.js.new    2011-01-11 11:42:25.100306926 -0800
@@ -1166,7 +1166,7 @@
          }

          if (this.callstack) {
-            for (var i in this.callstack) {
+            for (var i = 0, len = this.callstack.length; i < len; i++) {
                  DebugConsole.write("> " + this.callstack[i]);
              }
          }
@@ -1791,7 +1791,7 @@
              return res;
      },
      clear : function() {
-        for (var i in this.data) {
+        for (var i = 0, len = this.data.lengt; i < len; i++) {
              this.data[i] = null;
          }

@@ -7056,8 +7056,8 @@


  XMLEvents.dispatchList = function(list, name) {
-    for (var id in list) {
-        XMLEvents.dispatch(list[id], name);
+    for (var i = 0, len = list.length; i < len; i++) {
+        XMLEvents.dispatch(list[i], name);
      }
  };

@@ -7103,7 +7103,7 @@
                  ancestors.unshift(a);
              }

-            for (var i in ancestors) {
+            for (var i = 0, len = ancestors.length; i < len; i++) {
                  var event = document.createEventObject();
                  event.trueName = name;
                  event.phase = "capture";
@@ -9869,4 +9869,4 @@



-
\ No newline at end of file
+

[Xsltforms-support] XSLTForms name conflict: Event

[Leigh L K. Jr <lei...@xe...>]

XSLTForms defines a number of top-level variables, some of which have 
generic names.

The Event object, in particular, conflicts with other libraries.

It would be best to put all of XSLTForms in a single top-level object 
named XSLTForms.
However, it may be OK for now to rename "var Event" to "var XSLTFormsEvent".

Otherwise, you can't use XSLTForms with external widget libraries.

Leigh.

Re: [Xsltforms-support] Load Time Performance improvement - It works!

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

This sounds like a very useful result.

Thank you for sharing.

- Dan

On Tue, Jan 11, 2011 at 7:53 AM, Santosh Chandak
<san...@gm...>wrote:

> A simple trick has helped our form to reduce load time from 30 seconds to 4
> seconds. If form is big, XSLTForms transform takes some time to create the
> HTML elements. If we create the output HTML beforehand, the time spent in
> transforming the xml to html can be saved. I used java saxon8 xslt
> transformer for our 104 K size form. Result is saved to a HTML page, which
> can be loaded directly.
>
> I hope this will help others as well!
>
>
>
> ------------------------------------------------------------------------------
> Gaining the trust of online customers is vital for the success of any
> company
> that requires sensitive data to be transmitted over the Web.   Learn how to
> best implement a security strategy that keeps consumers' information secure
> and instills the confidence they need to proceed with transactions.
> http://p.sf.net/sfu/oracle-sfdevnl
> _______________________________________________
> 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] Load Time Performance improvement - It works!

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

A simple trick has helped our form to reduce load time from 30 seconds to 4
seconds. If form is big, XSLTForms transform takes some time to create the
HTML elements. If we create the output HTML beforehand, the time spent in
transforming the xml to html can be saved. I used java saxon8 xslt
transformer for our 104 K size form. Result is saved to a HTML page, which
can be loaded directly.

I hope this will help others as well!