[00:07]  * thumper hunts for fud
[02:40] <bschaefer> thumper, hey another update on the bug: https://bugs.launchpad.net/unity/+bug/711199
[02:41] <bschaefer> thumper, mhr3 finished the work in the lenses and I have the code set up for unity. Whats left is the HomeView which is getting reworked atm
[06:12] <[reed]> where does the unity launcher save the things that are stored on it? documentation seems to say ~/.local/share/applications/, but that's not true in my case
[07:58] <Saviq> morning
[09:01] <tsdgeos> Saviq: answered your question about if we need C++ for https://code.launchpad.net/~aacid/unity-2d/unity-2d-shell_no_dbus_to_ourselves/+merge/89247 Basically with the current status of the rest of the code, yes
[09:08] <nerochiaro> Saviq: do you know what's supposed to set the DASH_MIN_SCREEN_WIDTH and DASH_MIN_SCREEN_HEIGHT env variabled that the dash uses in trunk to choose if to go always fullscreen ?
[09:08] <nerochiaro> tsdgeos: dyams: ^
[09:10] <Saviq> guys, I don't have power, trying to cope on 3G, but I might not do well
[09:10] <tsdgeos> nerochiaro: no idea
[09:11] <nerochiaro> greyback: do you know ? ^
[09:12] <greyback> can you repeat? I just joined
[09:12] <nerochiaro> greyback: do you know what's supposed to set the DASH_MIN_SCREEN_WIDTH and DASH_MIN_SCREEN_HEIGHT env variabled that the dash uses in trunk to choose if to go always fullscreen ?
[09:13] <greyback> nerochiaro: no I don't. I didn't even think they were env vars, I thought they were constants
[09:13] <nerochiaro> greyback:     static int minHeight = getenvInt("DASH_MIN_SCREEN_HEIGHT",
[09:13] <nerochiaro>                                      DASH_MIN_SCREEN_HEIGHT);
[09:13] <nerochiaro> greyback: i'll try to look who did the commit then
[09:13] <greyback> nerochiaro: yes just grepped :) No idea
[09:15] <nerochiaro> greyback: wow it's from agateau at the end of february last year. it's the commit that introduces the non-fullscreen dash :)
[09:15] <nerochiaro> let's check what unity3d does...
[09:16] <greyback> nerochiaro: interesting. Might make testing the maximize stuff easier??
[09:16] <nerochiaro> greyback: i was actually thinking if it's possible to remove the conditional on that env var ;)
[09:17] <greyback> nerochiaro: :)
[09:17] <nerochiaro> greyback: i just grepped in unity and they don't seem to read that env anywhere
[09:18] <nerochiaro> smells like dead code to me
[09:18] <greyback> nerochiaro: then I don't really see why we need it.
[09:18] <greyback> nerochiaro: OEM never used it?
[09:18] <nerochiaro> greyback: no idea
[09:19] <greyback> nerochiaro: either way, I doubt removing the code would set them back
[09:20] <nerochiaro> greyback: yeah, i'll zap it
[09:20] <greyback> nerochiaro: great, thanks. Another nice all-red qdiff to look at :)
[09:21] <nerochiaro> greyback: nah, just less stuff i am bringing back from trunk to shell
[09:21] <nerochiaro> but same effect
[09:21] <greyback> ak oh
[09:21] <dyams> nerochiaro: lemme check
[09:24] <dyams> nerochiaro: Didi you check this ?  DASH_MIN_SCREEN_WIDTH = 1280;
[09:24] <dyams>  DASH_MIN_SCREEN_HEIGHT = 1084;
[09:24] <nerochiaro> dyams: where ?
[09:24] <nerochiaro> dyams: oh, seen it
[09:25] <dyams> DashSettings::
[09:25] <dyams> nerochiaro : DashSettings::
[09:26] <nerochiaro> dyams: i still don't see that used anywhere in unity-3d though
[09:27] <dyams> nerochiaro: then how they find out if the screen is wide enough to display dash in desktopMode? Just asking
[09:28] <nerochiaro> njpatel: do you know if the dash in unity has a feature where if the screen resolution is below a certain threshold it will always display fullscreen ?
[09:28] <nerochiaro> dyams: better to ask ;)
[09:28] <dyams> nerochiaro: As I remember class DashSettings itself was an import from 3D though :)
[09:29] <nerochiaro> dyams: it might be that i'm not good enough at grepping, then
[09:29] <njpatel> nerochiaro, yes, it should, I believe it checks height < 800px
[09:30] <nerochiaro> njpatel: any idea where that check is in the code ?
[09:30] <njpatel> nerochiaro, DashController.cpp or DashView.cpp would have that code
[09:30] <nerochiaro> njpatel: looking. thanks
[09:37] <mhr3> kamstrup, btw there's an issue - when i was doing the music-lens branch i noticed that unity doesn't care about position of an item in the model - so whenever you add something to the model unity just appends it to the result list (and it's understandable, the splitting to categories doesn't make this easy), this makes MergeStrategy a bit useless, you can't really sort the results with it
[09:37] <tsdgeos> Saviq: do you think you'll be able to have a look at the MR i put you in with your power issue or you prefer me to bug someone else to have a look at them?
[09:37] <dyams> nerochiaro: :)
[09:37] <kamstrup> mhr3: :-(
[09:38] <kamstrup> mhr3: we can look into it when we've landed the home-lenses branch
[09:38] <kamstrup> mhr3: I had the same issue with categories, but I fixed it in unity
[09:38] <mhr3> kamstrup, right, it's doable, but not exactly trivial
[09:38] <Saviq> tsdgeos, might be better if you bug someone else, I can't be sure I'll make it
[09:39] <kamstrup> mhr3: hehe, wait till you see the home-lens, you'll redefine trivial ;-)
[09:39] <Saviq> 3G doesn't work, either, I'm on EDGE now, and not going to be here long
[09:40] <mhr3> kamstrup, i'm worried already :P
[09:40] <tsdgeos> Saviq: okidoki
[09:42] <tsdgeos> nerochiaro: added you to the 3 MR that were on Saviq in case you have time
[09:43] <Saviq> tsdgeos, I might be able to do the BFB one
[09:43] <Saviq> was already on it before
[09:43] <tsdgeos> cool
[09:43] <nerochiaro> tsdgeos: i'll get one after i'm finished with the tests for this task i'm doing
[09:47] <Saviq> tsdgeos, approved
[09:47] <tsdgeos> Saviq: cheers
[09:48] <Saviq> tsdgeos, do you have an idea about testing the root qml selection?
[09:48] <tsdgeos> actually did not think about that
[09:49] <tsdgeos> should not be that difficult to do, just put a dummy .qml in the testing repo, point it there and then check via testability that the contents of the qml file is there
[09:50] <tsdgeos> i'll give it a go
[09:50] <Saviq> yup, I was thinking similiar
[09:53] <nerochiaro> greyback: is there any special way to set env vars with testability ?
[09:54] <greyback> nerochiaro: set them in the @app.run method
[09:55] <greyback> nerochiaro: like :environment => 'LC_ALL=en SPECIAL_VAR=value'
[09:55] <nerochiaro> greyback: awesome
[10:01] <Saviq> sorry all, I'm going offline, not sure I'm gonna make it for the standup, hope you boys will be good
[10:02] <nerochiaro> Saviq: good luck
[10:02] <greyback> Saviq: ok so
[10:14] <tsdgeos> greyback: there?
[10:14] <greyback> tsdgeos: yep
[10:15] <tsdgeos> greyback: i'm very confused, i am putting a printf inside the "if (arrayContains(argv, argv + argc, "-testability")) {" and it never gets there
[10:16] <greyback> tsdgeos: I know the qt libs look for -testability switch before we do, but I hope they don't remove it from argv
[10:17] <tsdgeos> well that is the "standard" QAppplication behaviour
[10:17] <tsdgeos> they eat the args they know
[10:17] <tsdgeos> that's why the check for style is done in earlySetup
[10:17] <greyback> ah in which case, there's your answer:(
[10:17] <greyback> I see
[10:17] <tsdgeos> instead of on the constructor
[10:17] <tsdgeos> then it means we don't really need that code?
[10:18] <greyback> tsdgeos: where is it? Did I put it there by accident?
[10:18] <tsdgeos> greyback: Unity2dApplication::Unity2dApplication
[10:19] <greyback> tsdgeos: oh feck, I thought I removed that.
[10:19] <greyback> tsdgeos: yes all that is not necessary, as is testabilityinterface.h
[10:19] <tsdgeos> oh
[10:19] <tsdgeos> ok :D
[10:19]  * tsdgeos was getting increasingly confused by that
[10:19] <greyback> qt since 4.6.4 (I think) does all that already
[10:20] <tsdgeos> can we kill it?
[10:20] <greyback> yep
[10:20] <greyback> When I started playing with Testability, I didn't realise it was built into Qt
[10:20] <greyback> docs didn't make it clear
[10:21] <kamstrup> did nux or compiz break abi or something recently?
[10:21]  * kamstrup getting weird segfaults
[10:21] <nerochiaro> dyams: i'm looking at your review on https://code.launchpad.net/~unity-2d-team/unity-2d/unity-2d-shell-dash-panel-buttons. regarding this comment: "2) In future, Dash mode needs to be persistent. It should remember fullscreen/desktop mode across login/logout.
[10:21] <nerochiaro> In your current change is it possible to restore the previous dash mode?" i think that if it's something "for the future" it's better to worry about it later when we actually need to implement that feature
[10:22] <dyams> nerochiaro: no prob, I was just asking
[10:23] <nerochiaro> dyams: ok, i'll leave it out for now. fixing the rest of the comments. thanks for the review btw
[10:26] <dyams> nerochiaro: no prob
[10:26] <tsdgeos> greyback: want me to make the MR to kill it?
[10:27] <kamstrup> mhr3: did you have a branch for u-l-m with the collated categories in global?
[10:28] <kamstrup> mhr3: if so, can you attach it to https://bugs.launchpad.net/unity/+bug/885738 please?
[10:28] <mhr3> kamstrup, k
[10:28] <greyback> tsdgeos: yeah please do
[10:33] <kamstrup> mhr3: works well, one thing though - the music lens should not show anything when we don't have a search in global
[10:33] <mhr3> oh, it shouldn't?
[10:34] <mhr3> easy fix
[10:34] <nerochiaro> dyams: updated the MR to match your review: https://code.launchpad.net/~unity-2d-team/unity-2d/unity-2d-shell-dash-panel-buttons/+merge/89436
[10:35] <davidcalle> kamstrup, does all these music lens tweaks impact the way the rbox scope should behave?
[10:35] <dyams> nerochiaro: thx, i'll check
[10:35] <kamstrup> davidcalle: yes
[10:36] <kamstrup> davidcalle: when I mp the homelens branch I'll attach some screenies for design review. When we have that up we can talk it through?
[10:38] <mhr3> kamstrup, pushed
[10:39] <mhr3> davidcalle, are you doing the rb scope as a separate remote scope?
[10:39] <davidcalle> kamstrup, no problem. I'm on the data fetching part, the global search part can wait. Are there changes for the lens view? Still tracks/albums ?
[10:39] <mhr3> in python?
[10:39] <kamstrup> davidcalle: afaik the lens view is the same
[10:40] <davidcalle> mhr3, yes for both. Do you hate me?
[10:40] <davidcalle> :)
[10:40] <mhr3> davidcalle, as a default scope, i think we'll want a native one
[10:43] <davidcalle> mhr3, won't this be an issue for people upgrading from Oneiric? A default scope recommending rhythmbox will install it. I don't think that's ideal.
[10:44] <mhr3> davidcalle, it doesn't need to recommend anything, it can be a local scope in the lens that will fail gracefully if rb isn't installed
[10:44] <mhr3> that's the case with the banshee scope afaik
[10:47] <davidcalle> mhr3, ok. There is still an issue, afaik I'm the only person working on the Rhythmbox scope and Vala is still an issue for me. I can give it a try, but it won't be nice before feature freeze.
[10:49] <mhr3> davidcalle, no worries i can help
[10:49] <mhr3> although you'll find out that processing strings and xml is so much nicer in python :/
[10:50] <davidcalle> Well, internal vala scope it is, then.
[11:14] <dyams> nerochiaro: currently the dashmode is already saved in dconf.
[11:15] <tsdgeos> greyback: we don't have unity-2d "staging" builds for oneiric anymore?
[11:15] <dyams> nerochiaro: the same parameter("com.canonical.Unity.farmFactor) used by unity3D is used in 2D too
[11:18] <greyback> tsdgeos: hmmm, looks like that got turned off.
[11:18] <greyback> tsdgeos: asking about it
[11:18] <tsdgeos> nice
[11:19] <nerochiaro> dyams: yes, but it's the form factor, it's not the dash mode
[11:19] <nerochiaro> dyams: they are two differnt things, no ?
[11:20] <nerochiaro> dyams: form factor is for saying desktop, tv, phone, tablet, and so on
[11:20] <nerochiaro> dyams: while dash mode is only for saying if dash should be fullscreen or not fullscreen
[11:21] <dyams> nerochiaro: dash.qml is using the farmfactor to set fullscreen/desktop
[11:22] <dyams> nerochiaro: you may be right that its for saying desktop, tv, phone, tablet...and so on.
[11:22] <nerochiaro> dyams: that is because only in desktop mode the dash can be non-fullscreen
[11:22] <dyams> nerochiaro: May be they misused it?
[11:22] <nerochiaro> dyams: no, it's right to have it there. but let me check again
[11:23] <greyback> tsdgeos: staging PPA is precise only now. unity-2d is building right now
[11:23] <tsdgeos> greyback: ok, sad for us still on oneiric
[11:24] <greyback> tsdgeos: I know. See dx channel for why
[11:25] <dyams> nerochiaro: currently, toggling the dash mode is also chaning the farmFactor in gconf.
[11:26] <nerochiaro> dyams: is it ? where is the write happening?
[11:27] <dyams> DashSettings itself
[11:27] <dyams> nerochiaro: It is in DashSettings::setFormFactor
[11:27] <nerochiaro> dyams: yes, but does anyone actually call that function ?
[11:28] <dyams> nerochiaro: currently? yes
[11:28] <nerochiaro> dyams: where ?
[11:28] <dyams> nerochiaro: from WindowHelper.cpp I believe, lemme check..one sec
[11:29] <nerochiaro> dyams: i think windowhelper just change isFullScreen
[11:29] <dyams> nerochiaro: Yes,  WindowHelper::unmaximize()
[11:30] <dyams> nerochiaro: Currently == from unity-2d/trunk
[11:30] <nerochiaro> dyams: ah, ok, i already removed that
[11:30] <nerochiaro> dyams: and i think we need to remove DashClient::formFactor completely
[11:30] <dyams> nerochiaro: You mean, DashSettings::formFactor?
[11:31] <nerochiaro> dyams: yes. because it doesn't make sense in DashClient. if someone wants to read the unity form factor it needs to read it from unityConfiguration
[11:31] <nerochiaro> but it's not the dash form factor. it's the form factor for the entire unity
[11:31] <dyams> nerochiaro: agreed
[11:31] <nerochiaro> dyams: i'm gonna change it as part of that branch you are reviewing then
[11:32] <dyams> nerochiaro: Don't we need a explicit parameter for DashMode?
[11:32] <dyams> nerochiaro: in Dconf i mean
[11:32] <nerochiaro> dyams: we need it later, when we want it to be permanent across sessions, i guess
[11:32] <dyams> nerochiaro: ok. I'll wait
[11:33] <[reed]> where does the unity launcher save the things that are stored on it? documentation seems to say ~/.local/share/applications/, but that's not true in my case
[11:33] <nerochiaro> dyams: and when it needs to be added, please let's set it from the dash itself, not in dashclient
[11:34] <nerochiaro> [reed]: in dconf i think
[11:34] <[reed]> nerochiaro: ok, thanks
[11:34] <dyams> nerochiaro: Ok, sure
[11:35] <nerochiaro> [reed]: /desktop/unity/launcher/favorites
[11:35] <[reed]> thx
[11:35] <dyams> nerochiaro: lemme check if 3D is also doing same thing... using the dconf->'formFactor' for desktop/fullscreen mode
[11:35] <nerochiaro> dyams: unity-3d doesn't have all the form factors that 2d has, IIRC
[11:36] <dyams> nerochiaro: ok.. if they are using that setting then we need to be consistent, no?
[11:37] <nerochiaro> dyams: if there's a specific formFactor for the dash that means only fullscreen or non-fullscreen then yes, otherwise it seems like a bug to me
[11:38] <nerochiaro> dyams: because what we call formFactor is global to the entire unity-2d
[11:38] <dyams> nerochiaro: agreed
[11:53] <dyams> nerochiaro: In 3D they are using it(gconf->formFactor) as a setting to store fullscreen/desktop mode
[11:54] <nerochiaro> dyams: gconf or dconf ?
[11:54] <dyams> nerochiaro: d :)
[11:54] <nerochiaro> dyams: :) and what's the full path of the key ?
[11:55] <dyams> nerochiaro: They are chaning it everytime toggle maximize is called. check here : PanelMenuView::OnRestoreClicked()
[11:55] <dyams> nerochiaro: one sec
[11:55] <dyams> nerochiaro: com.canonical.unity.formFactor. no?
[11:56] <nerochiaro> dyams: i don't know, but if it's that key, then it's definitely wrong to use it the way they are using it
[11:56] <nerochiaro> because that's the global unity form factor, not hte dash form factor
[11:57] <nerochiaro> dyams: and we're doing something wrong too, because we're reading the global form factor from com.canonical.unity-2d
[11:58] <dyams> nerochiaro: Changing that setting to something else might is technically correct, but that might confuse the current users
[11:59] <dyams> nerochiaro: It was for consistency purpose I believe.
[11:59] <nerochiaro> dyams: the real issue is: do we want to share that setting with unity3d ? if we don't it's fine as it is, if we do then we should come to an agreement, or just use the wrongly named setting from com.canonical.unity with comments to explain what it should be in reality
[11:59] <dyams> nerochiaro: but sure, that could lead to confusion too
[11:59] <nerochiaro> Kaleo: any input on the above ,please ? ^
[12:01] <Kaleo> nerochiaro: let me read
[12:02] <Kaleo> nerochiaro: 2d's semantic of the key is correct I believe
[12:03] <nerochiaro> Kaleo: so we're fine with that we have and we don't want to share this setting with 3d (to have fullscreen persist between sessions)
[12:04] <Kaleo> nerochiaro: yes, it's a tradeoff
[12:04] <nerochiaro> awesome
[12:04] <nerochiaro> thanks for the input
[12:04] <Kaleo> nerochiaro: we should have a good name for that feature (dashFullScreen or something)
[12:04] <kamstrup> mhr3: there was a conflict on https://code.launchpad.net/~mhr3/unity-lens-music/home-lenses/+merge/89667... not sure where that came from. I also added a small nitpick
[12:05] <nerochiaro> Kaleo: it's already called isFullScreen over DBUS, so i guess we'll use dashFullSCreen or dashIsFullScreen in dconf
[12:08] <Kaleo> nerochiaro: makes sense to me
[12:09] <dyams> nerochiaro: kaleo: a boolean?
[12:09] <nerochiaro> dyams: yes
[12:09] <nerochiaro> it's either fullscreen or not ;)
[12:11] <dyams> nerochiaro:  no need to worry what is Netbook or Desktop mode either. Easy and Simple :)
[12:13] <nerochiaro> dyams: yep
[12:13] <nerochiaro> :)
[12:48] <kamstrup> mhr3: I still get the g_variant_unref: assertion `value->ref_count > 0' error on libunity trunk when using dee trunk... I thought we fixed that with the tweak to the DeeSerializable?
[12:48] <mhr3> kamstrup, yep, it should work
[12:49] <mhr3> kamstrup, fwiw it's ok here
[12:49] <kamstrup> I think my system is hosed
[12:49] <kamstrup> unity is also crashing with no end
[12:50] <kamstrup> mhr3: argh! the i18n snuck in... :-/ *grumble*
[12:50] <kamstrup> I tried SO hard to not get it in
[13:02]  * Saviq is back
[13:08]  * greyback rejoices
[13:09] <davidcalle> mhr3, rbox xml parsed and tracks thumbs too with gio... So, the amount of help needed should be minimal.
[13:10] <om26er> greyback, hey bug 917458 , thoughts?
[13:10] <mhr3> davidcalle, oh wow, awesome!
[13:10] <greyback> om26er: looking...
[13:13] <greyback> om26er: could have accidentally put one Firefox on one workspace, and Terminator on the other. It would explain the behaviour.
[13:13] <greyback> om26er: I'll comment on it now
[13:13] <om26er> greyback, ah, thanks :)
[13:42] <kamstrup> greyback: I guess https://bugs.launchpad.net/unity-lens-music/+bug/841902 implies some work on unity-2d as well?
[13:43] <Saviq> kamstrup, ours does that already
[13:43] <kamstrup> there was a new filter type added "filter-checkoption-compact" that assumes unity will render 3 columns
[13:43] <kamstrup> Saviq: you guys are just to hawt ;-)
[13:43] <Saviq> oh ok, so ours hacks that up
[13:44] <Saviq> i.e. "if lens == 'music': 3 columns"
[13:44] <greyback> Saviq: yep it's a hack, tiagosh has done a little work getting ready to support it
[13:44] <kamstrup> ah, I don't expect many customers for the "filter-checkoption-compact" filter type though, so not big prio
[13:44] <Saviq> still, shouldn't be a big issue
[13:44]  * kamstrup adds a u2d task then
[13:44] <kamstrup> great
[13:45] <greyback> kamstrup: yep, it's in progress already I believe
[13:48] <dyams> kamstrup: filter-checkoption-compact is not in staging either..still waiting...lemme check again now
[13:49] <kamstrup> it's been in libunity and unity-lens-music trunks for a few days I believe
[13:49] <greyback> dyams: if you're on Oneiric, you may not be seeing any updates from the staging PPA. It's Precise only now
[13:50] <kamstrup> since Wednesday
[13:50] <dyams> greyback: sure, am on precise
[13:52] <dyams> kamstrup: there are 4-5 branches which one is final revision
[13:53] <greyback> dyams: good. last libunity build on staging was 2 minutes ago, so that filter-compact hint should be there now
[13:53] <dyams> greyback : lemme refresh
[13:54] <greyback> dyams: now don't ping me for 2 minutes, it's mucking up my tests :)
[14:03] <dyams> kamstrup: greyback: yay! filter-checkoption-compact is coming to unity2d-shell
[14:03] <dyams> saviq: ^^
[14:03] <Saviq> cool
[14:03] <dyams> saviq: greyback: lemme do it for unity2d-shell.
[14:05] <greyback> dyams: it was you I gave to do it, not tiagosh. My bad. Yes please do
[14:06] <dyams> greyback: no prob
[14:07] <kamstrup> woot
[14:18] <dyams> kamstrup: all renders will have two columns except "filter-checkoption-compact", no?
[14:18] <dyams> kamstrup: only "filter-checkoption-compact" have 3 columns
[14:19] <kamstrup> dyams: in short, yes
[14:20] <kamstrup> dyams: the reason we choose the "compact" moniker was to leave that a bit up to the unities rendering this. The lens can say "Like normal filters, but I have more options".
[14:20] <kamstrup> it just so happens that our Unity2/3d implementations use a 3 column layout for this :-)
[14:21] <dyams> kamstrup: Ok, thank you for the description
[14:21] <dyams> kamstrup: :)
[14:26] <mhr3> kamstrup, there's something odd with your branch - hiding the dash using super seems to reset the search string for the lenses, but it stays in the entry
[14:26] <mhall119> JohnLea: ping
[14:26] <tsdgeos> greyback: you were planning having tests for modes != intellihide, right? how far is that?
[14:27] <mhr3> kamstrup, ie "gedit" -> see gedit in results -> hide with super -> summon again -> see "gedit" in the entry, but lenses show results for ""
[14:27] <greyback> tsdgeos: not got ot it yet, sorry
[14:27] <greyback> *to
[14:27] <kamstrup> mhr3: let me check
[14:28] <tsdgeos> greyback: oh, i'm working on something "show-all-the-time" mode only, what's your suggestion for the test? change it forth and back manually?
[14:30] <kamstrup> mhr3: hold on, I need to fix my system. Got hit by a double whammy with nux abi break and libglew1.5->1.6 abi break as well... b000000orked
[14:32] <mhall119> thumper: ping
[14:34] <greyback> tsdgeos: launcher in the fixed state? (you're doing the strut stuff). Manual is only thing I can suggest just now.
[14:34] <tsdgeos> greyback: yes, the strut stuff
[14:34] <tsdgeos> greyback: ok, i'll go manual then
[14:37] <kamstrup> mhr3: I get it now... trunk also has this in reverse I think. It clears the text entry but not the lenses. You just don't see it because it's hidden
[14:37] <kamstrup> (behind the home screen tiles)
[14:38] <mhr3> kamstrup, no trunk doesn't clear the search string
[14:38] <mhr3> that's the statefulness design wanted, no?
[14:38] <kamstrup> mhr3: odd... it does here
[14:39] <mhr3> kamstrup, are you hiding using super or esc?
[14:39] <kamstrup> mhr3: I know, looking at the code it looks like it doesn't, but in reality it does; somewhere
[14:39] <kamstrup> mhr3: super
[14:39] <kamstrup> please don't say those are different
[14:39] <mhr3> afaik, yes :P
[14:39] <kamstrup> ah, so Esc is "back"
[14:39] <kamstrup> makes sense
[14:40] <kamstrup> mhr3: what do you see if you hit <super>, type "ged", <super>, and then <super> to re-show dash?
[14:41] <kamstrup> I get a cleared home screen with the tiles
[14:41] <mhr3> kamstrup, trunk or your branch?
[14:41] <kamstrup> trunk
[14:41] <mhr3> a sec
[14:42] <mhr3> i suppose "a crash" doesn't count? :)
[14:42] <kamstrup> mhr3: oh, I can add that in my branch as well if we need to mimic trunk?
[14:42] <kamstrup> ;-)
[14:43] <kamstrup> mhr3: you might be hit by the abi changes as well
[14:43] <mhr3> it's the music lens and compact filter
[14:43] <kamstrup> ah yeah
[14:43] <kamstrup> unity thinks it better crash if it doesn't know a filter
[14:43] <mhr3> ok, so i get the search cleared
[14:43] <kamstrup> saw that
[14:44] <mhr3> and i see the huge icons again
[14:44] <kamstrup> right
[14:44] <kamstrup> then it's the same as me
[14:44] <mhr3> nevermind then, i assumed it'd behave like lens views now
[14:44] <kamstrup> how about I just clear the entry in my branch then, and we should be equiv. to trunk
[14:44] <mhr3> better check with john what's desired now?
[14:44] <mhr3> JohnLea, ping
[14:44] <kamstrup> then we can chat to John about what we should *actually* be doing ;-)
[14:45] <mhr3> seems like he doesn't have time
[14:45] <kamstrup> you killed him!
[14:45] <kamstrup> better now JohnLea? ;-)
[14:45] <mhr3> someone resurrected him
[14:46] <JohnLea> kamstrup; hyia, out of meeting now
[14:46] <kamstrup> JohnLea: I am just discussing with mhr3 what state we carry around in the dash
[14:46] <kamstrup> JohnLea: currently trunk clears the text entry when you hide the dash
[14:47] <mhr3> which makes sense since we want to show the huge icons
[14:47] <kamstrup> (and places you back on the home screen next time dash comes up)
[14:47] <kamstrup> right
[14:47] <kamstrup> My gut instinct says we should still reset
[14:47] <JohnLea> kamstrup; the state of almost everything should be retained.  text entered into search field, filters, filters open or closed, category headers expanded or collapsed, etc...
[14:47] <kamstrup> the new home screen contains lots of useful stuff
[14:48] <kamstrup> k
[14:48] <JohnLea> one sec, let me dig out a bug...
[14:48] <JohnLea> found it.  have a look at https://bugs.launchpad.net/ayatana-design/+bug/914759
[14:49] <JohnLea> this fixes the inconsistency we have had with Dash Home and Lens behaviour
[14:49] <JohnLea> kamstrup, mhr3: ^
[14:49] <kamstrup> ah
[14:49] <mhr3> ok, i think that clears the it, thx JohnLea
[14:50] <kamstrup> yep
[14:50] <JohnLea> kamstrup, mhr3; thx!
[14:50] <kamstrup> mhr3: if I can easily implement it then I'll do so. Otherwise I'll just clear the entry for now and then we can add it as a later task to implement the statefulness
[14:50] <mhall119> JohnLea: I'd like to talk to you about coming up with some kind of guideline for the creation of new lenses
[14:51] <mhr3> kamstrup, ok
[14:51] <JohnLea> mhall119; e.g. what a Lens should and shouldn't do?
[14:51] <mhall119> JohnLea: yeah, since we're starting to see people make per-source lenses, not per-content-type lenses
[14:52] <mhall119> I'd like to have a wiki page or something to point them to that gives "official" recommendations about when you should and should not make a new lense
[14:52] <JohnLea> mhall119; yes, that would be very useful.  Did you see my post on the ayatana mailing list about part of this subject a little while ago?
[14:52] <mhall119> nope (not sure i'm on that ML, let me check)
[14:53] <mhall119> is it an LP list, or lists.u.c?
[14:53] <JohnLea> mhall119; that would be a really good, ping me when you have a first draft ready.  One sec, I'll dig out the post
[14:54] <mhall119> I like how you turned that back around into work for me :)
[14:54] <kamstrup> mhr3: hrm... I've started getting segfaults from unity in my branch http://paste.ubuntu.com/814339/ . The odd thing is that I don't get it when using the standalone dash...
[14:55] <mhr3> kamstrup, fun, works here though :)
[14:56] <kamstrup> mhr3: yeah, my gut instinct says it's somehow because I broke libunity-core abi...
[14:56]  * kamstrup will never break any abis again
[14:56] <mhr3> i was just going to say that
[14:56] <kamstrup> EVER!
[14:56] <kamstrup> (today. at least)
[14:57] <mhr3> kamstrup, it's almost like you didn't use jhbuild or something :P
[14:57] <kamstrup> mhr3: I use nothing else :-)
[14:57] <davidcalle> mhall119, would you mind if we draft it together in a Google doc?
[14:58] <kamstrup> mhr3: btw, I looked at the lens-icon-shifting-issue you pointed out. It's present in trunk as well. So not my bad! :-)
[14:58] <mhall119> davidcalle: 50% less work for me, definitely
[14:58] <mhall119> JohnLea: what was the title of your email onthe ML?
[14:58] <mhr3> kamstrup, no it's not, sorry there's really something wrong with your unity :P
[14:59] <kamstrup> JohnLea, mhall119, mhr3, davidcalle: the per source lenses thing is probably a relic of the old libunity API where the concept of "sources" wasn't really wired up. mhr3 fixed this in trunk where it should work great
[14:59] <kamstrup> mhr3: fuuuuu!
[15:00] <mhall119> kamstrup: what do you mean?
[15:00] <JohnLea> mhall119; just pinged it to you in irc, let me know when you have a first draft available.  This is a piece of documentation that we are really missing, thanks for spotting it and offering to help
[15:01] <mhall119> JohnLea: thanks
[15:01] <mhr3> mhall119, we now have api that the scopes can use to show in the lens a "Source" that can be enabled/disabled
[15:01] <kamstrup> mhall119: I was talking in relation to the lenses-per-source vs lenses-per-content-type you mentioned
[15:02] <mhall119> ok, I understand now, thanks
[15:02] <kamstrup> mhr3: I am *quite* sure that it is in trunk. Have you tried an up-to-date lp:unity and then running standalone-clients/dash (compile it with 'make dash')
[15:03] <mhr3> kamstrup, i'm running trunk unity right now, there's no offset issue
[15:03] <mhr3> oh wait
[15:03] <mhr3> no i'm not
[15:04] <mhr3> it's the one from precise
[15:04] <kamstrup> aha!
[15:04] <mhr3> kamstrup, ok you win
[15:06] <mhall119> davidcalle: JohnLea: invite to google doc sent
[15:07] <davidcalle> mhall119, thanks.
[15:10] <mhall119> JohnLea: do we have any document about when to create vs. reuse an indicator?  I think there might be some overlap in intention between indicators and lenses
[15:20] <tsdgeos> nerochiaro: what does "Put back in support for 4-finger slide gesture (in a way that's not tied to the panel)" mean in the MergePlan wiki?
[15:21] <nerochiaro> tsdgeos: let me point you at the relevant code. hold on
[15:22] <nerochiaro> tsdgeos: in short, on touch-enabled devices when you slide on the screen with 4 fingers you should "drag out" the launcher, which will then stay out if you slide past a certain "distance
[15:22] <tsdgeos> hmmm
[15:22] <tsdgeos> seems difficult to test :D
[15:22]  * tsdgeos looks for something else to do
[15:23] <nerochiaro> tsdgeos: :) that's the problem everyone will have with it :)
[15:23] <nerochiaro> i think it's something only Kaleo himself can do, i don't know anyone else with touch devices
[15:24] <Kaleo> nerochiaro: I can indeed
[15:24] <Kaleo> nerochiaro: anybody with a macbook can
[15:24]  * tsdgeos looks around
[15:24] <tsdgeos> no macbook
[15:25] <nerochiaro> Kaleo: none here
[15:25] <Kaleo> :)
[15:25] <Kaleo> nobody in the team has anything but me? :)
[15:25] <nerochiaro> tough beans
[15:25] <tsdgeos> Kaleo: i've a red tshirt!
[15:26] <tsdgeos> nerochiaro: you doing "When screen/desktop is resized adjust shell size accordingly and update input mask" ?
[15:26] <nerochiaro> Kaleo: serves you right for buying shiny white hardware
[15:26]  * greyback is playing it quiet :)
[15:26] <nerochiaro> tsdgeos: that one is easy. try killing the panel when the shell is up
[15:26] <nerochiaro> tsdgeos: fix the wrongness you see
[15:26] <tsdgeos> ok, though you were doing it somehow
[15:27] <nerochiaro> tsdgeos: i was "in the area", but didn't get to fix that specific one
[15:27] <nerochiaro> tsdgeos: feel free to take it
[15:27] <nerochiaro> tsdgeos: should be really simple
[15:27] <tsdgeos> nerochiaro: ok
[15:30] <tsdgeos> nerochiaro: with "shell up" you mean "visible" or simply "running" ?
[15:30] <nerochiaro> tsdgeos: visible to notice the issue, but the fix should be the same regardless
[15:31] <Kaleo> greyback: you have it
[15:31] <Kaleo> greyback: good luck :)
[15:33] <Kaleo> nerochiaro, greyback: ok, I take on the task of making the gestures work
[15:33] <nerochiaro> Kaleo: thanks
[16:18] <nerochiaro> Kaleo: greyback: tsdgeos: Saviq: does anyone know how to connect to QConf signals from c++ ?
[16:19] <tsdgeos> nope
[16:24] <nerochiaro> mardy: ^
[16:26] <greyback> sorry, no idea
[17:31] <mgedmin> very annoying unity bug: press <Super> + g, which is my custom keymap for launching a terminal -- terminal appears, but dash also shows up
[19:22] <mhall119> JohnLea: we're going to need some official recommendations from the dx team about when a new lens should be created and when an existing one should be reused
[19:22] <mhall119> this will also be used by the ARB when evaluating new packages to be included in the software center
[19:23] <mhall119> can you or someone else on the team provide that either as text or an outline we can use to write the text
[19:25] <davidcalle> mhall119, let's say there is a Canonical private project for a specific lens and during the dev, someone submits a lens for the same data type. How would you handle it?
[19:27] <mhall119> davidcalle: I guess it would be case-specific, but I'd want the canonical-private developers to see if they could use the contriuted lens, and if not can they send a patch for whatever changes they'll need to it before it gets approved
[19:28] <mhall119> davidcalle: but the policy I'm looking for is more along the lines of "Don't make a Netflix lens, make a Netflix scope for a generic Video lens"
[19:34] <davidcalle> mhall119, I completely agree, nevertheless I think it would be hard to convince a dev not to produce a Netflix lens, with a very specific set of filters and features dedicated to the source, instead of a scope that will be forced to use non Netflix oriented filters/categories.
[19:35] <mhall119> davidcalle: I agree, but I still think we should minimize the number of unnecessary source-specific lenses
[19:35] <mhall119> otherwise we lose the benefit of having lenses
[19:36] <jono> balloons, invite sent
[19:48] <thumper> morning
[19:53] <mhall119> thumper: morning, I need to talk to you for a bit if you'll have time in about an hour
[19:55] <thumper> mhall119: I'll see if I can make some time :)
[19:56] <mhall119> thumper: thanks
[20:30] <thumper> mhall119: do you skype?
[20:40] <mhall119> thumper: I do, yes
[20:40] <mhall119> give me another 30 minutes or so to finish up another meeting
[20:41] <thumper> I'm on a call too :)
[21:03] <thumper> hi bschaefer
[21:03] <bschaefer> thumper, it was more concerning my contract
[21:04] <bschaefer> thumper, not as much unity stuff right now
[21:04] <thumper> ok, it is the top of my todo list after calls :)
[21:05] <bschaefer> thumper, alright no worries, just wanted to check. Was going to campus to bug my professor later.
[21:05] <bschaefer> thumper, have fun on your calls :). Ill be around if you have any questions about the contract
[21:32] <thumper> mhall119: skype id?
[21:39] <mhall119> <--
[21:41] <mhall119> thumper: I'm ready when you are
[21:53] <mhall119> thumper: http://reports.qa.ubuntu.com/reports/unity-stats/#mp_stats
[22:30] <mhall119> davidcalle: hey, I was wondering if you've started a blog for ohscopes yet
[23:04] <davidcalle> mhall119, it's ready, I just need to write stuff on it.
[23:08] <htorque> hi all! is indicator-loader3 supposed to work with the appmenu right now? when i try to start it (running metacity), i get this: http://paste.ubuntu.com/814857/ and an empty loader window.
[23:08] <davidcalle> mhall119, I have some material for it actually. But it's pretty low on my priority list to be honest, I have not even sent my UDS sponsoring request yet.
[23:11] <mhall119> davidcalle: I don't think it's open for applications yet
[23:13] <davidcalle> mhall119, oh, you are right.