xsltforms-support — XSLTForms support list

[Xsltforms-support] [PATCH] Add event() xforms-standard XPath function, initially with properties for <xf:submit> and some helpful ones

[Kostis A. <ank...@gm...>]

Hi,

I started the implementation of the part of the XForms spec regarding
the event() XPath function:
  http://pastebin.com/uQvNZWXX

If this implementation seems the right one, it would be easier for
contributors to add contexts for other events.


EVENT CONTEXTS
----------------------------
To implement it, i added a XMLEvents.EventContexts stack that hold at
its top the event's context object
(a stack-of-associative-arrays).

The updating of this stack happens before and after sending the event,
in XMLEvents.dispatch(),
utilizing a try-finally structure to ensure no context objects left in
the stack in case of errors
(since the event functions are written by the author and may throw any
xforms-exception or errors).


DEFAULT EVENT PROPERTIES
------------------------------------
As a starting point, i added certain debug aids into the contexts for
all events, and this is *not* against the specs.
The extension properties are a subset of those described by Orbeon-Forms[1]
but without namespaces.
Maybe in a later step someone could add namespace support for the
event-property-names.

In particular, i added the following default-extension
event-properties into all event-contexts:
	type: the name of the event;
	targetid: the id of the event's target-element.
	bubbles = 'true' if it is a bubbling event.
	cancelable = 'true' if it is a cancelable event.

SUBMIT-ERROR EVENT PROPERTIES
-----------------------------------------------------
I added the following properties ONLY on "xforms-submt-error" event:
* STANDARD XForms event-properties:
    method: see XForms-1.1, ch 11.5 [2]
    resource-uri: see XForms-1.1, ch 11.5 [2]
    error-type: see XForms-1.1, ch 11.5 [2]
    response-status-code: see XForms-1.1, ch 11.5 [2]
    response-reason-phrase: see XForms-1.1, ch 11.5 [2]
    response-headers:  see XForms-1.1, ch 11.5 [2], TODO: Parse
headers into nodes.
    response-body: see XForms-1.1, ch 11.5 [2]
* XSLTForms EXTENSION event-properties
(better "standarize" those 2 throughout the code):
    message: any js-exception message
    stack-trace: any js-exception stack


NOTE 1: The code for adding event-context to the 'xforms-submit-error'
event is not 100% complete.
(although it took me 3-4 hours to do it)
* it checks for null-binding before sending a request (for 'no-data'
error-type) obeying to the xforms-spec, but does not evaluate the
binding to see if it is empty,
* it does not tries to discriminates submission errors after sending
request('parse-error' or 'target-error' error-type),
* it does not check cross-domain, neither post-form (METHOD="xml-url-encoded")
* it does not parses response-headers or response-body into nodesets.
There are some TODOs left in the patch about these points.

NOTE 2: The patch does not include changes into final files, you need
to build to generate them, before commiting the patch.
And since i still cannot manage to build the project, i hope i'm not
forgetting anything,
since i backported the changes from the final 'xsltforms.js' file
where i was testing them.


Regards,
  kostis Anagnostopoulos


[1] http://wiki.orbeon.com/forms/doc/developer-guide/xforms-events#TOC-Enhanced-event-function-support
[2] http://www.w3.org/TR/xforms11/#submit-evt-submit-error

Re: [Xsltforms-support] Dynamic loading of instance into a model

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

Hello Dhiradj,
> I have a question about the dynamic loading of an instance into a model.
> Here's in example of my code:
> <xf:model id="InlineWerken">
>          <xf:instance id="inlinewerken" src="vte_406207_d.xml" />
> </xf:model>
> The xml file is read from a local folder. This name of the XML file 
> will be different every time.(based on exports from another 
> application). I'm looking for a solution how to dynamically load the 
> instance in the model.
You can use a submission to be activated automatically after form load. 
This has to be associated with "xforms-ready" directly into the model 
declaration.

Sorry, I can't find a working example about that but I have already used 
this workaround...

