[07:55] hey [09:49] hi :) [12:18] kitallis: hi.. you need to ask Mac_Slow ;) [12:30] vish, yeah, i know :) === MacSlow is now known as MacSlow|lunch [13:23] I am offline for some hours, will be back later [13:25] hi tedg [13:26] Good morning jpetersen [13:27] tedg, there is a patch for https://bugs.launchpad.net/bugs/528527 in the linked branch [13:27] Launchpad bug 528527 in indicator-application (Ubuntu Lucid) (and 2 other projects) "should respect the gtk "always-show-image" property (affects: 2)" [Low,In progress] [13:28] jpetersen: Sweet, I'll look at that. [13:30] tedg, thanks, i am just going to be away, will be back later [14:31] seb128: fyi Nafai will be in and out today due to some doctor appointments [14:32] jcastro, ok [14:32] hey jcastro [14:46] qense: I think someone still needs to connect the monochrome icons in banshee. [14:46] wrt. your question this weekend [14:50] jcastro: It turned out that the wrong icon name was used for the monochrome icon. [14:51] jcastro: Banshee's icon name is media-player-banshee, so the applet looks for media-player-banshee-panel, logically it can't find banshee-panel that way. [14:51] ah excellent, so now all we need is the app indicator and we're all set. :D [14:54] jcastro: indeed [15:17] qense: does that icon thing have a bug, is hyperair aware? [15:19] jcastro: dashua brought it up and warned vish who warned me. I sent the problem back to vish since he manages the icons in humanity-icon-theme, which is where the fault lies. [15:19] the icon name needs to be changed there [15:19] oh ok, just making sure someone's on it! [15:19] vish is very thorough though so we're good. :D [15:20] yeah, it will turn out richt [15:33] ;) [15:42] jcastro: Bug 538725 , i wasnt sure if seb128 would do an update for this renaming , if he is free we can push it today ;) [15:42] Launchpad bug 538725 in humanity-icon-theme (Ubuntu) (and 1 other project) "Banshee monochrome icon needs renaming (affects: 2)" [Undecided,New] https://launchpad.net/bugs/538725 [15:43] vish, no, that can wait after beta [15:43] banshee is not used in the default installation [15:43] yeah, my thoughts too :) [15:43] and it's only a minor graphical issue [15:47] jcastro, the bluetooth applet icon issue has been fixed by jpetersen, fix in bzr and uploaded to lucid for beta if they accept it now [15:47] jcastro, it looks slick without those 2 icons ;-) === MacSlow is now known as MacSlow|errand [16:48] https://lists.launchpad.net/ayatana/msg01012.html [16:52] MacSlow|errand ^ [16:59] vish ^ [17:01] kitallis: 2 - is forbidden ;) notify-osd allows click-thorough [17:01] yeah, i know [17:01] just a thought [17:02] kitallis: for more ideas , have a look at brainstorm and wishlist bug reports on launchpad [17:03] kitallis: for notify-osd , MacSlow is the main guy you need to be talking to and mpt who controls the design [17:03] s/controls/specifies [17:04] yeah, well, i just put it up there [17:04] i doubt design manipulations in a gsoc project [17:04] cause, well it takes a lotta time and planning [17:05] but, don't we all need a little configuration ability [17:59] seb128: I knew they would look better without the icons! [18:00] ;-) === MacSlow|errand is now known as MacSlow [18:16] kitallis, I know and read this... but I'm not the once deciding about that sort of thing. [18:17] kitallis, do you know the reasoning behind notify-osd being _not_ customizable? Just wondering about the scope of your initial research [18:20] MacSlow: probably because apps may have different configurations? [18:22] kitallis, no... first notifications are just that... notifications (no full dialogs), second... defaults should be so well chosen that the majority of users don't feel the need to be changing them, third every configuration option add code-paths that neede to be covered by test (automated ones and test be users actually using them) [18:23] "just add this option, it's not much work" has the very nasty potential to cause code-paths that may rot and quickly become unmaintained... we want to avoid that... also a kind of anti-bloat-ware attitude :) [18:24] kitallis: hi [18:24] kitallis, I don't want to go into further detail as all of this is either stated on the spec or has been discussed already in the ayatana-list [18:24] well, a "defaults should be so well chosen" doesn't seem like the best approach either? [18:24] kitallis: i think you're proposed gsoc project is actually going in the opposite direction of what i think our design team was going to [18:25] ie, not having user settings at all [18:25] well, i just figured that, because me, i find hard coded defaults kinda annoying [18:26] and that's mostly by design [18:26] kitallis, notify-osd is OpenSource... you can go ahead and create a fork for you own needs... and then let community-popularity decide :) [18:27] the idea at the start is that notifications should be so basic to the interface, that just one version would be needed [18:27] kitallis, I am not sure why you made this into a GSoC-propsal [18:27] and if that doesn't work in certain circumstances, to change apps or adopt a different approach, instead of going "oh well, i'll add an option then" [18:27] it may sound a bit surprising at first [18:28] i obviously didn't know about the strong devotion for that strict design rules [18:28] kitallis, that's the beauty of OpenSource... if you don't like something... change it... I do that with a couple of tools, libraries I use myself [18:28] and defaults [18:28] kitallis: no worries [18:28] oh, well [18:28] kitallis, np... just grab the code and hack away [18:28] i'll just dump the gsoc idea atleast. [18:28] kitallis: but that's been a topic of discussions quite a few times on the list [18:29] kitallis: i think there are other ubuntu project that you could help with [18:30] kitallis: projects [18:30] kitallis: for the desktop aspects we're working on, you really want to check opportunities with mpt on the design team [18:30] i really love the OSD [18:31] kitallis: hey ;) thanks [18:32] see, that. [18:32] i just wish i could change that irssi ping notif up there :P [18:32] kitallis, irssi? What's that? [18:33] IRC client? [18:34] kitallis, irssi pushes a notification if you've been addressed on an IRC-channel?! [18:34] kitallis, that sounds rather like a candicate to get support for the messaging-menu [18:34] yeah, it's just a little perl script [18:35] it's not officially supported if i'm not wrong [18:35] kitallis, this really feels like it should integrate with the messaging-menu instead of directly pushing a notification via libnotify [18:36] kitallis, tedg will gladly point you to the right document-pages on the wiki, if you're interested in this [18:37] yeah, sure. [18:37] wait, just a second, i was eating dinner all this while, kinda immobile :P [18:37] kitallis: MacSlow: Yeah the problem with libindicate is that it requires the process to keep running, while libnotify is more "fire and forget" [18:38] So for things like irssi it can't just be a triggered perl script. [18:40] tedg, ah... right... forgot that detail for a bit.