Attachment '20120726_log.txt'

Download

   1 15:59:37 <jhernandez> #startmeeting
   2 15:59:37 <tota11y> Meeting started Thu Jul 26 15:59:37 2012 CET.  The chair is jhernandez. Information about MeetBot at http://wiki.debian.org/MeetBot.
   3 15:59:37 <tota11y> Useful Commands: #action #agreed #help #info #idea #link #topic.
   4 15:59:58 <jhernandez> #topic GNOME 3.6
   5 16:00:31 <clown> okay, jhernandez, here goes.
   6 16:00:39 <jhernandez> clown: ACK
   7 16:00:41 <jhernandez> :]
   8 16:01:05 <clown> #info Joseph fixed the main caret tracking problem in his focus tracker, based on mgorse's suggestions.
   9 16:01:17 <clown> #info the code now tracks the caret.
  10 16:01:58 <clown> #info Joseph, put together a patch, uploaded it to the bugzilla, and emailed the a11y list.
  11 16:03:07 <clown> #info there is still an issue of a delay when focussing on a gnome shell widget (St), and when the Atspi event is returned, it contains no accessible (? or maybe no component).
  12 16:03:24 <clown> #info next step is to try and write it in C.
  13 16:03:42 * clown looks up bugzilla to see what the issue is again with gnome-shell widgets.
  14 16:04:32 <clown> #info there is still an issue of a delay when focussing on a gnome shell widget (St), and when the Atspi event is returned, it contains no component.
  15 16:04:49 * jhernandez wondering about why clown needs to move this code into C
  16 16:05:08 <clown> because it might work?
  17 16:05:10 <clown> :-)
  18 16:05:26 <jhernandez> clown: ACK
  19 16:05:53 <clown> take a look at what API said: https://bugzilla.gnome.org/show_bug.cgi?id=647074#c6
  20 16:05:53 <tota11y> 04Bug 647074: enhancement, Normal, ---, gnome-shell-maint, UNCONFIRMED, GNOME Shell Magnifier should track focus and the caret
  21 16:06:05 <jhernandez> thanks
  22 16:06:08 * jhernandez reading ...
  23 16:06:21 <clown> he doesn't say that it will wokr in C, but that it may be a factor.
  24 16:07:05 <clown> on the other hand, if I rewrite in C and get exactly the same problem, then there is a bug somewhere.  Either in atspi or in St, or in the communication between the two.
  25 16:07:34 * jhernandez got it
  26 16:07:39 <clown> so jhernandez, do you think it should work in JavaScript?
  27 16:07:50 <clown> do you see any reason for the problem?
  28 16:08:02 <clown> off hand, that is.
  29 16:09:04 <jhernandez> I thought that gobject introspection stuff was working fine with javascript
  30 16:09:05 <clown> I really should try joanie's stand alone python version, first.
  31 16:09:20 <clown> yeah, so did I.
  32 16:09:21 <jhernandez> but, I'm a little more pythonic developer
  33 16:10:00 <clown> well, if you see anything, let me know.
  34 16:10:28 <clown> shall I go on?  I have updates for zoom options in 3.6
  35 16:10:44 <jhernandez> clown: I think joanie's suggestion was the best here
  36 16:10:55 <jhernandez> s/was/is
  37 16:11:07 <clown> what is her suggestion?
  38 16:11:18 <jhernandez> < clown> I really should try joanie's stand alone python version, first.
  39 16:11:55 <clown> ah, yes.  I see.  (it's still morning here).
  40 16:12:10 * clown takes his second sip of coffee.
  41 16:12:15 <jhernandez> hehe
  42 16:12:20 <jhernandez> no prob
  43 16:12:23 <clown> anyhow, moving on?
  44 16:12:28 <jhernandez> clown: of course
  45 16:12:43 <jhernandez> :]
  46 16:12:50 <clown> #action Joseph to confirm that joanie's python standalone focus tracker demo still works.
  47 16:13:35 <clown> #info Joseph has uploaded two glade files showing possible UI's for the new color effects in the magnifier.
  48 16:13:39 * clown looks up bug...
  49 16:14:36 <clown> #info, FWIW, Joseph favours this one:  https://bugzilla.gnome.org/show_bug.cgi?id=676817#c5
  50 16:14:36 <tota11y> 04Bug 676817: normal, Normal, ---, control-center-maint, UNCONFIRMED, universal access: Allow to control color-related shader options in the shell
  51 16:14:52 <clown> #info a screen shot of the above is here: https://bugzilla.gnome.org/attachment.cgi?id=219602&action=edit
  52 16:15:26 <clown> #info Joseph has been working on modifying the gnome-control-panel zoom-options.c code to make use of the porposed UI.
  53 16:16:01 <clown> #info that code is nearly ready; hopefully there will be a full patch to attach to bug soon.
  54 16:16:11 <clown> jhernandez:  do you use Fedora?
  55 16:16:26 <jhernandez> nope, I currently use openSUSE
  56 16:16:37 <jhernandez> why?
  57 16:16:46 <clown> maybe you know the answer.
  58 16:17:26 <jhernandez> maybe not
  59 16:17:29 <clown> when I run the latest nightly of gnome-shell, gnome-control-center, and gsettings-desktop-schemas, I get a bug out of dconf.
  60 16:17:32 <clown> :-)
  61 16:17:33 <jhernandez> or maybe for testing purposes?
  62 16:17:48 * clown looks up error message.
  63 16:18:26 <clown> "** (process:17779) : WARNING **: failed to commit changes to dconf: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod:  No such method 'Change'.
  64 16:18:35 <jhernandez> I have my hackbox here, so I could give a try to this
  65 16:19:01 <clown> API suggested that if I launched from the 'recovery terminal' I could get past this.
  66 16:19:40 <clown> unfortunately, he uses ubuntu, which has an recovery terminal option from the login screen.  There he does:
  67 16:19:52 <clown> jhbuild run dbus-launch --exit-with-session gnome-session
  68 16:20:06 <jhernandez> yup
  69 16:20:25 <clown> Fedora's login screen doesn't offer that option.  So, I'm  puzzled as to how to make do the dbus-launch.
  70 16:20:42 <clown> I can do it from any old terminal *after* I log in, but that doesn't help.
  71 16:21:10 <clown> it's "too late", I think.
  72 16:21:32 <jhernandez> hmm
  73 16:21:50 <clown> aren't you glad you contacted me for a light meeting?
  74 16:21:53 <clown> '-)
  75 16:23:34 <jhernandez> of course!
  76 16:23:54 <jhernandez> sorry, I was moving to another room
  77 16:24:13 * jhernandez looking for a link
  78 16:25:00 * clown hoping you find it
  79 16:25:25 <aleiva> ey
  80 16:26:36 <jhernandez> well, the link I was looking for is about how to get running your gnome-session under jhbuild from scratch
  81 16:27:22 <clown> ah, okay.
  82 16:28:34 <jhernandez> about the dconf error message ... maybe out-of-date dconf version?
  83 16:29:05 <jhernandez> dunno
  84 16:29:27 <jhernandez> or, maybe asking the wrong dbus?
  85 16:29:42 <clown> actually, dconf is "too new".
  86 16:30:03 <clown> rather, the system's dconf is "too old"
  87 16:30:49 <clown> when I do 'jhbuild run gnome-shell —replace", I'm running the gnome-shell under its "install" directory
  88 16:31:14 <clown> and that environment expects to use the latest dconf, but that's not the one running.
  89 16:31:28 <clown> API's technique is a way to get the new one running from log in.
  90 16:31:55 * clown looks up API's email.
  91 16:32:20 <clown> quoting API:
  92 16:32:22 <clown> In fact I think that the problem is due last
  93 16:32:22 <clown> changes on DConf, so if you are using gnome-shell and all stuff from
  94 16:32:22 <clown> jhbuild, it doesn't work fine with the settings-daemon from the system.
  95 16:32:22 <clown> So in summary you should be using gnome-settings-daemon from jhbuild
  96 16:32:23 <clown> too. In order to get that I login using the recovery terminal and then I
  97 16:32:25 <clown> execute a new session using my jhbuild stuff:
  98 16:32:27 <clown> jhbuild run dbus-launch --exit-with-session gnome-session
  99 16:34:11 <jhernandez> well, I used to run the latest gnome code by adding a new session to the system and then logging into the session by selecting my jhbuild's gnome session as default session
 100 16:34:29 <jhernandez> too "sessions" i think ...
 101 16:34:32 <jhernandez> :P
 102 16:34:48 * jhernandez looking again for this link
 103 16:35:11 <aleiva> clown: how is going the implementatino of tracking?
 104 16:35:27 <aleiva> I'm thinkin in implement a skel of a "emitter" of tracking information
 105 16:35:28 <aleiva> into gs
 106 16:35:36 <aleiva> in C
 107 16:35:38 <aleiva> GObject
 108 16:35:40 <aleiva> glib
 109 16:35:49 <clown> aleiva, not much news — I was going to try and port the stuff to C/GObject, and see if that worked better.
 110 16:35:50 <jhernandez> http://developer.gnome.org/jhbuild/stable/jhbuild-and-gnome.html.en
 111 16:36:18 <clown> But, my time is currently taken up by the prefs dialog for the new brightnesss/contrast effects in gnome-control-center.
 112 16:36:18 <jhernandez> clown: I did it by following these instructions
 113 16:36:21 * clown reads log.
 114 16:36:56 <clown> I think we are thinking the same thing, aleiva (re:  focus tracking C/GObject).
 115 16:36:58 <aleiva> clown: what do you think if I try that "emitter" thing and you imelement the client
 116 16:37:05 <aleiva> and settings
 117 16:37:13 <aleiva> and gs stuff that I think you know better than me
 118 16:37:18 <aleiva> after the contrast bug :-P
 119 16:38:06 <clown> aleiva, I kind of wanted to try it, but, in the interest of time, go ahead.
 120 16:38:49 * clown takes a look at jhernandez's link
 121 16:39:59 <clown> aleiva, you are going to make the focus/caret tracker such that it will support connect()?
 122 16:40:19 <aleiva> something like that
 123 16:40:25 <aleiva> or callback like
 124 16:40:35 <aleiva> whatever gnomeshell people usually do
 125 16:40:42 <aleiva> in this cases
 126 16:40:45 <clown> that's what I was trying to do with the JavaScript version — receive events from Atspi, and relay them out using the standard gnome signal technique.
 127 16:41:36 <clown> so, my focus tracker emit()s events, and allows clients to connect()/disconnect() to the tracker.
 128 16:41:51 <aleiva> yeah, that's the logical way
 129 16:42:15 <clown> but, on the atspi side, it  uses the register() technqiue.
 130 16:42:53 <clown> okay. give me a footnote :-)
 131 16:44:33 <aleiva> I'm at guadec and I can talk with gs people I think
 132 16:44:37 <aleiva> that will boost this
 133 16:44:40 <aleiva> I hope
 134 16:44:51 <aleiva> I only have one free weekend :-P
 135 16:45:01 <jhernandez> aleiva: go for it!
 136 16:45:32 <clown> indeed.
 137 16:48:43 <clown> jhernandez:  re: the jhbuild instructions, is the relevant section 3.3?
 138 16:50:32 <jhernandez> clown: yes
 139 16:51:13 <jhernandez> maybe this could help you
 140 16:51:14 <jhernandez> dunno
 141 16:51:33 <clown> maybe, I'll see what I can do.
 142 16:51:57 <jhernandez> ok
 143 16:51:58 <clown> 3.3.1 looks like the important part.
 144 16:52:52 * jhernandez nods
 145 16:53:40 <jhernandez> and 3.3.3
 146 16:54:02 * clown looks up his .jhbuildrc file
 147 16:54:49 <clown> okay, I have moduleset = 'gnome-apps-3.6' in my .jhbuildrc.
 148 16:55:48 <clown> I'm thinking I may not need to create this "gnomedev" account, but just to massage my own account as they suggest (and hope that doesn't bork the machine).
 149 16:56:27 <jhernandez> clown: maybe yes ... maybe not :P
 150 16:56:48 <jhernandez> I always create another account for this kind of purposes
 151 16:57:00 <jhernandez> I usually bork my machine
 152 16:57:07 <jhernandez> :P
 153 16:57:32 <clown> yes, another account is safer.  But I want to avoid having to re-build all of 3.6.  It takes hours.
 154 16:57:42 <jhernandez> yes
 155 16:58:19 <clown> anyhow, on another topic, I think the meeting is over?
 156 16:58:43 * jhernandez nods
 157 16:58:55 <clown> actually, let me record some of the things that aleiva just said.
 158 16:59:42 <clown> #info regarding focus tracking, aleiva is going to try to write the tracker in C/GObject/glib
 159 17:00:10 <clown> #info he is going to follow the architecture in Joseph's JavaScript tracker:
 160 17:00:50 <clown> #info taking Atspi events, and exposing them using the standard gnome signal technique (emit(), connect(), disconnect(), etc).
 161 17:01:07 <clown> done, unless aleiva wants to add anything.
 162 17:01:22 <aleiva> nothing more
 163 17:01:25 <aleiva> its ok, thanks
 164 17:01:36 <jhernandez> ok magnifier guys!
 165 17:01:55 <clown> okay, thanks for the collaboration, aleiva!
 166 17:01:57 <jhernandez> :]
 167 17:02:16 <jhernandez> so ...
 168 17:02:29 <jhernandez> clown: do we have more topics?¿
 169 17:02:35 <clown> not from me.
 170 17:02:46 * clown double checks
 171 17:03:16 <jhernandez> #topic Marketing and Fundraising
 172 17:03:33 <aleiva> :-D
 173 17:03:40 * clown wonders where jjmarin is.
 174 17:03:44 <jhernandez> #info today we reached the FoG goal!
 175 17:03:46 <jhernandez> :]
 176 17:04:00 <aleiva> xD
 177 17:04:16 <jhernandez> jjmarin was in a webkit related talk
 178 17:04:18 <clown> cool!
 179 17:04:26 <jhernandez> so ....
 180 17:04:46 <jhernandez> #topic Miscellaneous time
 181 17:04:57 <aleiva> \o/
 182 17:05:01 * aleiva steal the gavel
 183 17:05:03 <jhernandez> clown: do you have some pretty miscellaneous topic?
 184 17:05:15 <clown> nope.
 185 17:05:25 <jhernandez> clown: perfect
 186 17:05:33 <jhernandez> we (aleiva and me need a coffeee)
 187 17:05:34 <jhernandez> :]
 188 17:05:36 <aleiva> ~o/
 189 17:05:50 <aleiva> clown, and the misc joke?
 190 17:05:58 <clown> have a good one, guys.
 191 17:05:58 <jhernandez> xDDD
 192 17:06:00 <aleiva> where's it?
 193 17:06:06 <clown> why did the chicken cross the road?
 194 17:06:15 <aleiva> no idea
 195 17:06:24 <clown> because it was too far to walk around.
 196 17:06:29 <jhernandez> xDDDD
 197 17:06:30 <aleiva> xDDD
 198 17:07:36 <jhernandez> ok, guys, let's end the meeting
 199 17:07:38 <jhernandez> :]
 200 17:07:39 <jhernandez> 3
 201 17:07:41 <jhernandez> 2
 202 17:07:43 <jhernandez> .
 203 17:07:45 <jhernandez> .
 204 17:07:48 <jhernandez> .
 205 17:07:50 <jhernandez> 1
 206 17:07:53 <jhernandez> #endmeeting

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.
  • [get | view] (2021-02-25 09:41:57, 12.4 KB) [[attachment:20120726_log.txt]]
 All files | Selected Files: delete move to page copy to page

You are not allowed to attach a file to this page.