xsltforms-support — XSLTForms support list

Re: [Xsltforms-support] Fwd: SVG and XForms

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

Hello Jens,
> Do you see why <http://www.agencexml.com/xsltforms/flags.xml> gives an error with WebKit browsers?
>
>
Thank you for pointing at this exception.

It is due to the processing of the xf:include statement (which is an 
extension...): the document node of the included document is considered 
for templates. Apparently, WebKit browsers don't treat parameters the 
same way as others do in this situation.

Actually, it is good to directly consider the document element instead.

The corresponding fix will be committed as soon as possible.

Best,

-Alain

[Xsltforms-support] Fwd: SVG and XForms

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

Dear Alain,

Do you see why <http://www.agencexml.com/xsltforms/flags.xml> gives an error with WebKit browsers?

Best,

Jens

Begin forwarded message:

> From: Alain Couthures <ala...@ag...>
> Subject: [Xsltforms-support] SVG and XForms
> Date: April 2, 2012 11:31:03 PM GMT+02:00
> To: pub...@w3..., XSLTForms support <xsl...@li...>
> 
> Hello,
> 
> I have recently embedded XForms controls within SVG images to 
> dynamically render data.
> 
> For chart axes, I needed a repeat group based on numbers not on nodes so 
> I added an extension to XSLTForms: repeat/@from, repeat/@to and 
> repeat/@step. The loop index can be obtained with the "." XPath 
> expression so the context is not in any model and the instance() 
> function has always to be used when referring to nodes.
> 
> For pie charts, I needed trigonometric functions, which are only 
> available in XPath 3.0, but are already supported by XSLTForms.
> 
> For performance, I used an intermediate instance with calculated 
> bindings. I might have implemented the new 'var' element but initially 
> get confused with the 2.0 specs whether vars were limited to function 
> bodies or not.
> 
> AVT support is, of course, very important for SVG but I also used output 
> controls within text elements. I am not sure that labels in XForms group 
> controls can easily be rendered in SVG.
> 
> Here are some online examples: 
> http://www.agencexml.com/xsltforms/flags.xml, 
> http://www.agencexml.com/xsltforms/piechart.xml, 
> http://www.agencexml.com/xsltforms/gauges.xml and 
> http://www.agencexml.com/xsltforms/gantt.xml.
> 
> I would be happy to have your opinions about SVG and XForms.
> 
> Thanks!
> 
> -Alain
> 
> ------------------------------------------------------------------------------
> Better than sec? Nothing is better than sec when it comes to
> monitoring Big Data applications. Try Boundary one-second 
> resolution app monitoring today. Free.
> http://p.sf.net/sfu/Boundary-dev2dev
> _______________________________________________
> Xsltforms-support mailing list
> Xsl...@li...
> https://lists.sourceforge.net/lists/listinfo/xsltforms-support

[Xsltforms-support] prototype generic web XML editor via XLSTForms

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

Hello,

You might be interested to see a prototype generic browser based XML Editor
built using XSLTForms.

Its dependant on the transform XPath function.

http://forms.collinta.com.au/xml_edit.xml

It has an issue in IE presently, I should be doing other things so will
look at that later.

All the best for 2013.

Regards
Steve Cameron

Re: [Xsltforms-support] How to put a xf:hint within an xf:output text

[Elias M. <eli...@gm...>]

HI Alain.

Thanks for the quick reply.  That sounds good.  I actually had the xf:hint
within the output as straight text and it did work, but as you mentioned,
it eventually went away.

Thanks for fixing it.
Elias

On Thu, Dec 27, 2012 at 4:06 PM, Alain Couthures <
ala...@ag...> wrote:

> Hi Elias,
>
>  I would like the header of the table to show the label and description
>> from the instance.  I tried:
>>
>> <table>
>> <tr>
>> <th>
>>      <xf:output value="instance('labels')/Codes[Code = 'BCODE']/Name"/>
>>         <xf:hint><xf:output value="instance('labels')/Codes[Code =
>> 'BCODE']/Desc"/></xf:hint>
>>      </xf:output>
>> </th>
>> ..
>> ..
>> but it doesn't work.  Any suggestions??
>>
> I decided to ignore xf:alert for xf:output because an error due to an
> input field should not be propagated to all output controls using it. And
> xf:hint started to be ignored too...
>
> But I agree that xf:hint and xf:help might still be useful for xf:output
> controls.
>
> The XSLT template named "field" has to be modified to limit the
> restriction for xf:output to xf:alert only. I will commit this as soon as
> possible.
>
> Thanks!
>
> -Alain
>
>

