[09:51] <sense> good morning
[16:06] <LucidFox> I should say, I'm impressed how quickly indicator-appmenu has matured
[16:07] <LucidFox> It seems more stable to me than gnome-globalmenu, despite a much shorter development time.
[16:07]  * hyperair hopes indicator-applet will mature enough to stop leaking memory.
[16:09] <hyperair> considering how successful indicator-appmenu is, though, i can't help but wonder why a similar approach isn't used for windicators rather than using CSD.
[16:09]  * hyperair whistles
[16:09] <LucidFox> Honestly, I don't think windicators are a good idea to begin with
[16:11] <LucidFox> Are there any plans to add support for locations to indicator-datetime, for feature parity with the old panel applet?
[16:12] <hyperair> LucidFox: well, i don't either, but will refrain from thinking any further until it's actually implemented.
[17:10] <daoo> Is there documentation for the libindicate python bindings?
[17:30] <sense> daoo: If there is not, please feel free and encouraged by me to file a bug. I do have the sneaking suspicion there are indeed none.
[17:30] <daoo> I've not managed to find any.
[17:31] <sense> A shame
[17:31] <daoo> https://bugs.launchpad.net/libindicate/+bug/422039
[17:31] <ubot5> Launchpad bug 422039 in libindicate "Documentation should be completed (affected: 3, heat: 4)" [Medium,Confirmed]
[17:37] <sense> daoo: Thanks, will watch that bug.
[17:38] <daoo> And also this: https://bugs.launchpad.net/libindicate/+bug/422044
[17:38] <ubot5> Launchpad bug 422044 in libindicate "Documentation should find a home on the web (affected: 1, heat: 1)" [Low,Confirmed]
[17:43] <daoo> I was started to play around with libindicate but unfortunately didn't get very far when there was no documentation. :(
[19:21] <sense> daoo: Did you look at some examples?
[19:21] <daoo> Yes I did.
[19:22] <daoo> Well, what I want to do is check draw-attention of all message indicators.
[19:23] <daoo> I want to know, if for instance, pidgin has any new messages.
[19:24] <daoo> Well, I could do that with dbus and check against pidgin.
[19:26] <daoo> Though, if i use libindicate instead I could also check the status of other applications (I have mail, and rss reader).
[19:27] <daoo> I looked at list-and-print but it's confusing, is there no methods that return the value of a property instead of just sending it to a callback?
[19:27] <sense> daoo: All I could advise you to do is to look at the source code of the library to figure out what does what. Otherwise I wouldn't know.
[19:28] <sense> daoo: there is a libindicate-doc package
[19:28] <sense> You could try to figure out how the Python bindings work by following the C documentation.
[19:28] <daoo> Yeah, I've checked, but I'm not that good at C.
[19:29] <daoo> Yeah, the C bindings did seem to have functions where you could send variable pointers. Though, I could not find out if they were in the python bindings.
[20:15] <daoo> sense: There only seems to methods that take callbacks in the python bindigs.. :/
[20:16] <sense> daoo: If you need other methods, file a bug!
[20:24] <daoo> sense: I don't know but this bug might be what I need: https://bugs.launchpad.net/libindicate/+bug/499490
[20:24] <ubot5> Launchpad bug 499490 in libindicate "Indicator does not have normal GObject behavior (affected: 1, heat: 2)" [Undecided,New]
[20:25] <sense> yes