/srv/irclogs.ubuntu.com/2010/08/27/#ayatana.txt

JanCBorchardtvish, Iā€™m starting to look into One Hundred Paper Cuts, slap me if I do something wrong ;)01:51
Cimiivanka: iainfarrell1 : is it ok if I continue to answer to comments on the design blog?10:14
CimiMacSlow: ping10:18
MacSlowhey Cimi, what's up?10:20
Cimitwo things man ;)10:20
Cimi3 maybe :D one is OT10:20
MacSlowCimi, gee... you're demanding today ;)10:20
Cimi1) the glow around menu is slowing down performances, many users reported performance issue, is there something I could do? (caching or so)10:21
Cimi2) I would like to change gwd gconf default properties and shift compiz shadow a bit10:21
MacSlowCimi, well of course you should do caching... if the size/allocation doesn't change... _don't_ recreate the glow10:22
Cimi3) 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 :P10:22
iainfarrell1Cimi congrats on the bike :)10:23
iainfarrell1that's very cool :)10:23
iainfarrell1As for the comments on the blog, yes please do comment10:24
iainfarrell1but don't feel like you have to respond immediately10:24
iainfarrell1I'd suggest letting the post settle and then picking some to respond to10:24
Cimias I'm doing now10:24
MacSlowCimi, regarding 2.) you got to tweak gconf-values below /apps/compiz/plugins/decoration/allscreens/options/shadow_*10:24
Cimiiainfarrell1: I just wanted to stop people continue blaming otto's wallpaper10:25
MacSlowCimi, regarding 3.) where are the pictures? :)10:25
Cimiiainfarrell1: it has being annoying, even on omgubuntu 160+ comments of rants10:25
CimiMacSlow: I know for 2), but could you guide me patching compiz/gwd?10:26
MacSlowCimi, regarding 2.) change /apps/compiz/plugins/decoration/allscreens/options/shadow_x_offset and shadow_y_offset10:26
CimiMacSlow: I know! I already did it through compizconfig settings manager10:26
Cimi:)10:26
MacSlowCimi, you don#t need to patch them... just change the values... it's gconf10:26
CimiI just want to ship the new setting by default10:26
CimiI just want to ship the new setting by default10:26
MacSlowCimi, I'm looking up the xml-file needed to tweak these two values10:28
Cimithank you10:29
MacSlowCimi, it's /usr/share/compiz/decoration.xml being part of package compiz-plugins10:29
Cimifor 3) pictures of me will come next week when the byke will arrive :P10:29
CimiMacSlow: do you have an idea on how I could do caching?10:30
Cimisaving a pixmap?10:30
MacSlowCimi, 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 pixbuf10:31
Cimioh cool10:31
CimiI never played with buffering10:32
Cimiare there any APIs?10:32
MacSlowCimi, there's no dedicated API for surface-buffering/caching in cairo... it's how you deal with cairo_surface_t*10:33
Cimibecause actually the theming engine receives an area, x, y, width, height10:33
Cimiwhere it draws the menu (the glow)10:33
Cimiwhen I move a menuitem, it seems the menu is getting redrawn10:34
MacSlowCimi, general approach is... per widget (e.g. menu) keep the allocation/size (colors even) stored...10:34
Cimithe thing is, I'm not sure each drawing knows about its previous10:34
Cimiso, I really don't know how I could cache it10:35
MacSlowCimi, 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 painting10:36
MacSlowthat way you'll save re-creating the glow10:36
MacSlowof 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 ones10:37
MacSlowCimi, that's the general approach of it10:37
Cimisorry10:41
MacSlowCimi, 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 caching10:41
Cimigot disconnected after10:41
Cimi11:35:20    Cimi | so, I really don't know how I could cache it10:41
MacSlowCimi, but it has to be on a per-widget-basis for sure10:41
MacSlowIf 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 widget10:43
MacSlowbut for existing apps/widgets it has to happen elsewhere10:43
vishCimi: i would suggest using the artwork mailing list as a source for discussion about the theme rather than the blog comments :)10:59
vishs/source/playground ;)10:59
Cimisorry I don't know ifyou read me before11:05
Cimi11:42:08 MacSlow | Cimi, but it has to be on a per-widget-basis for sure                                                                                ā”‚ gabaug11:05
Cimi11:46:16    Cimi | MacSlow: do you have some code handy?                                                                                                ā”‚ gambs11:05
Cimi11: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   ā”‚ godbyk11:05
Cimiops11:05
CimiMacSlow?11:05
Cimio maybe11:07
CimiMacSuperSlow? :)11:07
Cimivish: mailing list has less visibility, we want to reach any kind of user11:08
vishCimi: 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 submissions11:09
vishCimi: you can just add a comment asking re-directing everyone to the ML, it would address your visibility concern too11:10
Cimiit's a matter of choice11:10
CimiI don't think everyone will subscribe to the mailing list just to post his impression11:10
Cimifor example, I wouldn't11:11
Cimialso, 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 guys11:12
vishCimi: 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:12
vishCimi: yes, the mailing list is not used properly, not even sure if we need one if we are not going to use ..11:13
MacSlowCimi, notify-osd uses surface-buffering11:20
Cimicool11:21
MacSlowCimi, but it's done application-side there... you nothing that would work in a theme-engine11:21
Cimioh d'oh11:21
MacSlowI don't know how to approach that... you're the theme-engine dude11:21
Cimicould you find 30 mins to help me today or another moment?11:21
Cimiyeah11:21
Cimiit's an important task11:21
MacSlowCimi, sorry... I've still bugs to kill myself11:22
Cimiyeah11:22
Ciminot today11:22
Cimimaybe next week11:22
CimiI don't want to remove the glow just because I don't know how to cache it11:22
Cimibratsche: ping11:30
CimiMacSlow: the only idea I have is to store the surface in memory11:33
Cimibut I don't know how I could do this11:33
Cimibecause if I'm correct each rendering behaves like a different istance of the engine11:33
CimiI might need to speak with cody11:33
lucidfoxIs it possible to port a Qt application use appindicators without introducing a GTK dependency?12:03
=== MacSlow is now known as MacSlow|lunch
thorwilvish: if the artwork mailing list was a horse, we'd should take it behind the barn to shoot it (out of mercy)12:07
=== MacSlow|lunch is now known as MacSlow
vishthorwil: +2  twice  for extra mercy :D14:00
jfiHello, 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?14:15
Cimidavidbarth: now do you have occasion to test the theme?15:32
=== oubiwann is now known as oubiwann-away
=== oubiwann-away is now known as oubiwann
davidbarthCimi: sorry, not yet, hopping from calls to channels16:06
vladahi again. Sorry for bothering, but can you take a look at Bug #621838 again. Thanks in advance16:49
ubot5Launchpad bug 621838 in indicator-applet (Ubuntu) "Keyboard layout part of indicator applet disappears (dup-of: 623205)" [Undecided,New] https://launchpad.net/bugs/62183816:49
ubot5Launchpad bug 623205 in Application Indicators "Indicator applet sets the label on the wrong indicator (affected: 2, heat: 116)" [Medium,Fix released] https://launchpad.net/bugs/62320516:49
kklimondavlada: it's fixed, right?16:51
vladanope, unfortunately16:52
kklimondavlada: so the fix is wrong? can you add a comment to the bug?16:53
vladaI'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:56
kklimondahave you updated indicator-application to 0.2.6?16:59
vladayes17:00
kklimondayup, I can confirm it17:03
vladakklimonda, bug? keyboard indicator disappears for you too?17:05
kklimondayes17:05
jfiI have also an issue with indication-application: #625371 in case somebody can confirm it17:06
vladakklimonda, great! subscribe to Bug 62183817:07
ubot5Launchpad bug 621838 in indicator-applet (Ubuntu) "Keyboard layout part of indicator applet disappears (affected: 1, heat: 6)" [Undecided,Confirmed] https://launchpad.net/bugs/62183817:07
vladabbl17:08
kklimondait's actually removing every icon next to it unless it's sound (which is handled by a different service)17:09
RfAFdlShi! who use unity in notebook?18:55
RfAFdlSsomebody use unity? :)18:57
=== simar__mohaar is now known as simar
lamalexIs there a way to debug indicators? I've got indicator-datetime installed but it's not loading for some reason. After a maverick upgrade23:00

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!