Re: [Xsltforms-support] How to put a xf:hint within an xf:output text

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

Hi Elias,
> I would like the header of the table to show the label and description 
> from the instance.  I tried:
>
> <table>
> <tr>
> <th>
>      <xf:output value="instance('labels')/Codes[Code = 'BCODE']/Name"/>
>         <xf:hint><xf:output value="instance('labels')/Codes[Code = 
> 'BCODE']/Desc"/></xf:hint>
>      </xf:output>
> </th>
> ..
> ..
> but it doesn't work.  Any suggestions??
I decided to ignore xf:alert for xf:output because an error due to an 
input field should not be propagated to all output controls using it. 
And xf:hint started to be ignored too...

But I agree that xf:hint and xf:help might still be useful for xf:output 
controls.

The XSLT template named "field" has to be modified to limit the 
restriction for xf:output to xf:alert only. I will commit this as soon 
as possible.

Thanks!

-Alain

[Xsltforms-support] How to put a xf:hint within an xf:output text

[Elias M. <eli...@gm...>]

Hi.

I use an instance with codes, labels and descriptions to populate the
labels and the hints of the fields on the form.  It works fine like that:

  <xf:input ref="/my/ref/data">
    <xf:label><xf:output value="instance('labels')/Codes[Code =
'ACODE']/Name"/></xf:label>
     <xf:hint><xf:output value="instance('labels')/Codes[Code =
'ACODE']/Desc"/></xf:hint>
</xf:input>

This works fine for fields. But if I have several nodes and I use xf:repeat
to create a table with options for the user, I would like the header of the
table to show the label and description from the instance.  I tried:

<table>
<tr>
<th>
     <xf:output value="instance('labels')/Codes[Code = 'BCODE']/Name"/>
        <xf:hint><xf:output value="instance('labels')/Codes[Code =
'BCODE']/Desc"/></xf:hint>
     </xf:output>
</th>
..
..
but it doesn't work.  Any suggestions??

Thanks
Elias

Re: [Xsltforms-support] xforms-submit-error - no context information - SOLVED

[Ihe O. <ihe...@gm...>]

On Fri, Dec 21, 2012 at 9:32 PM, Alain Couthures
<ala...@ag...> wrote:
> Le 21/12/2012 13:14, Ihe Onwuka a écrit :
>
>  can I suggest
> some sort of diagnostic message to this effect - i.e that the XML is
> not valid.
>
>
> It is implemented in XSLTForms: event('error-type') should return
> "validation-error"
>
> Did you try this?
>

I have now.

      <xf:submission id="load"
			  ref="instance('input')"
			  method="post"
			  resource="edit.xq">
        <xf:message ev:event="xforms-submit-error"
level="modal">Submission Error<xf:output
value="event('error-type')"/></xf:message>
      </xf:submission>

gives undefined as the modal message.

Re: [Xsltforms-support] xforms-submit-error - no context information - SOLVED

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

Le 21/12/2012 13:14, Ihe Onwuka a écrit :
>   can I suggest
> some sort of diagnostic message to this effect - i.e that the XML is
> not valid.
>
>
It is implemented in XSLTForms: event('error-type') should return 
"validation-error"

Did you try this?

Thanks!

-Alain

[Xsltforms-support] xforms-submit-error - no context information - SOLVED

[Ihe O. <ihe...@gm...>]