Thanks!

-Alain

[Xsltforms-support] [PATCH] Issue xforms-binding-exception on non-existent or null bind-IDs with helpfull message

[Kostis A. <ank...@gm...>]

Hi,

On rev393, "xf:output/@value enabled by default" the added lines:
  if (this.binding.isvalue) {
      Core.setClass(this.element, "xforms-disabled", false);
  }
cause null-refs errors without any meaningfull context
when outputs do not specify @ref or @value.

If the check becomes
  if (this.binding && this.binding.isvalue)
then the patch[1] i had submited 2 weeks ago, which gathered any such
errors along with non-existent-ids erros
and issued 'xforms-binding-exception' according to the specs would
continue to work.

So i'm rebasing that bindings-errors patch to the latest revision.
  http://pastebin.com/sFfcggjN

NOTE 1: that the patch contains at the bottom a minor css modification
to provide for lengthier status-panel which might not be exactly
suitable for IE...)
NOTE 2: The patch does not include changes into final files, you need
to build to generate them before commiting the patch.

Hope it gets accepted soon, since it really makes the life of xforms
authors much easier .

Kostis

[1] https://sourceforge.net/mailarchive/forum.php?thread_name=w2z...@ma...&forum_name=xsltforms-support

[Xsltforms-support] CSS broken since revision 385

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

Hi,

Since revision 385 (and at least up to revision 396), my own CSS is
simply "forgotten". I mean, I have the following tag in my "index.xml" file:

  <link rel="stylesheet" type="text/css" href="style/screen.css"></link>

But in the generated code, there's no trace of this "screen.css" file.
This must be related to the change in revision 385. From:

<xsl:copy-of select="xhtml:head/xhtml:*[local-name() != 'script'] |
xhtml:head/comment() | head/title | head/meta | head/style | head/link |
head/comment()"/>

to:

<xsl:copy-of select="xhtml:head/xhtml:*[local-name() != 'script' and
local-name() != 'style' and local-name() != 'link'] |
xhtml:head/comment() | head/title | head/meta | head/comment()"/>
 <xsl:apply-templates select="xhtml:head/xhtml:style |
xhtml:head/xhtml:link | head/style | head/link"/>

I don't understand why, but the latter version seems to be broken.

Thanks,
Grégoire

PS : Alain, did you had enough time to look at my email sent on 15th
april 21:17? This XPath problem is weird.

[Xsltforms-support] [PATCH] Problem with rev388 on XFNode.readonly manifested at xf:select with xf:items not updating from files

[Kostis A. <ank...@gm...>]

Hi,

