Attachment '20110224_log.txt'
Download 1 15:05 ::: API changed the topic of #a11y-meeting to: http://live.gnome.org/Accessibility/Meetings
2 15:05 < clown> pretty empty room still. is the 7:00 UTC better attended?
3 15:05 <@joanie> heh no
4 15:05 <@API> well clown
5 15:05 <@API> 1. Should we continue having the 07:00/15:00 meeting time split?
6 15:06 >>> clown marvels at his apropos-ness.
7 15:06 <@API> first item is about nuke 7:00 UTC schedule
8 15:06 <@API> when we decided that, we were thinking on people from china and australia
9 15:06 <@API> but, ie, last day
10 15:06 <@API> we were just 4 people
11 15:06 < li> I am ok with that
12 15:06 <@API> two from usa
13 15:06 <@API> two from spain
14 15:07 < li> sorry again for I miss that meeting
15 15:07 <@joanie> three from usa actually
16 15:07 <@API> li, np
17 15:07 <@joanie> Li you're not the only one
18 15:07 <@API> ah yeah, also tbsaunde on the last meeting
19 15:07 <@joanie> if you were, we'd tell you. It's all the people we made this time for.
20 15:08 <@API> anyway, in general, it seems that this 7:00 UTC efforts it is not worth
21 15:08 <@API> also
22 15:08 <@API> having the meeting always at the same time
23 15:08 <@API> would be easier to remember
24 15:08 <@API> every thursday at 15:00 UTC
25 15:08 <@API> no required to go to th ewiki
26 15:08 <@API> the wiki
27 15:08 <@API> to see the schedule of this week meeting
28 15:08 <@API> soo
29 15:09 < clown> API, if it would help, I could make 14:30 UTC. I'm thinking that would be slightly earlier for Europeans.
30 15:09 <@API> apart of li, that already exposed it, opinions about remove 7:00 UTC schedule?
31 15:09 <@API> hmm
32 15:09 <@joanie> all in favor of nuking the 07:00 time, yawn.
33 15:09 <@API> well, and that would be the advantage of just 30 minutes?
34 15:09 >>> clown yawns
35 15:09 < clown> API, yes, "just" 30 min.
36 15:10 < mgorse> It seems fine to me, but I think that we want to keep in mind that we may want to reconsider in the future. People come and go, etc
37 15:10 <@API> and the advantage ...
38 15:10 <@API> mgorse, of course
39 15:10 <@joanie> mgorse: +1
40 15:10 <@API> we are deciding it based on the current state
41 15:10 <@API> if the state changes, we can rethink it
42 15:11 <@API> clown, I still don't understand the advantage about move to 14:30 ...
43 15:12 < clown> API, it's earlier -- take Li for example. It's 11pm there. Would li appreciate starting at 15:30pm ?
44 15:12 <@API> ah ok
45 15:12 <@API> li, ?
46 15:12 < li> clown, yes, if it is not too early for US people
47 15:13 < clown> li, it's okay for this one Canadian.
48 15:13 >>> joanie doesn't minde
49 15:13 < clown> ;-)
50 15:13 <@joanie> mind either
51 15:13 < li> I guess all of our US attendees are from east?
52 15:13 <@joanie> no
53 15:13 <@joanie> mgorse is Central
54 15:13 < clown> good point. makes it difficult for west coasters
55 15:13 < mgorse> It's fine with me
56 15:13 <@joanie> And the west coast people never come
57 15:13 <@joanie> to either time
58 15:13 <@joanie> ;-)
59 15:13 < clown> never mind then.
60 15:14 <@API> ok, so concluding
61 15:14 <@API> moving to a middle term solution
62 15:15 <@API> always at 14:30 UTC
63 15:15 <@API> right?
64 15:15 >>> joanie nods
65 15:15 >>> clown agrees
66 15:15 >>> tbsaunde sure
67 15:15 <@API> ok, so lets move
68 15:15 <@API> Bastien updated the Universal Access Settings and some orca tips. see https://bugzilla.gnome.org/show_bug.cgi?id=638205
69 15:15 <@API> (item 2 btw)
70 15:15 <@API> well, this is just a informative item
71 15:15 <@API> Bastien was working on this bug
72 15:16 <@API> and made some changes on the gsettings thing
73 15:16 >>> clown reading...
74 15:16 <@API> ie, now the gsetting that says if a11y is enabled is toolkit-accessibility
75 15:16 <@API> in the same way
76 15:16 <@API> in the new universal access settings
77 15:16 <@API> thre isn't any "enable accessibility checkbutton"
78 15:16 <@API> as far as I understood Bastien
79 15:17 <@API> now that will be activated if you, for example, activate the screen reader feature
80 15:17 < clown> yes, that's my impression too.
81 15:17 <@API> as usual, it would be good if we test it as part of the "testing gnome3 environment" thing
82 15:17 <@API> well, as I said that was a informative item
83 15:17 <@API> questions, something to add?
84 15:18 <@API> joanie, afaik Bastien also modified orca code due this
85 15:18 < clown> is there ever any reason to turn off a11y once it's on?
86 15:18 <@API> not remember exactly what
87 15:18 <@joanie> yup
88 15:18 < mgorse> Where are these settings set in GNOME3? In gnome-shell?
89 15:18 <@API> mgorse, well, in the Universal Access Settings Dialog ;)
90 15:18 <@API> and yes, you can open it via gnome shell
91 15:18 < clown> is it here: org.gnome.desktop.interface.gschema.xml?
92 15:18 <@API> but you could also do that in the "classic desktop"
93 15:18 <@joanie> api http://git.gnome.org/browse/orca/commit/?id=5ee414ef9c88c37744ffab0ecea3c623d6545ace
94 15:19 <@API> (or fallback mode or whatever)
95 15:19 < clown> yes, it doesn't seem to depend on gnome shell.
96 15:20 <@API> mgorse, yes, it is a dialog included on gnome-control-center
97 15:20 ::: bnitz [~bn128650@gmp-ea-fw-1.sun.com] joined #a11y-meeting
98 15:21 >>> clown waves at bnitz
99 15:21 < li> hi bnitz!
100 15:21 <@API> well, any other question, comment?
101 15:21 < clown> is there ever any reason to turn off a11y once it's on?
102 15:21 < bnitz> Hi everyone
103 15:21 < tbsaunde> clown: if you have it on for testing something?
104 15:22 < clown> it looks like there is no dialog to use to turn it off, if I understand the state of things.
105 15:23 <@API> clown, afaiu accessibility will be turned off if the screen reader is turned off
106 15:23 < clown> so, I'm wondering if that's an issue. Not saying that it is, necessarily.
107 15:23 < clown> API, ah, okay.
108 15:23 <@API> and yes, right now there are reasons to turn off accessibility if you don't require it
109 15:23 < clown> but what if an on screen keyboard, say, is launched?
110 15:24 <@API> well, I told Bastien that the toolkit thing is required when you need any AT tool
111 15:24 < li> what does "turn off" accessibility mean?
112 15:24 < clown> to be even more specific, does Caribou require that a11y be turned on?
113 15:24 < li> quit at-spi2-registryd?
114 15:24 <@API> I guess that a11y will be enabled
115 15:24 <@API> li, yes
116 15:24 ::: aleiva [~gloob@petersburgo.euler.es] joined #a11y-meeting
117 15:24 <@API> it is about at-spi2
118 15:24 <@API> like the current gcont "accessibility" variable
119 15:24 <@API> that basically is used for that (AFAIK)
120 15:24 >>> joanie waves to aleiva
121 15:24 <@API> clown <API> well, I told Bastien that the toolkit thing is required when you need any AT tool
122 15:25 <@API> so I guess that also applies if you start any other AT tool on
123 15:25 < clown> okay (bear with me)...
124 15:25 <@API> this dialog
125 15:25 < li> API, that means disable atkbridge also
126 15:25 <@API> li, yes true
127 15:25 < clown> if both an onscreen keyboard is on, and orca is on, but then orca is turned off -- what's the state of a11y then?
128 15:25 <@API> in this case should be the same
129 15:25 < li> what about gail?
130 15:25 <@API> doesn't start the bridge or gail
131 15:25 >>> clown just trying to see logically how this is supposed to work.
132 15:25 <@API> anyway, at this moment
133 15:26 <@API> the only using directly this gsetting is
134 15:26 <@API> gnome-shell
135 15:26 <@API> and as I said, this requires some testing with a gnome 3 "compliant" environment
136 15:27 < li> I understand we can disable atkbridge, but I don't know how to disable gail either
137 15:28 <@API> li, remember that this is done right know using that .desktop files
138 15:28 <@API> this was an old change also made by Bastien
139 15:28 <@API> the thing is that, IMHI
140 15:28 < li> I mean for applications which has been running already
141 15:28 <@API> IMHO
142 15:28 <@API> there are a lot of doubts about the integration part of the accessibility support
143 15:29 <@API> li, ah ok
144 15:29 <@API> well, I think that in this case we are in the same point
145 15:29 <@API> and it would be required to logout
146 15:29 < li> yes
147 15:30 <@API> well, almost 15 minutes with this item, I will try to summarize it:
148 15:30 < aleiva> API: is it documented somewhere? (about the gnome(3)-shell a11y support)
149 15:30 <@API> aleiva, what do you mean?
150 15:30 < aleiva> the current state
151 15:30 <@API> that a11y would be started if X is true, and Y is true?
152 15:30 < aleiva> wiki, blog
153 15:30 < aleiva> whatever
154 15:30 < aleiva> yes
155 15:31 <@API> aleiva, well, I have pending to make a blog post
156 15:31 < aleiva> API: ok, perfect, thanks
157 15:31 <@API> updating the "gnome shell a11y status" that I made
158 15:31 <@API> on november
159 15:31 <@API> but I would like to solve that orca bug first
160 15:31 <@joanie> :-)
161 15:31 <@API> anyway
162 15:31 <@API> <API> well, almost 15 minutes with this item, I will try to summarize it:
163 15:31 <@API> * Bastien made some changes on the control panel
164 15:32 <@API> * accessibility gsetting was renamed to "toolkit-accessibility"
165 15:32 <@API> * need to test
166 15:32 <@API> anything else, or move to the next item?
167 15:33 < aleiva> one thing, we develop an interesting script to have a working gnome3 environment
168 15:33 < aleiva> I want to release it, should make thing easier
169 15:33 <@API> we == ?
170 15:33 < aleiva> we (my company) with the works about orca
171 15:33 <@API> this is a script focused on the Guadalinfo distribution or just a general purpose script?
172 15:34 < aleiva> API: general gnome-3
173 15:34 < aleiva> API: in fact the project is about orca + gnome3, no more
174 15:34 <@API> well, if you get that working
175 15:34 < aleiva> sure
176 15:34 <@API> it would be useful for out task
177 15:34 <@API> "we need to test a gnome 3 environment"
178 15:34 <@API> not just this gsetting thing
179 15:34 < aleiva> exactly, that's what I want to add ;-)
180 15:34 <@API> s/for out/for our
181 15:34 <@API> ok aleiva , thanks
182 15:35 <@API> so lets move then ...
183 15:35 >>> API checking agenda
184 15:35 <@API> 3. Mattias Clasen gail revamp
185 15:35 <@API> well, in summary
186 15:35 <@API> Matthias was testing gail
187 15:35 <@API> he detected some issues
188 15:35 <@API> and he said that a general review is required
189 15:35 <@API> and it would be use this moemnt
190 15:35 <@API> to move gail to gtk itself
191 15:36 <@API> he has a experimental git branch <I don't have the link here>
192 15:36 <@API> with some of them
193 15:36 <@API> li
194 15:36 <@API> something to add?
195 15:36 <@API> were you able to review this work?
196 15:36 < li> I am working on it
197 15:37 < li> I commit a patch to move gailarrow to gtkarrow yesterday
198 15:37 < li> the branch name is drop-gail
199 15:37 <@API> well, I have just a question
200 15:37 < li> http://git.gnome.org/browse/gtk+/log/?h=drop-gail
201 15:38 <@API> Matthias mentioned that it would be required to review part of the focus management
202 15:38 <@API> code
203 15:38 <@API> I guess that he is talking about the one on gail.c
204 15:38 <@API> it is supposed to be done now
205 15:38 <@API> or after the move?
206 15:39 < li> I think after
207 15:39 <@API> so where this gail.c code will be placed?
208 15:39 < li> this is step 4 in his mail
209 15:39 <@API> or the gail.c will be just moved
210 15:39 < li> I don't think this through now
211 15:39 <@API> ok
212 15:40 < li> but I think as a gtkmodule
213 15:40 < li> there should be a file for initialize
214 15:40 < li> just don't know where we will keep it
215 15:40 <@API> and the final question, you have started to review it and contribute, will you be able to continue to do that?
216 15:41 < li> yes, that's my plan, if nothing with higher priority comes out
217 15:41 <@API> awesome
218 15:41 <@API> this is a good new
219 15:42 < li> I am glad that this move can solve many very old gail bugs
220 15:42 <@joanie> yay!
221 15:42 < li> i filed them even before I become the maintainer :)
222 15:43 <@API> ;)
223 15:43 <@API> well, li, anything else to comment in this point?
224 15:43 < mgorse> It would really be nice if it somehow helps with treeview performance; Matthias implied that it might
225 15:43 < li> nothing for now, I just plan to move the widget one by one
226 15:44 < li> yes, it might be, but for sure this move only create opportunities to do this, much more work are still needed
227 15:44 <@API> mgorse, well, he also mentioned that due the treeview revamp, it would be required to adjust the a11y implementation
228 15:45 <@API> but, ok, we can conclude that this item is finished
229 15:45 <@API> so lets move to next point:
230 15:45 <@API> 4. Your topic here
231 15:45 <@API> ups
232 15:45 <@API> 5. If time allows: AT registration on at-spi2?
233 15:45 <@joanie> lol
234 15:46 <@API> well, this is due a mail that I sent to gnome-accessibility-devel
235 15:46 >>> API searching
236 15:46 <@API> https://mail.gnome.org/archives/gnome-accessibility-devel/2011-February/msg00037.html
237 15:47 <@API> some people already answered this
238 15:47 <@API> like li
239 15:47 <@API> mgorse, did you read that mail?
240 15:47 < li> my only concern is that i don't know what will happen when we create accessible objects for all widgets in all applications at the same time
241 15:47 <@API> joanie, as an AT maintainer it also involves you
242 15:47 <@joanie> :-)
243 15:47 < li> although i think it is a good idea
244 15:48 <@API> li, yeah, this is an issue, as I said this is something that we require to check
245 15:48 <@API> anyway
246 15:48 <@joanie> API the idea sounds good to me, but I'm leaving it up to the Li's and Mike's of this world to comment
247 15:48 < li> we can try it!
248 15:48 <@API> take into accoun that most people that require a11y
249 15:48 < mgorse> looking to look at it again. You want to do this for 3.0?
250 15:48 <@API> will have a11y on all the time
251 15:48 <@joanie> but it sure sounds like the right thing to do
252 15:48 <@API> and that would just allow to start on a11y "on heat"
253 15:48 <@API> so I guess that it would be something that just happen once
254 15:49 <@API> mgorse, yes
255 15:49 < mgorse> Right now AT-SPI2 shouldn't send events over the wire if no one is listening, but it will still listen for gail events...
256 15:49 <@API> instead of create a bug to be added on the "towards atk2.0"
257 15:49 <@API> I wanted to discuss it a little first, to check if it makes sense or if it is stupid
258 15:49 <@joanie> I don't think it's stupid.
259 15:49 <@API> mgorse, well at-spi2 no
260 15:49 <@API> but I guess that the bridge
261 15:49 < clown> makes sense to me, API.
262 15:50 < mgorse> So then we'd load gail and atk-bridge all the time, and only really enable atk-bridge when accessibility is enabled
263 15:50 <@API> send the gail (atk implementor) events to at-spi2
264 15:50 <@API> right?
265 15:50 <@API> hmm, so you are proposing to just avoid the overhead if a11y is enabled instead of a AT registration method?
266 15:50 <@API> mgorse, ?
267 15:51 < mgorse> That's how I was interpreting what you were proposing; it itn's clear to me right now how else we could have it register
268 15:51 < mgorse> so feel free to propose something else
269 15:52 <@API> mgorse, well in the same way that apps
270 15:52 <@API> are added to the register
271 15:52 <@API> I was suggesting that AT tools get also registered
272 15:53 <@API> so just enable the atk-bridge if there are any AT tools there
273 15:53 <@API> anyway, as usual, a11y-meeting it is not the place to discuss technical details
274 15:53 < aleiva> like a dependency counter?
275 15:54 < aleiva> :-)
276 15:54 <@API> aleiva, yeah something like that
277 15:54 < aleiva> go on
278 15:54 <@API> so as this is not the place
279 15:54 <@API> lets discuss it elsewhere
280 15:54 <@joanie> :-)
281 15:54 <@API> but it seems that in general
282 15:54 <@API> people thing that the idea makes sense
283 15:54 <@API> so I will create a bug
284 15:54 <@API> and discuss the details there
285 15:54 <@API> people?
286 15:55 <@joanie> sounds good to me
287 15:55 < li> great
288 15:55 < clown> yah
289 15:55 <@API> ok,
290 15:55 <@API> well, just 5 minutes till the end
291 15:55 >>> clown of the world?
292 15:55 <@API> so
293 15:55 <@API> miscellaneous time
294 15:55 <@API> if someone has something short and valuable to say
295 15:55 <@API> about *accessibility*
296 15:56 <@API> it is your moment
297 15:56 < clown> short (maybe valuable) --
298 15:56 < clown> https://bugzilla.gnome.org/show_bug.cgi?id=642032 Magnifier gsettings have been moved to a more central location (outside of Gnome Shell).
299 15:56 < clown> and...
300 15:57 < clown> https://bugzilla.gnome.org/show_bug.cgi?id=643086 - adding UI for the setting to Universal Access.
301 15:57 < clown> Just FYI.
302 15:57 >>> clown is done.
303 15:57 < tbsaunde> fer asked to poke about an api break for atk on bug bugzilla.gnome.org/show_bug.cgi?id=638377 so we can have sain text update signals so bugzilla.mozilla.org/show_bug.cgi?id=619002 is fixable :)
304 15:58 >>> API checking a lot of bugzilla links
305 15:58 < tbsaunde> :)
306 15:58 < mgorse> Has the code been committed to atk already? And is it okay to add this now?
307 15:59 < tbsaunde> mgorse: code hasn't been commited to atk yet, it would require breaking api freeze, but afaik its is only an addition
308 16:00 < tbsaunde> so, imho it should be fine
309 16:00 <@API> tbsaunde, well, afaik
310 16:00 <@API> fer
311 16:00 <@API> made a change to
312 16:00 <@API> avoid the ABI break
313 16:01 <@API> in his initial patch
314 16:01 <@API> he was modifying the class structure
315 16:01 <@API> adding the signals slots
316 16:01 <@API> and then he modified it
317 16:01 <@API> to avoid that
318 16:02 < tbsaunde> API: ok, that sounds familiar, but I'm just the messanger :-)
319 16:02 <@API> ok
320 16:02 <@API> well
321 16:02 <@API> over time
322 16:03 <@API> so if nobody wants to add anything ...
323 16:03 < tbsaunde> API: sorry, I had thought fer put it on the agenda until 30 minutes ago :/
324 16:03 <@API> tbsaunde, well we have miscellaneous time for this kind of things
325 16:03 < tbsaunde> yup
326 16:05 <@API> well, meeting over!!
327 16:05 <@API> thanks to be here
Attached Files
To refer to attachments on a page, use attachment:filename, as shown below in the list of files. Do NOT use the URL of the [get] link, since this is subject to change and can break easily.You are not allowed to attach a file to this page.