xsltforms-support Mailing List for XSLTForms (Page 50)
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: Alain C. <ala...@ag...> - 2012-03-01 21:17:17
|
Kurt,
I didn't test before AVT for SVG and I discovered that the DOM API is
not exactly the same for SVG as for HTML.
I fixed issues about classes and about children vs childNodes.
So now it works for rev.533 with your example in which I added
style="overflow:hidden" for IE9.
Thank you for your feedbacks!
-Alain
Le 29/02/2012 18:44, Kurt Cagle a écrit :
> Alain,
>
> Just wanted to say that I've downloaded and been testing the new AVT
> and JS changes to xsltforms and have only two words: */This ROCKS!!!!/*
>
> I think this will have a /profound/ impact upon how applications are
> built with XForms and XSLTForms.
>
> The only downside I've seen thus far is that trying to work with
> embedded SVG is generating significant errors. The following
> illustrates this:
>
> (
> xdmp:set-response-content-type("text/xml"),
> processing-instruction {"xml-stylesheet"} {'type="text/xsl"
> href="/lib/xsltforms/xsltforms.xsl"'},
> <html xmlns="http://www.w3.org/1999/xhtml"
> xmlns:xf="http://www.w3.org/2002/xforms">
> <head>
> <title>Background Colors</title>
> <xf:model>
> <xf:instance id="colors">
> <colors xmlns="">
> <color name="Blue" code="#0000FF" size="100"/>
> <color name="Green" code="#00FF00" size="120"/>
> <color name="Olive" code="#808000" size="150"/>
> <color name="Orange" code="#F87A17" size="90"/>
> <color name="Pink" code="#FFC0CB" size="200"/>
> <color name="Purple" code="#800080" size="80"/>
> <color name="Red" code="#FF0000" size="150"/>
> <color name="Yellow" code="#FFFF00" size="200"/>
> </colors>
> </xf:instance>
> <xf:instance id="state">
> <state xmlns="">
> <color>#0000FF</color>
> </state>
> </xf:instance>
> </xf:model>
> </head>
> <body>
>
> <xf:select1 ref="instance('state')/color">
> <xf:itemset nodeset="instance('colors')//color">
> <xf:label ref="@name"/>
> <xf:value ref="@code"/>
> </xf:itemset>
> </xf:select1>
> <input type="text" value="{{instance('state')/*:color}}"
> style="color:{{instance('state')/*:color}}"></input>
> <div
> style="background-color:{{instance('state')/color}};width:{{instance('colors')/color[@code=instance('state')/color]/@size}}px;height:50px;">
> This is a test.</div>
> <svg width="300" height="300" xmlns="http://www.w3.org/2000/svg">
> <circle
> r="{{instance('colors')/color[@code=instance('state')/color]/@size}}"
> cx="50" cy="50" fill="red"/>
> </svg>
> </body>
> </html>)
>
> Given that AVT just landed, this is not surprising, just wanted to let
> you know. However, other than that issue, I'm having a blast playing
> with this.
>
>
> On Wed, Feb 29, 2012 at 12:06 PM, Leigh L. Klotz, Jr.
> <Lei...@xe... <mailto:Lei...@xe...>> wrote:
>
> Please respond with corrections.
> Please start new threads for discussion.
>
>
|
|
From: Alain C. <ala...@ag...> - 2012-03-01 20:57:18
|
Hi André,
This form contains the Unicode character for a line separator (
)
instead of
This character is not supported in rev. 490. You could test with the
latest revision but, recently, the Javascript classes have been renamed
("Core" became "XsltForms_browser", for example) and I noticed that you
are using some of them directly.
If this is not possible for you to replace 
 with and if you
don't want to upgrade your XSLTForms version now, I can send you a
patched version of rev. 490.
I also detected duplicate ids in your forms for "stratedit": the main
instance and a table. This can cause issues difficult to locate.
Thank you for your feedbacks!
-Alain
Le 29/02/2012 18:11, Andre Cusson a écrit :
> oops, sorry for hijacking and not replacing the message subject, wich
> this instance tries to fix ...
>
> Hi Alain,
>
> Sorry for taking your time for this, and I hope that you are fine.
>
> On the StratML portal (http://stratml.hyperbase.com/), we have 842
> preloaded XSLTForms, each loaded with a specific StratML document (see
> http://stratml.hyperbase.com/documents.html "Edit" links for the
> forms). They all seem to work fine, even as they get pretty large,
> but the last one added ( http://stratml.hyperbase.com/documents.html
> entry #485-LDTC, "Edit" link), which also seems to work fine when I
> run it locally, returns an error when accessed from the deployed
> version. The error message is as follows (also attached):
>
> Do you have any idea what could cause this?
>
> Thank you,
>
> Andre
>
|
|
From: Alain C. <ala...@ag...> - 2012-02-26 16:55:35
|
Hello,
Rev. 531 in SF repositories is intended to become XSLTForms 1.0 RC soon
unless big issues would be reported by you.
It will replace XSLTForms Beta 3 which is currently downloaded more than
50 times per week from SF.
It has been tested with various browsers including IE9 in IE8
compatibility mode.
Latest "impressive" features are:
* AVT for HTML elements
* direct Javascript function calls in XPath expressions (parameters
are always passed as strings)
* basic iText support (no @form support):
http://opendatakit.org/help/form-design/itext/
Thank you very much for your feedbacks!
-Alain
------------------------------------------------------------------------
<html xmlns="http://www.w3.org/1999/xhtml"
xmlns:xf="http://www.w3.org/2002/xforms">
<head>
<title>Background Colors</title>
<xf:model>
<xf:instance>
<colors xmlns="">
<color name="Blue" code="#0000FF"/>
<color name="Green" code="#00FF00"/>
<color name="Olive" code="#808000"/>
<color name="Orange" code="#F87A17"/>
<color name="Pink" code="#FFC0CB"/>
<color name="Purple" code="#800080"/>
<color name="Red" code="#FF0000"/>
<color name="Yellow" code="#FFFF00"/>
</colors>
</xf:instance>
</xf:model>
<script id="myscript" type="text/javascript">
function luminosity(c) {
var r = parseInt(c.substr(1,2), 16);
var g = parseInt(c.substr(3,2), 16);
var b = parseInt(c.substr(5,2), 16);
return 0.2126 * Math.pow(r/255, 2.2) + 0.7152 *
Math.pow(g/255, 2.2) + 0.0722 * Math.pow(b/255, 2.2);
}
</script>
</head>
<body>
<h1>Background Colors</h1>
<p>Use of Attribute Value Templates, Direct Javascript Function Calls
and Javascript Evaluation.</p>
<xf:repeat nodeset="color">
<span style="background-color:{@code}; color:{choose(luminosity(@code)
> 0.5,'black','white')}"> <xf:output value="@name"/> </span>
</xf:repeat>
<p>Javascript function source for luminosity extracted from HTML DOM:
<pre><xf:output
value="js-eval('document.getElementById("myscript").innerHTML')"/></pre>
</p>
</body>
</html>
------------------------------------------------------------------------
<html xmlns="http://www.w3.org/1999/xhtml"
xmlns:xf="http://www.w3.org/2002/xforms">
<head>
<title>Address Form</title>
<xf:model>
<xf:instance>
<Address xmlns="">
<LocationStreetFullText />
<LocationCityName />
<LocationStateName />
<LocationPostalID />
</Address>
</xf:instance>
<xf:itext>
<xf:translation lang="eng">
<xf:text id="address">
<xf:value>Mailing Address</xf:value>
</xf:text>
<xf:text id="streetFullText">
<xf:value>Street: </xf:value>
</xf:text>
<xf:text id="cityName">
<xf:value>City: </xf:value>
</xf:text>
<xf:text id="stateName">
<xf:value>State: </xf:value>
</xf:text>
<xf:text id="postalID">
<xf:value>Postal Code: </xf:value>
</xf:text>
</xf:translation>
<xf:translation lang="fr">
<xf:text id="address">
<xf:value>Adresse postale</xf:value>
</xf:text>
<xf:text id="streetFullText">
<xf:value>Rue : </xf:value>
</xf:text>
<xf:text id="cityName">
<xf:value>Ville : </xf:value>
</xf:text>
<xf:text id="stateName">
<xf:value>Département : </xf:value>
</xf:text>
<xf:text id="postalID">
<xf:value>Code postal : </xf:value>
</xf:text>
</xf:translation>
</xf:itext>
</xf:model>
</head>
<body>
<xf:group ref="/Address">
<fieldset>
<legend><xf:output value="itext('address')"/></legend>
<xf:input ref="LocationStreetFullText">
<xf:label><xf:output value="itext('streetFullText')"/></xf:label>
</xf:input>
<br/>
<xf:input ref="LocationCityName">
<xf:label><xf:output value="itext('cityName')"/></xf:label>
</xf:input>
<br/>
<xf:input ref="LocationStateName">
<xf:label><xf:output value="itext('stateName')"/></xf:label>
</xf:input>
<br/>
<xf:input ref="LocationPostalID">
<xf:label><xf:output value="itext('postalID')"/></xf:label>
</xf:input>
</fieldset>
</xf:group>
</body>
</html>
|
|
From: Alain C. <ala...@ag...> - 2012-02-23 06:14:53
|
Leigh,
You are right that isXhtml is currently always set to false.
When I experimented SVG support, I could see a better support in XHTML
mode so my intend was to enable both HTML and XHTML modes.
I should check that again to see if it's still useful or not.
Thanks!
-Alain
Le 22/02/2012 23:50, Leigh L Klotz Jr a écrit :
> I see the XSLTForms source has many copies of lines like this
>
> var body = XsltForms_browser.isXhtml ?
> document.getElementsByTagNameNS("http://www.w3.org/1999/xhtml",
> "body")[0] : document.getElementsByTagName("body")[0];
> var selects = XsltForms_browser.isXhtml ?
> document.getElementsByTagNameNS("http://www.w3.org/1999/xhtml",
> "select") : document.getElementsByTagName("select");
> var scriptelt = XsltForms_browser.isXhtml ?
> document.createElementNS("http://www.w3.org/1999/xhtml", "script") :
> document.createElement("script");
>
> At the moment I don't see any cases where isXhtml is true.
>
> But if there are any, would it make sense add these three functions to
> XsltForms_browser conditionally based on isXhtml?
>
> getElementByTagName : XsltForms_browser.isXhtml ? function (name) {
> return
> document.getElementsByTagNameNS("http://www.w3.org/1999/xhtml", name)[0]
> } : function(name) { return document.getElementsByTagName(name)[0]; },
>
> getElementsByTagName : XsltForms_browser.isXhtml ? function (name) {
> return
> document.getElementsByTagNameNS("http://www.w3.org/1999/xhtml", name)
> } : function(name) { return document.getElementsByTagName(name); },
>
> createElement : XsltForms_browser.isXhtml ? function (name) {
> return document.createElementNS("http://www.w3.org/1999/xhtml",
> "script")
> } : function (name) { return document.createElement("script"); },
>
> Leigh.
>
> ------------------------------------------------------------------------------
> Virtualization& Cloud Management Using Capacity Planning
> Cloud computing makes use of virtualization - but cloud computing
> also focuses on allowing computing to be delivered as a service.
> http://www.accelacomm.com/jaw/sfnl/114/51521223/
> _______________________________________________
> Xsltforms-support mailing list
> Xsl...@li...
> https://lists.sourceforge.net/lists/listinfo/xsltforms-support
>
|
|
From: Leigh L K. Jr <lei...@xe...> - 2012-02-22 22:50:48
|
I see the XSLTForms source has many copies of lines like this
var body = XsltForms_browser.isXhtml ?
document.getElementsByTagNameNS("http://www.w3.org/1999/xhtml",
"body")[0] : document.getElementsByTagName("body")[0];
var selects = XsltForms_browser.isXhtml ?
document.getElementsByTagNameNS("http://www.w3.org/1999/xhtml",
"select") : document.getElementsByTagName("select");
var scriptelt = XsltForms_browser.isXhtml ?
document.createElementNS("http://www.w3.org/1999/xhtml", "script") :
document.createElement("script");
At the moment I don't see any cases where isXhtml is true.
But if there are any, would it make sense add these three functions to
XsltForms_browser conditionally based on isXhtml?
getElementByTagName : XsltForms_browser.isXhtml ? function (name) {
return
document.getElementsByTagNameNS("http://www.w3.org/1999/xhtml", name)[0]
} : function(name) { return document.getElementsByTagName(name)[0]; },
getElementsByTagName : XsltForms_browser.isXhtml ? function (name) {
return
document.getElementsByTagNameNS("http://www.w3.org/1999/xhtml", name)
} : function(name) { return document.getElementsByTagName(name); },
createElement : XsltForms_browser.isXhtml ? function (name) {
return document.createElementNS("http://www.w3.org/1999/xhtml",
"script")
} : function (name) { return document.createElement("script"); },
Leigh.
|
|
From: Conal T. <con...@ve...> - 2012-02-17 00:38:07
|
Maybe this is just a typo in your email, Joe, but shouldn't you have @appearance="full"? On 16/02/12 08:40, Joe Wicentowski wrote: > Hello, > > I have a form that fails in Chrome (17.0) when I add the > @full="appearance" attribute on a select1 element. Without the > attribute, the form displays without error, but with the attribute, I > get an error - please see my attached image. > > When I use Firefox (4.0), the form works whether I have this attribute or not. > > Could you please let me know if this is a known issue with XSLTForms > Beta 3, or suggest some troubleshooting steps? I'm happy to test. > > Thanks, > Joe -- Conal Tuohy eResearch Business Analyst Victorian eResearch Strategic Initiative +61-466324297 |
|
From: Alain C. <ala...@ag...> - 2012-02-16 21:49:24
|
Hello Bill, Yes, XSLTForms supports all of them. Have a look at 5.2.6, 5.2.7.a and 5.2.7.b tests for xforms:email and xforms:card-number types. Test 2.3.a is based on a regular expression. It is possible with XSLTForms to define its own XPath functions with Javascript. Have a look at XsltForms_xpathCoreFunctions in xsltforms.js Thank you for your feedbacks! -Alain Le 16/02/2012 14:55, William Velasquez a écrit : > Hi list, > > I'm couldn't find clear documentation about the right way of validating > a field vs a regular expression (ie. email, credit-card, phone) client > side (you can always validate on server vs schema, but this is not the > case). > > I've found in XForms documentation and other sources various methods to > do this, but I'm not sure XSLTForms can support them: > > - Specifying an Schema for the instance > - Using custom datatypes in the type attribute of xf:bind > - Using user defined functions in Javascript and calling it from bind > constraints or xforms-value-changed event handler > - Maybe other... > > Can somebody state the best method to do this with XSLTForms. > > Thanks for all the help you can provide, > > > Bill > > > ------------------------------------------------------------------------------ > Virtualization& Cloud Management Using Capacity Planning > Cloud computing makes use of virtualization - but cloud computing > also focuses on allowing computing to be delivered as a service. > http://www.accelacomm.com/jaw/sfnl/114/51521223/ > _______________________________________________ > Xsltforms-support mailing list > Xsl...@li... > https://lists.sourceforge.net/lists/listinfo/xsltforms-support > |
|
From: Alain C. <ala...@ag...> - 2012-02-16 21:15:43
|
Leigh, > Did you see my similar proposed patch for local:// and session:// for > HTML5 local storage for xf:submission? > It's not too hard to imagine how it would work. > Yes! I committed it (local:// support only) in rev. 521. opener:// is different and it doesn't depend on HTML5 support. It doesn't require the main form to store locally the instance and, when the sub-form has sent the instance back, there is no need for an action to be triggered in the main form. Thanks! -Alain |
|
From: Alain C. <ala...@ag...> - 2012-02-16 20:43:08
|
Hello Joe, Yes, I think you should try with the latest SVN version of XSLTForms. Recent versions of browsers have unexpectedly changed some of their behaviors. Thank you for your feedbacks! -Alain Le 15/02/2012 22:52, Joe Wicentowski a écrit : > Oops, here's the attachment showing the error. > > Joe > > On Wed, Feb 15, 2012 at 4:40 PM, Joe Wicentowski<jo...@gm...> wrote: >> Hello, >> >> I have a form that fails in Chrome (17.0) when I add the >> @full="appearance" attribute on a select1 element. Without the >> attribute, the form displays without error, but with the attribute, I >> get an error - please see my attached image. >> >> When I use Firefox (4.0), the form works whether I have this attribute or not. >> >> Could you please let me know if this is a known issue with XSLTForms >> Beta 3, or suggest some troubleshooting steps? I'm happy to test. >> >> Thanks, >> Joe >> >> >> ------------------------------------------------------------------------------ >> Virtualization& Cloud Management Using Capacity Planning >> Cloud computing makes use of virtualization - but cloud computing >> also focuses on allowing computing to be delivered as a service. >> http://www.accelacomm.com/jaw/sfnl/114/51521223/ >> >> >> _______________________________________________ >> Xsltforms-support mailing list >> Xsl...@li... >> https://lists.sourceforge.net/lists/listinfo/xsltforms-support |
|
From: William V. <wi...@bi...> - 2012-02-16 13:55:33
|
Hi list, I'm couldn't find clear documentation about the right way of validating a field vs a regular expression (ie. email, credit-card, phone) client side (you can always validate on server vs schema, but this is not the case). I've found in XForms documentation and other sources various methods to do this, but I'm not sure XSLTForms can support them: - Specifying an Schema for the instance - Using custom datatypes in the type attribute of xf:bind - Using user defined functions in Javascript and calling it from bind constraints or xforms-value-changed event handler - Maybe other... Can somebody state the best method to do this with XSLTForms. Thanks for all the help you can provide, Bill |
|
From: Joe W. <jo...@gm...> - 2012-02-15 21:53:10
|
Oops, here's the attachment showing the error. Joe On Wed, Feb 15, 2012 at 4:40 PM, Joe Wicentowski <jo...@gm...> wrote: > Hello, > > I have a form that fails in Chrome (17.0) when I add the > @full="appearance" attribute on a select1 element. Without the > attribute, the form displays without error, but with the attribute, I > get an error - please see my attached image. > > When I use Firefox (4.0), the form works whether I have this attribute or not. > > Could you please let me know if this is a known issue with XSLTForms > Beta 3, or suggest some troubleshooting steps? I'm happy to test. > > Thanks, > Joe |
|
From: Joe W. <jo...@gm...> - 2012-02-15 21:40:41
|
Hello, I have a form that fails in Chrome (17.0) when I add the @full="appearance" attribute on a select1 element. Without the attribute, the form displays without error, but with the attribute, I get an error - please see my attached image. When I use Firefox (4.0), the form works whether I have this attribute or not. Could you please let me know if this is a known issue with XSLTForms Beta 3, or suggest some troubleshooting steps? I'm happy to test. Thanks, Joe |
|
From: Leigh L K. Jr <lei...@xe...> - 2012-02-14 23:43:32
|
http://blog.gingertech.net/2012/02/14/a-systematic-approach-to-making-web-applications-accessible/ |
|
From: Stephen C. <ste...@gm...> - 2012-02-14 21:44:40
|
Thanks Leigh, Interesting suggestion but in this case I'd first like to look at the actual process of generating the page markup via XSLT transformation of the XForm. The theory of HTML is that a browser can start rendering before it has received (or parsed) all of a page. So, I feel its possible to display the page/form layout very early on, before it is filled with data. Presently there is no feedback to the user, other than via the browser icons, to tell the user that something is happening and I think this is due mainly to the html markup being generated at the end of the XSLT transformation after all the Javascript. I'd also be interested to know if you could display a updating progress bar over the page whilst the loading/processing of the model instances is going on. Mind you, I just tried my big form in IE9.0 and it opened very quickly compared to Firefox 10, so maybe this is a very low priority. But I can see the usefulness of subforms for another part of my project though! Steve C On Wed, Feb 15, 2012 at 8:15 AM, Leigh L Klotz Jr <lei...@xe...>wrote: > Stephen, > You might also consider using the subform support: > > http://www.w3.org/MarkUp/Forms/wiki/XForms_2.0#The_load_Element > http://www.w3.org/MarkUp/Forms/wiki/XForms_2.0#The_unload_Element<http://www.w3.org/MarkUp/Forms/wiki/XForms_2.0#The_load_Element> > > Alain has implemented load/@show='embed' support in the SVN versions of > XSLTForms. > > The event sequence model isn't yet written up but you should expect > model-construct-done and refresh and so on to work. > The loaded subform should be an XHTML+XForms document with a minimal model > (if you want to use the outer form's model) or a full model with an ID (if > you want the page to use the new model). Start the html/body with a single > xf:group with the desired @model attribute. In the outer page, use an > empty xf:group to contain the loaded subform. The xf:group will get an > xforms-subform-loaded CSS class added to it when then load is done, and it > will be removed when the unload is done. > > Leigh. > > > > On 02/09/2012 01:59 PM, Stephen Cameron wrote: > > Hi Dan, > > Its not the model that is the issue in this case but the form itself. > > Doesn't the current versions of XSLTForms make use of a browser DOM object > for each model instance? Whereas originally it built a Javascript tree > which was slower. > > > On Fri, Feb 10, 2012 at 1:11 AM, Dan McCreary <dan...@gm...>wrote: > >> Hi Stephen, >> >> One alternative I might suggest is to use a "multi-tab" form and use a >> technique called "incremental model loading" if your model is large. >> >> Here is a demo of incremental model loading: >> >> http://en.wikibooks.org/wiki/XForms/Incremental_Model_Loading >> >> here is some sample UI for the tabs: >> >> http://en.wikibooks.org/wiki/XForms/Horizontal_File_Tab_Menu >> >> The tricky part comes if you have bind rules that span tabs. >> >> - Dan >> >> On Thu, Feb 9, 2012 at 3:19 AM, Stephen Cameron < >> ste...@gm...> wrote: >> >>> Hello All, >>> >>> I have a large xform and its going to get bigger, the time to transform >>> the xform and render it is now quite significant and getting to the point >>> where it is an issue, given that people don't see anything happening >>> throughout the process. >>> >>> One option is to pre-transform the xml 'form' into an html 'page', which >>> I used to do successfully but now cannot using Saxon, it complains. >>> >>> But my questions actually relate to browser transformation: >>> >>> 1. If I give all of the xform controls an explicit ID, rather than the >>> xsltforms.xsl stylesheet having to calculate them, does this speed up the >>> transformation significantly? >>> >>> 2. Is it possible perhaps to change the way that the transform occurs >>> such that the html markup is generated first and then the Xform related >>> javascript second. In theory the browser should start rendering the page >>> before the parsing of the Javascript section is completed. I'm imagining >>> this as a two-pass process in the xsltforms stylesheet. >>> >>> I have to say that once the rendering is completed the performance of >>> the form itself is excellent, despite its growing complexity. I assume this >>> is due to the presence of a true dependency graph in the newer versions of >>> XSLTForms. :) >>> >>> Thanks for your insights. >>> >>> Steve Cameron >>> >>> >>> >>> >>> >>> ------------------------------------------------------------------------------ >>> Virtualization & Cloud Management Using Capacity Planning >>> Cloud computing makes use of virtualization - but cloud computing >>> also focuses on allowing computing to be delivered as a service. >>> http://www.accelacomm.com/jaw/sfnl/114/51521223/ >>> _______________________________________________ >>> 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: Leigh L K. Jr <lei...@xe...> - 2012-02-14 21:15:25
|
Stephen, You might also consider using the subform support: http://www.w3.org/MarkUp/Forms/wiki/XForms_2.0#The_load_Element http://www.w3.org/MarkUp/Forms/wiki/XForms_2.0#The_unload_Element <http://www.w3.org/MarkUp/Forms/wiki/XForms_2.0#The_load_Element> Alain has implemented load/@show='embed' support in the SVN versions of XSLTForms. The event sequence model isn't yet written up but you should expect model-construct-done and refresh and so on to work. The loaded subform should be an XHTML+XForms document with a minimal model (if you want to use the outer form's model) or a full model with an ID (if you want the page to use the new model). Start the html/body with a single xf:group with the desired @model attribute. In the outer page, use an empty xf:group to contain the loaded subform. The xf:group will get an xforms-subform-loaded CSS class added to it when then load is done, and it will be removed when the unload is done. Leigh. On 02/09/2012 01:59 PM, Stephen Cameron wrote: > Hi Dan, > > Its not the model that is the issue in this case but the form itself. > > Doesn't the current versions of XSLTForms make use of a browser DOM > object for each model instance? Whereas originally it built a > Javascript tree which was slower. > > > On Fri, Feb 10, 2012 at 1:11 AM, Dan McCreary <dan...@gm... > <mailto:dan...@gm...>> wrote: > > Hi Stephen, > > One alternative I might suggest is to use a "multi-tab" form and > use a technique called "incremental model loading" if your model > is large. > > Here is a demo of incremental model loading: > > http://en.wikibooks.org/wiki/XForms/Incremental_Model_Loading > > here is some sample UI for the tabs: > > http://en.wikibooks.org/wiki/XForms/Horizontal_File_Tab_Menu > > The tricky part comes if you have bind rules that span tabs. > > - Dan > > On Thu, Feb 9, 2012 at 3:19 AM, Stephen Cameron > <ste...@gm... <mailto:ste...@gm...>> > wrote: > > Hello All, > > I have a large xform and its going to get bigger, the time to > transform the xform and render it is now quite significant and > getting to the point where it is an issue, given that people > don't see anything happening throughout the process. > > One option is to pre-transform the xml 'form' into an html > 'page', which I used to do successfully but now cannot using > Saxon, it complains. > > But my questions actually relate to browser transformation: > > 1. If I give all of the xform controls an explicit ID, rather > than the xsltforms.xsl stylesheet having to calculate them, > does this speed up the transformation significantly? > > 2. Is it possible perhaps to change the way that the transform > occurs such that the html markup is generated first and then > the Xform related javascript second. In theory the browser > should start rendering the page before the parsing of the > Javascript section is completed. I'm imagining this as a > two-pass process in the xsltforms stylesheet. > > I have to say that once the rendering is completed the > performance of the form itself is excellent, despite its > growing complexity. I assume this is due to the presence of a > true dependency graph in the newer versions of XSLTForms. :) > > Thanks for your insights. > > Steve Cameron > > > > > ------------------------------------------------------------------------------ > Virtualization & Cloud Management Using Capacity Planning > Cloud computing makes use of virtualization - but cloud computing > also focuses on allowing computing to be delivered as a service. > http://www.accelacomm.com/jaw/sfnl/114/51521223/ > _______________________________________________ > Xsltforms-support mailing list > Xsl...@li... > <mailto:Xsl...@li...> > https://lists.sourceforge.net/lists/listinfo/xsltforms-support > > > > > -- > Dan McCreary > Semantic Solutions Architect > office: (952) 931-9198 <tel:%28952%29%20931-9198> > cell: (612) 986-1552 <tel:%28612%29%20986-1552> > > |
|
From: Leigh L K. Jr <lei...@xe...> - 2012-02-14 21:00:06
|
Did you see my similar proposed patch for local:// and session:// for HTML5 local storage for xf:submission? It's not too hard to imagine how it would work. |
|
From: Alain C. <ala...@ag...> - 2012-02-13 19:20:49
|
Hello, I have committed an extension allowing a form loaded by another form (the opener) to access instances in it with submissions and methods GET and PUT. The resource has to respect the following format: "opener://" followed by the id of the instance in the opener form (there is already a reserved id for the Profiler form to access profiling data). This allows a presentation form to load an edit form for one of its instance without requiring to send this instance to the server first. This is illustrated it the two attached forms: open the xmlviewer form first then load the xmleditor form from it. Thank you for your feedbacks! -Alain |
|
From: Alain C. <ala...@ag...> - 2012-02-13 14:53:37
|
Hello Steve, Which version of Saxon are you using? The node-set() function calls are always to be customized for each XSLT engine and Saxon changed its own approach last year, as far as I remember... I would be happy to get effective time measures for the transformation step. On Windows, I'm using Powershell which is based on .Net 2.0 by default. I could send you a script file for testing if you wish. At browser side, it's difficult to measure something. Maybe native profilers might give an indication for XSLT step, especially if the generated page is not automatically inserting and calling Javascript instructions. With XSLTForms Profiler, you will get measures for the HTML and the Javascript part loadings. XSLTForms is adding a lot of HTML elements, "just in case" a group could become irrelevant for example. Yes, the way ids are added is clearly not optimized, I think that using xsl:number could be interesting for that purpose, but I'm still not convinced that it is costing a lot. Adding yourself every possible ids might be a workaround. Changing the place where the generated script elements are is also easy to modify in the XSLT stylesheet. Could you please send me one of your huge forms? Thanks! -Alain Le 09/02/2012 10:19, Stephen Cameron a écrit : > Hello All, > > I have a large xform and its going to get bigger, the time to > transform the xform and render it is now quite significant and getting > to the point where it is an issue, given that people don't see > anything happening throughout the process. > > One option is to pre-transform the xml 'form' into an html 'page', > which I used to do successfully but now cannot using Saxon, it complains. > > But my questions actually relate to browser transformation: > > 1. If I give all of the xform controls an explicit ID, rather than the > xsltforms.xsl stylesheet having to calculate them, does this speed up > the transformation significantly? > > 2. Is it possible perhaps to change the way that the transform occurs > such that the html markup is generated first and then the Xform > related javascript second. In theory the browser should start > rendering the page before the parsing of the Javascript section is > completed. I'm imagining this as a two-pass process in the xsltforms > stylesheet. > > I have to say that once the rendering is completed the performance of > the form itself is excellent, despite its growing complexity. I assume > this is due to the presence of a true dependency graph in the newer > versions of XSLTForms. :) > > Thanks for your insights. > > Steve Cameron > > > > > > ------------------------------------------------------------------------------ > Virtualization& Cloud Management Using Capacity Planning > Cloud computing makes use of virtualization - but cloud computing > also focuses on allowing computing to be delivered as a service. > http://www.accelacomm.com/jaw/sfnl/114/51521223/ > > > _______________________________________________ > Xsltforms-support mailing list > Xsl...@li... > https://lists.sourceforge.net/lists/listinfo/xsltforms-support |
|
From: Stephen C. <ste...@gm...> - 2012-02-09 21:59:17
|
Hi Dan, Its not the model that is the issue in this case but the form itself. Doesn't the current versions of XSLTForms make use of a browser DOM object for each model instance? Whereas originally it built a Javascript tree which was slower. On Fri, Feb 10, 2012 at 1:11 AM, Dan McCreary <dan...@gm...>wrote: > Hi Stephen, > > One alternative I might suggest is to use a "multi-tab" form and use a > technique called "incremental model loading" if your model is large. > > Here is a demo of incremental model loading: > > http://en.wikibooks.org/wiki/XForms/Incremental_Model_Loading > > here is some sample UI for the tabs: > > http://en.wikibooks.org/wiki/XForms/Horizontal_File_Tab_Menu > > The tricky part comes if you have bind rules that span tabs. > > - Dan > > On Thu, Feb 9, 2012 at 3:19 AM, Stephen Cameron < > ste...@gm...> wrote: > >> Hello All, >> >> I have a large xform and its going to get bigger, the time to transform >> the xform and render it is now quite significant and getting to the point >> where it is an issue, given that people don't see anything happening >> throughout the process. >> >> One option is to pre-transform the xml 'form' into an html 'page', which >> I used to do successfully but now cannot using Saxon, it complains. >> >> But my questions actually relate to browser transformation: >> >> 1. If I give all of the xform controls an explicit ID, rather than the >> xsltforms.xsl stylesheet having to calculate them, does this speed up the >> transformation significantly? >> >> 2. Is it possible perhaps to change the way that the transform occurs >> such that the html markup is generated first and then the Xform related >> javascript second. In theory the browser should start rendering the page >> before the parsing of the Javascript section is completed. I'm imagining >> this as a two-pass process in the xsltforms stylesheet. >> >> I have to say that once the rendering is completed the performance of the >> form itself is excellent, despite its growing complexity. I assume this is >> due to the presence of a true dependency graph in the newer versions of >> XSLTForms. :) >> >> Thanks for your insights. >> >> Steve Cameron >> >> >> >> >> >> ------------------------------------------------------------------------------ >> Virtualization & Cloud Management Using Capacity Planning >> Cloud computing makes use of virtualization - but cloud computing >> also focuses on allowing computing to be delivered as a service. >> http://www.accelacomm.com/jaw/sfnl/114/51521223/ >> _______________________________________________ >> 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...> - 2012-02-09 14:11:29
|
Hi Stephen, One alternative I might suggest is to use a "multi-tab" form and use a technique called "incremental model loading" if your model is large. Here is a demo of incremental model loading: http://en.wikibooks.org/wiki/XForms/Incremental_Model_Loading here is some sample UI for the tabs: http://en.wikibooks.org/wiki/XForms/Horizontal_File_Tab_Menu The tricky part comes if you have bind rules that span tabs. - Dan On Thu, Feb 9, 2012 at 3:19 AM, Stephen Cameron <ste...@gm...>wrote: > Hello All, > > I have a large xform and its going to get bigger, the time to transform > the xform and render it is now quite significant and getting to the point > where it is an issue, given that people don't see anything happening > throughout the process. > > One option is to pre-transform the xml 'form' into an html 'page', which I > used to do successfully but now cannot using Saxon, it complains. > > But my questions actually relate to browser transformation: > > 1. If I give all of the xform controls an explicit ID, rather than the > xsltforms.xsl stylesheet having to calculate them, does this speed up the > transformation significantly? > > 2. Is it possible perhaps to change the way that the transform occurs such > that the html markup is generated first and then the Xform related > javascript second. In theory the browser should start rendering the page > before the parsing of the Javascript section is completed. I'm imagining > this as a two-pass process in the xsltforms stylesheet. > > I have to say that once the rendering is completed the performance of the > form itself is excellent, despite its growing complexity. I assume this is > due to the presence of a true dependency graph in the newer versions of > XSLTForms. :) > > Thanks for your insights. > > Steve Cameron > > > > > > ------------------------------------------------------------------------------ > Virtualization & Cloud Management Using Capacity Planning > Cloud computing makes use of virtualization - but cloud computing > also focuses on allowing computing to be delivered as a service. > http://www.accelacomm.com/jaw/sfnl/114/51521223/ > _______________________________________________ > 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: Stephen C. <ste...@gm...> - 2012-02-09 09:19:21
|
Hello All, I have a large xform and its going to get bigger, the time to transform the xform and render it is now quite significant and getting to the point where it is an issue, given that people don't see anything happening throughout the process. One option is to pre-transform the xml 'form' into an html 'page', which I used to do successfully but now cannot using Saxon, it complains. But my questions actually relate to browser transformation: 1. If I give all of the xform controls an explicit ID, rather than the xsltforms.xsl stylesheet having to calculate them, does this speed up the transformation significantly? 2. Is it possible perhaps to change the way that the transform occurs such that the html markup is generated first and then the Xform related javascript second. In theory the browser should start rendering the page before the parsing of the Javascript section is completed. I'm imagining this as a two-pass process in the xsltforms stylesheet. I have to say that once the rendering is completed the performance of the form itself is excellent, despite its growing complexity. I assume this is due to the presence of a true dependency graph in the newer versions of XSLTForms. :) Thanks for your insights. Steve Cameron |
|
From: Mark S. <m_s...@ma...> - 2012-02-03 17:59:15
|
Hi, Thanks, Alain, Leigh and Bill for help and suggestions, it is very much appreciated. Alain suggested that I put a nocss instruction in options, which did the trick. So now the form loads in IE9, though it is remarkably slower than in Firefox, Chrome and Safari. Best wishes Mark On 3 Feb 2012, at 13:36, William David Velasquez wrote: > Maybe the proceesing instruction <?xml-stylesheet > href="build/xsltforms.xsl" type="text/xsl"?> has a typo in your xforms. > Some browsers don't need the ? for closing processing instructions, so > they will recognize this: > > <?xml-stylesheet href="build/xsltforms.xsl" type="text/xsl"> without > the ? before > > > as a valid processing instruction. > > Check it. Also make sure you clear the browser cache after changing the > mime types in your server. > > I'll be helpful if you can send a test case here. > > > Bill > > > On 02.02.2012 15:23, Mark Seaborne wrote: >> Hi, >> >> Thanks Alain and William for the tips. >> >> I have now got the XSLT and XHTML served with the MIME type >> application/xml. I have also tried XHTML with the mime type >> application/xhtml+xml. >> >> It hasn't helped though, the transform isn't being executed in IE9. I >> have checked using the F12 tool and the mime types are reported as >> set. >> >> No problems at all with the form in Safari, Firefox or Chrome. >> >> I can't help wondering if I'm missing something else. >> >> Best wishes >> >> Mark >> >> >> On 2 Feb 2012, at 20:03, Alain Couthures wrote: >> >>> Hello Mark, >>> >>> This is probably a mime-type problem because IE is checking them >>> before applying the transformation. >>> >>> With IE9 you can use the F12 debugger to capture network traffic and >>> look at effective mime-types. >>> >>> Depending on your Apache version, there is a mime.types file in the >>> conf directory that should contain this uncommented line: >>> >>> application/xml xml xsl >>> >>> Thank you for your feedbacks! >>> >>> -Alain >>> >>> Le 02/02/2012 09:26, Mark Seaborne a écrit : >>>> Hi, >>>> >>>> I have set up an XSLTForms application on my machine using MAMP as >>>> the host. My XForms works beautifully in every browser I try with the >>>> exception of IE (8& 9). It looks as though the client-side XSLT just >>>> doesn't get called. Can anyone point me at documentation that >>>> explains what I need to do to to get my form to work in IE 8& 9. >>>> Thanks in advance for any advice. >>>> >>>> Mark >>>> >>>> >>>> ------------------------------------------------------------------------------ >>>> Keep Your Developer Skills Current with LearnDevNow! >>>> The most comprehensive online learning library for Microsoft >>>> developers >>>> is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, >>>> MVC3, >>>> Metro Style Apps, more. Free future releases when you subscribe >>>> now! >>>> http://p.sf.net/sfu/learndevnow-d2d >>>> _______________________________________________ >>>> Xsltforms-support mailing list >>>> Xsl...@li... >>>> https://lists.sourceforge.net/lists/listinfo/xsltforms-support >>>> >>> >>> >> >> >> >> ------------------------------------------------------------------------------ >> Keep Your Developer Skills Current with LearnDevNow! >> The most comprehensive online learning library for Microsoft >> developers >> is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, >> MVC3, >> Metro Style Apps, more. Free future releases when you subscribe now! >> http://p.sf.net/sfu/learndevnow-d2d >> _______________________________________________ >> Xsltforms-support mailing list >> Xsl...@li... >> https://lists.sourceforge.net/lists/listinfo/xsltforms-support > > -- > William David Velasquez > Laboratorio de Software Bitlab > http://bitlab.com.co > Movil 310 412 0218 > > ------------------------------------------------------------------------------ > Try before you buy = See our experts in action! > The most comprehensive online learning library for Microsoft developers > is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, > Metro Style Apps, more. Free future releases when you subscribe now! > http://p.sf.net/sfu/learndevnow-dev2 > _______________________________________________ > Xsltforms-support mailing list > Xsl...@li... > https://lists.sourceforge.net/lists/listinfo/xsltforms-support |
|
From: William D. V. <wi...@bi...> - 2012-02-03 13:36:12
|
Maybe the proceesing instruction <?xml-stylesheet href="build/xsltforms.xsl" type="text/xsl"?> has a typo in your xforms. Some browsers don't need the ? for closing processing instructions, so they will recognize this: <?xml-stylesheet href="build/xsltforms.xsl" type="text/xsl"> without the ? before > as a valid processing instruction. Check it. Also make sure you clear the browser cache after changing the mime types in your server. I'll be helpful if you can send a test case here. Bill On 02.02.2012 15:23, Mark Seaborne wrote: > Hi, > > Thanks Alain and William for the tips. > > I have now got the XSLT and XHTML served with the MIME type > application/xml. I have also tried XHTML with the mime type > application/xhtml+xml. > > It hasn't helped though, the transform isn't being executed in IE9. I > have checked using the F12 tool and the mime types are reported as > set. > > No problems at all with the form in Safari, Firefox or Chrome. > > I can't help wondering if I'm missing something else. > > Best wishes > > Mark > > > On 2 Feb 2012, at 20:03, Alain Couthures wrote: > >> Hello Mark, >> >> This is probably a mime-type problem because IE is checking them >> before applying the transformation. >> >> With IE9 you can use the F12 debugger to capture network traffic and >> look at effective mime-types. >> >> Depending on your Apache version, there is a mime.types file in the >> conf directory that should contain this uncommented line: >> >> application/xml xml xsl >> >> Thank you for your feedbacks! >> >> -Alain >> >> Le 02/02/2012 09:26, Mark Seaborne a écrit : >>> Hi, >>> >>> I have set up an XSLTForms application on my machine using MAMP as >>> the host. My XForms works beautifully in every browser I try with the >>> exception of IE (8& 9). It looks as though the client-side XSLT just >>> doesn't get called. Can anyone point me at documentation that >>> explains what I need to do to to get my form to work in IE 8& 9. >>> Thanks in advance for any advice. >>> >>> Mark >>> >>> >>> ------------------------------------------------------------------------------ >>> Keep Your Developer Skills Current with LearnDevNow! >>> The most comprehensive online learning library for Microsoft >>> developers >>> is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, >>> MVC3, >>> Metro Style Apps, more. Free future releases when you subscribe >>> now! >>> http://p.sf.net/sfu/learndevnow-d2d >>> _______________________________________________ >>> Xsltforms-support mailing list >>> Xsl...@li... >>> https://lists.sourceforge.net/lists/listinfo/xsltforms-support >>> >> >> > > > > ------------------------------------------------------------------------------ > Keep Your Developer Skills Current with LearnDevNow! > The most comprehensive online learning library for Microsoft > developers > is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, > MVC3, > Metro Style Apps, more. Free future releases when you subscribe now! > http://p.sf.net/sfu/learndevnow-d2d > _______________________________________________ > Xsltforms-support mailing list > Xsl...@li... > https://lists.sourceforge.net/lists/listinfo/xsltforms-support -- William David Velasquez Laboratorio de Software Bitlab http://bitlab.com.co Movil 310 412 0218 |
|
From: Leigh L K. Jr <lei...@xe...> - 2012-02-02 23:51:06
|
Mark, Try this one: http://xformstest.org/klotz/2011/08/pizza/pizza.xml It works for me in IE8. It's using xsltforms-522. Leigh. On 02/02/2012 12:23 PM, Mark Seaborne wrote: > > Hi, > > Thanks Alain and William for the tips. > > I have now got the XSLT and XHTML served with the MIME type > application/xml. I have also tried XHTML with the mime type > application/xhtml+xml. > > It hasn't helped though, the transform isn't being executed in IE9. I > have checked using the F12 tool and the mime types are reported as set. > > No problems at all with the form in Safari, Firefox or Chrome. > > I can't help wondering if I'm missing something else. > > Best wishes > > Mark > > > On 2 Feb 2012, at 20:03, Alain Couthures wrote: > > > Hello Mark, > > > > This is probably a mime-type problem because IE is checking them > before applying the transformation. > > > > With IE9 you can use the F12 debugger to capture network traffic and > look at effective mime-types. > > > > Depending on your Apache version, there is a mime.types file in the > conf directory that should contain this uncommented line: > > > > > application/xml xml xsl > > > > Thank you for your feedbacks! > > > > -Alain > > > > Le 02/02/2012 09:26, Mark Seaborne a écrit : > >> Hi, > >> > >> I have set up an XSLTForms application on my machine using MAMP as > the host. My XForms works beautifully in every browser I try with the > exception of IE (8& 9). It looks as though the client-side XSLT just > doesn't get called. Can anyone point me at documentation that explains > what I need to do to to get my form to work in IE 8& 9. Thanks in > advance for any advice. > > >> > >> Mark > >> > >> > ------------------------------------------------------------------------------ > >> Keep Your Developer Skills Current with LearnDevNow! > >> The most comprehensive online learning library for Microsoft > developers > >> is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, > MVC3, > >> Metro Style Apps, more. Free future releases when you subscribe now! > >> http://p.sf.net/sfu/learndevnow-d2d > >> _______________________________________________ > >> Xsltforms-support mailing list > >> Xsl...@li... > >> https://lists.sourceforge.net/lists/listinfo/xsltforms-support > >> > > > > > > > ------------------------------------------------------------------------------ > > Keep Your Developer Skills Current with LearnDevNow! > The most comprehensive online learning library for Microsoft developers > is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, > Metro Style Apps, more. Free future releases when you subscribe now! > http://p.sf.net/sfu/learndevnow-d2d > _______________________________________________ > Xsltforms-support mailing list > Xsl...@li... > https://lists.sourceforge.net/lists/listinfo/xsltforms-support > |
|
From: Mark S. <m_s...@ma...> - 2012-02-02 20:23:26
|
Hi, Thanks Alain and William for the tips. I have now got the XSLT and XHTML served with the MIME type application/xml. I have also tried XHTML with the mime type application/xhtml+xml. It hasn't helped though, the transform isn't being executed in IE9. I have checked using the F12 tool and the mime types are reported as set. No problems at all with the form in Safari, Firefox or Chrome. I can't help wondering if I'm missing something else. Best wishes Mark On 2 Feb 2012, at 20:03, Alain Couthures wrote: > Hello Mark, > > This is probably a mime-type problem because IE is checking them before applying the transformation. > > With IE9 you can use the F12 debugger to capture network traffic and look at effective mime-types. > > Depending on your Apache version, there is a mime.types file in the conf directory that should contain this uncommented line: > > application/xml xml xsl > > Thank you for your feedbacks! > > -Alain > > Le 02/02/2012 09:26, Mark Seaborne a écrit : >> Hi, >> >> I have set up an XSLTForms application on my machine using MAMP as the host. My XForms works beautifully in every browser I try with the exception of IE (8& 9). It looks as though the client-side XSLT just doesn't get called. Can anyone point me at documentation that explains what I need to do to to get my form to work in IE 8& 9. Thanks in advance for any advice. >> >> Mark >> >> ------------------------------------------------------------------------------ >> Keep Your Developer Skills Current with LearnDevNow! >> The most comprehensive online learning library for Microsoft developers >> is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, >> Metro Style Apps, more. Free future releases when you subscribe now! >> http://p.sf.net/sfu/learndevnow-d2d >> _______________________________________________ >> Xsltforms-support mailing list >> Xsl...@li... >> https://lists.sourceforge.net/lists/listinfo/xsltforms-support >> > > |
97 messages has been excluded from this view by a project administrator.
