/srv/irclogs.ubuntu.com/2014/04/30/#ubuntu-unity.txt

=== jhodapp|afk is now known as jhodapp
=== jhodapp is now known as jhodapp|afk
=== mhr3__ is now known as mhr3
tsdgeoshaleluya a merge \o/07:47
tsdgeosSaviq: so which channel do i use for an utopic image? devel-proposed? ubuntu-touch/devel-proposed ?07:52
Saviqtsdgeos, they're the same07:52
Saviqtsdgeos, but the latter is more future-proof07:52
tsdgeosok, i remember someone mentioning a difference07:52
tsdgeosmaybe it was about something else07:52
tsdgeosSaviq: got https://code.launchpad.net/~aacid/unity8/killqt51/+merge/217391 remerged08:03
tsdgeosshould hopefully not conflict anymore...08:03
Saviqtsdgeos, devel vs. devel-proposed is different08:03
tsdgeosah sure08:03
Saviqtsdgeos, devel-proposed == utopic-proposed now08:03
tsdgeosmaybe that was the message about and i misread08:03
Saviqit was == trusty-proposed before08:03
tsdgeosokidoki08:04
Saviqtsdgeos, looks good, no conflict merging on trunk08:04
SaviqMacSlow, I went through your doc, put some comments down08:26
SaviqMacSlow, were you tasked with actually writing that backend?08:27
MacSlowSaviq, thx... will look through them in a few minutes08:27
Saviqthis would get us on the path of maintaining more, instead of less, of that whole system...08:27
MacSlowSaviq, indirectly08:28
MacSlowSaviq, I don't know what else to do to try to fight notifications being abused as dialogs08:29
MacSlowSaviq, it's causing problems08:30
SaviqMacSlow, that fight needs to happen on design level first08:30
SaviqMacSlow, but anyway, I've commented on the doc, this is the time when the api team should take it over, not later08:30
SaviqIMO08:30
MacSlowSaviq, sure... I just needed to start something to get the ball rolling08:31
SaviqMacSlow, kk08:33
Cimitsdgeos, Saviq you know how much data a qt multimedia player uses?09:07
CimiI am trying to look into the source but maybe you know09:07
SaviqCimi, the source won't help you, I really doubt it's static09:07
CimiSaviq, thought might be a percentage09:07
Cimiof the file09:07
Cimior so09:07
SaviqCimi, it's the playback engine that buffers, Qt is only the messenger09:08
SaviqCimi, in our case, it's stagefright09:08
Cimior right09:08
Cimiso what do I do?09:08
Cimiyoutube-alike?09:08
Cimia small progressbar ahead the playback?09:09
SaviqCimi, I asked jhodapp yesterday, but missed him09:09
SaviqCimi, there's http://qt-project.org/doc/qt-5/qmediaplayercontrol.html#availablePlaybackRanges, but it's not exposed to QML09:09
Saviqand I'm not even sure it's supported in our implementation...09:09
SaviqCimi, TBH I'm not sure what bufferProgress is useful for, it's effectively a random 0..1 number that doesn't mean anything...09:11
SaviqCimi, I'd say that warrants a QTBUG09:11
tsdgeosdamn qml is hard sometimes for no reason09:13
CimiSaviq, it is not random09:13
CimiSaviq, can be used for a label imho09:14
Cimi"Buffering 0..15...100%"09:14
tsdgeosso my CardCreatorCache is a singleton which means i have to register it wiht qmlRegisterSingletonType which i can do in main.cpp but where do i do it for tests?09:14
tsdgeosor we need to make Dash stuff a plugin :S09:14
tsdgeosSaviq: ideas? ↑09:15
SaviqCimi, but what does 100% mean in that case - it is random, if you don't know what 100% is09:16
Saviqtsdgeos, make it a plugin, why not?09:16
CimiSaviq, yeah just means the player completed buffering09:16
Saviqtsdgeos, we already have DashViews plugin, maybe we need to recommission it?09:16
CimiSaviq, but is useless09:16
SaviqCimi, exactly09:16
tsdgeosSaviq: ok, let me see if i can add it there09:16
CimiSaviq, I did try it with my slow 3G sim card on purpose09:17
CimiSaviq, and it reaches 100% super quickly anyway09:17
SaviqCimi, yeah, uselesss09:19
CimiSaviq, https://bugreports.qt-project.org/browse/QTBUG-3868809:27
tsdgeosdid i break all the tryXYZ?¿09:29
=== alan_g is now known as alan_g|afk
Cimitsdgeos, where?09:29
tsdgeosunity809:30
tsdgeosok, no it works09:31
CimiSaviq, make progress widget half-wide09:31
CimiSaviq, designs?09:32
=== alan_g|afk is now known as alan_g
SaviqCimi, https://docs.google.com/a/canonical.com/file/d/0B-a_7E3tDxOgVzlJZEdtNEJ3NDQ/edit09:40
mhr3ah, you were faster09:40
CimiSaviq, where can I download spotify for ubuntu touch? :P09:42
SaviqCimi, from the cloud ;)09:42
CimiSaviq, ah in my dreams :D09:43
SaviqCimi, exactly! :)09:43
tsdgeosSaviq: i'll rename the plugin from DashViews to Dash, ok?09:53
tsdgeossince i moved the card creator singleton there09:53
tsdgeosor you prefer to keep the DashViews name?09:53
Saviqtsdgeos, rename away09:58
MacSlowSaviq, I did a quick test and added sound- and haptics-support to notifications (on the frontend) just to see how straight forward it is. Turns out to be pretty easy. If we can agree on a way to pass a haptics-effect-description via a hint, implementing support for sound and feedback won't be that much work. The sound-hint-value is obvious (string representing a filename).10:10
MacSlowSaviq, although I'd rather see modal snap-decisions landing first, before starting something new :)10:12
=== MacSlow is now known as MacSlow|lunch
CimiSaviq, basically it has to have same dimensions of the button?10:24
Cimibut it is still higher than the button10:25
Cimitaller10:25
Cimiit will look weird10:25
SaviqMacSlow|lunch, yeah, I'll tackle modals after SDK lands its unity8 tweak10:26
MacSlow|lunchSaviq, ok10:30
dednickbah, silly utopic upgrade hosed ns lookup!10:30
SaviqMacSlow|lunch, eat your lunch!10:31
SaviqCimi, same size as button10:54
CimiSaviq, done10:54
CimiSaviq, https://code.launchpad.net/~cimi/unity8/half-progress/+merge/21774210:56
Saviqtsdgeos, "use back chevron everywhere" task for dash... it's rather done, isn't it?10:58
CimiI'd center the chevron10:59
Cimithe back chevron10:59
Cimithere is lots of padding on the left10:59
Cimilooks weird10:59
Cimialso, it behaves like a button but has no int of being a button10:59
Cimiit should have a frame around it or something clear to distinguish is clickable11:00
Cimiwhat you guys think?11:00
SaviqCimi, it'll all be a header thing, it will come from SDK11:01
Cimiok11:01
Saviqpete-woods, can you comment on "make infographic configurable" task in https://blueprints.launchpad.net/ubuntu/+spec/client-1410-unity-ui-infographics ?11:01
Saviqpete-woods, is it different than the settings-app task below?11:01
tsdgeosSaviq: yeah i saw that yesterday too11:02
pete-woodsSaviq: well at the moment, it just shows all the infographics you have installed11:02
tsdgeosSaviq: i guess yes11:03
Saviqtsdgeos, ok, marking DONE11:03
tsdgeosSaviq: i think we don't support ultra embedded stuff though11:03
Saviqtsdgeos, huh?11:03
tsdgeoslike a scope embedding a scope embedding a scope11:03
pete-woodsSaviq: in the old infographic, the "settings" were basically just "do you want infographics at all or not"11:03
pete-woodsand that was handled in the shell11:04
Saviqpete-woods, yeah, there's two tasks though:11:04
Saviq[pete-woods] make currently shown infographic configurable: INPROGRESS11:04
Saviq[seb128] add infographic to settings app (similar to background image), only show settings if not explicitly prevented (by OEM): TODO11:04
tsdgeosSaviq: and a preview embedding a preview11:04
tsdgeosbut should not be hard to fix11:04
tsdgeosonce somebody needs it11:04
tsdgeosso yeah mark it as DONE11:04
Saviqtsdgeos, and a different task anyway11:04
pete-woodsSaviq: I guess what I'm saying is that I made it so you can pick your infographic from a list of installed ones, it just uses them all11:05
Saviqpete-woods, sure, we just want the task clarified (see kgunn's question in whiteboard), as we're not sure what that task entails?11:05
pete-woodsif we need to make it "configurable" (obvs I'd like to know exactly what that means), then I'll do that11:06
pete-woodsSaviq: I have no idea what it means11:06
pete-woodsI didn't add that task (unless my brain is totally fried)11:06
Saviq:D11:08
Saviqpete-woods, guess what, I added it ;)11:08
pete-woods:)11:09
Saviqpete-woods, I think I copied it from the old blueprint11:10
pete-woodshmm11:10
pete-woodsthat would make sense11:10
Saviqhah!11:10
pete-woodsI still don't know what it means, though11:10
Saviqthostr_, added it initially :D11:10
pete-woodsit probably came from a whiteboarding session11:10
Saviqthostr_, "make currently shown infographic configurable: TODO", what does that mean? :)11:11
thostr_Saviq: assume you have 10 infographics installed11:11
thostr_which one to display?11:11
thostr_I think it can be as easy of just remember the last one that was shown11:12
thostr_as the user can anyway swipe through all infographics on the greeter11:12
thostr_at least that was the plan AFAICT11:12
pete-woodsthostr_: there's a slight complication, in that some infographics can produce more than one SVG11:13
Saviqthostr_, so you mean to remember the last displayed one?11:14
Saviqthostr_, because there's also:11:14
Saviq[seb128] add infographic to settings app (similar to background image), only show settings if not explicitly prevented (by OEM): TODO11:14
pete-woodse.g. infographics that iterate through all the data of a particular "type", like the timeseries data from the usermetricsinput libraru11:14
Saviqthostr_, could you reply in the bp whiteboard please https://blueprints.launchpad.net/ubuntu/+spec/client-1410-unity-ui-infographics ?11:14
thostr_Saviq: done.11:25
thostr_pete-woods: from practical POV wouldn't it be ok to ignore the fact that one infographic has "subgraphics"?11:26
pete-woodsthostr_: sure, we could just remember the producer of the particular SVG we were looking at, and remember that11:26
thostr_pete-woods: in the end, the purpose and user interaction is the same: browsing through different graphics11:26
Saviqthostr_, thanks11:27
thostr_pete-woods: yes, we'd remember producer + index11:27
pete-woodsthostr_: from my perspective, I just want to know what behaviour is wanted (and for that behaviour to be fairly simple)11:27
Saviqpete-woods, why couldn't we remember the actual "subgraphic"?11:27
pete-woodsSaviq: sure, we could do that, too11:27
thostr_pete-woods: then let's do that11:27
pete-woodsthostr_: so are we looking for a settings panel for this? or just remembering the last viewed infographic?11:28
pete-woodsthe panel would seem redundant to me, but obviously it's not my choice11:29
thostr_pete-woods: I'd just remember the last one11:29
pete-woodsas long as that's my official requirement, then I'm happy11:29
pete-woodsi.e. let's make sure the blueprint says that's what I have to do11:29
thostr_pete-woods: alternative would be: from all the installed infographics, the setting would define which ones to make available to greeter. one the greeter itself we'd remember the last one.11:30
pete-woodssure, I don't really care *too* much, I just want to know what I have to implement11:30
thostr_pete-woods: I'll drop a mail to design11:31
greybackIs it known issue that flicking vertically in the dash is weird. The velocity on finger release doesn't look right11:42
greybacktsdgeos: ^^11:43
Saviqpete-woods, that'd be our task then11:43
tsdgeosgreyback: nothing specifically on finger release, no11:43
Saviqpete-woods, I don't think we need to remember it across reboots? thostr_?11:43
pete-woodsSaviq: sure, just need to know exactly what to do11:44
pete-woodsSaviq: thostr_ has sent an email to John about it11:44
pete-woodswe could easily store this in a GSetting11:44
pete-woodsit doesn't have to be visible in the settings app11:44
Saviqpete-woods, indeed11:44
Saviqpete-woods, only potential issue would be that if we'd store index, it could be a different one, otherwise if we store a name, we'd need to look for it in the model every time...11:45
Saviqpete-woods, but yeah, we'll manage somehow11:45
greybacktsdgeos: I should have said /after/ finger release. Sometimes it appear to accelerate a little after finger release, before it starts to decelerate11:45
pete-woodsSaviq: the model internally is stored as infographic-name/hash11:46
greybacktsdgeos: might just be me11:46
pete-woodswhere the hash is computed consistently from the data source name11:46
Saviqpete-woods, mhm11:46
pete-woodsso a simple index would remain valid only as long as you didn't add more sources11:47
pete-woodsbut yeah, we could figure something out, I'm sure11:47
pete-woodsthe only real question, as far as I'm concerned, is if we want the settings app to allow the user to enable / disable different infographics11:48
pete-woodsor if we should just say you have to uninstall them11:48
pete-woodsSaviq: thinking about it, we could just store the hash prefix of the filename, that would never change as long as that data source was present, then on first load we could just search through the list of SVGs for that one11:51
Saviqpete-woods, yeah, "search through the list" is what worries me ;)11:53
Saviqpete-woods, and it's not on first load, but on every load, 'cause we're destroying the greeter when it's not on screen11:54
pete-woodsSaviq: well you'd only have to search through the SVGs for a single infographic, as you could store that, too11:54
pete-woodsbut sure, it's something to be aware of11:55
Saviqpete-woods, yeah, we'll get there once we know the requirements11:55
pete-woodsyep11:55
SaviqCimi, wanna do changes to infographics?11:55
CimiSaviq, sure11:57
CimiSaviq, doing the card touch down effect11:57
Cimiwil be finished before the standup11:57
SaviqCimi, make sure to not conflict with tsdgeos's changes to how cards are created, where are you doing the touchdown?11:58
CimiSaviq, Card.qml11:58
SaviqCimi, then don't11:58
seb128Saviq, where is that workitem coming from? I've no recollection discussing that topic/taking that action item11:59
SaviqCimi, Card.qml is going away11:59
Saviqseb128, https://blueprints.launchpad.net/ubuntu/+spec/client-1410-unity-ui-infographics11:59
CimiSaviq, ah cool11:59
seb128Saviq, did somebody volunteer me without tell me?11:59
seb128telling11:59
Saviqseb128, possibly :)11:59
Saviqseb128, it's for "later" currently, not hugely important11:59
seb128k11:59
Saviqseb128, should probably be blocked on design, actually12:00
SaviqCimi, so, new infographics → silo 01012:01
seb128Saviq, yeah, we need design for that ... we also need to know if users are going to be able to select a bg image for the dash again to update the design12:01
Saviqseb128, indeed12:01
SaviqCimi, the backend part is https://code.launchpad.net/~unity-team/libusermetrics/file-based-infographics/+merge/2140212:02
CimiSaviq, let me finish the touchdown before12:02
SaviqCimi, didn't I say "don't"?12:02
Cimitsdgeos, where is your refactoring branch for how cards are created?12:02
SaviqCimi, Card.qml is going away ;)12:02
SaviqCimi, shelve it for now, wait until that refactor is done12:03
Cimiok12:03
SaviqCimi, net result is that we get a model of svg filenames to display, and switch between them by double-tap12:03
SaviqCimi, probably a fade-out+fade-in is in order12:03
Saviqpete-woods, you said there's command line to fake data for infographics?12:04
pete-woodsSaviq: yeah, the usermetricsinput command12:04
seb128Saviq, my emails tell me you volunteered me for that workitem a week ago ... ;-)12:04
Saviqseb128, ha! not true ;) it was in https://blueprints.launchpad.net/ubuntu/+spec/client-1303-unity-ui-infographic before12:05
seb128Saviq, anyway, good that mentioned it, I didn't notice it due to the batch of changes in unity8 blueprints, I just mark them read12:05
seb128oh ok12:05
seb128well, at least I know about it now ;-)12:05
pete-woodsSaviq: if Cimi is working on this, them I'm sure we can communicate to get the right information across12:05
pete-woods*then12:05
Saviqpete-woods, yup, I'm sure, too :)12:05
Saviqseb128, thostr_ volunteered you last July ;), it was even targeted for 13.08 milestone :D12:06
seb128Saviq, k, maybe I knew about it back then, it has been a while, lot going on ... ;-)12:08
Saviqindeed12:08
Saviqseb128, got POSTPONED soon after, and got back again very recently12:08
seb128k12:08
seb128thanks for the status update!12:08
=== MacSlow|lunch is now known as MacSlow
karnialecu: elopio: I think that is exactly what I needed http://developer.ubuntu.com/api/devel/ubuntu-14.04/cplusplus/unity-scopes/index.html#scopetesting12:30
karnialecu: what did you mean by getting rid of 'qtisms' from the scope code?12:31
=== jhodapp|afk is now known as jhodapp
alecukarni: we have qt's signals and slots in too many layers of the code12:31
alecukarni: we'd like to move them lower, so they are only in the layer that uses qnetwork12:32
karnialecu: I see12:32
alecukarni: and, after that, we'll probably replace qnetwork with netcpp12:32
karniinteresting!12:33
karnisuppose I have a reference to CategorisedResult - how do I set arbitrary result data on it, other than set_{uri, title, art, dnd_uri} ?12:56
karnik, that was easier than expected. always answering my questions ;) result["price"] = Variant(price.toStdString());12:56
mhr3karni, you're welcome :)12:57
karnimhr3: hehe. I thank my rubber duck ;D12:57
mhr3karni, btw solved your yesterday's QMirServer... crash?12:58
karnimhr3: yes, just install unity8-fake-env :)12:58
karnimhr3: I actually told you yesterday, maybe you missed it12:58
mhr3karni, i guess, didn't see it12:58
karnimhr3: Saviq knew the answer from the top of his head, known issue12:58
tsdgeosCimi:  lp:~aacid/unity8/dynamic_specialized_cards12:59
mhr3Saviq, is that cause something from scope-tool imports the app manager?12:59
Saviqmhr3, yeah :(12:59
Saviqmhr3, DashApps12:59
mhr3Saviq, hm, shouldn't those be instantiated only if you have click scope running?12:59
Saviqmhr3, if you launch the tool manually with no options13:00
Saviqmhr3, and you have click scope installed13:00
mhr3but karni was launching it via sdk13:00
mhr3that should launch just the one scope13:00
Saviqthen yeah, should not happen13:01
karnicorrect. but because there's no redirect of scope debug output, I'm back to launching it from CLI13:01
mhr3oh well, adding todo to look at it13:01
Saviqmhr3, actually we're importing it in GenericScopeView13:01
Saviqmhr3, but anyway13:01
mhr3Saviq, that explains it then13:01
Saviqmhr3, it can only happen if you have libunity-mir1 installed already13:02
Saviqmhr3, it doesn't pull -fake-env then, otherwise -fake-env is default13:02
mhr3i see13:02
mhr3anyway, lunch /me bbiab13:02
* Saviq biab, too13:03
paulliuDo I have any method to get the console log of unity8 running on phone?13:23
kgunndandrader: greyback just a note, the input dispatcher stuff landed on mir dev branch, is there anything else you want landed before we tag & promote the next one?13:28
kgunni'd like the next promotion to have all you need for qt comp13:28
greybackkgunn: unfortunately I mis-understood. One more branch is needed for qt comp, which isn't proposed yet13:28
kgunnhope to land 0.1.9 today, mir team have like 1 more branch to land then we're gonna go to 0.2.0 <- so that'd be the one i hope for13:28
dandraderkgunn, we need the other input stuff anpok is currently working on13:29
kgunnok13:29
kgunntsdgeos: i know you're still working on some of the card loading optimization...but we landed some optimization for the scope scrolling correct ?13:39
tsdgeoskgunn: scope scrolling effect?13:40
tsdgeosas in "it's jaggy"?13:40
kgunnyes :)13:40
tsdgeoswe landed some small stuff back then13:40
tsdgeosbut what i have now is better13:40
kgunngot it13:40
tsdgeosjsut unfinished13:40
kgunnmterry: were you wanting to target split greeter for landing? or am i making stuff up ?13:44
kgunn...maybe it was just retarget at utopic13:44
mterrykgunn, I'm waiting on blocker branches to land -- we need a small telepathy-service fix (should poke someone for that today), a QA test harness fix, and a Mir fix13:45
mterrykgunn, but I did want to retarget for utopic13:46
kgunnmterry: ....oh is that all ...lol, short list i see13:47
mterrykgunn, it keeps growing as the changes happen around split branches  :-/13:48
kgunni know...it's like trying to cross a highway as a pedestrian13:49
mterrykgunn, from Mir side, a solution for bug 1313832 would help us get around a design feedback problem13:49
mterryNo bot?13:49
mterryhttps://bugs.launchpad.net/ubuntu/+source/mir/+bug/131383213:49
kgunni know...13:49
kgunnhmmpf13:49
paulliutsdgeos: Fixed the pan over the bound problem. https://code.launchpad.net/~paulliu/unity8/zoomImage/+merge/20794113:53
paulliutsdgeos: please re-review it.13:53
tsdgeospaulliu: cool, will try to find time later today13:53
paulliutsdgeos: ok. Thanks a lot.13:53
paulliuSaviq: so should I move the Logout dbus interface to unity8/plugins/Unity/Logout ?13:58
Saviqpaulliu, as I said in the MP, I don't really care :D, decide within yourselves13:58
paulliuSaviq: ok. Got it!13:58
Saviqpaulliu, name it unity8/plugins/Unity/Session or unity8/plugins/Session, not Logout :)14:01
paulliuSaviq: ok.14:01
mhr3dpm, ping?14:06
mhr3dpm, do the scopes docs on duc still auto update? and from utopic?14:07
mhr3dpm, and how often? :)14:07
karniIs there any limitation on how many text fields I can put into a preview? seems 4th one doesn't want to show up. http://paste.ubuntu.com/7366536/14:10
dpmmhr3, otp, can you check with mhall119 in the meantime?14:11
karninvm, line 30, s/remarks/store14:11
mhr3mhall119, ^^^?14:12
mhr3karni, and again, you're welcome :)14:12
mhr3you use this channel as your debug teddybear14:13
karnimhr3: I should shut myself with rubber duck in a room, and only leave 1 hour before EOD. I would probably stop talking at all ;D14:13
Saviq;D14:13
mhall119mhr3: in UE Live! broadcast, will come back and read the backlog in a bit14:18
CimiSaviq, pete-woods is there a doc of infographics without reading the merge review?14:25
pete-woodsCimi: there are docs, but as far as I'm aware they are wrong14:32
pete-woodsCimi: the shell facing API is essentially a list of SVGs as strings14:32
pete-woodsand you need to move through them on double tap14:32
Cimiok14:33
pete-woodsCimi: https://docs.google.com/a/canonical.com/document/d/1VajNkWbBH61iVixXJAmOvNGiG__GWQTMXGNOZijXWJw/edit#heading=h.uvcw591kzumb14:33
pete-woodsbut as I say, that doc is very different to what Mark has asked for14:33
=== alan_g is now known as alan_g|tea
pete-woodsCimi: the only input the API needs is the user's UID14:35
pete-woodswhich is just a plain old property14:36
mhall119mhr3: currently scopes API docs don't auto-update, but we can change that14:36
mhall119mhr3: I have a script and the server has an API, we just need to get it integrated into your workflow so that it gets run whenever you have a successful build14:37
mhr3mhall119, i thought it's hooked to the pkg in distro/14:39
mhr3?14:39
mhall119mhr3: nope14:40
mhr3mhall119, any reason why not do that?14:41
mhall119it could be, I suppose, the script can be run anytime as long as the doc files are available, but I don't have the knowledge/access to do the hooking14:41
mhall119I'll gladly provide the script and instructions on on using it to anybody who can do that though14:42
mhr3mhall119, so none of the docs auto-update?14:43
=== alan_g|tea is now known as alan_g
mhr3from talking to dpm i thought this stuff is automated14:43
=== dandrader is now known as dandrader|afk
mhall119mhr3: not curretly, no, I wrote the code to allow it to happen, but I need somebody involve in each project's workflow to actually put the pieces together14:48
mhr3saviq, should https://bugs.launchpad.net/unity-scopes-shell/+bug/1260020 be retargetted to unity8?15:00
Saviqmhr3, it probably should just be marked fixed?15:02
mhr3saviq, do we have an ap test for it now?15:02
=== dandrader|afk is now known as dandrader
Saviqmhr3, no15:02
mhr3saviq, in that case it isn't fixed15:02
Saviqmhr3, no, that bug is fixed - there's another that there isn't a test, but it's not a unity8 bug either ;)15:03
mhr3the plugin passes a string to shell, it doesn't know if shell is able to do something about it15:03
Saviqmhr3, but a ubuntu-integration-tests one ;)15:03
mhr3saviq, ow, for a moment i thought such a thing actually exists15:04
Saviqearly EOD today, see you tomorrow15:32
=== jhodapp is now known as jhodapp|lunch
mhr3saviq, seeing some slowness when previewing albums15:59
mhr3saviq, and i'm wondering whether we didn't do async stuff properly, or whether it's qml16:00
mhr3saviq, but i guess all those Audio{} elements could be it16:00
dednickSaviq: you've updated to utopic?16:11
alesagefinding that my unity8 upstart scripts are unresponsive while trying to run an autopilot test, how to debug?16:24
alesagethe logs in .cache/upstart appear untouched16:24
alesageevil sorcery afoot16:24
mhr3dpm, i set auto transl exports for scopes scope16:26
mhr3apparently i don't have permissions to do it for the rest :/16:26
=== dandrader is now known as dandrader|lunch
dpmmhr3, awesome, thanks. Which one is the one you need permissions for?16:50
mhr3dpm, -mediascanner16:50
=== dandrader|lunch is now known as dandrader
=== jhodapp|lunch is now known as jhodapp
dpmmhr3, ok, let me see who's the maintainer for that project...17:41
mhr3dpm, jamesh is17:42
dpmmhr3, he's probably not around now, is he? I'm away tomorrow, could you follow up with him to set the exports branch tomorrow?17:43
mhr3dpm, sure, will do17:43
* mhr3 out17:43
dpmexcellent, thanks!17:43
=== dpm is now known as dpm-afk
kgunngreyback: you thinkin' much about how to optimize the side channel ?19:17
kgunnor is it just b/c we've glommed onto life cycle19:17
kgunnthat it seems to lag a bit19:17
greybackkgunn: it's laggy? How19:21
Saviqdednick, yes19:21
kgunnwell..so there's the video case...19:21
Saviqmhr3, there's only one Audio {} element per preview19:21
kgunnbut then also, i was just noticing on a game like wind (or whatever its called)19:22
Saviqmhr3, or well, per audio widget (but there's only one)19:22
kgunnyou put it to the back i was "killed"19:22
kgunncause it keeps rendering for a bit19:22
greybackkgunn: it's per-app, they need to support being told you've been made hidden or not19:22
greybackit may not be rendering, but the logic is still moving19:23
greybackif not supported, only the lifecycle sigstop actually stops the logic19:23
kgunngot it19:23
greybackso yeah, need a list of those apps to fix19:24
greybackkgunn: I guess the PPA is built with it?19:24
* kgunn thinks...this is going to be one of those not so fun, fun things19:24
kgunnyes~19:24
kgunnor i meant yes! (with excitement)19:24
greybacknice try..19:24
kgunni'm done with manual testing on n4 & n10...just need to run thru AP testing...then i'm done19:25
kgunnits looking good...same as before19:25
greybacksweet19:25
kgunni noticed you can get grooveshark into more f'd state than before :)19:25
kgunnbut its not us19:25
kgunnone other bug i notice, gallery/camera combo can get into a bad state...but only on n10, n4 works like a champ19:26
kgunnnot sure if the camera subsystem is good on n10 ?19:27
kgunnor if its known to have issues...19:27
greybacknor am I, sorry19:27
kgunni'll log a bug, but i don't think its our issue19:27
kgunngreyback: back to the educating apps...do we just need to broadcast this http://qt-project.org/doc/qt-5/qwindow.html#visibility-and-windowing-system-exposure19:33
kgunnvia the sdk team?19:34
kgunnor what are your thots ?19:34
kgunn...wonder if apps do like a weekly video...19:34
kgunnmhall119: ^ thots on that ?19:35
kgunn"that" being best/good ways to communicate to app developers they need to consider their occlusion wrt state19:36
greybackkgunn: this is the property in QML to listen to: https://qt-project.org/doc/qt-5/qml-qtqml-qt.html#application-prop19:36
kgunnah sorry...the one i did was for native19:36
kgunni suppose19:36
greybackkgunn: it's a really a per-app thing, so yeah the only choice is t oeducate developers19:36
greybacknot much the SDK can do, aside from documenting clearly that devs should use it19:37
greybackso some sort of "hey guys, please update our apps to react to Qt.application.state property" publicity would be important19:38
mhall119kgunn: sorry, can you tl;dr that for me?20:05
kgunnmhall119: finding some apps that aren't paying attn to having focus/visibility....in these cases, you can (depending on the app)20:09
kgunnget a sense of lag, since they're "stopped" by life cycle, rather than themselves...thru "doing the right thing" by reacting programmitcally to20:10
kgunnhttps://qt-project.org/doc/qt-5/qml-qtqml-qt.html#application-prop20:10
=== dandrader is now known as dandrader|bbl
kgunn..before, blocking swap buffers kinda hid this, but with non-blocking swap on its way to archive..some apps ignoring this will exhibit said behavior20:11
kgunnso...what's the best way to educate mhall119 ?20:11
mhall119kgunn: I'm afraid you're gonna have to dumb it down even more than that for me, what would a QML app need to do with this propery and why?20:25
greybackmhall119: an app can have logic running continuously, yet is is not visible on screen. e.g. a game20:41
greybackmhall119: currently that's not a problem, as due to implementation details, when app was not visible, that running logic was forcibly stopped.20:42
greybackbut that forced stop has consequences - one example being unable to adjust music volume when screen is off20:42
greybackor next track failing to load, again with screen off20:43
greybackso we have decided that forced stop is not desirable20:43
greybackas a result, now if an application is not visible, it's internal logic continues to run20:43
greybackthere are times when an app developer may not want that to be the case however - take a game20:44
greybackso the Qt.application.state property is what developers should write code to listen to, and when it is set to inactive, the internal logic should be paused, until that property set to running again20:45
mhall119greyback: hold on, we decided that force stop isn't desirable now?20:46
greybackmhall119: note, this is very different to the app lifecycle system20:47
mhall119ok, now I'm *more* confused....are we going to allow apps to continue running when they don't have focus on phone, or not?20:48
greybackmhall119: for this conversation, app lifecyle is not effected. Apps are suspended and resumed as they are now20:49
greybackmhall119: this is to deal with other situations where apps are not suspended, but need to pause their internal logic for other reasons20:49
greybackexample case: you're playing a game, and you open your indicators - that should pause the game20:50
greybackgame is not lifecycled20:50
greybackbut it still should pause, as the user is interacting with the indicators, not the game itself20:50
greybackthe second use-case is that there is a 3 second delay from app being made invisible, to app being lifecycle suspended20:51
greybackso for a game, it has proceeded 3 seconds further, without the users knowledge20:52
greybackmhall119: those problems make sense to you?20:53
mhall119greyback: ah, yes, ok, so instances where the app isn't in the background, but still isn't necessarily visible20:53
greybackmhall119: right20:53
mhall119and the answer is to do what, exactly?20:54
greybackhttps://qt-project.org/doc/qt-5/qml-qtqml-qt.html#application-prop <- this property notifies the app if it is in foreground or not20:55
=== _salem is now known as salem_
mhall119nitpick: http://developer.ubuntu.com/api/qml/sdk-14.04/QtQml.Qt/#application-prop we have those docs :)20:56
greybackwe should have app writers know about this property, so that they can pause their internal logic if their app is not visible/visible20:56
greybackmhall119: those docs are old. We're using Qt5.2, those are 5.0 docs20:56
mhall119is there any way to pause internal logic for them, by default, and allow them to override the behavior if they want something to keep running?20:56
greybackmhall119: no20:56
mhall119greyback: ubuntu-sdk-14.04 framework has Qt 5.2?20:57
greybackmhall119: the phone trusty image is running qt5.2, that's all I know20:57
mhall119ok, I'll make a note to myself to update the docs then20:57
mhall119so app developers need to Connect that propery to a handler function, correct?20:58
greybackmhall119: so there's a reason I'm telling you this now. We're making a change in Mir, with the result that app which do _not_ listen for Qt.applicaiton.state changes, will keep running20:59
greybackright now, they just stop (due to implementation details)20:59
greybackbut soon, they won't20:59
mhall119ok, so best thing we can do is to get bzoltan to change the QML template to add this connection and a handler function that does nothing, but has comments explaining what should be in it20:59
mhall119that should make it obvious for new apps21:00
greybackI suppose so yes21:00
mhall119popey can let the Core Apps developers know about the pending change and for those that have something to pause they can implement it21:00
greybackgreat21:00
mhall119for the rest, we can blog about it21:00
mhall119add a short guide or "cookbook recipe" to the devportal too21:01
greybackyeah, just need to get the word out there. The apps which are badly behaved will be noticed pretty quick21:01
mhall119yup21:01
mhall119we can pre-emptively add an askubuntu question with answer too21:01
mhall119can you email popey and I with an example of what the QML code for an app would need to be?21:02
greybacksure21:03
mhall119thanks21:03
=== jhodapp is now known as jhodapp|afk
=== salem_ is now known as _salem
Saviqgreyback, we won't be SIGSTOPing apps??21:51
greybackSaviq: we are21:53
greybackSaviq: this is the render thread blocking thing. New Mir won't block render thread any more, so the GUI thread is not blocked. But some apps were relying on that blocking21:54
Saviqgreyback, yeah well, they'll only have 5s or so to do their business anyway :)22:03
Saviqbut yeah, sure, they should know about us suspending them22:03
=== dandrader|bbl is now known as dandrader
=== _salem is now known as salem_

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!