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