[14:17] <davidbarth> hey MacSlow, could you help Cimi prepare some compiz settings update? he'd like to adjust a few variables and is the looking for the best way to submit a patch for that
[14:28] <oubiwann> Cimi: you around?
[14:37] <MacSlow> davidbarth, ok
[14:37] <MacSlow> Cimi, ping me whenever you need
[14:38] <iainfarrell> oubiwann: He's chatting to Otto right now
[14:38] <iainfarrell> Otto's away from tomorrow until Tuesday
[14:38] <oubiwann> iainfarrell: ah, cool -- thanks!
[15:34] <ronoc> Cimi: ping
[15:35] <Cimi> ronoc: yeah I'm here
[15:35] <Cimi> I heard you ;)
[15:35] <ronoc> good stuff
[15:36] <Cimi> restarting so
[15:36] <Cimi> one sec
[15:36] <ronoc> Cimi: okay
[15:39] <Cimi> ronoc: ok here
[15:41] <ronoc> Cimi: so I hear you were talking about storing all the necessary colours of things in the theme
[15:41] <ronoc> Cimi: I have setup the code to be aware of theme changes, I was just waiting for someone to take care of the themes :)
[15:42] <ronoc> Cimi: we just need to be clear in which fields you store which colours.
[15:42] <ronoc> #
[15:42] <ronoc> whoops
[15:42] <ronoc> will we start with the transport bar
[15:42] <ronoc> (play button)
[15:46] <Cimi> sorry had a disconnection
[15:46] <Cimi> so
[15:46] <ronoc> no worries
[15:46] <Cimi> I never said I would like to store colors
[15:46] <ronoc> hmm
[15:46] <Cimi> I said two things
[15:46] <ronoc> okay
[15:47] <Cimi> 1) for the scrubber please set a custom widget name for example ide-scrubber
[15:47] <Cimi> *ido-scrubber
[15:47] <ronoc> sure I can do that
[15:47] <Cimi> 2) for the player buttons
[15:47] <Cimi> we can have two solutions
[15:48] <Cimi> 1) you can draw just the border and fill with alpha (gradient from black to grey with alpha)
[15:48] <Cimi> that will work for dark menus and white menus as weel
[15:48] <Cimi> another idea is using gtk colors
[15:49] <Cimi> for example bg[GTK_STATE_NORMAL] and bg[GTK_STATE_PRELIGHT]
[15:49] <Cimi> but then, you could set up a different widget name
[15:49] <Cimi> so in the gtkrc we can just do
[15:49] <ronoc> sure thats easy
[15:49] <Cimi> widget_class "*ido-playerbutton" style "ido-playerbutton"
[15:49] <Cimi> style "ido-playerbutton" {}
[15:50] <Cimi> sorry { bg[NORMAL] = @bg_color ... whatever }
[15:50] <ronoc> yep my thoughts exactly, this is what I meant by you storing the colour
[15:50] <Cimi> so we can use shades or which color we want just playing with the gtkrc
[15:50] <ronoc> sounds good
[15:50] <Cimi> you don't need to store any color
[15:50] <Cimi> just use gtk colors
[15:50] <Cimi> and set a custom widget name
[15:51] <ronoc> sure which ever I get the colour from the style object passed to me from gtk and do not have hard coded colours in my C file ?
[15:51] <Cimi> once you have colors from gtk
[15:52] <Cimi> you have to do color operations to have nice gradients
[15:53] <ronoc> Cimi, can we work on this maybe late tmrw or Monday. I basically need to finish up some stuff for seb for the freeze that was last week
[15:53] <Cimi> tomorrow, not monday
[15:54] <ronoc> Cimi, any other day next week ?
[15:55] <ronoc> I could maybe do tmrw ?
[15:55] <ronoc> But I would prefer to get a release ready for seb
[15:55] <ronoc> at the moment
[15:57] <ronoc> Cimi ?
[15:57] <Cimi> yeah
[15:57] <Cimi> maybe on tuesday
[15:57] <Cimi> but starting from the next week I will me much more busy
[15:58] <Cimi> and davidbarth wants me even on other tasks so my brain is about to explode xD
[15:58] <Cimi> BAM
[15:58]  * Cimi imploses
[15:58] <ronoc> Cimi: I can imagine you are popular man !
[15:59] <Cimi> anyway it shouldn't be that complicated
[15:59] <ronoc> let me ping you in the morning, and hopefully we can crack something together tomorrow.
[15:59] <Cimi> if you point me to the file where the rendering code is
[15:59] <Cimi> I can write a patch
[15:59] <Cimi> ok cool
[15:59] <ronoc> okay cool, for the play button
[15:59] <ronoc> its in play-button.c
[15:59] <ronoc> that covers the full transport bar
[15:59] <ronoc> in the src dir of lp:indicator-sound
[16:00] <davidbarth> Cimi: ;)
[16:00] <davidbarth> btw
[16:00] <davidbarth> klattimer: hi ;)
[16:01] <Cimi> looks like mirco made his appearance here ;)
[16:01] <ronoc> indeed :)
[16:01] <Cimi> his coding style eheh
[16:01] <davidbarth> klattimer: the ibus patch is ready now it seems
[16:02] <davidbarth> klattimer: i've re-pushed the icon set request yesterday
[16:02] <davidbarth> klattimer: did you get a chance to look at the g-p-m bug yet?
[16:02] <klattimer> davidbarth: can you test the packages from my ppa before you say that
[16:02] <klattimer> I've had some quirks pop up
[16:02] <klattimer> I'm currently looking at fixing the g-s-d bugs again
[16:02] <davidbarth> klattimer: ah, ok, testing
[16:02] <klattimer> as it seems the initial fix didn't fix properly
[16:02] <klattimer> I've got an almost perfect patch working now
[16:02] <klattimer> shouldn't be too long
[16:02] <klattimer> hopefully before 5
[16:06] <davidbarth> klattimer: ibus-setup breaks here
[16:06] <davidbarth> klattimer: but i did a crude manual install
[16:08] <klattimer> k
[16:08] <klattimer> try from ppa:karl-qdh/ppa
[16:08] <klattimer> that should work
[16:10] <davidbarth> klattimer: doing that
[16:10] <davidbarth> need to restart my session
[16:16] <davidbarth> klattimer: which ibus-* package do i need to get some more input methods registered; ibus-setup crashes (now that i have a proper ppa instlal) because its enginedesc table seems empty
[17:25] <klattimer> davidbarth: you'll need at least ibus-table and pinyin or other engines are a good idea to add
[17:38] <davidbarth> klattimer: sorry, i totally broke my install here with an upgrade -f
[17:38] <davidbarth> klattimer: can't confirm the fix is working
[17:39] <davidbarth> kenvandine: can you test klattimer ibus package from is ppa before the package goes into maverick?
[17:40] <davidbarth> kenvandine: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/564034/comments/41
[17:40] <kenvandine> davidbarth, sure
[17:42] <davidbarth> thans
[17:42] <davidbarth> thanks
[18:13] <lucidfox> I wonder, can libappindicator be used as easily with Qt as with GTK?
[18:33] <kenvandine> klattimer, so how do i test ibus?
[18:33] <kenvandine> i have it installed, plus some engines and stuff
[18:34] <kenvandine> ibus-setup worked, changed keyboard input to ibus
[18:34] <kenvandine> but i can't tell that changing it in the indicator actually does anything
[18:34]  * kenvandine knows nothing about input stuff, so it might be working and i have no idea :)
[18:36] <lucidfox> What would the Powers That Be say about this possible usability improvement for the new keyboard indicator? bug #620571
[19:39] <jcastro> lucidfox: it would be helpful to get some feedback from the design people on that bug
[19:39] <jcastro> perhaps mpt or so
[19:39] <jcastro> and if it's all good we can ask klattimer to bust it out!
[19:39] <jcastro> klattimer: http://lucidfox.org/posts/view/607
[19:39] <jcastro> that's starting to look quite awesome now
[19:49] <lamalex> pretty confusing that the menu opens on the opposite side of the arrow
[19:49] <lamalex> there's a gtk papercut
[22:15] <AlanBell> hi all
[22:16] <AlanBell> we have a user in #ubuntu-accessibility who wants to remove the suspend and hibernate options from the shutdown menus
[22:17] <AlanBell> can someone help me understand how the menu options in the indicator applet are controlled please