On Wed, Dec 19, 2012 at 10:39 PM, Ihe Onwuka <ihe...@gm...> wrote:
> The application I am developing has  an option to upload and digitally
> sign a file. However when my post to the server includes the digitally
> signed markup in the instance I get an xforms-submit-error (I can
> successfully submit when I don't upload the digitally signed content).
>
> I have affirmed that the instance is well-formed by cutting and
> pasting the display from the XSLTForms debugger and running XMLLint on
> it.
>
> The next thing I have tried is to access information about the
> submission error via the event() function however I just get undefined
> for every option I try so I'm guessing context information on events
> is not implemented.
>
> Fundamentally I want to diagnose the submission error but apart from
> being told it happened on the trace log there doesn't seem to be any
> more information available.

OK problem solved.

Claudius's cryptographic module allows digital signage at the element
level with the default being to embed the digital signature in the
element being signed.

The intractability of the error was on account that post signage, the
XForm would not submit XML that was perfectly well formed and gave no
clue that anything else was amiss.

As ever the inspiration for the solution came from an enforced period
away from the computer.

I changed the options on the signage   to reverse the embedding
process, that is instead of the default, embedding the digital
signature in the element,  I now embed the element in it's digital
signature and lo and behold I was  able to submit the XForm.

The reason I suspected this would make a difference was that I am
digitally signing an element which is base64Binary and has an xsi:type
set accordingly. The default cryptographic embed changes this element
to one of mixed content which I suspect invalidates the typing. This
must be something that is validated during submission, if it is and
such validation is in accordance with  the spec then can I suggest
some sort of diagnostic message to this effect - i.e that the XML is
not valid.

May I also  suggest a reconsideration of the default Cryptographic
signage option from 'enveloped' to 'enveloping' (or detached) since
'enveloped't has the capability of invalidating your XML as has been
seen from my example.

[Xsltforms-support] xforms-submit-error - no context information

[Ihe O. <ihe...@gm...>]

The application I am developing has  an option to upload and digitally
sign a file. However when my post to the server includes the digitally
signed markup in the instance I get an xforms-submit-error (I can
successfully submit when I don't upload the digitally signed content).

I have affirmed that the instance is well-formed by cutting and
pasting the display from the XSLTForms debugger and running XMLLint on
it.

The next thing I have tried is to access information about the
submission error via the event() function however I just get undefined
for every option I try so I'm guessing context information on events
is not implemented.

Fundamentally I want to diagnose the submission error but apart from
being told it happened on the trace log there doesn't seem to be any
more information available.

Re: [Xsltforms-support] XForms 1.1 Cryptographic functions

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

SHA-1, MD5 and BASE64 (as an extension...) are supported in digest() but 
hmac() is not supported... Sorry

-Alain

Le 18/12/2012 23:08, Ihe Onwuka a écrit :
> Can I confirm whether the hmac() and digest() functions are
> implemented in XSLTForms as it doesn't seem to recognise my calls to
> hmac.
>
> I am aware of the option of   Claudius's excellent EXPath cryptographic library.
>
> thanks
>
> ------------------------------------------------------------------------------
> LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial
> Remotely access PCs and mobile devices and provide instant support
> Improve your efficiency, and focus on delivering more value-add services
> Discover what IT Professionals Know. Rescue delivers
> http://p.sf.net/sfu/logmein_12329d2d
> _______________________________________________
> Xsltforms-support mailing list
> Xsl...@li...
> https://lists.sourceforge.net/lists/listinfo/xsltforms-support
>

[Xsltforms-support] XForms 1.1 Cryptographic functions

[Ihe O. <ihe...@gm...>]

Can I confirm whether the hmac() and digest() functions are
implemented in XSLTForms as it doesn't seem to recognise my calls to
hmac.

I am aware of the option of   Claudius's excellent EXPath cryptographic library.

thanks

[Xsltforms-support] XForms course offered for May 2013 in Rockville, Maryland

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

[Subscribers to this list may be interested in the XForms course
mentioned below.  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 May 2013, in Rockville, Maryland.


XQUERY FOR DOCUMENTS

  20-21 May 2013, 9:30 - 5:30
  http://www.blackmesatech.com/2013/05/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.


INTRODUCTION TO XFORMS FOR XML USERS

  22-23 May 2013, 9:30 - 5:30
  http://www.blackmesatech.com/2013/05/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.


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/2013/05/xforms
   http://www.blackmesatech.com/2013/05/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] "The namespace axis starting at an attribute node will never select anything"

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

Hello, Alain.

Saxon from oxygen xml editor says:
System ID: \xsltforms\xsltforms.xsl
Scenario: xml-stylesheet processing instruction
Engine name: Saxon-HE 9.4.0.3
Severity: warning
Description: The namespace axis starting at an attribute node will never
select anything
Start location: 5150:0

line 5150 of latest xsltforms.xsl is:
    <xsl:for-each select="(namespace::* | @*/namespace::*)[name()!='xml']">

Do I need to worry about this warning?)

Re: [Xsltforms-support] Exception caused by null namespace declaration on xf:instance

[Ihe O. <ihe...@gm...>]

On Tue, Dec 18, 2012 at 12:01 PM, Ihe Onwuka <ihe...@gm...> wrote:
> Rev 559.
>
> <xf:instance id="biff" xmlns="">
>     {$xQueryVariable}
> </xf:instance>
>
> leads to the following exception.
>
>
> XSLTForms Exception
> --------------------------
>
> Incorrect Javascript code generation:
>
> xsltforms_init@http://localhost:8080/exist/rest//db/apps/clinsys/crypto.xq:2
> onload@http://localhost:8080/exist/rest//db/apps/clinsys/crypto.xq:1
>
>
> ReferenceError
>
> xsltforms_initImpl is not defined
>
> <xf:instance id="biff">
>    <root xmlns="">{$xQueryVariable}</root>
>  </xf:instance>
>
> works fine.

I've figured out what is going on here, and it is my error and it
serves as a reminder of the perils of not putting instance data in
it's own namespace.

The actual scenarion leading to the problem is

<model xmlns:xf="http://www.w3.org/2002/xforms">
  <instance id="biff" xmlns=''">

which takes the instance declaration out of the XForms namespace and
causes the error. Note this would not have happened if I had put my
instance data in a namespace (well I wanted to but that is not how the
data comes).

So the remaining issue is whether it is nice for XSLTForms to give a
Javascript exception in this circumstance.

[Xsltforms-support] Exception caused by null namespace declaration on xf:instance

[Ihe O. <ihe...@gm...>]

Rev 559.

<xf:instance id="biff" xmlns="">
    {$xQueryVariable}
</xf:instance>

leads to the following exception.


XSLTForms Exception
--------------------------

Incorrect Javascript code generation:

xsltforms_init@http://localhost:8080/exist/rest//db/apps/clinsys/crypto.xq:2
onload@http://localhost:8080/exist/rest//db/apps/clinsys/crypto.xq:1


ReferenceError

xsltforms_initImpl is not defined

<xf:instance id="biff">
   <root xmlns="">{$xQueryVariable}</root>
 </xf:instance>

works fine.

Re: [Xsltforms-support] Upload - mediatype and filename not supported

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

Hi Dan,

Here is my test case:

<html xmlns:xforms="http://www.w3.org/2002/xforms" 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
xmlns="http://www.w3.org/1999/xhtml" 
xmlns:xhtml="http://www.w3.org/1999/xhtml" 
xmlns:ev="http://www.w3.org/2001/xml-events" 
xmlns:xsd="http://www.w3.org/2001/XMLSchema">
   <head>
     <title>Uploads and types</title>
     <xforms:model>
        <xforms:instance xmlns="">
           <data>
             <filename1/>
             <attachment1 xsi:type="xsd:anyURI"/>
             <filename2/>
             <attachment2 xsi:type="xsd:hexBinary"/>
             <filename3/>
             <attachment3 xsi:type="xsd:base64Binary"/>
           </data>
        </xforms:instance>
     </xforms:model>
   </head>
   <body>
     <h1>Uploads and types</h1>
     <p>
         <xforms:upload ref="attachment1" incremental="true">
             <xforms:label>Upload for anyURI: </xforms:label>
             <xforms:filename ref="../filename1"/>
         </xforms:upload>
         <br/>
         <xforms:output value="filename1">
<xforms:label>Filename:&#160;</xforms:label>
         </xforms:output>
         <br/>
         <xforms:output value="attachment1">
<xforms:label>Value:&#160;</xforms:label>
         </xforms:output>
     </p>
     <p>
         <xforms:upload ref="attachment2" incremental="true">
             <xforms:label>Upload for hexBinary: </xforms:label>
             <xforms:filename ref="../filename2"/>
         </xforms:upload>
         <br/>
         <xforms:output value="filename2">
<xforms:label>Filename:&#160;</xforms:label>
         </xforms:output>
         <br/>
         <xforms:output value="attachment2">
<xforms:label>Value:&#160;</xforms:label>
         </xforms:output>
     </p>
     <p>
         <xforms:upload ref="attachment3" incremental="true">
             <xforms:label>Upload for base64Binary: </xforms:label>
             <xforms:filename ref="../filename3"/>
         </xforms:upload>
         <br/>
         <xforms:output value="filename3">
<xforms:label>Filename:&#160;</xforms:label>
         </xforms:output>
         <br/>
         <xforms:output value="attachment3">
<xforms:label>Value:&#160;</xforms:label>
         </xforms:output>
     </p>
   </body>
</html>

Thanks!

-Alain

Le 15/12/2012 16:12, Dan McCreary a écrit :
> Hi Alain,
>
> Do you have a small XForms sample that has an upload control in it? 
>  If you do I will add it to the eXist XSLTForms samples with a backend 
> "catcher" script.
>
> - Dan
>
> -- 
> Dan McCreary
> NoSQL Evangelist
> office: (952) 931-9198
> cell: (612) 986-1552

Re: [Xsltforms-support] Upload - mediatype and filename not supported

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

Hi Alain,

Do you have a small XForms sample that has an upload control in it?  If you
do I will add it to the eXist XSLTForms samples with a backend "catcher"
script.

- Dan

On Fri, Dec 14, 2012 at 2:00 PM, Alain Couthures <
ala...@ag...> wrote:

> filename is now supported in the latest builds.
>
> -Alain
>
> Le 14/12/2012 16:06, Ihe Onwuka a écrit :
> > I unsuccessfully tried to use the mediatype and filename children
> > elements of xf:upload and got a message saying they were not
> > supported.
> >
> > Said message was confirmed when I tried the example in the discussion
> > section here.
> >
> > http://en.wikibooks.org/wiki/XForms/Upload#Uploading_Binary_Files
> >
> > Is this by design.
> >
> >
> ------------------------------------------------------------------------------
> > LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial
> > Remotely access PCs and mobile devices and provide instant support
> > Improve your efficiency, and focus on delivering more value-add services
> > Discover what IT Professionals Know. Rescue delivers
> > http://p.sf.net/sfu/logmein_12329d2d
> > _______________________________________________
> > Xsltforms-support mailing list
> > Xsl...@li...
> > https://lists.sourceforge.net/lists/listinfo/xsltforms-support
> >
>
>
>
> ------------------------------------------------------------------------------
> LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial
> Remotely access PCs and mobile devices and provide instant support
> Improve your efficiency, and focus on delivering more value-add services
> Discover what IT Professionals Know. Rescue delivers
> http://p.sf.net/sfu/logmein_12329d2d
> _______________________________________________
> Xsltforms-support mailing list
> Xsl...@li...
> https://lists.sourceforge.net/lists/listinfo/xsltforms-support
>



-- 
Dan McCreary
NoSQL Evangelist
office: (952) 931-9198
cell: (612) 986-1552

[Xsltforms-support] Fwd: Upload - mediatype and filename not supported

[Ihe O. <ihe...@gm...>]

---------- Forwarded message ----------
From: Ihe Onwuka <ihe...@gm...>
Date: Sat, Dec 15, 2012 at 5:38 AM
Subject: Re: [Xsltforms-support] Upload - mediatype and filename not supported
To: Alain Couthures <ala...@ag...>


I also noticed that setting  the readonly attribute of an upload
control to true changes it's appearance but doesn't stop you from
changing it'z value.

On Fri, Dec 14, 2012 at 8:00 PM, Alain Couthures
<ala...@ag...> wrote:
> filename is now supported in the latest builds.
>
> -Alain
>
> Le 14/12/2012 16:06, Ihe Onwuka a écrit :
>>
>> I unsuccessfully tried to use the mediatype and filename children
>> elements of xf:upload and got a message saying they were not
>> supported.
>>
>> Said message was confirmed when I tried the example in the discussion
>> section here.
>>
>> http://en.wikibooks.org/wiki/XForms/Upload#Uploading_Binary_Files
>>
>> Is this by design.
>>
>>
>> ------------------------------------------------------------------------------
>> LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial
>> Remotely access PCs and mobile devices and provide instant support
>> Improve your efficiency, and focus on delivering more value-add services
>> Discover what IT Professionals Know. Rescue delivers
>> http://p.sf.net/sfu/logmein_12329d2d
>> _______________________________________________
>> Xsltforms-support mailing list
>> Xsl...@li...
>> https://lists.sourceforge.net/lists/listinfo/xsltforms-support
>>
>

Re: [Xsltforms-support] Upload - mediatype and filename not supported

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

filename is now supported in the latest builds.

-Alain

Le 14/12/2012 16:06, Ihe Onwuka a écrit :
> I unsuccessfully tried to use the mediatype and filename children
> elements of xf:upload and got a message saying they were not
> supported.
>
> Said message was confirmed when I tried the example in the discussion
> section here.
>
> http://en.wikibooks.org/wiki/XForms/Upload#Uploading_Binary_Files
>
> Is this by design.
>
> ------------------------------------------------------------------------------
> LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial
> Remotely access PCs and mobile devices and provide instant support
> Improve your efficiency, and focus on delivering more value-add services
> Discover what IT Professionals Know. Rescue delivers
> http://p.sf.net/sfu/logmein_12329d2d
> _______________________________________________
> Xsltforms-support mailing list
> Xsl...@li...
> https://lists.sourceforge.net/lists/listinfo/xsltforms-support
>

Re: [Xsltforms-support] Upload - mediatype and filename not supported

[Ihe O. <ihe...@gm...>]

On Fri, Dec 14, 2012 at 3:06 PM, Ihe Onwuka <ihe...@gm...> wrote:
> I unsuccessfully tried to use the mediatype and filename children
> elements of xf:upload and got a message saying they were not
> supported.
>
> Said message was confirmed when I tried the example in the discussion
> section here.
>
> http://en.wikibooks.org/wiki/XForms/Upload#Uploading_Binary_Files
>
> Is this by design.

If I may clarify my requirement. I want to upload the file as
base64binary AND grab the filename and mediatype.

[Xsltforms-support] Upload - mediatype and filename not supported

[Ihe O. <ihe...@gm...>]

I unsuccessfully tried to use the mediatype and filename children
elements of xf:upload and got a message saying they were not
supported.

Said message was confirmed when I tried the example in the discussion
section here.

http://en.wikibooks.org/wiki/XForms/Upload#Uploading_Binary_Files

Is this by design.

Re: [Xsltforms-support] Fwd: Is xf:select1 containingitemset allowed in xf:itemset

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

Hello Alex,
>
> I have xforms with
> <xf:select1 ref="value_check" class="baseInput">
>     <xf:itemset nodeset="../itemset/info/row">
>         <xf:label ref="name" />
>         <xf:value ref="uid" />
>     </xf:itemset>
> </xf:select1>
>
> inside
> xf:repeat element(line 327 in attached file).
>
>
> When I click to checkbox the error message appears.(output from 
> firebug console):
> TypeError: this.select.firstChild is null
> [????????? ?? ???? ??????] 	
> if (!this.full && this.select.firstChild.value === "\xA0") {(xsltforms.js (line 7250)
>
I haven't reproduced this issue with latest version of Firefox for 
Windows. The line number is not enough to be sure that you're using the 
latest build.
> Thus results to an unexpected behaviour: clicking on one checkbox may 
> change value of another( from another repeat iteration).
After an exception, behavior is quite hazardous ;-)
>
> Otherwise, when I delete select1 from repeat element everything works 
> properly.
I don't understand what you want to do with ref="value_check" for this 
select1 control. It means that the value of this element is set by this 
control but the itemset has not boolean values.
>
> Is itemset allowed inside repeat?
Yes, of course...

-Alain

Re: [Xsltforms-support] ordering repetitions

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

Hi Stephen,

Thanks a lot: it works just fine.

I guess I should have figured out something like this myself ….

Since the buttons showed up if there were any siblings at all, I added a condition to ensure that they only showed up if the siblings had the same name - if the repetition can actually be moved up or down.

<xf:group ref="preceding-sibling::*[1][self::mods:name]">
	<xf:trigger>
		<xf:label>Move Up</xf:label>
		<xf:action ev:event="DOMActivate">
			<xf:insert nodeset="self::*" origin="following-sibling::*[1]" position="before"/>
			<xf:delete nodeset="following-sibling::*[1]"/>
		</xf:action>
	</xf:trigger>
</xf:group>
<xf:group ref="following-sibling::*[1][self::mods:name]">
	<xf:trigger>
		<xf:label>Move Down</xf:label>
		<xf:action ev:event="DOMActivate">
			<xf:insert nodeset="self::*" origin="preceding-sibling::*[1]" position="after"/>
			<xf:delete nodeset="preceding-sibling::*[1]"/>  
		</xf:action>
	</xf:trigger>
</xf:group>

Thanks again!

Best,

Jens

On Dec 6, 2012, at 1:15 AM, Stephen Cameron <ste...@gm...> wrote:

> one approach.
> repeats need a dynamic sort capability, is this in Xforms 2.0?              
> 
>                      <xf:group ref="instance('xyz')/*[index('repeat_id')]>
> 
>                           <xf:group ref="preceding-sibling::*[1]">
>                                        <xf:trigger>
>                                           <xf:label>Move Up</xf:label>
>                                           <xf:action ev:event="DOMActivate">
>                                              <xf:insert nodeset="self::*" origin="following-sibling::*[1]" position="before"/>
>                                              <xf:delete nodeset="following-sibling::*[1]"/>
>                                           </xf:action>
>                                        </xf:trigger>
>                                     </xf:group>
>                                     <xf:group ref="following-sibling::*[1]">
>                                        <xf:trigger>
>                                           <xf:label>Move Down</xf:label>
>                                           <xf:action ev:event="DOMActivate">
>                                              <xf:setvalue ref="instance('temp')/s2x:posn" value="index('element_details')"/>
>                                              <xf:insert nodeset="self::*" origin="preceding-sibling::*[1]" position="after"/>
>                                              <xf:delete nodeset="preceding-sibling::*[1]"/>
>                                              <xf:setindex repeat="element_details" index="instance('temp')/s2x:posn + 1"/>
>                                           </xf:action>
>                                        </xf:trigger>
>                                     </xf:group>
>                                     <xf:trigger>
>                                        <xf:label>Delete</xf:label>
>                                        <xf:delete ev:event="DOMActivate" nodeset="current()"/>
>                                     </xf:trigger>
>                                  </xf:group>
> 
> 
> On Thu, Dec 6, 2012 at 2:35 AM, Jens Østergaard Petersen <oe...@gm...> wrote:
> Hi,
> 
> Sometimes, if you have a repeat, you wish to be able to move the repetitions up or down, for instance arranging names in some meaningful order. I have seen code for this somewhere, but I can't find it again. Does anyone have something like this lying around?
> 
> Thanks in advance for any assistance,
> 
> Jens
> ------------------------------------------------------------------------------
> LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial
> Remotely access PCs and mobile devices and provide instant support
> Improve your efficiency, and focus on delivering more value-add services
> Discover what IT Professionals Know. Rescue delivers
> http://p.sf.net/sfu/logmein_12329d2d
> _______________________________________________
> Xsltforms-support mailing list
> Xsl...@li...
> https://lists.sourceforge.net/lists/listinfo/xsltforms-support
> 

[Xsltforms-support] ordering repetitions

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

Hi,

Sometimes, if you have a repeat, you wish to be able to move the repetitions up or down, for instance arranging names in some meaningful order. I have seen code for this somewhere, but I can't find it again. Does anyone have something like this lying around?

Thanks in advance for any assistance,

Jens