1 / 12

Future of XForms

Future of XForms. Tuukka Haapaniemi 26.11.2008. XForms – What’s the need?. HTML forms Very outdated Hard to develop and to maintain Requires lot of work To create basic validation To create basic calculations In effect, to make anything userfriendly’ish. Limitations of HTML forms.

mikayla-osborne
Download Presentation

Future of XForms

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Future of XForms Tuukka Haapaniemi 26.11.2008

  2. XForms – What’s the need? • HTML forms • Very outdated • Hard to develop and to maintain • Requires lot of work • To create basic validation • To create basic calculations • In effect, to make anything userfriendly’ish Future of XForms - Tuukka Haapaniemi

  3. Limitations of HTML forms • Provides no means of separating data from the view • Data insertion into the templated form • Client -> Server ideology • Hard to implement workflow • Flat, key-value paired data Future of XForms - Tuukka Haapaniemi

  4. Key ideas of XForms • Separation of data from views of data • Model View Controller –pattern • Referencing complex data easily from the view • Workflow by changing only the view • Simple calculations • Simple validations • Dynamic controls • Device specific rendering Future of XForms - Tuukka Haapaniemi

  5. XForms’ requirements • XML namespaces • XML Xchema • Xpath • XML events • CSS3 Future of XForms - Tuukka Haapaniemi

  6. How to use XForms now • Browser specific plug-in • Common users propably don’t want to download • Server side XForms engine • Orbeon Forms • Many others • Client side parsing • Ubiquity XForms • Many others Future of XForms - Tuukka Haapaniemi

  7. Server side XForms engine • No need for a separately downloaded plug-in • Similar idea as with PHP, ASP(.NET) etc. • Produce currently supported code, that is, HTML, JavaScript and CSS from the XFoms code on the server • Emulation layer creates extra payload on server • Multiple postbacks or heavy custom scripting required Future of XForms - Tuukka Haapaniemi

  8. Client side parsing • No need for a separately downloaded plug-in • By using existing JavaScript libraries and adding new APIs to them, parse the XForms code on client • Light on the server • A bit slower on the client • Ajax support – less full postbacks required • Hard to make cross-platform and cross-browser compatible Future of XForms - Tuukka Haapaniemi

  9. Near future of XForms • Current implementations allow to test and learn the technology • New applications can be created with XForms and used through the existing implementations • Easy to transform if/when native support arrives • Intelligent usage of supported technologies possible • Strong ground through being a W3C standard Future of XForms - Tuukka Haapaniemi

  10. Future of native XForms • FireFox • Has a good plug-in created close to the browsers core • Implements most of XForms’ requirements • Is constantly rising in ”market share” (44%, Oct 2008) • Microsoft Internet Explorer • Has one of the best plug-ins • Microsoft has a competing product: InfoPath • Could lose its market leader status (47,1%, Oct 2008) • Opera and Apple unenthusiastic Future of XForms - Tuukka Haapaniemi

  11. Questions & discussion Future of XForms - Tuukka Haapaniemi

  12. Thank you! Future of XForms - Tuukka Haapaniemi

More Related