17:32:41 RRSAgent has joined #ua 17:32:41 logging to http://www.w3.org/2006/10/19-ua-irc 17:52:04 JR has joined #ua 17:53:27 WAI_UAWG()2:00PM has now started 17:53:34 +Jim_Allan 17:53:56 meeting: UAWG conference call 17:54:08 chair: JAllan 17:54:17 scribe: JR 18:00:03 +Jan_Richards 18:02:20 +[IBM] 18:02:51 cklaws has joined #ua 18:03:00 zakim, [IBM] is cklaws 18:03:00 +cklaws; got it 18:11:45 Topic: 9.2 Provide user interface focus (P1) 18:16:28 CL: IBM sees UI as diff from content. 18:16:43 CL: UI handled better by MSAA etc 18:17:32 JR: (pre-CL comments) read from email (http://lists.w3.org/Archives/Public/w3c-wai-ua/2006OctDec/0010.html) 18:17:45 JR: Might we split like ATAG? 18:17:48 JA: Like that 18:17:59 CL: Also split content into static and dynamic 18:18:25 CL: OS widget sets have solved many problems... 18:18:48 CL: But firefox diff because it is created by XUL...not OS widgets 18:19:22 JA: 7.1 covers a lot of this 18:20:56 JA: UI focus does seem visual to me. 18:21:02 JR: THat's also in 10.2 18:21:24 JA: Should we be bold and assume 9.2 is done. 18:22:28 JR: Maybe some things could be rolled together? 18:22:38 HR: e.g. "Provide a user-controlled (content|user interface) focus" 18:22:43 HR=JR 18:23:06 CL: Should add that if creating a CUSTOM UI you still need to satisfy. 18:23:58 action: ja add technique about if creating a CUSTOM UI you still need to provied a user interface focus 18:24:19 CL: Also we talked last week about AJAX etc widgets... 18:24:36 JA: Might some of the UI be created with AJAX etc? 18:27:08 JR: Maybe if UA stuff added to content in a larger wrapper. 18:27:15 CL: Looked at that. 18:27:29 JR: could a UA crate UI panes to provide addtional funtionality (history list) that was created in AJAX 18:28:04 JR: Maybe that would be considered content? 18:28:10 CL: its a lot of work and it is very slow. 18:28:14 CL: Confusing since code may be on server. 18:29:37 CL: That's what Google is doing - eg office apps as web pages that edit other docs 18:30:00 JR: go to a website, that provide a user interface to manipulate web content in novel ways, then this shell that renders in a client UA becomes a UA 18:30:27 CL: ALl controls in Web page, not in browser 18:31:17 JR: Is this USER AGENT content or CONTENT able to browse 18:31:38 CL: COmplicated when widgets pulled into content from elsewhere 18:33:38 CL: Complicates 9.2 18:33:51 CL: Flash is also like this. 18:35:20 CL: Flash player would have to implement MSAA 18:35:54 CL: Content layer is developer who doesn't need to know C++ etc, instead uses markup, scripting etc 18:37:36 JR: Had same plethora of tools in ATAG dev 18:38:20 CL: UA is conveying information about widgets, tools, and functionality, CONTENT is more about the actual information being conveyed 18:39:55 CL: Long term gol to separate content from interaction from presentation 18:40:46 JA: Interested in CL's "layers diagram". 18:40:50 JR: Me too. 18:42:29 CL: Even more complicated when browser runs in Java or Eclipse - they write to Eclipse - then Eclipse writes to platform.access API 18:43:39 JA: So they have to trust Eclipse... 18:44:12 CL: Eclipse has own widgets paired to lower native widgets with written in accessibility... 18:44:52 CL: But custom widgets in eclipse requires the eclipse custom accessibility that then maps back to native platform 18:47:15 CL: And when use standard widget keyboard access is built in - but Firefox doesn't understand DOJO widget - so accesskeys used 18:50:49 -Jim_Allan 18:50:51 -cklaws 18:50:56 -Jan_Richards 18:50:58 WAI_UAWG()2:00PM has ended 18:51:00 Attendees were Jim_Allan, Jan_Richards, cklaws 18:51:01 Ended early 18:51:20 RRSAgent, make minutes 18:51:20 I have made the request to generate http://www.w3.org/2006/10/19-ua-minutes.html JR 19:02:54 jallan has left #ua 19:04:10 RRSAgent, set logs public 19:04:15 Zakim, bye 19:04:15 Zakim has left #ua 19:04:19 RRSAgent, bye 19:04:19 I see 1 open action item saved in http://www.w3.org/2006/10/19-ua-actions.rdf : 19:04:19 ACTION: ja add technique about if creating a CUSTOM UI you still need to provied a user interface focus [1] 19:04:19 recorded in http://www.w3.org/2006/10/19-ua-irc#T18-23-58