[00:00] <Cimi> simply playing with the color
[00:00] <bratsche> The thing I was wanting to look into symbolic colors for was for setting status-relevant colors to widgets like GtkEntry (so it could convey information like "warning" or whatever)
[00:01] <Cimi> bratsche: for gtkinfobar as well?
[00:02] <bratsche> Yeah, using the same colors that GtkInfoBar uses now.
[00:02] <bratsche> But I need to think about it some more still, because there are other widgets that could possibly take advantage of it.
[00:02] <bratsche> I wrote a very rough first patch to do it for GtkEntry.
[00:03] <bratsche> GtkLabel could possibly use it as well.
[00:03] <bratsche> I hadn't really thought of it before, but possibly individual rows in a treeview could do something like this.
[00:26] <Cimi> bratsche: how's the newtwitter
[00:26] <Cimi> ?
[00:26] <bratsche> It's pretty nice.
[00:26] <bratsche> They're doing this whole dynamic UI stuff, kind of like Facebook does.
[00:30] <bratsche> All the routing happens on the client side using the document location hash, instead of doing it in URLs and stuff.
[00:31] <bratsche> One of my friends fucking *hates* it when websites do that.  I'm not really sure why.
[00:33] <Cimi> me neither :)
[00:34] <bratsche> Actually, Google is doing that now with Google Instant.
[00:35] <bratsche> Okay, I think I found the solutions to both of these appmenu-gtk bugs.  One of them is working, the other I need to write the patch later tonight.
[00:35] <bratsche> But now I'm hungry. :)
[00:35] <bratsche> Cimi: ttyl dude!  Good luck on your interview!
[00:38] <Cimi> oh thank you again
[11:14] <ronoc> Cimi, ping
[11:14] <Cimi> hi ronoc
[11:15] <ronoc> hey I just noticed the box around the indicator on ambience
[11:15] <ronoc> something changed theme wise in the past 6 days
[11:16] <Cimi> box?
[11:18] <ronoc> yes the background around the control
[11:18] <ronoc> Cimi, ^
[11:19] <ronoc> just one sec, on a call
[11:21] <Cimi> yep, it changed
[11:21] <ronoc> why then is there such a distinct box around the control ?
[11:21] <ronoc> its like the colour in the style fetched by the cairo code is wrong
[11:22] <Cimi> because the menu has a gradient
[11:22] <Cimi> while the box doesn't
[11:22] <ronoc> but now its even more distinct
[11:22] <Cimi> yep
[11:22] <Cimi> because i've changed the way it is rendered
[11:22] <Cimi> boh speed issues
[11:23] <Cimi> *for
[11:33] <ronoc> Cimi, okay shame because before what looked like a UI slight discrepancy now looks like an outright bug
[11:33] <ronoc> which I supposed it is
[11:33] <ronoc> -ed
[11:36] <Cimi> it is a bug in fact :(
[11:36] <Cimi> damn drawing areD
[11:37] <ronoc> a pretty ugly one, considering it our default theme
[11:37] <Cimi> I can't do anything
[11:38] <Cimi> if you set a custom widget name
[11:38] <ronoc> fair enough, yup
[11:38] <Cimi> maybe we could change bg[NORMAL] to reduce the "difference"
[11:38] <ronoc> okay will branch now and do that, one sec
[11:39] <Cimi> then add something like
[11:39] <Cimi> widget_class "*widgetblablabla*" style "ido-blabla"
[11:39] <Cimi> and before
[11:40] <Cimi> style "ido-blabla" { bg[NORMAL] = "#coloryouchose" }
[11:40] <Cimi> in the gtkrc
[11:44] <ronoc> Cimi, do you have time to look at this today
[11:44] <ronoc> Cimi, I need to look at some other stuff
[11:45] <Cimi> maybe I can
[11:45] <ronoc> Cimi, who is controlling your time at the moment ?
[11:46] <ronoc> Cimi, are you still working with us ?
[11:46] <Cimi> ronoc: when I start working, I use hamster applet to track my time
[11:46] <Cimi> chat it not counted (I am not working now i.e.)
[12:21] <hicham> is ayatana ubuntu specific ?
[12:22] <OwaisL> hicham: Yes, but it's open so anyone can borrow ideas and improve the.
[12:22] <OwaisL> them*
[15:31] <Cimi> davidbarth: do you know where ronoc is?
[15:48] <davidbarth> Cimi: he's there
[15:48] <Cimi> no
[15:48] <Cimi> :)
[15:49]  * bratsche summons him
[15:51] <Cimi> hi man
[15:51] <Cimi> _P
[15:51] <ronoc> Cimi, hey
[15:51] <Cimi> :P
[15:51] <ronoc> Cimi, I might have a fix for this
[15:51] <ronoc> one sec
[15:51] <Cimi> I was having a look at your branch
[15:51] <ronoc> yep
[15:51] <ronoc> which branch ?
[15:52] <ronoc> the new one ?
[15:52] <Cimi> https://code.launchpad.net/~cjcurran/indicator-sound/background-gradient-bug
[15:54] <ronoc> yep
[15:57] <ronoc> Cimi, yep and its doesn't work I think, the button looses its position when using the event box :(
[16:00] <Cimi> bratsche: help ronoc :P
[16:00] <bratsche> I can't right now.
[17:07] <Cimi> seb128: are you there dude?
[17:07] <seb128> Cimi, hey
[17:30] <Cimi> bratsche: summon ronoc pls
[17:37] <Cimi> ronoc: sorry :)
[17:37] <Cimi> ronoc: so, your gtkeventbox doesn't work or it does?
[17:37] <ronoc> no it doesn't
[17:37] <ronoc> well
[17:37] <Cimi> in case it doesn't, we should play with the custom widget name
[17:37] <ronoc> the problem is that the transport positioning gets screwed up
[17:38] <ronoc> it ends up at the top of the menu
[17:38] <ronoc> not at the bottom and only gets drawn sometimes as it fights with the slider widget for last one drawn
[17:39] <Cimi> mmm
[17:40] <Cimi> the transport positioning or just the drawing?
[17:40] <Cimi> maybe you need to use different x,y starting points
[17:40] <Cimi> using widget->allocation.x and widget->allocation.y
[17:40] <ronoc> Cimi, sure just playing with it now
[17:59] <Cimi> ronoc: is there a way to test the applet without installing it and killing the panel?
[18:01] <ronoc> Cimi, what applet the indicator-applet
[18:01] <Cimi> mmm
[18:01] <ronoc> Cimi, have you used libindicator-tools ?
[18:02] <Cimi> applet/indicator sound
[18:02] <ronoc> yeah install libindicator=tools
[18:02] <Cimi> ok
[18:02] <Cimi> done
[18:02] <ronoc> then compile the branch or what ever
[18:03] <ronoc> if its indicator only changes (UI changes)
[18:03] <ronoc> then run up the indicator-loader with
[18:04] <ronoc> /usr/lib/libindicator/indicator-loader /libsoundmenu.so
[18:04] <ronoc> Cimi, the path is wrong there to the .so.
[18:04] <Cimi> ok
[18:04] <ronoc> so from the root of the branch just make sure your path is right
[18:04] <Cimi> thank you
[18:04] <ronoc> src/.libs/libsoundmenu.so
[18:04] <Cimi> yeah :D
[18:05] <Cimi> I know don't worry man
[18:09] <Cimi> ronoc: I don't remember the file I should edit
[18:09] <Cimi> :)
[18:10] <ronoc> play-button.c
[18:10] <ronoc> Cimi, are you working on my branch ?
[18:10] <Cimi> yep
[18:10] <ronoc> I can push now if you want
[18:10] <ronoc> so we are up to date one
[18:10] <ronoc> sec
[18:10] <Cimi> ops ok
[18:12] <ronoc> Cimi, what do you plan to do  ?
[18:12] <ronoc> I got the help of njpatel earlier and it is almost there
[18:13] <ronoc> got distracted with a conversation in dx
[18:13] <ronoc> so just coming back to it now
[18:13] <ronoc> basically the positioning is screwed so we need to set the allocation on the eventbox
[18:13] <Cimi> yeah
[18:13] <Cimi> I tould tou that before if you remmeber :)
[18:14] <ronoc> ok
[18:15] <ronoc> Cimi, thats pushed now
[18:20] <ronoc> Cimi, okay done with distractions, are you working on this or will I have a go
[18:20] <ronoc> don't mind
[18:20] <Cimi> #define Y 7.0f
[18:20] <Cimi> #define X37.0f
[18:20] <Cimi> these are broken
[18:20] <Cimi> ronoc: ^^
[18:20] <ronoc> Cimi, okay but don't you want it to be relative to top of the parent gtkmenuitem
[18:20] <ronoc> there maybe more than one player
[18:20] <Cimi> yeah
[18:21] <Cimi> it's easy I guess
[18:21] <Cimi> just define x as widget->allocation.x + X
[18:21] <Cimi> or whatever
[18:21] <Cimi> something like that, I hope you understood
[18:21] <ronoc> okay will try that now
[18:22] <ronoc> thx
[18:22] <Cimi> button->allocation.x iirc
[18:27] <Cimi> maybe it's not enogh or I did something wrong
[18:58] <ronoc> Cimi, offset the positioning in the draw method but still no joy, gotta go now, if you fancy taking a look please be my guest, I have pushed my adjustments
[18:59] <ronoc> bye
[19:06] <ken> meebey: playing with smuxi again :)
[20:18] <joajimenez> Hellos
[20:26] <joajimenez> MeMenu....Why it have to depend on gwibber-service?
[20:28] <sense> joajimenez: Because it is integrated with it, from the MeMenu side. Gwibber doesn't hook into the Me Menu, but the Me Menu into Gwibber.
[20:34] <joajimenez> sense: I know, but if I unistall Gwibber, gwibber-service stay there consuming memory. I dont think that much users keep Gwibber once they discover: Pino, Hotot, Facebook.com, etc... :)
[20:34] <sense> That a bit of your memory is used isn't very bad, it's not too scarce.
[20:35] <sense> When you don't use Gwibber it shouldn't be too much anyway, since there is nothing to do for the daemon.
[20:35] <sense> joajimenez: But if I'm correct the daemon shouldn't even launch on boot if you didn't enavle it.
[20:37] <joajimenez> sense: I got Gwibber unistalled, but I got three (3) gwibber-service instances running when I check system-monitor
[20:38] <kklimonda> it's most likely a bug, I don't have a single instance running
[20:39] <sense> joajimenez: You should check the settings of Gwibber.
[20:39] <joajimenez> GS1: 5.4MiB, GS2: 5.4MiB, GS3: 5.0MiB
[20:42] <joajimenez> Check this: http://ubuntuone.com/p/Huy/
[20:44] <sense> joajimenez: Have you used Gwibber previously?
[20:44] <joajimenez> Yep.
[20:45] <joajimenez> But I unistalled it, 'cause I don't like it. I prefer Pino or Hotot.
[20:45] <sense> joajimenez: It could be that you left some settings behind, which start the daemon by default.
[20:46] <sense> joajimenez: Check System->Settings->Start-up Applications and disable the service there.
[20:48] <joajimenez> I dont have ANYTHING named gwibber or gwibber related on my Start-up Apps
[20:48] <joajimenez> Thats very weird
[20:49] <sense> joajimenez: indeed
[20:57] <joajimenez> Let me report it as a bug.