The single-line commit on rev388("Missing property causing infinite
loop") of defining the XFNode.readonly property on node-initialization
broke <xf:select> controls, and their itemsets do not get updated when
their underlying nodeset change.
I have not cheked whether more problems exist with this modification.
Reported against Chrome (assuming it applies to all browsers though)


The example-form below demonstrate the problem:
  http://pastebin.com/BsdsxDhh
(copied from an older still-unsolved problem on itemsets, ignore the
text descriptions)



I cannot explain why this happen, but i found that if on XFNode initialization,
the XFNode.readonly property is set to 'undefined' instead of 'false',
then the problem dissappears, and the infinite recurssion issue remains fixed.
(i performed no other tests

The patch below performs the suggested modification:
(and fixes tabstops and spaces)

Index: src/js/xpathexpr/DOM/XNode.js.xml
===================================================================
--- src/js/xpathexpr/DOM/XNode.js.xml	(revision 396)
+++ src/js/xpathexpr/DOM/XNode.js.xml	(working copy)
@@ -313,7 +313,7 @@
     this.valid = true;
     this.required = false;
     this.relevant = true;
-		this.readonly = false;
+    this.readonly = undefined;
     this.type = Schema.getType("xsd_:string");
     this.schemaType = false;
     this.bind = null;


Regards,
  Kostis

[Xsltforms-support] Bad link on sourceforge on xsltform html page

[Kostis A. <ank...@gm...>]

Hi,

the link to sourceforge on page:
  http://www.agencexml.com/xsltforms
does not point to sourceforge xsltforms project

Kostis.

Re: [Xsltforms-support] [PATCH] Reworked Dialogs to fix show-hidding problems

[Kostis A. <ank...@gm...>]

Hi Alain,


1. By mistake at paste-bin i had placed an earlier version of the patch,
which in the Dialog.hide() function it was invoking the
Dialog.showSelects() prior to decreasing zindex,
which wasn't correct.
(you must have noticed that the attached diff-file was not even complete)

2. The Dialog.depth variable in xsltforms.js:347 is not used anywhere.
It can be safely deleted (that was included in the patch).

3. Finally i replaced some spaces with tabs for homogenity.

The following patch applies the above changes:

Index: src/js/main/jsCore.js.xml
===================================================================
--- src/js/main/jsCore.js.xml	(revision 396)
+++ src/js/main/jsCore.js.xml	(working copy)
@@ -352,10 +352,9 @@
 Dialog Panel Management</cm:wiki>
 <![CDATA[
 var Dialog = {
-    openPosition: {},
-    dialogs : [],
-    init : false,
-		depth : 0,
+		openPosition: {},
+		dialogs : [],
+		init : false,
 		initzindex : 50,
 		zindex: 0,
 		selectstack : [],
@@ -436,9 +435,6 @@
 				return;
 			}
 			
-			this.showSelects(div, true, modal);
-			div.style.display = "none";
-			
 			if (modal) {
 				if (!this.dialogs.length) {
 					this.zindex = 0;
@@ -453,6 +449,9 @@
 					}
 				}
 			}
+			
+			this.showSelects(div, true, modal);
+			div.style.display = "none";
     },
 ]]>
 		<cm:wiki>

-------------------------- end-patch ----------------------

I apologize for the inconvinience,
  Kostis


On Mon, Apr 19, 2010 at 12:09 AM, COUTHURES Alain
<ala...@ag...> wrote:
> Hi Kostis,
>>
>> OK, i crafted a solution that prevents the
>> «focus-remaining-in-show-dialog-trigger» problem
>> from re-opening the same modal-dialog multiple times on [Enter] key
>> and then not hidding its "surround" modal-panel .
>>
>> The same solution also solves the (unreported) general problems of
>> invoking multiple times <xf:show> and <xf:hide> for the same
>> dialog-ids.
>>
>
> Thank you very much for this solution.
>
> I have checked and tested it successfully (I just had to fix a problem with
> Calendar control).
>
> This is committed now.
>
> Thanks!
>
> -Alain
>

Re: [Xsltforms-support] XForm fail in IE6 fails with comments with I18N characters (and XPath handling problems)

[Kostis A. <ank...@gm...>]

On Mon, Apr 19, 2010 at 12:20 AM, COUTHURES Alain
<ala...@ag...> wrote:
> Hi Kostis,
>>
>> I atteched the gr file you asked, but i note that the language is 'el'.
>> The 'gr' refers to the country, similar to en_UK, etc.
>>
>
> So the file name should be "config_el.xsl". Can you please check that it
> works for you?

Hi Alain,

I cannot switch to *any* language.
I tried adding the follosing PI:
  <?xsltforms-options debug="yes" lang="el"?>
but it did not work.

Am i missing something here?

Regards,
  Kostis

Re: [Xsltforms-support] Dynamic loading of instance into a model

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

Hello Dhiradj,

Dhiradj Badloe a écrit :
> Hello,
>
> I have a question about the dynamic loading of an instance into a model.
> Here's in example of my code:
> <xf:model id="InlineWerken">
>          <xf:instance id="inlinewerken" src="vte_406207_d.xml" />
> </xf:model>
> The xml file is read from a local folder. This name of the XML file
> will be different every time.(based on exports from another
> application). I'm looking for a solution how to dynamically load the
> instance in the model. Can someone help or advise me on this? Thanks!

