[07:59] <Cimi> Saviq, fixed issue
[08:01] <Saviq> Cimi, bug #1355046 btw
[08:01] <Cimi> Saviq, cool
[08:01] <Cimi> Saviq, for now I rely on source != ""
[08:01] <Saviq> Cimi, yup, sounds good
[08:03] <Cimi> Saviq, I think we want to branch and fix overview
[08:04] <Cimi> Saviq, or maybe merge and branch later on
[08:04] <Saviq> Cimi, please comment on the MP with any issues you have
[08:04] <Cimi> Saviq, most of them are UX issues
[08:04] <Cimi> Saviq, only UI issue is the white indicator on black frame
[08:05] <Saviq> Cimi, white indicator?
[08:05] <Saviq> Cimi, ah activity
[08:05] <Cimi> Saviq, your dash activity indicator has a white box AROUND
[08:06] <Cimi> Saviq, let's call it processing indicator
[08:06] <Cimi> or activity bar
[08:06] <Saviq> Cimi, yeah, this is a slightly weird issue, 'cause I'd have to pass opacity back to all the respective views so that they draw the background on which I overlay the orange bar...
[08:07] <Saviq> Cimi, not a problem of the overlay branch in any case
[08:07] <Saviq> Cimi, is a problem in trunk
[08:08] <Saviq> but we just don't have any other scope that exposes it
[08:11] <Saviq> Cimi, you're done with settings are you?
[08:18] <Cimi> Saviq, nope
[08:18] <Saviq> ah ok
[08:18] <Cimi> Saviq, doing tests today then is done
[08:25] <Cimi> Saviq, when we flick the dash and change scope, which is the component in charge of that?
[08:25] <Saviq> Cimi, DashContent
[08:25] <Cimi> dashcontentlist?
[08:25] <Cimi> ok
[08:26] <Cimi> Saviq, I have to stop it to accept flicks when the previews are on screen
[08:27] <Saviq> Cimi, previews have their own horizontal flickable, why would those propagate up to dashcontent?
[08:27] <Saviq> (since they have not until now)
[08:28] <Cimi> Saviq, settings don't :)
[08:28] <Cimi> Saviq, a quick interactive false
[08:28] <Saviq> Cimi, so settings, not previews :P
[08:28] <Saviq> Cimi, you said that you have to disable it if previews are up
[08:28] <Cimi> pff :P
[08:28] <Cimi> monday morning :P
[08:29] <Saviq> Cimi, if you'd just put it all in a page stack already you'd be done with it by now ;)
[08:30] <Cimi> Saviq, there's all the work for the header to be done, isn't it?
[08:30] <Saviq> Cimi, I don't think we'd do anything special with the header, it'd be part of a page in our case
[08:31] <Cimi> anyway currently my dash doesn't run
[08:37] <Cimi> Saviq, does dash run for you?
[08:38] <Cimi> today?
[08:38] <Cimi> only thing I did was rebooting from friday I think
[08:38] <Cimi> forget
[08:39] <Saviq> done
[09:09] <Cimi> Saviq, how do I mock something like data.property = value in js?
[09:09] <Cimi> Saviq, i remember how do do it for arrays, but not .property
[09:10] <Cimi> (disctionary I mean)
[09:10] <Saviq> Cimi, data = { "property": "value" } you mean?
[09:10] <Cimi> Saviq, data.property will work?
[09:11] <Saviq> Cimi, actually scrap the first quotes, but yes
[09:11] <Saviq> Cimi, FWIW both data.property and data["property"] willl
[09:11] <Saviq> JS is weird like that
[09:11] <Cimi> Saviq, I thought that was data["property"]
[09:11] <Cimi> ah ok
[09:11] <Cimi> that was my concern
[09:11] <Saviq> Cimi, { } is an object
[09:11] <Saviq> Cimi, so it has properties
[09:12] <anpok> (something completely different, that just seems to fit here: https://www.destroyallsoftware.com/talks/wat )
[09:19] <Cimi> Saviq, settings should behave like listItems?
[09:19] <Cimi> Saviq, touching everywhere to have focus?
[09:20] <Cimi> or action
[09:20] <Cimi> mmm maybe not
[09:20] <Cimi> because they can be very mixed
[09:59] <Saviq> Cimi, small one for you https://code.launchpad.net/~saviq/unity8/fix-preview-anchor/+merge/230268
[10:02] <Cimi> Saviq, the label setting
[10:03] <Cimi> Saviq, horizontal space is limited
[10:03] <Cimi> Saviq, I don't see how I can have both the description and the entry
[10:03] <Saviq> Cimi, ENOCONTEXT
[10:03] <Cimi> HAH
[10:03] <Cimi> Saviq, scope settings, what else am I doing now? :)
[10:03] <Cimi> Saviq, we have no design for them right?
[10:04] <Saviq> Cimi, no
[10:04] <Cimi> so the description label is usually is
[10:04] <Saviq> Cimi, so just add one on top of another?
[10:04] <Saviq> instead of next to each other?
[10:04] <Cimi> "display grooveshark result in dash" or something long like that
[10:05] <Cimi> it is already ellipsised (cannot write that word)
[10:05] <Cimi> with the switch
[10:05] <Cimi> (that was for boolean)
[10:05] <Cimi> then we have settings with a text field
[10:05] <Cimi> they might have a long label with the description
[10:05] <Cimi> then a text field
[10:06] <Cimi> I was wondering if we want to consider using two rows for settings
[10:06] <Cimi> description on top, action/control on bottom
[10:07] <Cimi> Saviq, ~cimi/unity8/scope-settings
[10:08] <Cimi> Saviq, you can see boolean settings (real) in Music and Video scopes
[10:08] <Cimi> Saviq, then test the switch with make try(test)ScopeSettingSwitch
[10:08] <Cimi> Saviq, label with make try(test)ScopeSettingLabel
[10:09] <Saviq> Cimi, yeah, just put it on top
[10:09] <Saviq> Cimi, also, calling it 'label' feels wrong
[10:10] <Saviq> Cimi, shouldn't it be ScopeSettingText?
[10:10] <Cimi> Saviq, ok
[10:10] <Saviq> Cimi, label implies static text
[10:10] <Cimi> ah good pppoint
[10:14] <Cimi> looks really ugly in two lines
[10:14] <Cimi> better to use checkbox
[10:40] <Saviq> greyback, if you didn't know, you can uncheck "Needs review" in MP submission page to make it WiP to start with
[10:40] <greyback> Saviq: yep, I just forgot
[10:40] <Saviq> greyback, sure
[10:40] <greyback> sorry for the noise
[11:14] <Cimi> freaking ctrl q
[11:15] <Cimi> so close to ctrl tab
[11:24] <Saviq> cwayne, you'll be happy with this: https://code.launchpad.net/~saviq/unity8/dash-horizontal-list/+merge/230279
[11:24] <cwayne> Saviq: :D thank you!
[11:31] <facundobatista> Holas!
[11:32] <Saviq> elo
[11:38] <Saviq> /food
[12:02] <Cimi> so if I add text in a textfield with insert(0, "new text)
[12:02] <Cimi> the text property does not seem to update
[12:13] <jgdx> Saviq, hey, the flag we talked about for disabling rotation sensors, any docs on that yet? :)
[12:42] <Cimi> Saviq, do we want to darken and make setting touchable?
[12:42] <Cimi> scope settings
[12:43] <Cimi> because putting textfield in a listitem might be weird - if I subclass listitem.empty I get the triggered signal when I press the content, but this might not be ready
[12:44] <Cimi> or not valid
[12:44] <Cimi> when I press the listitem I mean
[12:44] <Cimi> so I can create a new signal and such...
[12:44] <Saviq> Cimi, it probably depends, for a checkbox I'd actually trigger the checkbox as you press on the item
[12:44] <Cimi> and makes sense
[12:44] <Cimi> and that's why I used it
[12:45] <Saviq> Cimi, Empty has a property to disable the highlight
[12:45] <Cimi> but now I am confused on the string and number setting
[12:45] <Cimi> what shall I do when user taps the listitem?
[12:45] <Saviq> Cimi, you could focus the text entry
[12:46] <Saviq> Cimi, for numbers obviously nothing
[12:46] <Cimi> highlightWhenPressed seems visual only
[12:46] <Cimi> Saviq, triggered is always emitted though
[12:46] <Saviq> Cimi, yeah, but what would ever listen to that?
[12:46] <Cimi> Saviq, so when I tap the string listitem it will emit trigger
[12:46] <Saviq> Cimi, so?
[12:46] <Cimi> I was thinking of listening to trigger in the scopesettings
[12:47] <Cimi> I will have to create another signal
[12:47] <Cimi> settingUpdated
[12:47] <Cimi> that's fine I just wanted to keep code simple
[12:47] <Saviq> Cimi, is that for the model.value = foo part?
[12:47] <Saviq> Cimi, triggered wasn't a good name for that anyway
[12:47] <Cimi> Saviq, it is the signal I want to emit from each single setting component
[12:48] <Cimi> when the editing was finished
[12:48] <Cimi> ok
[12:48] <Cimi> settingUpdated maybe
[12:48] <Saviq> Cimi, yeah, and "triggered" doesn't sound like a good name for it at all
[12:48] <Saviq> Cimi, no need for the "setting" part there
[12:48] <Cimi> Saviq, is the same name we use in PreviewWidget (triggered)
[12:49] <Saviq> Cimi, yeah, but those are, actually, triggered
[12:49] <Saviq> Cimi, actions are triggered on those, there's no value associated with the triggering
[12:59] <Cimi> Saviq, how do I focus the textfield to a specific char?
[12:59] <Cimi> cannot find in APIS
[13:00] <Saviq> Cimi, I don't think you do, why?
[13:01] <Cimi> Saviq, we said would be good to focus the textfield when clicking the listitem?
[13:01] <Saviq> Cimi, yeah, but why on a particular char?
[13:01] <Cimi> Saviq, last one
[13:02] <Saviq> Cimi, I think we should go for http://qt-project.org/doc/qt-5/qml-qtquick-controls-textfield.html#selectAll-method
[13:02] <Cimi> ok
[13:02] <Cimi> Saviq, I'm using ubuntu components textfield btw
[13:03] <Cimi> (which has same method)
[13:03] <Saviq> Cimi, which is just a wrapper around the upstream one
[13:03] <Cimi> Saviq, nope
[13:03] <Cimi> Saviq, it doesn't have editingFinished()
[13:04] <Saviq> Cimi, right, it's not, another waste of API :|
[13:05]  * Saviq really doesn't get why we're replacing all the upstream components ;(
[13:05] <Cimi> :/
[13:05] <Cimi> editingFinished is also quite handy
[13:06] <Cimi> otherwise you have to do onActiveFocusChanged: if (!activeFocus && acceptableInput)
[13:07] <Cimi> and listen to other keys
[13:07] <Saviq> Cimi, onAccepted doesn't help does it?
[13:08] <Cimi> Saviq, is only on enter
[13:08] <Cimi> return key
[13:08] <Cimi> so I have both
[13:08] <Saviq> Cimi, yeah thought so
[13:09] <Saviq> Cimi, sounds like a bug against UITK is in order
[13:15] <Saviq> karni, I believe you can mark https://bugs.launchpad.net/unity8/+bug/1352940 fixed for Savilerow?
[13:16] <Saviq> karni, the fix was in UITK after all
[13:16] <karni> Saviq: done
[13:16] <Saviq> karni, tx
[13:31] <Cimi> Saviq, any way to fake pressing return?
[13:31] <Saviq> Cimi, why?
[13:31] <Cimi> Saviq, testing that I emit the signal when I press enter
[13:32] <Saviq> Cimi, just go .accepted()
[13:32] <Cimi> Saviq, is not exposed
[13:32] <Cimi> Saviq, and I cannot test it...
[13:32] <Saviq> Cimi, wdym it's not exposed :D
[13:32] <Cimi> I have the widget and I want to fake an user interaction
[13:32] <Cimi> I want to fake the user pressing enter on the keyboard
[13:32] <Saviq> Cimi, but this way you'd start testing the TextField widget
[13:33] <Saviq> Cimi, that it does indeed emit accepted when enter is pressed
[13:33] <Cimi> ah ok
[13:33] <Cimi> so I do textField.accepted() ?
[13:33] <Saviq> Cimi, which is the responsibility of the UITK test suite
[13:33] <Saviq> Cimi, yes
[13:44] <Saviq> dednick_, hey, any ETA on dash-overview review?
[13:53] <dandrader> mzanetti, ping
[13:54] <mzanetti> dandrader: hi
[13:55] <dandrader> mzanetti, hi! when would you have time to review https://code.launchpad.net/~dandrader/unity8/lifecycle/+merge/230090 ?
[13:55] <dandrader>  just rebased it on top of latest trunk
[13:56] <mzanetti> right... hmm... dunno. will try to get to it asap
[14:16] <Cimi> Saviq, if I use Clipboard in the test, the test segfaults at the end
[14:16] <Cimi> Saviq, uitk bug?
[14:17] <Saviq> Cimi, you gave rather little info to determine that
[14:17] <Cimi> Saviq, to check I am selecting text on clicking the listitem, I copy the content of the selection and check if Clipboard.data.text is equal to what I expect
[14:18] <Cimi> Saviq, this pass, but after all tests are running, I see qmltestrunner segmentation fault
[14:18] <Saviq> Cimi, more testing of TextField, eh?
[14:18] <Saviq> Cimi, just check if it's focused ;)
[14:18] <Cimi> Saviq, yes, did that, then wanted to test if we were selecting all the text
[14:19] <Saviq> Cimi, which is testing TextField
[14:19] <Cimi> I can avoid using clipboard by calling cut and checking displayed text
[14:19] <Saviq> or just testing that it's focused and relying on UITK to have tested their own component's selectAll
[14:32] <dednick_> Saviq: i'll get back on it shortly. i've just been re-installing ubuntu on new ssd.
[14:39] <Saviq> dednick_, tx
[14:42] <Saviq> MacSlow, https://www.youtube.com/watch?v=-HoHkFgslJc
[14:44] <mzanetti> MacSlow: recommendation to get started: https://developer.oculusvr.com/forums/viewtopic.php?t=1539
[14:44] <mzanetti> MacSlow: the planetarium is also amazing
[14:45] <MacSlow> Saviq, mzanetti: I assume I won't get much sleep starting tomorrow :)
[14:45] <mzanetti> heh
[14:45] <mzanetti> MacSlow: well, first time I tried I got sick after 5 mins
[14:45] <mzanetti> MacSlow: takes a bit to get used to...
[14:46] <MacSlow> mzanetti, I'm used to some really bad VR back from my university-days...
[14:46] <mzanetti> MacSlow: yeah... but back then the brain was able to figure that its not real
[14:46] <mzanetti> that changed a bit
[14:46] <mzanetti> now it seems real without gravity lining up with what you see
[14:48] <MacSlow> mzanetti, I'm willing to play guinea pig for you all :)
[14:48] <mzanetti> MacSlow: as I said... I tried them in June last year...
[14:49] <mzanetti> MacSlow: was sharing a room with the guy that developed that "alone in the rift" demo I posted before
[14:49] <MacSlow> mzanetti, I assume that was still the DK1 version?!
[14:49] <mzanetti> yeah... it was the low-res version still
[14:50] <mzanetti> but already impressive enough
[14:50] <mterry> Saviq, do you know if anyone has cycles to review https://code.launchpad.net/~mterry/unity8/wrong-password-handling/+merge/229184 ?  That has the delay-on-failed-login feature that security requested and kgunn wanted to get in by Thursday
[14:50] <MacSlow> mzanetti, they've done much work to improve upon the usual motion-sickness factors (higher res, less latency, motion "prediction"...)
[14:51] <mzanetti> MacSlow: they still can't simulate gravity, which is the main reason
[14:51] <mzanetti> MacSlow: well, they can, but I doubt you've got that piece of hardware in your mailbox :)
[14:51] <MacSlow> mzanetti, true...
[14:51] <mzanetti> if you do, I'm on my way
[14:52] <mzanetti> :)
[14:52] <MacSlow> mzanetti, hehe
[14:53] <dednick_> Saviq: is the dash overview handle always supposed to show? (the little tag you are supposed to pull at the bottom)
[14:53] <Saviq> dednick_, no, and it doesn't
[14:53] <dednick_> Saviq: it's always there for me.
[14:53] <Saviq> dednick_, it only shows on the dash, and only if the header is all on screen
[14:53] <dednick_> oh right. yes, thats what i mean
[14:53] <Saviq> dednick_, if you scroll down, it'll go away
[14:53] <Saviq> dednick_, then yes
[14:54] <Saviq> dednick_, https://sites.google.com/a/canonical.com/unity8dash/scopes/dash-overview
[14:54] <Saviq> dednick_, it actually even says "The hint is always visible - never hidden or smaller (unlike hints used in apps)"
[14:54] <Saviq> dednick_, but we alleviated that slightly
[14:54] <Saviq> (with design ACK)
[14:59] <dednick_> Saviq: any idea why the CI failed for overview? can't see any qmltest failures.
[14:59] <Saviq> dednick_, looking
[15:04] <Saviq> dednick_, yes, that's what I mentioned
[15:05] <Saviq> dednick_, it fails because gcovr hangs for 2h in qmluitests
[15:05] <dednick_> Saviq: ok. cool
[15:05] <Saviq> dednick_, but if the test report says no failures, then it's passed
[15:05] <Saviq> dednick_, there are two failures there though https://jenkins.qa.ubuntu.com/job/unity-phablet-qmluitests-utopic/845/testReport/?
[15:06] <dednick_> Saviq: ah. i wasn't looking at the full log
[15:07] <dednick_> or the report
[15:07] <Saviq> dednick_, yeah, it doesn't show them if the job failed
[15:07] <Saviq> dednick_, testDashContent segfaulted there
[15:08] <Saviq> dednick_, and looking at https://jenkins.qa.ubuntu.com/job/unity-phablet-qmluitests-utopic/845/testReport/%28root%29/qmltestrunner/Dash__test_dash_overview_show_select_different_favorite/ it's a timing issue (didn't wait for something)
[15:08] <asac> Saviq: hello hello; i have a hung unity/shell (password screen for unlocking does not accept input etc.); anything i shall extract?
[15:08] <asac> (before rebooting)
[15:08] <asac> i can adb shell into device luckily
[15:08] <Saviq> asac, power button shows the greeter?
[15:09] <asac> Saviq: yeah, that thing i can swipe away
[15:09] <asac> but then the pin screen doesnt take any input
[15:09] <Saviq> asac, ok, ~known issue, touch vs. mouse events (don't ask, Qt limitation, we need to dig into it)
[15:09] <asac> indicators still work etc.
[15:09] <asac> ok so you have all info?
[15:10] <Saviq> or er s/limitation/weird choice/
[15:10] <asac> the pin screen is greyed out though
[15:10] <Saviq> asac, only info we'd be interested in is steps to reproduce...
[15:10] <asac> i had similar feeling hangs regularly
[15:10] <asac> ok, guess its something racy, so not easy to repro
[15:10] <asac> Saviq: no gdb dump or anything that could help?
[15:11] <asac> e.g. force a coredump and submit that?
[15:11] <Saviq> asac, not really, as the whole thing works
[15:11] <Saviq> asac, so it doesn't hang anywhere
[15:11] <Saviq> asac, it's just part of the even logic gets confused
[15:11] <Saviq> asac, so we need to get it under gdb in that state and step it
[15:11] <Saviq> *event
[15:12] <Saviq> asac, so steps to reproduce are what we're most interested in
[15:12] <asac> Saviq: remote access could help?
[15:12] <asac> e.g. ssh into my machine?
[15:13] <asac> anyway rebooted now... see that often enough so we can still do that
[15:13] <Saviq> asac, it's happening to us somewhat frequently, too, so once we focus on it we should be able to find out what's going on
[15:13] <asac> kk
[15:13] <asac> thanks
[15:14] <Saviq> asac, bug #1295623 btw
[15:14] <mzanetti> Saviq: I don't see it often any more... its still there, but I get it like once in 2 weeks nowadays
[15:15] <asac> thanks!
[15:15] <Saviq> asac, if you find anything that suggests triggers it, please write down there
[15:16] <greyback> is it normal getting segfaults after some qmltests have run?
[15:16] <greyback> i.e. the tests pass, but then maybe xvfb crashes??
[15:16] <mzanetti> no
[15:17] <greyback> ok, I musta broke something
[15:17] <Saviq> greyback, DashContent is the only one crashing sometimes that I know of
[15:18] <Saviq> dednick_, in any case, if you can verify those tests passing locally, I wouldn't block on those failures (unless you can reproduce the overview related one)
[15:18] <dednick_> Saviq: i'm running it now
[15:21]  * Saviq loves qmltests with xvfb, can run them on all my 8 cores ;)
[15:21] <dednick_> Saviq: what's an xfail?
[15:21] <Saviq> dednick_, expected fail, meaning this is a negative tests
[15:21] <Saviq> *test
[15:21] <dednick_> ah
[15:22] <Saviq> dednick_, hence the PASS after that
[15:23] <Saviq> dednick_, the issue you reported, sounds like not a dash overview one, you can get there by tapping on the search entry and dismissing the keyboard by swiping it down
[15:23] <dednick_> Saviq: ok, passed for me. i approved branch
[15:25] <dednick_> Saviq: hm. i think the switch to overview needs to cancel input focus
[15:26] <dednick_> Saviq: you can also reproduce putting keyboard into layout mode (orientation). you can then use the bottom (now left) edge to swipe in overview.
[15:27] <dednick_> not exactly intended, but the popup still remaing
[15:27] <Saviq> dednick_, you mean landscape mode? ;)
[15:27] <dednick_> :) yes
[15:27] <dednick_> bit edge case though!
[15:27] <Saviq> dednick_, hmm interesting, I can't get the OSK to rotate when in dash
[15:28] <Saviq> dednick_, yeah, and for my usecase the field should unfocus on keyboard dismissal
[15:28] <dednick_> Saviq: rotate, then click search
[15:28] <Saviq> dednick_, yeah so... we can't really unfocus on bottom swipe as we're getting a snapshot just then
[15:29] <dednick_> Saviq: popup not included in snapshot it would seem
[15:29] <Saviq> dednick_, yeah, popups are parented to root object unfortunately
[15:29] <Saviq> dednick_, bug in UITK IMO
[15:29] <Saviq> or well, something
[15:30] <dednick_> but yeah, there's a bit of animation and shit happening when you unfocus the search.
[15:31] <Saviq> dednick_, yeah, that would get snapshotted in the middle
[15:31] <dednick_> Saviq: why do we snapshot? shouldn't it just be same as app switch? considering dash is an app?
[15:31] <Saviq> dednick_, overview is the same app
[15:31] <dednick_> Saviq: ah
[15:31] <dednick_> right
[15:31] <Saviq> dednick_, we *could* just scale the actual object down
[15:31] <Saviq> dednick_, but that wouldn't solve this issue
[15:32] <Saviq> dednick_, I think both are edge cases, and not really bugs with the overview branch, so not blockers IMO
[15:32] <Saviq> dednick_, keyboard should never rotate when on dash ('cause it doesn't rotate)
[15:32] <dednick_> Saviq: yep. that's why i approved.
[15:32] <Saviq> dednick_, and field should get unfocused on keyboard dismissal
[15:33] <Saviq> dednick_, sure, just justifying myself here ;D
[15:33] <dednick_> well, you can always just blame me for approving!
[15:33] <Saviq> ;)
[15:35] <Saviq> greyback, do we have a bug# for "launch two apps quickly → non-foreground app does not suspend"?
[15:36] <greyback> Saviq: we do, hunting...
[15:38] <pete-woods> Saviq: just tried unity-scope-tool after updating today, I just get a blank results area now. I think this is because we are now dependent on the "scopes" (overview) scope being loaded
[15:38] <pete-woods> is that something you're aware of
[15:38] <Saviq> pete-woods, overview not landed yet
[15:39] <Saviq> pete-woods, and scope tool works fine here?
[15:39]  * Saviq checks again
[15:39] <pete-woods> Saviq: it only breaks for an individual scope
[15:39] <pete-woods> i.e. if you do scope-tool PATH_TO_INI
[15:39] <Saviq> pete-woods, oh hmm
[15:40] <pete-woods> when it generates a new scope config, starts a registry, etc
[15:40] <Saviq> pete-woods, file:///usr/share/unity8/ScopeTool.qml:139:23: Unable to assign null to QString
[15:40] <Saviq> ERROR! Caught unity::scopes::TimeoutException: Request timed out after 5000 milliseconds
[15:40] <Saviq> Unable to add overview scope, can't find with ID: "scopes"
[15:40] <pete-woods> Saviq: yeah, that's the error I get
[15:40] <pete-woods> I think the config generator in the tool needs to include the scopes scope somehow
[15:40] <pete-woods> or something (perhaps the shell plugin) needs to stop being totally dependent on that scope being present
[15:42] <Saviq> pete-woods, should be somewhat easy http://bazaar.launchpad.net/~unity-team/unity8/trunk/view/head:/tools/scopetool.cpp#L73
[15:42] <Saviq> pete-woods, to just include scopes in the extraScopes list
[15:42] <pete-woods> Saviq: yeah, that makes sense
[15:43] <Saviq> pete-woods, will you make a branch or will I?
[15:43] <pete-woods> Saviq: I don't mind doing it, but obviously I'll need your review
[15:43] <Saviq> pete-woods, that's easier than me doing it and getting yours ;D
[15:44] <Saviq> pete-woods, only concern is getting the right path
[15:44] <pete-woods> :)
[15:44] <pete-woods> yes
[15:44] <Saviq> pete-woods, but perhaps you can get it from the registry somehow?
[15:44] <Saviq> pete-woods, or even just get it from .pc build time
[15:44] <Saviq> pete-woods, but you'll manage I'm sure
[15:44] <pete-woods> Saviq: hmm, the difficultly
[15:45] <greyback> Saviq: can't find the damn bug, must be imagining it. Will log one
[15:45] <pete-woods> is that you want the dir: /usr/lib/ARCH/unity-scopes/ (which will contain the scopes scope)
[15:45] <pete-woods> Saviq: but that will also pull in all the other scopes :(
[15:47] <Saviq> greyback, thanks, I couldn't find it either
[15:47] <pete-woods> might need to do something fun with symlinks in the temporary directory that the tool creates
[15:47] <Saviq> pete-woods, why can't we just pass the .ini for the scopes scope alone?
[15:48] <Saviq> pete-woods, I thought we could just push it into the extraScopes set
[15:48] <pete-woods> Saviq: oh, is that how that works?
[15:48]  * pete-woods actually reads docs
[15:49] <pete-woods> I'm (fairly) confident you have to give directory paths to the registry ini
[15:49] <pete-woods> and those dirs are expected to contain scope directories
[15:49] <Saviq> pete-woods, no, you pass .ini files, read --help
[15:50] <Saviq> 'passing a path to a scope config file'
[15:50] <Saviq> pete-woods, but anyway that doesn't work too well
[15:50] <Saviq> pete-woods, I end up with just the scopes scope in the UI
[15:50] <Saviq> pete-woods, which we probably don't want to show
[15:51] <Saviq> pete-woods, ah no wait, wrong .ini
[15:51] <pete-woods> Saviq: hmmmm. just tried starting the user session version of the registry
[15:51] <pete-woods> and it magically owrks
[15:51] <pete-woods> *works
[15:52] <greyback> Saviq: https://bugs.launchpad.net/unity8/+bug/1355275
[15:52] <Saviq> unity-scope-tool /usr/lib/x86_64-linux-gnu/unity-scopes/scopes/scopes.ini /usr/lib/x86_64-linux-gnu/unity-scopes/musicaggregator/musicaggregator.ini
[15:52] <Saviq> pete-woods, ↑
[15:52] <Saviq> pete-woods, only we might want to do something special to UNITY_SCOPES_LIST
[15:53] <Saviq> pete-woods, or maybe that's fine...
[15:53] <Cimi> I have difficulties with implicitHeight of expandable listitem http://paste.ubuntu.com/8018151/
[15:53] <Cimi> implicitHeight here doesn't grow when I expand the listitem
[15:53] <pete-woods> Saviq: I think something as simple as that works well enough for me
[15:54] <Saviq> pete-woods, so yeah, we might append the scopes .ini to extraScopes in the tool
[15:54] <Saviq> pete-woods, whether we want to tweak UNITY_SCOPES_LIST or not...
[15:54] <Saviq> pete-woods, you tell me ;)
[15:55] <pete-woods> if this is only affecting the scope tool, I don't want to play with anything else
[15:55] <pete-woods> I'm also more relieved now I know that it currently does work if the main registry is running
[15:56] <Saviq> Cimi, does ListItem.ItemSelector change its height?
[15:56] <Saviq> Cimi, do you have height set explicitly on ScopeSetting maybe?
[15:56] <Saviq> Cimi, which of those items is Expandable, for that matter?
[15:57] <Cimi> Saviq, height changes if I don't set implicitHeight on the ScopeSetting item
[15:58] <Saviq> Cimi, does it really? where does ScopeSetting take its height from?
[15:58] <Cimi> so if I set ImplicitHeight in root
[15:58] <Cimi> Saviq, scopesetting doesn't set height
[15:58] <Cimi> Saviq, is just item with properties (interface)
[15:58] <Cimi> Saviq, I mean if the root item of that pastebin
[15:58] <Saviq> Cimi, yeah, so how can it change height it if you don't set either height or implicitHeight?
[15:59] <Cimi> Saviq, http://paste.ubuntu.com/8018193/ this doesn't work
[15:59] <Cimi> Saviq, when I click on the listitem, the size of the listitem shrinks
[15:59] <Cimi> it gets smaller
[16:00] <Cimi> I think I want implicitHeight that grows with the size?
[16:03] <Saviq> Cimi, well, how would it grow if you set it to 6gu?
[16:03] <Saviq> Cimi, do you not want OptionSelector btw?
[16:03] <Cimi> Saviq, thought this looked better
[16:04] <Cimi> I don't know
[16:04] <Saviq> Cimi, isn't ItemSelector deprecated/
[16:04] <Saviq> ?
[16:04] <Saviq> apparently not
[16:04] <Cimi> cannot see deprecated in the file
[16:04] <Cimi> I can use optionselesctor
[16:04] <Saviq> ah ValueSelector is deprecated
[16:05] <Saviq> Cimi, no, that's fine
[16:05] <Saviq> Cimi, anyway
[16:05] <Cimi> I don't know how to set the height
[16:05] <Cimi> if I have to
[16:06] <Saviq> Cimi, ScopeSetting has no height unless you set it
[16:06] <Saviq> Cimi, where would it take the height from?
[16:07] <mhall119> Saviq: are there designs to make the dash always the bottom of the switcher stack? Or if not a designs, a bug report requesting that?
[16:07] <Saviq> mhall119, there's no such design desire, no
[16:08] <mhall119> Saviq: should I file this against lp:unity or lp:unity8?
[16:09] <Saviq> mhall119, bug #1355048 though
[16:09] <mhall119> thanks, I'll add comments to that
[16:09] <Saviq> mhall119, I really don't think placing it at the bottom makes sense
[16:10] <Saviq> mhall119, you can always get to it quickly with left edge swipe
[16:10] <Saviq> mhall119, otherwise it's just part of your app stack like anything else
[16:10] <Saviq> mhall119, if you want design feedback on those, please add ubuntu-ux to affected projects
[16:11] <mterry> Saviq, how on earth did just tag 0.1.16 survive the great purge?  I assume people would wipe all tags or none
[16:12] <Saviq> mterry, they were dropped one by one with the original .sh script
[16:12] <Saviq> mterry, so somewhere someone's connection dropped for that one ;)
[16:13] <Saviq> Cimi, ACK on https://code.launchpad.net/~aacid/unity8/dash_overview/+merge/228649 please?
[16:13] <Saviq> dednick_, and top-ACK ↑?
[16:13] <dednick_> Saviq: done
[16:14] <Saviq> dednick_, tx
[16:14] <Saviq> bregma, landing the fixed unity8 job now
[16:14] <Saviq> (I mean it's going into a silo with the desire to land)
[16:14] <Cimi> Saviq, control tags in trunk after we land that
[16:15] <Saviq> Cimi, I always try to strip them just after landing (unless I forget like I did last time)
[16:15] <Saviq> Cimi, but there's also a checklist entry about those :P
[16:16] <Cimi> Saviq, ok but albert got 0.1.16 on friday
[16:16] <Cimi> Saviq, not sure he fixed
[16:16] <Saviq> Cimi, it was in trunk then, and no he didn't, and I will after this lands
[16:18] <mhall119> Saviq: commented and added ubuntu-ux
[16:18] <mhall119> JohnLea: ^^
[16:18] <Saviq> facundobatista, FWIW I'm just building overview in silo 11 now
[16:18] <om26er> Saviq, is dash rotation coming ?
[16:19] <Saviq> om26er, unlikely
[16:19] <Saviq> om26er, or well, *dash* rotation is something not desired by design for now
[16:19] <Saviq> om26er, *shell* rotation following apps might not happen in time, although I'm hopeful it will
[16:19] <om26er> Saviq, the OSD conflicts when writing an sms in landscape
[16:24] <Saviq> om26er, by OSD do you mean notification?
[16:24] <om26er> Saviq, yes,
[16:24] <Saviq> om26er, bug #1210199
[16:24] <om26er> I am typing on the keyboard and if the notification appears, I end up tapping on it
[16:25] <Saviq> om26er, sure, we get it that it's problematic, but it's quite problematic to implement, too
[16:25] <Saviq> om26er, and it's not considered a priority for a phone form factor, except for media consumption
[16:26] <om26er> Saviq, hmm, can we just rotate the notification ? is that possible ?
[16:26] <Saviq> om26er, that would just be a band-aid that would unglue *really* quickly
[16:27] <Saviq> and the wound get rotten and everything
[16:29] <om26er> Saviq, ok, I'll see if people agree to disable screen rotation for messaging-app
[16:29] <mhall119> Saviq: are notifications part of the shell rotation design?
[16:30] <Saviq> mhall119, notifications are part of the shell, not sure what do you mean by shell rotation design?
[16:30] <Saviq> mhall119, when shell rotates, notifications will, too
[16:30] <mhall119> I mean does the design show how/where to display them when the shell is rotated to landscape
[16:30] <mhall119> ok, so that should solve om26er's problem
[16:32] <Saviq> mhall119, for a certain definition of solve, the OSK takes enough space on the screen in landscape very often they will cover one or the other
[16:32] <Saviq> mhall119, especially if you enable predictive text
[16:35] <Saviq> greyback, ah, mzanetti found it bug #1343259
[16:36] <greyback> that's the one
[16:54] <Saviq> mzanetti, greyback, what's happening in phone-right-edge ppa?
[16:55] <greyback> Saviq: nothing afaik
[16:55] <greyback> it's old stuff
[16:55] <Saviq> greyback, Michael Zanetti (1 hour ago)
[16:55] <greyback> oO
[16:55] <greyback> no idea then
[16:55] <Saviq> ah auto build from recipe probs
[16:56]  * Saviq deletes that recipe
[16:56] <greyback> hmm, can turn if off so
[16:56] <Saviq> mzanetti, you got 10s to veto
[16:56] <Saviq> 9
[16:56] <Saviq> 8
[16:56] <Saviq> 7
[16:56] <Saviq> 6
[16:56] <Saviq> 5
[16:56] <Saviq> 4
[16:56] <Saviq> 3
[16:56] <mzanetti> noooo
[16:56] <mzanetti> :D
[16:56] <Saviq> made it ;D
[16:56] <Saviq> mzanetti, wassup there?
[16:57] <mzanetti> I just kicked a build to test the new lockscreen
[16:57] <Saviq> ah new lockscreen, slacker
[16:57] <mzanetti> afaik noone else is using it atm
[16:57] <Saviq> mzanetti, just build locally, eh?
[16:57] <Saviq> if only x-build wasn't broken :|
[16:57] <mzanetti> Saviq: ^
[16:57] <Saviq> I blame tvoss :|
[16:57] <Saviq> mzanetti, I need a PPA to give to user testing
[16:58] <Saviq> mzanetti, with your launcher hotfix
[16:58] <mzanetti> Saviq: well. even if it works, every time I want to use it somethings broken in my chroots or whatever
[16:58] <Saviq> mzanetti, who did you report it to?
[16:58] <mzanetti> Saviq: I think its always "my fault"
[16:59] <mzanetti> it just requires too much much maintenance for me :D
[16:59] <mzanetti> but I seems the SDK works reasonably well nowadays
[16:59] <mzanetti> if we could hook it into that somehow it would be awesome
[16:59] <Saviq> mzanetti, maintenance is sbuild-update $chroot-name, what else?
[16:59] <mzanetti> but I guess that does only click for now
[17:00] <Saviq> and that sbuild-update is not strictly required either
[17:00] <Saviq> mzanetti, you can actually build packages in the click chroot just as well
[17:00] <Saviq> but yeah, bug #1353855
[17:00] <mzanetti> Saviq: I know... I don't even know what to say... it's just always broken when I use it so...
[17:01] <mzanetti> for _something_. be it that bug, or some ppa I require, or whatever
[17:01] <Saviq> mzanetti, you can add ppas no problem
[17:01] <mzanetti> I know I can..
[17:01] <Cimi> Saviq, I only need integration tests (maybe AP for the settings), but I finished and pushed the rest, we can try the settings running if we had scopes using them
[17:01] <Saviq> Cimi, don't we? didn't you say music has them?
[17:02] <Cimi> Saviq, yes but no sign of string settings, numbers or list
[17:02] <Cimi> Saviq, but I have them tested using mocks
[17:02] <Saviq> Cimi, ah yes, doubt we'll have any
[17:02] <Saviq> for now that is
[17:02] <Saviq> mzanetti, and please bug me whenever that doesn't work, we really need to maintain it working (ideally we'd add a X-build job to unity8-ci for example, except that will be "too late" already)
[17:02] <Saviq> but at least we'll know
[17:03] <Cimi> will finish tomorrow morning for the rest of tests
[17:03] <Cimi> hopefully with dash overview in trunk
[17:03] <Saviq> Wellark, /me loves the padlock icon so much better than SIM Locked...
[17:03] <Saviq> thanks for making it happen!
[17:06] <mzanetti> Saviq: I'm pulling the lockscreen packages atm. you can have the ppa in a minute
[17:06] <mzanetti> Saviq: what padlock icon?
[17:06] <Saviq> mzanetti, when SIM locked, on the indicator
[17:06] <Saviq> mzanetti, you get a small SIM card icon with a padlock on it
[17:07] <Saviq> mzanetti, before it was a label saying "SIM Locked"
[17:07] <Saviq> which kinda pushed other indicators offscreen in Germany ;P
[17:07] <mzanetti> ah right. yeah. that's awesome
[17:07] <Saviq> for xample
[17:07] <Saviq> xample
[17:07] <Saviq> it's a hip kind of an example
[17:07] <mzanetti> I think there was a bug with a screenshot of french :D
[17:07] <Saviq> like xzibit
[17:07] <Saviq> yeah exaactly
[17:07] <mzanetti> which was like a whole book :D
[17:08] <Saviq> bug #1333555
[17:08] <mzanetti> yeah :)
[17:08] <mzanetti> ok... its not much shorter in german either
[17:08] <Saviq> and they stole a nice bug no., too
[17:09] <mzanetti> hehe
[17:09] <facundobatista> Saviq, that's for testing? or you plan to release it soon?
[17:09] <Saviq> facundobatista, testing now
[17:09] <facundobatista> ('overview' in silo 11, I meant)
[17:09] <Saviq> facundobatista, will hopefully release within an hour
[17:09] <facundobatista> Saviq, oh, ok
[17:09] <facundobatista> Saviq, release to devel proposed?
[17:10] <Saviq> facundobatista, well, release to ubuntu, then image build, promotion... who knows
[17:10] <Saviq> facundobatista, so yeah should be in devel-proposed tomorrow
[17:10] <mzanetti> Saviq: ppa free for you btw
[17:10] <Saviq> mzanetti, tx
[17:11] <Saviq> facundobatista, I identified a few things that I believe needs to happen on the server https://code.launchpad.net/~aacid/unity8/dash_overview/+merge/228649/comments/554150
[17:11] <Saviq> facundobatista, I marked them with "[sserver]"
[17:11] <Saviq> well [ssserver] for that matter, Slytherin-style
[17:13] <Wellark> Saviq: <3
[17:14] <facundobatista> Saviq, - wrong images [ssserver]: will incorporate last ones from Joshua
[17:15] <facundobatista> Saviq, - mascot should be gone [ssserver]: which mascot are you talking about?
[17:15] <elopio> mzanetti: shouldn't the dash appear as the first app on the spread view?
[17:16] <mzanetti> elopio: not according to design
[17:16] <facundobatista> Saviq, - background in Results should be gone [ssserver]: yes (actually replacing it with 'logo-overlay-color'
[17:16] <elopio> I see.
[17:16] <mzanetti> elopio: at least not so far... lets see how many more bugs we'll get
[17:16] <mzanetti> elopio: so far the idea is to thread dash the same as any other app.
[17:17] <facundobatista> ah, mascot in the search
[17:17] <facundobatista> mmm
[17:17] <elopio> There are some things that still confuse me. Like not being able to go through all the apps swiping one by one.
[17:17] <elopio> I tend to get stuck swiping between two apps until I realize it
[17:17] <Saviq> facundobatista, mascot in https://lh3.googleusercontent.com/9a4ULEwWTsE45jpIMLPBa8qp94wWrZT3iMhlivLDqxkBEPqpDsoZS6uu81sAJkNxhqLzGQ=w1503-h953 should be gone
[17:17] <elopio> is not a circle.
[17:17] <Saviq> facundobatista, although that might not be you, but the scopes scope?
[17:18] <Saviq> facundobatista, and background is https://docs.google.com/a/canonical.com/file/d/0B32jwBcbaPloMGU4TmR6aVpfRVU/edit
[17:18] <Saviq> facundobatista, the background behind "Nike, Inc." result shouldn't be there
[17:18] <Saviq> facundobatista, or well, have a different colour maybe...
[17:19] <Saviq> facundobatista, since it has to have it according to the dash toolkit, 'cause it has a summary
[17:19] <Saviq> https://f966f709-a-c881af26-s-sites.googlegroups.com/a/canonical.com/unity8dash/scopes/dash-overview/5.results.png
[17:19] <mzanetti> elopio: well, I'm quite positive the current implementation reflects design requirements. Not saying that it would be perfect, but I can't just change things without going through design.
[17:19] <Saviq> facundobatista, that might not be you either, though...
[17:19] <Saviq> biab
[17:21] <elopio> mzanetti: I'm not complaining yet. Just a little confused trying to get used to it.
[17:22] <mzanetti> elopio: :)
[17:23] <mzanetti> elopio: knowing the whole story how the spec evolved I have to say that current state makes the most sense to me too
[17:23] <elopio> mzanetti: yesterday I got the app stuck, it was unresponsive to touches. Today I can't reproduce it, but if it happens again, are there some logs I can get into a bug report?
[17:23] <elopio> the dash app I mean.
[17:23] <mzanetti> elopio: only the dash app or all apps?
[17:23] <elopio> mzanetti: only the dash. The launcher, the indicators and the other apps still worked.
[17:24] <mzanetti> elopio: we have a ~known issue that mouse input (regular touches) get broken while touch input (edge drag gestures) still work
[17:24] <mzanetti> elopio: so the test would not be to only pull launcher/indictors in, but also try to interact with them
[17:24] <elopio> doesn't sound like that because I kept sending sms.
[17:24] <mzanetti> ah ok... so if its only the dash app then yes.
[17:25] <mzanetti> elopio: attach gdb and print a stack trace
[17:25] <elopio> ok, I'll see if it happens again.
[17:25] <mzanetti> ok, cool
[17:27] <facundobatista> Saviq, ok, I understood now; I'll fix those and let you know
[17:40] <dandrader> mzanetti, got time for a chat in mumble?
[17:41] <mzanetti> yes
[18:41] <mterry> Saviq, I notice you seem to track bugs against unity8 in project tasks.  I thought we wanted to try to track them with ubuntu tasks?
[18:41] <Saviq> mterry, except I can't triage/assign ubuntu tasks...
[18:42] <Saviq> mterry, I need to get BugControl, which I don't necessarily agree with...
[18:42] <mterry> Saviq, oh, hah.  hm
[18:42] <Saviq> like sure, I could get BugControl, but getting a blanket perm to triage Ubuntu bugs outside of projects I'm aware of... not entirely agree with
[18:42] <Saviq> and then anyone in the team has the same problem
[18:43] <Saviq> mterry, I'd gladly get rid of either ubuntu or upstream tasks, just didn't come to terms with the above requirement ;)
[18:43] <Saviq> and well, can't get rid of Ubuntu tasks, so it's a check-mate ;)
[18:44] <mterry> Saviq, plus Ubuntu tasks have that nice auto-close-by-bot-with-comment feature and all that
[18:44] <Saviq> trueth
[18:44] <Saviq> mterry, so yeah, ideally I'd like for our team to get traging rights to unity8 (Ubuntu), but that's not possible...
[19:30] <mterry> greyback, heyo!  You still around?  I've managed to bork my qtmir setup on my desktop somehow
[19:31] <greyback> mterry: yeah I'm around. What's happened?
[19:33] <mterry> greyback, I'm getting "UbuntuClientIntegration: connection to Mir server failed." when running unity8 qmluitests  -- do I need to be running a Mir desktop session for such things to work?
[19:33] <mterry> (I may or may not have mucked up my Mir desktop stuff)
[19:35] <greyback> mterry: have you QT_QPA_PLATFORM set to ubuntumirclient?
[19:36] <mterry> greyback, yes
[19:36] <greyback> if yes, I'd unset that
[19:36] <mterry> oh
[19:36]  * mterry wonders what sets that
[19:37] <mterry> greyback, that fixed it
[19:37] <greyback> mterry: cool. Curious what set that env var though
[19:37] <mterry> greyback, me too...  I don't have it in bashrc or anything
[19:53] <Saviq> mterry, it only gets set that on the device by /etc/environment... no idea what could do that on your desktop...
[19:56] <mterry> Saviq, greyback: aha!  I had ubuntu-touch-session installed, which ships a /etc/profile.d/qpa_plugin.sh file
[19:57] <Saviq> mterry, ah, you should not have that installed ;)
[19:57] <mterry> Saviq, but it's such a nice little package
[20:37] <mhall119> can anybody help me understand this exception I'm getting trying to run a scope in the emulator: unity::ResourceException: /opt/click.ubuntu.com/com.ubuntu.developer.mhall119.ubuntucommunity/0.5/ubuntucommunityscope/libcom.ubuntu.developer.mhall119.ubuntucommunity_ubuntucommunityscope.so: undefined symbol: _ZN25UbuntucommunityscopeQuery16progress_handlerERKN4core3net4http7Request8ProgressE
[20:37] <mhall119> https://code.launchpad.net/~mhall119/+junk/ubuntu-community-scope is the code
[20:38] <Saviq> mhall119, you're built against a different version than you have on the emulator most likely
[20:39] <Saviq> mhall119, that's libunity-api0 I'd imagine
[20:39] <Saviq> or libunity-scopes3 rather
[20:40] <Saviq> hmm or somewhere
[20:40] <Saviq> mhall119, #ferrets on canonical's IRC should be able to help
[20:40] <Saviq> mhall119, or #unity-api for that matter
[20:44] <Wellark> Saviq: hey, when switching between scopes in the dash
[20:44] <Wellark> there is this small grey beam
[20:44] <Wellark> which contains four circles
[20:46] <Wellark> should that beam scroll with the rest of the page? it would look much more pleasant to the eye if it would stay still and only the "active" circle would animate a transition
[20:50] <Wellark> is the current behaviour a bug or by design?
[21:07] <Saviq> Wellark, now, scroll the scope page down and then switch to a different scope
[21:11] <Wellark> Saviq: I mean.. open the dash
[21:11] <Wellark> keep your eyes looking at the circles
[21:11] <Saviq> Wellark, yes, but when you scroll it up, that "beam" goes up
[21:11] <Wellark> and swipe to a next scope
[21:11] <Saviq> Wellark, but you can still switch between scopes swiping to the sides
[21:12] <Wellark> and the circles swipe away also
[21:12] <Saviq> Wellark, at which point we'd need to sync the "coming back" of the beam as you start swiping
[21:12] <Saviq> Wellark, which wouldn't be more pleasing than what we have now
[21:12] <Saviq> Wellark, what's more that divider is meant to support different colours as defined by the scope
[21:13] <Saviq> Wellark, meaning we need to switch between light and dark versions of those dots
[21:13] <Wellark> Saviq: sure. that's what Transitions are all for :)
[21:13] <Saviq> Wellark, we discussed this in London two weeks ago, decided it'd be too much movement for little visual gain
[21:14] <Wellark> Saviq: I was proposing less movement
[21:14] <Wellark> or asking about it
[21:14] <Saviq> Wellark, not really, as the dots would move counter to the rest of the page
[21:15] <Wellark> no no, the dots would stay in the vertical center of the screen the whole time. that's what I'm saying
[21:15] <Wellark> now they slide vertically
[21:15] <Wellark> *horizontally
[21:16] <Wellark> we might be talking about different things
[21:16] <Saviq> Wellark, vertical center is between top and bottom, so I assume you mean horizontal center
[21:17] <Saviq> Wellark, but in any case, you need to remember the "beam" as you call it is not static on the page
[21:17] <Saviq> Wellark, it moves up and down, and is not synchronized between the different scopes
[21:18] <Wellark> sure. even better
[21:19] <Saviq> Wellark, IIUC you want the dots to never move to the sides
[21:19] <Wellark> I need to find a video how the similar navigational "dots" function there
[21:19] <Saviq> Wellark, I know how they work
[21:19] <Saviq> Wellark, but they are always statically placed in whatever they navigate between
[21:19] <Saviq> Wellark, this is not the case for the dash
[21:19] <Wellark> Saviq: indeed. the dot's would always stay in the same place
[21:19] <Saviq> Wellark, because as you scroll up/down, they move up/down
[21:20] <Saviq> Wellark, but we don't have where to put them, there's not a place in the dash that's static
[21:20] <Wellark> right
[21:20] <Wellark> I understand the problem in terms of QML
[21:22] <Wellark> but as a user.. :) in the case where I have not scrolled down the scope. I just want to switch betwen them without having scrolled down. and at this scenario the dots moving feels odd if you have ever seen the similar things on android
[21:22] <Saviq> Wellark, it's not a problem "in terms of QML", it's a problem in terms of UX and visual
[21:23] <Saviq> Wellark, you're just looking at one case "I didn't scroll them" and say that's how it should work
[21:23] <Saviq> Wellark, when I have to think about IRL case
[21:23] <Wellark> asking, not telling. :)
[21:24] <Wellark> trying to understand
[21:24] <Saviq> Wellark, what do we do when in the middle of transition left-to-right the "beams" don't line up between scopes? you start drawing stairs? ;)
[21:25] <Wellark> Saviq: oh, they might not line up always?
[21:25] <Saviq> Wellark, what if half of them are on white, the other half on black?
[21:26] <Saviq> Wellark, if you scroll sideways real fast, they don't
[21:27] <Wellark> I must be missing something.. well, anyway. I will "fix it" for you next time we are having a pint in IRL, OK? ;)
[21:27] <Saviq> Wellark, just scroll to the bottom of, say, Apps
[21:28] <Saviq> Wellark, now swipe quickly to either side
[21:28] <Saviq> Wellark, as Apps go off screen to the side, you can still see it not line up with the scope you're getting to
[21:30] <Wellark> sure, but there already is an animation that brings in the header + "beam" of the next scope
[21:30] <Wellark> which is totally fine
[21:31] <Saviq> Wellark, yeah, but the dots, if they stuck to the center, would not "get there" in time to line up with the page you're going to
[21:31] <Saviq> Wellark, aanyway, this will get redesigned from scratch before we meet IRL next so what do you care ;)
[21:32] <Wellark> :D
[21:32] <Wellark> indeed