RE: XForms Myths Exposed - By Ian Hixie (Opera)

jeez, I dont know,
I think he makes some pretty reasonable points actually.
one thing I would say in XForms favour is that if you are using it for
x-platform compatibility, then as long as you stick to xforms (ie dont use
script) then your app will run on any x-forms compatible renderer (whethere
is visually based or something else!)
you just cant do that with script. you would need a different version of the
script for each target.
but otherwise his arguments are actually pretty reasonable I think.
x-forms is largely declaritive, yes but actions can have side-effects (take
the whole submission/relevant thing and watch your data dissapear just
because you wanted to view it selectively in your form for example!)
I find it very awkward to do many things with xforms that are trivial with a
html form. but having said that, it is possible to get a great deal going in
an xform with remarkably little code. "its just when your boss says can I
just have it like this instead?", and you cant because Xforms is so
draconian in its definition that you just have to shake your head and hope
that the xforms gods get together and fix things so that it is possible to
do things without resorting to all kinds of wierdness & workarounds.
Anyway, I am still very hopeful for Xforms, its just not quite there yet.
I still actively use them here and there, but I'm much more selective about
where i will choose to try them now. once bitten ...
I certainly wouldnt argue that a better alternative to html forms isnt
required. its obvious that it is because there is sooo much work going on to
that end.
So c'mon u folk at w3c, dont just say that any real power x-forms might need
is available in scripts, cause using scripts kills half the reason i want to
use x-forms. Work it out already ;-)

its been a long day, I hope this doesnt sound too awful in the cold light of
day.

Cheers
Jason.

Received on Friday, 11 March 2005 04:50:03 UTC