I guess you will have to write a simple XQuery (ex:
"get_latest_xml_file.xql") which would return the instance to use.
Something like :

let $file := doc("/db/path_to/vte_406207_d.xml")
return $file

Then your XForm remains with a static file :
<xf:instance id="inlinewerken" src="get_latest_xml_file.xql" />

Now you only have to find how to generate the correct path for the doc()
function. And since I don't know how this name is generated, I cannot
help. :)

Regard,
Grégoire

Re: [Xsltforms-support] Getting the xf:upload control to work

[Kostis A. <ank...@gm...>]

Hi Alain,
maybe you can base the upload-impl on existing javascipt code.

For instance, by searching:
  http://www.google.gr/search?q=javascript+upload+file
I found:
  http://www.webtoolkit.info/ajax-file-upload.html

I apologize for not having the time to try it myself whether it is of
any value mu suggestion.

Regards,
  Kostis


On Mon, Apr 19, 2010 at 12:06 AM, COUTHURES Alain
<ala...@ag...> wrote:
> Hi Dan,
>> We are trying to get the xf:upload control to work.  Does anyone have
>> a sample that they can share?
> Sorry, the upload control is not yet implemented in XSLTForms.
>
> A full support at client-side only seems impossible for Javascript
> instructions due to security reasons: a Javascript instruction cannot be
> used to read the content of a local file.
>
> There is a workaround with a basic server treatment to send back the
> content of the file so it can be read at client-side. It means that the
> file will be transfered twice in this case!
>
> Do you require a full support?
>
> Thanks!
>
> -Alain
>
> ------------------------------------------------------------------------------
> Download Intel&#174; Parallel Studio Eval
> Try the new software tools for yourself. Speed compiling, find bugs
> proactively, and fine-tune applications for parallel performance.
> See why Intel Parallel Studio got high marks during beta.
> http://p.sf.net/sfu/intel-sw-dev
> _______________________________________________
> Xsltforms-support mailing list
> Xsl...@li...
> https://lists.sourceforge.net/lists/listinfo/xsltforms-support
>

[Xsltforms-support] Dynamic loading of instance into a model

[Dhiradj B. <dh...@gm...>]

Hello,

I have a question about the dynamic loading of an instance into a model.
Here's in example of my code:
<xf:model id="InlineWerken">
         <xf:instance id="inlinewerken" src="vte_406207_d.xml" />
</xf:model>
The xml file is read from a local folder. This name of the XML file will be
different every time.(based on exports from another application). I'm
looking for a solution how to dynamically load the instance in the model.
Can someone help or advise me on this? Thanks!

Regard,

Dhiradj

Re: [Xsltforms-support] sending xsltforms submission to PayPal for processing - possible?

[Alexander Ž. <sa...@st...>]

ok, I found an article (Fixing AJAX: XMLHttpRequest Considered  
Harmful) explaining this in more detail.

thanks

A.


On Apr 18, 2010, at 10:55 PM, COUTHURES Alain wrote:

> Hi Alexander,
>> I guess I do not understand where the "...cross-domain  
>> restriction..."  comes from. As a consequence I do not understand  
>> how to use "...GET  method instead with xforms:load..."
>>
> For security reasons, pure Javascript instructions cannot be used to  
> exchange data with a server not been in the same domain and same  
> port. This is the "cross-domain restriction" implemented in  
> XmlHttpRequest. There are workarounds based on HTML tricks, one of  
> them being using SCRIPT element with @src passing parameters in the  
> query string while Javascript instructions returned by this other  
> server call a callback function...
>
> xforms:load is not implemented with XmlHttpRequest in XSLTForms but  
> with location.href so the cross-domain restriction is not to be  
> considered in this case.
>> URL rewriting - again - due to not understanding why/where is the  
>> form  failing now, I can't comment.
>>
> URL rewriting allows to trick the client browser in a sense that it  
> believes that the request URL will be treated by the targeted server  
> but, using URL rewriting, this one just sends the request to another  
> one in a different domain. There is no security restriction there  
> because it's performed at server-side.
>
> Hope it helps!
>
> -Alain
>
>
>

