xsltforms-support — XSLTForms support list

Re: [Xsltforms-support] Cyrillic symbols in serialize

[Alain C. <ala...@ag...>]

Hi Alex,

The serialize function is performed by an XSLT transformation and 
entities are valid in this context... But I understand that entities are 
are not human readable.

I tested with IE9 and latest versions of FireFox, Opera and Chrome for 
Windows and they all rendered Cyrillic symbols, not entities.

What browser are you testing with?

Thanks!

-Alain


Le 10/09/2012 12:02, ale...@gm... a écrit :
> When i'm trying to serialize instance containing cyrillic characters
>         <pre><xf:output 
> value="serialize(instance('mainInstance'))"></xf:output></pre>
> i get them escaped like this.
>
>     <group name="&#1055;&#1072;&#1089;&#1087;&#1086;&#1088;&#1090;">
>             <parameter id="current_Code"
>                 name="&#1050;&#1086;&#1076;
>     &#1087;&#1072;&#1094;&#1080;&#1077;&#1085;&#1090;&#1072;"
>                 type="" value="&#1041;&#1040;&#1042;23101983"/>
>         </group>
>
>
> Can i prevent this?
>
> My page encoding is utf-8.

[Xsltforms-support] XForms course November 2012 in Rockville, Maryland

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

[Subscribers to this list may be interested in the XForms course
mentioned below; XSLTforms will be used in the training course.
Apologies to those who see multiple copies of this announcement.]

Black Mesa Technologies is pleased to announce two hands-on
introductory courses, one on XForms and one on XQuery, to take place
in November 2012, in Rockville, Maryland.


INTRODUCTION TO XFORMS FOR XML USERS

  8-9 November 2012, 9:30 - 5:30
  http://www.blackmesatech.com/2012/11/xforms/

  XForms allows you to develop vocabulary- and task-specific editors
  which require less training and provide better task-specific
  support than full XML editors; domain experts can thus examine and
  modify XML encoding mor easily, and routine tasks can be performed
  more quickly and reliably.

  This course introduces XForms as a technology for building
  special-purpose XML editors with focused functionality and
  correspondingly simple user interfaces. XForms is built on the
  model / view / controller idiom, in which the 'model' is a set of
  XML documents, the 'view' is specified using XHTML and XForms
  widgets, and the 'controller' takes the form of declarative links
  between widgets and elements or attributes in the XML documents.


XQUERY FOR DOCUMENTS

  13-14 November 2012, 9:30 - 5:30
  http://www.blackmesatech.com/2012/11/xquery/

  This course introduces XQuery as a flexible language for working
  with natural-language documents (books, prose, verse, drama,
  correspondence, historical documents, articles, legislation, etc.)
  encoded in XML. The focus is on the application of XQuery to
  textual material with complex and variable structure, as opposed to
  the typically simpler, more regular structures of data-oriented
  XML.  The course will cover XPath location paths, atomic values,
  sequences of values, the XDM data model, FLWOR expressions,
  function declarations, regular expressions and string manipulation,
  collections, and the full-text extensions to XQuery.


LOGISTICS

The courses will be held on the dates indicated, from 9:30 a.m. to
5:30 p.m. at

  Mulberry Technologies, Inc.
  17 West Jefferson St., Suite 207
  Rockville, MD 20850

For other logistical information, see 

   http://www.blackmesatech.com/2012/11/xforms
   http://www.blackmesatech.com/2012/11/xquery

Thanks to Mulberry Technologies for hosting the courses.


REGISTRATION / INFO

To reserve a space, to register, or to ask for more information,
please send email to in...@bl... or call us at
505/747-4224.


FUTURE ANNOUNCEMENTS

[If you'd like to receive announcements of future courses (etc.) by
email, go to http://lists.blackmesatech.com/blackmesatech-announce-l/
to sign up for the Black Mesa Technologies announcement list.]


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

[Xsltforms-support] Cyrillic symbols in serialize

[<ale...@gm...>]

When i'm trying to serialize instance containing cyrillic characters
        <pre><xf:output
value="serialize(instance('mainInstance'))"></xf:output></pre>
i get them escaped like this.

    <group name="&#1055;&#1072;&#1089;&#1087;&#1086;&#1088;&#1090;">
>         <parameter id="current_Code"
>             name="&#1050;&#1086;&#1076;
> &#1087;&#1072;&#1094;&#1080;&#1077;&#1085;&#1090;&#1072;"
>             type="" value="&#1041;&#1040;&#1042;23101983"/>
>     </group>
>

Can i prevent this?

