[16:10] <Nafai> good morning
[16:17] <jcastro> morning Nafai!
[16:18] <Nafai> Morning!
[16:19] <Nafai> How are you jcastro?
[16:19] <jcastro> good, just a bad monday, heh
[16:19] <Nafai> :)
[17:31] <doctormo> ivanka1: Mark has said that the left aligned buttons are that way for some future design considerations. Do you know what those are?
[18:31] <jcastro> jpetersen: ping
[18:31] <jpetersen> jcastro, yes
[18:31] <jcastro> do you have the upstream bug for the g-s-d app indicator patch handy?
[18:32] <jcastro> or since it was only partially implemented did we not push that up?
[18:32] <jpetersen> jcastro, i am just looking
[18:33] <jpetersen> https://bugzilla.gnome.org/show_bug.cgi?id=610867
[18:33] <ubot4> Gnome bug 610867 in plugins "Support for application-indicators/StatusNotifierIcon" [Enhancement,Unconfirmed]
[18:34] <jpetersen> jcastro, that was the patch which included the gnome keyboard patch
[18:35] <jcastro> jpetersen: ok
[18:35] <jpetersen> jcastro, I will attach the current patch (without the keyboard indicator) to that bug report
[18:35] <jpetersen> also
[18:35] <jcastro> jpetersen: as you finish up can you make sure all your patches are up to date?
[18:35] <jcastro> also pinging the maintainers to try to get them accepted would help me out
[18:36] <jpetersen> jcastro, yes i will do
[18:37] <jcastro> jpetersen: also what do you think we should do as far as the strings thing hughsie brought up?
[18:37] <jcastro> I was thinking, the goal is to get the a-i work upstream, so if he doesn't want those changes we made to the strings maybe we could just drop those?
[18:38] <jpetersen> jcastro, one could just drop the strings for upstream, but there is the problem, that either the tooltip with the information is missing or the text in the menu items is really wide
[18:39] <jcastro> hmmm
[18:40] <jpetersen> jcastro, maybe mpt (who wrote https://wiki.ubuntu.com/PowerStatusMenu) can comment on it
[18:40] <jcastro> good idea
[18:40] <jcastro> mpt: ping
[18:43] <jcastro> Nafai: for gnome-bt you might need to be persistant on getting the review through.
[18:43] <jcastro> Nafai: but don't be so persistant that you annoy him, heh
[18:44] <jcastro> jpetersen: ok so if you could just due diligence each patch upstream as time allows before you finish off for good that would be great.
[18:46] <jpetersen> jcastro, yes I will do.
[18:46] <jpetersen> jcastro,  I will split up the patch for gnome-power-manager so that the string changes are in an extra patch
[18:46] <jcastro> rock
[19:06] <lamalex> oh man, tomboy needs a monochrome icon
[19:18] <qense> lamalex: isn't it there already>
[19:18] <qense> s/>/?
[19:19] <lamalex> qense: not for me, no
[19:22] <lamalex> qense: http://lamalex.net/static/panel.png
[19:33] <qense> lamalex: neither here, btw
[19:34] <qense> \vish: Do you know anything about the Tomboy monochrome icon?
[19:36] <mdc_laptop> \vish, also, do you know anything about a pidgin m-c icon? (also, hi! :) )
[19:37] <jcastro>   I think the icon is done but it isn't using it yet?
[19:37] <mdc_laptop> jcastro, which one?
[19:39] <qense> jcastro: Tomboy isn't using the monochrome icon.
[19:39] <qense> jcastro: Could it be that the -panel suffix was added to the icon name in spite of Tomboy not having an Application Indicator?
[19:39] <C10uD> hey, you didn't fix the python icon issue with libappindicator -- and i even provided a patch for that :p you're not following jono's advices eheh
[19:39] <jcastro> last time I saw the bug scroll by the icon was made but I don't think tomboy is using -panel yet?
[19:40] <qense> C10uD: me?
[19:40] <C10uD> i'll release "emesene" without libappindicator support, too bad if i can get the new version in lucid :(
[19:40] <C10uD> qense, i guess it's not you, it's "ayatana" in general
[19:40] <C10uD> https://bugs.launchpad.net/indicator-application/+bug/527061
[19:40] <ubot4> Launchpad bug 527061 in indicator-application "python bindings for libappindicator don't allow to change icon-theme-path (affects: 3)" [Undecided,Confirmed]
[19:40] <qense> C10uD: where is the bug, I could take a look at th
[19:40] <C10uD> one month with attached patch
[19:40] <qense> I'll look at the patch :)
[19:41] <qense> C10uD: what advice, btw?
[19:41] <jcastro> wait what
[19:41] <C10uD> i've seen some blogposts about reviewing patches, etc. in planet :)
[19:41] <jcastro> tedg: can you check out that bug please?
[19:41] <jcastro> C10uD: dang, be louder next time, I can help get ted to look at things!
[19:41] <jcastro> maybe it's not too late
[19:42] <C10uD> i complained a bit sometime ago but no luck (noone seemed to know if it was a proper patch, even if it's a very few tested lines), seems like other python applications doesn't need it :P
[19:43] <C10uD> so there hasn't been much noise about this issue
[19:43] <tedg> I missed the second patch.  Sorry about that.
[19:43] <tedg> It looks fine to me.
[19:43] <C10uD> tedg, 002 doens't workl
[19:43] <tedg> Oh :(
[19:43] <tedg> Heh, looks fine :)
[19:44] <tedg> kenvandine: Do you know anything about adding this constructor in the Python bindings?
[19:44] <tedg> kenvandine: bug 527061
[19:44] <ubot4> Launchpad bug 527061 in indicator-application "python bindings for libappindicator don't allow to change icon-theme-path (affects: 3)" [Undecided,Confirmed] https://launchpad.net/bugs/527061
[19:44] <kenvandine> tedg, i do not
[19:44] <qense> tedg: you can't specify the same function multiple times but with a different number of arguments
[19:45] <qense> you'll have to add a fourth icon_path=None argument and check for that
[19:45] <tedg> qense: It looks to me like it's a new function.  "app_indicator_new_with_path"
[19:45] <jcastro> tedg: btw, https://bugs.edge.launchpad.net/indicator-application/+patches
[19:45] <jcastro> tedg: +patches works for projects AND people/teams!
[19:45] <qense> tedg: isn't it specified as the constructor for the AppIndicator object?
[19:46] <qense> jcastro: and for source packages?
[19:46] <jcastro> try it, I am pretty sure 
[19:46] <tedg> jcastro: And project groups!  https://bugs.edge.launchpad.net/ayatana/+patches
[19:46] <C10uD> tedg, patch 002 adds another constructor, but seems like you can define multiple constructors with python bindings
[19:46] <tedg> qense: Ah, so you can't have two constructors.
[19:46] <qense> tedg: as far as I'm aware not
[19:47] <C10uD> with 001 instead, you have a single constructors which accepts an optional argument -- i've tested it and it works both ways
[19:47] <C10uD> not sure about other python applications using those bindings, but i don't see why they shouldn't break, if the c code is good
[19:48] <C10uD> s/shouldnt/should
[19:48] <qense> C10uD: I think 001 looks good indeed
[19:49] <tedg> Hmm, what's another Python app using libappindicator... gtg?
[19:49] <qense> tedg: it shouldn't matter because the fourth argument is optional and there is this check in _set_property(): if (priv->icon_path != NULL) {
[19:49] <kiko> hey there
[19:49] <qense> so if it's NULL by default, which it is, it should work just fine
[19:49] <qense> hi kiko
[19:49] <kiko> hey there
[19:49] <kiko> I'm otp so a bit lagged
[19:49] <kiko> but ask away
[19:50] <tedg> Hey kiko  we're looking at bug 527061
[19:50] <ubot4> Launchpad bug 527061 in indicator-application "python bindings for libappindicator don't allow to change icon-theme-path (affects: 3)" [Undecided,Confirmed] https://launchpad.net/bugs/527061
[19:50] <tedg> C10uD: Has a couple of patches there.  Seems that 001 works, but we don't know if it'll effect other Python apps.
[19:50] <qense> I think it won't.
[19:50] <tedg> 002 doesn't work, but we're not sure why.  It seems there can't be two constructors?
[19:58] <qense> tedg: by the way, are the Vala bindings going to make it into Lucid?
[20:00] <tedg> qense: I don't know.  Maybe.  I want to build them via GIR files.  It seems like the GIR packages probably won't make it, but that doesn't mean the vala files won't.  (we could just build the GIRs and discard them)
[20:00] <qense> ok
[20:12] <jcastro> qense: on a semi-related note
[20:12] <jcastro> I went to show off kde apps running in gnome with app indicators at the jam and it didn't work
[20:12] <qense> yes?
[20:12] <qense> no?
[20:12] <jcastro> do you happen to have any kde stuff installed to test?
[20:13] <qense> no, but could you name a few?
[20:13] <jcastro> it worked last time I tested it
[20:13] <jcastro> I tried choqok and kmix
[20:13] <qense> ok, I'll test those
[20:13] <tedg> jcastro: We're adjusting...
[20:13] <tedg> We had to change the names because the spec didn't get accepted by Freedesktop
[20:13] <jcastro> tedg: ah ok so you're aware it's broken then?
[20:13] <tedg> So I think Riddel is going to apply the KDE patch shortly.
[20:13] <tedg> The indicator-application went in already.
[20:14] <jcastro> eh when did this happen?
[20:14] <jcastro> the non-accepted part?
[20:14] <tedg> jcastro: Eh, well, it's all committees, right?  So it got non-accepted by no one accepting it :)
[20:15] <jcastro> oh so it didn't get rejected it just got fizzled
[20:15] <tedg> jcastro: The KDE guys wouldn't sign off until someone "from GNOME" would sign off.
[20:15]  * tedg should sign up to XDG list with his @gnome.org address
[20:16] <qense> ask jcastro to sign off! :P He's in the GNOME Board.
[20:16] <jcastro> no one has talked about it since January
[20:19] <jcastro> tedg: oh well, at least greg has proposed including "<3" in the spec
[20:19] <jcastro> the icon spec I mean
[20:19] <tedg> Heh.  Important.
[20:20] <tedg> And they're brining up the icon names that I filled bugs on last year.
[20:20] <jcastro> ok so for sure you guys are on this kde apps not working in gnome thing right?
[20:21] <jcastro> because it would be lame if that didn't work since that's like a major reason for doing this right?
[20:27] <qense> jcastro, tedg: I can confirm that Choqok doesn't use an AppInd in GNOME.
[20:28] <qense> Maybe it is related to the DBus interface namechange: Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString)
[20:28] <qense> Maybe KNotift still uses freedesktop
[20:28] <qense> namespace
[20:31] <tedg> qense: Yeah, I think that's the case.
[20:31] <qense> tedg: Is someone working on that issue?
[20:31] <tedg> qense: agateau has submitted a patch, but I don't believe it's been uploaded yet.
[20:31] <qense> ok
[20:31] <tedg> qense: Riddle said he'd do it with the KDE 4.2.2 update
[20:31] <tedg> Riddel
[20:31] <qense> 4.2?
[20:32] <qense> Doesn't Lucid provide 4.4?
[20:32] <tedg> Hmm, I probably mean 4.4.2 :)
[20:45] <doctormo> tedg: Is ian normally on IRC?
[20:48] <tedg> doctormo: No, I don't see around a lot.
[20:48] <tedg> doctormo: He's not on internal IRC either.  He's probably gone home.
[20:50] <doctormo> Ah thanks ted.
[21:19] <Nafai> jcastro: I still haven't got feedback from hadess, so I'm going to email him directly asking for follow up due to my time frame