[07:03] <lucidfox> Is it possible to tell programmatically if the appindicator menu is open?
[07:04] <lucidfox> I have a program using a tray icon that updates its menu every time it is opened, and polls for its items every X seconds, so porting it to the indicator API causes flicker when the menu is open
[07:07] <lucidfox> I also wonder what is the Right Way(tm) for a third-party application to distribute separate indicator icons for dark and light themes
[07:07] <lucidfox> monochrome ones, that is
[07:12] <lucidfox> And... are there any plans to patch gnome-shell for indicator support?
[08:54] <lucidfox> What would be the best way to indicate on https://wiki.ubuntu.com/NotificationAreaTransition/CompatibilityFixes that an application is fixed?
[08:55] <lucidfox> For example, I ported liferea, epiphany-browser, guake and linuxdcpp, so they should no longer be on that list
[09:42] <klattimer> kenvandine: davidbarth: could one of you re-assign this https://bugs.launchpad.net/ayatana-ubuntu/+bug/599844 to the canonical desktop team?
[09:42] <klattimer> I've updated the patch, no more memory leaks and all the other issues brought up have been addressed
[09:47] <davidbarth> klattimer: hi, ok checking that now
[09:53] <klattimer> closed a bunch of gsd bugs
[09:53] <klattimer> and it's much nicer to use now
[09:53] <klattimer> feels a bit sharper :)
[09:59] <seb128> klattimer, hey, thanks for the g-s-d fixes, please don't set the bug fix released though
[09:59] <davidbarth> klattimer: you want to reassign to get confirmation of the fixes and then have it landed?
[09:59] <davidbarth> seb128: it's not
[09:59] <seb128> klattimer, use fix commited rather, they will be closed when the package with the update is uploaded
[09:59] <davidbarth> seb128: it's still 'in progress'
[09:59] <davidbarth> right
[09:59] <seb128> [Bug 620571] Re: [Maverick] Move keyboard layouts out of the submenu
[09:59] <seb128> ** Changed in: gnome-settings-daemon (Ubuntu)
[09:59] <seb128>        Status: Confirmed => Fix Released
[09:59] <seb128>  
[09:59] <seb128> I just got that by email
[09:59] <davidbarth> ah
[10:11] <klattimer> seb128: sorry, I thought that the best way of pushing the bugs upto the main bug
[10:13] <davidbarth> seb128: so does that help to have dx-team reassigned, or can we just check the packages and you take the proposed ones into maverick on monday?
[10:13] <seb128> klattimer, no worry
[10:14] <seb128> davidbarth, dx-team reassigned?
[10:14] <seb128> davidbarth, klattimer: I just uploaded the g-s-d update
[10:14] <seb128> klattimer, just set the bugs you fix to fix commited so I know which ones to list in the changelog for the upload
[10:15] <seb128> klattimer, do you have other changes that need upload?
[10:18] <seb128> davidbarth, mpt, klattimer: btw can we drop the keyboard icon?
[10:18] <davidbarth> drop? wdym?
[10:18] <seb128> ie bug #620331
[10:19] <mpt> seb128, no, not without changing the API.
[10:19] <mpt> And it would only be a temporary change until the icon generation is implemented.
[10:19] <seb128> hum ok, it has very weird spacing compared to other indicators and the icon waste space
[10:19] <seb128> temporary like for this cycle in the stable version having something nice to use
[10:21] <klattimer> seb128: we'd have to do something in libappindicators and libindicator I think, which might break abi
[10:21] <klattimer> it's possible to do it without breaking abi I suppose but that could be messy
[10:21] <klattimer> e.g. passing a NULL icon to indicator_new
[10:23] <klattimer> seb128: no other changes to upload no
[10:23] <seb128> klattimer, mpt: ok thanks, don't bother then, could you add a comment in this bug saying that?
[10:23] <davidbarth> seb128, mpt: i guess pitti asks more for a way to hide it even if you do have multiple layouts configured
[10:23] <seb128> klattimer, ok, what do you work on next?
[10:23] <davidbarth> seb128, mpt: which would be consistent with your (mpt's) design
[10:23] <seb128> davidbarth, no, pitti just say the icon is useless and use space
[10:24] <klattimer> seb128: jorge said apport
[10:24] <seb128> klattimer, no ibus fixing?
[10:24] <klattimer> i don't think so
[10:24] <mpt> seb128, sure
[10:24] <davidbarth> by implementing the option to hide the indicator, the space is saved, and that's part of mpt's design
[10:24] <seb128> that's still broken in maverick
[10:24] <klattimer> is it?
[10:24] <klattimer> hmm
[10:24] <seb128> you updated your ppa
[10:24] <seb128> but you didn't send any updated patch for us to upload
[10:24] <klattimer> i tested in my vm and the package in the ppa was working
[10:24] <seb128> that's why I'm asking
[10:24] <klattimer> i'll test again
[10:24] <seb128> well you didn't ask any sponsoring
[10:25] <seb128> is your update patch to upload?
[10:25] <seb128> updated
[10:25] <seb128> or was that just a testing ppa to debug?
[10:25] <klattimer> there's no updated patch
[10:25] <klattimer> just an updated build and removing the distro patch
[10:25] <seb128> well you have a ppa version working according to comment
[10:25] <klattimer> yeah, that's a rebuilt package
[10:25] <klattimer> same patch as already in the bug report
[10:25] <seb128> which is the same as in maverick?
[10:26] <klattimer> oh hang on
[10:26] <klattimer> there is something
[10:26] <seb128> davidbarth, the point is that the icon is useless
[10:26] <klattimer> I'm testing it now, nearly forgot about this
[10:26] <klattimer> there's still a problem with the activated signal not being sent from menu items
[10:26] <seb128> davidbarth, it eats space compared to what we had an other systems have, ie just the label
[10:26] <klattimer> in python
[10:26] <klattimer> need tedg to look into that testing my ibus package which shows the problem
[10:28] <davidbarth> seb128: right, so that's why i say, we should push a little further and add mpt's checkboxes to be able to hide the icon
[10:28] <seb128> davidbarth, but seems it's not trivial so let's not bother for this cycle
[10:28] <seb128> having the spacing fixed would be nice though
[10:28] <davidbarth> seb128: a gconf key and a dialog update
[10:29] <seb128> it's a bit weird right now
[10:29] <seb128> davidbarth, ok, that would be ok I guess
[10:29] <davidbarth> spacing
[10:29] <davidbarth> ?
[10:29] <seb128> klattimer, http://launchpadlibrarian.net/53938769/ibus_1.3.7-1ubuntu2_1.3.7-1ubuntu3.diff.gz is weird
[10:29] <davidbarth> for the ibus one?
[10:29] <seb128> davidbarth, did you try the layout indicator?
[10:29] <klattimer> weird?
[10:29] <davidbarth> or the gsd one?
[10:29] <klattimer> what's weird about it?
[10:29] <davidbarth> i'm testing it right now (ibus is fubared on my system)
[10:29] <seb128> klattimer, did you drop the indicator support of was there some cruft in the maverick version?
[10:29] <klattimer> there was cruft in the maverick version
[10:30] <seb128> klattimer, I'm trying to understand what you did in your ppa and what we should do in maverick to it
[10:30] <seb128> oh ok
[10:30] <klattimer> a patch which removed part of my patch
[10:30] <seb128> so we need to clean that?
[10:30] <klattimer> yeah
[10:30] <seb128> ok, that's what I was asking before
[10:30] <seb128> thanks
[10:30] <klattimer> if you look I removed debian-changed-1.3.7-1ubuntu2
[10:30] <seb128> davidbarth, gsd one
[10:30] <seb128> klattimer, right, ok, makes sense now
[10:30] <seb128> klattimer, thanks
[10:30] <seb128> davidbarth, there is no left margin
[10:30] <seb128> davidbarth, but there is quite some space between the label and the right border
[10:31] <davidbarth> seb128: there is for me, i have the network icon on the left
[10:31] <davidbarth> the connman one that is
[10:31] <klattimer> seb128: in GSD?
[10:31] <davidbarth> hmm right
[10:31] <klattimer> It's hard to get the guide size right on that
[10:31] <klattimer> I used XXX1
[10:31] <seb128> davidbarth, click on it and watch the rectangle
[10:31] <davidbarth> on the right you mean, the right padding is too wide
[10:31] <davidbarth> yeah, because of the guide
[10:31] <seb128> the spacing next to the label and icon are not identical
[10:31] <klattimer> as different layouts will be different widths, and changing width doesn't appear to be the right thing to do
[10:32] <seb128> davidbarth, yes
[10:32] <seb128> ok, I've to run for some errands, will be back in an hour
[10:32] <davidbarth> ok
[10:35] <mpt> seb128, done
[10:36] <davidbarth> to be nitpicking, the guide could be calculated according to the declared layouts, so that if none are 4 char wide, the padding could be adjusted
[10:38] <klattimer> davidbarth: that's true
[10:39] <klattimer> do you want me to do that and produce a new patch?
[10:41] <klattimer> davidbarth: the other thing with it, would be that it's centrally aligned within the allocated space
[10:41] <klattimer> if we're going to have an icon we should align to the left against the edge of the icon + spacing
[10:48] <ronoc> Cimi: ping
[10:48] <davidbarth> klattimer: align to the left? sorry, re-reading
[10:50] <davidbarth> klattimer: the label you mean, but then that's something to patch in indicator-application
[10:51] <klattimer> yeah that's right
[10:51] <klattimer> I'm just saying
[10:51] <klattimer> I can patch the guide size now if you like?
[10:53] <davidbarth> klattimer: that'd be cool, yes
[10:53] <davidbarth> klattimer: if you think that's a safe change
[10:54] <davidbarth> klattimer: ie, if there aren't parts to update all across the module
[10:54] <davidbarth> klattimer: i'm looking at the dialog thing, to see if mpt's checkbox could be also an easy win
[10:54] <klattimer> k
[10:55] <Cimi> ronoc: pong
[10:55] <klattimer> cool
[10:55] <davidbarth> klattimer: can't find where the ui for the layout preferences tab is located
[10:55] <klattimer> :/
[10:55] <ronoc> Cimi: any joy with the colours etc. ?
[10:55] <davidbarth> klattimer: do you know where that is?
[10:56] <Cimi> not yet
[10:56] <klattimer> nope
[10:56] <klattimer> not yet
[10:56] <klattimer> :)
[10:56] <klattimer> will find out in a sec
[10:56] <davidbarth> ok, i'll keep digging, don't worry
[10:56] <ronoc> Cimi: okay let me know if you need anything
[10:58] <davidbarth> klattimer: seems to be in gsd-keyboard-xkb.c
[10:58] <klattimer> ?
[10:58] <klattimer> the layout preferences?
[10:58] <klattimer> nooo, surely not
[10:58] <davidbarth> klattimer: ah, where then?
[10:59] <klattimer> I've been through that file all day and haven't seen it
[10:59] <klattimer> not sure
[10:59] <klattimer> gimme a sec
[10:59] <klattimer> it calls popup_menu_launch_capplet from gsd-keyboard-xkb.c
[11:00] <davidbarth> ah a capplet of course
[11:00] <klattimer> so there's a capplet for it called gnome-keyboard-properties
[11:00] <davidbarth> yeah, hmm
[11:02] <klattimer> davidbarth: your patch is on the bug report now
[11:02] <klattimer> using the shortest guide width
[11:03] <davidbarth> klattimer: wow! impressive! ;)
[11:03] <klattimer> not really :)
[11:03] <klattimer> right onto the preference item
[11:05] <klattimer> davidbarth: the file gsd-keyboard-plugin is the capplet
[11:06] <klattimer> hmm noooo
[11:06] <klattimer> :/
[11:06] <klattimer> ok, this is getting a bit quirky
[11:08] <davidbarth> klattimer: ah ok, so it's only for "extended" layouts, cool, the changes looks ok
[11:09] <davidbarth> klattimer: it's in gnome-control-center
[11:09] <klattimer> ah bugger
[11:09] <davidbarth> and the ui is in the capplets-data package
[11:11] <davidbarth> gnome-keyboard-properties-dialog.ui
[11:12] <klattimer> yeah looking at it now
[11:13] <klattimer> well, a few things need to be done, add the necessary XML, add the handler for it which writes to gconf and then have that gconf change detected in the applet and the hide to be done
[11:13] <klattimer> ... is there not a way to hide applets from showing in libindicator?
[11:13] <klattimer> I'd assume not
[11:13] <davidbarth> klattimer: hmm, it's going to be a fun one, with a schema definition to share between the capplet and the gsd plugin
[11:14] <klattimer> lovely
[11:14] <klattimer> :/
[11:20] <davidbarth> klattimer: hmm, a new way with the approver mechanism, but that's even more complex, because that would mean fiddling with bamf, for something it's not meant to be
[11:21] <davidbarth> klattimer: can you get the gconf key first, because if time runs out, at least that provides an option for "people who know" (like pitti)
[11:22] <klattimer> i'll have a look at what can be done
[11:24] <davidbarth> mpt: https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/620331/comments/7
[11:25] <mpt> davidbarth, neat
[11:25] <davidbarth> klattimer: awesome, thanks; assigning the task to you then; i know you loooove that indicator ;)
[12:08] <klattimer> mpt: I've updated ibus to include a radio menu item, but the string "Turn off input method" should probably be changed to "Input Method Off" as it's a member of the radio group
[12:08] <klattimer> when is string freeze?
[12:08] <mpt> klattimer, excellent choice. String freeze is Thursday 26th.
[12:09] <klattimer> urgh :/
[12:09] <klattimer> I've got a bunch of string fixes to do before then
[12:09] <klattimer> :(
[12:10] <klattimer> ok, well I'll change the string
[12:10] <klattimer> what's the procedure when I've changed the code?
[12:10] <klattimer> should I just leave it for translators to just get to work?
[12:10] <mpt> I don't know, sorry.
[12:10] <klattimer> k
[12:11] <klattimer> well seb128 do you know ^^
[12:11] <mpt> David Planella (dpm) might also know.
[12:12] <seb128> klattimer, you can change the strings they will show up in launchpad to translate
[12:12] <klattimer> oh, don't need to change any other files?
[12:12] <klattimer> that's pretty cool ;)
[12:13] <klattimer> the problem is, there's something wrong somewhere in the python bindings for the indicators
[12:13] <klattimer> the radio group doesn't even change on click
[12:13] <klattimer> there's definitely something wrong here :/
[12:13]  * mpt wonders why nothing appears in the panel when he turns on IBus
[12:13] <klattimer> anyway, I'll update the patch
[12:13] <seb128> kamstrup, open a bug and assign to ted
[12:13] <klattimer> mpt do you have the ibus from my ppa
[12:13] <klattimer> the current one in maverick is broken
[12:14] <seb128> the fixed one will be uploaded today
[12:14] <klattimer> seb128: did you mean me?
[12:14] <klattimer> seb128: I'm cooking a new patch for ibus with the menu item changes mpt wanted
[12:14] <klattimer> will add it to the bug report
[12:14] <seb128> klattimer, yes
[12:14] <seb128> kamstrup, sorry that was for klattimer
[12:15] <seb128> klattimer, if you have issues due to the indicator stack please open bugs
[12:15] <seb128> so they can be assigned to ted
[12:16] <klattimer> k will do
[12:23] <mpt> klattimer, no, I'll try your PPA
[12:24] <mpt> I see "System" > "Preferences" now contains (1) "Input Method Switcher" (2) "Keyboard" (3) "Keyboard Input Methods" (4) "Keyboard Shortcuts"
[12:25] <mpt> One day we'll fix that, but for now it's a mighty depressing example of uncoordination in open source
[12:25] <klattimer> seb128: can you assign https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/621075 to tedg
[12:25] <klattimer> mpt: I know, I hate that too :/
[12:26] <klattimer> what's the right thing to do however, is mighty difficult
[12:26] <c10ud> sorry guys disturbing your work but.. mpt when will we have an ubuntu-control-center that handles all this kind of stuff? yea, like mac
[12:26] <klattimer> merging of gnome-settings-daemon->keyboard with ibus in some way
[12:26] <seb128> klattimer, done and reassigned to one of the components he works on so he can't ignore it
[12:26] <mpt> c10ud, http://live.gnome.org/Design/SystemSettings/
[12:26] <klattimer> awesome :)
[12:27] <c10ud> no maverick i guess
[12:28] <mpt> certainly not
[12:28] <mpt> UI freeze is six days away
[12:29] <c10ud> heh, btw looking at all those visual improvements you've been doing lately, a 1080 dropdown menu for preferences is certainly a punch in your eye :p
[12:30] <mpt> c10ud, yes, especially when bug 578768 makes it near-impossible for me to choose the later items. :-)
[12:32] <c10ud> aww
[12:35] <mpt> "To be removed: xserver-xorg-video-i740" -- I hope that isn't anything important
[12:35] <klattimer> mpt: doubtful unless you've got a graphics card made by intel a decade ago?
[12:35] <mpt> Mine's Intel but 2007~2008 vintage
[12:35] <klattimer> it'll be fine :)
[12:37] <klattimer> mpt: btw https://bugs.launchpad.net/ubuntu/+source/light-themes/+bug/578768 should be marked as a duplicate of https://bugs.launchpad.net/bugs/548652
[12:40] <Cimi> ronoc: the code is there
[12:40] <Cimi> we just need to decide which colors we might use
[12:41] <ronoc> Cimi, sure for now I have the colours hardcoded in the play-button.c, can you use these for ambiance?
[12:41] <ronoc> Cimi: which branch is it ?
[12:42] <Cimi> ronoc: I mean
[12:42] <Cimi> I am actually getting the colors fromgtk
[12:42] <Cimi> apply a shade
[12:42] <Cimi> and draw with them
[12:42] <Cimi> now the question is:
[12:43] <ronoc> okay
[12:43] <Cimi> which colors we might use? I suggest bg[NORMAL] for the background, and fg[NORMAL] for the symbols on top
[12:43] <ronoc> sounds good
[12:43] <Cimi> does it support prelight etc etc?
[12:44] <ronoc> not yet, never spec'd but at some point we might need it
[12:44] <ronoc> lets refactor what is there to start with and then add stuff as we need it
[12:46] <Cimi> which is the design to implement?
[12:50] <Cimi> chaotic:
[13:14] <mpt> klattimer, with the keyboard menu from your PPA, it now shows the correct title ("USA2" instead of "USA" as it did before), but the menu has zero items.
[13:16] <meebey> kenvandine: reading about libgwibber, is it possible or will it be possible to retrieve statuses?
[13:16] <meebey> kenvandine: I would very like to see that for some sexy integration into smuxi
[13:20] <Cimi> ronoc: bzr branch lp:~cimi/indicator-sound/use-gtk-colors
[13:20] <ronoc> thanks Cimi, will take a look after lunch
[13:21] <meebey> kenvandine: with retrieve I mean to fetch the status per API not UI
[13:32] <ronoc> Cimi, did I hear you wanted to do rounded corners on the album art ?
[13:32] <ronoc> :)
[13:37] <kenvandine> meebey, not yet, but that is planned
[13:37] <kenvandine> the goal is to provide everything gwibber knows about through libgwibber
[13:37] <kenvandine> and then the gwibber client will use it
[13:37] <kenvandine> and hopefully lots of other apps
[13:38] <kenvandine> meebey, i would love some specific use cases you are after though, it will help in implementation
[13:38] <meebey> kenvandine: I have an issue to solve and havent decided yet
[13:38] <meebey> kenvandine: rewrite of the twitter engine in smuxi using twitterizer 2.0 (which has oauth support)
[13:39] <meebey> kenvandine: or use libgwibber if it can do the job :)
[13:39] <kenvandine> what is twitterizer going to do about the api key issue with oauth?
[13:39] <meebey> kenvandine: I have one use-case issue though, I would need pure libgwibber support... a headless linux server with smuxi server has no X server etc
[13:40] <klattimer> seb128: can you reassign this bug to canonical desktop team, the patch I have is working nicely; https://bugs.edge.launchpad.net/ubuntu/+source/indicator-application/+bug/558841
[13:40] <meebey> kenvandine: the client app needs to provide the key
[13:40] <kenvandine> right... but the key can't be in the source
[13:40] <seb128> klattimer, ok
[13:40] <meebey> kenvandine: it has to be in the source for opensource software
[13:40] <meebey> kenvandine: there is no issue ^^
[13:40] <seb128> klattimer, btw the g-s-d one still has issues
[13:40] <klattimer> seb128: like what?
[13:40] <kenvandine> meebey, but twitter won't allow that
[13:40] <meebey> kenvandine: everyone can use the key of course
[13:41] <meebey> kenvandine: what?
[13:41] <kenvandine> meebey, we are going though right now with gwibber...
[13:41] <kenvandine> it is a huge issue
[13:41] <seb128> klattimer, the menu selection is wrong sometime, it shows a layout selected which doesn't match the label
[13:41] <meebey> kenvandine: thats the standard practice to my knowledge
[13:41] <seb128> klattimer, the label is right though
[13:41] <klattimer> seb128: not with the updated patch it shouldn't
[13:41] <seb128> klattimer, but it does with the patch from today
[13:41] <kenvandine> meebey, they told us they will shutdown the key if they find it in any published source
[13:41] <klattimer> or is there a specific circumstance that "sometimes" is
[13:42] <klattimer> I mean, if you change it by keyboard shortcut does it go out of sync?
[13:42] <kenvandine> meebey, i am working with them right now
[13:42] <seb128> klattimer, yes, I've  3 layout, I select one, do both alt together
[13:42] <seb128> the label is correctly updated
[13:42] <seb128> but the list selection is not
[13:43] <klattimer> but the list selection isn't made
[13:43] <klattimer> ah... I get ya
[13:43] <kenvandine> meebey, it might be good enough to obfuscate it by requiring the distro packager to include the key in the packaging and install it in a separate location on the filesystem
[13:43] <klattimer> I know why that'll happen, but it's a tough one to fix
[13:43] <klattimer> lemme tinker with it
[13:43] <seb128> klattimer, thanks
[13:43] <kenvandine> meebey, they are thinking about that... we have gone back and forth a lot now... getting me stressed!
[13:44] <kenvandine> i need to get it resolved and SRU'd for lucid before the end of the month when they shutdown basic auth
[13:48] <meebey> kenvandine: yes I am also in stress because of the basic auth shutdown
[13:49] <meebey> kenvandine: to be honest, if they dont allow the key to be used in the source code, I might consider to simply drop twitter support
[13:49] <kenvandine> meebey, that is what ryan wants to do in gwibber... but twitter is just to popular, and ubuntu users are going to want it.
[13:49] <meebey> kenvandine: I kind of doubt the packaging obfuscation will help, each distro needs to obtain their own key then?
[13:50] <kenvandine> meebey, yeah... the solution they are giving to open source developers is to drive each user to dev.twitter.com to register their own application and enter their own key
[13:50] <meebey> kenvandine: well, if enough apps drop twitter support they might change their stupid EULA
[13:51] <kenvandine> the packaging obfuscation is about as good as stuffing it into a binary that can just be disassembled
[13:51] <meebey> kenvandine: if the key would be passed at build time...
[13:51] <kenvandine> either way it just can't be as secure as they want it
[13:51] <meebey> kenvandine: only the packagers would need to
[13:51] <meebey> kenvandine: that could be an acceptable workaround
[13:51] <meebey> still lame, but acceptable
[13:51] <kenvandine> not build time, the current though is to stuff it into a file, maybe several files on the filesystem
[13:51] <kenvandine> and we reassemble the files to get the key at runtime
[13:51] <meebey> kenvandine: I would do build time
[13:52] <kenvandine> so at least people have to do a little digging to figure out how to put it together
[13:52] <meebey> kenvandine: use with an automake maro
[13:52] <meebey> --with-twitter=$apikey
[13:52] <kenvandine> yeah... but gwibber is python so it would end up in plain text somewhere
[13:52] <meebey> oh!
[13:52] <meebey> :)
[13:52] <meebey> I dont have that particular issue with C#
[13:53] <meebey> but ic, a buildtime var is not helping, it ends up as plaintext on disk
[13:53] <meebey> disc, hehe
[13:54] <kenvandine> yeah :)
[13:54] <kenvandine> so build time could help, if we built it into some sort of binary
[13:54] <kenvandine> as long as they are OK with it being included in the packaging as plain text
[13:54] <meebey> kenvandine: actually....
[13:54] <meebey> kenvandine: libgwibber is C, why not that?
[13:55] <kenvandine> they definately are opposed to it being committed to the source repository
[13:55] <kenvandine> well libgwibber depends on gwibber-service
[13:55] <meebey> kenvandine: and at runtime gwibber reads (if needed) the api key from libgwibber
[13:55] <kenvandine> i don't want a circular depends
[13:55] <kenvandine> we could make gwibber build it into a tiny C module
[13:55] <meebey> yeah or that
[13:56] <meebey> something that is easy accessible from pyhton
[13:56] <kenvandine> they are discussing the idea of having the key in packaging but not in the source now
[13:56] <lucidfox> I don't understand why so many upstreams act downright hostile about libappindicator
[13:56] <lucidfox> "Until it appears in GNOME mainstream, no way we're supporting that"
[13:56] <kenvandine> lucidfox, yeah... i don't get it either
[13:56] <meebey> how backwards
[13:57] <meebey> good that there are also awesome upstreams like smuxi
[13:57]  * meebey hides
[13:57] <lucidfox> ^_^
[13:57] <meebey> GNOME is not providing any solution to the tray mess
[13:57] <kenvandine> awesome upstreams!
[13:57] <meebey> so why would I expect them to solve it?
[13:57] <meebey> they didnt for the past 10 years
[13:57] <meebey> ...
[13:58]  * meebey tries to get smuxi 0.8 ready in time for maverick with all the ayatana sexyness
[13:59] <kenvandine> woot
[13:59] <meebey> and twitter is the showstopper on that roadmap :/
[13:59] <meebey> maybe its time for a status.net replacement ^^ does it allow a brdige to twitter?
[14:00] <kenvandine> i think just posting
[14:00] <kenvandine> i haven't looked into it much
[14:00]  * meebey never used identica...
[14:00] <kenvandine> i want things like twitter lists and stuff
[14:00] <meebey> right, for full twitter support there is no way around it
[14:00] <lucidfox> Oh great, not bloody Twitter *here* too
[14:00] <meebey> but smuxi has no full blown twitter support yet, so...
[14:00] <meebey> haha
[14:01] <meebey> lucidfox went once crazy on #debian-cli because of using the word twitter
[14:01] <meebey> ...
[14:01] <kenvandine> hehe
[14:52] <tedg> mpt, Should we be puttin gin an override for the placement of the gsd keyboard layout switcher?
[14:52] <mpt> tedg, because it's not yet a system one?
[14:53] <tedg> mpt, Correct, so it gets place by category/id.
[14:53] <tedg> mpt, On my system that puts it all the way to the left.
[14:53] <mpt> tedg, it would make sense to override both the gsd one and the ibus one to put them at the trailing end
[14:53] <mpt> well spotted
[14:54] <tedg> mpt, Hmm, I would have guessed the opposite?  Why the trailing, it seems like the should be next to power?
[14:54] <mpt> tedg, yes, next to the other system ones
[14:55] <tedg> mpt, Ah, cool.  I thought you meant the other side ;)  Any preference on the order of gsd, ibus, gpm ?
[14:55] <mpt> https://wiki.ubuntu.com/SoftwareCenter#def-trailing :-)
[14:56] <mpt> tedg, no preference
[14:57] <mpt> just as long as gpm isn't separating the other two.
[14:57] <tedg> mpt, Hmm, I would have said trailing is "closest to white space" as the one in the corner is anchored and everyone else is following.
[14:57] <mpt> It's Java GUI lingo, apparently
[15:27] <Cimi> ronoc:
[15:27] <ronoc> Cimi
[15:28] <Cimi> ronoc: did ypu play with the branch?
[15:28] <ronoc> so I want get a chance today to get around to those branches. I have to finish something I'm working on here. But you mentioned earlier that you were interested in doing the rounded corners on the album art
[15:28] <ronoc> Cimi: do you want to branch and do that also, that is if you have nothing else on your plate ?
[15:29] <ronoc> davidbarth ^
[15:29] <Cimi> ronoc: the design is not definitive
[15:29] <Cimi> bug if you had chance to have a look at the code
[15:29] <Cimi> at the very beginning of the file I placed a lot of shade defines
[15:29] <Cimi> so you can easily adjust the colors
[15:30] <ronoc> hmm are you sure, I spoke with Otto yesterday and he seems to think the rounded corners were in.
[15:30] <ronoc> Cimi ^
[15:30] <Cimi> yeah but I want ottos' feedback
[15:30] <Cimi> anyway
[15:30] <ronoc> Cimi on which the rounded corners or the work you did this morning ?
[15:31] <Cimi> there are few things missing: 1) the background of the drawing area is filled with bg[NORMAL] and that looks ugly with the gradient of the menu
[15:31] <Cimi> ronoc: the work I did)
[15:31] <ronoc> okay
[15:31] <ronoc> well i would think it would be best to park that branch until Otto is back Tuesday
[15:31] <Cimi> another thing is could you please name the scrubber?
[15:31] <Cimi> for example ido-scrubber
[15:31] <ronoc> then we can go throw this on Tuesday with him.
[15:32] <ronoc> Cody is back next week also
[15:32] <davidbarth> ronoc, Cimi: don't forget the player item icon will have to move to the left column eventually; don't know if that impacts what you're adjusting at the moment
[15:32] <ronoc> Cimi: have you anything else to work on right now ?
[15:32] <Cimi> for the moment no
[15:33] <Cimi> I mean in the sound menu
[15:33] <ronoc> davidbarth: not right now
[15:33] <Cimi> the implementation is correct
[15:33] <ronoc> sorry not what I'm working on right now
[15:33] <ronoc> will talk to ted about this in mo
[15:34] <ronoc> davidbarth: I'm working on the blank graphic/the place holder for when there is no album art
[15:34] <ronoc> currently
[15:34] <ronoc> Cimi: well do you want to branch again from trunk and do the rounded rectangle work. doesn't seem like it would take too long ?
[15:34] <davidbarth> ronoc: ok nice
[15:35] <Cimi> which is the rounded rectangle work?
[15:35] <Cimi> for the cover?
[15:35] <ronoc> Cimi: the rounded corners on the album art, yep
[15:36] <ronoc> sorry rounded squares :)
[15:36] <Cimi> ok
[15:36] <ronoc> thx
[15:36] <Cimi> where's the code?
[15:36] <ronoc> in the metadata-widget.c
[15:36] <ronoc> art-url property update
[15:37] <Cimi> thx
[15:37] <ronoc> static void
[15:37] <ronoc> metadata_widget_update_album_art(MetadataWidget* self){
[15:37] <ronoc> Cimi ^
[15:37] <ronoc> that does the pixbuf and scaling
[15:38] <Cimi> ok
[15:48] <danyR> hi ayatana. anyone knows where can I get some indicator-network suppport?
[15:49] <davidbarth> danyR: hi
[15:50] <davidbarth> danyR: i'll call kvalo on this channel
[15:50] <davidbarth> danyR: what's the issue?
[15:51] <danyR> davidbarth: hi. indicator-network stopped working on my system. the indicator-network-agent is running fine
[15:51] <danyR> but everytime I call the indicator-network-service, I get a "(process:1721): libindicator-WARNING **: Name request failed.  Status returned: 3"
[15:51] <danyR> error
[15:52] <davidbarth> danyR: is indicator-network-service running already?
[15:54] <danyR> davidbarth: yeah. even if I kill it, it restarts itself
[15:55] <davidbarth> danyR: which is normal, the indicator restarts the service automatically
[15:55] <davidbarth> what's wrong with the instance that is runnign?
[15:57] <bcurtiswx> hey all, does the fact that rhythmbox still launches the icon on the top when using Applications-->sound and video  need a bug report, (since the sound menu will replace it) or not?
[15:58] <danyR> davidbarth: sorry, indicator-network started working suddenly. I don't really know what happened, it was unresponsive before
[15:58] <danyR> didn't answer to mouse clicks & actions
[15:58] <danyR> it started working, so I had to kill NM
[15:59] <danyR> however I've still an issue, it isn't updating icons/displaying connecting annimations
[15:59] <davidbarth> danyR: indicator-network works with connman
[15:59] <danyR> davidbarth: I know, I've a little knowledge on its insights :)
[15:59] <davidbarth> danyR: if you have both connman + i-network and NM running, you're up for some not so fun bugs with your connection
[16:00] <davidbarth> danyR: no offense, it's just that NM should /never/ run at the same time as connman
[16:02] <danyR> connman is running now. but I'm pretty sure it wasn't NM causing my problem. it's working, so I've just one last problem: no icon change/connecting animation
[16:02] <danyR> it seems it's crashed
[16:02] <danyR> unresponsive
[16:02] <danyR> but it's working
[16:05] <danyR> ok, it's working now. displays icons/animations.
[16:06] <danyR> I don't really know what happened, but it's funny that when I came here asking support, it started working.
[16:06] <danyR> I gues indicator-network was afraid of official support :P
[16:08] <danyR> kvalo: hi. what's the state of the "application start in offline mode" bug?
[16:14] <Cimi> davidbarth: I'm the only one who finds ugly the etched shadow around the user avatar in indicator-me?
[16:15] <davidbarth> Cimi: it is ugly, but it is gone altogether in the latest version; ivanka did some user testing and the avatar was creating confusion it seems
[16:15] <davidbarth> Cimi: i've kept the code around, just in case
[16:16] <davidbarth> Cimi: the test entry style is not great however with the current theme: it's not highlighted to reflect that it has the focus
[16:16] <davidbarth> and the text color doesn't work well with the rest of the background and menu
[16:17] <Cimi> davidbarth: Idon't have the text entry here
[16:18] <davidbarth> you need a configured account on gwibber for it to show up
[16:19] <Cimi> i havw it
[16:21] <Cimi> strange
[16:21] <Cimi> I can't test it if I don't have the entry
[16:32] <danyR> Cimi: I think I don't have a text entry either, in Maverick. with gwibber accounts configured
[16:33] <danyR> I confirm, it doesn't show yp
[16:33] <danyR> up*
[17:07] <lucidfox> I wonder
[17:07] <lucidfox> how is the notification area transition problem going to be solved for Wine?
[17:07] <lucidfox> Windows applications can't exactly be patched
[17:07] <kklimonda> it wont and people will learn at last that wine is not a solution
[17:07] <kklimonda> <wine rant />
[17:07] <kklimonda> ;)
[17:09] <kklimonda> lucidfox: but frankly I don't see why should we do anything about it - I've always seen wine as a compatibility layer that eases the switch from windows to linux. sacrificing linux experience so people can use their windows applications indefinitely just seems wrong to me.
[17:09] <kklimonda> and with that explanation I have to go for a while, don't flame me too much ;)
[17:09] <lucidfox> Well, I only use Wine for games, so
[17:09] <lucidfox> *coughsteamcough* *coughblizzardupdatercough*
[17:10] <gambs> I agree with kklimonda, if anything, that should be Wine's problem.
[17:10] <jcastro> we discussed it at UDS
[17:11] <jcastro> iirc the solution was "if you care enough to try to get windows programs to run on linux then adding the old tray on your panel will be easy"
[17:12] <kklimonda> lucidfox: and thanks to wine developers have actually one less reason to port their games to linux. but that's getting offtopic, jcastro's explanation is good :)
[17:13] <jcastro> I'm sure a person running a windows program with a totally different UI, different file chooser, etc. will not care about their tray
[17:14] <lucidfox> Ah, so it will only be removed by default, but the applet will be available to add onto the panel?
[17:14] <lucidfox> then yes, problem solved, Wine users will just use that
[17:14] <jcastro> right
[17:15] <gambs> I thought the Unity panel couldn't be messed with?
[17:15] <lucidfox> Well, if you use Windows programs, chances are you won't be running unity
[17:15] <lucidfox> May I suggest, however, that when it's removed by default, it's renamed to something like "Legacy notification area" and has Wine mentioned in its description
[17:16] <lucidfox> That reminds me, is gnome-shell going to be patched for indicator support?
[17:17] <gambs> Better question is whether Gnome-shell is going into natty <.<
[17:18] <lucidfox> Well
[17:18] <lucidfox> My personal opinion, and I'm not anyone official, is that gnome-shell is stillborn
[17:19] <lucidfox> It's subjectively bad both speed-wise and usability-wise - at least the latter is going to get mitigated with them redesigning it into basically Unity Desktop Edition
[17:19] <lucidfox> and too tightly coupled (Unity has that problem too, by design)
[17:19] <gambs> I know, I'm not actually asking because I know no one "official" would answer typically.
[17:21] <jcastro> nothing is really official about natty until UDS
[17:21] <gambs> Not complaining.
[17:23] <jcastro> lucidfox: how's the keyboard indicator working for you now after the update today?
[17:23] <lucidfox> jcastro> Almost flawlessly - the text by the icon is updated when I press Alt-Shift
[17:23] <lucidfox> but
[17:24] <lucidfox> when I open the menu itself, the layout radio button marks the wrong layout, not the one actually selected
[17:24] <jcastro> can you file a bug?
[17:24] <lucidfox> sure
[17:24] <jcastro> klattimer: ^
[17:29] <lucidfox> filed, bug #621247
[17:36] <Cimi> ronoc: I've tried using the code from gnome-scrensaver lock
[17:36] <Cimi> but
[17:36] <ronoc> yep
[17:37] <Cimi> gtk_widget_get_window (GTK_IMAGE(image) return NULL
[17:37] <Cimi> no window :(
[17:37] <ronoc> hmm one sec
[17:38] <ronoc> i think you will need to get the window from the expose signal
[17:38] <ronoc> i'm working on a branch right now that does that
[17:39] <ronoc> so lets pick this up Monday
[17:39] <ronoc> could you email the branch with the work you did this morning and the branch you are working on now -> conor.curran@canon....
[17:39] <ronoc> Cimi ^
[17:40] <Cimi> ok
[17:40] <Cimi> the actual branch crash :)
[17:41] <ronoc> not to worry, breaking things is always the first step :)
[17:48] <Cimi> lp:~cimi/indicator-sound/rounded-albumart
[17:58] <lucidfox> How is sound indicator support for Banshee coming along?
[17:58] <lucidfox> Is it going to be uploaded to Maverick?
[18:07] <jcastro> lucidfox: it's upstream, hyperair has been on holiday, which is why it's not in maverick
[18:45] <vish> is anyone aware that bug #607410  occurs even in the latest daily?
[21:24] <jcastro> klattimer: put lp #587272 in your low-hanging-fruit nice-to-have-but-not-a-requirement pile pls.
[21:39] <sense> vish: Do you think we should pass bug #606149 to the Design Team?
[21:58] <GreySim> I hope someone does *something* about that. I really loved the window borders in Neil Patel's Gwibber mockups: http://4.bp.blogspot.com/_Xie1ydrCav4/TEHqsC8MxbI/AAAAAAAABDg/dEBLMZbX43I/s1600/compact-multi-column.png
[22:04] <klattimer> jcastro: I've got the previous bug you mentioned on my radar
[22:05] <klattimer> the off-by-one error in gsd
[22:05] <klattimer> not sure where it comes from though
[22:05] <klattimer> I'll add this to my list of bugs
[22:05] <klattimer> :)
[22:05] <klattimer> oh it's all ready there
[22:06] <jcastro> heh
[22:40] <lamalex> kenvandine: is new gwibber in a ppa yet?
[22:40] <kenvandine> no... but it is in maverick :)
[22:41] <lamalex> if only I could install maverick!
[22:41] <kenvandine> it will hit fta'a nightlies tonight