[07:10] <tsdgeos> Saviq: big question, with utopic open, shall we move?
[07:11] <Saviq> tsdgeos, you can stick until it works for you, but that's not gonna be long ;)
[07:11] <tsdgeos> so let's do the move
[07:11] <tsdgeos> the earlier the easier
[07:11] <tsdgeos> since packages should be the same-ish as of now (i'm hoping)
[07:12] <Saviq> tsdgeos, yeah, I don't think anything entered U for real yet
[07:12] <Saviq> OTOH I'm not sure it's possible to switch yet
[07:12] <Saviq> at least do-release-upgrade -d doesn't think so
[07:12] <RAOF> Yeah, that won't work for a bit.
[07:13] <RAOF> sed -i s/trusty/utopic/g /etc/apt/sources.list will¹ work, though :)
[07:14] <RAOF> ¹: For values of “work” that are provided by the current utopic repositories; I'd probably wait a week for the early churn to die down :)
[07:14] <tsdgeos> Saviq: never used those fancy tools
[07:14] <Saviq> :)
[07:15] <Saviq> seems only PPAs are not there yet, cool
[07:17] <tsdgeos> half of ddebs isn't either
[07:18] <tsdgeos> but main is
[07:18] <tsdgeos> so that's cool
[07:21] <Saviq> right, ddebs will probably only happen once something is built in the respective repos
[07:21] <Cimi> I'll wait
[07:21] <Cimi> :)
[07:22] <Cimi> MacSlow, hey mirco, do you have some instructions for which branches I need for power on animation?
[07:22] <Saviq> Cimi, silo 002
[07:24] <Cimi> Saviq, which branches has in? I'm working on power off
[07:24] <Saviq> Cimi, https://docs.google.com/a/canonical.com/spreadsheet/ccc?key=0AuDk72Lpx8U5dFlCc1VzeVZzWmdBZS11WERjdVc3dmc&usp=drive_web#gid=20
[07:26] <MacSlow> Cimi, you mean the animaiotn
[07:26] <MacSlow> Cimi, spinner-animation
[07:26] <Cimi> yeah
[07:26] <Cimi> actually, more all the rest
[07:28] <MacSlow> Cimi, there's lp:~unity-team/unity-system-compositor/new-gl-screen
[07:28] <MacSlow> Cimi, and if your only after the related .debs themselves... like Saviq said silo 002
[08:02] <tsdgeos> Cimi: you were reviewing https://code.launchpad.net/~aacid/unity8/filtergrid_bindingloop/+merge/216147 ? how's it going?
[08:03] <Cimi> tsdgeos, yeah let me review it now
[08:03] <Cimi> I mean finish
[08:03] <Cimi> tsdgeos, I tested it and works fine
[08:03] <Cimi> tsdgeos, I was reviewing the code but got drag into another review
[08:04] <tsdgeos> happens :)
[08:05] <tsdgeos> Cimi: added comment to https://code.launchpad.net/~cimi/unity8/fix-locale-tests/+merge/216068
[08:06] <Cimi> tsdgeos, it might happen that we still need LC_ALL=C
[08:06] <Cimi> tsdgeos, i did not manage to add it for the qmltests
[08:07] <Cimi> the unit tests I think
[08:07] <tsdgeos> Cimi: but we don't (at the moment)
[08:07] <tsdgeos> what's the problem with qmltests?
[08:08] <tsdgeos> aren't we using the same functions?
[08:08] <Cimi> tsdgeos, cmake
[08:08] <Cimi> I failed at setting itr
[08:08] <Cimi> *it
[08:24] <tsdgeos> Cimi: so you're basically saying that the
[08:24] <tsdgeos> set(qmltest_DEFAULT_PROPERTIES ENVIRONMENT "LC_ALL=C")
[08:24] <tsdgeos> you added doesn't do anything?
[08:25] <Cimi> tsdgeos, this works
[08:26] <Cimi> tsdgeos, but if you see the one before in that cmakelists
[08:26] <Cimi> tsdgeos, there's already QPA_PLATFORM=minimum or something
[08:26] <Cimi> tsdgeos, I was not able to set two properties at the same time
[08:26] <Cimi> might be something to do with the macro
[08:27] <tsdgeos> so you mean that there's two tests that don't have the LC_ALL because they have the QPA?
[08:31] <tsdgeos> Saviq: i've removed mysel from the category index thing from https://blueprints.launchpad.net/ubuntu/+spec/client-1303-unity-ui-dash since i don't even know if that's on the table anymore with the last design
[08:31] <Saviq> tsdgeos, sure, of course
[08:31] <tsdgeos> and probably needs to be moved to somewhere not named 1303 too :D
[08:32] <tsdgeos> Cimi: so you mean that there's two tests that don't have the LC_ALL because they have the QPA?
[08:32] <Cimi> yes
[08:39] <tsdgeos> Cimi: then it's two tests, please remove the comment and if ever we need the LC_ALL let's find out how to fix it
[08:39] <Cimi> ok
[08:40] <Cimi> tsdgeos, done
[08:44] <tsdgeos> Cimi: why the two changes in plugins/Utils/CMakeLists.txt ?
[08:45] <tsdgeos> should just one of them be enough?
[08:45] <Cimi> tsdgeos, one is for make test
[08:45] <Cimi> tsdgeos, one for make testTimeFormatter etc
[08:45] <tsdgeos> ah
[08:45] <tsdgeos> right
[08:47] <tsdgeos> Saviq: i'm approving https://code.launchpad.net/~cimi/unity8/fix-locale-tests/+merge/216068 since afaics it contains all your wanted fixes
[08:47] <Saviq> tsdgeos, sure
[08:50] <Cimi> tsdgeos, I'm struggling to understand comment of object d in https://code.launchpad.net/~aacid/unity8/filtergrid_bindingloop/+merge/216147
[08:50] <Cimi> rephrase pls :)
[08:51] <tsdgeos> not sure i can :D
[08:51] <tsdgeos> Cimi: let me try to explain it to you here and then maybe you can suggest what would make it easier to understand for you
[08:51] <tsdgeos> Cimi: so this is the opening/closing grid from the dash
[08:52] <tsdgeos> we have two properties filter,  that controls if the model should be limited to 6 items or not limited at all
[08:53] <tsdgeos> and collapsed that triggers the height animation
[08:53] <tsdgeos> we need two because when going from "big to small" we need to trigger the height animation
[08:53] <tsdgeos> but still we need to be shoing all the items and not 6, because otherwise you'd see the items be removed first and then the height animation happen
[08:54] <tsdgeos> does that explain it better?
[08:54] <Cimi> yes
[08:54] <tsdgeos> ok, so what changes would you suggest to the wording in there?
[08:55] <tsdgeos> i mean it's easy for me to understand since i know what i want to mean :D
[08:55] <tsdgeos> so an outsider suggestion is more than welcome
[08:56] <Cimi> tsdgeos, I don't like those properties
[08:57] <Cimi> tsdgeos, now that you told me how they work
[08:57] <tsdgeos> Cimi: you're free to rework the code to not need them :)
[08:57] <tsdgeos> fwiw we already had them before
[08:57] <Cimi> tsdgeos, I feel like we don't need them but just animate when we are uncollapsing, no?
[08:57] <tsdgeos> just not documented
[08:57] <Cimi> but I am still reading the code first, so I might ended up with your exact code
[08:58] <tsdgeos> Cimi: what do you mean "just animate when we are uncollapsing"?
[08:58] <tsdgeos> we nee the animation in both ways
[08:58] <Cimi> I mean filter just on uncollapsing
[08:58] <Cimi> sorry when is collapsed
[08:58] <Cimi> otherwise is automatically false
[08:59] <tsdgeos> and this is what it does really
[09:00]  * Cimi reads first
[09:13] <tsdgeos> Saviq: so what we do with https://bugs.launchpad.net/unity8/+bug/1308477 ? can we merge https://code.launchpad.net/~mterry/unity8/greeter-ux-fixes/+merge/210042 or you want a definitive answer from Jouni
[09:13] <tsdgeos> ?
[09:14] <Saviq> tsdgeos, we can't land yet anyway, will try and get an answer today
[09:14] <tsdgeos> ok
[09:16] <Saviq> FWIW I really hope this will go away, it's rather annoying to have the launcher pop out every time you unlock the screen...
[09:16] <tsdgeos> i agree
[09:16] <tsdgeos> i told him on the review too
[09:16] <tsdgeos> but i'm not design so if design wants to see it
[09:16] <tsdgeos> well i guess they will want to unsee it afterwards :D
[09:17] <Saviq> indeed ;)
[09:18] <Saviq> /food
[09:45] <tsdgeos> mhr3: do you happen to know if anyone is using ZoomableImage in previews?
[09:47] <mhr3> tsdgeos, according to spec, any non-gallery widget is a zoomable image
[09:48] <tsdgeos> mhr3: correct, do you know of anyone not using galleries?
[09:48] <mhr3> tsdgeos, yea, pretty much every single image will be using it
[09:49] <tsdgeos> ok, tx
[09:49] <mhr3> so music previews for example
[09:49] <mhr3> although they're zoomable prop should be false
[09:49] <mhr3> their*
[09:50] <tsdgeos> mhr3: do we have a design how a zoomable image is supposed to behave?
[09:51] <tsdgeos> is it supposed to be zoomable in place? or should it kind of be a press -> grow fullscreen -> then zoomable
[09:51] <mhr3> tsdgeos, the spec doesn't mention fullscreening
[09:51] <tsdgeos> so zoomable in place
[09:51] <mhr3> it does for gallery though
[09:51] <mhr3> so yea, in place afaict
[09:52] <tsdgeos> ok, that's what paulliu has done, bit weird UX wise though i'd say
[09:52] <mhr3> on phone weird, yea, less so on other form factors
[09:54] <mzanetti> Saviq: what happens with unity8 when the screen is off?
[09:54] <mzanetti> Saviq: is unity8 frozen too?
[09:55] <mzanetti> seems to suspend call for the app is only executed once the screen is turned on again
[09:55] <mzanetti> hmm... crap... yeah, we only lock the screen on wakeup
[09:56] <mzanetti> and the suspend logic is bound to the greeter.locked
[09:56] <tsdgeos> mzanetti: don't spend much time on that i guess
[09:57] <tsdgeos> since there's mterry's split greeter "coming somewhen"
[09:57] <mzanetti> I won't... But I was really curious on why that bug was happening, given that I only recently tested that suspend-app-on-greeter.locked
[10:06] <mzanetti> I'll never understand when and why I can or can't reassign bugs in Launchpad
[10:06] <mzanetti> today I can't
[10:12] <tsdgeos> mzanetti: it's all magic
[10:12] <tsdgeos> mzanetti: but i think it depends if the bug is in the unity8 product or in the unity8 package
[10:13] <tsdgeos> you have karma over the product but not over the package
[10:13] <tsdgeos> since you're not an ubuntu bug admin
[10:13] <tsdgeos> or something
[10:21] <Saviq> mzanetti, what tsdgeos said - we can't assign to people other than ourselves for the Ubuntu task - because that's an Ubuntu bug, in the unity8 package
[10:21] <tsdgeos> mzanetti: you'll take care of https://code.launchpad.net/~ted/unity8/launcher-dbus/+merge/215917 that is launcher related?
[10:21] <Saviq> mzanetti, and we're not https://wiki.ubuntu.com/UbuntuBugControl
[10:24] <Cimi> tsdgeos, how about using a sequential animation that sets filter on start / end?
[10:25] <tsdgeos> Cimi: given that it has to be set on start when uncollapsing and at the end when collapsing, i don't see the difference with the current code, it'd even be more weird i'd say
[10:27] <Cimi> tsdgeos, but now I don't understand something:
[10:28] <Cimi> tsdgeos, in case of setFilter(false. true) d.filter ends up being set twice
[10:29] <Cimi> confused that the setFilter and set of variable inside the behaviour might race
[10:30] <tsdgeos> Cimi: how is it going to race?
[10:30] <tsdgeos> it's set to false two times
[10:30] <Cimi> in case setFilter is called twice *whilE* behaviour is running
[10:30] <tsdgeos> is that raceable?
[10:30] <mzanetti> tsdgeos: yes, I'll take care of that one
[10:31] <Cimi> setFilter false true; setFilter true false
[10:31] <tsdgeos> ok
[10:32] <tsdgeos> what would happen?
[10:32] <tsdgeos> because i don't see anything wrong
[10:32] <tsdgeos> besides noone does that kind of call, but let's accept it could happen
[10:33] <Cimi> or other combinations
[10:33] <Cimi> I don't know, just thinking
[10:33] <tsdgeos> i am thinking
[10:33] <Cimi> all this filter code is not nice to read
[10:33] <tsdgeos> and i can't see anything broken with it
[10:34] <Cimi> I don't mean yours, in general
[10:34] <tsdgeos> so don't say "I don't know" when you try to say something is not going to work
[10:35] <Cimi> tsdgeos, I said I was confused and I didn0t understand
[10:35] <tsdgeos> ok, sorry for the misunderstanding
[10:36] <Cimi> tsdgeos, I learnt to be very cautious with animations in the past years, especially when I had animations running and objects destroyed while animations were running :)
[10:37] <Cimi> I just like to set things either before or totally after an animation, not in the meanwhile
[10:42] <tsdgeos> Wellark: see my last comment on https://code.launchpad.net/~kaijanmaki/unity8/indicator-root-state-icons-fix/+merge/213727
[10:43] <tsdgeos> Cimi: any reason you're not copying the entire checklist?
[10:45] <Cimi> tsdgeos, which case?
[10:45] <tsdgeos> Cimi: https://code.launchpad.net/~cimi/unity8/fix-1309135/+merge/216707
[10:45] <Cimi> tsdgeos, because I did not change the packaging
[10:46] <Cimi> so if I answer no is like
[10:46] <Cimi> "no I did not subscribe"
[10:46] <Cimi> and I did not change the ui
[10:46] <Cimi> they are "if you"... so I skip them
[10:49] <tsdgeos> Cimi: ok, i prefer a N/A or something, but ok
[10:50] <tsdgeos> Cimi: aboout those required fields
[10:50] <tsdgeos> can it only be review or rating?
[10:50] <Cimi> ok will do next time
[10:50] <tsdgeos> can not both be required?
[10:50] <Cimi> tsdgeos, they are both then
[10:51] <Cimi> tsdgeos, widgetData['required'] = "both"
[10:51] <tsdgeos> Cimi: you meant the variable value will be "both"? then your check in readyToSubmit doesn't work?
[10:51] <tsdgeos> ah it does
[10:51] <tsdgeos> ignore me
[10:52] <tsdgeos> you're doing !== and not [10:52] <Cimi> yes
[10:52] <Cimi> there are tests for that :)
[10:53] <tsdgeos> yeah, i wondered how the tests were passing ^_^
[12:35] <Wellark> tsdgeos: thanks for the headsup
[12:35] <Wellark> I was going to do that once I have all the MP's ready
[13:01] <Saviq> Wellark, hey, you got a INPROGRESS workitem in https://blueprints.launchpad.net/ubuntu/+spec/notifications-ng-backend - should probably be moved outside of there and that BP closed?
[13:01] <Saviq> thostr_1, ↑
[13:02] <Saviq> Wellark, some more here https://blueprints.launchpad.net/ubuntu/+spec/launcher-backend-api - should probably include the interface Ted was doing for launcher counters
[13:03]  * thostr_1 checking...
[13:06] <thostr_1> Saviq: yes, makes sense.... are you doing some spring cleaning
[13:06] <Saviq> thostr_1, I am, yes, trying to revive blueprint usage
[13:07] <Saviq> so going through all old BPs and moving incomplete tasks to ones that are targeted towards meaningful milestones in the current cycle
[13:07] <thostr_1> Saviq: do you already have a new bp for remaining dash UI items
[13:07] <Saviq> thostr_1, not yet, will have one in a few minutes probably
[13:07] <Saviq> thostr_1, I'll let you know
[13:08] <thostr_1> Saviq: thanks.  I'll just make sure that the items you have left there are in sync with todo items/priorities on design side
[13:08] <Saviq> thostr_1, kk
[13:15] <Saviq> thostr_1, https://blueprints.launchpad.net/ubuntu/+spec/client-1410-unity-ui-dash
[13:20] <Wellark> Saviq: by all means just clean away all the old items
[13:25] <Saviq> thostr_1, there's one more item here: https://blueprints.launchpad.net/ubuntu/+spec/unity-greeter-backend
[13:25] <Saviq> TODO I mean
[13:33] <Saviq> thostr_1, fwiw, there's also https://docs.google.com/a/canonical.com/document/d/1jeGVALlFH7KFEuu7DNPW1KhEhBFh1GhcT4ZsSxIRRqY/edit
[13:33] <Saviq> thostr_1, which lists items that are missing spec and/or implementation
[13:35] <Saviq> thostr_1, I've just moved implementation-only items to the blueprint
[13:40] <Saviq> thostr_1, pete-woods, FYI: https://blueprints.launchpad.net/ubuntu/+spec/client-1410-unity-ui-infographics
[13:41] <kgunn> Saviq: agreed on bug 1311966 ... there may be a couple of bugs in there, the touch driver shouldn't be active for sure, altho not sure what "stops" the music....or why that's touch related
[13:41] <kgunn> was gonna test mako this morning
[13:42] <Saviq> kgunn, ATM music stops 'cause app is suspended on screen off, since it plays in-process - which will/should not be the case
[13:42] <Saviq> kgunn, but it should never resume until unlocked, not to mention when screen is off :)
[13:43]  * Saviq wonders if the launcher/greeter hinting have anything to do...
[13:43] <Saviq> like greeter.locked might be switching to false when hinting...
[13:43] <kgunn> Saviq: ...ah, but riddle me this, why does music keep playing uniterrupted on the virgin image ??
[13:43] <Saviq> kgunn, hah!
[13:43] <Saviq> kgunn, bug #1309915
[13:44] <Saviq> kgunn, greeter.locked would only become true when the screen turned on again
[13:44] <Saviq> kgunn, 'cause that's when the greeter actually comes on screen with blocked egl
[13:44] <Saviq> s/egl/swap/
[13:48] <kgunn> Saviq: sorry, what's confusing me isn't the greeter locked aspect ..or song advance. its why on the virgin image the song just keeps playing even after idling with screen off, but when i add non-block swap buffers, there is some time after idling at which the song is paused
[13:49] <mterry> kgunn, that's because in blocking mode, the greeter doesn't get to finish coming out -- so doesn't register as locked
[13:49] <mterry> kgunn, but with non-blocking, the greeter comes out in the background and is considered locked, suspending the app
[13:49] <kgunn> oh i see now....
[13:49] <kgunn> thanks
[13:49] <kgunn> demystified
[13:49] <Saviq> mterry, thanks :)
[13:49]  * Saviq goes to find a book on explaining things better
[13:49] <kgunn> lol
[13:50] <Saviq> kgunn, so basically, not a non-blocking-swap bug
[13:50] <kgunn> Saviq: it me not you...... remember with kgunn...mono-syllables
[13:50] <Saviq> :D
[13:58] <Cimi> I'll be back in 20 mins
[14:02] <Saviq> mzanetti, the "fix launcher snapping" Qt bug was merged wasn't it?
[14:02] <mzanetti> no, I don't think so
[14:03] <mzanetti> Saviq: people didn't like Alberts approach and as its not really visible on the phone we postponed it
[14:03] <Saviq> oh kk
[14:04] <Saviq> mzanetti, any updates to the work items in https://blueprints.launchpad.net/ubuntu/+spec/client-1404-unity-ui-launcher ?
[14:04] <Saviq> like the last autopilot one?
[14:06] <mzanetti> Saviq: I think we have this one now: Autopilot testing for application management from Launcher: TODO
[14:07] <mzanetti> Saviq: but for the rest no, seems still what it is
[14:07] <Saviq> worst blueprint execution ever :D
[14:07] <kgunn> Saviq: so i feel dumb...what's a suru icon ?
[14:07] <Saviq> kgunn, suru icon _theme_
[14:07] <Saviq> kgunn, suru is just the name
[14:08] <Saviq> kgunn, suru is the name we use for the new ubuntu styles used on phone, like the folded paper and such
[14:08] <kgunn> ok...didn't realize it was named
[14:08]  * kgunn thought it was called "stuff design team gave us" :)
[14:09] <Saviq> kgunn, and we have the new icon theme to go with it
[14:13] <Saviq> kgunn, can you please make https://blueprints.launchpad.net/ubuntu/+spec/client-1404-unity-ui-windowmanager happen to move against a 1410 milestone, wasn't involved much with this bp so don't want to step on toes
[14:14] <Saviq> kgunn, maybe a rename and retarget, since the whole thing is still active
[14:16] <kgunn> Saviq: yep...
[14:16] <kgunn> i always feel conflicted about retarget but maybe that's the right thing
[14:19] <tsdgeos> quick & easy one
[14:19] <tsdgeos> https://code.launchpad.net/~aacid/unity8/killqt51/+merge/217055
[14:19] <Saviq> kgunn, yeah, I generally move items around, but maybe it's fine in this case
[14:26] <Saviq> kgunn, remove the right-edge dependency from https://blueprints.launchpad.net/ubuntu/+spec/client-1410-unity-ui-windowmanager please?
[14:26] <Saviq> since that one's completed and targeting 1404
[14:50] <Saviq> kgunn, ok then, looks like we got the bps cleaned up / updated to U - I only targeted a few items for ubuntu-14.* milestones, we'll probably want to schedule more work at some point soon
[14:51] <mzanetti> mterry: maybe this comments is valid for the greeter too? https://code.launchpad.net/~ted/unity8/launcher-dbus/+merge/215917/comments/515908
[14:51] <kgunn> Saviq: and thank you very much for that....i'll try to review today
[14:52] <mterry> mzanetti, yeah  :(  Compatibility sucks
[14:52] <mzanetti> ah ok... so its compatibility indeed
[14:53] <mterry> mzanetti, at least for UnityGreeter -- that's part of "public" api
[14:53] <mzanetti> ok then
[14:53] <mzanetti> just noticed it so I thought I ask
[14:56] <asac> Saviq: how important is the split of unity8-common?
[14:56] <Saviq> asac, it's mostly due to bug #1304548
[14:57] <Saviq> asac, so not something we'd do for trusty any more, we'll wait for U
[14:58] <asac> hmm
[15:00] <dednick> Saviq: we using unity-mir/devel now?
[15:00] <dednick> for MPs
[15:01] <Saviq> dednick, yeah, mir kinda infected unity-mir with the devel approach
[15:02] <Saviq> 'cause they wanted to include unity-mir in the mir staging PPA
[15:02] <dednick> Saviq: heh. well.. better than having to apply multiple patches to my branch.
[15:02] <dednick> Saviq: ah, i c
[15:02] <Saviq> dednick, has its pros and cons
[15:02] <dednick> indeed
[15:07] <mhr3> i feel like a proper engineer now
[15:07] <mhr3> as i have a branch for unity-mir :P
[15:09] <tsdgeos> josharenson: ping
[15:10] <tsdgeos> josharenson: you probably want to merge  lp:~aacid/unity8/killqt51  into your https://code.launchpad.net/~josharenson/unity8/doc_args/+merge/216649  branch (you'll have to resubmit the MR setting a prerequisite branch)josharenson
[15:19] <tsdgeos> Cimi: honestly i don't know what's the difference between the imports
[15:24] <tsdgeos> ah, read the docu about it
[15:24] <tsdgeos> Cimi: doesn't give us anything
[15:24] <tsdgeos> i'll comment in the MR
[15:24] <tsdgeos> it actually could break some of the stuff
[15:29] <josharenson> tsdgeos, thanks
[15:32] <Wellark> Saviq: so what do you want me to do with those expired work items?
[15:32] <Wellark> I moved them now to a new bp: https://blueprints.launchpad.net/ubuntu/+spec/topic-u-unity-apis
[15:33] <Wellark> but what should I do with the old bp's?
[15:34] <Wellark> just remove the items from them and mark the bp's "Implemented" ?
[15:34] <Saviq> Wellark, ideally remove those moved items (btw, you put them in whiteboard instead of workitems)
[15:34] <Saviq> Wellark, and yeah, mark the bps Implemented indeed
[15:34] <Wellark> Saviq: well, if I put them to Items then there is the strict formatting and I can't have the titles
[15:35] <Saviq> Wellark, yeah, but you really need them there
[15:35] <Saviq> Wellark, otherwise they're not considered as work items, and not listed in the places where we do track work items
[15:36] <Saviq> i.e. http://status.ubuntu.com, http://launchpad.net/~/+upcomingwork etc.
[15:36] <Saviq> and you can't target them for a certain milestone
[15:36] <Wellark> Saviq: yes, but they are not "upcoming" work as nobody will work on them
[15:36] <Wellark> the whole point is just keep them stored somewhere
[15:36] <Saviq> Wellark, Ted is already working on the counters at least ;)
[15:36] <Wellark> well, then he will have his own BP
[15:37] <Wellark> and we will remove the relevant items from that whiteboard :)
[15:37] <Saviq> no he won't, it's just a one line task
[15:37] <Saviq> Wellark, sure, and "Work items for later:" is the way to put them for later, but still make them actual work items
[15:37] <Saviq> "later" being a moving milestone
[15:38] <Wellark> sure, but then I have to augment all of the items with somethig as I can't make sections inside the "Work items for later:"
[15:38] <Wellark> but I will let thostr_1 to figure it out ;)
[15:38] <Wellark> thostr_1: https://blueprints.launchpad.net/ubuntu/+spec/notifications-ng-backend
[15:38] <Wellark> could you please mark that as "Implemented"
[15:38] <Saviq> Wellark, thx
[15:41] <thostr_1> Wellark: done
[15:42] <pete-woods> can anyone help me with the finer points of getting unity8 to load a QML plugin from a path of my choosing? I've tried modifying the QML2_IMPORT_PATH env var
[15:42] <pete-woods> but it doesn't seem to quite work
[15:43] <tsdgeos> pete-woods: how are you running unity8? with ./run ?
[15:43] <pete-woods> tsdgeos: yes
[15:43] <Saviq> pete-woods, I think it overwrites QML2_IMPORT_PATH...
[15:43] <tsdgeos> eyah
[15:43] <pete-woods> Saviq: I've also tried changing the script
[15:43] <Saviq> hmm no shouldn't
[15:43] <tsdgeos> ah
[15:43] <tsdgeos> ok
[15:44] <tsdgeos> then it should work
[15:44] <Saviq> pete-woods, might be that some other path ends up earlier on the list
[15:44] <pete-woods> basically I'm doing var = /home/pete/Source/unity-scopes-shell/trunk-install/lib/x86_64-linux-gnu/unity8/qml/
[15:44] <pete-woods> (where I'm installing the plugin)
[15:44] <pete-woods> does that sound right?
[15:44] <tsdgeos> pete-woods: can you get a dummy .qml + qmlscene pick it up?
[15:44] <Saviq> or qmlplugindump easier
[15:44] <Saviq> pete-woods, try qDebug() << engine().importPathList() to see how the import path list looks in the end
[15:44] <tsdgeos> just to make sure your install dir struct is correct and stuff
[15:45] <Saviq> pete-woods, but yeah, "QML2_IMPORT_PATH=foo qmlplugindump MyPlugin 0.1" needs to work, too
[15:45] <kgunn> Cimi: i know welcome wizard is kind of done from your end, waiting on settings changes for privacy pages to happen....anything else ?
[15:46] <pete-woods> Saviq: how do I know what is the correct output from qmlplugindump?
[15:47] <pete-woods> ph
[15:47] <pete-woods> oh
[15:47] <pete-woods> okay,
[15:47] <pete-woods> that's outputting a load of json like stuff
[15:47] <pete-woods> qml, even
[15:47] <Saviq> yeah, that means it found the plugin
[15:47] <Saviq> now question is whether it found the one you wanted
[15:48] <Saviq> and not one that's installed system-wide
[15:48] <tsdgeos> strace ¿
[15:49] <Saviq> or just look for the difference in the API
[15:49] <Saviq> it also depends whether you have a system-wide installed one at all
[15:49] <Saviq> i.e. if it fails without QML2_IMPORT_PATH=foo, then you know
[15:49] <pete-woods> Saviq: there is a system installed one
[15:50] <pete-woods> I'm going to bin it to check
[15:50] <Saviq> pete-woods, add "qDebug() << view->engine()->importPathList();" after line 123 in main.cpp
[15:50] <Saviq> pete-woods, it will print out which paths are added, and in what order
[15:51] <pete-woods> qmlplugindump is definitely loading the version of the plugin I have
[15:51] <Saviq> pete-woods, good
[15:51] <Saviq> pete-woods, which plugin would that be?
[15:52] <pete-woods> Saviq: it's the Unity plugin I'm working with
[15:52] <pete-woods> hmm
[15:52] <pete-woods> that debug output doesn't show the path I would expect in the list...
[15:53] <Saviq> pete-woods, ah
[15:53] <Saviq> pete-woods, I think we failed a bit when moving "run" to upstart
[15:54] <Saviq> pete-woods, add 'QML2_IMPORT_PATH=$QML2_IMPORT_PATH' at the end of the /sbin/initctl start call
[15:54] <Saviq> tsdgeos, bug in run ↑
[15:55] <Saviq> tsdgeos, upstart jobs don't inherit env from the initctl caller
[15:55] <pete-woods> Saviq: awesome, that's fixed it
[15:55] <Saviq> tsdgeos, need to pass them explicitly as KEY=VALUE to the initctl call
[15:55] <tsdgeos> Saviq: ouch
[15:56]  * Saviq review fail
[15:56] <tsdgeos> Saviq: you do? i do?
[15:56] <Saviq> tsdgeos, /me
[15:59] <Saviq> tsdgeos, for tomorrow: https://code.launchpad.net/~saviq/unity8/fix-run-upstart-env/+merge/217080
[15:59] <Saviq> pete-woods, for reference ↑
[16:00] <tsdgeos> Saviq: you sure that works?
[16:00] <Saviq> tsdgeos, yeah, tried with -p, -k
[16:00] <tsdgeos> ok
[16:01] <Saviq> doesn't change anything in trunk, enables locks in that branch
[16:03] <Cimi> tsdgeos, you know why ;vw[h is failing a lot revently?
[16:04] <tsdgeos> Cimi: parse erorr :D
[16:04] <tsdgeos> you mean lvwph ?
[16:04] <Cimi> ahah yes
[16:04] <Saviq> lol
[16:04] <Saviq> more tomorra o/
[16:04] <tsdgeos> Cimi: yeah we messed up with a merge
[16:04] <Cimi> sorry I don't look at my keyboard while I type
[16:04] <tsdgeos> Cimi: we have a merge that fixes it
[16:04] <Cimi> sometimes not even at the screen :D
[16:04] <tsdgeos> but since we're not integrating
[16:04] <tsdgeos> it's just laying there
[16:05] <tsdgeos> if it's the listviewwithpageheaderqml:compile error
[16:05] <tsdgeos> you can ignore it
[16:05]  * tsdgeos leaves for the day
[16:57] <Cimi> mterry, don't know if you fixed this in the meanwhile
[16:57] <Cimi> mterry, but with landing 002
[16:57] <Cimi> on the phone
[16:58] <Cimi> I see the greeter automatically teasing and getting stuck now
[17:20] <Cimi> Saviq, where is powerd qml module we use in shell?
[17:23] <mzanetti> Cimi: plugins/Powerd
[17:23] <Cimi> ah han!
[17:23] <Cimi> and me bloody googling
[17:26] <mterry> Cimi, automatically teasing and getting stuck?  Stuck how?
[17:26] <Cimi> mterry, 1-2 gu inside the screen
[17:26] <Cimi> no input
[17:26] <mterry> Cimi, curious, I haven't seen that yet
[18:25] <Saviq> josharenson, to reply to your MP questions: yes, you got it right, there's a "resubmit proposal" link at the top right of the MP page
[18:26] <josharenson> saviq, thanks. I'll get to that by eod