Re: [Xsltforms-support] Add link to wikibook on xsltforms welcome pages

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

Hi Kostis,
> In order to help xform-authors and to facilitate contributtors to
> project's documentation,
> it would be good if you added the link to the wiki-books:
>   http://en.wikibooks.org/wiki/XSLTForms
> on pages:
> a) http://www.agencexml.com/xsltforms (since it is the first page on searches)
>   
This has been added.
> b) https://sourceforge.net/projects/xsltforms/ (somewhere on project details)
>   
Unfortunately, just one link can be provided for an SF project.

Thanks!

-Alain

Re: [Xsltforms-support] XForm fail in IE6 fails with comments with I18N characters (and XPath handling problems)

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

Hi Kostis,
> I atteched the gr file you asked, but i note that the language is 'el'.
> The 'gr' refers to the country, similar to en_UK, etc.
>   
So the file name should be "config_el.xsl". Can you please check that it 
works for you?
> Regarding the encodings, i had problems with IE particularly,not with
> FF or chrome.
> When on ISO-8859-1 encoding, and the message-text passes through
> either xsl or through js,
> IE fails to print greek messages correctly, i see their html entities instead
For output, there is a specific approach to be used with IE in this 
case: use of .innerHTML to convert entities. It appears that 
output/@encoding has to stay at "iso-8859-1" in this case.

Using output/@encoding="utf-8" is OK for UTF-8 comments but not for 
Javascript instructions. There might be a fix for that too but I 
preferred removing all comments in the XForms source. Is it a problem 
for you?

This is committed.

Thanks!

-Alain

Re: [Xsltforms-support] Infinite-recursion on xforms-recalculate when model without instance and some control exists

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

Hi Kostis,
> An empty <xf:model> without some <xf:instance> and xforms controls
> *without* bindings
> (i.e triggers, output with constant-string XPath values)
> causes infinite recusrion on form-loading while dispatching:
> xforms-recalculate on <span class="xforms-model" id="xf-model-config"/>
This was due to some different bugs and I don't know why one of them 
wasn't seen in every case...

This is committed.

Thanks!

-Alain

Re: [Xsltforms-support] [PATCH] Reworked Dialogs to fix show-hidding problems

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

Hi Kostis,
> OK, i crafted a solution that prevents the
> «focus-remaining-in-show-dialog-trigger» problem
> from re-opening the same modal-dialog multiple times on [Enter] key
> and then not hidding its "surround" modal-panel .
>
> The same solution also solves the (unreported) general problems of
> invoking multiple times <xf:show> and <xf:hide> for the same
> dialog-ids.
>   
Thank you very much for this solution.

I have checked and tested it successfully (I just had to fix a problem 
with Calendar control).

This is committed now.

Thanks!

-Alain

Re: [Xsltforms-support] Getting the xf:upload control to work

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

Hi Dan,
> We are trying to get the xf:upload control to work.  Does anyone have 
> a sample that they can share?
Sorry, the upload control is not yet implemented in XSLTForms.

A full support at client-side only seems impossible for Javascript 
instructions due to security reasons: a Javascript instruction cannot be 
used to read the content of a local file.

There is a workaround with a basic server treatment to send back the 
content of the file so it can be read at client-side. It means that the 
file will be transfered twice in this case!

Do you require a full support?

Thanks!

-Alain

Re: [Xsltforms-support] sending xsltforms submission to PayPal for processing - possible?

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

Hi Alexander,
> I guess I do not understand where the "...cross-domain restriction..."  
> comes from. As a consequence I do not understand how to use "...GET  
> method instead with xforms:load..."
>   
For security reasons, pure Javascript instructions cannot be used to 
exchange data with a server not been in the same domain and same port. 
This is the "cross-domain restriction" implemented in XmlHttpRequest. 
There are workarounds based on HTML tricks, one of them being using 
SCRIPT element with @src passing parameters in the query string while 
Javascript instructions returned by this other server call a callback 
function...

