[08:36] <Cimi> Saviq, before you needfix me
[08:37] <Cimi> Saviq, in the infographics, I need to get the user id
[08:37] <Cimi> uid
[08:38] <Cimi> so I did this http://paste.ubuntu.com/7420297/
[08:39] <Cimi> is not super nice as using a model role, otherwise we have to patch lightdm
[08:49] <dednick> anyone know how to set the display to "always on" on device? can't seem to get powerd-cli to do it...
[08:58] <mhr3> dednick, you get something like https://www.youtube.com/watch?v=Z86V_ICUCD4
[08:58] <mhr3> but instead it just taps on your phone regularly
[08:59] <dednick> mhr3: lol
[09:06] <Saviq> Cimi, better let's patch lightdm
[09:06] <Cimi> ahahahahahha
[09:06] <Cimi> I know it!!!
[09:06] <Saviq> Cimi, especially since we only use a local copy of the LightDM plugin still ;)
[09:06] <Cimi> Saviq, but we need to patch real lightdm
[09:06] <Saviq> Cimi, until the split greeter
[09:06] <Saviq> Cimi, sure, I know, let's
[09:07] <seb128> Saviq, hey
[09:07] <seb128> Saviq, https://blueprints.launchpad.net/ubuntu/+spec/client-1410-unity8-desktop-iso just as fyi
[09:07] <Saviq> "by 16.04", not "for 16.04" ;)
[09:08] <Saviq> subscribed
[09:13] <Saviq> dednick, "sync item progress" is different than "transfer" is it?
[09:16] <dednick> Saviq: hmm. not sure exactly. I know there is an "indicator-sync"
[09:16] <dednick> Saviq: https://launchpad.net/indicator-sync
[09:16] <dednick> and an https://launchpad.net/indicator-transfer
[09:16] <Saviq> dednick, ok, I'll leave it be then
[09:16] <dednick> Saviq: but the sync one is pretty old.
[09:17] <Saviq> dednick, kk
[09:17] <dednick> so they may have been merged
[09:17] <Saviq> dednick, I'll leave it be then, we'll adapt when we know more
[09:17] <dednick> ok
[09:19] <seb128> Saviq, "by" indeed, thanks ;-)
[09:19] <seb128> (fixed)
[09:30] <Saviq> Cimi, we're to tell Loïc what are our biggest beefs with the shape, apparently the new implementation is too far off still...
[09:30] <Cimi> Saviq, far off?
[09:31] <Cimi> Saviq, like we're not getting things?
[09:31] <Saviq> Cimi, incomplete still
[09:31] <Cimi> Saviq, what are we getting?
[09:31] <Saviq> Cimi, we need to list things we need to see what can be backported
[09:31] <Cimi> I talked to kevin
[09:31] <Cimi> hold on, logs
[09:31] <Saviq> Cimi, I know about:
[09:32] <Cimi> 1) ability to add any item inside and let ubuntushape clip it
[09:32] <Cimi> 2) enable/disable inner shadows and border
[09:32] <Cimi> 3) add external shado
[09:32] <Cimi> 4) peformance improvements and caching
[09:32] <Saviq> overlay support
[09:32] <Cimi> Saviq, overlay support should fall into 1
[09:32] <Saviq> Cimi, 1) is possible via a ShaderEffectSource
[09:33] <Saviq> Cimi, we're actually using it here and there
[09:33] <Saviq> ;)
[09:33] <Cimi> Saviq, yes
[09:34] <Cimi> Saviq, in Components
[09:34] <Saviq> now that I think of it, we should use it more
[09:34] <Cimi> Saviq, but we want it integrated
[09:34] <Saviq> Cimi, yeah sure, but I don't think that's a prio then, since there's a workaround
[09:34] <Cimi> Saviq, so 2 and 3 though
[09:34] <Cimi> Saviq, or more generally, ability to change border source
[09:35] <Cimi> sometyhing like that
[09:35] <Saviq> Cimi, don't we have that already?
[09:35] <Saviq> Cimi, borderSource?
[09:35] <Cimi> having always the inner shadow sucks
[09:35] <Cimi> Saviq, we had
[09:35] <Cimi> Saviq, now doesn't work anymore iirc
[09:35] <Cimi> since a year or a bit less
[09:37] <Saviq> Cimi, think it's still working, we use it in launcher and running tile
[09:37] <Cimi> Saviq, where?
[09:37] <Saviq> Cimi, grep for borderSource
[09:38] <Cimi> Saviq, those refers to prefixed border sources in the sdk
[09:39] <Cimi> Saviq, you cannot set to null
[09:39] <Cimi> or anything you like
[09:39] <Saviq> Cimi, well, it's set to "none" in LauncherDelegate, but sure, we can't override
[09:40] <Cimi> Saviq, http://paste.ubuntu.com/7420521/
[09:41] <Cimi> Saviq, I wrote that code
[09:41] <Cimi> in launcherdelegate :)
[09:42] <Cimi> Saviq, I remember when I did borderSource: "CimiDoesntWantBorder"
[09:42] <Cimi> someone needsfix that :D
[09:43] <Cimi> maybe I can use it for the carousel... let's see
[09:52] <greyback> any volunteers? https://code.launchpad.net/~gerboland/unity-mir/fix-upstart-closed-apps2/+merge/218721
[09:53] <greyback> for functional testing at the least
[10:02] <Saviq> greyback, I'll take it
[10:02] <greyback> Saviq: thanks
[10:25] <Cimi> Saviq, came up with something like that for lightdm http://paste.ubuntu.com/7420699/
[10:26] <Cimi> Saviq, how to I cast from a uid_t to guint64 in qt? is my approach correct?
[10:26] <Cimi> +            user.uid = (quint64)lightdm_user_get_uid(ldmUser);
[10:27] <Saviq> Cimi, looks legit
[10:27] <Cimi> ok
[10:27] <Saviq> Cimi, although mterry will obviously be better to review
[10:28] <Saviq> Cimi, is there nowhere you can get the uid from lightdm instead of getpwnam?
[10:28] <Cimi> Saviq, that is a mistake
[10:28] <Cimi> Saviq, that function is not called
[10:29] <Cimi> I am using lightdm for the model
[10:29] <Cimi> indeed
[10:29] <Saviq> Cimi, right
[10:29] <Cimi> I discovered lightdm already stored the uid
[10:29] <Cimi> after I added the function
[10:29] <Saviq> Cimi, yeah, looks legit, MP please and get mterry to review
[10:30] <Cimi> http://paste.ubuntu.com/7420719/
[10:30] <Cimi> ok
[10:30] <Cimi> I'll wait a jenkins build
[10:32] <seb128> Saviq, just saw https://blueprints.launchpad.net/ubuntu/+spec/client-1410-suru-icon-switch
[10:32] <seb128> Saviq, I've https://code.launchpad.net/~seb128/ubuntu-system-settings/use-theme-icons/+merge/214950 up but it's blocked on your uitk change to land
[10:32] <seb128> Saviq, just as a fyi
[10:33] <seb128> cyphermox, ^ (since you have the W.I on that blueprint)
[10:33] <Saviq> seb128, link them?
[10:34] <seb128> Saviq, done
[10:34] <seb128> cyphermox, took over your WI as well, set it as done
[11:13] <Cimi> Saviq, https://code.launchpad.net/~cimi/unity8/preview-text-summary-bottom-padding/+merge/217903
[11:13] <Saviq> Cimi, yup, will do it soon
[11:18] <Cimi> pete-woods, hey, are those SVGs animated?
[11:18] <pete-woods> Cimi: nope, just boring ol SVGs
[11:18] <Saviq> Cimi, animated SVGs are security nightmare
[11:18] <Saviq> Cimi, since you need to support javascript
[11:19] <Cimi> Saviq, so why we switched to use SVG?
[11:19] <Saviq> Cimi, because we want to adapt the colours
[11:19] <Cimi> Saviq, and you can do it other ways with properties
[11:19] <Saviq> Cimi, and we switched to SVG to allow easier visualizers than QML
[11:19] <Saviq> Cimi, and again, custom QML → security nightmare
[11:20] <Cimi> Saviq, properties
[11:20] <Cimi> anyway ok
[11:20] <Saviq> Cimi, properties what?
[11:20] <Cimi> I will tell designers anymations are gone
[11:20] <Cimi> Saviq, you can expose colors
[11:20] <Cimi> Saviq, like we do with the ubuntu themes
[11:21] <Saviq> Cimi, expose them to what? to SVGs? yes, that's what we want to do
[11:22] <Saviq> Cimi, but we didn't want to run any javascript (so animated SVGs and/or QML are not good)
[11:24] <Cimi> Saviq, we could have exposed other properties from a text file
[11:24] <Cimi> or anything really
[11:24] <Cimi> and use animated qml
[11:24] <Cimi> if we want just to change colours...
[11:25] <Cimi> if we want to change shapes, it's fine
[11:26] <Saviq> Cimi, NO ANIMATED QML
[11:26] <Saviq> Cimi, security BAD
[11:26] <Saviq> Cimi, and we didn't even want animated anyway
[11:26] <Cimi> why bad?
[11:26] <Saviq> Cimi, security
[11:26] <Cimi> our shell is animated
[11:27] <Cimi> our apps are animated
[11:27] <Cimi> now is insecure?
[11:27] <Saviq> Cimi, 3rd party infographics in the shell
[11:27] <Cimi> ah 3rd party ok
[11:27] <Saviq> Cimi, and anyway they're meant to be really as non-intrusive as possible
[11:27] <Cimi> thought we were drawing the infographics
[11:27] <Saviq> Cimi, so animation is not wanted
[11:27] <Cimi> and give develelopers a couple of values to change
[11:27] <Saviq> Cimi, nope, we want them to be installable as clicks and such
[12:18] <mhr3> Saviq, seen the design on departments behaviour yet?
[12:19] <Saviq> mhr3, you mean https://sites.google.com/a/canonical.com/unity8dash/toolkit/2-navigation ?
[12:19] <Saviq> mhr3, see bottom for my comments
[12:20] <mhr3> indeed
[12:21] <mhr3> Saviq, i'm interested in that from the model pov, i'll have to expose some kind of partial lazily loaded tree
[12:21] <mhr3> the widget for that will be... interesting i guess
[12:21] <Saviq> aaaargh foooking gsites
[12:21] <Saviq> limited characters in comments... what is this, 1990s?
[12:23] <Saviq> mhr3, since any change is meant to be applied instantly (it is, isn't it?
[12:23] <Saviq> )
[12:24] <Saviq> mhr3, or maybe it isn't...
[12:25] <mhr3> Saviq, well, yes, basically the widget isn't supposed to close by itself, unless you tap a leaf dep
[12:25] <Saviq> mhr3, right, so nothing until you explicitly select a thing
[12:25] <mhr3> and at the same time we don't have the whole tree, so loading children's children requires a query
[12:26] <Saviq> mhr3, yeah, sounds like lazy tree is what we need...
[12:26] <Saviq> children exposed as a ListModel
[12:26] <Saviq> FUN
[12:26] <mhr3> and did i mention that we'll be completely relying on the scope giving us proper data?
[12:26] <mhr3> kmn
[12:27] <mhr3> but well.. doable
[12:27] <Saviq> mhr3, and how do we not rely on scope giving proper data now? :0
[12:28] <mhr3> Saviq, well, this is different, we still expect stateless queries, but them having overall hierarchy
[12:29] <Saviq> mhr3, ah in that sense, yeah
[12:29] <mhr3> Saviq, anyway, i take it the widget will not be an issue :)
[12:29] <mhr3> Saviq, still, i'll need details on how you want the model(s) for it exposed
[12:29] <Saviq> mhr3, as long as you prepare the model ;)
[12:30] <Saviq> mhr3, definitely a ListModel for the results, and probably the two links separately
[12:31] <Saviq> mhr3, in a stack?
[12:32] <Saviq> so... a dynamic ListModel of department pages, filled as we descend in the hierarchy
[12:32] <Saviq> mhr3, the shell might maintain the stack, though, maybe that's better
[12:33] <Saviq> since we want to request a department page and only then push it onto the stack, to have the first items added
[12:33] <mhr3> Saviq, you mean the model always being flat and updating (clear+re-populate) when navigating?
[12:34] <Saviq> mhr3, hangout?
[12:35] <mhr3> Saviq, want to talk with pstolowski about it too, so let's do one in a bit
[12:35] <Saviq> mhr3, ok, ready when you are
[12:35] <mhr3> pstolowski, or you available now?
[12:35] <Saviq> yay diffs from gsites!!!
[12:36] <Saviq> mikenagle, you get a diff if you subscribe to a site!!!
[12:36] <mhr3> ah, he's on lunch
[12:53] <Saviq> AAARRGH
[12:53] <Saviq> it even discarded part of my reply over email
[12:53] <Saviq> like WTH
[12:54] <pstolowski> mhr3, i'm now
[12:55] <mhr3> Saviq, pstolowski, k, ho in 5?
[12:55] <Saviq> hooo!
[12:55] <pstolowski> k
[12:55] <Saviq> too much sugar... or maybe too little?
[12:57] <greyback> Saviq: take more pain kilers
[12:57] <Saviq> oh jeez this is the most half-baked comment support EVER
[12:57] <Saviq> greyback, ah, the blue pill
[12:57] <Saviq> wait
[12:57] <Saviq> that explains things
[12:57]  * Saviq looks at the bottle
[12:57] <greyback> Saviq: they're made for comments, not essays :)
[12:58] <Saviq> greyback, yeah, check that: only two-level threads, i.e. you can only reply to the top-level one
[12:59] <Saviq> top-level threads have <br/> after the name, sub-level ones don't!
[12:59] <Saviq> Mike added attachments, I even got email notifications about them, and can open them, but there's no links on the site!
[13:01] <mhr3> comments + email snippets = super easy to follow everything
[13:02] <greyback> sure, I get that, but otherwise they'd end up satisfying Zawinski's law
[13:02] <greyback> gotta draw a feature line somewhere
[13:03] <Saviq> greyback, well, in docs you can reply to sub-comments can't you?
[13:03] <Saviq> maybe it's the same, just here it suggests you can do more
[13:04]  * greyback decides not to get into this argument, goes to do something productive ;)
[13:19] <dandrader> you guys talking about comment system on launchpad merge proposals?
[13:20]  * dandrader curious
[13:48] <Cimi> mterry, ping :)
[13:49] <mterry> Cimi, hello!
[13:49] <Cimi> mterry, ciao!
[13:49] <Cimi> mterry, I did this https://code.launchpad.net/~cimi/lightdm/uid-bindings/+merge/218958
[13:50] <mterry> Cimi, ah cute.  That's nice
[13:50] <mterry> Cimi, I'll let robert_ancell review it though.  He's usually master-of-lightdm
[13:50] <Cimi> mterry, my only concern is tests, I have no clue where to start
[13:51] <mterry> Cimi, lightdm tests are interesting yeah.  Are there similar tests for other propertise?
[13:51] <Cimi> not sure
[13:53] <mterry> Cimi, there are several other tests that deal with user properties (tests/scripts/user-*.conf
[13:54] <mterry> Cimi, but uid isn't something that can be changed like the other properties
[13:54] <mterry> Cimi, so testing is a little odder there
[13:54] <Cimi> that's why my concern
[13:55] <mterry> Cimi, here's what you do.
[13:57] <Cimi> who can trigger a build btw
[13:57] <mterry> Cimi, tests/src/test-qt-greeter.cpp and tests/src/test-gobjecte-greeter.c (and the python greeter if you're feeling funky) have support for LOG-USER to query a specific user property
[13:57] <Cimi> would be nice to play with a arm build
[13:58] <mterry> Cimi, so add support for the UID field.  Then add a new baby test script that queries the field
[13:58] <mterry> Cimi, then add two "runner" scripts in ./tests (you'll see all the others there) that calls your script with the gobject greeter and the qt greeter (to test both interfaces)
[13:59] <mterry> Cimi, your baby test script can look like ./tests/scripts/user-name.conf but simpler and just for UID
[13:59] <Cimi> hey hey hey
[13:59] <Cimi> one thing at a time :D
[13:59] <Cimi> it's a complete new way of writing tests for me, I need to read code first :)
[14:00] <Cimi> I'll start with reading those two files and add UID
[14:00] <mterry> Cimi, well go back and read above later  :)
[14:11] <Cimi> mterry, I don't see tests for username etc etc
[14:11] <mterry> Cimi, tests/scripts/user-name.conf
[14:13] <Cimi> mterry, uid is not tested
[14:13] <mterry> Cimi, right...  but you just added it, eh?
[14:13] <Cimi> mterry, no
[14:13] <Cimi> mterry, it was already in common etc
[14:13] <mterry> Cimi, you added the public api
[14:13] <Cimi> like gid
[14:14] <mterry> Cimi, that's what this is testing
[14:20] <Saviq> Cimi, https://code.launchpad.net/~cimi/unity8/preview-text-summary-bottom-padding/+merge/217903/comments/522179
[14:27] <Cimi> seb128, overlay scrollbars are so slow on my core i7 with 300$ GPU that I think it's the case to trash them
[14:28] <seb128> Cimi, you should fix them to not be slow?
[14:29] <seb128> Cimi, I'm not the one deciding, talk to Mark ;-)
[14:29] <Cimi> seb128, cannot fix a hack
[14:30] <Cimi> seb128, they will stop working on mir anyway :)
[14:30] <seb128> Cimi, write a non hack implementation then?
[14:30] <Cimi> seb128, can't
[14:30] <Cimi> seb128, they require separate windows
[14:30] <seb128> build support in Mir :p
[14:30] <Cimi> I drop them
[14:31] <Cimi> or I change design
[14:31] <Cimi> I want them internal like facebook
[14:31] <Cimi> and osx (prefer facebook impl)
[14:32] <Saviq> Cimi, that will be supported on Mir, btw ;)
[14:32] <Saviq> Cimi, separate surface of a certain type
[14:32] <Cimi> Saviq, that move and send positions back and forth in sync with the app?
[14:32] <Cimi> Saviq, workarea hints etc?
[14:33] <Cimi> it's shitload of work
[14:33] <Cimi> let's just make them internal
[14:33] <Saviq> Cimi, still doable, if done properly in the toolkit :)
[14:33] <Cimi> superfast, not hackish
[14:33] <Cimi> Saviq, i doubt
[14:47] <elopio> ping Saviq, kgunn: we need to meet to talk about testability requirements for this cycle and goals for the malta sprint.
[14:47] <elopio> can we do it next week?
[14:48] <Saviq> elopio, sure, I'm off Monday, available rest of the week
[14:48] <elopio> Saviq, kgunn: what about tuesday, 10 minutes from now?
[14:49] <kgunn> elopio use my calendar
[14:49] <Saviq> elopio, OMG Tuesday is in 10 minutes?!
[14:49] <elopio> right.
[14:49] <Saviq> elopio, and yeah, just find a slot in our calendars
[14:49] <elopio> Saviq: yes, sorry you didn't get to enjoy your free weekend :)
[14:49]  * elopio dives into google calendar.
[14:50] <Saviq> elopio, ;)
[14:55] <elopio> kgunn: wow, you have all your mornings colored in the calendar.
[14:55]  * elopio hugs kgunn.
[14:56] <elopio> I've sent the invitation for wednesday
[14:58] <Saviq> elopio, that time doesn't work for me ;|
[14:59]  * Saviq looks for a better time
[15:13] <dednick> greyback: what's the purpose of the ProcInfo class in unity-mir? why is it passed to app manager?
[15:15] <greyback> dednick: it's used to support the --desktop_file_hint hack mainly. It fetches the command line for a PID and let's us parse it
[15:16] <dednick> greyback: sure. but why is an empty one passed to the App manager?
[15:17] <dednick> greyback: does ProcInfo mean "all process info" or "a single processes info"
[15:17] <greyback> dednick: empty?
[15:17] <greyback> it's used here:    std::unique_ptr<ProcInfo::CommandLine> info = m_procInfo->commandLine(pid);
[15:19] <greyback> we set the PID for ProcInfo to fetch, then use it to parse the PID
[15:19] <dednick> greyback: yeah, i know. But why is it passed to the app manager as a parameter? the class has no context.
[15:19] <greyback> dednick: ah, for each of testing
[15:19] <greyback> ease
[15:19] <greyback> so it can be easily mocked
[15:19] <dednick> greyback: ah. ok
[15:20] <dednick> greyback: so it's supposed to identify "all process info"
[15:20] <dednick> not just a single one
[15:20] <Cimi> seb128, Saviq I think we should change designs and have scrollbars with the internal overlay
[15:21] <seb128> Cimi, that works for me, but I'm not a designer
[15:21] <Cimi> is massively easier to implement, and lot faster
[15:21] <Saviq> Cimi, you want to present that to Mark? ;)
[15:21] <Cimi> Saviq, I could, no problem
[15:21] <Saviq> Cimi, TBH I don't care much, doesn't involve my work either way ;)
[15:22] <Cimi> Saviq, neither mine
[15:22] <Saviq> Cimi, sure, but you care, I don't
[15:22] <Cimi> but will for who in mir side will have to implement this
[15:22] <Cimi> and qt side
[15:22] <Cimi> and gtk
[15:22] <Saviq> Cimi, toolkits only, Mir will support it anyway
[15:23] <Cimi> Saviq, yes but if it's internal to the window, mir needs to do 0
[15:23] <Cimi> Saviq, otherwise we need features from the server
[15:23] <Saviq> Cimi, they need to do 0 anyway, those features are planned regardless of scrollbars, so they will get implemented
[15:24] <Saviq> whether they'll be used for scrollbars or not is a completely different topic
[15:24] <Saviq> Cimi, and I believe you're overreacting, if you can have a child surface and enforce/know its position in relation to the parent surface, it's really not that difficult to do
[15:25] <Cimi> Saviq, it is not child surface
[15:25] <Saviq> Cimi, it would be in Mir
[15:25] <Cimi> Saviq, children stay within the parent dimensions
[15:25] <Saviq> Cimi, said who?
[15:25] <Cimi> Saviq, cannot float around the screen outside the parent
[15:25] <Cimi> Saviq, X
[15:25] <Saviq> Cimi, yeah, and?
[15:26] <Saviq> since when do we care about what X implements?
[15:26] <Saviq> Cimi, really, please trust people that thought about this
[15:26] <Cimi> Saviq, not sure they thought about this
[15:27] <Saviq> Cimi, believe me, they did
[15:27] <Cimi> about how to implement overlay scrollbars in qt?
[15:27] <Cimi> and gtk?
[15:27] <Saviq> in Foo
[15:27] <Cimi> cool then
[15:27] <Cimi> I'll let them work on them
[15:27] <Saviq> Cimi, doesn't matter in what
[15:27] <Saviq> Cimi, what matters to Mir is making it possible
[15:28] <Saviq> in a sane way
[15:30] <Cimi> Saviq, performance will still suck though :)
[15:30] <Cimi> on scrolling
[15:30] <Saviq> Cimi, why?
[15:30] <Saviq> Cimi, what's different with overlay scrollbars?
[15:30] <Cimi> Saviq, because there is a client that waits for signals coming from the window manager/server
[15:31] <Cimi> and this is out of the rendering pipeline of the toolkit
[15:31] <Saviq> Cimi, and why does that have to suck?
[15:31] <Cimi> because it is slower than direct input
[15:31] <Cimi> if you move a mouse inside a mousearea
[15:31] <Saviq> Cimi, slower than 16ms? ;)
[15:31] <Cimi> is direct input
[15:32] <Saviq> Cimi, I really fail to see the bottleneck here, it's one real value to communicate every frame
[15:32] <Cimi> otherwise you move a window, this window is moved on the server that generates an event with how much it moved
[15:32] <Cimi> there is a callback connected in the toolkit that translates this into input
[15:33] <Saviq> Cimi, _one real value every frame_ really? bottleneck?
[15:33] <Cimi> Saviq, it is super slow here on compiz
[15:33] <Saviq> well now
[15:33] <Cimi> on my machine
[15:33] <Cimi> faster than  a 3000 retina macbook
[15:33] <Saviq> why do you translate unity+compiz+X directly to Mir?
[15:34] <Saviq> Cimi, yes, we know you have a fast notebook
[15:34] <Cimi> Saviq, cannot imagine if it is slow here
[15:34] <Cimi> how it could be on a slower hardware
[15:34] <Saviq> Cimi, good you're not writing it then
[15:34] <Saviq> end of message, sorry
[15:34] <Cimi> anyway
[15:34] <Cimi> indeed
[15:34] <Cimi> was about to say
[15:34] <Cimi> just let's try to change design so we can have something much faster
[15:35] <Saviq> Cimi, it's a broken argument
[15:35] <Saviq> Cimi, "let's change design because it's slow"
[15:35] <Saviq> Cimi, it's not inherently slow
[15:35] <Saviq> Cimi, it's slow in the current implementation, let's make the implementation better
[15:35] <Saviq> Cimi, some humility please
[15:35] <Cimi> Saviq, well I also don't like the design
[15:36] <Saviq> Cimi, so start with that, not with "it's slow on my beefy machine"
[15:36] <Saviq> Cimi, that argument won't get you anywhere
[15:36] <Cimi> I don't like it and is slow because of implementation
[15:36] <elopio> Saviq: ok, you have permissions to move it, just find a better spot.
[15:36] <Cimi> I much prefer other implementations of scrollbars
[15:36] <elopio> or we can meet with you, and then with kevin.
[15:36] <Saviq> elopio, would be easier if everyone had their work hours marked in the calendar :|
[15:38] <elopio> yeah, I've just updated mine.
[15:40] <Saviq> Cimi, sure, but that doesn't lead to "let's change design" unless "I don't like it" resonates with those responsible for design and/or unless "it's slow because of implementation" is analyzed and determined to be unfixable, which in this case I tell you it's crazy to think it will be slow in every implementation - again, it's just one real value to communicate every frame
[15:41] <Saviq> Cimi, we'd be in a much worse situation if we'd had problems to communicate that
[15:41] <Saviq> mzanetti, look at https://blueprints.launchpad.net/ubuntu/+spec/client-1410-unity-ui-appsplash please and comment / add anything you think important
[15:59] <sil2100> Saviq: btw.!
[16:00] <sil2100> Saviq: we noticed an unity8 crash in our smoketesting recently, could you have someone look at that by any chance? I can fill in a bug if needed, the crash can be found here for instance: http://ci.ubuntu.com/smokeng/utopic/touch/mako/19:20140509.1:20140506.1/7941/unity8/
[16:00] <sil2100> Saviq: (hi!)
[16:06] <Saviq> sil2100, isn't it the same crash on unity8 exit?
[16:07] <Saviq> grrrrr why no stacktrace :[
[16:08] <Saviq> why aren't those preprocessed again? :)
[16:08] <Saviq> :( rather
[16:12] <Cimi> Saviq, best way for carousel shadow now is adding a property to Card, can I?
[16:12] <Saviq> sil2100, same crash - bug #1315251
[16:12] <Saviq> Cimi, can't the shadow be added in CardCarousel to the delegate?
[16:12] <Saviq> Cimi, since it's the only place where we'd use it?
[16:13] <Cimi> Saviq, but the delegate is the Card
[16:13] <Saviq> Cimi, yeah, and?
[16:13] <Cimi> Saviq, and to add shadow I need to set borderSource of artShape to an invalid value
[16:13] <Saviq> base off of https://code.launchpad.net/~aacid/unity8/dynamic_specialized_cards/+merge/218089 btw
[16:14] <Cimi> Saviq, as well as placing under artShape
[16:14] <Cimi> so cardShadow
[16:14] <Cimi> bool
[16:14] <Cimi> might be easy, light
[16:15] <Saviq> Cimi, why do you need to remove the border, we don't want it in carousel?
[16:15] <sil2100> Saviq: oh, so this one is the crash on stop as well? Thought it's something new as we had one unity8-crash on test-stop already 'fixed by itself' recently
[16:15] <Cimi> Saviq, nope
[16:15] <sil2100> Saviq: anyway, ok, thanks for having a quick look!
[16:15] <Saviq> sil2100, apparently not any more
[16:15] <Cimi> Saviq, the border is an inset
[16:15] <Cimi> Saviq, we would like an outer border, but the shadow is enough
[16:16] <Saviq> sil2100, bug #1317968 btw
[16:16] <Saviq> Cimi, ok, a) look into Albert's branch
[16:16] <Saviq> Cimi, we'll need to insert the borderSource: "none" to the generated delegate in case of carousel
[16:17] <Saviq> Cimi, and put the shadow in there under artShape
[16:17] <Cimi> tak
[16:17] <Saviq> Cimi, OTOH I still think we should be able to add the shadow in CardCarousel
[16:17] <Saviq> with z: -1
[16:17] <Cimi> Saviq, but I need the anchors of the artShape
[16:18] <Cimi> Saviq, otherwise I will fill the entire card
[16:18] <Saviq> Cimi, the artShape *is* the card in carousel
[16:18] <Cimi> yeah I know
[16:18] <Cimi> but feels like it works because it's a specific case
[16:18] <Cimi> it is not anchored to the right thing
[16:18] <Saviq> Cimi, depends on what we want to support in the carousel
[16:19] <Saviq> Cimi, if we say the only supported delegates are ubuntu-shaped
[16:19] <Saviq> Cimi, and that carousel has drop-shadows
[16:19] <Saviq> Cimi, that's the right place to put it
[16:19] <Saviq> Cimi, if it's supposed to be specific to the dash, then CardCarousel is the place I believe
[16:19] <Saviq> not Card itself, we don't want the shadow anywhere else
[16:20] <Saviq> ~EOW o/
[16:21] <Cimi> bye
[16:21] <Cimi> catch you monday
[16:22] <Cimi> rain is waiting for me http://www.bbc.co.uk/weather/2643743?day=1
[16:22] <Cimi> x-|
[16:24] <Cimi> wow weather for malta seems amazing
[16:31] <Cimi> Saviq, I fixed https://code.launchpad.net/~cimi/unity8/preview-text-summary-bottom-padding/+merge/217903/comments/522179 for Monday
[16:36] <Cimi> mterry, which timezone is robert?
[16:36] <Cimi> thought he was in canada
[16:36] <mterry> Cimi, australia, not sure which
[16:36] <Cimi> ok
[16:38] <Saviq> Cimi, ah, so height of the items changed and you had to make the thing smaller?
[16:38] <Cimi> Saviq, from a quick look at the file
[16:39] <Cimi> Saviq, it looked like the item number 9 was expected to be outside of the window
[16:39] <Cimi> so I reduced height
[16:39] <Cimi> hah
[16:39] <Cimi> will ask albert monday
[16:40] <Cimi> you go and enjoy your weekend
[16:40] <Cimi> I have 20 mins left
[16:40] <Saviq> Cimi, it's my test, yeah that's correct
[16:43] <Saviq> Cimi, ACK
[16:44] <Cimi> Still on trusty :| :D
[16:51] <mhr3> where do i get the tag remover script?
[16:51] <mhr3> Saviq, ?^
[16:52] <Cimi> mhr3, I'll give u
[16:53] <Cimi> mhr3, http://people.canonical.com/~msawicz/unity8/strip-u8-tags.sh
[16:53] <Cimi> mhr3, then you run both LOCAL and REMOTE
[16:54] <mhr3> right, thx Cimi
[16:54] <Cimi> so wget http://people.canonical.com/~msawicz/unity8/strip-u8-tags.sh
[16:54] <Cimi> chmod
[16:54] <Cimi> and run with the local path
[16:54] <Cimi> then against where you pushed
[16:54] <Cimi> otherwise it happens (it happened to me) that you keep pushing the tags
[16:56] <Saviq> mhr3, you can supply multiple paths (i.e. ./strip-u8-tags lp:foo ~/bar lp:baz)
[16:56] <mhr3> poor thing, it's deleting it one by one remotely
[16:56] <mhr3> will take ages
[16:57] <Cimi> mhr3, and be aware it takes ages for the remotes
[16:57] <Cimi> hah
[16:57] <Cimi> mhr3, so do it when you don't want to close PC for weekend :)
[16:57] <Cimi> probably 30 mins or less
[16:57] <Cimi> more than 10 iirc
[16:58] <mhr3> need to do some ironing
[16:58] <mhr3> like a proper housewife
[16:59] <mhr3> so i'll let it run
[16:59] <mhr3> enjoy weekend everyone
[16:59] <Saviq> mhr3, alternative would be to maybe use liblaunchpad, couldn't be bothered :P
[16:59] <Cimi> mhr3, train yourself with warsow
[16:59] <Cimi> instagib :P
[17:00] <Cimi> that was fun
[17:00] <mhr3> Cimi, heh, tell that to your body that i was passing by lots of times :P
[17:00] <mhr3> *to your *dead* body :)
[17:01] <Cimi> mhr3, the very old unreal tournament has a fun instagib mode
[17:01] <Cimi> mhr3, runs on linux
[17:01] <Cimi> mhr3, we might try that...
[17:01] <Cimi> warsow runs crap on my notebook
[17:01] <mhr3> yea, or we just convince dednick to install windows
[17:02] <Cimi> otherwise quake 3
[17:02] <Cimi> I don't have windows on my notebook
[17:02] <Cimi> was thinking of malta :)
[17:03] <mhr3> wow, am i the only one who doesn't delete that partition?
[17:03] <Cimi> mhr3, bought a SSD
[17:03] <mhr3> oh that reminds me, i wanted to order the wifi chip
[17:03] <Cimi> no windows dvd
[17:04] <Cimi> mhr3, first open your laptop and find out your mini pcie
[17:05] <Cimi> mhr3, which model you have?
[17:05] <mhr3> e430
[17:06] <Cimi> http://www.lenovo.com/shop/americas/content/user_guides/e430_e530_ug_en.pdf
[17:07] <Cimi> actually http://support.lenovo.com/en_GB/product-and-parts/detail.page?DocID=PD023308
[17:09] <Cimi> mhr3, you want this http://www.amazon.co.uk/Intel-Dual-Band-Wireless-AC-7260/dp/B00E7QGHE6/ref=sr_1_1?ie=UTF8&qid=1399655043&sr=8-1&keywords=7260
[17:10] <Cimi> mhr3, here we go http://www.ebuyer.com/522031-bnw-intel-dual-band-wireless-ac-7260-2x2-7260-hmwwb
[17:10] <Cimi> mhr3, I might buy one at that price
[17:10] <Cimi> so I say bye bye broadcom
[17:10] <mhr3> meh, already ordered from amazon :P
[17:11] <Cimi> mhr3, so you in the office monday? ahahahah
[17:12] <mhr3> Cimi, doesn't support prime :P
[17:12] <mhr3> will arrive on tuesday probably
[17:12] <mhr3> and anyway i have monday off :)
[17:14] <Cimi> mhr3, I'm off to gym! let me know if  you want to play a bit over the weekend, we can play online
[17:14] <Cimi> ciao
[17:15] <mhr3> Cimi, got friends staying at my place, so we'll be walking around london
[17:16] <Cimi> mhr3, rain is expected
[17:16] <Cimi> :(
[17:16] <mhr3> and that's why i need to do the ironing, so there's some actual space :)
[17:16] <mhr3> yea... sucks
[17:16] <mhr3> but well
[22:20] <mhall119> Saviq: I'm still having to unlock and re-add apps on my Launcher when I get updates, wasn't that fixed?
[22:21] <Saviq> mhall119, no, it wasn't, but will be, soon
[22:24] <mhall119> ah, ok, I thought that was part of the big Unity 8 update that brought the new scopes
[22:29] <Saviq> mhall119, no, totally unrelated :)