xsltforms-support Mailing List for XSLTForms (Page 52)
Brought to you by:
alain-couthures
Menu
▾
▴
xsltforms-support — XSLTForms support list
You can subscribe to this list here.
| 2009 |
Jan
|
Feb
|
Mar
|
Apr
(1) |
May
(6) |
Jun
(9) |
Jul
(16) |
Aug
(5) |
Sep
(43) |
Oct
(36) |
Nov
(58) |
Dec
(43) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2010 |
Jan
(79) |
Feb
(81) |
Mar
(107) |
Apr
(93) |
May
(85) |
Jun
(54) |
Jul
(64) |
Aug
(54) |
Sep
(45) |
Oct
(53) |
Nov
(34) |
Dec
(77) |
| 2011 |
Jan
(56) |
Feb
(53) |
Mar
(52) |
Apr
(66) |
May
(44) |
Jun
(16) |
Jul
(28) |
Aug
(5) |
Sep
(15) |
Oct
(21) |
Nov
(51) |
Dec
(46) |
| 2012 |
Jan
(16) |
Feb
(38) |
Mar
(47) |
Apr
(45) |
May
(41) |
Jun
(41) |
Jul
(72) |
Aug
(17) |
Sep
(10) |
Oct
(16) |
Nov
(29) |
Dec
(30) |
| 2013 |
Jan
(25) |
Feb
(13) |
Mar
(20) |
Apr
(25) |
May
(34) |
Jun
(8) |
Jul
(12) |
Aug
(9) |
Sep
(21) |
Oct
(19) |
Nov
(6) |
Dec
(2) |
| 2014 |
Jan
(14) |
Feb
(8) |
Mar
(7) |
Apr
(13) |
May
(33) |
Jun
(13) |
Jul
(6) |
Aug
(5) |
Sep
(5) |
Oct
(34) |
Nov
(7) |
Dec
|
| 2015 |
Jan
(1) |
Feb
(6) |
Mar
(17) |
Apr
(12) |
May
(10) |
Jun
(18) |
Jul
(31) |
Aug
(9) |
Sep
(3) |
Oct
(6) |
Nov
(19) |
Dec
(1) |
| 2016 |
Jan
(18) |
Feb
(4) |
Mar
(13) |
Apr
(19) |
May
|
Jun
(17) |
Jul
(7) |
Aug
|
Sep
(3) |
Oct
(6) |
Nov
(3) |
Dec
|
| 2017 |
Jan
(5) |
Feb
(17) |
Mar
(4) |
Apr
(8) |
May
(3) |
Jun
|
Jul
(8) |
Aug
(2) |
Sep
|
Oct
(5) |
Nov
(6) |
Dec
(4) |
| 2018 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(6) |
Nov
|
Dec
(1) |
| 2019 |
Jan
|
Feb
|
Mar
(4) |
Apr
(2) |
May
(4) |
Jun
|
Jul
|
Aug
(2) |
Sep
(7) |
Oct
|
Nov
|
Dec
|
| 2020 |
Jan
(13) |
Feb
(17) |
Mar
(8) |
Apr
(11) |
May
(15) |
Jun
(11) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(6) |
| 2021 |
Jan
(9) |
Feb
(26) |
Mar
(17) |
Apr
|
May
(7) |
Jun
(18) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(10) |
| 2022 |
Jan
|
Feb
(1) |
Mar
|
Apr
|
May
(3) |
Jun
|
Jul
|
Aug
(2) |
Sep
(3) |
Oct
(2) |
Nov
(10) |
Dec
(1) |
| 2023 |
Jan
(10) |
Feb
|
Mar
(7) |
Apr
(8) |
May
(3) |
Jun
|
Jul
|
Aug
|
Sep
(8) |
Oct
(11) |
Nov
(8) |
Dec
(5) |
| 2024 |
Jan
(7) |
Feb
(3) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2025 |
Jan
(4) |
Feb
(2) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Stephen C. <ste...@gm...> - 2012-01-06 03:25:08
|
Futher to my last email
this works better
XsltForms_repeat.prototype.setIndex = function(index) {
if (this.index !== index) {
this.index = index;
if (this.index <= this.nodes.length && this.nodes[index-1] ) {
XsltForms_globals.openAction();
this.element.node = this.nodes[index-1];
XsltForms_globals.addChange(this);
XsltForms_globals.addChange(document.getElementById(XsltForms_browser.getMeta(this.element.node.ownerDocument.documentElement,
"model")).xfElement);
XsltForms_globals.closeAction();
}
}
};
:)
|
|
From: Stephen C. <ste...@gm...> - 2012-01-05 23:03:36
|
Hi Alain,
Further to my email yesterday regarding issue with setindex failing to
work correctly.
I found that the problem is in the following routine.
XsltForms_repeat.prototype.setIndex = function(index) {
if (this.index !== index) {
var node = this.nodes[index - 1];
if (node) {
XsltForms_globals.openAction();
this.index = index;
this.element.node = node;
XsltForms_globals.addChange(this);
XsltForms_globals.addChange(document.getElementById(XsltForms_browser.getMeta(node.ownerDocument.documentElement,
"model")).xfElement);
XsltForms_globals.closeAction();
}
}
};
At the time this is called the nodes array has the old set of nodes
(without the new one just added via xf:insert) so it will never reset
if you are making it to the last node
Changing it to the following seems to fix the issue
XsltForms_repeat.prototype.setIndex = function(index) {
if (this.index !== index) {
this.index = index;
var node = this.nodes[index - 1];
if (node) {
XsltForms_globals.openAction();
//this.index = index;
this.element.node = node;
XsltForms_globals.addChange(this);
XsltForms_globals.addChange(document.getElementById(XsltForms_browser.getMeta(node.ownerDocument.documentElement,
"model")).xfElement);
XsltForms_globals.closeAction();
}
}
};
Not sure if you might need to add further checks e.g.
XsltForms_repeat.prototype.setIndex = function(index) {
if (this.index !== index) {
this.index = index;
if (this.index < this.nodes.length && this.nodes[index-1] ) {
XsltForms_globals.openAction();
this.element.node = this.nodes[index-1];
XsltForms_globals.addChange(this);
XsltForms_globals.addChange(document.getElementById(XsltForms_browser.getMeta(node.ownerDocument.documentElement,
"model")).xfElement);
XsltForms_globals.closeAction();
}
}
};
Regards
Steve Cameron
|
|
From: Stephen C. <ste...@gm...> - 2012-01-05 07:59:32
|
Hello All, I have been trying to resolve an issue that I thought I had fixed by using the latest build, but no luck. I am building a XML Schema designer and Xforms generator using XSLTforms. I want to add both elements and types to a schema list with the list appearing in a repeat. Sometimes adding just an element and sometimes both an element and a type, with all the elements appearing first, then followed by the all the types (it would be good if they could display in alphabetical order within these categories). On adding an element, I want to use xf:setindex to select the element just added (the last element in the list). The unusual behaviour is that setindex works when I add both an element and a type but doesn't when I add just the element. The different behaviour can be seen by commenting out the line in the code below that inserts the type (as marked below in capitals). Maybe I am doing something wrong but I seen no errors. <?xml version="1.0" encoding="UTF-8"?> <?xml-stylesheet href="build/xsltforms.xsl" type="text/xsl"?> <?xsltforms-options debug="yes"?> <html xmlns="http://www.w3.org/1999/xhtml" xmlns:xf="http://www.w3.org/2002/xforms" xmlns:ev="http://www.w3.org/2001/xml-events" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:s2x="http://www.sourceforge.net/schema2xforms" xmlns:sch="http://purl.oclc.org/dsdl/schematron"> <head> <title /> <xf:model id="model1"> <xf:instance id="xml_schema_elements"> <s2x:data> <xs:element name=""/> <xs:type name=""/> </s2x:data> </xf:instance> <xf:instance id="built_schema"> <xs:schema> <s2x:data /> </xs:schema> </xf:instance> <xf:instance id="temp"> <xs:data> <s2x:posn /> </xs:data> </xf:instance> </xf:model> <style type="text/css"> .xforms-repeat-item-selected { background-color:lightblue; } </style> </head> <body> <div> <xf:group ref="instance('xml_schema_elements')/xs:element"> <xf:input id="new_element_name" ref="@name" /> <xf:trigger> <xf:label>Add</xf:label> <xf:hint>Adds a new schema element</xf:hint> <xf:action ev:event="DOMActivate" if="string-length(@name) > 0 and not(instance('built_schema')/*/@name = current()/@name)"> <xf:setvalue ref="instance('temp')/s2x:posn" value="count(instance('built_schema')/xs:element)+1"/> <xf:setvalue ref="instance('xml_schema_elements')/xs:type/@name" value="current()/@name"/> <xf:insert nodeset="instance('built_schema')/*" origin="current()" at="instance('temp')/s2x:posn" position="before" /> <!-- COMMENT OUT THE FOLLOWING LINE --> <xf:insert nodeset="instance('built_schema')/*" origin="instance('xml_schema_elements')/xs:type"/> <xf:setvalue ref="current()/@name" value="" /> <xf:setvalue ref="instance('xml_schema_elements')/xs:type/@name" value=""/> <xf:setfocus control="new_element_name" /> <xf:setindex repeat="elements_and_types" index="instance('temp')/s2x:posn"/> </xf:action> <xf:action ev:event="DOMActivate" if="string-length(@name) > 0 and instance('built_schema')/*/@name = current()/@name"> <xf:message> An element with name <span style="font-weight:bold;"> <xf:output ref="@name" /> </span> already exists </xf:message> <xf:setfocus control="new_element_name" /> </xf:action> </xf:trigger> <xf:trigger> <xf:label>Set Index</xf:label> <xf:hint>Adds a new schema element</xf:hint> <xf:action ev:event="DOMActivate"> <xf:setindex repeat="elements_and_types" index="instance('temp')/s2x:posn"/> </xf:action> </xf:trigger> </xf:group> </div> <div> <xf:repeat nodeset="instance('built_schema')/*[not(self::s2x:data)]" id="elements_and_types"> <div> <xf:output value="if(name(.)='xs:element','e:','t:')" /><xf:output value="@name" /> </div> </xf:repeat> </div> </body> </html> Thanks for your assistance and all the best for 2012! |
|
From: Joe W. <jo...@gm...> - 2011-12-29 17:06:19
|
Hi Dan, Thanks for the great explanation! I'll try out the divs and spans-based approach. Joe Sent from my iPhone On Dec 29, 2011, at 7:53 AM, Dan McCreary <dan...@gm...> wrote: > Hi Joe, > > From what I know, repeats within tables are very tricky due to the way that tables are rendered within a browser. Browsers usually assume that they get an entire table from the server and they then try to calculate the correct layout after the </table> tag arrives. With XSLTForms we build the table interactively after all the data arrives in the model and this confuses most browsers. Since some browsers have different strategies for rendering tables so it is very hard to get table rendering right across all browsers. > > I have found the most fail-safe way to render tabular data using the <repeat> is to try to use a combination of divs, spans and a CSS file that will create fixed-with output for the cells. This can be done with Blueprint using "span" tags within your class attributes. I know that this is not nearly as easy as using the <table> tag but it is consistent across most browsers. I suspect that you may be able to try to use a combination of tables and fixed-with cell layout and get it to work on FF9 on the Mac but it may not work on all tables. > > Here is a very small example: > > http://en.wikibooks.org/wiki/XForms/Highlight_Selected_Row > > This example uses a combination of the following: > display: inline; > position: absolute; > margin-left: 150px; > > One newer CSS structure that I have also been using is the inline-block property. This allows you to set the "width" on any cell. Something that does not work with inline layout. The problem with this is that older versions of IE did not support it but since you are on FF this may work out fine. > > Let me know what works and I can update the XForms wikibook. > > - Dan > > On Wed, Dec 28, 2011 at 11:30 PM, Joe Wicentowski <jo...@gm...> wrote: > Hi all, > > I'm building a basic gradebook app for a professor I happen to know (my wife) using XSLTForms, and while it's been working great for most of my forms, I'm encountering difficulties when using <xf:repeat> inside of tables. I would appreciate any suggestions or troubleshooting hints folks here might have. I'm using XSLTForms (trunk rev. 522 from http://xsltforms.svn.sourceforge.net/viewvc/xsltforms/trunk/build/) with FF9 on Mac OS X. Here's the relevant portion of my form: > > <div xmlns="http://www.w3.org/1999/xhtml"> > <table> > <thead> > <tr> > <th>Student</th> > <!-- one heading for the name of each assessment (i.e., tests and assignments) --> > <xf:repeat nodeset="instance('course')/assessments/assessment"> > <th><xf:output ref="name"/></th> > </xf:repeat> > <th>Final Letter Grade</th> > </tr> > </thead> > <tbody> > <!-- one row for each student record: name, grades for each assessment, final grade --> > <xf:repeat nodeset="instance('students')/student" id="repeat-students"> > <tr> > <td><xf:output value="concat(surname, ', ', forename)"/></td> > <xf:repeat nodeset="instance('course')/assessments/assessment" id="repeat-assessments"> > <td><xf:input ref="instance('students')/student[index('repeat-students')]/course-record/assessments/assessment[index('repeat-assessments')]/grade"/></td> > </xf:repeat> > <td><xf:input ref="course-record/final-grade"/></td> > </tr> > </xf:repeat> > </tbody> > </table> > </div> > > Here the "courses" instance contains info about each course, including assessments (i.e., tests and assignments), and the "students" instance contains info about each student's grades -- for each assessment and for the final grade. > > The result in FF9 is quite odd. Instead of a structure I would expect like: > > Student Test 1 Test 2 Final Letter Grade > ----------- --------- ---------- --------------------------- > Joe 80 81 B- > Sue 90 91 A- > ... > > I get something like: > > Test 1 Test 2 Final Letter Grade > --------- --------- -------------------------- > Joe > A- Sue Bill Harry Melinda ... > > Such an odd rendering suggests to me that either (1) there is a problem with my coding of the form (2) there is an XSLTForms issue or (3) both. I'm not sure which it is. When I search the list archives I see some references to problems XSLTForms has with tables and repeats, and Alain's suggestion to use the trunk version of XSLTForms and to use thead/tbody. I'm using trunk and using thead/tbody, so we can rule those factors out. I've also tried using the alternate "attributes" syntax for repeats (detailed at http://www.w3.org/TR/xforms/#ui.repeat.via.attrs), and the rendering of the form is even more unrecognizable. So I'm not sure how best to continue troubleshooting the issue. Could anyone suggest some ideas? I'm happy to provide more info. > > Thanks, > Joe > ------------------------------------------------------------------------------ > Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex > infrastructure or vast IT resources to deliver seamless, secure access to > virtual desktops. With this all-in-one solution, easily deploy virtual > desktops for less than the cost of PCs and save 60% on VDI infrastructure > costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox > _______________________________________________ > 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 |
|
From: Dan M. <dan...@gm...> - 2011-12-29 13:54:05
|
Hi Joe, >From what I know, repeats within tables are very tricky due to the way that tables are rendered within a browser. Browsers usually assume that they get an entire table from the server and they then try to calculate the correct layout after the </table> tag arrives. With XSLTForms we build the table interactively after all the data arrives in the model and this confuses most browsers. Since some browsers have different strategies for rendering tables so it is very hard to get table rendering right across all browsers. I have found the most fail-safe way to render tabular data using the <repeat> is to try to use a combination of divs, spans and a CSS file that will create fixed-with output for the cells. This can be done with Blueprint using "span" tags within your class attributes. I know that this is not nearly as easy as using the <table> tag but it is consistent across most browsers. I suspect that you may be able to try to use a combination of tables and fixed-with cell layout and get it to work on FF9 on the Mac but it may not work on all tables. Here is a very small example: http://en.wikibooks.org/wiki/XForms/Highlight_Selected_Row This example uses a combination of the following: display: inline; position: absolute; margin-left: 150px; One newer CSS structure that I have also been using is the inline-block property. This allows you to set the "width" on any cell. Something that does not work with inline layout. The problem with this is that older versions of IE did not support it but since you are on FF this may work out fine. Let me know what works and I can update the XForms wikibook. - Dan On Wed, Dec 28, 2011 at 11:30 PM, Joe Wicentowski <jo...@gm...> wrote: > Hi all, > > I'm building a basic gradebook app for a professor I happen to know (my > wife) using XSLTForms, and while it's been working great for most of my > forms, I'm encountering difficulties when using <xf:repeat> inside of > tables. I would appreciate any suggestions or troubleshooting hints folks > here might have. I'm using XSLTForms (trunk rev. 522 from > http://xsltforms.svn.sourceforge.net/viewvc/xsltforms/trunk/build/) with > FF9 on Mac OS X. Here's the relevant portion of my form: > > <div xmlns="http://www.w3.org/1999/xhtml"> > <table> > <thead> > <tr> > <th>Student</th> > *<!-- one heading for the name of each assessment > (i.e., tests and assignments) -->* > <xf:repeat > nodeset="instance('course')/assessments/assessment"> > <th><xf:output ref="name"/></th> > </xf:repeat> > <th>Final Letter Grade</th> > </tr> > </thead> > <tbody> > *<!-- one row for each student record: name, grades for > each assessment, final grade -->* > <xf:repeat nodeset="instance('students')/student" > id="repeat-students"> > <tr> > <td><xf:output value="concat(surname, ', ', > forename)"/></td> > <xf:repeat > nodeset="instance('course')/assessments/assessment" id="repeat-assessments"> > <td><xf:input > ref="instance('students')/student[index('repeat-students')]/course-record/assessments/assessment[index('repeat-assessments')]/grade"/></td> > </xf:repeat> > <td><xf:input ref="course-record/final-grade"/></td> > </tr> > </xf:repeat> > </tbody> > </table> > </div> > > Here the "courses" instance contains info about each course, including > assessments (i.e., tests and assignments), and the "students" instance > contains info about each student's grades -- for each assessment and for > the final grade. > > The result in FF9 is quite odd. Instead of a structure I would expect > like: > > Student Test 1 Test 2 Final Letter Grade > ----------- --------- ---------- --------------------------- > Joe 80 81 B- > Sue 90 91 A- > ... > > I get something like: > > Test 1 Test 2 Final Letter Grade > --------- --------- -------------------------- > Joe > A- Sue Bill Harry Melinda ... > > Such an odd rendering suggests to me that either (1) there is a problem > with my coding of the form (2) there is an XSLTForms issue or (3) both. > I'm not sure which it is. When I search the list archives I see some > references to problems XSLTForms has with tables and repeats, and Alain's > suggestion to use the trunk version of XSLTForms and to use thead/tbody. > I'm using trunk and using thead/tbody, so we can rule those factors out. > I've also tried using the alternate "attributes" syntax for repeats > (detailed at http://www.w3.org/TR/xforms/#ui.repeat.via.attrs), and the > rendering of the form is even more unrecognizable. So I'm not sure how > best to continue troubleshooting the issue. Could anyone suggest some > ideas? I'm happy to provide more info. > > Thanks, > Joe > > ------------------------------------------------------------------------------ > Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex > infrastructure or vast IT resources to deliver seamless, secure access to > virtual desktops. With this all-in-one solution, easily deploy virtual > desktops for less than the cost of PCs and save 60% on VDI infrastructure > costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox > _______________________________________________ > 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 |
|
From: Joe W. <jo...@gm...> - 2011-12-29 05:30:54
|
Hi all, I'm building a basic gradebook app for a professor I happen to know (my wife) using XSLTForms, and while it's been working great for most of my forms, I'm encountering difficulties when using <xf:repeat> inside of tables. I would appreciate any suggestions or troubleshooting hints folks here might have. I'm using XSLTForms (trunk rev. 522 from http://xsltforms.svn.sourceforge.net/viewvc/xsltforms/trunk/build/) with FF9 on Mac OS X. Here's the relevant portion of my form: <div xmlns="http://www.w3.org/1999/xhtml"> <table> <thead> <tr> <th>Student</th> *<!-- one heading for the name of each assessment (i.e., tests and assignments) -->* <xf:repeat nodeset="instance('course')/assessments/assessment"> <th><xf:output ref="name"/></th> </xf:repeat> <th>Final Letter Grade</th> </tr> </thead> <tbody> *<!-- one row for each student record: name, grades for each assessment, final grade -->* <xf:repeat nodeset="instance('students')/student" id="repeat-students"> <tr> <td><xf:output value="concat(surname, ', ', forename)"/></td> <xf:repeat nodeset="instance('course')/assessments/assessment" id="repeat-assessments"> <td><xf:input ref="instance('students')/student[index('repeat-students')]/course-record/assessments/assessment[index('repeat-assessments')]/grade"/></td> </xf:repeat> <td><xf:input ref="course-record/final-grade"/></td> </tr> </xf:repeat> </tbody> </table> </div> Here the "courses" instance contains info about each course, including assessments (i.e., tests and assignments), and the "students" instance contains info about each student's grades -- for each assessment and for the final grade. The result in FF9 is quite odd. Instead of a structure I would expect like: Student Test 1 Test 2 Final Letter Grade ----------- --------- ---------- --------------------------- Joe 80 81 B- Sue 90 91 A- ... I get something like: Test 1 Test 2 Final Letter Grade --------- --------- -------------------------- Joe A- Sue Bill Harry Melinda ... Such an odd rendering suggests to me that either (1) there is a problem with my coding of the form (2) there is an XSLTForms issue or (3) both. I'm not sure which it is. When I search the list archives I see some references to problems XSLTForms has with tables and repeats, and Alain's suggestion to use the trunk version of XSLTForms and to use thead/tbody. I'm using trunk and using thead/tbody, so we can rule those factors out. I've also tried using the alternate "attributes" syntax for repeats (detailed at http://www.w3.org/TR/xforms/#ui.repeat.via.attrs), and the rendering of the form is even more unrecognizable. So I'm not sure how best to continue troubleshooting the issue. Could anyone suggest some ideas? I'm happy to provide more info. Thanks, Joe |
|
From: Alain C. <ala...@ag...> - 2011-12-26 13:23:35
|
Hello Dominic,
The "standard" way to escape ' and " characters in XML is to use entities.
Please try again with:
<xf:load>
<xf:resource value="concat('javascript:myfunc("',@att1,'","',@att2,'","',@att3,'")')"/>
</xf:load>
Thank you for your feedbacks!
-Alain
Le 24/12/2011 19:17, dom a écrit :
> Would very much appreciate any help with the following:
>
> Given a javascript function myfunc('xxx','yyy','zzz')
>
> and an xforms instance element containing attributes att1="xxx"
> att2="yyy" att3="zzz"
>
> how do I call this function from the resource child element of a load
> element ie:
>
> <xf:load>
> <xf:resource
> value="concat('javascript:myfunc(''',@att1,''',''',@att2,''',''',@att3,''')')"/>
> </xf:load>
>
> which produces the correct result in Saxon but in XSLTForms returns an
> 'operator unknown' error
> at the position of the first escaped single quote.
>
> Thanks
> Dominic Martin
>
>
>
> ------------------------------------------------------------------------------
> Write once. Port to many.
> Get the SDK and tools to simplify cross-platform app development. Create
> new or port existing apps to sell to consumers worldwide. Explore the
> Intel AppUpSM program developer opportunity. appdeveloper.intel.com/join
> http://p.sf.net/sfu/intel-appdev
> _______________________________________________
> Xsltforms-support mailing list
> Xsl...@li...
> https://lists.sourceforge.net/lists/listinfo/xsltforms-support
>
|
|
From: dom <do...@th...> - 2011-12-24 18:53:30
|
Would very much appreciate any help with the following:
Given a javascript function myfunc('xxx','yyy','zzz')
and an xforms instance element containing attributes att1="xxx"
att2="yyy" att3="zzz"
how do I call this function from the resource child element of a load
element ie:
<xf:load>
<xf:resource
value="concat('javascript:myfunc(''',@att1,''',''',@att2,''',''',@att3,''')')"/>
</xf:load>
which produces the correct result in Saxon but in XSLTForms returns an
'operator unknown' error
at the position of the first escaped single quote.
Thanks
Dominic Martin
|
|
From: Alain C. <ala...@ag...> - 2011-12-23 07:42:56
|
Hi Steve, Because Internet Explorer doesn't allow display="none" for an option element within a select HTML element, it is not currently possible to memorize an empty itemset to be populated after. To change this, it will be necessary to associate a JSON structure to xf:select to work with... I suggest you to use a dedicated instance to store the itemset or to add the "No translation" item in your current instance with an extra attribute to filter it when necessary. Thank you for your feedbacks! -Alain Le 20:59, st...@sa... a écrit : > Hi, Alain, > > Here is a problem I am observing in r521 which looks as though > the nodeset binding on an itemset which depends on the value of > a checkbox is not being updated properly. > > To reproduce: > > http://oracc.museum.upenn.edu/itemset-update.xml > > Click on 'Erridupizir 1' > > Click on select1 on lower right of navigation area which > reads 'English'--you will see an entry labeled > 'No translation' > > Leave the translation on English > > Click on the checkbox labeled 'only'; the display switches > to show only the translation > > Click on the select1 labeled 'English'--the 'No translation' > entry has disappeared, correctly > > Click on the 'only' box to toggle it back to 'false'; the > Sumerian reappears in the text display area > > Click on the select1 labeled 'English' and you see the > problem: the 'No translation' entry in the select1 has > not reappeared > > You can read the code at a glance, I am sure, but the way > it is supposed to work is that 'No translation' is an > itemset which is supposed to display when the checkbox > transonly is false and hide when transonly is true. > > This is with FF 8.0.1 on Mac Lion 10.7.2 > > Steve > > |
|
From: srividhya <n.s...@ni...> - 2011-12-22 04:58:54
|
Hi Stephen Cameron, thanks for the reply.... yes we really interested and know further details about the solution. Please give me the related documents or procedures to implement in both client and server side with XSLTForms. If you have any sample code please let me know .... awaiting for your reply. thanks and regards, N. Srividhya NIC, OTC, Govt. of. India. Chennai. On 12/21/11, Stephen Cameron <ste...@gm...> wrote: > Hello Srividhya, > > A couple of us are presently working on an open-source project that I > hope will solve the issue that you are interested in. > > This is an XForm for designing an XML Schema and from which one or > more XForms are then generated. > > The XML Schema can have Schematron rules embedded inside it that, in > the XForm generation process, are converted to bind constraints. > > My idea is that the same XML Schema (& Schematron) file is also used > on the server side to validate submissions. > > Although the validation is done twice I see this as being a RESTful solution. > > The Schema Designer and XForms Generator 'prototype' is almost ready > for public release on sourceforge, however if you are keen to pursue > this now contact me directly. > > Regards > Steve Cameron > > On Tue, Dec 20, 2011 at 11:03 PM, srividhya <n.s...@ni...> wrote: > > > > Hi XSLTForms Users !!! > > > > We have a scenario to validate XForms with XSLTForms in offline mode as well > > as the same validation with online mode ...Pls suggest a possible solution > > > > Like i have a sample form with a date comparison field .. So, i have written > > the rule in my client side XForms with Bind option. while i submit the date > > to the server i need to reuse the same bind rule in server side ....We dont > > know how to do the same in Server side with Same client side rule written in > > XForms bind section . > > > > > > > > with thanks and regards, > > N. srividhya > > NIC-OTC, > > chennai. > > > > -- With thanks and Regards, N.Srividhya(RS-I) O.T.C, N.I.C, Chennai. |
|
From: <st...@sa...> - 2011-12-21 04:26:45
|
Thanks, Alain--little trick by little trick the forms become more and more compatible across platforms! Steve Quoting Alain Couthures <ala...@ag...>: > Hi Steve, > > * <br/> being doubled occurs in some browsers when they apply the XSLT > stylesheet themselves. I suggest you to use 2 DIV elements instead > as a workaround. > * Opera latest version is replacing @ev:event with @ev:actiontype in > the XForms document (unbelievable!) so I added @ev:actiontype > support! (This will be in the next commit!) > * IE9 doesn't like empty SCRIPT elements (when @src is present, > they're empty in XHTML...). You can change that accordingly in each > of your pages but it's a frequent issue so I force now a dummy value > (/* */) for them. > > Thank you for your feedbacks! > > -Alain > > > Le 15/12/2011 15:23, st...@sa... a écrit : >> Hi, Alain, >> >> I have refactored my search form to use bind instead of group and things >> are a bit better--with FF 8.0.1 the behaviour is as expected. >> >> On Safari/Chrome, a spurious<br/> is inserted (there is supposed to be >> one in one of the TDs but Safari/Chrome put two). To reproduce: >> >> http://oracc.museum.upenn.edu/oas-nogroup.xml >> >> Click on the '+' button beside the hint diamond: the two rows of controls >> should be separated by one<br/> but there are two there. >> >> On Opera, clicking on the '+' button changes the border indicating the >> press has been received, but then nothing further happens. >> >> On IE 9 I get an XSLTForms Exception Incorrect Javascript code generation: >> ReferenceError xsltforms_initImpl is undefined. >> >> Thanks for any insight, >> >> Steve >> >> >> >> >> ------------------------------------------------------------------------------ >> 10 Tips for Better Server Consolidation >> Server virtualization is being driven by many needs. >> But none more important than the need to reduce IT complexity >> while improving strategic productivity. Learn More! >> http://www.accelacomm.com/jaw/sdnl/114/51507609/ >> _______________________________________________ >> Xsltforms-support mailing list >> Xsl...@li... >> https://lists.sourceforge.net/lists/listinfo/xsltforms-support >> > > > |
|
From: Stephen C. <ste...@gm...> - 2011-12-20 22:46:06
|
Hello Srividhya, A couple of us are presently working on an open-source project that I hope will solve the issue that you are interested in. This is an XForm for designing an XML Schema and from which one or more XForms are then generated. The XML Schema can have Schematron rules embedded inside it that, in the XForm generation process, are converted to bind constraints. My idea is that the same XML Schema (& Schematron) file is also used on the server side to validate submissions. Although the validation is done twice I see this as being a RESTful solution. The Schema Designer and XForms Generator 'prototype' is almost ready for public release on sourceforge, however if you are keen to pursue this now contact me directly. Regards Steve Cameron On Tue, Dec 20, 2011 at 11:03 PM, srividhya <n.s...@ni...> wrote: > > Hi XSLTForms Users !!! > > We have a scenario to validate XForms with XSLTForms in offline mode as well > as the same validation with online mode ...Pls suggest a possible solution > > Like i have a sample form with a date comparison field .. So, i have written > the rule in my client side XForms with Bind option. while i submit the date > to the server i need to reuse the same bind rule in server side ....We dont > know how to do the same in Server side with Same client side rule written in > XForms bind section . > > > > with thanks and regards, > N. srividhya > NIC-OTC, > chennai. > |
|
From: Dan M. <dan...@gm...> - 2011-12-20 18:26:16
|
Hello Srividhya, Yes, this is easy to do without writing a single line of JavaScript! I call this "server-side" field validation. Here is an example: http://en.wikibooks.org/wiki/XForms/Server-Side_Field_Validation Ann Kelly wrote most of this article, so the thanks should got to her. Please let me know if this works for you and if the materials are clear. - Dan On Mon, Dec 19, 2011 at 11:43 PM, srividhya <n.s...@ni...> wrote: > Alain, > Is it possible to do the validation through some libraries or API's > for form data or xml data at server side without using XMLSchema or XForms > bind controls.. > > N. Srividhya > OTC, N. I. C, > Chennai > > > On 12/17/11, xsl...@li... wrote: > > Send Xsltforms-support mailing list submissions to > xsl...@li... > > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.sourceforge.net/lists/listinfo/xsltforms-support > or, via email, send a message with subject or body 'help' to > xsl...@li... > > You can reach the person managing the list at > xsl...@li... > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of Xsltforms-support digest..." > > > Today's Topics: > > 1. Re: getting your feet wet with the profiler (was Re: > optimization question) (Jakob Fix) > 2. xforms:repeat / tr / br (st...@sa...) > 3. XSLTForms with ASP.NET (William David Velasquez) > 4. Re: XSLTForms with ASP.NET (Dan McCreary) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Wed, 14 Dec 2011 22:24:03 +0100 > From: Jakob Fix <jak...@gm...> > Subject: Re: [Xsltforms-support] getting your feet wet with the > profiler (was Re: optimization question) > To: Kurt Cagle <kur...@gm...> > Cc: xsl...@li... > Message-ID: > <CAC...@ma...> > Content-Type: text/plain; charset=ISO-8859-1 > > Hi Kurt, this is the exact same behaviour we have observed, and Alain > suggested using the profiler to find out where the bottlenecks might > be. Our forms are also served by MarkLogic, although that's a > coincidence rather than the reason, of course. > > Jakob. > > > > On Wed, Dec 14, 2011 at 22:16, Kurt Cagle <kur...@gm...> wrote: > > It may be something in the form rendering - the download of the XSLT file > > takes very little time, but I'm looking at 15-20s before the form itself > is > > rendered in Chrome - compared to 2-3 for the October release which I had > > been using. Firefox is faster, but not appreciably. This is being > delivered > > out of MarkLogic. > > > > > > Kurt Cagle > > Invited Expert, XForms Working Group, W3C > > Managing Editor, XMLToday.org > > kur...@gm... > > 443-837-8725 > > > > > > > > > > On Wed, Dec 14, 2011 at 3:11 PM, Alain Couthures > > <ala...@ag...> wrote: > >> > >> Kurt, > >> > >> I'm not sure I understand correctly. Is it that, when clicking on the > >> Profiler button, you have to wait a very long time especially on Chrome > with > >> which once you got an alert about a Javascript execution overload?? > >> > >> Thanks! > >> > >> -Alain > >> > >> Le 13/12/2011 17:30, Kurt Cagle a ?crit?: > >> > >> Alain, > >> > >> I too like the profiler, though I'm a bit distressed with the overall > >> download time for the package - on Firefox it's long but acceptable, > but on > >> Chrome it seems to take forever to load (it times out at least once). > >> > >> Kurt Cagle > >> Invited Expert, XForms Working Group, W3C > >> Managing Editor, XMLToday.org > >> kur...@gm... > >> 443-837-8725 > >> > >> > >> > >> > >> On Fri, Dec 9, 2011 at 4:09 PM, Alain Couthures > >> <ala...@ag...> wrote: > >>> > >>> Wow! What an impressive Christmas gift for XML fans! > >>> > >>> You're absolutely right about the Profiler I added to XSLTForms: it's a > >>> wonderful tool to locate time-costing XPath expressions and refreshes. > >>> > >>> In the latest builds, the Profiler is even a form: this means that it > >>> can be customized by authors themselves. The profiling data is > collected > >>> as an XML document and a specific processing-instruction tells > XSLTForms > >>> which form to associate with. > >>> > >>> I plan to add more information in the Profiler instance (instances > >>> copies, the calling form source, ...): the Profiler will progressively > >>> become a real XForms Debugger written in XForms. > >>> > >>> About your form performance, I already suspected that counting > preceding > >>> siblings would cost a lot of time: Javascript doesn't like loops > >>> (XSLTForms has to have its own XPath machine written in Javascript... I > >>> proposed a paper for XML Prague 2012 about how to write an XQuery > >>> compiler into Javascript instructions). I recently added support for > the > >>> id() function and it's even much better for performance. > >>> > >>> Defining a subform is now another possibility to simplify a form. This > >>> is not yet documented but I already love it much. Don't hesitate to ask > >>> me about subforms if you're interested in. > >>> > >>> If you want to load another form in a new browser tab from an instance > >>> without server exchanges, defining an extra parameter for the load > >>> action should be simple with the processing-instruction capability I > >>> already use for the Profiler (this processing-instruction mechanism is > >>> very promising indeed, I'm currently building a small XRAP > >>> (XForms-REST-Apache-PHP) application with minimal generic PHP scripts, > >>> XML files and folders on server). > >>> > >>> XML allows us to consider programs as data. We might not be numerous to > >>> envision this (but the community is strong) and I have to confess that > >>> I'm still marveled by this. > >>> > >>> Thank you very much for your feedbacks! > >>> > >>> -Alain > >>> > >>> Le 09/12/2011 02:41, C. M. Sperberg-McQueen a ?crit : > >>> > Just a short report, for the record, of my experience with the > profiler > >>> > now built into XSLTForms. > >>> > > >>> > Short version: ?the profiler is very helpful; in this case three > >>> > relatively > >>> > simple changes produced a five-fold speedup in the form. > >>> > > >>> > Long version: > >>> > > >>> > Looking at the profile information for the form I was worrying about, > >>> > which had gotten too slow when the document it was operating on got > >>> > bigger, I found that the most expensive XPath expressions were those > >>> > used for numbering the cells of the stack and for numbering the > >>> > instructions in the code area. ?I hard-coded appropriate numbers into > >>> > attributes in the machine description, and I added a set of actions > for > >>> > adding a numbering attribute to the instructions in a program, after > >>> > loading it. I then replaced each XPath expression of the form > >>> > count(preceding-sibling::cell) +1 or count(preceding-sibling::i) with > >>> > a reference to @n. ?I also removed the support for editing the > program > >>> > code; I'll move it to a separate form which communicates with the > >>> > main form by bouncing the XML representation of the document off > >>> > of a routine on the server. > >>> > > >>> > The first two changes (prenumbering the stack cells and autonumbering > >>> > the instructions in the program) reduced the XForms Cumulative > Refresh > >>> > Time after loading a program and stepping through 50 cycles of > machine > >>> > time (i.e. clicking Step 50 times) from 94.6 seconds to 42.3 seconds, > >>> > making the program about twice as fast. > >>> > > >>> > The third change (removing the editing functionality to a separate > >>> > form) > >>> > took it down to 17.7 seconds, another twofold speedup, for a > five-fold > >>> > speedup overall. > >>> > > >>> > Those who are curious can compare the timings and the subjective > >>> > experience of the form by looking at the old and new versions of the > >>> > form at > >>> > > >>> > http://blackmesatech.com/2011/12/pl0/v01.xhtml (old) > >>> > http://blackmesatech.com/2011/12/pl0/index.xhtml (new) > >>> > > >>> > (Hmm. ?I notice that the XSLTforms I'm using on that server is > >>> > an old version that doesn't yet have the profiler. ?I'll have to > update > >>> > soon.) > >>> > > >>> > >>> > >>> > >>> > ------------------------------------------------------------------------------ > >>> Cloud Services Checklist: Pricing and Packaging Optimization > >>> This white paper is intended to serve as a reference, checklist and > point > >>> of > >>> discussion for anyone considering optimizing the pricing and packaging > >>> model > >>> of a cloud services business. Read Now! > >>> http://www.accelacomm.com/jaw/sfnl/114/51491232/ > >>> _______________________________________________ > >>> Xsltforms-support mailing list > >>> Xsl...@li... > >>> https://lists.sourceforge.net/lists/listinfo/xsltforms-support > >> > >> > >> > > > > > > > ------------------------------------------------------------------------------ > > Cloud Computing - Latest Buzzword or a Glimpse of the Future? > > This paper surveys cloud computing today: What are the benefits? > > Why are businesses embracing it? What are its payoffs and pitfalls? > > http://www.accelacomm.com/jaw/sdnl/114/51425149/ > > _______________________________________________ > > Xsltforms-support mailing list > > Xsl...@li... > > https://lists.sourceforge.net/lists/listinfo/xsltforms-support > > > > > > ------------------------------ > > Message: 2 > Date: Thu, 15 Dec 2011 09:23:21 -0500 > From: st...@sa... > Subject: [Xsltforms-support] xforms:repeat / tr / br > To: xsl...@li... > Message-ID: <201...@we...> > Content-Type: text/plain; charset=ISO-8859-1; DelSp="Yes"; > format="flowed" > > Hi, Alain, > > I have refactored my search form to use bind instead of group and things > are a bit better--with FF 8.0.1 the behaviour is as expected. > > On Safari/Chrome, a spurious <br/> is inserted (there is supposed to be > one in one of the TDs but Safari/Chrome put two). To reproduce: > > http://oracc.museum.upenn.edu/oas-nogroup.xml > > Click on the '+' button beside the hint diamond: the two rows of controls > should be separated by one <br/> but there are two there. > > On Opera, clicking on the '+' button changes the border indicating the > press has been received, but then nothing further happens. > > On IE 9 I get an XSLTForms Exception Incorrect Javascript code generation: > ReferenceError xsltforms_initImpl is undefined. > > Thanks for any insight, > > Steve > > > > > > > ------------------------------ > > Message: 3 > Date: Fri, 16 Dec 2011 16:11:14 -0500 > From: William David Velasquez <wi...@bi...> > Subject: [Xsltforms-support] XSLTForms with ASP.NET > To: <xsl...@li...> > Message-ID: <c11...@bi...> > Content-Type: text/plain; charset=UTF-8; format=flowed > > Hi XForms fans! > > I just saved tons of work using XForms instead of WebForms in a .NET > project I?m currently working. > > It's pretty easy to include an XForms in a ASP.NET page using XSLTForms > and the asp:Xml Control for a server side transform. This line does the > trick: > > <asp:Xml ID="Xml1" runat="server" DocumentSource="~/myform.xforms" > TransformSource="~/xsltforms/xsltforms.xsl" EnableViewState="False" > ></asp:Xml> > > And to process the submission with DOM, two lines do the work: > > <%@ Page Language="C#" %> > <% > System.Xml.XmlDocument doc = new System.Xml.XmlDocument(); > doc.Load(Request.InputStream); > > // process your xml here.... > > %> > > There is just two things to keep in mind: > > 1. You need the latest version of XSLTForms from the repository (I > tested with rev 521). Previous versions don?t work with .NET > transformation engine. > > 2. ASP.NET WebForms wraps all the controls in the page with <form > >...</form> so when the Xml Control renders the xhtml for the XForm, > clicking in the xf:triggers post the form submission (an undesirable > behavior) because they are rendered as <button> with the default > type=submit. > > There are to workarounds: > 1. Move the <asp:Xml> outside the <form runat="server"> tag in the aspx > page, > 2. When that isn't possible (for example, when you use MasterPages), > make a little modification in xsltforms.xsl to add the atributte > type="button" when triggers are rendered. This is done in this template > (line 1141 in rev 521): > > <xsl:template match="xforms:trigger|xforms:submit" ... > > Below is the generation of the <button> tag (line 1162 in rev 521): > > <button> > <xsl:copy-of select="$innerbody"/> > </button> > > You can add the attribute this way: > > <button> > <xsl:attribute name="type">button</xsl:attribute> > <xsl:copy-of select="$innerbody"/> > </button> > > I know monsieur Alain kindly will include this change in a future > release ;-) > > I'm getting mixed reaactions from my co-workers (most of them are MS > fans), so I asked them to write a form using the normal aspnet way to > calculate an invoice, allowing users to add details lines, sum totals, > taxes, etc. They had to write more than 50 tricky lines of code, with > events handlers, javascript and a lot of Googling. Then I showed it with > XForms: five xf:bind and two xf:trigger for custom logic > > No need to say they are starting to get convinced. > > Merry Christmas, > > > William Velasquez > > > > ------------------------------ > > Message: 4 > Date: Fri, 16 Dec 2011 22:01:28 -0600 > From: Dan McCreary <dan...@gm...> > Subject: Re: [Xsltforms-support] XSLTForms with ASP.NET > To: William David Velasquez <wi...@bi...> > Cc: xsl...@li... > Message-ID: > <CAO...@ma...> > Content-Type: text/plain; charset="iso-8859-1" > > William, > > Thank you for sharing this story. It is always good to hear of > knowledgeable people showing the rest of the world "The Declarative Way". > I hope your team shares their results with others. > > - Dan > > On Fri, Dec 16, 2011 at 3:11 PM, William David Velasquez < > wi...@bi...> wrote: > > > Hi XForms fans! > > > > I just saved tons of work using XForms instead of WebForms in a .NET > > project I?m currently working. > > > > It's pretty easy to include an XForms in a ASP.NET page using XSLTForms > > and the asp:Xml Control for a server side transform. This line does the > > trick: > > > > <asp:Xml ID="Xml1" runat="server" DocumentSource="~/myform.xforms" > > TransformSource="~/xsltforms/xsltforms.xsl" EnableViewState="False" > > ></asp:Xml> > > > > And to process the submission with DOM, two lines do the work: > > > > <%@ Page Language="C#" %> > > <% > > System.Xml.XmlDocument doc = new System.Xml.XmlDocument(); > > doc.Load(Request.InputStream); > > > > // process your xml here.... > > > > %> > > > > There is just two things to keep in mind: > > > > 1. You need the latest version of XSLTForms from the repository (I > > tested with rev 521). Previous versions don?t work with .NET > > transformation engine. > > > > 2. ASP.NET WebForms wraps all the controls in the page with <form > > >...</form> so when the Xml Control renders the xhtml for the XForm, > > clicking in the xf:triggers post the form submission (an undesirable > > behavior) because they are rendered as <button> with the default > > type=submit. > > > > There are to workarounds: > > 1. Move the <asp:Xml> outside the <form runat="server"> tag in the aspx > > page, > > 2. When that isn't possible (for example, when you use MasterPages), > > make a little modification in xsltforms.xsl to add the atributte > > type="button" when triggers are rendered. This is done in this template > > (line 1141 in rev 521): > > > > <xsl:template match="xforms:trigger|xforms:submit" ... > > > > Below is the generation of the <button> tag (line 1162 in rev 521): > > > > <button> > > <xsl:copy-of select="$innerbody"/> > > </button> > > > > You can add the attribute this way: > > > > <button> > > <xsl:attribute name="type">button</xsl:attribute> > > <xsl:copy-of select="$innerbody"/> > > </button> > > > > I know monsieur Alain kindly will include this change in a future > > release ;-) > > > > I'm getting mixed reaactions from my co-workers (most of them are MS > > fans), so I asked them to write a form using the normal aspnet way to > > calculate an invoice, allowing users to add details lines, sum totals, > > taxes, etc. They had to write more than 50 tricky lines of code, with > > events handlers, javascript and a lot of Googling. Then I showed it with > > XForms: five xf:bind and two xf:trigger for custom logic > > > > No need to say they are starting to get convinced. > > > > Merry Christmas, > > > > > > William Velasquez > > > > > > > ------------------------------------------------------------------------------ > > Learn Windows Azure Live! Tuesday, Dec 13, 2011 > > Microsoft is holding a special Learn Windows Azure training event for > > developers. It will provide a great way to learn Windows Azure and what > it > > provides. You can attend the event by watching it streamed LIVE online. > > Learn more at http://p.sf.net/sfu/ms-windowsazure > > _______________________________________________ > > 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 > -------------- next part -------------- > An HTML attachment was scrubbed... > > ------------------------------ > > > ------------------------------------------------------------------------------ > Learn Windows Azure Live! Tuesday, Dec 13, 2011 > Microsoft is holding a special Learn Windows Azure training event for > developers. It will provide a great way to learn Windows Azure and what it > provides. You can attend the event by watching it streamed LIVE online. > Learn more at http://p.sf.net/sfu/ms-windowsazure > > ------------------------------ > > _______________________________________________ > Xsltforms-support mailing list > Xsl...@li... > https://lists.sourceforge.net/lists/listinfo/xsltforms-support > > > End of Xsltforms-support Digest, Vol 31, Issue 8 > ************************************************ > > -- > With thanks and Regards, > N.Srividhya(RS-I) > O.T.C, N.I.C, > Chennai. > > ------------------------------------------------------------------------------ > Write once. Port to many. > Get the SDK and tools to simplify cross-platform app development. Create > new or port existing apps to sell to consumers worldwide. Explore the > Intel AppUpSM program developer opportunity. appdeveloper.intel.com/join > http://p.sf.net/sfu/intel-appdev > _______________________________________________ > 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 |
|
From: srividhya <n.s...@ni...> - 2011-12-20 12:01:21
|
p { margin-bottom: 0.21cm; }
Hi XSLTForms Users !!!
We have
a scenario to validate XForms with XSLTForms in offline mode as well
as the same validation with online mode ...Pls suggest a possible
solution
Like i have a sample form with a date comparison
field .. So, i have written the rule in my client side XForms with
Bind option. while i submit the date to the server i need to reuse
the same bind rule in server side ....We dont know how to do the same
in Server side with Same client side rule written in XForms bind
section .
with thanks and regards,
N. srividhya
NIC-OTC,
chennai.
On 12/20/11, xsl...@li... wrote:
> Send Xsltforms-support mailing list submissions to
> xsl...@li...
>
> To subscribe or unsubscribe via the World Wide Web, visit
> https://lists.sourceforge.net/lists/listinfo/xsltforms-support
> or, via email, send a message with subject or body 'help' to
> xsl...@li...
>
> You can reach the person managing the list at
> xsl...@li...
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Xsltforms-support digest..."
>
>
> Today's Topics:
>
> 1. Re: XSLTForms with ASP.NET (Alain Couthures)
> 2. Re: xforms:repeat / tr / br (Alain Couthures)
> 3. Re: Xsltforms-support Digest, Vol 31, Issue 8 (srividhya)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Mon, 19 Dec 2011 21:12:37 +0100
> From: Alain Couthures <ala...@ag...>
> Subject: Re: [Xsltforms-support] XSLTForms with ASP.NET
> To: William David Velasquez <wi...@bi...>
> Cc: xsl...@li...
> Message-ID: <4EE...@ag...>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
> Hi William,
>
> I have added 'type="button"' to each generated button element and I hope
> that it will ease XSLTForms use with ASP.Net.
>
> It would be great if there was a section in the XSLTForms WikiBook
> (http://en.wikibooks.org/wiki/XSLTForms) about ASP.Net!
>
> Thanks!
>
> -Alain
>
> Le 16/12/2011 22:11, William David Velasquez a ?crit :
> > Hi XForms fans!
> >
> > I just saved tons of work using XForms instead of WebForms in a .NET
> > project I?m currently working.
> >
> > It's pretty easy to include an XForms in a ASP.NET page using XSLTForms
> > and the asp:Xml Control for a server side transform. This line does the
> > trick:
> >
> > <asp:Xml ID="Xml1" runat="server" DocumentSource="~/myform.xforms"
> > TransformSource="~/xsltforms/xsltforms.xsl" EnableViewState="False"
> > ></asp:Xml>
> >
> > And to process the submission with DOM, two lines do the work:
> >
> > <%@ Page Language="C#" %>
> > <%
> > System.Xml.XmlDocument doc = new System.Xml.XmlDocument();
> > doc.Load(Request.InputStream);
> >
> > // process your xml here....
> >
> > %>
> >
> > There is just two things to keep in mind:
> >
> > 1. You need the latest version of XSLTForms from the repository (I
> > tested with rev 521). Previous versions don?t work with .NET
> > transformation engine.
> >
> > 2. ASP.NET WebForms wraps all the controls in the page with<form
> > >...</form> so when the Xml Control renders the xhtml for the XForm,
> > clicking in the xf:triggers post the form submission (an undesirable
> > behavior) because they are rendered as<button> with the default
> > type=submit.
> >
> > There are to workarounds:
> > 1. Move the<asp:Xml> outside the<form runat="server"> tag in the aspx
> > page,
> > 2. When that isn't possible (for example, when you use MasterPages),
> > make a little modification in xsltforms.xsl to add the atributte
> > type="button" when triggers are rendered. This is done in this template
> > (line 1141 in rev 521):
> >
> > <xsl:template match="xforms:trigger|xforms:submit" ...
> >
> > Below is the generation of the<button> tag (line 1162 in rev 521):
> >
> > <button>
> > <xsl:copy-of select="$innerbody"/>
> > </button>
> >
> > You can add the attribute this way:
> >
> > <button>
> > <xsl:attribute name="type">button</xsl:attribute>
> > <xsl:copy-of select="$innerbody"/>
> > </button>
> >
> > I know monsieur Alain kindly will include this change in a future
> > release ;-)
> >
> > I'm getting mixed reaactions from my co-workers (most of them are MS
> > fans), so I asked them to write a form using the normal aspnet way to
> > calculate an invoice, allowing users to add details lines, sum totals,
> > taxes, etc. They had to write more than 50 tricky lines of code, with
> > events handlers, javascript and a lot of Googling. Then I showed it with
> > XForms: five xf:bind and two xf:trigger for custom logic
> >
> > No need to say they are starting to get convinced.
> >
> > Merry Christmas,
> >
> >
> > William Velasquez
> >
> > ------------------------------------------------------------------------------
> > Learn Windows Azure Live! Tuesday, Dec 13, 2011
> > Microsoft is holding a special Learn Windows Azure training event for
> > developers. It will provide a great way to learn Windows Azure and what it
> > provides. You can attend the event by watching it streamed LIVE online.
> > Learn more at http://p.sf.net/sfu/ms-windowsazure
> > _______________________________________________
> > Xsltforms-support mailing list
> > Xsl...@li...
> > https://lists.sourceforge.net/lists/listinfo/xsltforms-support
>
>
>
>
> ------------------------------
>
> Message: 2
> Date: Mon, 19 Dec 2011 21:30:28 +0100
> From: Alain Couthures <ala...@ag...>
> Subject: Re: [Xsltforms-support] xforms:repeat / tr / br
> To: st...@sa...
> Cc: xsl...@li...
> Message-ID: <4EE...@ag...>
> Content-Type: text/plain; charset="iso-8859-1"
>
> Hi Steve,
>
> * <br/> being doubled occurs in some browsers when they apply the XSLT
> stylesheet themselves. I suggest you to use 2 DIV elements instead
> as a workaround.
> * Opera latest version is replacing @ev:event with @ev:actiontype in
> the XForms document (unbelievable!) so I added @ev:actiontype
> support! (This will be in the next commit!)
> * IE9 doesn't like empty SCRIPT elements (when @src is present,
> they're empty in XHTML...). You can change that accordingly in each
> of your pages but it's a frequent issue so I force now a dummy value
> (/* */) for them.
>
> Thank you for your feedbacks!
>
> -Alain
>
>
> Le 15/12/2011 15:23, st...@sa... a ?crit :
> > Hi, Alain,
> >
> > I have refactored my search form to use bind instead of group and things
> > are a bit better--with FF 8.0.1 the behaviour is as expected.
> >
> > On Safari/Chrome, a spurious<br/> is inserted (there is supposed to be
> > one in one of the TDs but Safari/Chrome put two). To reproduce:
> >
> > http://oracc.museum.upenn.edu/oas-nogroup.xml
> >
> > Click on the '+' button beside the hint diamond: the two rows of controls
> > should be separated by one<br/> but there are two there.
> >
> > On Opera, clicking on the '+' button changes the border indicating the
> > press has been received, but then nothing further happens.
> >
> > On IE 9 I get an XSLTForms Exception Incorrect Javascript code generation:
> > ReferenceError xsltforms_initImpl is undefined.
> >
> > Thanks for any insight,
> >
> > Steve
> >
> >
> >
> >
> > ------------------------------------------------------------------------------
> > 10 Tips for Better Server Consolidation
> > Server virtualization is being driven by many needs.
> > But none more important than the need to reduce IT complexity
> > while improving strategic productivity. Learn More!
> > http://www.accelacomm.com/jaw/sdnl/114/51507609/
> > _______________________________________________
> > Xsltforms-support mailing list
> > Xsl...@li...
> > https://lists.sourceforge.net/lists/listinfo/xsltforms-support
> >
>
>
> -------------- next part --------------
> An HTML attachment was scrubbed...
>
> ------------------------------
>
> Message: 3
> Date: Tue, 20 Dec 2011 11:13:37 +0530
> From: srividhya <n.s...@ni...>
> Subject: Re: [Xsltforms-support] Xsltforms-support Digest, Vol 31,
> Issue 8
> To: xsl...@li...
> Message-ID: <fb7...@ni...>
> Content-Type: text/plain; charset="iso-8859-1"
>
> Alain,
> ?????? Is it possible to do the validation through some libraries or API's for form data or xml data at server side without using XMLSchema or XForms bind controls..
>
> N. Srividhya
> OTC, N. I. C,
> Chennai
>
> On 12/17/11, xsl...@li... wrote:
> > Send Xsltforms-support mailing list submissions to
> > xsl...@li...
> >
> > To subscribe or unsubscribe via the World Wide Web, visit
> > https://lists.sourceforge.net/lists/listinfo/xsltforms-support
> > or, via email, send a message with subject or body 'help' to
> > xsl...@li...
> >
> > You can reach the person managing the list at
> > xsl...@li...
> >
> > When replying, please edit your Subject line so it is more specific
> > than "Re: Contents of Xsltforms-support digest..."
> >
> >
> > Today's Topics:
> >
> > ?? 1. Re: getting your feet wet with the profiler (was Re:
> > ????? optimization question) (Jakob Fix)
> > ?? 2. xforms:repeat / tr / br (st...@sa...)
> > ?? 3. XSLTForms with ASP.NET (William David Velasquez)
> > ?? 4. Re: XSLTForms with ASP.NET (Dan McCreary)
> >
> >
> > ----------------------------------------------------------------------
> >
> > Message: 1
> > Date: Wed, 14 Dec 2011 22:24:03 +0100
> > From: Jakob Fix <jak...@gm...>
> > Subject: Re: [Xsltforms-support] getting your feet wet with the
> > profiler (was Re: optimization question)
> > To: Kurt Cagle <kur...@gm...>
> > Cc: xsl...@li...
> > Message-ID:
> > <CAC...@ma...>
> > Content-Type: text/plain; charset=ISO-8859-1
> >
> > Hi Kurt, this is the exact same behaviour we have observed, and Alain
> > suggested using the profiler to find out where the bottlenecks might
> > be. Our forms are also served by MarkLogic, although that's a
> > coincidence rather than the reason, of course.
> >
> > Jakob.
> >
> >
> >
> > On Wed, Dec 14, 2011 at 22:16, Kurt Cagle <kur...@gm...> wrote:
> > > It may be something in the form rendering - the download of the XSLT file
> > > takes very little time, but I'm looking at 15-20s before the form itself is
> > > rendered in Chrome - compared to 2-3 for the October release which I had
> > > been using. Firefox is faster, but not appreciably. This is being delivered
> > > out of MarkLogic.
> > >
> > >
> > > Kurt Cagle
> > > Invited Expert, XForms Working Group, W3C
> > > Managing Editor, XMLToday.org
> > > kur...@gm...
> > > 443-837-8725
> > >
> > >
> > >
> > >
> > > On Wed, Dec 14, 2011 at 3:11 PM, Alain Couthures
> > > <ala...@ag...> wrote:
> > >>
> > >> Kurt,
> > >>
> > >> I'm not sure I understand correctly. Is it that, when clicking on the
> > >> Profiler button, you have to wait a very long time especially on Chrome with
> > >> which once you got an alert about a Javascript execution overload??
> > >>
> > >> Thanks!
> > >>
> > >> -Alain
> > >>
> > >> Le 13/12/2011 17:30, Kurt Cagle a ?crit?:
> > >>
> > >> Alain,
> > >>
> > >> I too like the profiler, though I'm a bit distressed with the overall
> > >> download time for the package - on Firefox it's long but acceptable, but on
> > >> Chrome it seems to take forever to load (it times out at least once).
> > >>
> > >> Kurt Cagle
> > >> Invited Expert, XForms Working Group, W3C
> > >> Managing Editor, XMLToday.org
> > >> kur...@gm...
> > >> 443-837-8725
> > >>
> > >>
> > >>
> > >>
> > >> On Fri, Dec 9, 2011 at 4:09 PM, Alain Couthures
> > >> <ala...@ag...> wrote:
> > >>>
> > >>> Wow! What an impressive Christmas gift for XML fans!
> > >>>
> > >>> You're absolutely right about the Profiler I added to XSLTForms: it's a
> > >>> wonderful tool to locate time-costing XPath expressions and refreshes.
> > >>>
> > >>> In the latest builds, the Profiler is even a form: this means that it
> > >>> can be customized by authors themselves. The profiling data is collected
> > >>> as an XML document and a specific processing-instruction tells XSLTForms
> > >>> which form to associate with.
> > >>>
> > >>> I plan to add more information in the Profiler instance (instances
> > >>> copies, the calling form source, ...): the Profiler will progressively
> > >>> become a real XForms Debugger written in XForms.
> > >>>
> > >>> About your form performance, I already suspected that counting preceding
> > >>> siblings would cost a lot of time: Javascript doesn't like loops
> > >>> (XSLTForms has to have its own XPath machine written in Javascript... I
> > >>> proposed a paper for XML Prague 2012 about how to write an XQuery
> > >>> compiler into Javascript instructions). I recently added support for the
> > >>> id() function and it's even much better for performance.
> > >>>
> > >>> Defining a subform is now another possibility to simplify a form. This
> > >>> is not yet documented but I already love it much. Don't hesitate to ask
> > >>> me about subforms if you're interested in.
> > >>>
> > >>> If you want to load another form in a new browser tab from an instance
> > >>> without server exchanges, defining an extra parameter for the load
> > >>> action should be simple with the processing-instruction capability I
> > >>> already use for the Profiler (this processing-instruction mechanism is
> > >>> very promising indeed, I'm currently building a small XRAP
> > >>> (XForms-REST-Apache-PHP) application with minimal generic PHP scripts,
> > >>> XML files and folders on server).
> > >>>
> > >>> XML allows us to consider programs as data. We might not be numerous to
> > >>> envision this (but the community is strong) and I have to confess that
> > >>> I'm still marveled by this.
> > >>>
> > >>> Thank you very much for your feedbacks!
> > >>>
> > >>> -Alain
> > >>>
> > >>> Le 09/12/2011 02:41, C. M. Sperberg-McQueen a ?crit :
> > >>> > Just a short report, for the record, of my experience with the profiler
> > >>> > now built into XSLTForms.
> > >>> >
> > >>> > Short version: ?the profiler is very helpful; in this case three
> > >>> > relatively
> > >>> > simple changes produced a five-fold speedup in the form.
> > >>> >
> > >>> > Long version:
> > >>> >
> > >>> > Looking at the profile information for the form I was worrying about,
> > >>> > which had gotten too slow when the document it was operating on got
> > >>> > bigger, I found that the most expensive XPath expressions were those
> > >>> > used for numbering the cells of the stack and for numbering the
> > >>> > instructions in the code area. ?I hard-coded appropriate numbers into
> > >>> > attributes in the machine description, and I added a set of actions for
> > >>> > adding a numbering attribute to the instructions in a program, after
> > >>> > loading it. I then replaced each XPath expression of the form
> > >>> > count(preceding-sibling::cell) +1 or count(preceding-sibling::i) with
> > >>> > a reference to @n. ?I also removed the support for editing the program
> > >>> > code; I'll move it to a separate form which communicates with the
> > >>> > main form by bouncing the XML representation of the document off
> > >>> > of a routine on the server.
> > >>> >
> > >>> > The first two changes (prenumbering the stack cells and autonumbering
> > >>> > the instructions in the program) reduced the XForms Cumulative Refresh
> > >>> > Time after loading a program and stepping through 50 cycles of machine
> > >>> > time (i.e. clicking Step 50 times) from 94.6 seconds to 42.3 seconds,
> > >>> > making the program about twice as fast.
> > >>> >
> > >>> > The third change (removing the editing functionality to a separate
> > >>> > form)
> > >>> > took it down to 17.7 seconds, another twofold speedup, for a five-fold
> > >>> > speedup overall.
> > >>> >
> > >>> > Those who are curious can compare the timings and the subjective
> > >>> > experience of the form by looking at the old and new versions of the
> > >>> > form at
> > >>> >
> > >>> > http://blackmesatech.com/2011/12/pl0/v01.xhtml (old)
> > >>> > http://blackmesatech.com/2011/12/pl0/index.xhtml (new)
> > >>> >
> > >>> > (Hmm. ?I notice that the XSLTforms I'm using on that server is
> > >>> > an old version that doesn't yet have the profiler. ?I'll have to update
> > >>> > soon.)
> > >>> >
> > >>>
> > >>>
> > >>>
> > >>> ------------------------------------------------------------------------------
> > >>> Cloud Services Checklist: Pricing and Packaging Optimization
> > >>> This white paper is intended to serve as a reference, checklist and point
> > >>> of
> > >>> discussion for anyone considering optimizing the pricing and packaging
> > >>> model
> > >>> of a cloud services business. Read Now!
> > >>> http://www.accelacomm.com/jaw/sfnl/114/51491232/
> > >>> _______________________________________________
> > >>> Xsltforms-support mailing list
> > >>> Xsl...@li...
> > >>> https://lists.sourceforge.net/lists/listinfo/xsltforms-support
> > >>
> > >>
> > >>
> > >
> > >
> > > ------------------------------------------------------------------------------
> > > Cloud Computing - Latest Buzzword or a Glimpse of the Future?
> > > This paper surveys cloud computing today: What are the benefits?
> > > Why are businesses embracing it? What are its payoffs and pitfalls?
> > > http://www.accelacomm.com/jaw/sdnl/114/51425149/
> > > _______________________________________________
> > > Xsltforms-support mailing list
> > > Xsl...@li...
> > > https://lists.sourceforge.net/lists/listinfo/xsltforms-support
> > >
> >
> >
> >
> > ------------------------------
> >
> > Message: 2
> > Date: Thu, 15 Dec 2011 09:23:21 -0500
> > From: st...@sa...
> > Subject: [Xsltforms-support] xforms:repeat / tr / br
> > To: xsl...@li...
> > Message-ID: <201...@we...>
> > Content-Type: text/plain; charset=ISO-8859-1; DelSp="Yes";
> > format="flowed"
> >
> > Hi, Alain,
> >
> > I have refactored my search form to use bind instead of group and things
> > are a bit better--with FF 8.0.1 the behaviour is as expected.
> >
> > On Safari/Chrome, a spurious <br/> is inserted (there is supposed to be
> > one in one of the TDs but Safari/Chrome put two).? To reproduce:
> >
> > ? http://oracc.museum.upenn.edu/oas-nogroup.xml
> >
> > Click on the '+' button beside the hint diamond: the two rows of controls
> > should be separated by one <br/> but there are two there.
> >
> > On Opera, clicking on the '+' button changes the border indicating the
> > press has been received, but then nothing further happens.
> >
> > On IE 9 I get an XSLTForms Exception Incorrect Javascript code generation:
> > ReferenceError xsltforms_initImpl is undefined.
> >
> > Thanks for any insight,
> >
> > ? Steve
> >
> >
> >
> >
> >
> >
> > ------------------------------
> >
> > Message: 3
> > Date: Fri, 16 Dec 2011 16:11:14 -0500
> > From: William David Velasquez <wi...@bi...>
> > Subject: [Xsltforms-support] XSLTForms with ASP.NET
> > To: <xsl...@li...>
> > Message-ID: <c11...@bi...>
> > Content-Type: text/plain; charset=UTF-8; format=flowed
> >
> > Hi XForms fans!
> >
> > I just saved tons of work using XForms instead of WebForms in a .NET
> > project I?m currently working.
> >
> > It's pretty easy to include an XForms in a ASP.NET page using XSLTForms
> > and the asp:Xml Control for a server side transform. This line does the
> > trick:
> >
> > <asp:Xml ID="Xml1" runat="server" DocumentSource="~/myform.xforms"
> > TransformSource="~/xsltforms/xsltforms.xsl" EnableViewState="False"
> > ?></asp:Xml>
> >
> > And to process the submission with DOM, two lines do the work:
> >
> > <%@ Page Language="C#"? %>
> > <%
> > System.Xml.XmlDocument doc = new System.Xml.XmlDocument();
> > doc.Load(Request.InputStream);
> >
> > // process your xml here....
> >
> > %>
> >
> > There is just two things to keep in mind:
> >
> > 1. You need the latest version of XSLTForms from the repository (I
> > tested with rev 521). Previous versions don?t work with .NET
> > transformation engine.
> >
> > 2. ASP.NET WebForms wraps all the controls in the page with <form
> > ?>...</form> so when the Xml Control renders the xhtml for the XForm,
> > clicking in the xf:triggers post the form submission (an undesirable
> > behavior) because they are rendered as <button> with the default
> > type=submit.
> >
> > There are to workarounds:
> > 1. Move the <asp:Xml> outside the <form runat="server"> tag in the aspx
> > page,
> > 2. When that isn't possible (for example, when you use MasterPages),
> > make a little modification in xsltforms.xsl to add the atributte
> > type="button" when triggers are rendered. This is done in this template
> > (line 1141 in rev 521):
> >
> > <xsl:template match="xforms:trigger|xforms:submit" ...
> >
> > Below is the generation of the <button> tag (line 1162 in rev 521):
> >
> > <button>
> > ?? <xsl:copy-of select="$innerbody"/>
> > </button>
> >
> > You can add the attribute this way:
> >
> > <button>
> > ?? <xsl:attribute name="type">button</xsl:attribute>
> > ?? <xsl:copy-of select="$innerbody"/>
> > </button>
> >
> > I know monsieur Alain kindly will include this change in a future
> > release ;-)
> >
> > I'm getting mixed reaactions from my co-workers (most of them are MS
> > fans), so I asked them to write a form using the normal aspnet way to
> > calculate an invoice, allowing users to add details lines, sum totals,
> > taxes, etc. They had to write more than 50 tricky lines of code, with
> > events handlers, javascript and a lot of Googling. Then I showed it with
> > XForms: five xf:bind and two xf:trigger for custom logic
> >
> > No need to say they are starting to get convinced.
> >
> > Merry Christmas,
> >
> >
> > William Velasquez
> >
> >
> >
> > ------------------------------
> >
> > Message: 4
> > Date: Fri, 16 Dec 2011 22:01:28 -0600
> > From: Dan McCreary <dan...@gm...>
> > Subject: Re: [Xsltforms-support] XSLTForms with ASP.NET
> > To: William David Velasquez <wi...@bi...>
> > Cc: xsl...@li...
> > Message-ID:
> > <CAO...@ma...>
> > Content-Type: text/plain; charset="iso-8859-1"
> >
> > William,
> >
> > Thank you for sharing this story.? It is always good to hear of
> > knowledgeable people showing the rest of the world "The Declarative Way".
> > I hope your team shares their results with others.
> >
> > - Dan
> >
> > On Fri, Dec 16, 2011 at 3:11 PM, William David Velasquez <
> > wi...@bi...> wrote:
> >
> > > Hi XForms fans!
> > >
> > > I just saved tons of work using XForms instead of WebForms in a .NET
> > > project I?m currently working.
> > >
> > > It's pretty easy to include an XForms in a ASP.NET page using XSLTForms
> > > and the asp:Xml Control for a server side transform. This line does the
> > > trick:
> > >
> > > <asp:Xml ID="Xml1" runat="server" DocumentSource="~/myform.xforms"
> > > TransformSource="~/xsltforms/xsltforms.xsl" EnableViewState="False"
> > >? ></asp:Xml>
> > >
> > > And to process the submission with DOM, two lines do the work:
> > >
> > > <%@ Page Language="C#"? %>
> > > <%
> > > System.Xml.XmlDocument doc = new System.Xml.XmlDocument();
> > > doc.Load(Request.InputStream);
> > >
> > > // process your xml here....
> > >
> > > %>
> > >
> > > There is just two things to keep in mind:
> > >
> > > 1. You need the latest version of XSLTForms from the repository (I
> > > tested with rev 521). Previous versions don?t work with .NET
> > > transformation engine.
> > >
> > > 2. ASP.NET WebForms wraps all the controls in the page with <form
> > >? >...</form> so when the Xml Control renders the xhtml for the XForm,
> > > clicking in the xf:triggers post the form submission (an undesirable
> > > behavior) because they are rendered as <button> with the default
> > > type=submit.
> > >
> > > There are to workarounds:
> > > 1. Move the <asp:Xml> outside the <form runat="server"> tag in the aspx
> > > page,
> > > 2. When that isn't possible (for example, when you use MasterPages),
> > > make a little modification in xsltforms.xsl to add the atributte
> > > type="button" when triggers are rendered. This is done in this template
> > > (line 1141 in rev 521):
> > >
> > > <xsl:template match="xforms:trigger|xforms:submit" ...
> > >
> > > Below is the generation of the <button> tag (line 1162 in rev 521):
> > >
> > > <button>
> > >?? <xsl:copy-of select="$innerbody"/>
> > > </button>
> > >
> > > You can add the attribute this way:
> > >
> > > <button>
> > >?? <xsl:attribute name="type">button</xsl:attribute>
> > >?? <xsl:copy-of select="$innerbody"/>
> > > </button>
> > >
> > > I know monsieur Alain kindly will include this change in a future
> > > release ;-)
> > >
> > > I'm getting mixed reaactions from my co-workers (most of them are MS
> > > fans), so I asked them to write a form using the normal aspnet way to
> > > calculate an invoice, allowing users to add details lines, sum totals,
> > > taxes, etc. They had to write more than 50 tricky lines of code, with
> > > events handlers, javascript and a lot of Googling. Then I showed it with
> > > XForms: five xf:bind and two xf:trigger for custom logic
> > >
> > > No need to say they are starting to get convinced.
> > >
> > > Merry Christmas,
> > >
> > >
> > > William Velasquez
> > >
> > >
> > > ------------------------------------------------------------------------------
> > > Learn Windows Azure Live!? Tuesday, Dec 13, 2011
> > > Microsoft is holding a special Learn Windows Azure training event for
> > > developers. It will provide a great way to learn Windows Azure and what it
> > > provides. You can attend the event by watching it streamed LIVE online.
> > > Learn more at http://p.sf.net/sfu/ms-windowsazure
> > > _______________________________________________
> > > 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
> > -------------- next part --------------
> > An HTML attachment was scrubbed...
> >
> > ------------------------------
> >
> > ------------------------------------------------------------------------------
> > Learn Windows Azure Live!? Tuesday, Dec 13, 2011
> > Microsoft is holding a special Learn Windows Azure training event for
> > developers. It will provide a great way to learn Windows Azure and what it
> > provides. You can attend the event by watching it streamed LIVE online.?
> > Learn more at http://p.sf.net/sfu/ms-windowsazure
> >
> > ------------------------------
> >
> > _______________________________________________
> > Xsltforms-support mailing list
> > Xsl...@li...
> > https://lists.sourceforge.net/lists/listinfo/xsltforms-support
> >
> >
> > End of Xsltforms-support Digest, Vol 31, Issue 8
> > ************************************************
> >
> >
> --
> With thanks and Regards,
> N.Srividhya(RS-I)
> O.T.C, N.I.C,
> Chennai.
> -------------- next part --------------
> An HTML attachment was scrubbed...
>
> ------------------------------
>
> ------------------------------------------------------------------------------
> Write once. Port to many.
> Get the SDK and tools to simplify cross-platform app development. Create
> new or port existing apps to sell to consumers worldwide. Explore the
> Intel AppUpSM program developer opportunity. appdeveloper.intel.com/join
> http://p.sf.net/sfu/intel-appdev
>
> ------------------------------
>
> _______________________________________________
> Xsltforms-support mailing list
> Xsl...@li...
> https://lists.sourceforge.net/lists/listinfo/xsltforms-support
>
>
> End of Xsltforms-support Digest, Vol 31, Issue 9
> ************************************************
>
>
--
With thanks and Regards,
N.Srividhya(RS-I)
O.T.C, N.I.C,
Chennai.
|
|
From: srividhya <n.s...@ni...> - 2011-12-20 05:42:16
|
Alain, Is it possible to do the validation through some libraries or API's for form data or xml data at server side without using XMLSchema or XForms bind controls.. N. Srividhya OTC, N. I. C, Chennai On 12/17/11, xsl...@li... wrote: > Send Xsltforms-support mailing list submissions to > xsl...@li... > > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.sourceforge.net/lists/listinfo/xsltforms-support > or, via email, send a message with subject or body 'help' to > xsl...@li... > > You can reach the person managing the list at > xsl...@li... > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of Xsltforms-support digest..." > > > Today's Topics: > > 1. Re: getting your feet wet with the profiler (was Re: > optimization question) (Jakob Fix) > 2. xforms:repeat / tr / br (st...@sa...) > 3. XSLTForms with ASP.NET (William David Velasquez) > 4. Re: XSLTForms with ASP.NET (Dan McCreary) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Wed, 14 Dec 2011 22:24:03 +0100 > From: Jakob Fix <jak...@gm...> > Subject: Re: [Xsltforms-support] getting your feet wet with the > profiler (was Re: optimization question) > To: Kurt Cagle <kur...@gm...> > Cc: xsl...@li... > Message-ID: > <CAC...@ma...> > Content-Type: text/plain; charset=ISO-8859-1 > > Hi Kurt, this is the exact same behaviour we have observed, and Alain > suggested using the profiler to find out where the bottlenecks might > be. Our forms are also served by MarkLogic, although that's a > coincidence rather than the reason, of course. > > Jakob. > > > > On Wed, Dec 14, 2011 at 22:16, Kurt Cagle <kur...@gm...> wrote: > > It may be something in the form rendering - the download of the XSLT file > > takes very little time, but I'm looking at 15-20s before the form itself is > > rendered in Chrome - compared to 2-3 for the October release which I had > > been using. Firefox is faster, but not appreciably. This is being delivered > > out of MarkLogic. > > > > > > Kurt Cagle > > Invited Expert, XForms Working Group, W3C > > Managing Editor, XMLToday.org > > kur...@gm... > > 443-837-8725 > > > > > > > > > > On Wed, Dec 14, 2011 at 3:11 PM, Alain Couthures > > <ala...@ag...> wrote: > >> > >> Kurt, > >> > >> I'm not sure I understand correctly. Is it that, when clicking on the > >> Profiler button, you have to wait a very long time especially on Chrome with > >> which once you got an alert about a Javascript execution overload?? > >> > >> Thanks! > >> > >> -Alain > >> > >> Le 13/12/2011 17:30, Kurt Cagle a ?crit?: > >> > >> Alain, > >> > >> I too like the profiler, though I'm a bit distressed with the overall > >> download time for the package - on Firefox it's long but acceptable, but on > >> Chrome it seems to take forever to load (it times out at least once). > >> > >> Kurt Cagle > >> Invited Expert, XForms Working Group, W3C > >> Managing Editor, XMLToday.org > >> kur...@gm... > >> 443-837-8725 > >> > >> > >> > >> > >> On Fri, Dec 9, 2011 at 4:09 PM, Alain Couthures > >> <ala...@ag...> wrote: > >>> > >>> Wow! What an impressive Christmas gift for XML fans! > >>> > >>> You're absolutely right about the Profiler I added to XSLTForms: it's a > >>> wonderful tool to locate time-costing XPath expressions and refreshes. > >>> > >>> In the latest builds, the Profiler is even a form: this means that it > >>> can be customized by authors themselves. The profiling data is collected > >>> as an XML document and a specific processing-instruction tells XSLTForms > >>> which form to associate with. > >>> > >>> I plan to add more information in the Profiler instance (instances > >>> copies, the calling form source, ...): the Profiler will progressively > >>> become a real XForms Debugger written in XForms. > >>> > >>> About your form performance, I already suspected that counting preceding > >>> siblings would cost a lot of time: Javascript doesn't like loops > >>> (XSLTForms has to have its own XPath machine written in Javascript... I > >>> proposed a paper for XML Prague 2012 about how to write an XQuery > >>> compiler into Javascript instructions). I recently added support for the > >>> id() function and it's even much better for performance. > >>> > >>> Defining a subform is now another possibility to simplify a form. This > >>> is not yet documented but I already love it much. Don't hesitate to ask > >>> me about subforms if you're interested in. > >>> > >>> If you want to load another form in a new browser tab from an instance > >>> without server exchanges, defining an extra parameter for the load > >>> action should be simple with the processing-instruction capability I > >>> already use for the Profiler (this processing-instruction mechanism is > >>> very promising indeed, I'm currently building a small XRAP > >>> (XForms-REST-Apache-PHP) application with minimal generic PHP scripts, > >>> XML files and folders on server). > >>> > >>> XML allows us to consider programs as data. We might not be numerous to > >>> envision this (but the community is strong) and I have to confess that > >>> I'm still marveled by this. > >>> > >>> Thank you very much for your feedbacks! > >>> > >>> -Alain > >>> > >>> Le 09/12/2011 02:41, C. M. Sperberg-McQueen a ?crit : > >>> > Just a short report, for the record, of my experience with the profiler > >>> > now built into XSLTForms. > >>> > > >>> > Short version: ?the profiler is very helpful; in this case three > >>> > relatively > >>> > simple changes produced a five-fold speedup in the form. > >>> > > >>> > Long version: > >>> > > >>> > Looking at the profile information for the form I was worrying about, > >>> > which had gotten too slow when the document it was operating on got > >>> > bigger, I found that the most expensive XPath expressions were those > >>> > used for numbering the cells of the stack and for numbering the > >>> > instructions in the code area. ?I hard-coded appropriate numbers into > >>> > attributes in the machine description, and I added a set of actions for > >>> > adding a numbering attribute to the instructions in a program, after > >>> > loading it. I then replaced each XPath expression of the form > >>> > count(preceding-sibling::cell) +1 or count(preceding-sibling::i) with > >>> > a reference to @n. ?I also removed the support for editing the program > >>> > code; I'll move it to a separate form which communicates with the > >>> > main form by bouncing the XML representation of the document off > >>> > of a routine on the server. > >>> > > >>> > The first two changes (prenumbering the stack cells and autonumbering > >>> > the instructions in the program) reduced the XForms Cumulative Refresh > >>> > Time after loading a program and stepping through 50 cycles of machine > >>> > time (i.e. clicking Step 50 times) from 94.6 seconds to 42.3 seconds, > >>> > making the program about twice as fast. > >>> > > >>> > The third change (removing the editing functionality to a separate > >>> > form) > >>> > took it down to 17.7 seconds, another twofold speedup, for a five-fold > >>> > speedup overall. > >>> > > >>> > Those who are curious can compare the timings and the subjective > >>> > experience of the form by looking at the old and new versions of the > >>> > form at > >>> > > >>> > http://blackmesatech.com/2011/12/pl0/v01.xhtml (old) > >>> > http://blackmesatech.com/2011/12/pl0/index.xhtml (new) > >>> > > >>> > (Hmm. ?I notice that the XSLTforms I'm using on that server is > >>> > an old version that doesn't yet have the profiler. ?I'll have to update > >>> > soon.) > >>> > > >>> > >>> > >>> > >>> ------------------------------------------------------------------------------ > >>> Cloud Services Checklist: Pricing and Packaging Optimization > >>> This white paper is intended to serve as a reference, checklist and point > >>> of > >>> discussion for anyone considering optimizing the pricing and packaging > >>> model > >>> of a cloud services business. Read Now! > >>> http://www.accelacomm.com/jaw/sfnl/114/51491232/ > >>> _______________________________________________ > >>> Xsltforms-support mailing list > >>> Xsl...@li... > >>> https://lists.sourceforge.net/lists/listinfo/xsltforms-support > >> > >> > >> > > > > > > ------------------------------------------------------------------------------ > > Cloud Computing - Latest Buzzword or a Glimpse of the Future? > > This paper surveys cloud computing today: What are the benefits? > > Why are businesses embracing it? What are its payoffs and pitfalls? > > http://www.accelacomm.com/jaw/sdnl/114/51425149/ > > _______________________________________________ > > Xsltforms-support mailing list > > Xsl...@li... > > https://lists.sourceforge.net/lists/listinfo/xsltforms-support > > > > > > ------------------------------ > > Message: 2 > Date: Thu, 15 Dec 2011 09:23:21 -0500 > From: st...@sa... > Subject: [Xsltforms-support] xforms:repeat / tr / br > To: xsl...@li... > Message-ID: <201...@we...> > Content-Type: text/plain; charset=ISO-8859-1; DelSp="Yes"; > format="flowed" > > Hi, Alain, > > I have refactored my search form to use bind instead of group and things > are a bit better--with FF 8.0.1 the behaviour is as expected. > > On Safari/Chrome, a spurious <br/> is inserted (there is supposed to be > one in one of the TDs but Safari/Chrome put two). To reproduce: > > http://oracc.museum.upenn.edu/oas-nogroup.xml > > Click on the '+' button beside the hint diamond: the two rows of controls > should be separated by one <br/> but there are two there. > > On Opera, clicking on the '+' button changes the border indicating the > press has been received, but then nothing further happens. > > On IE 9 I get an XSLTForms Exception Incorrect Javascript code generation: > ReferenceError xsltforms_initImpl is undefined. > > Thanks for any insight, > > Steve > > > > > > > ------------------------------ > > Message: 3 > Date: Fri, 16 Dec 2011 16:11:14 -0500 > From: William David Velasquez <wi...@bi...> > Subject: [Xsltforms-support] XSLTForms with ASP.NET > To: <xsl...@li...> > Message-ID: <c11...@bi...> > Content-Type: text/plain; charset=UTF-8; format=flowed > > Hi XForms fans! > > I just saved tons of work using XForms instead of WebForms in a .NET > project I?m currently working. > > It's pretty easy to include an XForms in a ASP.NET page using XSLTForms > and the asp:Xml Control for a server side transform. This line does the > trick: > > <asp:Xml ID="Xml1" runat="server" DocumentSource="~/myform.xforms" > TransformSource="~/xsltforms/xsltforms.xsl" EnableViewState="False" > ></asp:Xml> > > And to process the submission with DOM, two lines do the work: > > <%@ Page Language="C#" %> > <% > System.Xml.XmlDocument doc = new System.Xml.XmlDocument(); > doc.Load(Request.InputStream); > > // process your xml here.... > > %> > > There is just two things to keep in mind: > > 1. You need the latest version of XSLTForms from the repository (I > tested with rev 521). Previous versions don?t work with .NET > transformation engine. > > 2. ASP.NET WebForms wraps all the controls in the page with <form > >...</form> so when the Xml Control renders the xhtml for the XForm, > clicking in the xf:triggers post the form submission (an undesirable > behavior) because they are rendered as <button> with the default > type=submit. > > There are to workarounds: > 1. Move the <asp:Xml> outside the <form runat="server"> tag in the aspx > page, > 2. When that isn't possible (for example, when you use MasterPages), > make a little modification in xsltforms.xsl to add the atributte > type="button" when triggers are rendered. This is done in this template > (line 1141 in rev 521): > > <xsl:template match="xforms:trigger|xforms:submit" ... > > Below is the generation of the <button> tag (line 1162 in rev 521): > > <button> > <xsl:copy-of select="$innerbody"/> > </button> > > You can add the attribute this way: > > <button> > <xsl:attribute name="type">button</xsl:attribute> > <xsl:copy-of select="$innerbody"/> > </button> > > I know monsieur Alain kindly will include this change in a future > release ;-) > > I'm getting mixed reaactions from my co-workers (most of them are MS > fans), so I asked them to write a form using the normal aspnet way to > calculate an invoice, allowing users to add details lines, sum totals, > taxes, etc. They had to write more than 50 tricky lines of code, with > events handlers, javascript and a lot of Googling. Then I showed it with > XForms: five xf:bind and two xf:trigger for custom logic > > No need to say they are starting to get convinced. > > Merry Christmas, > > > William Velasquez > > > > ------------------------------ > > Message: 4 > Date: Fri, 16 Dec 2011 22:01:28 -0600 > From: Dan McCreary <dan...@gm...> > Subject: Re: [Xsltforms-support] XSLTForms with ASP.NET > To: William David Velasquez <wi...@bi...> > Cc: xsl...@li... > Message-ID: > <CAO...@ma...> > Content-Type: text/plain; charset="iso-8859-1" > > William, > > Thank you for sharing this story. It is always good to hear of > knowledgeable people showing the rest of the world "The Declarative Way". > I hope your team shares their results with others. > > - Dan > > On Fri, Dec 16, 2011 at 3:11 PM, William David Velasquez < > wi...@bi...> wrote: > > > Hi XForms fans! > > > > I just saved tons of work using XForms instead of WebForms in a .NET > > project I?m currently working. > > > > It's pretty easy to include an XForms in a ASP.NET page using XSLTForms > > and the asp:Xml Control for a server side transform. This line does the > > trick: > > > > <asp:Xml ID="Xml1" runat="server" DocumentSource="~/myform.xforms" > > TransformSource="~/xsltforms/xsltforms.xsl" EnableViewState="False" > > ></asp:Xml> > > > > And to process the submission with DOM, two lines do the work: > > > > <%@ Page Language="C#" %> > > <% > > System.Xml.XmlDocument doc = new System.Xml.XmlDocument(); > > doc.Load(Request.InputStream); > > > > // process your xml here.... > > > > %> > > > > There is just two things to keep in mind: > > > > 1. You need the latest version of XSLTForms from the repository (I > > tested with rev 521). Previous versions don?t work with .NET > > transformation engine. > > > > 2. ASP.NET WebForms wraps all the controls in the page with <form > > >...</form> so when the Xml Control renders the xhtml for the XForm, > > clicking in the xf:triggers post the form submission (an undesirable > > behavior) because they are rendered as <button> with the default > > type=submit. > > > > There are to workarounds: > > 1. Move the <asp:Xml> outside the <form runat="server"> tag in the aspx > > page, > > 2. When that isn't possible (for example, when you use MasterPages), > > make a little modification in xsltforms.xsl to add the atributte > > type="button" when triggers are rendered. This is done in this template > > (line 1141 in rev 521): > > > > <xsl:template match="xforms:trigger|xforms:submit" ... > > > > Below is the generation of the <button> tag (line 1162 in rev 521): > > > > <button> > > <xsl:copy-of select="$innerbody"/> > > </button> > > > > You can add the attribute this way: > > > > <button> > > <xsl:attribute name="type">button</xsl:attribute> > > <xsl:copy-of select="$innerbody"/> > > </button> > > > > I know monsieur Alain kindly will include this change in a future > > release ;-) > > > > I'm getting mixed reaactions from my co-workers (most of them are MS > > fans), so I asked them to write a form using the normal aspnet way to > > calculate an invoice, allowing users to add details lines, sum totals, > > taxes, etc. They had to write more than 50 tricky lines of code, with > > events handlers, javascript and a lot of Googling. Then I showed it with > > XForms: five xf:bind and two xf:trigger for custom logic > > > > No need to say they are starting to get convinced. > > > > Merry Christmas, > > > > > > William Velasquez > > > > > > ------------------------------------------------------------------------------ > > Learn Windows Azure Live! Tuesday, Dec 13, 2011 > > Microsoft is holding a special Learn Windows Azure training event for > > developers. It will provide a great way to learn Windows Azure and what it > > provides. You can attend the event by watching it streamed LIVE online. > > Learn more at http://p.sf.net/sfu/ms-windowsazure > > _______________________________________________ > > 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 > -------------- next part -------------- > An HTML attachment was scrubbed... > > ------------------------------ > > ------------------------------------------------------------------------------ > Learn Windows Azure Live! Tuesday, Dec 13, 2011 > Microsoft is holding a special Learn Windows Azure training event for > developers. It will provide a great way to learn Windows Azure and what it > provides. You can attend the event by watching it streamed LIVE online. > Learn more at http://p.sf.net/sfu/ms-windowsazure > > ------------------------------ > > _______________________________________________ > Xsltforms-support mailing list > Xsl...@li... > https://lists.sourceforge.net/lists/listinfo/xsltforms-support > > > End of Xsltforms-support Digest, Vol 31, Issue 8 > ************************************************ > > -- With thanks and Regards, N.Srividhya(RS-I) O.T.C, N.I.C, Chennai. |
|
From: Alain C. <ala...@ag...> - 2011-12-19 20:30:50
|
Hi Steve,
* <br/> being doubled occurs in some browsers when they apply the XSLT
stylesheet themselves. I suggest you to use 2 DIV elements instead
as a workaround.
* Opera latest version is replacing @ev:event with @ev:actiontype in
the XForms document (unbelievable!) so I added @ev:actiontype
support! (This will be in the next commit!)
* IE9 doesn't like empty SCRIPT elements (when @src is present,
they're empty in XHTML...). You can change that accordingly in each
of your pages but it's a frequent issue so I force now a dummy value
(/* */) for them.
Thank you for your feedbacks!
-Alain
Le 15/12/2011 15:23, st...@sa... a écrit :
> Hi, Alain,
>
> I have refactored my search form to use bind instead of group and things
> are a bit better--with FF 8.0.1 the behaviour is as expected.
>
> On Safari/Chrome, a spurious<br/> is inserted (there is supposed to be
> one in one of the TDs but Safari/Chrome put two). To reproduce:
>
> http://oracc.museum.upenn.edu/oas-nogroup.xml
>
> Click on the '+' button beside the hint diamond: the two rows of controls
> should be separated by one<br/> but there are two there.
>
> On Opera, clicking on the '+' button changes the border indicating the
> press has been received, but then nothing further happens.
>
> On IE 9 I get an XSLTForms Exception Incorrect Javascript code generation:
> ReferenceError xsltforms_initImpl is undefined.
>
> Thanks for any insight,
>
> Steve
>
>
>
>
> ------------------------------------------------------------------------------
> 10 Tips for Better Server Consolidation
> Server virtualization is being driven by many needs.
> But none more important than the need to reduce IT complexity
> while improving strategic productivity. Learn More!
> http://www.accelacomm.com/jaw/sdnl/114/51507609/
> _______________________________________________
> Xsltforms-support mailing list
> Xsl...@li...
> https://lists.sourceforge.net/lists/listinfo/xsltforms-support
>
|
|
From: Alain C. <ala...@ag...> - 2011-12-19 20:12:51
|
Hi William, I have added 'type="button"' to each generated button element and I hope that it will ease XSLTForms use with ASP.Net. It would be great if there was a section in the XSLTForms WikiBook (http://en.wikibooks.org/wiki/XSLTForms) about ASP.Net! Thanks! -Alain Le 16/12/2011 22:11, William David Velasquez a écrit : > Hi XForms fans! > > I just saved tons of work using XForms instead of WebForms in a .NET > project I´m currently working. > > It's pretty easy to include an XForms in a ASP.NET page using XSLTForms > and the asp:Xml Control for a server side transform. This line does the > trick: > > <asp:Xml ID="Xml1" runat="server" DocumentSource="~/myform.xforms" > TransformSource="~/xsltforms/xsltforms.xsl" EnableViewState="False" > ></asp:Xml> > > And to process the submission with DOM, two lines do the work: > > <%@ Page Language="C#" %> > <% > System.Xml.XmlDocument doc = new System.Xml.XmlDocument(); > doc.Load(Request.InputStream); > > // process your xml here.... > > %> > > There is just two things to keep in mind: > > 1. You need the latest version of XSLTForms from the repository (I > tested with rev 521). Previous versions don´t work with .NET > transformation engine. > > 2. ASP.NET WebForms wraps all the controls in the page with<form > >...</form> so when the Xml Control renders the xhtml for the XForm, > clicking in the xf:triggers post the form submission (an undesirable > behavior) because they are rendered as<button> with the default > type=submit. > > There are to workarounds: > 1. Move the<asp:Xml> outside the<form runat="server"> tag in the aspx > page, > 2. When that isn't possible (for example, when you use MasterPages), > make a little modification in xsltforms.xsl to add the atributte > type="button" when triggers are rendered. This is done in this template > (line 1141 in rev 521): > > <xsl:template match="xforms:trigger|xforms:submit" ... > > Below is the generation of the<button> tag (line 1162 in rev 521): > > <button> > <xsl:copy-of select="$innerbody"/> > </button> > > You can add the attribute this way: > > <button> > <xsl:attribute name="type">button</xsl:attribute> > <xsl:copy-of select="$innerbody"/> > </button> > > I know monsieur Alain kindly will include this change in a future > release ;-) > > I'm getting mixed reaactions from my co-workers (most of them are MS > fans), so I asked them to write a form using the normal aspnet way to > calculate an invoice, allowing users to add details lines, sum totals, > taxes, etc. They had to write more than 50 tricky lines of code, with > events handlers, javascript and a lot of Googling. Then I showed it with > XForms: five xf:bind and two xf:trigger for custom logic > > No need to say they are starting to get convinced. > > Merry Christmas, > > > William Velasquez > > ------------------------------------------------------------------------------ > Learn Windows Azure Live! Tuesday, Dec 13, 2011 > Microsoft is holding a special Learn Windows Azure training event for > developers. It will provide a great way to learn Windows Azure and what it > provides. You can attend the event by watching it streamed LIVE online. > Learn more at http://p.sf.net/sfu/ms-windowsazure > _______________________________________________ > Xsltforms-support mailing list > Xsl...@li... > https://lists.sourceforge.net/lists/listinfo/xsltforms-support |
|
From: Dan M. <dan...@gm...> - 2011-12-17 04:01:35
|
William, Thank you for sharing this story. It is always good to hear of knowledgeable people showing the rest of the world "The Declarative Way". I hope your team shares their results with others. - Dan On Fri, Dec 16, 2011 at 3:11 PM, William David Velasquez < wi...@bi...> wrote: > Hi XForms fans! > > I just saved tons of work using XForms instead of WebForms in a .NET > project I´m currently working. > > It's pretty easy to include an XForms in a ASP.NET page using XSLTForms > and the asp:Xml Control for a server side transform. This line does the > trick: > > <asp:Xml ID="Xml1" runat="server" DocumentSource="~/myform.xforms" > TransformSource="~/xsltforms/xsltforms.xsl" EnableViewState="False" > ></asp:Xml> > > And to process the submission with DOM, two lines do the work: > > <%@ Page Language="C#" %> > <% > System.Xml.XmlDocument doc = new System.Xml.XmlDocument(); > doc.Load(Request.InputStream); > > // process your xml here.... > > %> > > There is just two things to keep in mind: > > 1. You need the latest version of XSLTForms from the repository (I > tested with rev 521). Previous versions don´t work with .NET > transformation engine. > > 2. ASP.NET WebForms wraps all the controls in the page with <form > >...</form> so when the Xml Control renders the xhtml for the XForm, > clicking in the xf:triggers post the form submission (an undesirable > behavior) because they are rendered as <button> with the default > type=submit. > > There are to workarounds: > 1. Move the <asp:Xml> outside the <form runat="server"> tag in the aspx > page, > 2. When that isn't possible (for example, when you use MasterPages), > make a little modification in xsltforms.xsl to add the atributte > type="button" when triggers are rendered. This is done in this template > (line 1141 in rev 521): > > <xsl:template match="xforms:trigger|xforms:submit" ... > > Below is the generation of the <button> tag (line 1162 in rev 521): > > <button> > <xsl:copy-of select="$innerbody"/> > </button> > > You can add the attribute this way: > > <button> > <xsl:attribute name="type">button</xsl:attribute> > <xsl:copy-of select="$innerbody"/> > </button> > > I know monsieur Alain kindly will include this change in a future > release ;-) > > I'm getting mixed reaactions from my co-workers (most of them are MS > fans), so I asked them to write a form using the normal aspnet way to > calculate an invoice, allowing users to add details lines, sum totals, > taxes, etc. They had to write more than 50 tricky lines of code, with > events handlers, javascript and a lot of Googling. Then I showed it with > XForms: five xf:bind and two xf:trigger for custom logic > > No need to say they are starting to get convinced. > > Merry Christmas, > > > William Velasquez > > > ------------------------------------------------------------------------------ > Learn Windows Azure Live! Tuesday, Dec 13, 2011 > Microsoft is holding a special Learn Windows Azure training event for > developers. It will provide a great way to learn Windows Azure and what it > provides. You can attend the event by watching it streamed LIVE online. > Learn more at http://p.sf.net/sfu/ms-windowsazure > _______________________________________________ > 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 |
|
From: William D. V. <wi...@bi...> - 2011-12-16 21:11:22
|
Hi XForms fans! I just saved tons of work using XForms instead of WebForms in a .NET project I´m currently working. It's pretty easy to include an XForms in a ASP.NET page using XSLTForms and the asp:Xml Control for a server side transform. This line does the trick: <asp:Xml ID="Xml1" runat="server" DocumentSource="~/myform.xforms" TransformSource="~/xsltforms/xsltforms.xsl" EnableViewState="False" ></asp:Xml> And to process the submission with DOM, two lines do the work: <%@ Page Language="C#" %> <% System.Xml.XmlDocument doc = new System.Xml.XmlDocument(); doc.Load(Request.InputStream); // process your xml here.... %> There is just two things to keep in mind: 1. You need the latest version of XSLTForms from the repository (I tested with rev 521). Previous versions don´t work with .NET transformation engine. 2. ASP.NET WebForms wraps all the controls in the page with <form >...</form> so when the Xml Control renders the xhtml for the XForm, clicking in the xf:triggers post the form submission (an undesirable behavior) because they are rendered as <button> with the default type=submit. There are to workarounds: 1. Move the <asp:Xml> outside the <form runat="server"> tag in the aspx page, 2. When that isn't possible (for example, when you use MasterPages), make a little modification in xsltforms.xsl to add the atributte type="button" when triggers are rendered. This is done in this template (line 1141 in rev 521): <xsl:template match="xforms:trigger|xforms:submit" ... Below is the generation of the <button> tag (line 1162 in rev 521): <button> <xsl:copy-of select="$innerbody"/> </button> You can add the attribute this way: <button> <xsl:attribute name="type">button</xsl:attribute> <xsl:copy-of select="$innerbody"/> </button> I know monsieur Alain kindly will include this change in a future release ;-) I'm getting mixed reaactions from my co-workers (most of them are MS fans), so I asked them to write a form using the normal aspnet way to calculate an invoice, allowing users to add details lines, sum totals, taxes, etc. They had to write more than 50 tricky lines of code, with events handlers, javascript and a lot of Googling. Then I showed it with XForms: five xf:bind and two xf:trigger for custom logic No need to say they are starting to get convinced. Merry Christmas, William Velasquez |
|
From: <st...@sa...> - 2011-12-15 14:23:31
|
Hi, Alain, I have refactored my search form to use bind instead of group and things are a bit better--with FF 8.0.1 the behaviour is as expected. On Safari/Chrome, a spurious <br/> is inserted (there is supposed to be one in one of the TDs but Safari/Chrome put two). To reproduce: http://oracc.museum.upenn.edu/oas-nogroup.xml Click on the '+' button beside the hint diamond: the two rows of controls should be separated by one <br/> but there are two there. On Opera, clicking on the '+' button changes the border indicating the press has been received, but then nothing further happens. On IE 9 I get an XSLTForms Exception Incorrect Javascript code generation: ReferenceError xsltforms_initImpl is undefined. Thanks for any insight, Steve |
|
From: Jakob F. <jak...@gm...> - 2011-12-14 21:24:31
|
Hi Kurt, this is the exact same behaviour we have observed, and Alain suggested using the profiler to find out where the bottlenecks might be. Our forms are also served by MarkLogic, although that's a coincidence rather than the reason, of course. Jakob. On Wed, Dec 14, 2011 at 22:16, Kurt Cagle <kur...@gm...> wrote: > It may be something in the form rendering - the download of the XSLT file > takes very little time, but I'm looking at 15-20s before the form itself is > rendered in Chrome - compared to 2-3 for the October release which I had > been using. Firefox is faster, but not appreciably. This is being delivered > out of MarkLogic. > > > Kurt Cagle > Invited Expert, XForms Working Group, W3C > Managing Editor, XMLToday.org > kur...@gm... > 443-837-8725 > > > > > On Wed, Dec 14, 2011 at 3:11 PM, Alain Couthures > <ala...@ag...> wrote: >> >> Kurt, >> >> I'm not sure I understand correctly. Is it that, when clicking on the >> Profiler button, you have to wait a very long time especially on Chrome with >> which once you got an alert about a Javascript execution overload?? >> >> Thanks! >> >> -Alain >> >> Le 13/12/2011 17:30, Kurt Cagle a écrit : >> >> Alain, >> >> I too like the profiler, though I'm a bit distressed with the overall >> download time for the package - on Firefox it's long but acceptable, but on >> Chrome it seems to take forever to load (it times out at least once). >> >> Kurt Cagle >> Invited Expert, XForms Working Group, W3C >> Managing Editor, XMLToday.org >> kur...@gm... >> 443-837-8725 >> >> >> >> >> On Fri, Dec 9, 2011 at 4:09 PM, Alain Couthures >> <ala...@ag...> wrote: >>> >>> Wow! What an impressive Christmas gift for XML fans! >>> >>> You're absolutely right about the Profiler I added to XSLTForms: it's a >>> wonderful tool to locate time-costing XPath expressions and refreshes. >>> >>> In the latest builds, the Profiler is even a form: this means that it >>> can be customized by authors themselves. The profiling data is collected >>> as an XML document and a specific processing-instruction tells XSLTForms >>> which form to associate with. >>> >>> I plan to add more information in the Profiler instance (instances >>> copies, the calling form source, ...): the Profiler will progressively >>> become a real XForms Debugger written in XForms. >>> >>> About your form performance, I already suspected that counting preceding >>> siblings would cost a lot of time: Javascript doesn't like loops >>> (XSLTForms has to have its own XPath machine written in Javascript... I >>> proposed a paper for XML Prague 2012 about how to write an XQuery >>> compiler into Javascript instructions). I recently added support for the >>> id() function and it's even much better for performance. >>> >>> Defining a subform is now another possibility to simplify a form. This >>> is not yet documented but I already love it much. Don't hesitate to ask >>> me about subforms if you're interested in. >>> >>> If you want to load another form in a new browser tab from an instance >>> without server exchanges, defining an extra parameter for the load >>> action should be simple with the processing-instruction capability I >>> already use for the Profiler (this processing-instruction mechanism is >>> very promising indeed, I'm currently building a small XRAP >>> (XForms-REST-Apache-PHP) application with minimal generic PHP scripts, >>> XML files and folders on server). >>> >>> XML allows us to consider programs as data. We might not be numerous to >>> envision this (but the community is strong) and I have to confess that >>> I'm still marveled by this. >>> >>> Thank you very much for your feedbacks! >>> >>> -Alain >>> >>> Le 09/12/2011 02:41, C. M. Sperberg-McQueen a écrit : >>> > Just a short report, for the record, of my experience with the profiler >>> > now built into XSLTForms. >>> > >>> > Short version: the profiler is very helpful; in this case three >>> > relatively >>> > simple changes produced a five-fold speedup in the form. >>> > >>> > Long version: >>> > >>> > Looking at the profile information for the form I was worrying about, >>> > which had gotten too slow when the document it was operating on got >>> > bigger, I found that the most expensive XPath expressions were those >>> > used for numbering the cells of the stack and for numbering the >>> > instructions in the code area. I hard-coded appropriate numbers into >>> > attributes in the machine description, and I added a set of actions for >>> > adding a numbering attribute to the instructions in a program, after >>> > loading it. I then replaced each XPath expression of the form >>> > count(preceding-sibling::cell) +1 or count(preceding-sibling::i) with >>> > a reference to @n. I also removed the support for editing the program >>> > code; I'll move it to a separate form which communicates with the >>> > main form by bouncing the XML representation of the document off >>> > of a routine on the server. >>> > >>> > The first two changes (prenumbering the stack cells and autonumbering >>> > the instructions in the program) reduced the XForms Cumulative Refresh >>> > Time after loading a program and stepping through 50 cycles of machine >>> > time (i.e. clicking Step 50 times) from 94.6 seconds to 42.3 seconds, >>> > making the program about twice as fast. >>> > >>> > The third change (removing the editing functionality to a separate >>> > form) >>> > took it down to 17.7 seconds, another twofold speedup, for a five-fold >>> > speedup overall. >>> > >>> > Those who are curious can compare the timings and the subjective >>> > experience of the form by looking at the old and new versions of the >>> > form at >>> > >>> > http://blackmesatech.com/2011/12/pl0/v01.xhtml (old) >>> > http://blackmesatech.com/2011/12/pl0/index.xhtml (new) >>> > >>> > (Hmm. I notice that the XSLTforms I'm using on that server is >>> > an old version that doesn't yet have the profiler. I'll have to update >>> > soon.) >>> > >>> >>> >>> >>> ------------------------------------------------------------------------------ >>> Cloud Services Checklist: Pricing and Packaging Optimization >>> This white paper is intended to serve as a reference, checklist and point >>> of >>> discussion for anyone considering optimizing the pricing and packaging >>> model >>> of a cloud services business. Read Now! >>> http://www.accelacomm.com/jaw/sfnl/114/51491232/ >>> _______________________________________________ >>> Xsltforms-support mailing list >>> Xsl...@li... >>> https://lists.sourceforge.net/lists/listinfo/xsltforms-support >> >> >> > > > ------------------------------------------------------------------------------ > Cloud Computing - Latest Buzzword or a Glimpse of the Future? > This paper surveys cloud computing today: What are the benefits? > Why are businesses embracing it? What are its payoffs and pitfalls? > http://www.accelacomm.com/jaw/sdnl/114/51425149/ > _______________________________________________ > Xsltforms-support mailing list > Xsl...@li... > https://lists.sourceforge.net/lists/listinfo/xsltforms-support > |
|
From: Kurt C. <kur...@gm...> - 2011-12-14 21:16:53
|
It may be something in the form rendering - the download of the XSLT file takes very little time, but I'm looking at 15-20s before the form itself is rendered in Chrome - compared to 2-3 for the October release which I had been using. Firefox is faster, but not appreciably. This is being delivered out of MarkLogic. Kurt Cagle Invited Expert, XForms Working Group, W3C Managing Editor, XMLToday.org kur...@gm... 443-837-8725 On Wed, Dec 14, 2011 at 3:11 PM, Alain Couthures < ala...@ag...> wrote: > Kurt, > > I'm not sure I understand correctly. Is it that, when clicking on the > Profiler button, you have to wait a very long time especially on Chrome > with which once you got an alert about a Javascript execution overload?? > > Thanks! > > -Alain > > Le 13/12/2011 17:30, Kurt Cagle a écrit : > > Alain, > > I too like the profiler, though I'm a bit distressed with the overall > download time for the package - on Firefox it's long but acceptable, but on > Chrome it seems to take forever to load (it times out at least once). > > Kurt Cagle > Invited Expert, XForms Working Group, W3C > Managing Editor, XMLToday.org > kur...@gm... > 443-837-8725 > > > > > On Fri, Dec 9, 2011 at 4:09 PM, Alain Couthures < > ala...@ag...> wrote: > >> Wow! What an impressive Christmas gift for XML fans! >> >> You're absolutely right about the Profiler I added to XSLTForms: it's a >> wonderful tool to locate time-costing XPath expressions and refreshes. >> >> In the latest builds, the Profiler is even a form: this means that it >> can be customized by authors themselves. The profiling data is collected >> as an XML document and a specific processing-instruction tells XSLTForms >> which form to associate with. >> >> I plan to add more information in the Profiler instance (instances >> copies, the calling form source, ...): the Profiler will progressively >> become a real XForms Debugger written in XForms. >> >> About your form performance, I already suspected that counting preceding >> siblings would cost a lot of time: Javascript doesn't like loops >> (XSLTForms has to have its own XPath machine written in Javascript... I >> proposed a paper for XML Prague 2012 about how to write an XQuery >> compiler into Javascript instructions). I recently added support for the >> id() function and it's even much better for performance. >> >> Defining a subform is now another possibility to simplify a form. This >> is not yet documented but I already love it much. Don't hesitate to ask >> me about subforms if you're interested in. >> >> If you want to load another form in a new browser tab from an instance >> without server exchanges, defining an extra parameter for the load >> action should be simple with the processing-instruction capability I >> already use for the Profiler (this processing-instruction mechanism is >> very promising indeed, I'm currently building a small XRAP >> (XForms-REST-Apache-PHP) application with minimal generic PHP scripts, >> XML files and folders on server). >> >> XML allows us to consider programs as data. We might not be numerous to >> envision this (but the community is strong) and I have to confess that >> I'm still marveled by this. >> >> Thank you very much for your feedbacks! >> >> -Alain >> >> Le 09/12/2011 02:41, C. M. Sperberg-McQueen a écrit : >> > Just a short report, for the record, of my experience with the >> profiler >> > now built into XSLTForms. >> > >> > Short version: the profiler is very helpful; in this case three >> relatively >> > simple changes produced a five-fold speedup in the form. >> > >> > Long version: >> > >> > Looking at the profile information for the form I was worrying about, >> > which had gotten too slow when the document it was operating on got >> > bigger, I found that the most expensive XPath expressions were those >> > used for numbering the cells of the stack and for numbering the >> > instructions in the code area. I hard-coded appropriate numbers into >> > attributes in the machine description, and I added a set of actions for >> > adding a numbering attribute to the instructions in a program, after >> > loading it. I then replaced each XPath expression of the form >> > count(preceding-sibling::cell) +1 or count(preceding-sibling::i) with >> > a reference to @n. I also removed the support for editing the program >> > code; I'll move it to a separate form which communicates with the >> > main form by bouncing the XML representation of the document off >> > of a routine on the server. >> > >> > The first two changes (prenumbering the stack cells and autonumbering >> > the instructions in the program) reduced the XForms Cumulative Refresh >> > Time after loading a program and stepping through 50 cycles of machine >> > time (i.e. clicking Step 50 times) from 94.6 seconds to 42.3 seconds, >> > making the program about twice as fast. >> > >> > The third change (removing the editing functionality to a separate form) >> > took it down to 17.7 seconds, another twofold speedup, for a five-fold >> > speedup overall. >> > >> > Those who are curious can compare the timings and the subjective >> > experience of the form by looking at the old and new versions of the >> > form at >> > >> > http://blackmesatech.com/2011/12/pl0/v01.xhtml (old) >> > http://blackmesatech.com/2011/12/pl0/index.xhtml (new) >> > >> > (Hmm. I notice that the XSLTforms I'm using on that server is >> > an old version that doesn't yet have the profiler. I'll have to update >> soon.) >> > >> >> >> >> ------------------------------------------------------------------------------ >> Cloud Services Checklist: Pricing and Packaging Optimization >> This white paper is intended to serve as a reference, checklist and point >> of >> discussion for anyone considering optimizing the pricing and packaging >> model >> of a cloud services business. Read Now! >> http://www.accelacomm.com/jaw/sfnl/114/51491232/ >> _______________________________________________ >> Xsltforms-support mailing list >> Xsl...@li... >> https://lists.sourceforge.net/lists/listinfo/xsltforms-support >> > > > |
|
From: Alain C. <ala...@ag...> - 2011-12-14 20:11:38
|
Kurt, I'm not sure I understand correctly. Is it that, when clicking on the Profiler button, you have to wait a very long time especially on Chrome with which once you got an alert about a Javascript execution overload?? Thanks! -Alain Le 13/12/2011 17:30, Kurt Cagle a écrit : > Alain, > > I too like the profiler, though I'm a bit distressed with the overall > download time for the package - on Firefox it's long but acceptable, > but on Chrome it seems to take forever to load (it times out at least > once). > > Kurt Cagle > Invited Expert, XForms Working Group, W3C > Managing Editor, XMLToday.org > kur...@gm... <mailto:kur...@gm...> > 443-837-8725 > > > > > On Fri, Dec 9, 2011 at 4:09 PM, Alain Couthures > <ala...@ag... <mailto:ala...@ag...>> > wrote: > > Wow! What an impressive Christmas gift for XML fans! > > You're absolutely right about the Profiler I added to XSLTForms: > it's a > wonderful tool to locate time-costing XPath expressions and refreshes. > > In the latest builds, the Profiler is even a form: this means that it > can be customized by authors themselves. The profiling data is > collected > as an XML document and a specific processing-instruction tells > XSLTForms > which form to associate with. > > I plan to add more information in the Profiler instance (instances > copies, the calling form source, ...): the Profiler will progressively > become a real XForms Debugger written in XForms. > > About your form performance, I already suspected that counting > preceding > siblings would cost a lot of time: Javascript doesn't like loops > (XSLTForms has to have its own XPath machine written in > Javascript... I > proposed a paper for XML Prague 2012 about how to write an XQuery > compiler into Javascript instructions). I recently added support > for the > id() function and it's even much better for performance. > > Defining a subform is now another possibility to simplify a form. This > is not yet documented but I already love it much. Don't hesitate > to ask > me about subforms if you're interested in. > > If you want to load another form in a new browser tab from an instance > without server exchanges, defining an extra parameter for the load > action should be simple with the processing-instruction capability I > already use for the Profiler (this processing-instruction mechanism is > very promising indeed, I'm currently building a small XRAP > (XForms-REST-Apache-PHP) application with minimal generic PHP scripts, > XML files and folders on server). > > XML allows us to consider programs as data. We might not be > numerous to > envision this (but the community is strong) and I have to confess that > I'm still marveled by this. > > Thank you very much for your feedbacks! > > -Alain > > Le 09/12/2011 02:41, C. M. Sperberg-McQueen a écrit : > > Just a short report, for the record, of my experience with the > profiler > > now built into XSLTForms. > > > > Short version: the profiler is very helpful; in this case three > relatively > > simple changes produced a five-fold speedup in the form. > > > > Long version: > > > > Looking at the profile information for the form I was worrying > about, > > which had gotten too slow when the document it was operating on got > > bigger, I found that the most expensive XPath expressions were those > > used for numbering the cells of the stack and for numbering the > > instructions in the code area. I hard-coded appropriate numbers > into > > attributes in the machine description, and I added a set of > actions for > > adding a numbering attribute to the instructions in a program, after > > loading it. I then replaced each XPath expression of the form > > count(preceding-sibling::cell) +1 or count(preceding-sibling::i) > with > > a reference to @n. I also removed the support for editing the > program > > code; I'll move it to a separate form which communicates with the > > main form by bouncing the XML representation of the document off > > of a routine on the server. > > > > The first two changes (prenumbering the stack cells and > autonumbering > > the instructions in the program) reduced the XForms Cumulative > Refresh > > Time after loading a program and stepping through 50 cycles of > machine > > time (i.e. clicking Step 50 times) from 94.6 seconds to 42.3 > seconds, > > making the program about twice as fast. > > > > The third change (removing the editing functionality to a > separate form) > > took it down to 17.7 seconds, another twofold speedup, for a > five-fold > > speedup overall. > > > > Those who are curious can compare the timings and the subjective > > experience of the form by looking at the old and new versions of the > > form at > > > > http://blackmesatech.com/2011/12/pl0/v01.xhtml (old) > > http://blackmesatech.com/2011/12/pl0/index.xhtml (new) > > > > (Hmm. I notice that the XSLTforms I'm using on that server is > > an old version that doesn't yet have the profiler. I'll have to > update soon.) > > > > > ------------------------------------------------------------------------------ > Cloud Services Checklist: Pricing and Packaging Optimization > This white paper is intended to serve as a reference, checklist > and point of > discussion for anyone considering optimizing the pricing and > packaging model > of a cloud services business. Read Now! > http://www.accelacomm.com/jaw/sfnl/114/51491232/ > _______________________________________________ > Xsltforms-support mailing list > Xsl...@li... > <mailto:Xsl...@li...> > https://lists.sourceforge.net/lists/listinfo/xsltforms-support > > |
|
From: Kurt C. <kur...@gm...> - 2011-12-13 16:30:53
|
Alain, I too like the profiler, though I'm a bit distressed with the overall download time for the package - on Firefox it's long but acceptable, but on Chrome it seems to take forever to load (it times out at least once). Kurt Cagle Invited Expert, XForms Working Group, W3C Managing Editor, XMLToday.org kur...@gm... 443-837-8725 On Fri, Dec 9, 2011 at 4:09 PM, Alain Couthures < ala...@ag...> wrote: > Wow! What an impressive Christmas gift for XML fans! > > You're absolutely right about the Profiler I added to XSLTForms: it's a > wonderful tool to locate time-costing XPath expressions and refreshes. > > In the latest builds, the Profiler is even a form: this means that it > can be customized by authors themselves. The profiling data is collected > as an XML document and a specific processing-instruction tells XSLTForms > which form to associate with. > > I plan to add more information in the Profiler instance (instances > copies, the calling form source, ...): the Profiler will progressively > become a real XForms Debugger written in XForms. > > About your form performance, I already suspected that counting preceding > siblings would cost a lot of time: Javascript doesn't like loops > (XSLTForms has to have its own XPath machine written in Javascript... I > proposed a paper for XML Prague 2012 about how to write an XQuery > compiler into Javascript instructions). I recently added support for the > id() function and it's even much better for performance. > > Defining a subform is now another possibility to simplify a form. This > is not yet documented but I already love it much. Don't hesitate to ask > me about subforms if you're interested in. > > If you want to load another form in a new browser tab from an instance > without server exchanges, defining an extra parameter for the load > action should be simple with the processing-instruction capability I > already use for the Profiler (this processing-instruction mechanism is > very promising indeed, I'm currently building a small XRAP > (XForms-REST-Apache-PHP) application with minimal generic PHP scripts, > XML files and folders on server). > > XML allows us to consider programs as data. We might not be numerous to > envision this (but the community is strong) and I have to confess that > I'm still marveled by this. > > Thank you very much for your feedbacks! > > -Alain > > Le 09/12/2011 02:41, C. M. Sperberg-McQueen a écrit : > > Just a short report, for the record, of my experience with the profiler > > now built into XSLTForms. > > > > Short version: the profiler is very helpful; in this case three > relatively > > simple changes produced a five-fold speedup in the form. > > > > Long version: > > > > Looking at the profile information for the form I was worrying about, > > which had gotten too slow when the document it was operating on got > > bigger, I found that the most expensive XPath expressions were those > > used for numbering the cells of the stack and for numbering the > > instructions in the code area. I hard-coded appropriate numbers into > > attributes in the machine description, and I added a set of actions for > > adding a numbering attribute to the instructions in a program, after > > loading it. I then replaced each XPath expression of the form > > count(preceding-sibling::cell) +1 or count(preceding-sibling::i) with > > a reference to @n. I also removed the support for editing the program > > code; I'll move it to a separate form which communicates with the > > main form by bouncing the XML representation of the document off > > of a routine on the server. > > > > The first two changes (prenumbering the stack cells and autonumbering > > the instructions in the program) reduced the XForms Cumulative Refresh > > Time after loading a program and stepping through 50 cycles of machine > > time (i.e. clicking Step 50 times) from 94.6 seconds to 42.3 seconds, > > making the program about twice as fast. > > > > The third change (removing the editing functionality to a separate form) > > took it down to 17.7 seconds, another twofold speedup, for a five-fold > > speedup overall. > > > > Those who are curious can compare the timings and the subjective > > experience of the form by looking at the old and new versions of the > > form at > > > > http://blackmesatech.com/2011/12/pl0/v01.xhtml (old) > > http://blackmesatech.com/2011/12/pl0/index.xhtml (new) > > > > (Hmm. I notice that the XSLTforms I'm using on that server is > > an old version that doesn't yet have the profiler. I'll have to update > soon.) > > > > > > ------------------------------------------------------------------------------ > Cloud Services Checklist: Pricing and Packaging Optimization > This white paper is intended to serve as a reference, checklist and point > of > discussion for anyone considering optimizing the pricing and packaging > model > of a cloud services business. Read Now! > http://www.accelacomm.com/jaw/sfnl/114/51491232/ > _______________________________________________ > Xsltforms-support mailing list > Xsl...@li... > https://lists.sourceforge.net/lists/listinfo/xsltforms-support > |
|
From: Leigh L K. J. <Lei...@xe...> - 2011-12-12 20:11:02
|
I tried your code with xsltforms-521 and noted you will need to change the custom XPath function code to use the XsltForms_ prefix and change capitalization, in two places. I also tried a quick test of putting readonly="true" (an XSLTForms extension, but common enough) on the instances that don't change by setvalue or form controls. In earlier versions (pre dependency) this produced a great performance improvement. The work Alain has done to take more advantage of dependency calculations might have lessened the effect, but I still think you should try it and run your profiler benchmark before and after. Leigh. _____ From: C. M. Sperberg-McQueen [mailto:cm...@bl...] Sent: Thursday, December 08, 2011 5:41 PM To: C. M. Sperberg-McQueen Cc: xsl...@li... Subject: Re: [Xsltforms-support] getting your feet wet with the profiler(was Re: optimization question) Just a short report, for the record, of my experience with the profiler now built into XSLTForms. Short version: the profiler is very helpful; in this case three relatively simple changes produced a five-fold speedup in the form. |
97 messages has been excluded from this view by a project administrator.
