[07:08] <Saviq> tsdgeos, re-ack https://code.launchpad.net/~lukas-kde/unity8/fix-window-title-vs-menu/+merge/319975 please?
[07:09] <Saviq> there's two commits fixing the tests after your ACK
[07:09]  * tsdgeos clicks
[07:09] <Saviq> mzanetti, https://code.launchpad.net/~lukas-kde/unity8/fix-windows-behind-unmaximize-transition/+merge/321440 is ready for re-review please
[08:03] <mzanetti> kk
[08:21] <awh> Hey folks. Will Unity 8 still use compiz? If not, will there be some similar alternative mechanism for making plugins for it?
[08:31] <mzanetti> Saviq: fwiw, this is done: https://code.launchpad.net/~mzanetti/unity8/appdrawer-recent-apps/+merge/319697
[08:32] <mzanetti> Saviq: just putting together a silo to get a green ci run
[08:32] <mzanetti> awh: no compiz any more and so far no plugin system for effects...
[08:32] <Saviq> mzanetti, ack, should we just plug into our current silo?
[08:32] <mzanetti> if you want, it's not reviewed yet, so a bit of risk involved there
[08:35] <awh> mzanetti: I'm currently making a compiz plugin that facilitates window nav with they keyboard for touch typists, so it's not effects based. Do you envision Unity8 will facilitate plugging in such functionality at some point in the future?
[08:35] <mzanetti> awh: unlikely
[08:38] <Saviq> mzanetti, ok, let's leave it out and have a follow-up silo
[08:38] <mzanetti> kk
[08:40] <awh> mzanetti: Hmm, that's a shame. Would you accep third party contributions that added such functionality?
[08:40] <mzanetti> I would think yes, but this is not a trivial task...
[08:41] <awh> Surely it is not, I agree :)
[08:41] <awh> What about just contributing the navigation mechanism as a direct patch?
[08:42] <awh> If that isn't going to fly, I would have to maintain a fork
[08:43] <awh> Which is super-unappealing
[08:43] <mzanetti> I didn't really understand what exactly this keyboard navigation does... But in general we do accept 3rd party contributions if they don't break things, are well tested and don't interfere with the design vision of unity8
[08:44] <awh> That sounds promising, thanks. Are you familiar with the vimfx browser plugin by any chance?
[08:44] <awh> I'm making something that allows you to change window focus using the same method vimfx uses for navigating to links
[08:45] <awh> Essentially you press a hotkey, and every visible window is overlayed with a letter (preferring home-row keys - a, s, d etc); pressing that key focuses that window
[08:47] <mzanetti> ah ok, yes, I've seen such a thing on KDE iirc
[08:47] <awh> This is quite easily achieved with a compiz plugin that does not interfere with the existing unity7 plugin
[08:51] <awh> Really looking forward to trying Unity 8 - any thoughts on when it's going to be generally available using the nvidia driver?
[08:52] <mzanetti> I guess this could be achieved rather easily in unity8 by adding such a keyboard handler to the spread... i.e. one presses Super+W to go to spread and then just starts typing the letters and filters down the items in the spread with that
[08:53] <mzanetti> can't say much about the nvidia driver support.. maybe try asking in #ubuntu-mir for that
[08:53] <mzanetti> I did have it running here on noveau, not perfectly but it did run
[08:54]  * awh nods
[08:54] <awh> Thanks!
[09:24] <mzanetti> tsdgeos: hey, I just had my design weekly with vesa, talked about the drawer. He's ok with how I described it, but mind sending a screenshot so he can look at it?
[09:28] <tsdgeos> sure
[09:30] <tsdgeos> mzanetti: http://i.imgur.com/qKcnFZr.png
[09:30] <tsdgeos> vesar: ↑↑
[09:30] <mzanetti> ta
[09:30] <tsdgeos> fwiw lukas wasn't very happy with the blue outline
[09:33] <dandrader> agree that blue outline doesn't look good
[09:33] <vesar> thanks! I think as well that the blue outline might be something that our visual team would have different opinion as well
[09:34] <vesar> could we just drop it?
[09:35] <vesar> lately we've tried not overuse colors and this is one example when it's not really needed
[09:35] <vesar> otherwise I'm very pleased to see this implementation. Good improvement!!
[09:45] <Saviq> tsdgeos, mzanetti, can we just drop the outline, then ↑
[09:45] <tsdgeos> Saviq: no
[09:45] <tsdgeos> without the outline it looks awful
[09:46] <tsdgeos> because it's black on black
[09:46] <mzanetti> yeah... I would have thought no outline, just the whole background in a "highlight" color
[09:46] <mzanetti> whether that's blue or orange, I don't properly understand the palette tbh
[09:46] <Saviq> the blue is too bright
[09:46] <Saviq> to be a background
[09:48] <Saviq> tsdgeos, could you show a few options please? no outline, light grey or some such? also with keyboard navigation highlight?
[09:48] <tsdgeos> Saviq: vesar: http://i.imgur.com/NlBTR8k.jpg without outline
[09:49] <tsdgeos> Saviq: isn't keyboard navigation blue'
[09:49] <tsdgeos> ?
[09:49] <mzanetti> yes
[09:49] <mzanetti> that's why I say blue...
[09:49] <mzanetti> because it's the color for "highlighted/active"
[09:50] <mzanetti> but yes, I agree it's too much for the complete background
[09:53] <Saviq> tsdgeos, btw, it should be shown on keyboard highlight, too, I think? that would clash with the blue focus outline, so we shouldn't use that, but I'm thinking one of the light greys
[09:54] <Saviq> Silk or Ash from https://design.canonical.com/2016/05/colour-palette-updates/
[09:55] <tsdgeos> silk http://i.imgur.com/j8JgsHk.jpg
[09:56] <tsdgeos> i'm only showing the expanded text on hover, but i guess it makes sense to do what you said and show it on keyboard nav too
[09:58] <tsdgeos> so blue, nothing or ash?
[09:58] <Saviq> tsdgeos, silk looks too bright
[09:58] <Saviq> can you try ash?
[09:59] <Saviq> and show how it would look along with keyboard highlight?
[10:01] <tsdgeos> ash http://i.imgur.com/LuX41mQ.jpg
[10:02] <tsdgeos> ash + keyboard http://i.imgur.com/BbIDY6w.png
[10:03] <Saviq> and we lost vesa ;P
[10:03] <Saviq> ughies, that's too close :/
[10:05] <tsdgeos> a bit, yeah
[10:05] <tsdgeos> so either
[10:05] <tsdgeos> we can say "it's a bit too close but whatever"
[10:06] <tsdgeos> or i don't expand the text on keyboard navigation
[10:06] <tsdgeos> only on mouse hover like now and it's "less bad"
[10:06] <tsdgeos> but still a bit useless
[10:07] <Saviq> yeah, when navigating with a keyboard you need the full name, too
[10:09] <ltinkl> Saviq, tsdgeos: it would imo look much nicer with the 2 highlights being the same (blue  -> ash, and thinner)
[10:09] <Saviq> not sure, it's weird to have two items outlined like this
[10:10] <Saviq> I think I'd actually go for the one without outline
[10:10] <Saviq> so http://i.imgur.com/NlBTR8k.jpg
[10:10] <Saviq> the blue keyboard outline wouldn't clash with that
[10:11] <tsdgeos> both blue https://i.imgur.com/Iq2yYeO.jpg
[10:11] <Saviq> no, that's bad - tsdgeos IMO let's go with no outline for the full label
[10:12] <Saviq> tsdgeos, also, make the full label limited in width (2x icon width?) and elided after 3 lines
[10:12] <tsdgeos> Saviq: so i throw away all the code
[10:12] <tsdgeos> ok
[10:13] <Saviq> tsdgeos, sorry, I did say straight away that it shouldn't just be "as wide as the text is", must've gotten lost in translation
[10:13] <Saviq> if an app name doesn't fit in 3 lines of text, it's not our fault
[10:13] <tsdgeos> yes it is
[10:13] <tsdgeos> it is us that are choosing this very restricted way of showing the app name
[10:14] <tsdgeos> you mean "if the app name doesn't fit in 3 lines we're fine with that"
[10:14] <Saviq> no, I'm saying the app name needs to be fixed
[10:14] <tsdgeos> because unity8 is always right! (TM)
[10:14] <tsdgeos> Saviq: anyway limiting the width is not going to work
[10:15] <Saviq> someone has to be
[10:15] <tsdgeos> see http://i.imgur.com/8qHm1V1.jpg
[10:15] <tsdgeos> you want to see
[10:15] <tsdgeos> Controladors Addic
[10:15] <tsdgeos> ionals
[10:15] <tsdgeos> ?
[10:15] <tsdgeos> noone wants to see that
[10:15] <Saviq> tsdgeos, word wrap
[10:15] <Saviq> or well, the elastic one that tries on words and fall backs to forced rwap
[10:16] <tsdgeos> so
[10:16] <tsdgeos> Controladors Addic
[10:16] <tsdgeos> ionals
[10:16] <tsdgeos> that is what you get with the elastic one
[10:16] <Saviq> why wouldn't it be
[10:16] <Saviq> Controladors
[10:16] <Saviq> Addicionals
[10:16] <Saviq>  ?
[10:16] <ltinkl> qml is stupid in word wrapping sometimes
[10:17] <tsdgeos> i guess it may be that
[10:17] <tsdgeos> but then suddenlty your 3 lines of text are very few space
[10:17] <tsdgeos> anyhow i shall stop arguing and do as instructed
[10:18] <tsdgeos> when is the deadline for this ?
[10:19] <mzanetti> I didn't follow the whole discussion, but we can't change the keyboard navigation ring to something else than the blue...
[10:19] <Saviq> tsdgeos, ltinkl, http://pastebin.ubuntu.com/24312576/
[10:20] <Saviq> mzanetti, not planning to, no
[10:21] <Saviq> tsdgeos, ltinkl, resize that, IMO it behaves exactly like we want it to?
[10:22] <ltinkl> Saviq, depends on the width of the qmlscene window; it does break correctly but if I shrink it some more, it breaks at random places in the middle of words
[10:22] <Saviq> ltinkl, that is how Text.Wrap is defined
[10:22] <Saviq> and that is what we want
[10:23] <ltinkl> Saviq, yeah I know, but it's wrong :) nobody wants to see "Controlad - ors - Addicional - s"
[10:23] <Saviq> ltinkl, and we won't
[10:23] <Saviq> unless the word is crazy long
[10:23] <ltinkl> Saviq, I want to see a German name there ;)
[10:24] <Saviq> if you have an idea how to make it "as wide as the longest word, no less than 2×icon.width", I'm fine with that
[10:24] <ltinkl> Saviq, something that's 25+ letters in one word
[10:24] <Saviq> ltinkl, I proposed the width to be 2×icon, was probably thinking more like 2×default label width
[10:24] <Saviq> that would be more than 25+ letters
[10:25] <ltinkl> Saviq, I suppose we don't want another elision in the extended label, do we?
[10:26] <Saviq> ltinkl, I proposed 3 lines, if there's more text than that in an app name, I'm not really willing to accept that
[10:26] <Saviq> that'd be probably 100 or so letters in an app name
[10:27] <Saviq> so yes, elide in that case
[10:27] <Saviq> because the alternative is worse
[10:28] <tsdgeos> Saviq: 2x the delegatewidth or the icon width?
[10:29] <Saviq> tsdgeos, deleaget
[11:29] <tsdgeos> Saviq: ok, so updated https://code.launchpad.net/~aacid/unity8/spacier_drawer/+merge/321720
[11:29] <tsdgeos> ltinkl: you'll have to re-review
[11:29] <ltinkl> tsdgeos, kk, I will
[11:29] <Saviq> tsdgeos, thanks, rebuilding the silo
[11:30] <Saviq> tsdgeos, does it wrap good in the end?
[11:31] <tsdgeos> yeah, i guess 20gu is wide enough
[11:32] <Saviq> ack, glad
[13:01] <boiko> hi guys, unity8 autopkgtests failed on xenial/i386 for a silo that contains changes for telephony-service, but it doesn't really look like a real failure:
[13:01] <boiko> https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-xenial-ci-train-ppa-service-2629/xenial/i386/u/unity8/20170403_185700_c0929@/log.gz
[13:01] <boiko> is it by any chance known already?
[14:29] <mzanetti> ltinkl: Saviq: https://code.launchpad.net/~mzanetti/unity8/fix-focus-on-app-launch/+merge/321868