15:40:18 RRSAgent has joined #forms 15:40:18 logging to http://www.w3.org/2010/11/10-forms-irc 15:40:20 RRSAgent, make logs public 15:40:20 Zakim has joined #forms 15:40:22 Zakim, this will be IA_XForms 15:40:22 ok, trackbot; I see IA_XForms()11:00AM scheduled to start in 20 minutes 15:40:23 Meeting: Forms Working Group Teleconference 15:40:23 Date: 10 November 2010 15:56:49 pfennell has joined #forms 15:58:59 nick has joined #forms 15:59:14 zakim, code? 15:59:14 the conference code is 93676 (tel:+1.617.761.6200 tel:+33.4.26.46.79.03 tel:+44.203.318.0479), nick 15:59:58 I'll be on the call in the next five minutes. 16:00:10 IA_XForms()11:00AM has now started 16:00:17 +??P9 16:00:30 zakim, I am ??P9 16:00:30 +nick; got it 16:00:44 zakim, dial steven-617 16:00:44 ok, Steven; the call is being made 16:00:45 +Steven 16:01:35 Agenda: http://lists.w3.org/Archives/Public/public-forms/2010Nov/0010.html 16:01:53 Regrets: Erik, Uli 16:03:15 +Leigh_Klotz 16:04:47 John_Boyer has joined #forms 16:05:25 zakim, code? 16:05:25 the conference code is 93676 (tel:+1.617.761.6200 tel:+33.4.26.46.79.03 tel:+44.203.318.0479), John_Boyer 16:05:31 +John_Boyer 16:06:53 -nick 16:07:10 +[IPcaller] 16:07:21 zakim, I'm IPCaller 16:07:21 I don't understand 'I'm IPCaller', nick 16:07:25 zakim, [IP is nick 16:07:25 +nick; got it 16:07:39 zakim, who is on the phone? 16:07:40 On the phone I see Steven, Leigh_Klotz, John_Boyer, nick 16:08:16 zakim, who is choppy? 16:08:16 I don't understand your question, klotz. 16:09:02 bind nodeset="age" constraint=". <= 65" 16:09:16 bind nodeset="age" constraint=". >= 18" 16:10:18 bind nodeset="age" constraint=". >= 18" alert="You must be at least 18" 16:10:30 and similarly alert="you must be less than or equal to 65" 16:11:12 just for illustrative purposes 16:12:03 + +44.782.483.aaaa 16:12:22 zakim, aaaa is pfennell 16:12:22 +pfennell; got it 16:12:27 Nick and Leigh: need a way to separate UI from presentation 16:12:37 16:13:25 Steven: I feel a similar problem with select/select1, where we hardwire esp. values in the UI where they should be in the model 16:14:02 Steven: This is the other direction but similar in that you have to repeat yourself at both UI and model levels 16:14:18 Steven: part of a larger story about separation of model and UI 16:16:04 Leigh: If you had the xforms-invalid event that included the bind ID of the constraint that failed, 16:16:17 Leigh: not necessarily xforms-invalid 16:16:43 John: breaks because alert not tied to xforms-invalid 16:18:45 John: but logical equivalent of css pseudo-class is something we're free to implement as being always correct, and so it can be tied to whether you show the alert 16:20:26 If you go from invalid because of input 17 to invalid because of input 67, then you don't get an xforms-invalid because the UI control goes from invalid to invalid 16:21:20 Steven: that needs fixing 16:25:38 It is a result of us considering invalidity as a monolithic property 16:25:43 John: you could get xforms-invalid with two different context infos, then that would conflict with UI events improvements, which are attempting to eliminate duplicate versions of such events 16:27:25 Leigh: maybe you could use the calculation engine 16:27:39 John: yes that's how I got to using a pseudo MIP syntax 16:27:49 Steven: You mean the attribute on the bind 16:27:51 John: Yes 16:28:47 John: would be nice if you could configure an alert MIP using codes that could be referenced by alert at the UI level 16:29:07 ... 16:29:37 ... Too young! 16:31:26 s/,/./ 16:31:31 Maybe you could say that UI alert ref="X" is a reference to the alert message associated with thenode 16:31:40 Exactly 16:32:15 Broken due to X 16:32:36 s/.../ref="some node" 16:33:12 Too young 16:33:21 Steven: automatically gets the alert from above 16:33:27 yes 16:34:36 Nick: But if you want to style it, then it needs to be in the UI 16:34:43 Steven: It is copied to the UI 16:35:29 John: wouldn't this type of alert show up in UI as a pseudo element? 16:35:50 Nick: yes but you'd also need to be able to get it in the error summary 16:36:19 John: Yes, this is where we'd need to issue an xforms-invalid for an invalid control because the reason changed 16:36:46 Nick: Putting just text is insufficient due to translation needs 16:36:59 John: you could put a ref on the alert in the bind 16:37:04