Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
What would be the best client side javascript based XForms processor?
I’m trying to migrate plugin (activeX) based Xforms processing solution to a javascript based client side processor. But the migrating XForm does not work properly in any of the client side solutions I found. They give various unfriendly errors and its very hard to find why as it is unable to debug. Ideally migration should work without any changes isn’t it? How should I approach my goal ?
I too will refrain from saying which is the best solution. 😉
On your particular problem though, either you were using a non-standard feature in formsPlayer, or you were you were using a standard feature, but it is not implemented in the processor you are trying to move to.
Without seeing the form, I couldn’t say.
On your other question about JavaScript client-side engines, you might want to take a look at [backplanejs][1]. It’s a JavaScript library, built on YUI, and which provides an XForms processor and an RDFa parser, amongst other things. (The XForms support comes from the Ubiquity XForms engine, which we’re working on with IBM — they’re keen to add Dojo support, and others want to add jQuery support.)
There will also be a successor to formsPlayer available soon, which will be a set of installable extensions to backplanejs, rather than a self-contained application.
[1]: http://backplanejs.googlecode.com/ backplanejs