[00:11] <JanCBorchardt> is there a tool to compare lines of code written fixing a bug to lines of comments written on its report?
[01:49] <Paddy_NI> I fear there may not be enough room on the top panel for ubuntu netbook 10.10
[01:49] <Paddy_NI> My screen resolution is 1024x640
[08:22] <ronoc> Cimi: you there ?
[08:30] <vish> ronoc: hey, i dint understand your comment : https://bugs.launchpad.net/ubuntu/+source/indicator-sound/+bug/624610/comments/8 .. you are working on fixing it for Natty? and this menu-close is a temporary workaround?
[08:30] <ubot5> Launchpad bug 624610 in indicator-sound (Ubuntu) "Media Buttons should trigger action only on button release (affected: 3, heat: 22)" [Low,Triaged]
[08:31] <vish> oh boo! i seem to have missed him ;p
[08:31]  * vish should really stop hiding join/part!
[08:40] <thorwil> heh, whenever i consider to hide joins/quits, i'm reminded of how useful those referring to people you want to talk with are
[09:40] <klattimer> kenvandine: I can't find any entry point in vino for empathy, can you point me in the right direction?
[09:41]  * klattimer 's eyes sore with code :/
[10:42] <ronoc> Cimi, ping
[10:44] <Cimi> ronoc: pong
[10:45] <ronoc> Cimi, remember what we talked about yesterday ?
[10:45] <ronoc> Cimi, gradient etc
[10:45] <Cimi> y
[10:45] <ronoc> Cimi, do you know of any example code of where this implemented
[10:45] <Cimi> it's in the engine
[10:46] <Cimi> but, why you might need that?
[10:46] <ronoc> Cimi, is it possible to do this the transport control
[10:46] <Cimi> no, too difficult
[10:46] <ronoc> Cimi, do you have time to take a look ?
[10:46] <Cimi> we can't fix it in that way
[10:47] <ronoc> Cimi, so what way should we fix it, sorry UI is not my strong point
[10:47] <ronoc> i just want to get it fixed
[10:49] <Cimi> it can't :)
[10:49] <Cimi> unfortunately, I've noticed that bug already a month ago
[10:50] <Cimi> but there's no proper fix if not making a transparent gtkdrawingarea
[10:50] <Cimi> but bratsche told us it's impossible
[10:59] <ronoc> Cimi, okay, so without the rgba we cannot fix this ?
[11:01] <ronoc> Cimi, Okay just commented on that bug and kicked it out to touch.
[11:03] <Cimi> ok :(
=== MacSlow is now known as MacSlow|lunch
[12:14] <kenvandine> klattimer, you mean for the event?  look in vino-tube-server.c or vino-tube-servers-manager.c
[12:14] <klattimer> kenvandine: yeah
[12:14] <klattimer> I can't see why the name of the user isn't present
[12:15] <klattimer> the string is produced in a reasonable way
[12:17] <klattimer> the condition seems to be the only reason this would fail
[12:17] <klattimer> but even that shouldn't be broken
[12:17] <klattimer> :/
[12:19] <kenvandine> klattimer, indeed
[12:19] <klattimer> I'm perplexed to say the least
[12:19] <kenvandine> if you look at the status icon code, it doesn't look up the alias until much later
[12:19] <klattimer> it's going to take a lot more digging
[12:19] <kenvandine> it does it when you activate the icon
[12:19] <klattimer> hmm
[12:20] <klattimer> kenvandine: there seem to be a bunch of problems related to the timing
[12:20] <kenvandine> look at the SERVER_PROP in vino-tube-app-indicator.c
[12:20] <klattimer> everything is written to work with borken status icons
[12:20] <kenvandine> value is null when it gets the SERVER_PROP
[12:21] <klattimer> that's strange
[12:21] <klattimer> surely it should know what the server is, if it's connected to it
[12:21] <klattimer> *sigh* :/
[12:59] <JanCBorchardt> andreasn, thorwil, wers, godbyk: off to #ubuntu-meeting this time ;)
[12:59] <thorwil> JanCBorchardt: sure, but where's his mpt'ness?
[13:00] <JanCBorchardt> thorwil, I was wondering as well
=== MacSlow|lunch is now known as MacSlow
[13:02] <godbyk> JanCBorchardt: If my Internet connection holds up.
[13:02] <thorwil> mpt: hi! we just started missing you ;)
[13:02] <thorwil> heh
[13:03] <JanCBorchardt> :D
[13:03] <godbyk> I may be off and on -- my Internet connection is wonky this morning. :-(
[13:05] <JanCBorchardt> mat_t, are you coming to the meeting?
=== rgreening_ is now known as rgreening
[13:40] <mat_t> JanCBorchardt: hi, unfortunately swamped with other work atm :(
[13:46] <JanCBorchardt> mat_t, ok, no problem. Can you poke mpt by any chance?
=== njpatel_ is now known as njpatel
[14:45] <bratsche> Cimi: If the widget doesn't draw a background on itself at all, will that fix it?  Or will it just be white space then?
[14:45] <Cimi> bratsche: I don't know, we should try
[14:46] <bratsche> Cimi: RGBA won't fix it though, that's for sure.  RGBA is composited by the compositor, not by gtk+.  So if you tried to make the widget transparent then you'd just see the desktop under it, not the widget under it.
[14:47] <Cimi> yes
[16:03] <kklimonda> bah, am I the only one tired of hearing that Ubuntu doesn't contribute enough?
[16:04] <klattimer> kklimonda: nope
[16:04] <kklimonda> tedg: what is the status of inclusion of indicators in gtk+? have you guys tried pushing it further after first rejection? How is the whole spec going in fd.o? Any chance to get it approved as a standard?
[16:04] <klattimer> kklimonda: I upstreamed patches over a week ago
[16:04] <klattimer> and can't see a response to them
[16:05] <tedg> kklimonda, Unfortunately the GNOME folks seem to not want to accept anything that isn't "Shell focused" and Shell hasn't decided what they want to do yet. :(
[16:06] <kklimonda> klattimer: heh, just upstreaming patches to glib/gtk+ doesn't seem enough - you have to poke them on the ML.. I think the gio patch required by unity and zeig.. still hasn't been commented on :/
[16:06] <tedg> kklimonda, The FD.o thing is held up because the KDE guys don't want to push it unless someone from GNOME agrees.  And since there isn't anyone formally in charge of that in GNOME we don't have anyone to lobby.
[16:06] <kklimonda> tedg: argh..
[16:06] <tedg> kklimonda, I thought about just writing the XDG list with my @gnome.org mail address ;)
[16:07] <klattimer> tedg: that sounds a great move tbh
[16:07] <klattimer> put it bluntly that it's an implementation for both kde and gnome and the dbus api is fairly sweet
[16:07] <tedg> klattimer, Heh, yeah.  Unfortunately I think I'm too well known. :)
[16:07] <klattimer> the spec probably still needs some discussion, but for the most part it's a massive improvement
[16:08] <klattimer> for crying out loud I can SLIDE between my notification icons!!!!!!!
[16:08] <kklimonda> yeah, that's the killer feature in my opinion
[16:08] <kklimonda> it looks great
[16:08] <klattimer> kklimonda: it's ONE killer feature
[16:08] <klattimer> there's lots of cool stuff in there
[16:08] <tedg> klattimer, Yeah, there's some movement there.  Hopefully, we can get some discussion going at GNOME Boston Summit... we'll see though.
[16:09] <klattimer> but what _is_ kinda missing is the ability to put arbitrary items there, and mangle with the graphics a little more
[16:09] <klattimer> e.g. tomboy pins
[16:09] <tedg> For one, I know the indicators all work in Clutter -- the Unity integration could easily be stolen :)
[16:09] <klattimer> and also doing non-standard icony things
[16:09] <kklimonda> klattimer: sure, but this one should convince everyone that indicators are superior..
[16:09] <klattimer> e.g. rendering icons as a bunch of layers
[16:09] <tedg> klattimer, Yeah, and the problem there is theming.  So we hope that the GTK symbolic icons will solve some of that.
[16:09] <tedg> klattimer, Not all of course, but some.
[16:10] <klattimer> tedg: I see symbolic icons solving about 80% but that 20% is still a little annoying
[16:10] <kklimonda> but leaving jokes aside - how do indicators work when you use remote X? Do they show up as expected? I remember this question from the discussion back then when you tried upstreaming it for the first time.
[16:10] <klattimer> for instance, symbolic icons which could reference other svgs
[16:10] <tedg> klattimer, I think that jcastro is trying to organize a discussion at UDS/Boston Summit -- you should ping him with your list if ideas.
[16:10] <tedg> kklimonda, For all practical purposes they don't work when you remote X :-/
[16:10] <klattimer> e.g. the mail icon, references an SVG file which has a property of <number> then what you get is a small overlay of an icon with the number in it, positioned well and appropriately
[16:11] <tedg> klattimer, I'm curious if we couldn't take an SVG over the bus that was symoblic.  It fixes the theming issues.
[16:11] <tedg> klattimer, Either that or make an library API that makes it easy to "build a temp icon theme"
[16:12] <tedg> klattimer, So then you'd have a disk area to play with.  And advanced users could do advanced things, but we could make some common things easy.
[16:12] <klattimer> tedg: really there's a lot of librsvg work to be done
[16:13] <klattimer> external CSS and xref SVG's would solve most of the problems
[16:13] <kklimonda> tedg: so this is going to be one point people cry about in every discussion - it would be great to prepare some good counterargument other than "meh, who does that anyway?".. I guess pushing dbus over the network would be stupid, have either you or KDE guys thought about it?
[16:14] <tedg> klattimer, Yeah, actually the symbolic icon guys (I think hadess, but I don't remember off hand) pushed a lot of those things into rsvg.  One of the problems is that Inkscape doesn't support drawing with them easily :(
[16:15] <tedg> kklimonda, Yeah, it's the same problem with appmenu.  It's one of those things that I think everyone would love a solution, but no one is willing to invest the time to build one.
[16:16] <tedg> kklimonda, It's hard to justify as it really has become a corner case.  Even "dumb terminals" have pretty fast processors in them.
[16:19] <Paddy_NI> Have I heard right, that there is a tomboy notes app indicator?
[16:19] <kklimonda> yeah, I actually agree but there are still quite a lot of people using some old terminals for things like LTSP.. things are going to get ugly again when you start pushing it :)
[16:21] <kklimonda> on the other hand one could always implement indicators the way that they fall back to xembed (it's what notifications currently use) when they are launched over the network..
[16:22] <tedg> kklimonda, They do fallback to xembed with the notification area... but, we want to drop that long term.
[16:22] <tedg> Paddy_NI, yes
[16:22] <Paddy_NI> tedg, is it currently only for maverick?
[16:22] <Paddy_NI> Or should I use the core ppa
[16:22] <Paddy_NI> lucid here
[16:23] <tedg> Paddy_NI, Mostly, I had an old patch.  But I wouldn't trust it anymore.
[16:23] <Paddy_NI> ah sure thanks for the info.. I guess I can wait for maverick netbook
[16:24] <Paddy_NI> I need to get myself one of those MiFi devices
[16:24] <Paddy_NI> mobile broadband here so one computer online at a time
[16:25] <kklimonda> tedg: I know they do.. so actually it should just work[tm], right? The remote application won't find indicator-applet, will fallback to xembed and send it over network as it does today.
[16:25] <Paddy_NI> oh yeah I just gotta say this, love the work you guys do absolutely great :D
[16:26] <tedg> kklimonda, Correct, it should "Just work" :)
[16:28] <kklimonda> tedg: so it's not that big deal - lets just say that "the long term" when you believe xembed should be removed is not 1-2 years but 4-5. After all what's really important is to get the code accepted by upstream and start further work on the specification. Maybe broader community will have a better idea how to push indicators over network (which we can steal for appmenu ;) )
=== MacSlow is now known as MacSlow|break
[17:52] <pavolzetor> #include "libindicate-gtk/indicator.h"
[17:52] <pavolzetor> hallo, do I have to use it, if I wanna add icon?
[17:56] <pavolzetor> no one?
[18:44] <lucidfox> Does notify-osd ignore custom timeout values?
[18:49] <kklimonda> lucidfox: afair yet
[18:49] <kklimonda> yes
[18:50] <kklimonda> lucidfox: https://bugs.edge.launchpad.net/ubuntu/+source/notify-osd/+bug/390508
[18:50] <ubot5> Launchpad bug 390508 in notify-osd (Ubuntu) "notify-send ignores the expire timeout parameter (affected: 41, heat: 207)" [Wishlist,Confirmed]
=== MacSlow|break is now known as MacSlow