[01:56] <Saviq> elopio, thanks to you, they're in silo, hopefully for release soon
[07:14] <Cimi> morning
[07:20] <Cimi> Saviq, scope settings review :P
[07:52] <Cimi> Saviq, what is "alt nav"?
[08:54] <Cimi> bug with dash and manta
[08:54] <Cimi> open sidestage, close
[08:54] <Cimi> then dash becomes unresponsive
[08:55] <Cimi> in reality is processing things but the texture is not updated
[08:55] <Cimi> greyback, ?
[08:56] <greyback> Cimi: log a bug please
[09:11] <Saviq> Cimi, yeah, need to crwbar-open the eyes first
[09:12] <Cimi> Saviq, saw you worked till late
[09:14] <Saviq> Cimi, till early, rather
[09:15] <Cimi> hah
[09:15] <Saviq> but!
[09:15] <Saviq> check this out http://s-jenkins.ubuntu-ci:8080/job/unity-phablet-qmluitests-utopic/895/
[09:15] <Cimi> cannot, stupid vpn
[09:16] <Saviq> no vpn for you
[09:16] <Saviq> https://jenkins.qa.ubuntu.com/job/unity-phablet-qmluitests-utopic/895/
[09:16] <Saviq> Cimi, ↑
[09:16] <Cimi> @_@
[09:16] <Cimi> wow
[09:16] <Cimi> was used to red
[09:17] <Saviq> yikes autopilot failed on that completely, though :|
[09:19]  * Saviq worried something got seriously wrong
[09:27] <Cimi> Saviq, eyes working now?
[09:28] <Cimi> Saviq, so what is Alt Navigation?
[09:28] <Saviq> Cimi, https://drive.google.com/drive/#folders/0B32jwBcbaPloR1IyRF91ZWs0bFE
[09:28] <Saviq> Cimi, see ebay
[09:35] <Cimi> Saviq, Alt means secondary?
[09:35] <Saviq> Cimi, alternative
[09:35] <Cimi> Saviq, we never shortened variable names so far, btw
[09:36] <Saviq> Cimi, I know
[09:36] <Cimi> we should have called Alternative
[09:36] <Saviq> Cimi, but they are all long enough already
[09:36] <Saviq> AlternativeNavigationFOo
[09:36] <Cimi> So what?
[09:36] <Cimi> is consistency...
[09:36] <Cimi> I assumed it meant the Alt key
[09:36] <Cimi> either Alt key or a shortened for Alternative
[09:36] <Saviq> Cimi, the Alt key means Alternative, so you assumed kinda right ;)
[09:37] <Cimi> hah
[09:37] <Cimi> dednick, speaking of shortening, in your indicator polishing branch, you used id: ani instead animation, as well as other shortening, can you not shorten?
[09:37] <Saviq> Cimi, I understand your concern, but unless you come up with a better shorter alternative (pun intended), I think we should deal with Alt
[09:38] <Cimi> Saviq, SecondNavigation
[09:38] <Saviq> Cimi, except it's the first one!
[09:38] <Saviq> ;)
[09:39] <Saviq> left-to-right that is
[09:39] <Cimi> AlternateNavigation :P
[09:39] <Cimi> Primary then
[09:39] <Cimi> or First
[09:39] <dednick> Cimi: yeah. just add it to your comments.
[09:39] <Saviq> Cimi, well, no, because it's neither first, nor primary either
[09:39] <Saviq> Cimi, Alternate isn't much better
[09:39] <Saviq> 2 letters
[09:40] <Cimi> Saviq, anyway I commented that we need ellipsis
[09:40] <Saviq> Cimi, sure, you could even review it
[09:40] <Cimi> I was reviewing
[09:40] <Cimi> :)
[09:40] <Saviq> with the exception that I redo half of it in https://code.launchpad.net/~saviq/unity8/header-customizations/+merge/230719
[09:40] <Saviq> to improve visuals and such
[09:41] <Cimi> I wanted to review your small branches (so lazy I am), then I realised they are all dependent so I was starting from the first one
[09:41] <Saviq> Cimi, good thinking :D
[09:42] <Cimi> Saviq, they are tricky, you see they are 100 diff lines, you claim the review, and then you realise you're now in big trouble :D
[09:42] <Cimi> glad it doesn't depend on split greeter
[09:42] <Saviq> Cimi, gotcha
[09:43] <Cimi> Saviq, do we want to have this alt navigation in?
[09:44] <Saviq> Cimi, yeah, I'll take it over
[09:44] <Cimi> Saviq, then address those in your header customisation?
[09:44] <Saviq> Cimi, or I can take Albert's branch over
[09:44] <Cimi> Saviq, be aware that there are tags in that branch, so we need to delete them asap they got merged
[09:44] <Cimi> Saviq, then you have to rebase your branches though
[09:45] <Saviq> Cimi, just the first one
[09:45] <Saviq> Cimi, since it's a chain
[09:47] <Saviq> Cimi, I think I'll rebase and actually bring a bunch of the changes over, no point in having the branches split
[09:48] <Cimi> Saviq, up to you, but would be best
[09:48] <Cimi> I still have a look now
[09:49] <Saviq> Cimi, I might need to re-chain them though (put alt nav last) in that case
[09:49]  * Saviq doesn't want to :|
[09:58] <mzanetti> Saviq: you won't believe it :D
[09:58] <mzanetti> Saviq: current state of my device: touch input broken, mouse input working :D
[09:58] <mzanetti> or rather :(
[10:00] <Saviq> mzanetti, sounds like you're it
[10:00] <Saviq> bug #1295623
[10:01] <Saviq> mzanetti, I think this is the time to 'apt install qtdeclarative5-dbg qtcore5-dbg unity8-dbsym unity8-private-dbgsym`
[10:01] <Saviq> mzanetti, and step on it
[10:01] <Saviq> mzanetti, one thing
[10:01] <mzanetti> Saviq: I rebooted already
[10:01] <Saviq> mzanetti, NOOOOOOOOOOO
[10:01] <mzanetti> Saviq: and what I said is that its the other way round
[10:02] <Saviq> mzanetti, well, still
[10:02] <mzanetti> Saviq: edges were broken and apps were working
[10:02] <mzanetti> Saviq: anyways.. seems I'm getting this more often again lately
[10:02] <mzanetti> yesterday I had it twice
[10:02] <Saviq> mzanetti, so you were stuck to one app basically?
[10:02] <mzanetti> Saviq: yep, system-settings and indicators :)
[10:02] <mzanetti> that's it
[10:02] <Saviq> indicators?
[10:02] <Saviq> indicators are touch too
[10:02] <mzanetti> yeah... the panel is 2 gu's tall
[10:03] <mzanetti> in which area you can also pull it by mouse
[10:03] <Saviq> hmm can you
[10:03] <Saviq> mzanetti, no you can't
[10:03] <Saviq> mzanetti, the whole 2gu is touch
[10:04] <mzanetti> Saviq: err, yeah... the panel is more
[10:04] <mzanetti> the 2 gu is touch, the rest mouse
[10:04] <Saviq> mzanetti, ok, the whole panel is touch
[10:04] <Saviq> ah wait
[10:04] <Saviq> maybe I'm locked and that's why
[10:04] <mzanetti> anyways... it was working, but no launcher and no spread
[10:04] <Saviq> mzanetti, hmm without -mousetouch I can't do anything with indicators on desktop
[10:05] <Saviq> mzanetti, and I really believe the whole panel is touch
[10:05] <mzanetti> so maybe some other issue
[10:05] <Saviq> sounds like the edge areas got stuck somewhat
[10:05] <mzanetti> I have a feeling that the lockscreen plays bad on me every once in a while
[10:05] <Saviq> or maybe went under the app
[10:05] <Saviq> mzanetti, btw https://jenkins.qa.ubuntu.com/job/unity-phablet-qmluitests-utopic/895/?
[10:06] <Saviq> thanks again
[10:06]  * mzanetti gets out his pom poms
[10:06] <mzanetti> *\o/*
[10:06] <Saviq> mzanetti, there's a butt
[10:06] <Saviq> mzanetti, https://jenkins.qa.ubuntu.com/job/generic-deb-autopilot-runner-mako/3411/?
[10:06] <Saviq> but I very much doubt related
[10:06] <mzanetti> oh man...
[10:06] <Saviq> waiting for some other run after this got merged
[10:06] <mzanetti> ok... all fail... so there's chances its some single thing that breaks it
[10:07] <Saviq> mzanetti, well, half of 'em
[10:07] <Saviq> but I ran them all yesterday on mako and got all OK
[10:07] <Saviq> before landing the silo
[10:07] <Saviq> the other device is currently broken totally, so that failed
[10:08] <Cimi> Saviq, reviewed https://code.launchpad.net/~aacid/unity8/alt_nav_support/+merge/230054
[10:10] <laze1989> Any chance that the AppIndicator's API will change with Unity 8? I see limitations that the indicators are now traditional menus (e.g., in Chrome's new Notification Icon). Windows and OS X got it right.
[10:10] <laze1989> This concerns especially the desktop part.
[10:11] <Saviq> laze1989, we're still quite far away from desktop implementation, there's no extensive design for the next iteration of Unity on desktops
[10:12] <Saviq> laze1989, but please file a bug against ubuntu-ux so that we don't misplace your concern
[10:20] <Cimi> Saviq: 180	+        // only way to convert string to color 181	+        var c = Qt.lighter(arguments[k], 1.0);
[10:20] <Cimi> seriously?
[10:20] <Saviq> Cimi, ideas welcome
[10:21] <Cimi> this is in C++ right?
[10:21] <Saviq> Cimi, that's JS
[10:21] <Cimi> Saviq, so we can write a parser
[10:21] <Saviq> Cimi, no we can't
[10:21] <Cimi> Saviq, I meant, Qt.lighter is C++?
[10:21] <Saviq> Cimi, yes, it is
[10:21] <Cimi> the algorithm
[10:21] <Cimi> yeah
[10:21] <Cimi> so there is no benefit of writing a parser
[10:22] <Saviq> Cimi, you can't even write a parser, how do you parse "white"?
[10:22] <Saviq> Cimi, this needs to go through QColor
[10:22] <Saviq> Cimi, this is basically a no-op
[10:22] <Cimi> ]I see
[10:22] <Cimi> just ugly
[10:22] <Cimi> but probably best thing
[10:22] <Saviq> Cimi, it will do QColor() and multiply its .v by 1.0
[10:22] <Saviq> Cimi, and return it
[10:27] <Saviq> Cimi, I *could* just make this whole function C++ though
[10:27] <Cimi> Saviq, it is probably faster
[10:27] <Saviq> and maybe even use .v directly, having checked that it's a good enough value for us
[10:28] <Saviq> Cimi, how about a TODO then
[10:29] <Cimi> can we use shaders for those color operations?
[10:30] <Cimi> feel free to offend me
[10:30] <Cimi> I don't know much about shaders :)
[10:43] <laze1989> I tried to articulate myself :-) https://bugs.launchpad.net/ubuntu-ux/+bug/1356816
[11:13] <facundobatista> Hola
[11:21] <Saviq> Cimi, ugh, I need to reorder the branches, managed to do something real weird to them
[11:23] <Saviq> I think I pushed to the wrong branch at some point
[11:23] <Saviq> yeah
[11:28] <dednick> Cimi: done with review
[11:28] <dednick> fixed i mean
[11:28] <Cimi> dednick, thx
[11:36] <Cimi> dednick, next step is potfiles for that
[11:36] <Cimi> dednick, different branch though
[11:37] <Cimi> dednick, if we are going to have a horizontal listview in the indicators, we cannot stay with the sound slider issue
[11:37] <dednick> Cimi: yeah
[11:37] <Cimi> dednick, either add a mousearea around it eating those events
[11:37] <Cimi> or follow up with sdk
[11:37] <dednick> Cimi: the menus aren't interactive, only the header is
[11:37] <Cimi> it is in the examples
[11:38] <dednick> Cimi: yeah, i know
[11:38] <Cimi> dednick, so if is just examples - fine
[11:38] <Cimi> but if it will be in unity8, nope
[11:38] <dednick> Cimi: it's just the examples
[11:38] <Cimi> anyway let's make them aware
[11:38] <mzanetti> Saviq: do you know if something regarding SIM pin unlocking landed in the indicators?
[11:39] <Saviq> mzanetti, not recently no
[11:39] <mzanetti> Saviq: hmmm... the button to open the unlock dialog doesn't seem to show up any more here
[11:39] <mzanetti> will investigate
[11:39] <Saviq> mzanetti, wfm
[11:40] <mzanetti> Saviq: hmm... maybe I blocked it
[11:40] <mzanetti> and it just fails to ask for the PUK
[11:40] <Cimi> dednick, can we bump UC to 1.1?
[11:41] <dednick> Cimi: why?
[11:41] <dednick> Cimi: oh, you mean dependency?
[11:42] <Cimi> dednick, in the files
[11:42] <Cimi> dednick, I want to make sure we use the latest
[11:46] <Cimi> dednick, the wobbly animation on the icon in MessageComponents only work on expansion
[11:46] <Cimi> dednick, is that wanted?
[11:46] <dednick> yes
[11:46] <Cimi> ok
[11:46] <Cimi> dednick, also is always on for unexpandable ones
[11:46] <dednick> ya
[11:46] <Cimi> ok
[11:46] <Cimi> well rest is fine
[11:47] <Cimi> dednick, I'd just bump to 1.1 as said
[11:47] <Cimi> for the file we touch
[11:48] <Saviq> Cimi, https://code.launchpad.net/~cimi/unity8/scope-settings/+merge/230182/comments/560879 looks like a valid fail
[11:48] <Saviq> even though at first glance you're not touching anything there...
[11:48] <Cimi> Saviq, which failure?
[11:49] <Saviq> maybe a compare() instead of tryCompare
[11:49] <Cimi> of the two?
[11:49] <Saviq> Cimi, hmm let's see another run
[11:49] <Cimi> I can try locally
[11:50] <Cimi> Saviq, I also merged trunk lately
[11:51] <Saviq> Cimi, well, yeah, but at least after my fix-foo branch it passed, maybe something else in the recent landing
[11:51] <Cimi> testDash works here
[11:51] <dednick> Cimi: ok, updated to 1.1
[11:52] <Cimi> Saviq, QML AbstractButton: Binding loop detected for property "implicitWidth" so annoying
[11:52] <Saviq> Cimi, yeah, guess where that is ;)
[11:52] <Cimi> Saviq, yep :P
[11:53] <Cimi> Saviq, both tests pass here
[11:53]  * dednick is hungry!
[11:53] <Saviq> Cimi, ok, let's see, there's more qmluitest runs incoming
[11:54] <Cimi> dednick, http://theburgerlist.tumblr.com/post/94443927060/le-bourguinon-bun-le-bun-riverside-feast-battersea
[12:10] <Cimi> Saviq, did you see my comments in the previous review?
[12:11] <Saviq> Cimi, they shouldn't be lost
[12:11] <Cimi> Saviq, ok
[12:11] <Cimi> they are not
[12:13] <Saviq> not lost or lost?
[12:13] <Saviq> jeez that's a chain
[12:13] <Saviq> now someone needs to start reviewing the beginning of it...
[12:15] <cwayne> Saviq: thanks for landing horizontal-list so quickly :)
[12:15] <Saviq> cwayne, got even more goodness in store https://drive.google.com/drive/#folders/0B32jwBcbaPloR1IyRF91ZWs0bFE
[12:15] <Saviq> cwayne, just now we've like 7 branches dependant on each other that need to be reviewed ;)
[12:16] <cwayne> :D
[12:16] <cwayne> i saw those last night, super excited about it
[12:16] <Saviq> cwayne, do you know if any of the scopes try to send preview button color? I couldn't find any
[12:16] <davmor2> Saviq: if it's this chain it's okay https://www.youtube.com/watch?v=v1iuSmZHcwY
[12:16] <cwayne> Saviq: none of ours do yet
[12:17] <cwayne> Saviq: im happy to whip one up though if its helpful
[12:17] <Saviq> cwayne, nah, is fine
[12:18] <Saviq> davmor2, I'm not sure our chain's as nice as this one
[12:18] <Saviq> davmor2, I fear ours is more like http://www.hoax-slayer.com/images/mother-teresa-novena-chain-1.jpg
[12:18] <Saviq> nice url...
[12:19] <Saviq> davmor2, or well, right now it's more like http://yazminmedia.com/wp-content/uploads/2010/08/blog-broken-chains.jpg
[12:20] <Saviq> @unity I need volunteers to review https://code.launchpad.net/~unity-team/unity8/tablePreviewWidget/+merge/230787 https://code.launchpad.net/~unity-team/unity8/seeLessStuckBottom/+merge/230786
[12:20] <Saviq> there's some free karma in:
[12:20] <Saviq> https://code.launchpad.net/~saviq/unity8/grey-from-palette/+merge/230603
[12:20] <Saviq> https://code.launchpad.net/~saviq/unity8/move-pageheader/+merge/230609
[12:20] <Cimi> Saviq, I can do table preview
[12:21] <Saviq> Cimi, claim it!
[12:21] <Cimi> Saviq, it is automatic to mhr3
[12:22] <Saviq> Cimi, as long as there's no "unity team" in the reviewers list it's fine
[12:23] <Cimi> Saviq, I am lost
[12:23] <Cimi> Saviq, which one is the first???
[12:23] <Cimi> https://code.launchpad.net/~saviq/unity8/grey-from-palette/+merge/230603 ?
[12:23] <Cimi> seems like
[12:24] <Saviq> Cimi, yes
[12:43] <mzanetti> https://code.launchpad.net/~saviq/unity8/update-qmltypes/+merge/230737 and https://code.launchpad.net/~saviq/unity8/grey-from-palette/+merge/230603
[12:43] <mzanetti> Saviq: ^
[12:44] <Saviq> mzanetti, thanks, on the ScopesOverview button... it should really use SDK's Button, I think Albert didn't see the support for an outlined one
[12:45] <Saviq> ah feck it, same branch
[12:45]  * mzanetti got lost... but I'm sure you'll just fix it
[12:45] <mzanetti> :D
[12:47] <Saviq> ohnoes
[12:47] <Saviq> the stroked button does not allow for font color changes /facepalm
[12:48] <Saviq> jeezuz
[12:49] <mzanetti> :D
[12:54] <mzanetti> run_on_device working for you guys?
[12:58] <Saviq> bug #1356864
[12:58] <Saviq> mzanetti, it can't work too well with separate dash
[12:59] <Saviq> mzanetti, i.e. it will launch the system dash
[12:59] <Saviq> I've a branch that should've fixed that, but doesn't...
[12:59] <mzanetti> Saviq: I'm ok with that
[12:59] <mzanetti> Saviq: doesn't start unity at all here
[12:59] <mzanetti> just hangs
[12:59] <Saviq> mzanetti, status unity8?
[13:00] <mzanetti> Saviq: this is the output: http://paste.ubuntu.com/8045193
[13:00] <mzanetti> hangs here at the end
[13:00] <mzanetti> it says "start/running" if asking for status in another shell
[13:00] <Saviq> mzanetti, so no PID
[13:00] <Saviq> mzanetti, looks like it's in a crash loo[
[13:00] <Saviq> loop
[13:00] <mzanetti> hmm
[13:00] <mzanetti> interesting
[13:01] <mzanetti> indeed
[13:01] <mzanetti>   what():  Unknown command line options: -qmljsdebugger=port:3768
[13:01] <mzanetti> well, not in a loop, but just stuck here
[13:03] <Saviq> and bug #1356866
[13:03] <mzanetti> hmm.. removing that arg makes it start...
[13:03] <Saviq> mzanetti, new mir I believe
[13:03] <Saviq> mzanetti, we need to eat that arg before it gets to mir
[13:04]  * mzanetti still thinks libraries should not bail out on arguments they don't know
[13:04] <mzanetti> why would mir prevent me to add some cmdline arg
[13:04] <mzanetti> doesn't make sense to me
[13:04] <mzanetti> if it can't use it, ignore it
[13:08] <greyback_> mzanetti: Mir got a new API to allow us to stop mir bailing on args it doesn't recognise, but qtmir hasn't implemented it yet
[13:09] <mzanetti> an API for that? :)
[13:09] <greyback_> yeah
[13:09] <mzanetti> why would anyone want to enable that?
[13:09] <mzanetti> or better: not want to disable it
[13:10] <greyback_> is there a nice way a library can filter out the cmd line args it accepts?
[13:10] <mzanetti> don't think so...
[13:11] <greyback_> ultimately we don't want a mis-spelled cmd line arg being ignored
[13:11] <mzanetti> hmm... I'd say yes, better that then not starting at all. but even if we agree on that, its imo the applications responsibility to do that
[13:12] <greyback_> so this is an idea we had. Pass all cmd line args to Mir, mir filters out the ones it does accept, I pass the rest to Qt/the app
[13:12] <mzanetti> not one of the libs it loads
[13:12] <greyback_> we let Qt do it. Qt is a lib
[13:13] <mzanetti> qt doesn't assert if there's an argument it doesn't know
[13:13] <greyback_> sure, that's the mir default behaviour. We can (and will) override that
[13:14] <dandrader> greyback_, do you recall why do we have "PKGCONFIG += mircommon mirclient" in the ubuntumirclient QPA? It's supposed to talk just to platform-api...
[13:14] <greyback_> dandrader: nope, I don't recall
[13:14] <dandrader> wonder if it's a leftover. couldn't find any references to mir in the code...
[13:14] <greyback_> we most've missed it so
[13:14] <greyback_> must've
[13:38] <Saviq> @unity more free karma https://code.launchpad.net/~saviq/unity8/update-deps/+merge/230803
[13:41] <Wellark> Saviq: approved
[13:41] <Wellark> do you need top approval?
[13:41] <Saviq> Wellark, sneaky! ;)
[13:41] <Saviq> Wellark, generally yes :)
[13:43] <Cimi> mzanetti, I am reviewing this https://code.launchpad.net/~mzanetti/unity8/new-lockscreen-design/+merge/230478
[13:44] <Cimi> mzanetti, do you want to add https://bugs.launchpad.net/unity8/+bug/1169615 ?
[13:47] <ChrisTownsend> I'm getting the Hello Box o' Doom (ie, the lockscreen) when trying to log into the Unity8 desktop session now.  r1150 looks suspicious to me in causing this behavior, but I'm not 100% sure.
[13:54] <ChrisTownsend> greyback_: I saw your findings in https://bugs.launchpad.net/ubuntu/+source/unity8-desktop-session/+bug/1353041.  Thanks and sorry to blame qtmir:)
[13:54] <greyback_> ChrisTownsend: no worries! I'll see if I can whip up a quick patch fori it anyway
[13:54] <ChrisTownsend> greyback_: Cool, and thanks!
[13:56] <Saviq> mzanetti, fixed all your concerns
[13:59] <Cimi> do you guys use any extension for chrome to organise tabs?
[14:01] <mzanetti> Cimi: I guess I can add that
[14:01] <mzanetti> Cimi: have lots of conflicts now anyways after mterry's branch is merged
[14:01] <mzanetti> Saviq: I approved the grey one already
[14:01] <mzanetti> will check the other now
[14:05] <paulliu> Saviq: for "dash as app", is console.log() still works when do ./run.sh?
[14:06] <Cimi> Saviq, good to merge https://code.launchpad.net/~nick-dedekind/ubuntu-settings-components/indicator-polishing/+merge/229083
[14:08] <paulliu> Saviq: anyway. I found the solution. Watch ~/.cache/upstart/unity8-dash.log
[14:26] <Cimi> Saviq, using style delegates in unity is not nice
[14:26] <Cimi> Saviq, kinda kills the idea of themability
[14:26] <Saviq> Cimi, no it doesn't, if the style depends on the theme
[14:27] <Saviq> Cimi, which it does wherever it can right now
[14:27] <Cimi> Saviq, nope because if I ship my own theme, I still need Ambiance
[14:27] <Saviq> Cimi, it's there because scopes can override the default theme
[14:27] <Saviq> Cimi, you do understand we have virtually no themeability in the SDK currently?
[14:28] <Cimi> Saviq, why that? we have themes
[14:28] <Saviq> Cimi, doesn't mean they actually work properly
[14:28] <Saviq> Cimi, or are thought out
[14:28] <Cimi> it is not full, right
[14:29] <Cimi> but I can have squared buttons if I want
[14:29] <Saviq> Cimi, basically our design team doesn't want to *allow* themeability to the extent we're used to it
[14:29] <Cimi> Saviq, that's false
[14:29] <Saviq> Cimi, talk to them
[14:29] <Cimi> Saviq, what we want is to provide our theme
[14:29] <Cimi> Saviq, and support that
[14:29] <Saviq> Cimi, talk to them
[14:29] <Cimi> as well as allowing some changes for operators
[14:30] <Saviq> Cimi, aaanyway
[14:30] <Saviq> Cimi, the styling component for the dash is a requirement
[14:30] <Saviq> Cimi, but
[14:30] <Saviq> Cimi, as you can see, it tries to base off of the theme where possible
[14:31] <Saviq> Cimi, but the theme is just lacking information in a few places, or is plain incompatible with the dash design
[14:31] <Cimi> dednick, standup
[14:44] <Cimi> Saviq, how do we try qml/Hud/HudParametrizedActionsPage.qml ?
[14:44] <Cimi> on https://code.launchpad.net/~saviq/unity8/move-pageheader/+merge/230609
[14:44] <Saviq> Cimi, tryHud
[14:45] <Saviq> Cimi, but really just make sure testHud works, if we ever bring this back we'll have to fix tons of things there anyway
[14:46] <Cimi> Saviq, yes, but not good reason to regress :)
[14:46] <Cimi> but yeah don't worry about it
[14:56] <Cimi> Saviq, approved, waiting CI
[14:57] <Cimi> Saviq, should be fine, I grep for PageHeader all around
[14:58] <Cimi> on https://code.launchpad.net/~saviq/unity8/header-customizations/+merge/230719 now
[14:58] <Cimi> MacSlow, you still looking for reviews?
[14:59] <Cimi> pete-woods, any update on the fix?
[14:59] <pete-woods> Cimi: it will be rolled out with our next scopes release
[15:00] <pete-woods> which should be "real soon now"
[15:02] <MacSlow> Cimi, yes
[15:03] <MacSlow> Cimi, take any of the top ten from  https://code.launchpad.net/~macslow, which isn't claimed yet...
[15:04] <MacSlow> Cimi, e.g. https://code.launchpad.net/~macslow/sync-monitor/fix-1350282
[15:05] <Cimi> MacSlow, no thanks :D
[15:06] <Cimi> MacSlow, I thought you were looking to do reviews
[15:06] <Cimi> MacSlow, I have already few for today
[15:06] <MacSlow> Cimi, sure... that too... but I would want to focus on Dash-related bits as Saviq suggested during the stand-up
[15:09] <MacSlow> Saviq, speaking of Dash-related MPs... any favourite ones reviewers should focus on?
[15:10] <Saviq> Cimi, you're doing the customization ones and table, right?
[15:10] <Cimi> Saviq, one at a time
[15:10] <Saviq> Cimi, you're assigned to all of them ;)
[15:11] <Cimi> hah yeah
[15:11] <Saviq> Cimi, give one up to MacSlow :)
[15:11] <cwayne> Cimi: any updated ETA on settings landing?
[15:13] <Cimi> cwayne, talk to Saviq :P
[15:14] <Cimi> cwayne, it's waiting review
[15:14] <Cimi> cwayne, looks fine on my side
[15:14] <Saviq> cwayne, hopefully by Monday
[15:14] <Cimi> cwayne, there is though a bug on backend side
[15:14] <Saviq> cwayne, if all else fails, I'll have everything related in silo for Monday
[15:16] <Cimi> Saviq, can we have luminance in C++ ?
[15:16] <Cimi> or well, a generic color util
[15:16] <Cimi> would be nice to have in SDK though
[15:17] <Saviq> Cimi, yeah, 90% of this needs to go into SDK
[15:17] <Saviq> Cimi, and no, you can't atm
[15:17] <Saviq> not worth it
[15:24] <Cimi> Saviq, https://jenkins.qa.ubuntu.com/job/unity-phablet-qmluitests-utopic/903/?
[15:24] <Cimi> still broken on a different branch, might be trunk then
[15:26] <Saviq> Cimi, right, care to find a fix?
[15:26] <Cimi> Saviq, I was looking
[15:26] <Cimi> Saviq, issue is that I cannot reproduce
[15:26] <Saviq> Cimi, ok, I'll have a look in a moment, redoing part of ScopeStyle...
[15:28] <Cimi> they also are using tryCompare... so I don;t know
[15:38] <Cimi> Saviq, I don't understand https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1356487
[15:38] <Saviq> Cimi, right edge is confusing
[15:39] <Saviq> Cimi, we don't have an edge demo for it
[15:39] <Cimi> description is different
[15:40] <Cimi> which is https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1356488
[16:06] <Cimi> Saviq, the total flatness of the header in the new header customisation branch is wanted/design approved?
[16:06] <Saviq> Cimi, wanted
[16:06] <Cimi> Saviq, but we have 3d effect in every other app, and sdk
[16:06] <Saviq> Cimi, https://docs.google.com/a/canonical.com/file/d/0B8I8ZVKH-8SsS01CcE93TFNUSGc/edit
[16:07] <Saviq> Cimi, yeah, and?
[16:07] <Saviq> Cimi, think that's the only place where we differ from SDK?
[16:07] <Cimi> Saviq, there is highlight/3d effect here
[16:08] <Saviq> Cimi, yeah, only in a few places
[16:08] <Saviq> Cimi, but flat is really what's wanted
[16:08] <Cimi> Saviq, I'd add something subtle
[16:09] <Saviq> Cimi, I was told flat
[16:09] <Cimi> it's not hard to achieve, a simple rectangle on top and bottom
[16:09] <Saviq> Cimi, yeah, and then you have a black divider, red header, blue background
[16:09] <Saviq> Cimi, still easy to achieve?
[16:09] <Cimi> Saviq, flat meaning no gradient IN the darker area
[16:09] <Saviq> Cimi, no, flat meaning flat
[16:09] <Cimi> but between that and the top header, there is a little line giving 3d sensation
[16:10] <Saviq> Cimi, https://docs.google.com/a/canonical.com/file/d/0B71w9p1v_aX4VjZtTkc2di15RnM/edit
[16:10] <Saviq> is there?
[16:10] <Cimi> Saviq, you can apply a darkening effect to the color used in the divider
[16:10] <Saviq> Cimi, a darkening effect to black?
[16:10] <Cimi> Saviq, there is a whitening effect at the bottom though
[16:11] <Saviq> Cimi, Joshua looked at https://drive.google.com/drive/#folders/0B32jwBcbaPloR1IyRF91ZWs0bFE, approved how the divider looks
[16:11] <Cimi> definitely not white though
[16:11] <Cimi> this image is a mess
[16:11] <Cimi> how can you share a jpg?
[16:11] <Cimi> that compresses colors?
[16:12] <Saviq> Cimi, regardless, I really did ask
[16:12] <Saviq> Cimi, explicitly
[16:12] <Saviq> Cimi, it's supposed to be flat
[16:12] <Saviq> if you want to challenge that design, you know where to go
[16:12] <Saviq> Cimi, but please don't do it on this branch
[16:13] <Cimi> Saviq, ack, will chase jouni soon
[16:13] <Saviq> Cimi, don't chase Jouni, chase Esti and Josh, Jouni has nothing to do with those designs
[16:13] <Cimi> Saviq, he is lead visual
[16:14] <Cimi> Saviq, and he is theming sdk, which is supposed to be consistent with shell
[16:14] <Cimi> so I will ask them to agree on which style to go: flat or little highlight
[16:14] <Saviq> Cimi, either case, you know where to find them
[16:14] <Cimi> I personally like flat
[16:14] <kgunn_> Cimi, how about this...can you file a bug? they've been good about addressing
[16:15] <kgunn_> this way we can keep on movin' for the day
[16:15] <Cimi> kgunn_, let me try sorting this out with design
[16:15] <AlbertA2> kdub: so I guess this should address the halt seen in the spinner? https://code.launchpad.net/~kdub/mir/fix-1352883/+merge/229804
[16:15] <AlbertA2> that's not in 0.6.0 right?
[16:17] <kdub> AlbertA, oh yeah, probably
[16:17] <kdub> let me check where it is...
[16:18] <kgunn_> kdub, AlbertA2 nope doesn't appear to be
[16:18] <Cimi> Saviq, kgunn_ we'll know tomorrow morning
[16:18] <kgunn_> on 0.6
[16:19] <Cimi> Saviq, kgunn_ but yes they are aware esti was doing some flat design
[16:19] <AlbertA2> ok I'll do a quick test to see if it fixes it
[16:19] <kdub> AlbertA, yeah, should catch the 0.7 train
[16:19] <kdub> if its an intermittent lock up that will continue after a second or two, its most likely the same thing
[16:20] <kdub> oh, and occurs around surface reordering
[16:24] <Cimi> Saviq, scopes scope in header customization has weird colors
[16:24] <Cimi> Saviq, header is white on white
[16:24] <Saviq> Cimi, scopes scope?
[16:24] <Cimi> Saviq, in unity8-dash, maybe is a mock
[16:24] <Saviq> Cimi, in unity8-dash is probably not a mock, but where?
[16:25] <Saviq> Cimi, also, I just pushed a rework of that logic
[16:25] <Cimi> Saviq, one of the last scopes
[16:25] <Cimi> Saviq, anyway tomorrow I'll catch up with them
[16:25] <Saviq> Cimi, how are you running it?
[16:25] <Cimi> Saviq, from builddir
[16:25] <Cimi> ./src/Dash/unity8-dash
[16:26] <Saviq> Cimi, yeah, that's overview
[16:26] <Cimi> Saviq, we can purge it from the mock then
[16:26] <Saviq> Cimi, no, that's a real scope, there's no mocks
[16:26] <Cimi> ah
[16:26] <Saviq> Cimi, but you can only access it from bottom swipe IRL
[16:26] <Saviq> start unity8-dash BINARY=$PWD/builddir/src/Dash/unity8-dash ARGS=-mousetouch
[16:26] <Cimi> Saviq, I meant from this fake utility
[16:27] <Saviq> Cimi, still, that should be fixed in unity-scopes-shell, but won't affect real usage
[16:27] <Cimi> I know it doesn't
[16:27] <Cimi> I was just saying about this issue
[16:27] <Cimi> in case is was due to a not covered case
[16:27] <Saviq> Cimi, yeah, the scope doesn't send an explicit background
[16:28] <Cimi> Saviq, we should not force to set both foreground/bg?
[16:28] <Saviq> Cimi, we are
[16:28] <Saviq> Cimi, in real life, in overview
[16:29] <Saviq> Cimi, it will never show up in the dash like you see it there
[16:29] <Cimi> I understood that
[16:29] <Cimi> I was just wondering if we can have broken scopes
[16:29] <Cimi> which have same styling options of the scopes scope
[16:29] <Saviq> Cimi, sure we can
[16:30] <Saviq> Cimi, if they don't send a proper configuration
[16:30] <Saviq> Cimi, but how's that our problem?
[16:30] <Cimi> Saviq, and whether we should apply header customisation only when both bg and fg are set
[16:31] <Cimi> like, ok you developer, if you provided both fg and bg means you actually tested they work fine
[16:31] <Cimi> and might keep them independent to theme changes
[16:31] <Saviq> Cimi, you are a developer, you developed a scope, means you actually tested they work fine
[16:31] <Cimi> in case one day we tweak the fg or bg colour
[16:32] <Cimi> but if one day we decide to turn the dash dark, and developers just set bg or fg (not both), scopes header might be broken
[16:33] <Saviq> Cimi, that's why if they override one, they will override the other
[16:33] <Saviq> Cimi, we really don't need to hand-hold them, it's enough to document
[16:33] <Cimi> fine
[16:33] <Cimi> anyway I was just picky now
[16:33] <Cimi> rest seems fine, I quite like it flat
[16:34] <Cimi> but we need to wait tomorrow morning for jouni to catch up with esti
[16:34] <Cimi> I'll review the rest
[16:34] <Saviq> Cimi, you could say that about changing just the foreground color, if you don't set a background and we change it, you're screwed
[16:35] <Cimi> yeah
[16:35] <Cimi> I was thinking we should allow customisation only when both are set
[16:36] <Cimi> when I was doing themes, 95% of times I was picking up a different bg or fg I had to change the other one, accordingly
[16:36] <Saviq> Cimi, but it wasn't enforced
[16:37] <Cimi> so it will keep the contrast bg/fg balanced
[16:37] <Cimi> with the rest of the ui
[16:37] <Cimi> with forcing developers to set both, is like saying "you set a new bg, now please find the right fg for that"
[16:38] <Cimi> it's a more complete customisation work
[16:38] <Saviq> Cimi, yes, but in your 'when I was doing themes', were you ever forced to set them both?
[16:39] <Cimi> Saviq, nope, but it looked better if I did
[16:39] <Cimi> and that is entirely my point
[16:39] <Cimi> forcing devs to pick up the perfect match
[16:39] <Saviq> Cimi, sure, let's do that when we can actually afford the time to have that discussion
[16:41] <Cimi> and also before criticising devs, we should look at what we do
[16:41] <Cimi> everytime I see a button in ubuntu, white text on light grey, I want to cry
[16:42] <Saviq> Cimi, who said anything about criticizing devs?
[16:42] <Cimi> if you really want to do white on grey, add a subtle inset shadow to the text to increase contrast/sharpness
[16:42] <Cimi> i was
[16:42] <Cimi> potential scope devs
[16:42] <Saviq> Cimi, you wanna cry? check bug #1356866 out
[16:42] <Saviq> Cimi, and bug #1356864
[16:42] <Cimi> I'll leave them for tomorrow
[16:43] <Cimi> Saviq, you were trying them for dash overview?
[16:43] <Saviq> Cimi, yeah
[16:44] <Cimi> Saviq, also text size changes, and border
[16:44] <Cimi> when you press
[16:44] <Cimi> at least trying in indicator polishing branch for settings components
[16:44] <Saviq> Cimi, http://i.imgur.com/pI50Ai2.png
[16:44] <Cimi> :')
[16:45] <Cimi> I need some napkins
[16:45] <Saviq> Cimi, I don't think it changes size, but it does change color... from grey to white, regardless of stroke color :|
[16:45] <Cimi> Saviq, it changes size if you rpess
[16:46] <Saviq> Cimi, yeah maybe
[16:46] <Saviq> my eyes are glued up whole day today
[16:46] <Saviq> Cimi, the last push I made made the extreme usecase in tryDash work better
[16:47] <Saviq> Cimi, started selecting the more contrasting color of the two, not just "a contrasting" one
[16:47] <Saviq> Cimi, i.e. https://docs.google.com/a/canonical.com/file/d/0B32jwBcbaPloM3JlVlF2NXJDVmM/edit
[16:47] <Saviq> Cimi, before it would select the grey, because it's lighter than black after all ;)
[16:47] <Cimi> Saviq, what happens to the second scope? :)
[16:48] <Cimi> in trydash
[16:48] <Saviq> Cimi, it's beautiful, whaddya want?
[16:48] <Cimi> hah
[16:48] <Cimi> Saviq, yes we should not force devs to set both fg and bg
[16:50] <cwayne> you cant force me to do anything! ill set my fg and bg both to black if i want!
[16:50] <mhall119> Saviq: pete-woods: where does cout go to from a scope? unity8-dash.log, scope-registry.log or somewhere else?
[16:50] <cwayne> scope-registry
[16:50] <cwayne> i think
[16:51] <pete-woods> mhall119: I think you need to do cerr. I think cout might be swallowed
[16:51] <pete-woods> but the log is in ~/.cache/upstart/scoperegistry.log
[16:52] <Saviq> mhall119, should be in scope-registry, yeah
[16:52] <Saviq> mhall119, unless as pete-woods says, registry swallows cout
[16:52] <mhall119> pete-woods: ok, I'll try that, thanks
[17:04] <smallfoot-> Last time you updated Unity un Utopic you introduced a regression in Compiz
[17:04] <smallfoot-> https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1356981
[17:09] <Cimi> Saviq, commented https://code.launchpad.net/~saviq/unity8/header-customizations/+merge/230719/comments/561079 for now
[17:10] <Saviq> Cimi, thanks
[17:30] <greyback__> mterry: ping
[17:31] <mterry> greyback__, heyo
[17:31] <greyback__> mterry: hey there, I was looking into bug 1353041
[17:32] <greyback__> mterry: which I have tracked down to inside tests/mocks/LightDM/demo/GreeterPrivate.cpp:158
[17:32] <greyback__> you are waiting for a QFuture to return a value
[17:32] <mterry> Interesting... OK
[17:32] <greyback__> that blocks shutdown on the desktop though
[17:33] <mterry> greyback__, right, that would be us in the middle of our PAM conversation
[17:33] <mterry> greyback__, hm
[17:33] <greyback__> I'm not very savvy with Futures, so I'm learning as I go, but I guess a way to cancel or force a future to return would do
[17:34] <mterry> greyback__, well we use QtConcurrent::run which I don't think can be cancelled
[17:34] <mterry> greyback__, but we can force PAM to end its converstaion
[17:35] <mterry> greyback__, perhaps with a pam_end call or feeding it blank password answers just to get through the PAM conversation
[17:35] <greyback__> mterry: mind if I leave the bug with you? It's a sharp learning curve
[17:37] <mterry> greyback__, OK.  What's the easiest way to test?
[17:37] <greyback__> mterry: I do what the bug report said. unity8 on desktop, log in,  then log out. It hangs on log out
[17:38] <mterry> greyback__, I was hoping there was an easier way  :)
[17:38] <greyback__> latest unity8 I wasn't able to get past a "hello" dialog
[17:38] <greyback__> mterry: I'd recommend a secondary machine
[17:38] <greyback__> mterry: I'm happy to test anything you come up with...
[17:38] <mterry> greyback__, I'm not made of desktops!  I am made of phones at this point though..  ;)
[17:39] <greyback__> mterry: pah, call yourself a geek
[17:39] <greyback__> :D
[17:39] <greyback__>             while (respond(QString())); // clear our local queue of QFutures
[17:40] <greyback__> calling that in a deconstructor - would that work?
[17:40] <mterry> greyback__, yeah probably
[17:40] <greyback__> trying...
[17:44] <dandrader> tedg, ping
[17:45] <cwayne> man oh man am I excited for this next landing
[17:45] <greyback__> mterry: that appeared to work
[17:46] <mterry> greyback__, yay!
[17:49] <mterry> greyback__, it would probably be cleaner to cancel QtConcurrent::run and just call pam_end.  But we can't cancel that run.  So we'd have to use a more complicated concurrent method
[17:49] <greyback__> ChrisTownsend: with u8 on desktop, when you logged out, do you get back to the lightdm greeter?
[17:49] <mterry> greyback__, maybe mention that as a TODO
[17:50] <ChrisTownsend> greyback__: When it was working before, it did.
[17:51] <greyback__> ChrisTownsend: hmm okay. I have a hack to stop the hang on logout, but it logged back out to the u8 greeter. Not sure why
[17:52] <ChrisTownsend> greyback__: Is the u8 greeter the screen with the dial looking thing in it?
[17:52] <greyback__> ChrisTownsend: yep
[17:52] <ChrisTownsend> greyback__: Also, I think some changes when in recently that may affect this, but I'm not sure.  As of today, when I log in, it goes to the lockscreen and I can't do anything else.
[17:53] <ChrisTownsend> greyback__: Ok
[17:53] <greyback__> according to the logs, u8 does totally shut down and something restarts it
[17:53] <ChrisTownsend> greyback__: Hmm, the hang may just be a layer to the onion.
[17:54] <ChrisTownsend> greyback__: Recent changes in the upstart handling may also affect this as well.
[17:54] <ChrisTownsend> greyback__: But that couldn't be tested due to the hang.
[17:54] <greyback__> ChrisTownsend: I don't understand much of how log in/out works unfortunately
[17:55] <ChrisTownsend> greyback__: Ok ,well sounds like one issue is knocked out.
[17:55] <greyback__> ChrisTownsend: I'll propse the fix later/tomorrow
[17:55] <ChrisTownsend> greyback__: Cool.
[17:55] <ChrisTownsend> greyback__: Thanks!
[17:56] <greyback__> ChrisTownsend: no worries. BTW can you log in to the most recent u8? When I started it, I got a "Hello" dialog with a text box, and had no idea what to do
[17:56] <greyback__> that was after lighdm log in
[17:56] <ChrisTownsend> greyback__: Yep, I get that issue now too.  I filed a bug.
[17:57] <ChrisTownsend> greyback__: https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1356902
[17:57] <greyback__> ChrisTownsend: ok cool. I had to rewind to before 1150 to get a way to reprouce your original bug
[17:58] <ChrisTownsend> greyback__: Somebody marked it as a dup already, so I'm guessing it's a known issue.  Although I think the dup is a bit different issue.
[17:58] <ChrisTownsend> greyback__: I guessed 1150 causes the new issue.
[17:58] <ChrisTownsend> greyback__: mterrry marked it as a dup, so maybe he's on top of it?
[17:59] <ChrisTownsend> Errr, mterry did.
[17:59] <greyback__> I'd say so
[17:59] <mterry> ChrisTownsend, I'm not actively working on it, but I'm aware of it
[18:00] <mterry> ChrisTownsend, it sounded like a dup.  But if you thought it was different, maybe my quick read of the bug was wrong
[18:00] <ChrisTownsend> mterry: Eww, can't use the desktop at all now.
[18:00] <ChrisTownsend> mterry: I think it may be related, but in my case, caused by r1150.
[18:01] <ChrisTownsend> mterry: I didn't have the issue until the latest unity8 update.
[18:02] <mterry> ChrisTownsend, OK interesting
[18:03] <mterry> ChrisTownsend, before 1150, did you actually see a login screen and such?
[18:03] <ChrisTownsend> mterry: Only briefly and then it would automatically go to the Dash.
[18:04] <ChrisTownsend> mterry: Now it's just the lockscreen with no way out.  Indicators don't work or anything.
[18:05] <ChrisTownsend> mterry: I call it the Hello Box o' Doom:)
[18:10] <mterry> ChrisTownsend, indicators not working (visible but can't pull them down) is expected when locke
[18:10] <ChrisTownsend> mterry: Ok, that makes sense.
[18:11] <mterry> ChrisTownsend, sounds like you are hitting one aspect of the bug that I marked yours as a dup-of.  It started getting worse for you from 1150 because I closed a loophole in the logic that let you not experience the other bug so bad (that's what I'm thinking anyway, without looking into it)
[18:12] <ChrisTownsend> mterry: Ok, that sounds reasonable.  I thought they might be related, but since my issue just started, I wasn't sure, so I opened the new bug.
[18:13] <ChrisTownsend> mterry: Hopefully, a resolution can be found soon-ish as the u8 desktop is unusable in this state- that is unless you know a workaround like what magic code to enter in the Hello box or some way to dismiss it or something.
[18:16] <mterry> ChrisTownsend, nope!
[18:16] <mterry> ChrisTownsend, I know and I'm sorry.  I've just been too busy with phone stuff
[18:17] <ChrisTownsend> mterry: Ok, that's what I thought.  And I understand you are busy with phone stuff and it has a higher prio.  Just hoping:)
[18:17] <ChrisTownsend> mterry: Thanks
[18:18] <mterry> ChrisTownsend, no worries, hopefully I can get your desktop back to you before too long
[18:19] <mterry> :)
[18:19] <ChrisTownsend> mterry: I'll keep my fingers crossed