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