=== bilalakhtar_ is now known as bilalakhtar === MacSlow is now known as MacSlow|lunch === oubiwann is now known as oubiwann-away === oubiwann-away is now known as oubiwann === MacSlow|lunch is now known as MacSlow [15:51] good afternoon [16:40] is it normal that the datetime indicator doesn't show? [16:41] devildante: Apparently. [16:42] Several people have mentioned that it's been stripped out. [16:42] (But, as I use indicator-complete, I hadn't noticed XD) [16:43] but I liked it :( [16:43] You can get it back. [16:53] gambs: installing -complete made it return! thanks :) [16:54] * devildante wonders why -complete is not default - they wouldn't have to bother with *two* indicator applets [16:54] Complete isn't default because the network indicator and datetime are ready fro primetime last I heard. [16:55] So, desktop will use the old clock applet still. [16:57] (For instance, my datetime indicator doesn't update what day it is on the calendar unless I restart my computer... So, it still says it's Saturday) [16:59] mmm... thanks gambs :) [17:00] No problem! [20:20] kenvandine: do you know if twitter finds it acceptable to ship the api key in source but not regular binary distribution (as hidden in binary content) [20:21] or dont they like if "forks" or different distros will use the same key [20:21] meebey, the compromise i came to them was separating the key from the source [20:21] by putting the key in packaging [20:21] kenvandine: even if the source is not the regular distribution? as its not python... [20:22] however, if anyone abuses it they will shut it down [20:22] hrmpf [20:22] they just don't want it to be very discovera ble [20:22] kenvandine: source isnt, it needs lots of skillz [20:22] if they disable the key, we need to get an update out with the new key [20:22] true [20:23] so better to allow to pass it at buildtime [20:23] without shipping it in the regular source [20:23] yeah... and frankly it is easier to go to dev.twitter.com and register a new app than to go digging in bzr for someone else's :) [20:23] but oh well... :) [20:23] yes [20:23] kind if stupid [20:23] s/if/of/ [20:24] hm [20:24] yeah... they aren't really focused on our use case... desktop apps aren't the top of their priority stack [20:24] actually I have an idea [20:24] hrhr [20:25] I will include a default key that is replacable at buildtime [20:25] if it ever gets abused [20:25] yeah [20:25] distros can simply replace it [20:25] ^^ [20:25] gwibber is doing that too now :) [20:25] yup [20:25] :) [20:25] we are including a default key that we don't care if it gets shutdown [20:25] yep [20:25] and provide an override mechanism for distros to use their own [20:25] do you use a differet name for that one or something? [20:26] same variable names [20:26] but they come from a different file [20:26] which isn't included in gwibber source [20:26] but in the package [20:26] if that file exists, it uses it for overrides [20:26] so you can override any default setting [20:26] not just the key [20:28] kenvandine: ic [20:28] kenvandine: with name I meant the software name though in the twitter app db [20:28] oh... that is tied to the key [20:28] Gwibber Official, Gwibber FOSS, etc [20:28] so nothing in code [20:28] or just Gwibber for all? [20:29] or shows the name in the tweet though [20:29] thats why I ask [20:29] it shows the name associated with the key [20:29] so for Ubuntu, it now says "from Ubuntu" [20:29] instead of from Gwibber [20:29] hm ic [20:30] Gwibber (Ubuntu) would have been nicer probably [20:30] ^^ [20:30] that is up to the app owner on twitter [20:30] I think I will use Smuxi (default key in source), Smuxi Official, Smuxi ($Distro) if neeed someday [20:31] well the owner of the key controls that name, the app developer doesn't [20:31] I know [20:31] as I upstream and downstream though [20:31] ^^ [20:31] +am [20:31] true [20:31] I do control that [20:31] but if fedora packages it then they control it [20:31] for example [20:32] indeed [20:32] thats why I want to give good example :) [20:32] :) [20:32] so --engine-twitter-engine needs an optional parameter, righto [20:32] errr --enable-twitter-engine [20:33] kenvandine: I just made indicate and notify deps optional for the backwards distros [20:33] cool [20:33] say non-debian and non-ubuntu ones [20:33] ^^ [20:33] notify-sharp seems to be more spread though [20:34] do you know if inidicate is available elsewhere? [20:34] I would prefere makign the default to "yes" and not "auto" [20:34] but only if the major distros ship it [20:34] i know foresight does [20:34] kenvandine: is gwibber also using them as optional builddeps? [20:34] but not sure about others [20:35] yeah [20:35] well optional runtime [20:35] ah ic [20:35] * kenvandine hugs python [20:35] :) [20:35] its doable in C# too but its nasty, needs black magic [20:36] kenvandine: will gwibber break in the 1st sep? [20:36] s/in/on/ [20:36] if this update isn't out yet [20:36] well sort of... it'll stop working with twitter [20:36] hehe, I am not alone then... [20:36] yeah I meant the twitter support of it [20:36] lots of people are behind.. [20:37] this has good and bad sides [20:37] good is that most crappy apps will now simply die, finally [20:37] i think pino won't work either [20:37] bad is that is puts so much stress on us [20:37] yeah, and i need to backport this for lucid and get an SRU [20:37] :/ [20:38] the JSON parser that Twitterizer uses (the twitter lib that smuxi uses) has a bug currently, making it a showstopper :/ [20:38] kenvandine: thanks for the nice chat! going back to hackery... [20:40] np [20:40] good luck :) [21:58] I don't suppose I can get support for using libindicator here? I'm having a signal problem [22:27] I am using pygtk and appindicator and it appears that I am not receiving most signals. I would like a signal that I can use to determine when the indicator menu is being displayed.