RE: label in message

Hi Leigh,

I agree we do need to get around to dialog.

However, message is not always implemented by alert, for example its 
implementation in the Ubiquity XForms processor is the more modern 
dialog-like UI control that you describe.  And yet we still can't control 
the dialog caption in such a simple case.  Regardless of when dialog shows 
up, I'd still advocate this twiddle of message as a simple and minor 
dot-release fix.

As for dialog, we did a huge triage to separate 1.2 from 2.0 features, and 
in the interest of higher productivity, all manner of features like dialog 
have gone to 2.09.  Basically, if it is a small fix to an existing 
feature, it belongs in 1.2, but if it is a larger feature it is in 2.0. 
There is nothing stopping interested working group members from developing 
some content, and the place to do that for dialog is [1]

[1] http://www.w3.org/MarkUp/Forms/wiki/Dialogs

But our problem is that we are not even getting very much velocity getting 
through 1.2 because we are getting very little weekly effort from most 
working group members beyond coming to the telecon, and we'll need to fix 
that first. 

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: 
http://www.ibm.com/developerworks/blogs/rss/JohnBoyer?flavor=rssdw





From:
"Klotz, Leigh" <Leigh.Klotz@xerox.com>
To:
John Boyer/CanWest/IBM@IBMCA, <public-forms@w3.org>
Date:
01/07/2009 10:24 AM
Subject:
RE: label in message



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.
 
Leigh.

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: 
http://www.ibm.com/developerworks/blogs/rss/JohnBoyer?flavor=rssdw