My page encoding is utf-8.

[Xsltforms-support] Force checkbox readonly

[Javier D. <jd...@tc...>]

Hello,

We are trying to set a checkbox readonly but it only gets shadowed, but
it can still be checked.

We have done this change in javascript:

 XsltForms_input.prototype.changeReadonly = function() {
+       var node = this.element.node;
+       var type = node ?
XsltForms_schema.getType(XsltForms_browser.getType(node) ||
"xsd_:string") : XsltForms_schema.getType("xsd_:string");
+
        if (this.input) {
+               if (type["class"] === "boolean") {
+                   this.input.disabled = this.readonly;
+               }
+
                this.input.readOnly = this.readonly;
                if (this.calendarButton) {
                        this.calendarButton.style.display =
this.readonly ? "none" : "";


So the checkbox is readonly, althought it isn't sent when submit (it
isn't a problem for me).

¿Do you know a better way of forcing it?















************************************************************************************************************************************************
*La información contenida en este mensaje de correo electrónico es confidencial y puede revestir el carácter de reservada.   *
*Está dirigida exclusivamente a la persona destinataria.                                                                                                   *
*El acceso o cualquier uso por parte de cualquier otra persona de este mensaje no están autorizados y pueden ser ilegales.*
*Si no es Ud. la persona destinataria, le rogamos que proceda a borrarlo.                                                                          *
*The information in this e-mail is confidential and may be legally privileged.                                                                        *
*It is intended solely for the addressee.                                                                                                                           *
*Access or any use by any other person to this Internet e-mail is not authorised and may be unlawful.                                 *
*If you are not the intended recipient, please delete this e-mail.                                                                                         *
************************************************************************************************************************************************
 

Re: [Xsltforms-support] Weird behavior with xf:repeat and HTML table headers

[Florent G. <li...@fg...>]

Alain Couthures wrote:


  Hi Alain,
> This is a known limitation for XSLTForms with TABLE.
> The workaround is to explicitly add THEAD and TBODY elements:


  Good enough for me.  Thanks for your quick response!
 
-- 
Florent Georges
http://fgeorges.org/
http://h2oconsulting.be/

Re: [Xsltforms-support] Weird behavior with xf:repeat and HTML table headers

[Alain C. <ala...@ag...>]

Hi Florent,

This is a known limitation for XSLTForms with TABLE.

The workaround is to explicitly add THEAD and TBODY elements:

     <table>
         <thead>
             <tr>
                 <th>Thing</th>
             </tr>
         </thead>
         <tbody>
             <xf:repeat nodeset="/things/*">
                 <tr>
                     <td>
                         <xf:output ref="."/>
                     </td>
                 </tr>
             </xf:repeat>
         </tbody>
     </table>


Thank you for your feedbacks!

-Alain
>    Hi,
>
>    With the example at the end of this email, I expect to get something
> like the following in the browser:
>
>      Thing
>      Un
>      Deux
>      Trois
>      Quatre
>
> but I get instead the following:
>
>      Thing
>      Deux
>      Thing
>      Thing
>
>    That is, the table header line replaces all regular lines, except
> the second one (and see, there is not 1 + 4 lines, but only 4).  I've
> tested it with both Chrome and Safari on Mac OS X 10.6.8.  The
> stylehseet xsltforms.xsl says:
>
>      <dcterms:hasVersion>1.0RC</dcterms:hasVersion>
>      <dcterms:created>2012-03-18</dcterms:created>
>
>    I have no idea how to debug any farther.  Any idea?
>
>    Regards,
>
> -- 
> Florent Georges
> http://fgeorges.org/
> http://h2oconsulting.be/
>
>
> <?xml-stylesheet href="xsltforms/xsltforms.xsl" type="text/xsl"?>
> <htmlxmlns:xf="http://www.w3.org/2002/xforms">
>     <head>
>        <title>Test</title>
>        <xf:model>
>           <xf:instanceid="docs">
>              <thingsxmlns="">
>                 <thing>Un</thing>
>                 <thing>Deux</thing>
>                 <thing>Trois</thing>
>                 <thing>Quatre</thing>
>              </things>
>           </xf:instance>
>        </xf:model>
>     </head>
>     <body>
>        <table>
>           <tr>
>              <th>Thing</th>
>           </tr>
>           <xf:repeatnodeset="/things/*">
>              <tr>
>                 <td>
>                    <xf:outputref="."/>
>                 </td>
>              </tr>
>           </xf:repeat>
>        </table>
>     </body>
> </html>
>
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> Xsltforms-support mailing list
> Xsl...@li...
> https://lists.sourceforge.net/lists/listinfo/xsltforms-support
>

[Xsltforms-support] Weird behavior with xf:repeat and HTML table headers

[Florent G. <li...@fg...>]

  Hi,

  With the example at the end of this email, I expect to get something
like the following in the browser:

    Thing
    Un
    Deux
    Trois
    Quatre

but I get instead the following:

    Thing
    Deux
    Thing
    Thing

  That is, the table header line replaces all regular lines, except
the second one (and see, there is not 1 + 4 lines, but only 4).  I've
tested it with both Chrome and Safari on Mac OS X 10.6.8.  The
stylehseet xsltforms.xsl says:

    <dcterms:hasVersion>1.0RC</dcterms:hasVersion>
    <dcterms:created>2012-03-18</dcterms:created>

  I have no idea how to debug any farther.  Any idea?

  Regards,

-- 
Florent Georges
http://fgeorges.org/
http://h2oconsulting.be/


<?xml-stylesheet href="xsltforms/xsltforms.xsl" type="text/xsl"?>
<htmlxmlns:xf="http://www.w3.org/2002/xforms">
   <head>
      <title>Test</title>
      <xf:model>
         <xf:instanceid="docs">
            <thingsxmlns="">
               <thing>Un</thing>
               <thing>Deux</thing>
               <thing>Trois</thing>
               <thing>Quatre</thing>
            </things>
         </xf:instance>
      </xf:model>
   </head>
   <body>
      <table>
         <tr>
            <th>Thing</th>
         </tr>
         <xf:repeatnodeset="/things/*">
            <tr>
               <td>
                  <xf:outputref="."/>
               </td>
            </tr>
         </xf:repeat>
      </table>
   </body>
</html>

Re: [Xsltforms-support] JSON bug

[Alain C. <ala...@ag...>]

Hi Steve,

I have updated the Wikipedia OpenSearch example for the latest build: 
http://www.agencexml.com/xsltforms/wikipediasearch.xml

I fixed the same bug but I think it is better to keep a short name for 
the callback function so it is back from "XsltForms_browser.jsoninst" to 
"jsoninst".

Comparing to the old version of this example, @mediatype="text/jsonp" is 
now mandatory for the submission. The generated XML structure for the 
JSON response is defining elements with different names so "*" is to be 
used in XPath expressions instead of "item".

This is still an experimental feature because the XForms 2.0 
Specifications are not yet fully detailed about serialization in XML and 
mediatype.

Thank you for your feedbacks!

-Alain

Le 23/08/2012 03:09, Stephen Cameron a écrit :
> Hi Alain,
>
> There is a simple bug in revision 556 regarding JSONP support
>
> from line 3885
>         if (this.mediatype === "text/jsonp") {
>             XsltForms_browser.jsoninstobj = !instance ? (node ? 
> document.getElementById(XsltForms_browser.getMeta(node.documentElement 
> ? node.documentElement : node.ownerDocument.documentElement, 
> "instance")).xfElement : this.model.getInstance()) : 
> document.getElementById(instance).xfElement;
>             var scriptelt = XsltForms_browser.isXhtml ? 
> document.createElementNS("http://www.w3.org/1999/xhtml", "script") : 
> document.createElement("script");
> <<         scriptelt.setAttribute("src", action.replace(/&amp;/g, 
> "&")+((action.indexOf("?") === -1) ? "?" : "&")+"callback=jsoninst");
> >>         scriptelt.setAttribute("src", action.replace(/&amp;/g, 
> "&")+((action.indexOf("?") === -1) ? "?" : 
> "&")+"callback=XsltForms_browser.jsoninst");
>             scriptelt.setAttribute("id", "jsoninst");
>             scriptelt.setAttribute("type", "text/javascript");
>             body = XsltForms_browser.isXhtml ? 
> document.getElementsByTagNameNS("http://www.w3.org/1999/xhtml", 
> "body")[0] : document.getElementsByTagName("body")[0];
>             body.insertBefore(scriptelt, body.firstChild);
>             XsltForms_xmlevents.dispatch(this, "xforms-submit-done");
>             XsltForms_globals.closeAction();
>         } else {
>
> The ALA web service does support JSONP once you know what it does its 
> quite neat!
>
> Regards
> Steve

[Xsltforms-support] JSON bug

[Stephen C. <ste...@gm...>]

Hi Alain,

There is a simple bug in revision 556 regarding JSONP support

from line 3885
        if (this.mediatype === "text/jsonp") {
            XsltForms_browser.jsoninstobj = !instance ? (node ?
document.getElementById(XsltForms_browser.getMeta(node.documentElement ?
node.documentElement : node.ownerDocument.documentElement,
"instance")).xfElement : this.model.getInstance()) :
document.getElementById(instance).xfElement;
            var scriptelt = XsltForms_browser.isXhtml ?
document.createElementNS("http://www.w3.org/1999/xhtml", "script") :
document.createElement("script");
<<         scriptelt.setAttribute("src", action.replace(/&amp;/g,
"&")+((action.indexOf("?") === -1) ? "?" : "&")+"callback=jsoninst");
>>         scriptelt.setAttribute("src", action.replace(/&amp;/g,
"&")+((action.indexOf("?") === -1) ? "?" :
"&")+"callback=XsltForms_browser.jsoninst");
            scriptelt.setAttribute("id", "jsoninst");
            scriptelt.setAttribute("type", "text/javascript");
            body = XsltForms_browser.isXhtml ?
document.getElementsByTagNameNS("http://www.w3.org/1999/xhtml", "body")[0]
: document.getElementsByTagName("body")[0];
            body.insertBefore(scriptelt, body.firstChild);
            XsltForms_xmlevents.dispatch(this, "xforms-submit-done");
            XsltForms_globals.closeAction();
        } else {

The ALA web service does support JSONP once you know what it does its quite
neat!

Regards
Steve

[Xsltforms-support] autocomplete demo error

[Stephen C. <ste...@gm...>]

Hi

I'm trying to build an XForm autocomplete demo working with a JSON service,
I'm getting an submit error when asking the service for matches.

This is strange as filling the 'results' instance with an initial query is
successful and a list of query matches appears. It only breaks when the
user tries a new text string to get a new set of matches.

I cannot see what I am doing wrong and I copied an online demo that works,
so not sure if it might be a regression?

My version is here:

http://collinta.com.au/xsltforms/ala_incremental_find.xml

Alains working demo I copied is here:

http://www.agencexml.com/jsoncallback/wikipediasearch.xml

I do see a exception being trapped when the xf:submission is sent but don't
know how to progress in debugging that.

Thanks for any ideas

Steve Cameron

[Xsltforms-support] Fwd: cross domain requests

[Stephen C. <ste...@gm...>]

Seems it does work, the problem is in the xf:repeat inside the table.

So cross domain JSON is handled just fine.

---------- Forwarded message ----------
From: Stephen Cameron <ste...@gm...>
Date: Tue, Aug 21, 2012 at 2:13 PM
Subject: cross domain requests
To: xsl...@li...


Hello,

Does anyone have good experience with cross-domain requests?

I'm not sure why the following JSON example only works for me in FF, not ie
IE, Chrome or Safari.

http://collinta.com.au/xsltforms/ala_search.xml

Is it simply a cross-domain security issue?

Thanks for any insight.

Steve Cameron

[Xsltforms-support] cross domain requests

[Stephen C. <ste...@gm...>]

Hello,

Does anyone have good experience with cross-domain requests?

I'm not sure why the following JSON example only works for me in FF, not ie
IE, Chrome or Safari.

http://collinta.com.au/xsltforms/ala_search.xml

Is it simply a cross-domain security issue?

Thanks for any insight.

Steve Cameron

Re: [Xsltforms-support] case element in toggle, exception in last version - possible bug ?

[Alain C. <ala...@ag...>]

Hi Ioan,
> The following example (taken from 
> http://en.wikibooks.org/wiki/XForms/Storing_Tabs_in_the_Model ) worked 
> well in version 533:
>
>  In version555, on loading show next alert:
>
>> XSLTForms Exception
>> --------------------------
>>
>> Error initializing :
>>
>> @http://localhost:8888/xsltforms/xsltforms.js:8887
>> xsltforms_initImpl@http://localhost:8888/probe/tabs-model.xhtml:54
>> xsltforms_init@http://localhost:8888/probe/tabs-model.xhtml:2
>> onload@http://localhost:8888/probe/tabs-model.xhtml:1
>>
>>
>> TypeError
>>
>> target is null
>
> After, also work well, change correct the value of tabs. When is 
> removed de case element from toggle, the message not appear.
The XSLT transformation has been seriously improved for performance in 
recent revisions and the case element was still not correctly supported.

This is now fixed and will be committed as soon as possible.
> Would be possible, instead, to use case as attribute in toggle 
> element, with AVT, in the near future? Or caseref from switch (XForms 
> 2.0)?
AVT is now supported by XSLTForms but just for host language (HTML, SVG) 
attributes.

switch/@caseref is not yet supported and, even though it is interesting, 
it is not currently considered as a priority.

Thanks!

-Alain

[Xsltforms-support] case element in toggle, exception in last version - possible bug ?

[Ioan F. <mi...@gm...>]

Hi,

The following example (taken from 
http://en.wikibooks.org/wiki/XForms/Storing_Tabs_in_the_Model ) worked 
well in version 533:

<?xml version="1.0" encoding="utf-8"?>
<?xml-stylesheet href="../xsltforms/xsltforms.xsl" type="text/xsl"?>

<html xmlns="http://www.w3.org/1999/xhtml"
     xmlns:xf="http://www.w3.org/2002/xforms"
     xmlns:ev="http://www.w3.org/2001/xml-events"
     xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
     xmlns:xs="http://www.w3.org/2001/XMLSchema">
     <head>
         <title>Tabs</title>
         <xf:model id="data-model">
             <xf:instance id="tabset-instance" xmlns="">
                 <tabset value="validate">
                     <item value="create">Create</item>
                     <item value="configure">Configure</item>
                     <item value="validate">Validate</item>
                     <item value="review">Review</item>
                 </tabset>
             </xf:instance>
         </xf:model>
         <style type="text/css"><![CDATA[
body {margin:0.25in; background-color:#d8dcda;}

.xforms-repeat-item  {
     display:inline-block;
     font-size:12pt;
     font-family:Arial;
     text-align:center;
     padding:5px;
     margin-right: 1em;
     border:solid 1px #29768a;
     background-color:#29768a;

     border-radius: .4em .4em 0em 0em;
     margin-bottom: 0px;

     hover.background-color:#f2f0fb;
}

/* this formats the selected tab differently so that you can tell what 
tab you are using */
.xforms-repeat-item-selected {
     border-bottom:solid 5px #f2f0fb;
     background-color:#f2f0fb;
}
.tabframe {
     position:relative;
     }

.tabs {
/*    position:absolute;
     z-index:2; */
     margin-left:15px;
     }

.tabpane {
     width:700px;
     height:400px;
     border:solid 1px #29768a;
     z-index:1;
/*    position:absolute; box-shadow: 7px 7px 8px #818181;*/
     margin-top:-2px;
     padding:10px;


     border-radius:10px;


     background: -webkit-linear-gradient(top, #f2f0fb, #d8dcda);
     background:-moz-linear-gradient(top, #f2f0fb, #d8dcda);
     };
         ]]></style>
    </head>
     <body>
         <div class="tabframe">
         <div class="tabs">
         <xf:repeat nodeset="instance('tabset-instance')/item" 
id="tab-item-repeat">
             <xf:trigger ref="." appearance="minimal">
                 <xf:label><xf:output ref="."/></xf:label>
                 <xf:action ev:event="DOMActivate">
                     <xf:setvalue ref="instance('tabset-instance')/@value"
value="instance('tabset-instance')/item[index('tab-item-repeat')]/@value"/>
                        <xf:toggle ref=".">
                         <xf:case value="@value"/>
                     </xf:toggle>
                 </xf:action>
             </xf:trigger>
         </xf:repeat>
         </div>
         <div class="tabpane">
         <xf:switch>
             <xf:case id="create" selected="true">
                     <h1>Create Transformation Strategy</h1>
                     <p>This is the pane where strategies for 
transformations are designed</p>
             </xf:case>
             <xf:case id="configure">
                     <h1>Configure Strategy Parameters</h1>
                     <p>This sets the parameters necessary for the 
execution of the strategy.</p>
             </xf:case>
             <xf:case id="validate">
                     <h1>Validate Strategy Rules</h1>
                     <p>This sets up tests for determining whether the 
transformation has succeeded or failed.</p>
             </xf:case>
             <xf:case id="review">
                     <h1>Review Strategy</h1>
                     <p>This provides a comprehensive review of the 
states defined within a given strategy.</p>
             </xf:case>
         </xf:switch>
         </div>
         </div>
     </body>
</html>



  In version555, on loading show next alert:

> XSLTForms Exception
> --------------------------
>
> Error initializing :
>
> @http://localhost:8888/xsltforms/xsltforms.js:8887
> xsltforms_initImpl@http://localhost:8888/probe/tabs-model.xhtml:54
> xsltforms_init@http://localhost:8888/probe/tabs-model.xhtml:2
> onload@http://localhost:8888/probe/tabs-model.xhtml:1
>
>
> TypeError
>
> target is null

After, also work well, change correct the value of tabs. When is removed 
de case element from toggle, the message not appear. Would be possible, 
instead, to use case as attribute in toggle element, with AVT, in the 
near future? Or caseref from switch (XForms 2.0)?

With thanks,

Ioan

Re: [Xsltforms-support] rev. 546 seems to have broken TinyMCE support

[Alain C. <ala...@ag...>]

Hi Michael,

> In 546 it fails.
This revision added support for TinyMCE in subforms (there is still a 
bug for that with Firefox only, probably in TinyMCE itself...).

Sorry this broke something in your form. My own examples still work fine...

To fix this, I would need a test case or an online access. Is it possible?

> I don't have a good way to convert the data from <p>paragraphs 
> like this&lt;/p&gt; to <p>paragraphs like this</p> If anyone has 
> solved this problem, I would very much like to hear their solution.
What do you mean exactly by "convert the data"? Did you try 
xf:output/@mediatype= "application/xhtml+xml"?

Thanks!

-Alain

Re: [Xsltforms-support] IE9 subforms access error

[Alain C. <ala...@ag...>]

Hello Jeremy,

Le 13/07/2012 23:50, Jeremy Frier a écrit :
> The problem in IE9 was caused by having compatibility mode turned on.  Unfortunately, this does not correct the problem in IE8.  I'm not sure how to go about fixing the problem in the xsltforms.js as the issue appears to be with the appendChild method on a script element being generated in the XsltForms_load.prototype.run method for the show=embed.
>
> 				var scriptelt = XsltForms_browser.isXhtml ? document.createElementNS("http://www.w3.org/1999/xhtml", "script") : document.createElement("script");
> 				scriptelt.setAttribute("id", "xsltforms-subform-" + XsltForms_globals.nbsubforms + "-script");
> 				scriptelt.setAttribute("type", "text/javascript");
> 				var scripttxt = document.createTextNode(subjs);
> 				scriptelt.appendChild(scripttxt);
>
> I've updated locally xsltforms.js to now be what's shown below and IE8 is working, looking forward to using subforms now:
> 				var scriptelt = XsltForms_browser.isXhtml ? document.createElementNS("http://www.w3.org/1999/xhtml", "script") : document.createElement("script");
> 				scriptelt.setAttribute("id", "xsltforms-subform-" + XsltForms_globals.nbsubforms + "-script");
> 				scriptelt.setAttribute("type", "text/javascript");
> 				if (window.addEventListener) {
> 					/* Firefox, Chrome, IE9 */
> 					scriptelt.appendChild(document.createTextNode(subjs))
> 				} else {
> 					/* IE8 */
> 					scriptelt.text = subjs;
> 				}
>
> If anybody sees an issue with this approach, please let me know as I'm really just trying to get to the point of testing performance to determine if we have to move in a new direction or whether subforms is our answer.
>
>
I already had the same problem with IE<9 and the script embedded XForms 
feature and used the same approach.

This will be included in the next commit.

Thanks!

-Alain

[Xsltforms-support] rev. 546 seems to have broken TinyMCE support

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

Hi, Alain and others interested,

Just a quick report to say that apparently rev. 546 broke something in the
TinyMCE support in XSLTForms.  I regret that I have not had time to try
to see just what the cause is, and I'm unlikely to have time in the next ten
days or so to look more carefully.

I had been hoping to combine the TinyMCE support with the experimental
xf:setnode action implemented in rev.550, to make a form that used the
TinyMCE rich text editor and stored the results not as a string with
escaped XML but as normal XML.

I have not checked all recent versions; I guessed the relevant code was
broken just once, so I did a binary search on versions:  in rev. 535, 
TinyMCE works.

In rev. 549 it doesn't work.

In 542 it works.

In 545 it works.

In 547 it fails.

In 546 it fails.

In each case, it fails with a dialog box saying:

> http://localhost
> 
> XSLTForms Exception
> --------------------------
> 
> Error initializing :
> 
> 
> SyntaxError
> 
> Unexpected EOF

I can use 1.0RC for this form, and so I can use TinyMCE, but I don't 
have a good way to convert the data from

  <p>paragraphs like this</p>

to 

  <p>paragraphs like this</p>  

If anyone has solved this problem, I would very much like to hear
their solution.

Michael Sperberg-McQueen

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

Re: [Xsltforms-support] CSS not applied when using XSLTForms

[Stephen C. <ste...@gm...>]

Hi,

I think that in the past it was recommended to put your  css, or links to
css files, into the <extensions> tag in config.xml.

This was so that they would get inserted into the compiled XForm markup
after the xsltforms.css link and so allow you to override things in that
file.

I had to go back to that after a recent version update.

I'm not sure if this is still a recommendation?

Steve Cameron


On Fri, Aug 3, 2012 at 5:21 AM, Florent Georges <li...@fg...> wrote:

> Conal Tuohy wrote:
>
>   Hi,
>
> > Here's a slightly improved version where an XML parser which
> > evaluates the text content of the css element will also get
> > valid CSS (the previous version had unmatched CSS comment
> > markers):
>
> > <!--/*--><css><![CDATA[/**/
> > [...]
> > /*]]>*/<!--/*--></css><!--*/-->
>
>   Thanks.  I am a bit surprised to have to use such work-around,
> but at least I am now able to use external files instead of
> copying and pasting the CSS into each forms... :-)
>
>   Regards,
>
> --
> Florent Georges
> http://fgeorges.org/
> http://h2oconsulting.be/
>
>
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
> _______________________________________________
> Xsltforms-support mailing list
> Xsl...@li...
> https://lists.sourceforge.net/lists/listinfo/xsltforms-support
>

[Xsltforms-support] xf:upload: selecting multiple files

[Florent G. <li...@fg...>]

  Hi,

  I would like to write an upload form.  It should be able to
load several files.  Is it possible to select all the files in a
directory? (e.g. by holding the shift key in the file selector
dialog box)

  Regards,
 
-- 
Florent Georges
http://fgeorges.org/
http://h2oconsulting.be/

Re: [Xsltforms-support] CSS not applied when using XSLTForms

[Florent G. <li...@fg...>]

Dan McCreary wrote:

  Hi Dan,

> http://en.wikibooks.org/wiki/XRX/XSLTForms_and_eXist#Modifying_your_CSS_to_work_with_XSLTForms

  Thanks for the link.  And thanks for the XForms wikibook, it is
very useful! (btw, shouldn't that tip be in the XForms book?)

  Regards,

-- 
Florent Georges
http://fgeorges.org/
http://h2oconsulting.be/

Re: [Xsltforms-support] CSS not applied when using XSLTForms

[Florent G. <li...@fg...>]

Conal Tuohy wrote:

  Hi,

> Here's a slightly improved version where an XML parser which
> evaluates the text content of the css element will also get
> valid CSS (the previous version had unmatched CSS comment
> markers):

> <!--/*--><css><![CDATA[/**/
> [...]
> /*]]>*/<!--/*--></css><!--*/-->

  Thanks.  I am a bit surprised to have to use such work-around,
but at least I am now able to use external files instead of
copying and pasting the CSS into each forms... :-)

  Regards,

-- 
Florent Georges
http://fgeorges.org/
http://h2oconsulting.be/

Re: [Xsltforms-support] CSS not applied when using XSLTForms

[Conal T. <con...@ve...>]

On 28/07/12 01:18, C. M. Sperberg-McQueen wrote:
> On Jul 26, 2012, at 9:19 PM, Conal Tuohy wrote:
>
>> It's convenient, if you have to author CSS documents in a well-formed XML file, to be able to retain CSS validity.
> My thoughts exactly.
>
>> In order to hide CSS from HTML 3 user agents, the CSS grammar allows SGML comment delimiters, which it ignores. So with a bit of finagling you can write polyglot xml/css using just a tricky prolog and epilog, e.g.
>>
>> <!--/*--><css><![CDATA[*/
>>
>> /* Plain old css goes in here, & and < are all good */
>>
>> h1 {
>>      color: green;
>> }
>>
>> /*]]></css><!--*/-->
> That is one of the most ingenious, twisted, sick and brilliant hacks I've
> seen in a while.  Thank you for that!

Thanks Michael! :-)

Here's a slightly improved version where an XML parser which evaluates 
the text content of the css element will also get valid CSS (the 
previous version had unmatched CSS comment markers):

<!--/*--><css><![CDATA[/**/

/* Plain old css goes in here, & and < are all good */

h1 {
     color: green;
}

/*]]>*/<!--/*--></css><!--*/-->


-- 
Conal Tuohy
eResearch Business Analyst
Victorian eResearch Strategic Initiative
+61-466324297

Re: [Xsltforms-support] CSS not applied when using XSLTForms

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

On Jul 26, 2012, at 9:19 PM, Conal Tuohy wrote:

> It's convenient, if you have to author CSS documents in a well-formed XML file, to be able to retain CSS validity. 

My thoughts exactly.

> In order to hide CSS from HTML 3 user agents, the CSS grammar allows SGML comment delimiters, which it ignores. So with a bit of finagling you can write polyglot xml/css using just a tricky prolog and epilog, e.g.
> 
> <!--/*--><css><![CDATA[*/
> 
> /* Plain old css goes in here, & and < are all good */
> 
> h1 {
>     color: green;
> }
> 
> /*]]></css><!--*/-->

That is one of the most ingenious, twisted, sick and brilliant hacks I've
seen in a while.  Thank you for that!

Michael

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

Re: [Xsltforms-support] CSS not applied when using XSLTForms

[Conal T. <con...@ve...>]

It's convenient, if you have to author CSS documents in a well-formed 
XML file, to be able to retain CSS validity.

In order to hide CSS from HTML 3 user agents, the CSS grammar allows 
SGML comment delimiters, which it ignores. So with a bit of finagling 
you can write polyglot xml/css using just a tricky prolog and epilog, e.g.

<!--/*--><css><![CDATA[*/

/* Plain old css goes in here, & and < are all good */

h1 {
     color: green;
}

/*]]></css><!--*/-->


On 26/07/12 22:57, Dan McCreary wrote:
> Hi Florent,
>
> You may have to wrap the CSS files in XML tags like <css>...</css>.
>
> http://en.wikibooks.org/wiki/XRX/XSLTForms_and_eXist#Modifying_your_CSS_to_work_with_XSLTForms 
>
>
> - Dan
>
> On Thu, Jul 26, 2012 at 7:10 AM, Florent Georges <li...@fg... 
> <mailto:li...@fg...>> wrote:
>
>       Hi,
>
>       When I add XSLTForms support to my page, it does not apply my
>     CSS files anymore.  Those are imported by:
>
>         <link href="xxx.css" rel="stylesheet" type="text/css"/>
>
>       XSLTForms is plugged in by:
>
>         <?xml-stylesheet href="xsltforms.xsl" type="text/xsl"?>
>
>       XSLTForms works fine.  If I remove the processing instruction
>     to import it, the CSS is correctly apply.  But with XSLTForms,
>     it is not anymore.
>
>       Any reason for this?  Any solution?
>
>
>       Regards,
>
>
>     --
>     Florent Georges
>     http://fgeorges.org/
>     http://h2oconsulting.be/
>
>     ------------------------------------------------------------------------------
>     Live Security Virtual Conference
>     Exclusive live event will cover all the ways today's security and
>     threat landscape has changed and how IT managers can respond.
>     Discussions
>     will include endpoint security, mobile security and the latest in
>     malware
>     threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
>     _______________________________________________
>     Xsltforms-support mailing list
>     Xsl...@li...
>     <mailto:Xsl...@li...>
>     https://lists.sourceforge.net/lists/listinfo/xsltforms-support
>
>
>
>
> -- 
> Dan McCreary
> NoSQL Evangelist
> office: (952) 931-9198
> cell: (612) 986-1552
>
>
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
>
>
> _______________________________________________
> Xsltforms-support mailing list
> Xsl...@li...
> https://lists.sourceforge.net/lists/listinfo/xsltforms-support


-- 
Conal Tuohy
eResearch Business Analyst
Victorian eResearch Strategic Initiative
+61-466324297

Re: [Xsltforms-support] CSS not applied when using XSLTForms

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

On Jul 26, 2012, at 6:10 AM, Florent Georges wrote:

>   Hi,
> 
>   When I add XSLTForms support to my page, it does not apply my
> CSS files anymore.  Those are imported by:
> 
>     <link href="xxx.css" rel="stylesheet" type="text/css"/>
> 
>   XSLTForms is plugged in by:
> 
>     <?xml-stylesheet href="xsltforms.xsl" type="text/xsl"?>
> 
>   XSLTForms works fine.  If I remove the processing instruction
> to import it, the CSS is correctly apply.  But with XSLTForms,
> it is not anymore.
> 
>   Any reason for this?  Any solution?


I ran into this recently, too. (I.e. no, you're not imagining it.)
It seems to vary by version; see the test cases at 

  http://blackmesatech.com/2012/07/testcase/css-in-xsltforms.xhtml

The summary appears to be:  1.0RC loads external CSS
in the same way as beta3 and beta3RC before it, while
rev. 549 requires (as Dan McCreary has already suggested)
that the external files be wrapped in XML.

It may be relevant, of course, that none of the CSS files 
used in this test actually require pre-processing: they don't
do anything with the XForms namespace.

I am hoping that this is just a temporary glitch and that the
behavior will revert to the older pattern soon.

Michael


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