Slashdot Mirror

← Back to Stories (view on slashdot.org)

XForms Becomes Proposed Recommendation

Posted by michael on from the xml-for-everyone-whether-they-like-it-or-not dept.

leighklotz writes "The W3C has announced that XForms is now a Proposed Recommendation, after certification of one full implementation (open source Java XSmiles from Finland) and two more implementations of each feature (the Internet Explorer plug-in FormsPlayer and the Java standalone Novell xPlorer). XForms is the next generation of forms for the Web, and uses an XML-based three-layer model: data model, data, and user interface. XForms uses CSS for device independencence and is designed for integration into XHTML 2, SVG, and other XML-based markup languages. A host of other implementations are available or in progress, but my pick for most interesting is DENG, which is an XForms to Flash compiler written in Flash. DENG supports XForms, SVG, RSS, XHTML, and CSS. XForms is in consideration for other standards as diverse as Universal Remote Controls and the UK Government Interoperability Framework, and was developed with the participation of IBM, Oracle, Xerox, Adobe, Novell, SAP, Cardiff, PureEdge, and a host of other companies, universities, and invididuals."

3 of 247 comments (clear)

  1. WTF? That name is already taken, try again. by Dr.+Zowie · · Score: 5, Informative
    Jesus Christ, doesn't anyone look out for name collisions anymore? XForms is a GUI toolkit for X., in (slow) development since 1995 and still used in many useful apps like GeomView and Lyx.

    Now it's also "the next generation of web forms". Gag me with a buzzword.

    It's not as if the original XForms were unknown, either -- it comes up second in a Google search for "Xforms". These jokers should have known better.

    Feh.

  2. This is big. by CYwo1f · · Score: 5, Informative
    I, personally, can't wait until XForms is supported by all the major browsers. I've been planning for it in my web development framework for a few reasons. The benefits of having the browser construct an XML document and submit it back the server are tremendous:
    • You get hierarchical data, as opposed to the flat list of query parameters you have today. This makes a huge difference in the expressibility of a form. In fact, the XForms spec outlines some support for, for instance, dynamically adding controls to a form. No more re-submitting because those 3 file upload controls weren't enough for you, extend the form offline via javascript!
    • You get to reuse your form handling code to service SOAP requests, too. Instantly.
    • Form data can be serialized by the browser or by a more specialized client, and submitted later on (this is the Suspend and Resume another poster mentioned). How about being able to disconnect from the internet, copy that article submission form to your laptop, and fixing all those typos while you wait for that call from your editor? Or even submitting the form via an alternate method, SOAP or even email if your server supports it.
    • Accessibility. This isn't something I worry about on a daily basis, but there are many people who do. XForms controls are fairly platform-agnostic, and cater better to those with visual or other disabilities. Plus they're more easily adapted to novel input devices, like a cellphone.
    If you're a frustrated web developer itching for a simpler way of living, this may be your ticket. Even today, you should consider supporting XForms on your back end, while translating to the simpler HTML forms for today's web clients. I am.
  3. This is really a good thing by duncanFrance · · Score: 5, Informative

    I'm surprised at the number of negative posts I've seen already.

    This is actually a good thing. HTML forms are badly broken at every level, as anyone who has actually tried to build a decent UI with them will know.

    I have been using the draft specification for a while to produce forms in my software and it is useful because it lets me write code (PHP) which produces XFORMS XML, without worrying about how it will look. I then pass the XML through a transform and end up with good old html. Because the actual layout is produced by a transform, I can let my designers choose which transform they want to use to get the kind of prettiness they like. I can get complex layout, with sexy results, without having to write hideous html or wrangle with the cruft that is CSS each time.

    That's just the layout side of things. The three-level model give me much more control over adding scripting behaviours (Javascript), abstracting the form control out into PHP classes etc. etc.

    If you don't understand why html forms are broken, I suggest you start playing with Xforms. Once you grok it you won't look back. When I first came across Xforms, I thought "great, loads of complexity for no good reason" too.