| === MacSlow is now known as MacSlow|lunch | ||
| === MacSlow|lunch is now known as MacSlow | ||
| jcastro | klattimer: ping | 13:47 |
|---|---|---|
| klattimer | hey | 13:47 |
| klattimer | I just saw the bug come in | 13:48 |
| klattimer | looking at it | 13:48 |
| jcastro | rock | 13:48 |
| klattimer | hmm | 13:48 |
| jcastro | hey so, sandy overall isn't happy with the indicator situation | 13:48 |
| klattimer | there's some missing menu items | 13:48 |
| klattimer | no I know he's not | 13:48 |
| jcastro | so if you can love this, and love the one that is breaking the fallback for xubuntu | 13:48 |
| jcastro | that would be swell | 13:48 |
| klattimer | I'm trying to find the bug in the fallback among other things | 13:48 |
| jcastro | rock, thanks | 13:48 |
| klattimer | it's not easy | 13:48 |
| jcastro | :-/ | 13:48 |
| klattimer | I'm not *big* on mono bindings | 13:48 |
| jcastro | ok, I think he'll at least be relieved that you're looking into it | 13:49 |
| klattimer | yeah it's in my list | 13:49 |
| * jcastro goes to offer himself | 13:49 | |
| Cimi | iainfarrell: I'm going out know, early in Monday morning I'll leave for Orlando | 17:16 |
| Cimi | iainfarrell: great weekend to you and all the design team, have a safe flight too! | 17:16 |
| Cimi | seb128: didrocks: bratsche: ronoc: you too! see you next week guys | 17:19 |
| didrocks | Cimi: enjoy your week-end! have a safe flight and see you on Tuesday :) | 17:19 |
| ronoc | Cimi, nice one, safe trip | 17:20 |
| bratsche | Cimi: I won't be there next week. | 17:21 |
| Cimi | cool guys, my server will stay online, will read everything :P | 17:21 |
| Cimi | bratsche: oh sad :( anyway cool stuff for the resize grip | 17:21 |
| bratsche | I'm in Spain next week. | 17:21 |
| bratsche | Cimi: But I'll be at UDS a week later. | 17:21 |
| Cimi | bratsche: OT: does widget_class <GtkResize*> style "resize_grip" works to style the grip? | 17:22 |
| Cimi | which is the right widget match to set up? | 17:22 |
| bratsche | I don't know what you mean.. what is GtkResize*? | 17:23 |
| bratsche | The widget is GtkWindow | 17:23 |
| Cimi | bratsche: I want to match only the resize grip | 17:23 |
| Cimi | bratsche: in order to make it more sharp | 17:24 |
| bratsche | It's not a widget. | 17:24 |
| Cimi | mmm | 17:24 |
| Cimi | that's a problem for our theming | 17:24 |
| Cimi | I want to setup something to match only the resize grip | 17:24 |
| bratsche | Why? It uses the same function to draw the grip that GtkStatusbar did. | 17:24 |
| bratsche | Just do it the same way you did before, but instead of GtkStatusbar use GtkWindow | 17:24 |
| Cimi | so I can use different engines options (engine "murrine" { contrast = 1.2 } ) for example | 17:25 |
| Cimi | bratsche: but then I will match the whole window and all widgets inside | 17:25 |
| Cimi | not only the resize grip | 17:25 |
| Cimi | for example separators or others | 17:26 |
| bratsche | Well, what did you do when it was in GtkStatusbar? Did it affect everything that was inside a GtkStatusbar? | 17:26 |
| Cimi | bratsche: I did widget_class "*<GtkStatusbar>" style "statusbar" | 17:27 |
| Cimi | that affects every widget inside the staturbar, but they are only progressbars and buttons | 17:28 |
| Cimi | Imagine I want a red resize grip | 17:28 |
| Cimi | doing bg[NORMAL] = "#ff0000" would make the whole window red | 17:28 |
| Cimi | using GtkWindow | 17:29 |
| bratsche | But GtkStyleClass has a method for draw_resize_grip(), and you're a theme engine author. This is clearly solvable without making the resize grip a whole new widget. :) | 17:30 |
| Cimi | mmm maybe not every widget, because I was not using * after the match | 17:30 |
| Cimi | I know | 17:30 |
| Cimi | but everything is static | 17:31 |
| Cimi | I mean I can't send a direct match to the resize grip | 17:31 |
| Cimi | I'll have to add a custom engine optin | 17:31 |
| Cimi | there's no difference with draw_resize_grip or whatever :) | 17:32 |
| bratsche | Let's talk about it at UDS. | 17:32 |
| Cimi | ok cool | 17:33 |
| Cimi | bye guys then | 17:33 |
| === chaotic_ is now known as chaotic | ||
| Fitzsimmons | where can I find documentation on adding an entry to the MeMenu? | 21:38 |
| sense_ | Fitzsimmons: What type of entry do you want to add? The Me Menu is fully created in its own code. | 21:39 |
| Fitzsimmons | oh, that seems a bit shortsighted | 21:39 |
| sense_ | Fitzsimmons: Why would you want to add anything to those menu items? | 21:41 |
| Fitzsimmons | but I'm writing a daemon that allows for putting your session into "private mode" as browsers are calling it now, such that ~/.recently-used.xbel would be frozen, or all new entries would be marked with private, or some such | 21:41 |
| Fitzsimmons | one of my potential users suggested that a MeMenu item might be a good place to add toggling that on and off | 21:41 |
| sense_ | Fitzsimmons: You'll have to modify the Me Menu to do so, but you cannot extend it using another application | 21:42 |
| Fitzsimmons | it doesn't fit very well into any of the other menus, and would be somewhat wasteful to have its own App Indicator | 21:42 |
| Fitzsimmons | I'm surprised; why was the Messaging Menu built to be extensible by other apps, but the Me Menu not? | 21:43 |
| sense_ | It may be something to discuss on the Ayatana mailing list. | 21:43 |
| sense_ | Fitzsimmons: Because the Me Menu doesn't give provide state information from different applications, but gives general system control. | 21:43 |
| sense_ | It was designed in its current form by Canonical and I'm sure it isn t the vision of the DX Team to allow applications to add all kinds of menu items to it when they feel like. | 21:44 |
| sense_ | It would ruin the design and make it prone to cause confusion. | 21:45 |
| Fitzsimmons | the alternative is having all sorts of applications adding their own AppIndicators | 21:45 |
| Fitzsimmons | which is the same problem as the notification area clutter except with a new API | 21:45 |
| sense_ | But it doesn't clutter an already long menu. | 21:45 |
| Fitzsimmons | well, since you're here, where would you suggest I put the UI for a system-wide "privacy toggler" | 21:48 |
| Fitzsimmons | in an ideal world, that is, independent of available APIs and the such | 21:49 |
| sense_ | Fitzsimmons: The Ayatana mailing list is the right place to discuss the indicator stack, including the Me Menu. I would try it there. | 21:54 |
| Fitzsimmons | hm, what about the "session" menu that's beside it (with the power indicator), used for shutting down and logging out? what's that called? | 21:55 |
| sense_ | Fitzsimmons: Session Indicator! | 21:58 |
| Fitzsimmons | haha | 21:58 |
| sense_ | The Me Menu is actually a part of it on regular GNOME Panels. | 21:58 |
| Fitzsimmons | interesting | 21:58 |
| Fitzsimmons | so I'm still stuck with taking up the case for extensibility on the mailing list then, eh? | 21:59 |
| sense_ | It's because it's an easy way of getting the order right: they've put the Session Indicator and the Me Menu in one thing. | 21:59 |
| sense_ | Fitzsimmons: Yes indeed! | 21:59 |
| sense_ | Although I don't give you much chance pleading for extensibility, you'd have more chance promoting a system-wide privacy-mode button since that has been brought up before and is one specific thing that can be added in a controlled way. | 22:00 |
| Fitzsimmons | well, I got laid off today, so I guess I have time for a protracted mailing list flamewar | 22:00 |
| sense_ | Flame wars on the Ayatana mailing list are noted for not getting any attention by anyone with the capability of changing anything whatsoever. | 22:01 |
| sense_ | Flame wars (rightly) go on ignore. | 22:01 |
| Fitzsimmons | indeed | 22:02 |
| sense_ | Fitzsimmons: Anyway, I'm rebooting now to test some changes to the ALSA configuration. brb! | 22:03 |
| === dennis is now known as GreySim | ||
| ^Mike | Sadly, what sense_ said about flamewars also seems to be true of legitimate criticism :( | 22:20 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!