xforms:load is not implemented with XmlHttpRequest in XSLTForms but with 
location.href so the cross-domain restriction is not to be considered in 
this case.
> URL rewriting - again - due to not understanding why/where is the form  
> failing now, I can't comment.
>   
URL rewriting allows to trick the client browser in a sense that it 
believes that the request URL will be treated by the targeted server 
but, using URL rewriting, this one just sends the request to another one 
in a different domain. There is no security restriction there because 
it's performed at server-side.

Hope it helps!

-Alain

Re: [Xsltforms-support] sending xsltforms submission to PayPal for processing - possible?

[Alexander Ž. <sa...@st...>]

Hi Alain,

I guess I do not understand where the "...cross-domain restriction..."  
comes from. As a consequence I do not understand how to use "...GET  
method instead with xforms:load..."

URL rewriting - again - due to not understanding why/where is the form  
failing now, I can't comment.

Sorry :-(

A.

On Apr 16, 2010, at 10:06 PM, COUTHURES Alain wrote:

> Hi Alexander,
>> Have any of you managed to accomplish this? I have a 3-product  
>> ordering xsltforms form. I would like to send the data the form  
>> collects for payment processing to PayPal using this submission:
>>
>> <xforms:submission id="s01" method="post" ref="order/paypal"  
>> replace="all" action="http://www.sandbox.paypal.com/cgi-bin/webscr"/>
> This is clearly a problem concerning the cross-domain restriction.
>
> Would there be possible to use a GET method instead with xforms:load?
>
> Another approach, do you think you could use URL rewriting?
>
> This is an interesting feature!
>
> Thank you for your feedbacks!
>
> -Alain

[Xsltforms-support] is external shema validation of input working?

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

Hello,

I'm looking at test-case "3.3.1.c1 valid schema" but XSLTForms does not 
seem to actually apply any validation specified in the schema for the 
element '<ex:myYear>', even though if finds and parses the schema.

Here is my copy of 3.3.1.c1, should  not this indicate that  a  
non-integer input (year) value is invalid?


1. XForm

<?xml-stylesheet href="build/xsltforms.xsl" type="text/xsl"?>
<html xmlns:my="http://commerce.example.com/payment" 
xmlns:txs="http://sourceforge.net/projects/txs" 
xmlns="http://www.w3.org/1999/xhtml" 
xmlns:req="http://www.agencexml.com/requests" 
xmlns:xforms="http://www.w3.org/2002/xforms" 
xmlns:ex="http://www.example.com" 
xmlns:ev="http://www.w3.org/2001/xml-events" 
xmlns:xhtml="http://www.w3.org/1999/xhtml">
  <head>
    <title>3.3.1.c1 valid schema</title>
    <xforms:model id="m_001" schema="schema.xsd">
        <xforms:instance>
            <data xmlns="">
                <ex:myYear>2001</ex:myYear>
            </data>
        </xforms:instance>
        <xforms:bind id="year" nodeset="ex:myYear" incremental="true()"/>
        <xforms:message ev:event="xforms-link-exception" 
level="modal">xforms-link-exception</xforms:message>
  </xforms:model>
  </head>
  <body>
      <xforms:input bind="year">
       <xforms:label>Year:</xforms:label>
    </xforms:input>
  </body>
</html>

2 XML Schema (schema.xsd)

<?xml version="1.0" encoding="UTF-8"?>
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" 
targetNamespace="http://www.example.com">
  <xs:element name="myYear">
    <xs:simpleType>
      <xs:restriction base="xs:integer"/>
    </xs:simpleType>
  </xs:element>
</xs:schema>


I'd appreciate it if someone could help get me started with this, I 
actually want to apply a regular expression to a string via a restriction.

This example should work (from xforms essentials 
http://xformsinstitute.com/essentials/browse/ch04s04.php) .

<xs:simpleType name="email">
  <xs:restriction base="xs:string">
    <xs:pattern value="[A-Za-z0-9!#-'\*\+\-/=\?\^_`\{-~]+
        (\.[A-Za-z0-9!#-'\*\+\-/=\?\^_`\{-~]+)*@[A-Za-z0-9!#-
        '\*\+\-/=\?\^_`\{-~]+(\.[A-Za-z0-9!#-'\*\+\-/=\?\^_`\
        {-~]+)*"/>
  </xs:restriction>
</xs:simpleType>



-- 
Regards

Stephen Cameron

Data Programmer
Integrated Marine Observing System  (IMOS)
eMarine Information Infrastructure Project
University of Tasmania, Private Bag 21, Hobart, TAS 7001, Australia

Tel: +61 3 6226 8507
Fax: +61 3 6226 2997
Email: ste...@ut...
URL: http://www.imos.org.au/eMII.html

[Xsltforms-support] Getting the xf:upload control to work

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

Hello everyone,

We are trying to get the xf:upload control to work.  Does anyone have a
sample that they can share?

We are using the following as our reference:

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

I realized this was written for the FireFox extension but I hoped that this
would also run on XSLTForms.

Thanks! - Dan

-- 
Dan McCreary
Semantic Solutions Architect
syntactica.com
952-460-1674
VOIP: 111@69.199.167.229

Re: [Xsltforms-support] Using JQuery with XSLTForms?

[David C. <ot...@cr...>]

Grégoire Colbert wrote ...

> Did you succeed in using JQuery with XSLTForms? When I add :
>  <script type="text/javascript" src="js/jquery-1.3.2.min.js"></script>
> 
> I get an error message in my XForm :
> 
> Incorrect Javascript code generation
> (...)
> TypeError
> div.style is undefined
> 
> If anyone had better luck, I would be happy to know what's wrong.

Did you include jQuery.noConflict()? That's worked for me.

- David

[Xsltforms-support] Using JQuery with XSLTForms?

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

Hello,

Did you succeed in using JQuery with XSLTForms? When I add :
 <script type="text/javascript" src="js/jquery-1.3.2.min.js"></script>

I get an error message in my XForm :

Incorrect Javascript code generation
(...)
TypeError
div.style is undefined

If anyone had better luck, I would be happy to know what's wrong.

Thanks,
Grégoire

PS : I'm using XSLTForms revision 384 since rev 385, with HTML output in,
seems to completely ignore my CSS. I'm using :
<xsl:output method="html" encoding="UTF-8" ......>

Re: [Xsltforms-support] sending xsltforms submission to PayPal for processing - possible?

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

Hi Alexander,
> Have any of you managed to accomplish this? I have a 3-product 
> ordering xsltforms form. I would like to send the data the form 
> collects for payment processing to PayPal using this submission:
>
> <xforms:submission id="s01" method="post" ref="order/paypal" 
> replace="all" action="http://www.sandbox.paypal.com/cgi-bin/webscr"/>
This is clearly a problem concerning the cross-domain restriction.

Would there be possible to use a GET method instead with xforms:load?

Another approach, do you think you could use URL rewriting?

This is an interesting feature!

Thank you for your feedbacks!

-Alain

[Xsltforms-support] sending xsltforms submission to PayPal for processing - possible?

[Alexander Ž. <sa...@st...>]

Have any of you managed to accomplish this? I have a 3-product  
ordering xsltforms form. I would like to send the data the form  
collects for payment processing to PayPal using this submission:

<xforms:submission id="s01" method="post" ref="order/paypal"  
replace="all" action="http://www.sandbox.paypal.com/cgi-bin/webscr"/>

Using FireFox and Safari on Mac I am getting an error when submitting:

1 -> "Submit post - undefined - http://www.sandbox.paypal.com/cgi-bin/webscr 
  - true

The full error trace is shown in an attached image (not sure if it  
makes it through to the list - if not and somebody will react to this,  
I will retype the error):