W3C home > Mailing lists > Public > public-forms@w3.org > January 2009

RE: label in message

From: Klotz, Leigh <Leigh.Klotz@xerox.com>
Date: Wed, 7 Jan 2009 10:22:47 -0800
Message-ID: <E254B0A7E0268949ABFE5EA97B7D0CF406ADEC4A@USA7061MS01.na.xerox.net>
To: "John Boyer" <boyerj@ca.ibm.com>, <public-forms@w3.org>
Most people these days don't use the Javascript alert function anyway.
Take a look at any site developed in the past two years, and you'll see
it uses div and css and layers to display full HTML content, including
forms, on top of the regular content which is itself grayed out.  XForms
is behind the curve by not having a version of message or dialog that
has full content.  
So again, my point of view is that we should solve the event dispatch
issue that prevents us from having Orbeon's xxf:dialog, or think of
another way of doing it with syntactic sugar a la XForms for HTML for
switch/case or group relevance, and stop trying refine the small beer we
get from xf:message.


From: public-forms-request@w3.org [mailto:public-forms-request@w3.org]
On Behalf Of John Boyer
Sent: Wednesday, December 17, 2008 11:24 AM
To: public-forms@w3.org
Subject: label in message

Dear Forms Working Group, 

In the case of modal and modeless message actions, there has been no
standardized way to specify the caption bar content. 

In XForms 1.2, shouldn't we just add the label element as a potential
child element of the message action? 

This would give us the freedom to specify exact text or to obtain the
text from the instance data.  Granted someone *could* try to put very
elaborated content, including images, into the caption bar, but we could
make it clear that simple char data is required to implement and more
elaborated content is optional. 

In the ephemeral message case, the label content could simply be
prepended to the other content. 

Finally, this might be seen as the "long hand" of having a simple label
attribute for elements like message, as well as UI controls.  Currently,
"XForms for HTML" proposes such an attribute for form controls, but it
seems natural to extend the attribute to anything that allows the label
element as a child. 

Thanks for considering this. 

John M. Boyer, Ph.D.
STSM, Interactive Documents and Web 2.0 Applications
Chair, W3C Forms Working Group
Workplace, Portal and Collaboration Software
IBM Victoria Software Lab
E-Mail: boyerj@ca.ibm.com  

Blog: http://www.ibm.com/developerworks/blogs/page/JohnBoyer
Blog RSS feed:
Received on Wednesday, 7 January 2009 18:24:26 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:13:59 UTC