=== funkyHat is now known as funkyTones === funkyTones is now known as funkyHat === chaotic_ is now known as chaotic === MacSlow is now known as MacSlow|lunch === MacSlow|lunch is now known as MacSlow [15:29] qense: good job on the virt-manager bug, I was looking forward to tagging it but you were all over it! [15:30] jcastro: Whenever I find an application that uses the tray I file a bug, if it's not on the list yet. I've now got proof that it's worth it! ;) [15:35] tedg, there is a patch in https://launchpad.net/bugs/522151 fixing a problem with insensitive menu items [15:35] Launchpad bug 522151 in indicator-application (Ubuntu) "indicator-application does not support insensitive menu items (affects: 1)" [Undecided,New] [15:35] Recently the checkboxes in Indicator Application menus did stop changing state, they are either always active or inactive now. [15:45] jpetersen: Sweet! === jpetersen_ is now known as jpetersen [16:16] jpetersen: thanks for the updates [16:16] jpetersen: hmm, where is the upstream bug for gnome-settings-daemon? [16:17] jcastro, I will look, I just wanted to update the upstream bug [16:17] cool, I just noticed it wasn't linked in lp [16:21] jcastro, is there an upstream connman-gnome bug? [16:23] I don't think so [16:25] jpetersen: marcel is more of a mailing list guy, you might have better luck mailing his list. [16:25] jcastro, ok [16:26] kenvandine: Can you cherrypick this? https://code.launchpad.net/~ted/indicator-application/sensitive-522151/+merge/19876 [16:26] tedg, kenvandine: I do that [16:27] seb128: Thanks! [16:27] np [16:30] seb128, thx [17:31] Nafai: ping me when you're ready to start today, I have a change [17:33] jpetersen: which apps are you working on today? === MacSlow is now known as MacSlow|break [17:46] jcastro, I just finished connman-gnome, I wanted to push some patches upstream now and than start with packagekit-gnome [17:46] https://bugs.edge.launchpad.net/indicator-application/+bug/524150 [17:46] Launchpad bug 524150 in indicator-application "Menus updated at runtime aren't rendered correctly (affects: 1)" [High,In progress] [17:46] so this bug is blocking nafai's apps [17:46] the problem is Cody is going to be unavailable to look at this [17:46] I was wondering if you could look at this [17:48] jcastro, yes I will look at it [17:49] that's blocking like 2 of his apps that we ship by default, so a fix here would be a big win [17:49] jpetersen: thanks! [17:51] ping [17:51] :) [17:52] Nafai: ok so since bratsche is unavailable to fix 524150 I'm hoping that Jan might be able to figure it out [17:52] Awesome [17:52] Nafai: so other than those 2 it leaves Vino right? [17:52] Yeah [17:52] I'm almost done, I'm down to a couple of calls I need to replace [17:53] excellent! [17:53] I need to find an appropriate replacement for this: [17:53] screen = gtk_status_icon_get_screen (GTK_STATUS_ICON (icon)); [18:05] tedg: Hey quick question. I'm needing to replace this call that is in the Status Icon using code of vino: [18:05] screen = gtk_status_icon_get_screen (GTK_STATUS_ICON (icon)); [18:05] Is there a sane way that I can get the screen? [18:06] Nafai, what is it used for? [18:06] One of them is this: gdk_spawn_command_line_on_screen (screen, "vino-preferences", &error) [18:07] And the other is a call to gtk_show_uri, where the first parameter is the screen [18:07] Nafai: There is no way to really know the screen that the menu is being shown on. Instead it should use the default screen. [18:07] Nafai: I suggested that it wasn't perfect to do that, and mclasen yelled at me saying the function is perfect :-/ [18:08] Yes I would use the default screen for that also (gdk_screen_get_default ()) [18:08] thanks [18:57] tedg: are tooltips going to eventually be supported in the application indicator? [18:57] hyperair: Not for Lucid for sure, I don't know about long term. [18:58] tedg: i see. do you happen to know how gnome-power-manager handles this? [18:58] tedg: how does gpm tell the user how much time is remaining? [18:58] for battery i mean [18:58] hyperair: I think it uses a top menu item, but I'm not sure. https://wiki.ubuntu.com/CustomStatusMenuDesignGuidelines#tooltips [18:59] Nafai: Did you do gpm? ^ [18:59] nope [18:59] can't remember if that was jpetersen or smithj [18:59] pitti [19:00] wasn't me [19:00] tedg: why are tooltips not supported by appind? [19:01] hyperair, it should be displayed in the menu item of the battery [19:01] hyperair: "Like other menus, status menus do not have tooltips." from https://wiki.ubuntu.com/CustomStatusMenuDesignGuidelines#tooltips [19:01] hyperair: To match normal menus. As they goal is to make them as much like menus as possible. [19:01] tedg: that states that status menus do not have tooltips. i want to know *why&* [19:02] tedg: even toolbar icons have tooltips, you know? [19:02] smithj: hey what's up with g-d-u? [19:02] tedg: supposing i don't recognize the icon of the application i'm looking for, how do i identify which icon it is? click on each one and examine the menu? [19:03] jpetersen: is g-s-d ready to be looked at by the desktop team? LP #497875 [19:03] Launchpad bug 497875 in libgnomekbd (Ubuntu) (and 1 other project) "Support Application Indicators (affects: 1)" [Wishlist,Confirmed] https://launchpad.net/bugs/497875 [19:03] jcastro, yes [19:04] jcastro: i need to implement the fading-window thing that mpt said [19:04] actually, i meant to ask... is there a library for that somewhere? or at least an example i could look at [19:05] hyperair: One would hope that an application that you start and use enough to enable it's application indicator, you'd know that icon. But other than that, yes. Most people couldn't tell you why an "Edit" menu is called an "Edit" menu, they're just comfortable exploring their because they understand the risks involved with menus. We're trying to provide the same easy exploration by using a standard menu meme. [19:05] Nafai, I have a patch for LP #524150 can you try it out? [19:05] Launchpad bug 524150 in indicator-application "Menus updated at runtime aren't rendered correctly (affects: 1)" [High,In progress] https://launchpad.net/bugs/524150 [19:05] jpetersen: Sure, if I can figure out how to get the deb built locally [19:05] smithj: We're past feature freeze, I think the best thing to do now is just get it ported and in the distro [19:05] Last time I tried it failed :) [19:06] tedg: one would hope that i'd recognize an application *i start*. what about applications that start upon startup? [19:06] hyperair: Like? [19:06] tedg: i don't know, the theoretical application. [19:06] jcastro: oh, ok. i was most of the way done with porting when mpt said that, so i should be able to clean up the patches pretty quickly [19:06] Nafai, I can build you the deb [19:06] smithj: please do. We'll have to revisit it for L+1. [19:06] hyperair: Heh, we'll fix it to not start on startup ;) [19:07] tedg: unless you're saying that applications which start when logging in should not have application indicators, period. [19:07] jpetersen, cool x86_64, plz :) [19:07] tedg: pardon me for being blunt, but i feel this is a retarded design. [19:07] hyperair: I think we're saying that applications shouldn't start on logging in unless the user requests them to. [19:07] hyperair: Which would require the user running them and configuring them to do so. [19:07] smithj: freeze for A3 is like tomorrow so we need as many done ASAP. [19:08] and after all that was said about being more conservative about adding/removing features for an LTS i.e. lucid, adding application indicators, removing tooltips seems like a massive change to me. [19:08] jcastro: so we can't continue porting after feature freeze? [19:08] Nafai, oh I only have i386 [19:09] hyperair: Heh. I'd have a hard time calling "tooltips" massive ;) [19:09] smithj: we've got the default apps almost done, after that it'll be best effort but let's concentrate on finishing up what we have now. [19:09] Tell me how to build and I will [19:09] k [19:09] tedg: it is for certain applications, especially media applications like banshee. [19:09] smithj: would rather get 8 solid ones done and accepted upstream and 20 half finished ones that have no chance of making it into Lucid [19:09] tedg: now i have to open my media application's huge window to figure out what song is currently playiing. [19:10] tedg: it doesn't even take a child to count how many more clicks and tell you how much more inconvenient that is. [19:10] hyperair: I think that is an issue. But I don't think just adding back tooltips will fix it appropriately. [19:10] hyperair: Usability can't be defined by the number of clicks. [19:10] tedg: but accessibility of features can. [19:11] hyperair: It's like measuring programs by Lines of Code. Easy to measure, but not useful. [19:11] tedg: you're making me jump through hoops to query for information which used to be easily accessed. [19:11] smithj: what else is on your list that isn't in Lucid? [19:12] jcastro: what do you mean by "isn't in lucid"? [19:12] that hasn't been committed yet? [19:12] right [19:12] tedg: and if that's not enough, the menus look ugly when your icons are pushed inwards [see: http://files.qense.nl/Schermafdruk.png] [19:12] hyperair: We'll have to agree to disagree that tooltips are critical for Lucid. [19:12] I just want to make sure all the bugs that are finished are assigned to the desktop team [19:13] i sent the patch for hplip, don't think ken has gotten to it yet [19:13] i'm working on gdu and seahorse [19:13] tedg: i really like ubuntu development goes these days. "i'll just implement things my way, and if you don't agree with me, we'll agree to disagree." [19:13] well specifically the (d|u)x things [19:15] hyperair: https://wiki.ubuntu.com/CustomStatusMenuDesignGuidelines#icons [19:15] smithj: ok let's not even bother with seahorse, finish off g-d-u please. Based on if/when Jan/Nafai fix this cascading menu thing I might need to you do policy-1-gnome instead [19:15] jcastro: ok [19:15] tedg: i also wonder how a11y things go with indicator applications. i highly doubt that text-to-speech can read icons to a blind user. [19:15] jcastro: just let me know. i was figuring out vala last night though... would be a shame to waste that knowledge :-P [19:16] hyperair: So you're saying that a11y was better with the notification area? [19:16] tedg: i'm not saying it's better with the notification area, but i'm saying it's impossible without tooltips. [19:16] tedg: unless you're telling me you can find a way to read out icons to a blind user. [19:16] tedg: icons without tooltips, mind. [19:17] smithj: we'll get back to it at some point I am sure, just want to get things in the default install on the CD for A3. Or if not right after. [19:17] hyperair: So, we've made it better. Not perfect yet. [19:19] tedg: right, so we're going to push this imperfect solution onto users in an LTS. [19:20] hyperair: Yes, I think OpenOffice is imperfect too. But, it being LTS doesn't meant that all problems are always solved 100% ;) [19:20] Nafai, bzr clone lp:ubuntu/indicator-application [19:20] tedg: openoffice has been there since the beginning of time. that is besides the point. [19:21] Nafai, apply the patch and dpkg-buildpackage -rfakeroot [19:21] tedg: i'm talking about throwing away features for an imperfect solution that does not give back enough. [19:21] tedg: and all that in an LTS. [19:21] tedg, can you look at the patch attached to LP #524150 Nafai could test it with gnome-bluetooth [19:21] jcastro: Yes. The question is whether that's a plus or minus. It makes the menus "non standard".... though it provides information. I'm not against tooltips, but I feel that we need to start small. [19:21] Launchpad bug 524150 in indicator-application "Menus updated at runtime aren't rendered correctly (affects: 1)" [High,In progress] https://launchpad.net/bugs/524150 [19:22] hardy was a miserable LTS already, why must we keep repeating the same mistakes and implement loads of crazy life-changing shit in our LTSes? [19:22] jpetersen: Will do. [19:23] smithj: what days are you planning on working this week? During the week at all? [19:24] http://www.notmart.org/misc/statusnotifieritem/statusnotifieritem.html <-- for some reason i see tooltips in this specification. are we having a completely different specification implemented? [19:24] * tedg loves that his work is considered "life-changing" he only thought it was little icons. [19:25] hyperair: We're not implementing the tooltips in the KSNI spec. They're optional. [19:27] tedg: i can't leave my pointer over gpm's icon and watch my battery time while reading something else in the background, and i have to click banshee's icon, wait for it to get swapped in, see the current playing artist/title and then hide it again. [19:27] jpetersen, Okay, I'll take a look now [19:27] tedg: those aren't minor changes in usability. [19:27] jcastro: i can if needed [19:27] tedg: and neither of them are positive changes either. [19:27] Nafai, ok [19:28] tedg: in fact, what do application indicators have that the notification area didn't provide besides "standardized look and feel"? [19:28] i think we've lost more than we've gained. [19:28] I am off for the day, bye bye [19:28] thanks jpetersen! [19:28] thanks jpetersen :) [19:28] Yes, thanks [19:29] Hope this works! :) [19:29] Nafai: I hope so too [19:29] jono: How did your scale talk go? [19:29] Nafai, hey! [19:29] went well [19:29] just coordinating repeating it on ustream.tv :) [19:29] Nafai: at a minimum we can get Vino in today I hope? [19:29] hyperair: No offense, but I'm tired of this conversation at this point. You are entitled to your opinion, I just happen to disagree. [19:29] Nafai, just leave the feedback in the bug report, I will look into it tomorrow again if there is still something broken [19:29] jcastro: Yes, pretty close :) [19:29] jpetersen, will do [19:30] Nafai, thanks [19:30] tedg: well thanks for your time, and for forcing your opinion on everyone who does not agree. [19:30] hyperair: you're better off discussing this with mpt, the DX guys just implement what the design team does [19:30] oh him again. [19:30] last i remember, i had a flame war with him on the list regarding update-notifier popping up automatically [19:31] which incidentally was left unresolved, with mpt just brushing aside all opinions [19:31] total epic win. [19:31] honestly, where the hell are we going? [19:32] ok so dude, let's calm down for a sec [19:32] i've had a whole day to calm down. [19:32] hyperair, what are your primary concerns? [19:33] jono: tooltips. [19:33] hyperair, what about them? [19:33] jono: because apparently tooltips aren't necessary to tell what icons are/do [19:33] hyperair, right [19:33] and what is the problem? [19:34] jono: i can't query the current playing track in banshee/rhythmbox without opening the main window, and i can't query my battery status without clicking on gpm. [19:34] hyperair, right, and how have you engaged around the solution? [19:34] hmm? [19:34] engaged meaning? [19:35] tried to comunicate the issue and resolve it? [19:35] discussed with upstream, various other people, some people implementing indicator applications, and tedg, as you saw just now. [19:35] hyperair, and what is the conclusion? [19:36] jono: that my opinion is utterly and totally rejected with no good reason. [19:37] hyperair, why do you feel that way? [19:37] jono: because i have not seen a good reason for ditching tooltips. [19:37] Nafai: ok, so I guess it's up to you to test it and hope we don't need jpetersen for the rest of the day. [19:37] Yeah, but this time it isn't even showing the device menus :( [19:38] ugh [19:38] Yeah [19:38] tedg: help? [19:38] hyperair, so you feel you were rejected because they have not implemented what you want? [19:38] jono: no, because tedg said they were not going to implement it. implying that it is a conscious decision to get rid of tooltips. [19:39] Nafai: Uhg. Uhm, so it doesn't show submenues? [19:39] jono: similar to having update-manager pop up on its own, but at least that could be disabled. [19:39] hyperair, maybe it is? [19:39] jono: if it is a conscious decision to get rid of tooltips, then i'd at least expect to see a good reason. [19:39] that doesnt mean you were "utterly and totally rejected with no good reason" [19:39] jono: but there was no reason given. [19:39] tedg, Yeah, in gnome bluetooth, there are submenus for the devices. with jan's latest patch, they don't show up at all [19:40] tedg, is there a reason? [19:40] Nafai: Hmm, okay, let me look, it probably doesn't recurse. [19:40] thanks [19:40] bbiab, getting lunch [19:40] jono: (01:01:47 PM) tedg: hyperair: To match normal menus. As they goal is to make them as much like menus as possible. [19:41] right and normal menus dont have tooltips [19:41] to which i mentioned that they're more like toolbar icons with menus dangling from them. [19:41] menus have text. [19:41] if you wanted to match menus, you'd get rid of the icons and use text for them instead. [19:41] hyperair, you want each menu t have a tooltip? [19:41] but that's obviously not going to work. [19:41] jono: toolbar icons have tooltips, yes? [19:41] hyperair, I am talking about the menus [19:42] do you want each item on an app indicator to have a tooltip? [19:42] precisely. [19:42] or could a tooltip for the icon solve what you need? [19:42] the icon [19:42] I mean the main app indicator icon [19:42] yes, the app indicator icon [19:42] tedg, can you have a tooltip for the app indicator icon? [19:42] that seems sane to me [19:44] jono: Not for Lucid. I imagine we'll reopen the discussion for Meandering Marmot. I'm not against them. I'm just not sure they're required. With the new placement the Fedora guys did they're not as annoying on menus, so that helps a ton. [19:44] hyperair, so why don't we discuss this for Lucid+1? we are a bit late in the cycle to do this now [19:44] jono: I think the two features "up for discussion" right now for M is scroll wheel and tooltips. [19:44] does that sound ok? [19:44] that sounds fine. [19:44] hyperair, awesome :) [19:45] =) [19:45] we want to ensure our friends such as yourself are happy :) [19:45] well thanks. that's nice to know. [19:45] sorry I can't chat more, have a meeting in 15 and need to go and put trousers on :) [19:45] haha [19:45] nice picture jono! [19:45] kenvandine, lol [19:46] Does anyone know if the fall-back mechanism is supported by AppInd's Mono bindings? [19:47] qense, it used to work.. [19:47] so it should [19:47] aww, bad formulated sentence [19:47] i am almost certain it did in tomboy [19:47] I meant: can you override the default fall-back mechanism? [19:51] not sure [19:52] I couldn't find anything in the Tomboy patch and AppIndicator support doesn't seem to be in the Tomboy version on Lucid yet. [19:52] qense: tomboy won't be ported [19:53] it uses custom UI for pins and we didn't want to break that in lucid [19:53] I already thought I heard something like that. [19:56] qense: In theory, the custom fallback stuff should work, but I'm not sure how it would work. Sorry. But if it doesn't work, that's a bug :) [19:56] tedg: Ok then, I'll try to see if it works. [19:58] hmm , is it the design to not have tooltips for the app-indicators? or is it still in the works? [19:59] vish: jono: Not for Lucid. I imagine we'll reopen the discussion for Meandering Marmot. I'm not against them. I'm just not sure they're required. With the new placement the Fedora guys did they're not as annoying on menus, so that helps a ton. [20:00] :( [20:01] hehe , that was just discussed a few lines above :p [20:01] * vish should read scroll-backs more [20:01] I just arrived [20:02] can sb pastebinit? [20:07] artir: the logs are available at irclogs.ubuntu.com [20:26] of course [20:26] XD [20:26] i forgot [20:49] tedg: Nafai: any luck with those menus? [20:49] Nafai: also, power-manager is now in. \o/ [20:51] tedg: Is it possible to not use the fallback mechanism and only make appindicator work when Indicator Application is available? I would like the class calling it to fail so the application can continue with trying other options. [20:51] jcastro: Looking. [20:52] qense: You'd have to subclass the object and set the fallback and unfallback functions to be empty functions or null. [20:52] tedg: ok, then I'll do that [20:52] thanks! [21:02] Back from lunch, btw [21:18] Sweet, now to just add a menu item indicating status and vino is hopefully done :) [21:25] will networkmanager be migrated to the new indicator system? [21:26] artir: no [21:26] because it's a bit weird to have power,sound,session,messaging and me menues [21:26] and not having a net indicator [21:26] I assume because we don't yet have the necessary widgets for nm? [21:27] yeah but it requires all sorts of custom widgets [21:27] what Nafai said [21:28] I predict that it'll be migrated maybe in lucid+2 or even +1 [21:33] Nafai: I'm getting submenus... can you build this branch and see if works for you? lp:~ted/indicator-application/menu-updates-lucid [21:33] tedg, Sure thing. I'm guessing I'll have to restart the service? [21:33] Nafai: Not the service, bluetooth-applet though. [21:34] ok, thanks [21:38] tedg, having trouble trying to build with dpkg-buildpackage -rfakeroot [21:38] /bin/sh: /home/nafai/Work/Ubuntu/menu-updates-lucid/./configure: not found [21:38] Nafai: I'd just do "debuild" [21:38] Nafai: Oh, you need to ./autogen.sh [21:38] * Nafai tries that one [21:39] Okay, and then debuild? [21:39] Yeah, I think debuild -us will not ask for my password ;) [21:39] But, it doesn't matter if you don't know it. [21:54] tedg: A bit closer, but not quite: http://www.travishartwell.net/bluetooth-latest.png [21:55] Nafai: I'm unsure why you have that double separator... [21:55] Nafai: I think the blank item is the menu tear off, which I odn't understand. [21:55] Oh, wait, I think it should be for each instead of for all. [21:55] All that should show in the submenu is send files and browse files [21:55] tedg: I had triple separators when I left a placeholder in the menu declaration. [21:56] removing the placeholder solved it [21:56] actually, double as well: I removed one separator and the placeholder. [21:56] anyway, I'm off for this day, bye! [22:52] Nafai: Can you pull that branch again and tell me how things look for you? [23:00] Hi, I'm going to submit a bug in Skype's bugtracker asking them to support the messaging menu.. Could someone point me towards documentation of the api? [23:08] Nafai: how's it looking?