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