Comments on: Confirmation With XForms http://www.orbeon.com/blog/2006/04/18/confirmation-with-xforms/ XForms Everywhere Thu, 21 Aug 2008 13:54:06 +0000 http://wordpress.org/?v=1.5.1.3 by: ebruchez http://www.orbeon.com/blog/2006/04/18/confirmation-with-xforms/#comment-531 Thu, 20 Apr 2006 19:46:14 +0000 http://www.orbeon.com/blog/2006/04/18/confirmation-with-xforms/#comment-531 Thanks for the comment. In defense of the XForms 1.0 spec though: I am not sure the purpose of a spec in general is to provide code samples. Blogs, articles and books are probably a better place for that. Of course you are free to use good old buttons instead of links :-) That's a good thing about XForms' "intent-driven" user interface: it allows you to very quickly change appearances while keeping the exact same functionality. BTW xxforms:link is non standard, but there is now a suggested way of rendering triggers as links with the use of the "minimal" appearance. Thanks for the comment. In defense of the XForms 1.0 spec though: I am not sure the purpose of a spec in general is to provide code samples. Blogs, articles and books are probably a better place for that.

Of course you are free to use good old buttons instead of links :-) That’s a good thing about XForms’ “intent-driven” user interface: it allows you to very quickly change appearances while keeping the exact same functionality. BTW xxforms:link is non standard, but there is now a suggested way of rendering triggers as links with the use of the “minimal” appearance.

]]> by: amaah http://www.orbeon.com/blog/2006/04/18/confirmation-with-xforms/#comment-530 Thu, 20 Apr 2006 17:04:15 +0000 http://www.orbeon.com/blog/2006/04/18/confirmation-with-xforms/#comment-530 This snippet of code should have been prominent in the XForms 1.0 spec. The point was to move away from javascripting but XForms never acknowledged that Javascript built in the alert and confirm methods. In order to create usable sites, you need to be able to warn the user about actions that are potentially destructive and or costly and give them the opportunity. I have one quibble, the use of appearance="xxforms:link", I say let's stick to buttons ergo: <a href="http://koranteng.blogspot.com/2005/05/unloved-html-button-and-other.html" rel="nofollow">The Unloved HTML and other folktales</a> This snippet of code should have been prominent in the XForms 1.0 spec. The point was to move away from javascripting but XForms never acknowledged that Javascript built in the alert and confirm methods. In order to create usable sites, you need to be able to warn the user about actions that are potentially destructive and or costly and give them the opportunity.

I have one quibble, the use of appearance=”xxforms:link”, I say let’s stick to buttons

ergo: The Unloved HTML and other folktales

]]>