=== smorar__ is now known as smorar_ === smorar_ is now known as smorar__ === gord|afk is now known as gord [01:05] Newbie question: If a branch is started to fix a bug is started and fixes the bug does that mean the bug is fixed? [01:06] And no other development is needed for it? [01:06] rbnswartz: The bug isn't fixed until that branch is merged to trunk and a release is made. [01:09] Okay I was working on the bite sized bugs (the workspace indicator being useless with only one workspace) and the code looks like what I was going to do for my fix. Should I start on another bug? [01:12] If there's a branch that fixes the bug then I'd move on to another bug; if it that branch doesn't get merged to trunk soon I'd check out why and see if you could prod it along, though. [01:14] Any suggestions for a bug to work on? (I am a competent c++ programmer) [01:15] Anything on the bitesized bugs list should be good. I'm not familiar with the unity or compiz source to be able to point out anything beyond that. [01:15] DBO's a good source of bugs to fix, but he's probably asleep :) [01:15] I dont go to bed at 8:15 :P [01:16] Any suggestions DBO? [01:16] I am however arguing politics on reddit [01:16] mmm [01:16] rbnswartz, define competent [01:17] I would have called myself competent for most of my programming careers... its only now I realize I am far from it [01:17] DBO: Fix indicator-datetime so I can get a world clock, and I'll stop suggesting you sleep at 8:15 :P [01:17] RAOF, stop having such glorious hair and I'll stop calling you Fabio [01:18] Why would I want to lose such glorious hair? :) [01:18] you're giving all the lions in african "mane envy" [01:19] rbnswartz, I am looking through bugs for you [01:19] In that case I'm a newbie. I know c++ and a little gtk [01:19] rbnswartz, what kind of time investment are you looking for? [01:21] Anything that will be relatively easy to fix that doesn't require someone with a large amount of skill. [01:21] rbnswartz, this one is probably a good one: https://bugs.launchpad.net/unity/+bug/683135 [01:21] Ubuntu bug 683135 in unity (Ubuntu) "the launcher autohiding is not blocked by the trash launcher" [Low,Triaged] [01:21] actually I dont know if thats valid anymore [01:21] I just redid all that code... [01:22] mmmm [01:22] I was looking in the bitesize list [01:22] ya? [01:23] I follow jono bacon on twitter and I thought fixing a bite-sized bug would give me an opportunity to help out (a dream come true) [01:23] yeah its just a lot of bugs are not so... bite sized [01:24] we have had a lot of people snatch up the easy ones already [01:24] Im trying to dig out an easy one [01:25] how hard would the launcher autohiding but be to fix you think? [01:26] someone just fixed it [01:26] I was mentoring him [01:26] good for him [01:27] ...frustrating [01:28] OH! [01:28] I know [01:28] click behavior on windows [01:28] it needs more work to be a smart behavior [01:28] it should give preferential treatment to Urgent windows [01:28] so if there is an urgent window, it takes you to it no matter where it is [01:28] rbnswartz, ^^ [01:29] kvalo, one of the geoclue providers uses something ofono provides [01:29] Where would I look in the source for the code that handles this? [01:30] rbnswartz, src/BamfLauncherIcon.cpp [01:32] Okay I haven't looked a that piece of code yet I'll be sure to study it. [01:37] DBO what do you mean by take you to it? Do you mean have it on top of the windows that are currently displayed? [01:37] it should call activate () on the window [01:38] basically if there are *any* urgent windows, we activate them and them only [01:38] basically we ensure that a click clears the urgent status [01:39] like the flashing highlight we have in gnome when a window need immediate attention? [01:39] yes, that is called urgent :) [01:39] got it. [01:40] in unity we represent this (right now) by flashing the icon, and glowing the icon [01:40] however a single icon may manage multiple windows [01:40] so when we focus windows, we have to ensure we give priority to urgent windows [01:42] rbnswartz: welcome to the bitesizer program! [01:43] thanks jcastro it has been a dream of mine to be involved in ubuntu. I saw this as a chance to get involved. [01:43] awesome, you're like the 4th person to show up, we're going to build quite a squad at this rate! [01:44] how about this one? https://bugs.launchpad.net/unity/+bug/685639 [01:44] Ubuntu bug 685639 in Unity "Implement launcher border for floating mode" [Undecided,Confirmed] [01:44] no one seems to be working on that [01:44] What do you think DBO? [01:45] well you and jono keep talking about it on twitter about it so I thought might as well. [01:45] floating mode is going the way of the dinosaurs [01:45] I think i broken it recently even [01:45] hilariously, nobody has reported the bug yet [01:45] heh [01:45] haha [01:46] going to yank it? [01:46] yep, broken [01:46] yeah, it doesn't make much sense really [01:46] with intellihide, floating is much help [01:46] isn't [01:48] i always thought it was kind of useless, but I wasn't about to say much if you guys wanted to put effort into it heh [01:48] DBO: if 683135 is bitesize can you mark it so pls? [01:48] DBO: also, we're kind of running out for this week, got any more you can tag? [01:48] bug #683135 [01:48] Launchpad bug 683135 in unity (Ubuntu) "the launcher autohiding is not blocked by the trash launcher" [Low,Triaged] https://launchpad.net/bugs/683135 [01:48] jcastro, I am not even sure its valid anymore [01:49] I am pretty sure its not [01:49] https://bugs.launchpad.net/unity/+bug/687956 [01:49] Ubuntu bug 687956 in unity (Ubuntu) "should display the launcher tooltips after a delay" [Medium,Triaged] [01:49] aha, what about this one [01:49] jcastro, not bitesize but jamal is working on it [01:50] it might be useful to show him how to snag "Assigned" so it's more obvious to me before I dole them out [01:50] I think I might be able to handle that one. [01:50] maybe [01:51] DBO: and/or mark it In Progress [01:51] all I would have to do is insert a timer of sorts into the mouseover event right? [01:52] * jcastro keeps looking for more [01:52] jcastro, done [01:52] rbnswartz, no I dont want it done that way [01:52] rbnswartz, essentially what we want is a static method in LauncherIcon.cpp [01:53] this method can be used as a global control for tooltips [01:53] then Launcher can turn them on and off as it sees fit [01:53] this way when design changes their mind about how it works, it's not a problem [01:53] DBO: hey what about feature-parity bugs for having webapps in the launcher? how easy are those? [01:53] * jcastro pines for his gmail icon on his launcher [01:54] not bitesize... [01:55] alt-f2 support? [01:55] OH! [01:55] thats not a small one [01:55] but a fun one for sure [01:55] come to think of it [01:55] should Alt+F2 just shortcut the dash? [01:55] maybe? [01:56] hmm, how about quicklists on the trash can? [01:56] jcastro, the problem with papercuts/bitesize bugs is we tend to fix those on our own [01:56] I notice those are missing [01:56] that one is bitesize [01:56] so is quicklist on the workspace switcher [01:56] is there a bug for that? [01:56] ohh, two new ones [01:57] lemme think [01:57] so yeah there is that indeed... [01:57] ok so let's start small [01:57] quick lists for the trash can [01:57] I have to scoot fellas if you find something for me send me an email rbn.swartz@gmail.com [01:57] that'll get rbnswartz up to speed on like the workflow and stuff [01:58] rbnswartz: what's your launchpad id? [01:58] rbn-swartz [01:58] rock on, I'll get back to you once I have it filed and whatnot [01:58] jcastro, implementing launcher scrolling is bite sized [01:59] which bug is that? [01:59] you assume there is a bug [01:59] so cute... [01:59] ok, I'll make you a deal, you file that one and I'll file the trash can one [01:59] done [01:59] first let me check the spec [02:00] I always gotta see if they dropped this shit [02:00] nothing in the spec about it [02:00] I will assume we are good to go [02:00] https://bugs.launchpad.net/ubuntu/+source/unity/+bug/683547 [02:00] is this it? [02:00] Ubuntu bug 683547 in Unity "Bottom launchers hard to expand with filled launcher bar, need edge scrolling" [Medium,Triaged] [02:02] no [02:02] edge scrolling is of course part of it [02:02] but I mean mouse wheel scrolling [02:02] edge scrolling is also bite sized [02:02] ok so I can mark edge scrolling? [02:02] yeah [02:02] er, tag it? [02:02] ok [02:03] its probably going to be a 20 line patch [02:03] awesome [02:03] ok, I can file a new one on "launcher needs to support mouse scrolling" or something like that? [02:03] https://bugs.launchpad.net/unity/+bug/688406 [02:03] Ubuntu bug 688406 in Unity "Launcher does not respond to scroll events" [Undecided,New] [02:04] I am the worlds worst bug reporter by the way [02:09] DBO: thanks for the rely on my mail re windows underneath the dock [02:09] i replied? [02:10] yes [02:10] oh [02:10] with a token "please like me" [02:10] it was an awesome email [02:10] haha [02:10] you should have seen the email I got to write dbarth the other day [02:10] he emails me a list of action items and asks for a progress report on them [02:10] after each bullet point: "Done" [02:11] nothing else in my reply [02:11] amazing [02:11] http://rageguy.com/media/2010/07/fuck-yea.png [02:11] <3 [02:12] <3 [02:22] Hey make it so my windows don't go past my panels [02:22] that's annoying [02:26] While you're at it, make it so evince doesn't start with ~20 pixels on the top of this workspace and the rest on the workspace above :P [02:30] DBO: is that proposal what I've been waiting for? [02:30] woo! [02:32] donno [02:32] its not perfect yet [02:32] but I am working on it still [02:32] its also far from animated... === ssj6akshat is now known as akshat|school [06:24] morning [06:58] RAOF: the evince bug is fixed upstream in compiz [06:59] RAOF: it is just not packaged yet (since the diff is like humungous) [06:59] because I fixed about 30 or so other bugs at the same time [06:59] jcastro: there's a discussion on ayatana-list about letting windows go past panels. I started it :) [07:02] didrocks: mornin [07:03] didrocks: I got the shadows stuff working, maybe we can upload unity-window-decorator soon ^_^ [07:03] good morning smspillaz [07:03] smspillaz: oh nice! [07:03] smspillaz: should it be part of compiz, or unity? [07:05] didrocks: it is currently in my compiz userrepo [07:05] didrocks: we can ship it as part of unity though [07:06] smspillaz: yeah, that will make more sense. So merging that in unity source and such [07:06] although there's no point doing the contributor agreement on it since it is based on other code [07:07] didrocks: It will be fairly easy to merge in with the unity source since the buildsystem is based on when I did the "modular" buildsystem for compiz a month ago [07:08] didrocks: so you can just shove it anywhere you want and then add_subdirectory (decorator) and it will Just Work [tm] [07:08] smspillaz: sure as it's basically create a directory and drop stuff in it :) [07:08] ok :) [07:09] didrocks: also, there are going to be a couple of new plugins for unity like my dialog handler so I will propose a merge to make the buildsystem build multiple plugins [07:09] smspillaz: what's the dialog handler again? [07:10] smspillaz: maybe rather than a patch, we should then create a new source [07:10] didrocks: oh for the decorator we need a new source [07:10] the patch would be huge [07:10] also we need to patch metacity in order for it to work [07:10] smspillaz: hence the fact that is can be in unity itself [07:10] didrocks: yeah [07:10] smspillaz: but the dialog handler? [07:11] I'll try and re-sync it to the master decorator every so often, though I don't imagine I'm going to be doing much work on the master gtk-window-decorator anywaysy [07:11] didrocks: the dialog handler is a little plugin to pin modal dialogs to windows [07:11] so that they move/resize etc in sync [07:11] nice [07:11] also it dims the parent [07:11] oh right! [07:12] smspillaz: maybe a new source with all our plugins [07:12] didrocks: it's been in launchpad for a while now [07:12] didrocks: well I was thinking something more like this -> [07:12] lp:unity so you have unity / [07:12] err [07:12] unity/ [07:12] and then inside that you've got [07:12] vala/ [07:12] dbus/ [07:12] blahblah/ [07:12] foo/ [07:12] plugins/ [07:12] inside plugins you've got [07:12] unityshell/ [07:12] unitydialog/ [07:13] and then I have a cmakelists.txt which automatically adds both and compiles them [07:13] works for me [07:13] didrocks: there was also going to be some work done to split out most of unityshell from the unityshell plugin and turn unityshell into unitybridge [07:13] so we'll have a libunityviews and unitybridge links and compiles against that [07:15] smspillaz: aren't you afraid that we end with too many plugins? [07:15] I mean, compiz is already slow to start one plugin at a time [07:15] and I have a pretty descent machine [07:15] didrocks: we're going to compile them into core and toss the ones we don't need [07:16] so we can zip through the plugin init phase really quick [07:17] smspillaz: if we can prevent depending on profile, user to remove some plugins :) [07:17] yeah, easy [07:17] well by compiled into core, I mean you can still disable them [07:18] we can just specify certain plugins on the command line for the unity session [07:18] (like we already specify "ccp") [07:18] no command line please [07:18] we already discussed that :/ [07:18] should be the profile defining that [07:18] didrocks: how did you make it automatically load the ccp plugin then ? [07:19] smspillaz: it's the distro-patch which add unconditionnally ccp to the command line [07:19] but no other plugin should be set [07:19] hrm ok [07:20] and you're sure there's no way for us to specify to gnome-session for, the unity session to load "compiz --replace ccp move resize decor" [07:20] smspillaz: and what about people launching compiz --replace then? [07:20] smspillaz: you don't want people to provide the full list everytime they are trying to debug it [07:20] didrocks: those plugins are still enabled, but if they try to disable them, they will actually get disabled [07:21] smspillaz: so, they can disable it this way, it looks wrong… and you told me that it can be enabled twice by this way [07:21] didrocks: it removed duplicates [07:21] *removes [07:21] smspillaz: not what you told me one month ago :) (I have the logs if you want ;)) [07:22] didrocks: I only committed the change recently [07:22] like 3 days ago :p [07:22] smspillaz: but in any case, that doesn't make sense, it should be a settings in the profile [07:22] oh ok :) [07:22] commandline for that just seems hackish [07:22] didrocks: it does, but at least it makes debugging easier when compiz doesn't try to fight you when you disable plugins [07:23] smspillaz: and why is a profile settings wrong then? [07:23] if it's implemented the same way [07:24] didrocks: if the user does compiz --replace in the unity session and tries to disable "mandatory plugins" it will not let them [07:24] this is annoying for debugging [07:25] didrocks: btw, I definitely agree with you that this could work well in the profile (eg a mandatory_plugins section) but for now this works fine [07:27] smspillaz: well, it's a settings, so I think he can still fiddle with it if needed, isn't it? [07:27] smspillaz: so I think we should stick to that [07:27] smspillaz: so, basically there is some code to prevent a plugin to be disable again if set in the command line, right? [07:27] on* [07:30] didrocks: yes, basically anything on the command line == always on, even if you try to unload it [07:31] smspillaz: ok, so it should be easy for us (== non compiz hacker) to add the profile settings based on that [07:31] so that you don't have to deal with it [07:31] so you want to do it the profile way then ? [07:32] like, I can do either way, just saying that the cmdline way was already done :) [07:32] smspillaz: yeah, it's really the only way to have consistent experience with fallback mode, people using compiz --replace and such [07:32] smspillaz: but if you don't want to do it, we can catch it, no worry :) [07:32] smspillaz: I would prefer that you get the num workspace/viewport working back for my Monday upload :) [07:33] smspillaz: oh btw, I mesured the amount of gconf writing on switching profile, it's 2x900 keys! [07:34] totally insane :) [07:35] didrocks: oof [07:35] didrocks: yeah, I say that come beta time we start distro patching to nuke useless options [07:36] didrocks: Compiz: We're a bunch of indecisive programmers so we'll just give you a shit-ton of options and let you work it out for youself [07:36] smspillaz: well, not sure for this cycle to be honest. I would prefer we can that in mind for the gsettings backend to at least *point* to the right profile, not copy it :) [07:36] smspillaz: I really really wonder why it was decided to be this way :) [07:37] smspillaz: yeah, and too many options == too many unknown combination == too many bugs [07:37] didrocks: it was to maintain compatibility with the legacy gconf plugin iirc [07:37] didrocks: it is the best unit testing ever ^_^ [07:37] smspillaz: yeah, but why the legacy gconf plugin used to be this way :) [07:37] didrocks: we get users with all kinds of weird configs and you file strange corer case bugs [07:37] yeah, it's a nice gconf stress tests :) [07:38] didrocks: legacy gconf plugin did not support profiles, it only read from /apps/compiz [07:38] smspillaz: right, and that's why I think some sanity in the future can be nice for the compiz project (but hard politically) [07:38] smspillaz: ok, "make sense" (if we can tell it that way) then [07:39] didrocks: we can keep the options, they don't really create too many problems believe it or not [07:39] smspillaz: for instance, for most of the workaround, if they know to not working without the workaround, it should be enabled and not proposed to be disabled [07:39] like the java one [07:39] didrocks: workarounds break some things though [07:39] like the java workaround *could* incorrectly detect windows and make them the wrong window type [07:39] smspillaz: well, I think it's a tradeoff… [07:39] smspillaz: in bamf, there are a lot of workarounds [07:39] it is better to keep it an option [07:40] yeah, but bamf is different [07:40] because window detection can be perfect [07:40] because you've got hardcoded almost everything there [07:40] hum… [07:40] compiz is designed to be flexible. If we didn't have all these options, and enforced some really strict API with not many plugins you'd have something as hard to work with as mutter [07:41] this is why porting unity was relatively easy :) [07:41] I don't think the API should be strict [07:41] because you can just disable this, disable that, enable this [07:41] just that the option should be sparsely choosen to sane default and not offer so much tweaking and possible breakagee :) [07:42] but well, that's another discussion, let's go back to work (for me ;)) [07:42] evolution, here I come :) [07:43] didrocks: yes, I agree we need better defaults [07:44] smspillaz: oh, maybe the rally time can be nice to seat down, you, neil, a designer and me and revisit this? [07:44] smspillaz: like taking 2 hours and tells "we want that for natty" [07:44] didrocks: oh definitely [07:44] smspillaz: I'll add this to the agenda then :) [07:44] didrocks: we can even work out some sane defaults for upstream compiz too :) [07:45] smspillaz: yeah, that's why it's important you to be there and tells "that one should be upstream or not" [07:45] I was going to caution against that, but then i remembered upstream compiz is one of the few projects that likes us. [07:45] the default patch is quite big already [07:45] spikeb: you're talking to the upstream compiz developer [07:45] spikeb: well, smspillaz is upstream :) [07:45] hi! [07:45] he *seems* to be friendly :) [07:45] :p [07:45] * smspillaz hides dossier with secret agenda [07:46] smspillaz: ahah! [07:46] smspillaz, i know :) [07:46] momentary brainfart. i have them often. [07:46] hehe [07:46] :) [07:46] nah, compiz <3 unity [07:46] in fact lots of people <3 unity [07:47] even if I wasn't working for the big ca then I would still <3 unity anyways [07:47] smspillaz: did you notice the new minimize effect on the launcher icon? [07:47] i'm a huge fan of the concept [07:47] and you guys are doing a great job of implementing it. [07:48] spikeb: heh, nice! :) [07:48] didrocks: how recent is it ? I've not actually (......) had a chance to run unity for a while [07:48] spikeb: :) [07:48] smspillaz: well, 2 days ago [07:48] didrocks: ah ok :) I will have a look then [07:48] * spikeb is running unity-mutter at the moment on his netbook. [07:48] can't wait for a3 or beta so i can upgrade. [07:48] beta will be pretty polished [07:48] smspillaz: when you minimize an icon and the launcher is visible, you have a little effect on the launcher icon blinking justttttt a little [07:48] it's early steps right now [07:49] didrocks: oh you mean how it shimmers ? [07:49] spikeb: you can still try on an usb key as a live system [07:49] i check on it once a week with a daily build [07:49] didrocks, i do. weekly. [07:49] spikeb: right, the schimmer effect on minimize [07:49] spikeb: good good :) [07:50] that is how i know enough to be impressed with the work so far ;) [07:50] smspillaz: ^^ [07:51] didrocks: yeah I've seen that [07:52] hopefully you will like the next few tweaks for compiz [07:52] smspillaz: hehe, I hope so! [07:52] smspillaz: just give me back my ws settings and I will be happy already :) [07:52] hrm my package hasn't arrived yet [07:52] didrocks: :p [07:52] smspillaz: yeah, there need to be a binary NEW [07:52] smspillaz: I can't NEW myself my package [07:53] policy :) [07:53] oh, no no [07:53] I meant something else [07:53] like by mail [07:53] smspillaz: oh a real package :) [07:53] I ordered one of those DS programming kits [07:53] it said next day shipping and they called me yesterday to confirm my details ... [07:53] really? it's compatible with DS 3D as well? [07:53] heh. next day shipping always takes 3 days for me. [07:54] spikeb: it is weird though since the sender is in Perth, and that's where I am [07:54] didrocks: no it isn't :( [07:54] that is pretty weird. [07:54] * didrocks wants to be younger again and have free time to hack during the night and week-end… [07:54] didrocks: it basically allows you to write and load software from a microsd card [07:55] smspillaz: oh, but you have some tools like the API doc and such? [07:55] smspillaz: and an emulator [07:55] yeah [07:55] (I should port compiz to it XD) [07:56] (and unity) [07:56] touchscreen ftw! [07:56] smspillaz: sure, to change ws :) [07:56] hehe [07:56] smspillaz: or something like, you can only unblock gnome-screensaver with a high score of… [07:56] haha [07:56] didrocks: I actually wrote a wiimote plugin for compiz once [07:57] yeah, you told me that :) [07:57] should be fun [07:57] http://www.youtube.com/watch?v=5M7ejHp2NM8 [07:58] * spikeb wonders if he should have explained why when he said "that's a bad idea" on the mailing list. [07:58] smspillaz: I'm sure it can be awesome for accessibility, like with ezoom [07:59] spikeb: that's generally better :) [07:59] i did provide a very terse explanation but perhaps i should think it over and provide a better one heh [07:59] didrocks: it is :) [08:00] didrocks: I still like this one http://www.youtube.com/watch?v=F2ATcBIS3Zc&feature=related [08:01] smspillaz: oh right, I remember this one :) [08:01] smspillaz: TBH, 2 years ago, I forgot the IR bar when taking my wii at ski [08:01] you can just use candles [08:02] smspillaz: we ended up using candies with the wiimote [08:02] yeah :p [08:02] candles* [08:02] yeah, was working perfectly :) [08:02] well, sometime, you make some air and the light is moving [08:02]