[01:51] <JanCBorchardt> vish, I’m starting to look into One Hundred Paper Cuts, slap me if I do something wrong ;)
[10:14] <Cimi> ivanka: iainfarrell1 : is it ok if I continue to answer to comments on the design blog?
[10:18] <Cimi> MacSlow: ping
[10:20] <MacSlow> hey Cimi, what's up?
[10:20] <Cimi> two things man ;)
[10:20] <Cimi> 3 maybe :D one is OT
[10:20] <MacSlow> Cimi, gee... you're demanding today ;)
[10:21] <Cimi> 1) the glow around menu is slowing down performances, many users reported performance issue, is there something I could do? (caching or so)
[10:21] <Cimi> 2) I would like to change gwd gconf default properties and shift compiz shadow a bit
[10:22] <MacSlow> Cimi, well of course you should do caching... if the size/allocation doesn't change... _don't_ recreate the glow
[10:22] <Cimi> 3) I've bought my first scooter/motorcycle, it's a 300cc but it's ok for being the first! maybe someday I will buy a real ducati and come in germany to you :P
[10:23] <iainfarrell1> Cimi congrats on the bike :)
[10:23] <iainfarrell1> that's very cool :)
[10:24] <iainfarrell1> As for the comments on the blog, yes please do comment
[10:24] <iainfarrell1> but don't feel like you have to respond immediately
[10:24] <iainfarrell1> I'd suggest letting the post settle and then picking some to respond to
[10:24] <Cimi> as I'm doing now
[10:24] <MacSlow> Cimi, regarding 2.) you got to tweak gconf-values below /apps/compiz/plugins/decoration/allscreens/options/shadow_*
[10:25] <Cimi> iainfarrell1: I just wanted to stop people continue blaming otto's wallpaper
[10:25] <MacSlow> Cimi, regarding 3.) where are the pictures? :)
[10:25] <Cimi> iainfarrell1: it has being annoying, even on omgubuntu 160+ comments of rants
[10:26] <Cimi> MacSlow: I know for 2), but could you guide me patching compiz/gwd?
[10:26] <MacSlow> Cimi, regarding 2.) change /apps/compiz/plugins/decoration/allscreens/options/shadow_x_offset and shadow_y_offset
[10:26] <Cimi> MacSlow: I know! I already did it through compizconfig settings manager
[10:26] <Cimi> :)
[10:26] <MacSlow> Cimi, you don#t need to patch them... just change the values... it's gconf
[10:26] <Cimi> I just want to ship the new setting by default
[10:26] <Cimi> I just want to ship the new setting by default
[10:28] <MacSlow> Cimi, I'm looking up the xml-file needed to tweak these two values
[10:29] <Cimi> thank you
[10:29] <MacSlow> Cimi, it's /usr/share/compiz/decoration.xml being part of package compiz-plugins
[10:29] <Cimi> for 3) pictures of me will come next week when the byke will arrive :P
[10:30] <Cimi> MacSlow: do you have an idea on how I could do caching?
[10:30] <Cimi> saving a pixmap?
[10:31] <MacSlow> Cimi, regarding the caching... I'd say surface-buffering is the best way... it's all cairo anyway, so I would not convert it to a pixbuf
[10:31] <Cimi> oh cool
[10:32] <Cimi> I never played with buffering
[10:32] <Cimi> are there any APIs?
[10:33] <MacSlow> Cimi, there's no dedicated API for surface-buffering/caching in cairo... it's how you deal with cairo_surface_t*
[10:33] <Cimi> because actually the theming engine receives an area, x, y, width, height
[10:33] <Cimi> where it draws the menu (the glow)
[10:34] <Cimi> when I move a menuitem, it seems the menu is getting redrawn
[10:34] <MacSlow> Cimi, general approach is... per widget (e.g. menu) keep the allocation/size (colors even) stored...
[10:34] <Cimi> the thing is, I'm not sure each drawing knows about its previous
[10:35] <Cimi> so, I really don't know how I could cache it
[10:36] <MacSlow> Cimi, and in every expose of the menu check these stored values (width, height, colors) against the last ones saved... if any of these changed, re-create the glow... otherwise don't and use the last created surface for painting
[10:36] <MacSlow> that way you'll save re-creating the glow
[10:37] <MacSlow> of course when any of the stored values changed (and you had to re-create the surface-cache) you need to updated the stored values with the new ones
[10:37] <MacSlow> Cimi, that's the general approach of it
[10:41] <Cimi> sorry
[10:41] <MacSlow> Cimi, I'm not sure how theme-engines work in detail, so I can't point you to the exact spot where you'd best hook up the caching
[10:41] <Cimi> got disconnected after
[10:41] <Cimi> 11:35:20    Cimi | so, I really don't know how I could cache it
[10:41] <MacSlow> Cimi, but it has to be on a per-widget-basis for sure
[10:43] <MacSlow> If one would write a new widget it be simple... derive from an existing one and add the caching mechanism... so it'll become transparent to the user of the widget
[10:43] <MacSlow> but for existing apps/widgets it has to happen elsewhere
[10:59] <vish> Cimi: i would suggest using the artwork mailing list as a source for discussion about the theme rather than the blog comments :)
[10:59] <vish> s/source/playground ;)
[11:05] <Cimi> sorry I don't know ifyou read me before
[11:05] <Cimi> 11:42:08 MacSlow | Cimi, but it has to be on a per-widget-basis for sure                                                                                │ gabaug
[11:05] <Cimi> 11:46:16    Cimi | MacSlow: do you have some code handy?                                                                                                │ gambs
[11:05] <Cimi> 11:49:59    Cimi | MacSlow: do you hear me? I had some disconnections, now the ADSL seems stable, last thing I read was MacSlow | Cimi, but it has to   │ godbyk
[11:05] <Cimi> ops
[11:05] <Cimi> MacSlow?
[11:07] <Cimi> o maybe
[11:07] <Cimi> MacSuperSlow? :)
[11:08] <Cimi> vish: mailing list has less visibility, we want to reach any kind of user
[11:09] <vish> Cimi: it has less visibility? i dont think so, its just a bad perception  :)  the countdown banner was announced on the ML alone, it has a huge number of submissions
[11:10] <vish> Cimi: you can just add a comment asking re-directing everyone to the ML, it would address your visibility concern too
[11:10] <Cimi> it's a matter of choice
[11:10] <Cimi> I don't think everyone will subscribe to the mailing list just to post his impression
[11:11] <Cimi> for example, I wouldn't
[11:12] <Cimi> also, being subscribed to the mailing list for a long time, I have the feeling that the quality is low, I mean, I can see only few talented guys
[11:12] <vish> Cimi: do you really want an impression from someone commenting "I demant perfection, i am UI fetishist" , how helpful is that gonna be to improve the theme?  ;)
[11:13] <vish> Cimi: yes, the mailing list is not used properly, not even sure if we need one if we are not going to use ..
[11:20] <MacSlow> Cimi, notify-osd uses surface-buffering
[11:21] <Cimi> cool
[11:21] <MacSlow> Cimi, but it's done application-side there... you nothing that would work in a theme-engine
[11:21] <Cimi> oh d'oh
[11:21] <MacSlow> I don't know how to approach that... you're the theme-engine dude
[11:21] <Cimi> could you find 30 mins to help me today or another moment?
[11:21] <Cimi> yeah
[11:21] <Cimi> it's an important task
[11:22] <MacSlow> Cimi, sorry... I've still bugs to kill myself
[11:22] <Cimi> yeah
[11:22] <Cimi> not today
[11:22] <Cimi> maybe next week
[11:22] <Cimi> I don't want to remove the glow just because I don't know how to cache it
[11:30] <Cimi> bratsche: ping
[11:33] <Cimi> MacSlow: the only idea I have is to store the surface in memory
[11:33] <Cimi> but I don't know how I could do this
[11:33] <Cimi> because if I'm correct each rendering behaves like a different istance of the engine
[11:33] <Cimi> I might need to speak with cody
[12:03] <lucidfox> Is it possible to port a Qt application use appindicators without introducing a GTK dependency?
[12:07] <thorwil> vish: if the artwork mailing list was a horse, we'd should take it behind the barn to shoot it (out of mercy)
[14:00] <vish> thorwil: +2  twice  for extra mercy :D
[14:15] <jfi> Hello, I have an compatibility issue regarding ApplicationIndicator, the following code: http://pastebin.com/8PxKgYTB changes correctly the icon with lucid but not with maverick. Is it a known issue? Did I miss something?
[15:32] <Cimi> davidbarth: now do you have occasion to test the theme?
[16:06] <davidbarth> Cimi: sorry, not yet, hopping from calls to channels
[16:49] <vlada> hi again. Sorry for bothering, but can you take a look at Bug #621838 again. Thanks in advance
[16:51] <kklimonda> vlada: it's fixed, right?
[16:52] <vlada> nope, unfortunately
[16:53] <kklimonda> vlada: so the fix is wrong? can you add a comment to the bug?
[16:56] <vlada> I've done that already. To my original report, that is. Doesn't make much sense to add a comment to totally unrelated bug (the one to which mine was wrongly characterized as dup).
[16:59] <kklimonda> have you updated indicator-application to 0.2.6?
[17:00] <vlada> yes
[17:03] <kklimonda> yup, I can confirm it
[17:05] <vlada> kklimonda, bug? keyboard indicator disappears for you too?
[17:05] <kklimonda> yes
[17:06] <jfi> I have also an issue with indication-application: #625371 in case somebody can confirm it
[17:07] <vlada> kklimonda, great! subscribe to Bug 621838
[17:08] <vlada> bbl
[17:09] <kklimonda> it's actually removing every icon next to it unless it's sound (which is handled by a different service)
[18:55] <RfAFdlS> hi! who use unity in notebook?
[18:57] <RfAFdlS> somebody use unity? :)
[23:00] <lamalex> Is there a way to debug indicators? I've got indicator-datetime installed but it's not loading for some reason. After a maverick upgrade