[11:03] <thorwil> only a few days actually using lucid and i already hate the downloads complete notification bubbles :/
[13:06]  * mpt is momentarily disoriented by how bad Docky's Web presence is
[13:07] <mpt> There's no screenshot in USC, and the "Web site" link goes to a Launchpad project page that has its own "Web site" link that goes to a page that's completely blank except for the word "Wiki" which is linked to a wiki page that doesn't have any screenshots either
[13:08] <mpt> I guess I should be complaining in #docky instead
[13:13] <thorwil> mpt: maybe that structure is secret hint for some game by Trent Reznor
[13:14] <mpt> ok, the wiki page does have one screenshot, I was using the wrong browser
[14:29] <njpatel> kamstrup, velkommen
[14:29] <kamstrup> njpatel, ahoy!
[14:31] <kamstrup> sjokkis, hi!
[14:31] <sjokkis> hi
[14:32] <sjokkis> kamstrup: if you're targeting for next april (or is it march?), i'd suggest looking into libfolks
[14:32] <sjokkis> http://telepathy.freedesktop.org/wiki/Folks
[14:32] <sjokkis> still quite immature, but the guy behind it is solid, so i think it's gonna pan out
[14:33] <kamstrup> sjokkis, njpatel is the supreme ruler on the technical side of Unity stuff and djsiegel is the design ninja :-) but you are most welcome to talk to me as well :-)
[14:33] <sjokkis> njpatel...i've seen that name elsewhere
[14:33] <kamstrup> sjokkis, Unity is for 10/10
[14:33] <sjokkis> oh yeah, he's in #gnome-shell
[14:33] <sjokkis> kamstrup: i meant the people place, you mentioned
[14:33]  * njpatel was thinking maybe from AWN
[14:33] <sjokkis> you said maverick+1, right?
[14:33] <njpatel> :)
[14:33] <kamstrup> sjokkis, yeah njpatel is everywhere ;-)
[14:34] <njpatel> everywhere and nowhere, all at once
[14:34] <kamstrup> njpatel, that's almost kinda Zen :-)
[14:34] <njpatel> sjokkis, kamstrup said you might be interested in building a people-place?
[14:34] <sjokkis> i don't know if i have the skillset to take charge of it, but i'd certainly be interested in helping out
[14:35] <sjokkis> and i have a lot of free time this summer
[14:35] <kamstrup> njpatel, I told sjokkis that we don't have the final architecture fully nailed down at this point
[14:35] <kamstrup> (but that we are very close)
[14:37] <njpatel> sjokkis, Awesome, as kamstrup said, we're just testing a few ideas out but will hopefully have a bedded-down arch. quickly after alpha 2
[14:38] <sjokkis> so in about a month?
[14:38] <njpatel> yeah 3-4 weeks, just because we're trying some interesting ideas and need to make sure they work :)
[14:38] <sjokkis> sure
[14:39] <njpatel> sjokkis, skillset wise, kamstrup  is trying hard to make sure that we have a clean Vala API, with wrappers for the more complex bits of dbus-bits
[14:39] <sjokkis> so, we're looking at aggregating users from various sources, into meta-contacts, and presenting them to the user, right?
[14:40] <njpatel> I guess so, djsiegel1 may have some ideas about that
[14:40] <sjokkis> djsiegel1: around?
[14:41] <sjokkis> njpatel: have you looked at the (afaik rejected) design proposal on this for gnome-shell?
[14:41] <njpatel> sjokkis, people stuff? Nope, do you have a link?
[14:41] <sjokkis> looking for it now
[14:44] <sjokkis> njpatel: http://live.gnome.org/GnomeShell/DesignerPlayground/PeopleOverlay?action=AttachFile&do=get&target=gnome-shell-people-overlay-mockup.png
[14:47] <njpatel> sjokkis, ah, okay
[14:49] <njpatel> sjokkis, So, the way places work is that you, over dbus, hand a model of data and tell us how to render that information. For this release, we were planning to support one main way of rendering (due to other work) and then support custom renderers from M+1. However I think we may able to 'bootstrap' the custom renderer stuff and maybe people-place can be the guinea pig for that :)
[14:51] <sjokkis> njpatel: do you have an API for that?
[14:56] <njpatel> sjokkis, for custom renderers?
[14:56] <njpatel> sjokkis, not as yet, it's something which we were just discussing. It would have to be a vala module that implements some interface, the rest being in Clutter to actually draw stuff
[15:06] <sjokkis> njpatel: for sending data to unity over dbus
[15:06] <njpatel> sjokkis, that's what we're working on now
[15:06] <sjokkis> would i have to use a custom renderer, though?
[15:06] <njpatel> I think so, the default one wouldn't fit for showing extra information (but would be great for the initial results)
[15:07] <njpatel> The API itself will be very model-like, so your just adding/remove rows depending on the search string
[15:08] <sjokkis> do you have an API draft i could look at?
[15:16] <sjokkis> njpatel: ^
[15:18] <njpatel> sjokkis, not at the moment, but can ping you when we do
[15:18] <njpatel> still in the process of tying things together
[18:24] <ScottK> tedg: I have to confess a complete lack of understanding for your enthusiasm for CSD and I don't see anyone outside Canonical (in this discussion) sharing it.
[18:25] <tedg> ScottK, well, most people are simply tired of this discussion :)
[18:25] <ScottK> tedg: If you all are not interested in alternatives to CSD, then we can stop.
[18:25] <tedg> ScottK, I think it simply comes down to having two people draw every window is a little silly, and it creates a bunch of inconsistencies.  Polishing them is just that, it's not fixing them.
[18:26] <ScottK> tedg: So you think all the negatives of CSD are fine?
[18:26] <ScottK> Good luck.
[18:26] <tedg> Ah, okay.
[18:29] <seb128> hey tedg
[18:29] <seb128> qense, hey
[18:29] <tedg> Evening seb128
[18:30] <qense> seb128: good evening
[18:30] <seb128> qense, tedg: did one of you try to work with the update gtk to fix the bluetooth issue?
[18:30] <seb128> updated
[18:30] <seb128> I would like to see if this gtk update should go to lucid or not
[18:30] <seb128> I've it ready but I don't want to stale
[18:30] <qense> seb128: I didn't.
[18:31] <seb128> tedg, you probably have a better understanding of the change and issue than me
[18:31] <qense> seb128: I am quite busy right now, but maybe tedg has some spare time? :)
[18:31] <seb128> tedg, should some indicator* component listen to a new signal?
[18:32] <tedg> seb128, I don't believe so.  Though, I don't have bluetooth -- so I'm mostly debugging from e-mails/bugs.
[18:32] <qense> but that would mean the current GTK+ change doesn't fix this issue.
[18:32] <seb128> tedg, so you don't have an understanding of the issue? do you know who has?
[18:33] <seb128> well bratsche said the gtk change fixes the issue but the indicator still doesn't work
[18:33] <seb128> we might need some extra indicator changes though
[18:33] <tedg> seb128, Ah, okay.  I hadn't got any information on whether the GTK fix had worked or not.
[18:34] <bratsche> The bluetooth thing?
[18:34] <qense> yeah!
[18:34] <seb128> well, how do you determine if it worked? it doesn't fix the indicator
[18:34] <seb128> bratsche, yes
[18:34] <bratsche> I think whoever was working on the patch connected to an "add" signal in the patch, and that needs to be changed to "child-added" or whatever I named this signal.
[18:34] <bratsche> Then I think it should work.
[18:34] <tedg> Ah, okay.
[18:35] <tedg> seb128, So, yes, an indicator fix is needed :)
[18:35] <tedg> bratsche, That should be in libappindicator, correct?
[18:35] <bratsche> I don't remember if his code was for libappindicator or for bluetooth now.
[18:36] <seb128> tedg, ok, can you try to put that on your friday todolist?
[18:36] <seb128> tedg, ie the bug fix day ;-)
[18:36] <tedg> seb128, Yup, for sure.  I also want to look at the Python one.  I'm hoping we can fix both.
[18:36] <seb128> tedg, thanks!
[18:37] <seb128> tedg, the updated gtk is in the ubuntu-desktop ppa if you need it
[18:37] <seb128> tedg, lucid build
[18:37] <tedg> seb128, Ah, cool, thanks!
[18:37] <seb128> tedg, the change is also in maverick for a few days
[18:37] <seb128> tedg, thank *you* ;-) and thanks bratsche of courses!
[18:39] <qense> So it's now all set to be fixed properly at last? Yay!