14:36:07 #startmeeting 14:36:07 Meeting started Thu Aug 4 14:36:07 2011 UTC. The chair is API. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:36:07 Useful Commands: #action #agreed #help #info #idea #link #topic. 14:36:30 #topic possibly add a children-invalidated even 14:36:39 well, this is somewhat a technical topic 14:36:54 mgorse, ? 14:36:58 you added that point 14:37:11 yeah, I added it in response to an email that fregl sent out 14:37:23 since, for kde, when removing a child, it no longer has access to the child's index 14:37:46 so he suggested having an event that would just say that children are invalidated 14:37:53 hi, great 14:37:57 insted of children-remove? 14:38:05 I was just wondering how to tackle this 14:38:12 but this would mean that ATs might not see children-changed::remove events, for instance, so need to discuss it 14:38:22 my problem is mostly that passing the child index along makes things hard 14:38:25 well, fwiw some weeks ago we talked with Company, and he is not sure about the index stuff 14:38:34 as some widgets don't have inherently a order 14:38:38 another option might be for the app-side AT-SPI implementor to send -1 for the detail, and then libatspi would fill in the index if it has the accessible cached 14:38:51 but, at least for MANAGES_DESCENDANTS objects, it won't have the child cached 14:38:59 mgorse: that would work for me 14:39:20 so would these be MANAGES_DESCENDANTS objects fregl? 14:39:23 for manages descendants I would think we shouldn't send child removed/added 14:39:28 joanie: no 14:39:47 it is a general thing in how object deletion works in the case of Qt in many cases 14:40:00 fregl, so that -1 is an option for you? 14:40:13 I mean, send -1 on the index if it is not possible to send the proper one 14:40:17 the parent get's it's pointer to the child removed and the child still knows the parent when I get the notification 14:40:26 API: yes, the -1 as detail would be perfect 14:40:43 and when it's not cached, all should be fine anyway as far as I understand 14:40:44 ok, so I guess that we can assume that in general: 14:40:46 and having at-spi deal with it would be perfect 14:40:48 and update the documentation: 14:40:50 http://developer.gnome.org/atk/unstable/AtkObject.html#AtkObject-children-changed 14:41:06 adding that -1 will be sent if it is not possible to know the index 14:41:19 mgorse, do you agree? 14:41:22 sweet 14:41:22 hmm, stupid question 14:41:27 you proposed that ;) 14:41:27 Having AT-SPI fill in the index might not always work or be easy, though 14:41:40 well, what is the index used for? 14:41:50 ie, if a children-changed:add event was send for the object, would it include the object path of the added child? 14:41:53 mgorse: we can punt in the worst case 14:42:19 fregl: depends on the app 14:42:24 if not, then the child won't be cached, unless AT-SPI were to ask for the child, which I'm not sure is what we want, either 14:42:28 often we don't care 14:43:14 in the case of impress I think the index is going to prove handy in terms of being able to communicate slides and placeholders that were just removed 14:43:22 I thought the whole purpose of this function was to just let the app know that the thing is no longer available 14:43:33 I guess we could always do that for now, have KDE send -1 for the detail, and AT-SPI would fill in the index if it has it cached, and deal with it later if it winds up causing problems for someone 14:43:38 but what thing fregl? 14:43:51 without the index we know that one of the children of the object went away 14:44:08 if we care which one (i.e. to say 'slide 5 deleted') 14:44:09 mgorse, as I said Company is not also sure about that index 14:44:10 joanie: no, you also get the path of the removed child 14:44:11 we don't know 14:44:24 the path? 14:44:29 joanie: yes, the path 14:44:30 but not the index? 14:44:31 although I guess that in the same way that we can document that -1 should be used if not index is available 14:44:34 the dbus path 14:44:44 who is we? 14:44:45 we should also said that this would be the lesser evil 14:44:49 I'm an AT 14:44:59 joanie: at-spi dbus 14:45:03 so the other side 14:45:14 fregl: When a child is added, do you send the path? I remember you talking about not wanting to instantiate objects unless they're needed, and getting a path requires instantiating an object 14:45:43 mgorse: actually we worked around that by patching the qt dbus implementation for this 14:46:16 I think it is very silly anyway - right now I send: parentpath children-changed:add index 0 childpath 14:46:24 oh okay. If you send the object path and a children-changed event when an object is added, then it should be cached, unless it has MANAGES_DESCENDANTS 14:46:24 so you get redundant information 14:46:52 ok 14:47:03 I really need to read the atspi code more 14:47:10 but all seems fine now 14:47:41 right now I send -1 as index for object removed already and that probably doesn't work 14:47:54 Anyway, I guess we can conclude this / add a #info 14:48:00 great 14:48:46 #info If an app sends -1 for the detail for a children-changed, we will assume that the index is unknown 14:48:49 yes please 14:49:01 my current state is that I want to release a beta and get people to test for real now. I got startup time and memory usage to almost nothing. 14:49:16 #info mgorse will modify libatspi to fill in the index when possible (ie, when it has the child cached, which it will not for trees with MANAGES_DESCENDANTS for instance) 14:49:29 mgorse: you rock! 14:49:31 (woo hoo fregl! Congrats!!!) 14:49:44 #info AtkObject:children-changed documentation will be updated, as this could be also used on ATK implementors 14:49:54 well, anything else? 14:49:55 by whom API? 14:49:59 I can do that 14:50:02 tables/trees with millions of lines cause no delay any more, that was what worried me :D 14:50:14 well in fact it is more an action item 14:50:19 but that just a nitpick 14:50:21 #action Piñeiro will update the documentation 14:50:21 Oh; that's an improvement over gtk :) 14:50:36 API it's a nitpick to you who doesn't deal with minutes :-P 14:50:42 anything else in this point? 14:52:05 ... silence .... 14:52:08 ok, moving 14:52:16 #topic CSUN Speaker Proposals 14:52:24 API no 14:52:26 joanie, you added this poing, AFAIK 14:52:27 no? 14:52:35 clown: added stuff 14:52:38 hmm, last minute changes ;) 14:52:41 I mean we could do this out of order 14:52:45 but... 14:52:49 #topic quick update on gs-mag 14:52:52 sure. I think I put my addition in the wrong place on the agenda, as it relates to 3.2 progress. If you want to postpone until we deal with 3.2 progess.. 14:53:05 clown: please go on 14:53:08 no problem, I just have that page open 14:53:15 we can go in order 14:53:17 clown please 14:53:23 okay. it's fairly quick anyhow. I'll just add some #infos. 14:53:33 #info Joseph submitted a new patch for the zoom options dialog in universal access. 14:53:40 #info https://bugzilla.gnome.org/show_bug.cgi?id=643086#c27 14:53:40 04Bug 643086: normal, Normal, ---, control-center-maint, NEW, Universal access: add dialog for zoom options 14:53:49 #info awaiting review. 14:53:53 and... 14:53:58 #info Re: Joseph's invert video patch for gs-mag 14:54:04 #info https://bugzilla.gnome.org/show_bug.cgi?id=639851#c8 14:54:04 04Bug 639851: normal, Normal, ---, gnome-shell-maint, UNCONFIRMED, Magnifier: Add brightness and contrast functionality. 14:54:09 #info suggestion is to move it to Clutter. 14:54:40 that last one is a bit of a surprise -- it would be cool if anyone who used Clutter had access to it. 14:54:47 brightness and contrast funcionality on clutter? 14:55:02 yes, and lightness inversion. 14:55:05 something like a property on the actor or the stage? 14:55:14 yes, exactly. 14:55:25 there already is, in clutter, various tint and other effects. 14:55:38 and an abstract class for any effect. 14:55:49 well, the good thing is that would allow to access to those effects to more apps 14:55:55 more easily I mean 14:55:58 I just implemented a specific object for the effects needed for the magnifier. 14:56:05 yes, exactly API. 14:56:38 #action Joseph to reply on bug to say, "yes, let's move these effects to clutter". 14:56:42 done. 14:57:08 ok, more questions, comments, doubts in this point? 14:58:30 #topic CSUN Speaker Proposals 14:58:31 joanie, ? 14:58:37 Thanks API 14:58:44 I'll #info to be efficient. 14:59:14 #info While we are still waiting for the budget to be approved, the treasurer and Board have not yet told us we are insane. 14:59:34 Just to clarify, are we talking about the conference end of Feb to March in San Diego 14:59:35 ? 14:59:39 #info We anticipate being able to send two speakers to CSUN, the key being "speakers" 14:59:41 heidi yes 14:59:49 THanks 15:00:06 heidi, he have been talking about that conference last meeting, we decided to not use the budget for a booth 15:00:07 #info CSUN call for papers typically opens in September. It's now August. 15:00:17 but it would be still interesting to send peoople to talk about GNOME 15:00:30 #info Now might be the time for anyone who would make a good speaker to consider speaking and thinking about topics. 15:00:33 (done) 15:01:37 I will use the "lets use native english speakers" poker ;) 15:01:46 hahaha 15:02:01 I will suggest that is nonsense. 15:02:16 * clown wonders how many native english speakers are present. 15:02:24 exactly 15:02:30 lalala 15:02:40 jjmarin: ;-) 15:02:42 * clown there's a native english singer present. 15:02:54 I'm a tenor :-) 15:03:02 well, it seems that there aren't too many people there 15:03:10 anyway, we don't have all the people here 15:03:13 * heidi looked at this conference last year and it is in direct conflict with the main CS educators conference and can't go 15:03:17 for example, eitan usually goes there 15:03:24 well, it's something for me to contemplate while on vacation next week. 15:03:33 clown: +1 15:03:36 so how about send a mail to gnome-list abou this? 15:04:02 and that clown comment is also a +1 to my proposal of use the ml 15:04:11 #action Joanie will send a mail to gnome-accessibility-list suggesting people be thinking about presenting at CSUN. 15:05:03 that ai is brought to you by the suffix -ing 15:05:47 I could redo my fosdem talk on dasher/opengazer/nomon/ticker ? 15:06:10 prlw1: I've not seen the talk, but potentially, yes. 15:06:25 like I said, call for papers is not for a month 15:06:31 but time travels quickly 15:06:43 so I'm asking people to start pondering the possibilities now 15:07:58 joanie, so the steps are (1) propose a paper, (2) get confirmed as a speaker, (3) apply to gnome-foundation? 15:08:10 yup 15:08:26 any chance gf will say "no" at step 3? 15:08:41 or, you could be a confirmed speaker, but not receive funding. 15:08:43 assuming our budget gets approved, which I think it will 15:08:52 ok 15:08:53 we have budgeted two speakers 15:08:56 from our team 15:09:07 including the possibility they might need to travel from Europe 15:09:42 Are we budgeting for people to attend the whole conference? Or just come one night in order to give a presentation? 15:09:46 and I cannot imagine our team going crazy and submitting tons of papers that get accepted. 15:10:10 i can imagine it. but I doubt it will happen that way :-) 15:10:10 mgorse: more than a night, less than the full conference 15:10:20 hah 15:10:59 for fy2013 we budgeted much more for CSUN 15:11:25 in the hopes that we'll have a real "story to tell" then 15:11:58 * clown once upon a time ... 15:12:07 in a galaxy far, far away 15:12:17 API the natives are getting restless 15:12:20 I think we can move on 15:12:28 yes, we don't have much time 15:12:31 On a related note, does anyone know the dates for the GNOME Summit in Boston this fall? 15:12:38 do you want some #infos for the last chitchatting? 15:12:42 heidi: almost certainly columbus day weekend 15:12:48 API not really 15:12:49 lol 15:12:56 joanie: Thanks, last year it wasn't for some reason... 15:12:58 ok 15:13:06 piggybacking on another event 15:13:15 #topic Testing Distro 15:13:21 heidi: Linux Plombers was in Boston last year, and it looks like it moves around, so it won't be there this year 15:13:26 is there something to talk about it? 15:13:28 Yeah, I added that one 15:13:35 joanie: Thanks 15:13:41 I'm going to be my "direct" self I'm afraid :-/ 15:13:48 so.... testing distro was super useful 15:13:52 and all kinds of awesome 15:14:06 but I think most of us (all of us but clown???) are no longer using it 15:14:22 and Javi is having difficulties spinning the "last" one 15:14:38 so I'm wondering if it is time to move on w.r.t. the testing distro 15:14:48 yes, I am waiting for the latest spin -- "we" promised it to AEGIS europe for their user testing. 15:14:48 clown? others? 15:15:10 alas, we need it. 15:15:14 aleiva: jjmarin: is jhernandez in shouting distance? 15:15:37 is korn here? 15:15:50 what kind of problems with the testing distro is jhfernandez having? 15:16:08 he was also very interested in having it as a basis for some other a11y stuff. 15:16:23 clown: Is he willing to pay Emergya to do this work? 15:16:24 joanie: nop. he's a at home. He's a little bit sick I'm afraid 15:16:54 clown: because it seems to me that if the "team" who needs it is really AEGIS because Peter wants it 15:17:06 and Javi is crazy busy (and sick! :-( ) 15:17:11 and having build problems 15:17:22 clown: aleiva you see the above? 15:18:20 �sorry, rebooting 15:18:35 API getting back to your question, it's come up in the minutes of previous meetings. Some of it is, I believe, packaging issues. Others is that the build service goes down a lot. 15:18:46 aleiva: meaning you are back now? 15:18:53 or going away? 15:18:56 just back now 15:20:03 #info Given the amount of trouble Javi has been having with the testing distro "final spin," she questioned who all is using it. 15:20:29 #info Joseph indicated that it is required, "promised to AEGIS europe for their user testing." 15:20:55 well, we're volunteers 15:21:05 so, when we "promise" something exactly? 15:21:15 #info Joanie thinks that AEGIS user testing, while valuable, goes well beyond the scope of GNOME Accessibility Team needs and what the volunteers (i.e. Javi) can be asked to do. 15:21:19 aleiva: patience 15:21:42 the mother of science 15:21:43 :-) 15:22:11 :) 15:22:20 well, anything else in this point? 15:22:29 ugh 15:22:29 anywy, we're open to any talk about this 15:22:31 API: nop 15:22:35 everyone just wait ffs 15:22:36 ;-) 15:22:44 * API stops to poke people 15:23:06 #info Joanie would encourage the AEGIS testing folks to find some other means for achieving their needs/goals in this area. 15:23:16 done. 15:23:18 sorry 15:23:27 language is such a delicate thing 15:23:29 ;-) 15:25:57 * API API start to poke people again 15:26:01 ok, anything else? 15:26:25 nope 15:26:28 nop 15:26:54 ok, 15:27:00 #topic miscellaneous time 15:27:14 so, someone has something to say 15:27:17 short 15:27:20 not scheduled? 15:27:35 see you guys at berlin :-) 15:28:31 see you! 15:28:54 \o/ 15:30:05 * heidi waves 15:30:23 well as is seems that nobody needs to add anything 15:30:31 I will close the meeting 15:30:35 #endmeeting