[05:23] <dpm> good morning all
[06:27] <dpm> good morning gusch, thanks a lot for the Weather app reviews yesterday. Just a quick heads up that we're going to start the Weather app hackfest in about ~1h 30 today, so there might be other branches to review or things to discuss on the channel - http://developer.ubuntu.com/2013/07/announcing-the-ubuntu-core-apps-hack-days/
[06:28] <gusch> dpm: ok - I'm here ;)
[06:29] <dpm> excellent, thanks! :-)
[06:32] <dpm> bzoltan, bzoltan1, timp, good morning! A number of core apps have been hit by bug 1201094 due to recent changes in the SDK. Do you think you could add a comment with some guidelines on how to fix it?
[06:32] <ubot2`> Launchpad bug 1201094 in Ubuntu Weather App "App content visible behind tab header" [High,In progress] https://launchpad.net/bugs/1201094
[06:32] <bzoltan1> dpm: let me see
[06:32] <bzoltan1> dpm: but it feels like the desk of timp
[06:33] <dpm> ok, will check with him when he's online
[07:17] <dholbach> good morning
[07:48] <oSoMoN> gusch: hey, https://code.launchpad.net/~osomon/webbrowser-app/transparent-header/+merge/174716 can now be tested (CI succeeded)
[07:48] <gusch> oSoMoN: ok, thx
[07:57] <gusch> oSoMoN: approved
[07:58] <oSoMoN> gusch: thanks
[08:31] <dpm> hi timp, around?
[08:33] <timp> dpm: yes
[08:34] <dpm> timp, morning! Zoltan suggested you'd be the best person to answer this: a number of core apps have been hit by bug 1201094 due to recent changes in the SDK. Do you think you could add a comment with some guidelines on how to fix it?
[08:34] <ubot2`> Launchpad bug 1201094 in Ubuntu Weather App "App content visible behind tab header" [High,In progress] https://launchpad.net/bugs/1201094
[08:41] <timp> dpm: ok, I added a comment. I am now working on bug 1201452
[08:41] <ubot2`> Launchpad bug 1201452 in Ubuntu UI Toolkit "[pageStack] PageStack does not save page state" [Critical,In progress] https://launchpad.net/bugs/1201452
[08:41] <timp> dpm: when I finish I'll check your bug, or perhaps Kaleo is around then and he'll check it first
[08:42] <dpm> ack, thanks timp
[08:45] <JamesTait> Good morning all, happy Corn Fritter Day! :-D
[08:46] <timp> Kaleo: ^perhaps you can have a look at bug 1201094? Otherwise I will, later today
[08:46] <ubot2`> Launchpad bug 1201094 in Ubuntu Weather App "App content visible behind tab header" [High,In progress] https://launchpad.net/bugs/1201094
[08:47] <m-b-o> timp: Kaleo: oh yes, please :)
[09:00] <WebbyIT> there is someone of weather app?
[09:01] <timp> WebbyIT: you have lousy weather and you need someone to blame? ;)
[09:02] <WebbyIT> timp: yes, something like this :P
[09:06] <m-b-o> WebbyIT: here is sunshine
[09:06] <WebbyIT> m-b-o: here it rains, at least there is a little 'fresh
[09:06] <timp> WebbyIT: ah. if the IT in your name means what I think it does, then in general you shouldn't have too much to complain about the weather :)
[09:07] <WebbyIT> timp: yeah, there is the game of the double meaning I.T. / Italy :D
[09:08] <timp> WebbyIT: your ircname gave it away :)
[09:15] <m-b-o> WebbyIT: approved :)
[09:44] <timp> popey: your weekdays and dates are not in sync
[09:48] <dpm> hi m-b-o, thanks for joining the hackfest! :-)
[09:48] <popey> oof
[09:48] <m-b-o> hi dpm :)
[09:48] <popey> thanks timp ☻
[09:49] <timp> popey: np. I'm impressed by your smiley ;)
[09:49] <timp> err.. emoticon is the correct term
[09:51] <timp> ah. those are the \u-codes I some times see when I run my irc client on a freebsd machine. when it runs in ubuntu I see what it actually means
[09:51]  * timp slowly transitioning to the 21st century
[09:53] <popey> ㋛
[09:57] <m-b-o> WebbyIT: are you around?
[09:59] <WebbyIT> m-b-o: yap
[10:00] <m-b-o> WebbyIT: https://bugs.launchpad.net/ubuntu-weather-app/+bug/1198541 I would not try to solve this (if you have intended to do so)
[10:00] <ubot2`> Ubuntu bug 1198541 in Ubuntu Weather App "Location results should also show state names for better clarity" [Undecided,Confirmed]
[10:01] <m-b-o> it can't be solved with openweathermap api, and it's possible that the weather data provider will change
[10:01] <WebbyIT> m-b-o: ups, wrong correlation between branch and bug
[10:02] <m-b-o> ah, ok :)
[10:03] <WebbyIT> m-b-o: thanks for letting me know :)
[10:04] <timp> who does the design for the calendar-app?
[10:11] <JamesTait> dholbach, just a heads-up, it seems I got my wires crossed wrt app categories - what we have in SCA (and thus Click Index) is freedesktop.org categorisation, rather than Debian control file sections.
[10:11] <dholbach> aha
[10:11] <dholbach> and is that what was used before? does that come from .desktop files?
[10:12] <JamesTait> dholbach, so what we have is http://standards.freedesktop.org/menu-spec/menu-spec-1.0.html#category-registry as opposed to http://www.debian.org/doc/debian-policy/ch-archive.html#s-subsections
[10:13] <dholbach> I don't know who all needs to be informed about this - do we get the data from .desktop files? click manifest? entered in myapps registration form?
[10:13] <JamesTait> dholbach, yes, that's in the .desktop files.  I'm not sure where the data in SCA comes from - whether it's entered manually or extracted from the .desktop file
[10:14] <JamesTait> dholbach, but when Argentina comes online I'll probably be able to get an answer pretty quickly.
[10:14] <dholbach> great - it'd be good to bring it up on the mailing list as well, so everybody's aware
[10:15] <dholbach> and we can get the categories use-case sorted out end-to-end :)
[10:15] <JamesTait> dholbach, I suspect they'll be entered manually, at least at this stage - I don't *think* we're doing any automatic extraction of anything yet, but it may be existing infrastructure from Software Centre.
[10:16] <JamesTait> dholbach, I'll drop a mail to the list anyway, yes. :)
[10:19]  * dholbach hugs JamesTait
[10:24] <JamesTait> dholbach, the Department and Categories fields are selected from drop-downs by the dev when they're uploading their app, in the "Finding your app" step of the upload.
[10:25] <dholbach> ok and the list is put together by using the stuff from the menu spec?
[10:25] <JamesTait> dholbach, for now, at least - later on we can extract a lot of the data that's currently in those forms from the uploaded file itself.
[10:25] <dholbach> ok
[10:26] <JamesTait> dholbach, I'm not sure who put the list together, but it does look that way.
[10:26] <dholbach> ok cool
[10:28] <JamesTait> dholbach, as regards Debian sections, I'm not sure if they're relevant to Click Packages - I suspect not, because Click Packages aren't (AIUI) part of the apt archive, which is why we have the Click Package Index and all that. ;)
[10:28] <dholbach> sure, I just wasn't sure how things worked
[10:29] <JamesTait> dholbach, I get that a lot too. :)  I'm not *at all* familiar with a lot of the desktop stuff.
[10:29] <JamesTait> But it's all starting to click together now.
[10:29] <dholbach> :)
[10:29] <JamesTait> See what I did there? ;)
[10:29]  * JamesTait needs tea.
[10:30] <dpm> lol
[10:30] <dholbach> :)
[12:15] <dpm> popey, I seem to remember you wrote some instructions to install and test core apps from bzr in the wiki, but I don't seem to find them. Do you happen to have the link handy?
[12:16] <popey> hmm, i did.
[12:17] <popey> i think the document I created was pasted into this, used by the design team, and maintained by callum.. https://docs.google.com/a/canonical.com/document/d/1P0rHOk8muyI3GHHE_CBj0whetzUcoa_7gUhxpxjJG6A/edit
[12:21] <dpm> popey, yeah, looks like it. So the public wiki page was removed? :/
[12:32] <dpm> ah, it wasn't removed: https://wiki.ubuntu.com/Touch/CoreApps/InstallingTesting
[12:53] <Kaleo> timp: I'll leave it to you
[13:39] <mhall119> fginther: ping
[13:39] <fginther> mhall119, pong
[13:40] <mhall119> fginther: would it be possible to make and upload core apps packages to precise without having to run autopilot on them, if autopilot runs and passes for other releases?
[13:42] <fginther> mhall119, yes, that's what were currently doing. We only run autopilot tests on raring, but we upload all 4 series if everything passes
[13:44] <mhall119> fginther: ah, didn't realize we had that going now
[13:44] <fginther> mhall119, we do a package build test on all four series
[13:44] <mhall119> thanks
[13:45] <fginther> mhall119, autopilot has only been enabled for 2 packages which started with 100% passing tests
[13:45] <fginther> mhall119, other packages have tests, but they didn't initially all pass. These are being re-evaluated as fixes are mede.
[13:47] <dpm> mhall119, yeah, I just noticed that after the conversation with Francis: we've already got daily packages for core apps for 12.04 in the PPA
[13:54] <timp> Kaleo: okay
[13:59] <mhall119> dpm: just published http://mhall119.com/2013/07/ubuntu-weather-app-hackfest/
[13:59] <dpm> nice, thanks mhall119!
[13:59]  * dpm promotes
[14:12] <krinye> Hello
[14:12] <krinye> I don't know if I am in the right place
[14:12] <krinye> my name is Kris, I am from the University of Toronto, I was looking for more information about the ubuntu app hackathons
[14:13] <mhall119> krinye: you are indeed in the right place :)
[14:13] <krinye> I believe the weather one is the one people are working on this next
[14:13] <mhall119> krinye: yup, there are some bugs that need fixing and tests that need writing, but overall the weather app is pretty far along
[14:14] <mhall119> krinye: how would you like to get involved?
[14:19] <mhall119> krinye: we have a development guide for the Core Apps, which covers how to get the code and how to submit your changes back: https://wiki.ubuntu.com/Touch/CoreApps/DevelopmentGuide
[14:19] <mhall119> you'll also need the Ubuntu SDK packages installed, instructions for that are here: http://developer.ubuntu.com/get-started/
[14:20] <mhall119> a good way to start is to get the code, look through it and run the app to get a feel for things
[14:20] <mhall119> then pick an Autopilot test that needs writing, or a bug that needs fixing, and give it a shot
[14:20] <mhall119> you can always ask for additional help or guidance in here
[14:23] <krinye> Awesome sauce!!!
[14:24] <krinye> let me start on that I will pop by the next couple of days to ask more questions
[14:24] <krinye> thanks again for the info!
[15:26] <jonathas> hi folks, to test Wather app, i need an image of Ubuntu Phone OS or just my ubuntu 13.04?
[15:28] <jo-erlend> jonathas, you mean the weather indicator? It should be the same.
[15:28] <PaoloRotolo> jonathas, Hi, just your ubuntu 13.04 :) You can download sources from bzr and run it in Qt
[15:28] <popey> jo-erlend: i think jonathas is talking about the weather app, given the /topic
[15:28] <popey> jonathas: you can run it on an ubuntu 13.04 desktop, sure
[15:28] <jo-erlend> ah. :)
[15:29] <jonathas> jo-erlend, yeah, weather app
[15:29] <jonathas> PaoloRotolo, popey, PaoloRotolo thanks!
[15:29] <PaoloRotolo> jonathas, you're welcome :)
[15:30] <jo-erlend> It seems it'll take me some time to get fully informed again. I've been away for some time. :)
[15:30] <om26er> salem_, boiko hey! if you guys need CI jobs setup for the splitted apps (or any for that matter), you can ask me as well.
[15:30] <jono> mhall119, all set?
[15:30] <mhall119> yup
[15:31] <salem_> om26er, ah cool! thanks. Not sure if boiko already asked sergio, but we need ci jobs for messaging-app and dialer-app.
[15:37] <renato_> Kaleo, timp, the Popover is not following the mainwindow theme
[15:37] <timp> renato_: what doe you mean with that?
[15:37] <renato_> I am using the "SuruGradient" but the popover is created in the withe color
[15:38] <renato_> white
[15:39] <timp> renato_: I don't see a PopoverForegroundStyle.qml in the SuruGradient theme, so expect it to be the same as the default theme
[15:40] <timp> renato_: the theme currently only has a different style for MainView, and a different color palette
[15:40] <timp> renato_: are there visual designs for a popover with the SuruGradient theme?
[15:44] <gusch> boiko: can you do a quick MR? https://code.launchpad.net/~schwann/gallery-app/gallery-visual-copyright/+merge/175018
[15:46] <renato_> timp, the problem is that I am using a popover with a ListItem inside, the listitem has withe font which make impossible to read since the popover is white too
[15:46] <renato_> *white
[15:46] <renato_> the list item is following the dark theme but the popover not
[15:46] <renato_> which make impossible to read
[15:48] <timp> renato_: sounds like a bug in the color palette
[15:48] <renato_> Kaleo, timp, and the toolbar still white with dark theme which looks ugly
[15:49] <renato_> timp ok I will report a bug
[15:50] <timp> renato_: yes the color ("overlay") for both toolbar and popover is very light grey in SuruDark and SuruGradient.
[15:50] <timp> renato_: add it to the Ubuntu UX project also so a designer can have a look at it
[15:51] <timp> thanks :)
[16:02] <renato_> timp, Kaleo https://bugs.launchpad.net/ubuntu-ui-toolkit/+bug/1201864
[16:02] <ubot2`> Ubuntu bug 1201864 in Ubuntu UI Toolkit "[popover] Impossible to read ListItems inside a popover when using SuruDark theme" [Undecided,New]
[16:03] <renato_> Kaleo, do you know if I should use "SuruDark" or SuruGradient for core apps?
[16:13] <Kaleo> renato_: usually SuruGradient, but check with the designer
[16:21] <gusch> renato_: can you do a quick MR? https://code.launchpad.net/~schwann/gallery-app/gallery-visual-copyright/+merge/175018
[16:21] <renato_> gusch, looking
[16:21] <gusch> renato_: thx
[16:22] <renato_> gusch, I notice that some projects contains the COPYING.CC file, do you think that we should add this to all projects?
[16:25] <renato_> Kaleo, timp, when do you intent to fix the suru theme?
[16:26] <Kaleo> renato_: for the popover there is a MR that should fix it already
[16:26] <Kaleo> renato_: https://code.launchpad.net/~fboucault/ubuntu-ui-toolkit/popover_efficient_rendering/+merge/174527
[16:26] <renato_> Kaleo, ok nice, my MR is blocked because of that
[16:27] <Kaleo> renato_: ok, we just need to get timp to review the prereq MR: https://code.launchpad.net/~fboucault/ubuntu-ui-toolkit/popover_simpler_layouting/+merge/174522
[16:27] <Kaleo> :)
[16:27] <Kaleo> timp: ^
[16:32] <boiko> gusch: just back from lunch, I think renato already took care of your MR, right?
[16:32] <dpm> seb128, which was the gstreamer 1.0 plugin you mentioned yesterday I should install for playing mp3 with the music app instead of the 0.10 version?
[16:32] <dpm> as in which package?
[16:32] <seb128> dpm, I gave you the url to the package yesterday...
[16:32] <timp> Kaleo: approving
[16:32]  * seb128 looks for it again
[16:33] <timp> Kaleo: I got caught up in another bug
[16:33] <dpm> seb128, I know, I can't find it in my irc logs for some reason :/
[16:33] <seb128> dpm, https://launchpad.net/ubuntu/+source/gstreamer-fluendo-plugins-partner/1:0.10.21-1
[16:33] <seb128> dpm, gstreamer1.0-fluendo-plugins-mp3-partner
[16:33]  * dpm hugs seb128
[16:33]  * seb128 hugs dpm back
[16:33] <dpm> thanks!
[16:33] <seb128> dpm, but make sure your code actually use gstreamer1.0
[16:33] <seb128> dpm, yw!
[16:33] <dpm> yeah, I'll check. Qt Multimedia is supposed to make it totally transparent, and I guess this is the best opportunity to see if it's actually true :)
[16:36] <Kaleo> renato_: approved https://code.launchpad.net/~renatofilho/ubuntu-ui-toolkit/fix-keyboard-visibility/+merge/174503
[16:36] <Kaleo> renato_: thank you very muchj
[16:38] <Kaleo> timp: thanks!
[16:46] <AskUbuntu> How to get an application when download an application? | http://askubuntu.com/q/320721
[16:50] <renato_> Kaleo, great, thanks
[16:51] <Kaleo> renato_: so actually I was wrong the color of text in list items in popover (#1201864) won't be fixed by that MR
[16:51] <Kaleo> renato_: I'm going to think quite a bit more about it
[16:52] <Kaleo> renato_: sorry
[16:53] <nik90> Kaleo: ping
[16:55] <Kaleo> nik90: pong
[16:55] <nik90> Kaleo: I had a question regarding the Theme.palette usage when using the suru themes.
[16:56] <Kaleo> nik90: shoot
[16:56] <nik90> here in this mockup http://ubuntuone.com/6DGNnsKGtQtF5e58pG42f7
[16:56] <nik90> which theme.palette color should I use for the swipe delete element?
[16:56] <nik90> (the dark purple one showing the delete text)
[16:57] <nik90> I tried base, field etc. but they do not seem to work. Should I be defining my own color here?
[17:00] <Kaleo> nik90: let me see
[17:01] <Kaleo> nik90: in the toolkit's gallery we are using Theme.palette.normal.base
[17:01] <Kaleo> nik90: yeah, that should be the right one
[17:02] <Kaleo> nik90: do you have code I can try?.
[17:02] <nik90> Kaleo: yes. https://code.launchpad.net/~nik90/ubuntu-clock-app/apply-visual-design-colors
[17:04] <nik90> Kaleo: another question: Do we have to specify the color of the text explicitly by Theme.palette.normal.baseText? Or is it okay to let it take the default text color?
[17:06] <Kaleo> nik90: where?
[17:06] <Kaleo> nik90: you are writing your own widget here essentially therefore you need to specify the colors yourself (Label does nothing smart)
[17:06] <nik90> Kaleo: ah ok.
[17:07] <nik90> Kaleo: for the delete widget color, I already tried Theme.palette.normal.base. But it doesnt show a darker shade purple
[17:09] <Kaleo> nik90: well, it should be the right color
[17:09] <Kaleo> nik90: essentially it's the same color we use as a background for the switch for example
[17:09] <Kaleo> nik90: or the slider
[17:09] <Kaleo> nik90: who's the designer?
[17:10] <nik90> Kaleo: lina and mehow
[17:10] <Kaleo> nik90: ok, check with them I would say
[17:11] <nik90> Kaleo: will do
[17:11] <Kaleo> nik90: that color right now is #19000000
[17:11] <Kaleo> nik90: ie black with 19 opacity in hexadecimal
[17:11] <Kaleo> nik90: ie. 10% opacity
[17:11] <nik90> Kaleo: my background gradient branch is almost complete then. Lets hope the new ubuntushape widget lands soon
[17:12] <Kaleo> nik90: nice :)
[17:12] <Kaleo> nik90: why the new shape?
[17:12] <Kaleo> nik90: so, the new shape won't be good for the clock actually; we will need something custom made for that; the shape is not meant to make circles
[17:13] <nik90> Kaleo: really? I thought loicm told me that he was making the ubuntushape useable as a circle as well
[17:13] <Kaleo> nik90: (in the light theme Theme.palette.normal.base  is slightly more opaque: #1A000000)
[17:13] <Kaleo> nik90: yeah but it's not going to be 1) efficient 2) enough for all your needs
[17:14] <Kaleo> nik90: we'll have to discuss it once the new shape is there :)
[17:14] <nik90> Kaleo: I really do not know to implement that 3d shape with the cool shadows etc.
[17:14] <nik90> Kaleo: yes
[17:18] <Kaleo> nik90: we'll help :)
[17:19] <nik90> Kaleo: :)
[17:20] <Kaleo> nik90: so about the color
[17:20] <Kaleo> nik90: ask them if it should be the same as the background color of the slider & switch
[17:21] <Kaleo> nik90: if yes, then something's wrong in their designs
[17:21] <nik90> Kaleo: okay.
[17:21] <Kaleo> nik90: if not, then it may be something you have to set manually for now
[17:21] <nik90> Kaleo: I think you mean if not, then something's wrong in their designs
[17:21] <Kaleo> nik90: color from the mockup seems to be black with 30% opacity
[17:22] <nik90> Kaleo: so the issue is that this widget color (from design) is different the default slider background color. I will ask them on thursday
[17:22] <Kaleo> nik90: right
[17:23] <Kaleo> nik90: Rosie chose the colors for the toolkit widgets (slider&switch)
[17:23] <Kaleo> nik90: and it's black 10% opacity
[17:23] <Kaleo> nik90: in this mockup, for this other widget, they picked black 30% opacity
[17:23] <nik90> Kaleo: ok. And the clock app design is 30% opacity
[17:23] <Kaleo> nik90: either it's meant to be different
[17:23] <nik90> got it
[17:23] <Kaleo> nik90: which is fine
[17:23] <Kaleo> nik90: or there is something to resolve :)
[17:24] <Kaleo> nik90: hope that helps
[17:24] <renato_> Kaleo, do you know if is possible to use the TextInput without borders?
[17:24] <renato_> TextField
[17:24] <nik90> Kaleo: yup thnx for your help
[17:24] <Kaleo> nik90: everything else worked to your linking?
[17:25] <nik90> Kaleo: Also is there a standard search widget in the plans?
[17:25] <Kaleo> renato_: hmm, the way we do it right now in some apps is to set a custom style
[17:25] <nik90> Kaleo: yeah everything else regarding the background gradient works fine.
[17:25] <Kaleo> renato_:                 style: TextFieldStyle {
[17:25] <Kaleo>                     background: Item {}
[17:25] <Kaleo>                 }
[17:26] <Kaleo> nik90: yes, kalikiana is working on the search widget
[17:26] <nik90> Kaleo: perfect :)
[17:26] <Kaleo> renato_: see calculator app ubuntu-calculator-app/Simple/CalcLabel.qml
[17:26] <Kaleo> renato_: you'll need to import Ubuntu.Components.Themes.Ambiance 0.1
[17:29] <Kaleo> renato_: does that work?
[17:29] <Kaleo> renato_: (wondering also, what's the design that requires it?)
[17:32] <renato_> Kaleo, works, but the input field has a left margin and I do not know how to remove it
[17:36] <Kaleo> renato_: right, the notes app does it
[17:36] <Kaleo> renato_: Components/TextDelegate.qml
[17:36] <Kaleo> renato_: frameSpacing: 0
[17:36] <Kaleo> renato_: http://pastebin.ubuntu.com/5881592/
[17:39] <Kaleo> renato_: it will look a bit more natural than import Ubuntu.Components.Themes.Ambiance 0.1 later
[17:39] <Kaleo> renato_: probably will change to import Ubuntu.Components.Styles 0.1
[17:40] <Kaleo> renato_: and it will be documented
[17:40] <Kaleo> renato_: anyhow
[17:40] <Kaleo> renato_: it should work
[17:41] <renato_> Kaleo, does not work
[17:41] <Kaleo> renato_: wha'ts wrong?
[17:42] <renato_> the margin stills
[17:42] <renato_> if I use a simple TextInput works
[17:43] <renato_> but using the TextField does not work even if I change the style
[17:43] <Kaleo> renato_: maybe it's overlaySpacing then
[17:43] <Kaleo> renato_: apparently frameSpacing is for TextArea
[17:43] <Kaleo> renato_: and overlaySpacing for TextField
[17:43] <Kaleo> renato_: go figure why
[17:43] <renato_> Kaleo, yes works
[17:43] <renato_> thanks
[17:44] <Kaleo> renato_: DONE
[17:44] <renato_> Kaleo, btw I am using the suru theme
[17:44] <Kaleo> is it nice?
[17:45] <Kaleo> renato_: oh, you mean about the import
[17:45] <Kaleo> renato_: yeah better to import SuruGradient then
[17:46] <Kaleo> (or whichever you use)
[17:46] <gusch> boiko: ping
[17:46] <boiko> gusch: pong
[17:46] <Kaleo> renato_: oh, no hang on
[17:46] <Kaleo> renato_: you can't do that
[17:46] <Kaleo> renato_: only importing Ambiance will work
[17:46] <Kaleo> renato_: interesting..
[17:46] <Kaleo> renato_: there is a failure in the system then
[17:47] <gusch> boiko: can you do a quick review? https://code.launchpad.net/~schwann/gallery-app/gallery-fatser-dtae-compare/+merge/175089
[17:47] <Kaleo> renato_: but that should not block you
[17:47] <renato_> Kaleo, yeah I will keep the import ambience for now
[17:48] <Kaleo> r	ok
[17:48] <boiko> gusch: is the branch name meant to be named like that or is that a typo? :)
[17:48] <Kaleo> renato_: ok
[17:48] <boiko> gusch: approved@
[17:48] <gusch> boiko: not only one ;)
[17:48] <gusch> boiko: thx
[17:49] <gusch> boiko: mybe this one as well? https://code.launchpad.net/~schwann/gallery-app/gallery-visual-copyright/+merge/175018
[17:50] <boiko> gusch: which reminds me I need to do the same for phone-app, but now I will wait and to that in the splitted apps
[17:51] <gusch> boiko: I waited for long enought ;) - thx
[17:52] <boiko> gusch: approved.
[18:33] <jo-erlend> I find it a little strange that people are focusing on a weather app as a core-app for Ubuntu Phone rather than focusing on something like good Anyremote support. Because if you can use your Ubuntu phone as a remote control for your presentations, desktop, music and video – out of the box, then that makes both Ubuntu Desktop and Ubuntu Phone much more attractive. Weather, on the other hand, is something you can easily find on the
[18:33] <jo-erlend>  web. Sure, it's nice, but I don't think anyone will choose Ubuntu because of it.
[18:34] <nik90> jo-erlend: My best possible is that the core apps was initially started out with apps which are essential for basic phone usage
[18:34] <jo-erlend> exactly. Weather isn't.
[18:35] <nik90> jo-erlend: and then slowly they started adding apps which were mature and also usefuly
[18:35] <nik90> jo-erlend: I like to think weather is more useful than a presentation app which might only apply to a smaller subset of people
[18:35] <jo-erlend> nik90, I'm not talking about a presentation app. I'm talking about a remote control that can be used with almost any Ubuntu application.
[18:36] <zeokila> jo-erlend: I've got to disagree with you, a weather app will hit a much larger audience then a presentation control thingy
[18:36] <jo-erlend> Anyremote does a very good job at that, but it's not at all polished and can be rather confusing to configure. However, when it works, it's very nice.
[18:36] <zeokila> The time it takes for you to launch the web browser, put in your query or open your favorites > time to open a weather app
[18:37] <jo-erlend> sure. I'm not saying the weather app is bad. Quite the contrary. It looks very nice. But I don't see it as a core app.
[18:37] <nik90> jo-erlend: do you mean an app which allows you to control your music player or <insert app here> running on your phone from your desktop and vice versa?
[18:38] <zeokila> Your control thingy could be good, but as something people whom specifically need it should download it on the to be 'app store thingy', it will just be an annoying icon for most people
[18:38] <popey> jo-erlend: feel free to develop an app.
[18:38] <jo-erlend> however, being able to control all your Ubuntu applications, including Totem, Rhythmbox, Firefox, Evince, LibreOffice, etc using your handheld device, is very nice. I currently do that in Android.
[18:39] <jono> jo-erlend, we are focusing on weather as many phones ship with a weather app and it isnt a huge amount of work to focus on
[18:39] <timp> jo-erlend: you can work on a remote control app while others work on a weather app :)
[18:39] <timp> ah, as popey said :)
[18:39] <jono> indeed :-)
[18:39] <nik90> jo-erlend: if the app is mature and found useful, I am positive it can be made a core app.
[18:40] <nik90> I have found other apps like sudoku, dropping-letters being added to the core apps program
[18:40] <timp> what is dropping-letters? I saw it on the wiki but without information
[18:40] <nik90> It is a matter of finding people to help develop them
[18:40] <popey> its a game
[18:40] <nik90> timp: its a nice game
[18:40] <popey> type words with the falling letters
[18:41] <timp> nik90, popey sounds nice... you have to type the words away? how do you do that without a keyboard?
[18:41] <popey> yes, you tap the latters
[18:41] <timp> without a *physical8 keyboard
[18:41] <popey> *letters
[18:42] <popey> its fun
[18:42] <timp> I guess I have to try it out to understand
[18:42] <popey> was the first ever game on ubuntu touch
[18:42] <popey> yeah
[18:42] <popey> ☻
[18:42] <timp> popey: there was another first
[18:42] <timp> unity ;)
[18:42] <popey> hah
[18:42] <nik90> :)
[18:43] <Mihir> Hello
[18:45] <Kaleo> kenvandine: you around?
[18:50] <kenvandine> hey Kaleo
[18:54] <Kaleo> kenvandine: I introduced a bug in the friends app
[18:54] <kenvandine> nice :)
[18:54] <Kaleo> kenvandine: actually, I just made it a lot more visible
[18:54] <kenvandine> Kaleo, what's that?
[18:54] <Kaleo> kenvandine: the header was never hiding before
[18:55] <Kaleo> kenvandine: but now on top of that the list of posts goes over it
[18:55] <Kaleo> kenvandine: (it's not clipped by it)
[18:56] <Kaleo> mhall119: you know martin boro?
[18:56] <nik90> Kaleo: This is actually a bug in the weather app as well.
[18:57] <nik90> Kaleo: this is most likely a bug in the sdk
[18:57] <Kaleo> mhall119: dev of the weather app
[18:57] <kenvandine> Kaleo, is that only while scrolling?
[18:57] <Kaleo> nik90: it looks like the same but it's different
[18:57] <Kaleo> nik90: and neither of these issues are bugs in the toolkit actually
[18:57] <Kaleo> kenvandine: yes
[18:57] <kenvandine> what do i need to do to fix it
[18:58] <Kaleo> kenvandine: you need to have the first child of each Page to be the ListView itself
[18:58] <mhall119> Kaleo: yeah, m-b-o on IRC
[18:58] <Kaleo> mhall119: he is not here is he
[18:58] <kenvandine> so it's really just the order?
[18:58] <nik90> Kaleo: oh. I assumed it was due to the sdk, since it started happening only recently
[18:58] <mhall119> Kaleo: not now, but he was earlier today
[18:58] <Kaleo> nik90: a change in the toolkit just made the wrong code more wrong
[18:58] <nik90> Kaleo: :)
[18:59] <Kaleo> mhall119: ok, we just need to have https://code.launchpad.net/~martin-borho/ubuntu-weather-app/Bug1201094 landed
[18:59] <Kaleo> kenvandine: well, yes
[18:59] <Kaleo> kenvandine: we only look if any of the children is a Flickable to do the smart hiding of the header
[18:59] <Kaleo> kenvandine: not any of the *descendants*
[19:00] <Kaleo> kenvandine: (and while you are at it you probably want to remove that ugly white background :))
[19:00] <kenvandine> so should i make the child flickable?
[19:00] <Kaleo> kenvandine: no, just move up the ListView
[19:00] <Kaleo> (ListView inherits from Flickable)
[19:01] <Kaleo> kenvandine: alternatively there is a 'flickable' property on the page
[19:01] <Kaleo> kenvandine: that you can set
[19:01] <Kaleo> (on Page)
[19:01] <kenvandine> that is what i was just doing :)
[19:01] <Kaleo> kenvandine: :)
[19:04] <jo-erlend> jono, but convergence is important to Ubuntu. So far, it seems to be about making one device able to act as different things. But enabling one device to control another should also be part of the convergence story, I think.
[19:04] <jono> jo-erlend, right, but that is not really a core app
[19:04] <jono> it is a cool app
[19:05] <jo-erlend> wow.
[19:05] <jono> and you are certainly free to write that app
[19:05] <jo-erlend> Weather should be a core app, but Ubuntu should not? :)
[19:06] <jono> jo-erlend, I never said that
[19:06] <jono> I don't think a unified remote control is an app, it is a system function
[19:06] <jono> but we nominated weather as a core app many folks will want
[19:06] <jono> jo-erlend, in any case, who cares, we are already working on weather, and we are not stopping others from writing a remote :-)
[19:06] <jo-erlend> oh, I see. Yes, I can understand that point.
[19:07] <jo-erlend> right :)
[19:09] <jo-erlend> I'd _really_ like to see a port of PokerTH as a core-app. I'd like to see it preinstalled in Ubuntu Desktop as well. Has to be one of the best open source games around.
[19:09] <popey> *boggle*
[19:10] <popey> the definition of "core app" isn't "whatever app jo-erlend uses most on his phone" you know? ☻
[19:10] <jo-erlend> hehe
[19:10] <jono> jo-erlend, can you help write these apps you want?
[19:10] <Kaleo> lol
[19:10] <jo-erlend> jono, I've been thinking about writing an anyremote frontend, yes.
[19:10] <Kaleo> I want my egg timer app
[19:10] <Kaleo> just to measure egg boiling time
[19:10] <kenvandine> lp:~ken-vandine/friends-app/page_for_flickable
[19:11] <kenvandine> Kaleo, can you look at that?
[19:11] <timp> Kaleo: http://e.ggtimer.com/2min :)
[19:11] <kenvandine> the header mostly stays hidden now
[19:11] <popey> i use the oven timer for that
[19:11] <Kaleo> kenvandine: wowo
[19:11] <Kaleo> kenvandine: not what I expect
[19:11] <Kaleo> timp: thanks
[19:11] <kenvandine> Kaleo, yeah, doesn't seem right :)
[19:11] <timp> I use e.ggtimer.com for everything. So if I don't have internet, my food becomes a mess
[19:12] <kenvandine> timp, lol
[19:15] <jo-erlend> hehe
[19:16] <Kaleo> kenvandine: ok, some parameters set on ListView trigger that
[19:16] <kenvandine> ah
[19:17] <kenvandine> not surprising... i tweaked the hell out of that :)
[19:17] <Kaleo> kenvandine: comment out currentIndex: 0
[19:17] <Kaleo> kenvandine: or better highlightRangeMode: ListView.StrictlyEnforceRange
[19:18] <kenvandine> commenting out the highlightRangeMode fixed the header
[19:19] <Kaleo> kenvandine: yeah
[19:19] <Kaleo> kenvandine: not sure why you have it there
[19:19] <kenvandine> for keyboard nav
[19:19] <Kaleo> kenvandine: ok
[19:19] <Kaleo> kenvandine: it sure is a bug in the toolkit anyways
[19:19] <kenvandine> which i just realized isn't working
[19:19] <Kaleo> kenvandine: not a new one too
[19:19] <Kaleo> kenvandine: lol
[19:19] <kenvandine> probably related to the page change
[19:20] <Kaleo> kenvandine: so, now
[19:20] <Kaleo> kenvandine: it looks like it could take a bit more time to fix all this
[19:20] <seb128> Kaleo, " kenvandine: but now on top of that the list of posts goes over it"
[19:21] <seb128> Kaleo, oh, that's you to blame!!! (seeing that as well in system settings)
[19:21] <Kaleo> kenvandine: if you want to fix the build quickly, what you can do is simply "clip: true" at the right spot
[19:21] <Kaleo> seb128: where?
[19:21] <seb128> Kaleo, the storage subpanel in about
[19:22] <kenvandine> seb128, is the flickable set?
[19:22] <Kaleo> seb128: not broken here
[19:22] <Kaleo> seb128: (in today's build)
[19:22] <seb128> Kaleo, no, in fact I'm lying, it was in "licenses" and Laney fixed it today by replacing the height value by a anchors.fill
[19:22] <kenvandine> ah
[19:22] <seb128> Kaleo, the storage one is acting weird in another way, when you scroll down the header doesn't hide
[19:23] <Kaleo> seb128: cool; it does not sound like the right fix though
[19:23] <Kaleo> seb128: is the header hiding when scrolling down with that fix?
[19:23] <seb128> Kaleo, what fix? I'm still reading scrollback ;-)
[19:23] <kenvandine> now i'm wondering if this just broke keyboard nav or if it was already broken
[19:23] <Kaleo> seb128: the storage header is hiding for me
[19:23] <Kaleo> seb128: Laney's fix
[19:23] <Kaleo> seb128: in the licenses the header does not hide for me
[19:24] <kenvandine> crap... not a new bug
[19:24] <Kaleo> seb128: I think you are mixing them up :)
[19:24] <Kaleo> kenvandine: :D
[19:24] <kenvandine> Kaleo, wtf broke that!
[19:24] <dkessel> danielholm, are you there? I am trying to write an autopilot test for the music app and i'm searching for something in the app's code to verify an assumption I have...
[19:24] <Kaleo> kenvandine: ok, I'll leave it up to you now :)
[19:24] <Kaleo> kenvandine: you hjave all the info you need
[19:24] <seb128> Kaleo, yeah, they are different bugs ... about->storage has the "not hiding" bug
[19:24] <kenvandine> Kaleo, what should i do about the highlightRangeMode?  do you have a bug to track that?
[19:25] <Kaleo> seb128: no
[19:25] <Kaleo> seb128: it's hiding for me "storage"
[19:25] <kenvandine> seb128, it is hiding for me
[19:25] <seb128> Kaleo, about->licenses has the "scroll over the header" + "no hidding" for me
[19:25] <Kaleo> seb128: me too
[19:25] <Kaleo> seb128: and the proper fix for that cannot be just a anchors.fill
[19:25] <seb128> Kaleo, kenvandine: weird, in storage it hides and when the scrolling stop I get the header displayed back over the top
[19:25] <Kaleo> seb128: is that fix in trunk?
[19:26] <Kaleo> seb128: are you testing trunk or the latest image?
[19:26] <seb128> Kaleo, trunk, I've been hacking on it just before dinner and built trunk+local changes
[19:26] <seb128> Kaleo, http://bazaar.launchpad.net/~system-settings-touch/ubuntu-system-settings/trunk/revision/146
[19:27] <seb128> Kaleo, that was Laney's fix, but seems like it doesn't really fix the header issue indeed...
[19:27] <Kaleo> seb128: (unrelated your commit 140 is incorrect: it should 1) not duplicate that code 2) have a FIXME)
[19:27] <seb128> that will teach me to trust the "easy looking fixes" :p
[19:28] <Kaleo> "Small tweaks to the license page: make scrolling work correctly so it doesn't hide the header & go a bit faster so the large list can be navigated.
[19:28] <Kaleo> does not hide the header...
[19:28] <kenvandine> yeah
[19:28] <kenvandine> that needs flickable
[19:28] <Kaleo> that looks wrong
[19:28] <seb128> Kaleo, 1) right, I was just unsure how to share the code between panels
[19:28] <kenvandine> in Software.qml
[19:28] <Kaleo> seb128: create a new class
[19:28] <kenvandine> flickable: softwareList
[19:28] <kenvandine> will probably fix that
[19:29] <Kaleo> seb128: inheriting from Flickable
[19:29] <seb128> kenvandine, let me try that
[19:29] <seb128> Kaleo, where? in system settings? and where do I install it?.
[19:29] <Kaleo> seb128: in system settings
[19:29] <Kaleo> seb128: you don't have common code between the plugins?
[19:30] <Kaleo> seb128: (and you should not compare the contentHeight with root.height but simply with height)
[19:30] <kenvandine> we do
[19:30] <seb128> kenvandine, where? ;-)
[19:30] <Kaleo> you must have :)
[19:30] <kenvandine> we have ItemPage which inherits from Page
[19:30] <Kaleo> I can't imagine that the toolkit is THAT good :)
[19:30] <seb128> well in libSystemSettings
[19:30] <Kaleo> that it provides all you need :)
[19:30] <kenvandine> you need to set flickable on ItemPage
[19:31] <seb128> Kaleo, system settings are mostly lists, we don't need that much custom code...
[19:31] <Kaleo> seb128: sweet
[19:31] <Kaleo> seb128: for the issue at hand (sorry for the side talk), kenvandine is right
[19:31] <kenvandine> http://paste.ubuntu.com/5881921/
[19:31] <kenvandine> seb128, ^^
[19:31] <kenvandine> that works
[19:32] <seb128> kenvandine, if you mp it I can approve it ;-)
[19:32] <kenvandine> will do :)
[19:32] <Kaleo> ok, my job is done; I gotta run
[19:32] <seb128> I'm not sure to understand why that's needed though
[19:32] <Kaleo> kenvandine: you good?
[19:32] <Kaleo> seb128: we need to know what's scrolling
[19:32] <Kaleo> seb128: so that we sync the header with it
[19:32] <seb128> but I guess that's one of those things I don't understand why qml is not doing the obvious
[19:32] <kenvandine> Kaleo, do you need a bug filed for my highlight thing breaking the header?
[19:32] <Kaleo> seb128: what would be the obvious?
[19:33] <Kaleo> kenvandine: yes please
[19:33] <seb128> like putting columns width to the container width
[19:33] <kenvandine> ok
[19:33] <Kaleo> seb128: that's very different :)
[19:33] <seb128> Kaleo, because when you have one item in a page there is not a lot of choices of what to scroll on :p
[19:33] <Kaleo> seb128: you don't have one item :)
[19:33] <seb128> we have a page with a ListView in it
[19:33] <Kaleo> seb128: you have an Item that contains another Item that contains a ListView
[19:34] <seb128> nothing else
[19:34] <seb128> ok, the header screws me there :p
[19:34] <Kaleo> seb128: hang on
[19:35] <Kaleo> seb128: looking more closely you are right I think
[19:35] <kenvandine> so in this case the toolkit doesn't know what to use to determine if it's scrolling
[19:35] <seb128> Kaleo, http://paste.ubuntu.com/5881930/ is my code
[19:35] <kenvandine> we have an ItemPage with a ListView
[19:35] <timp> softwareList is a direct child of the Page, so page.flickable should be automatically set
[19:35] <Kaleo> seb128: ok, I know the bug
[19:35] <Kaleo> seb128: I don't know the bug
[19:35] <Kaleo> timp: you are right
[19:35] <timp> unless UbuntuStorageAboutPanel  is also flickable, then that will be the value of page.flickable
[19:35] <Kaleo> timp: it should just work
[19:36] <Kaleo> please everybody ignore me and listen to timp
[19:36] <seb128> lol
[19:36] <Kaleo> I'm gone
[19:36] <kenvandine> https://code.launchpad.net/~ken-vandine/ubuntu-system-settings/flickable/+merge/175110
[19:36] <kenvandine> seb128, ^^
[19:36] <seb128> Kaleo, have fun, ttyl!
[19:37]  * timp eod a while ago. But I'm always tempted to eavesdrop ;)
[19:37] <seb128> yeah, same here ;-)
[19:37] <seb128> kenvandine, looking
[19:38] <timp> I don't have system settings running here, probably I have to configure and install stuff for that for a few hours first ;)
[19:38] <timp> but the Page seems good. If it doesn't work, then maybe it is the way the page is added to the MainView
[19:38] <timp> or to a PageStack or Tabs inside a MainView
[19:39] <seb128> ItemPage is simple code
[19:39] <seb128> it does
[19:39] <seb128> Page {
[19:39] <seb128>     id: root
[19:39] <seb128>     property variant plugin
[19:39] <seb128>     title: i18n.dtr(plugin.translations, plugin.displayName)
[19:39] <seb128> }
[19:40] <seb128> then the code is what I pastebined before
[19:41] <timp> I have the source tree, but nothing compiled
[19:41] <timp> where is your main window?
[19:41] <Laney> erm, what?
[19:41] <Laney> It certainly does make the header hide when you scroll
[19:42] <timp> ah, found it.
[19:43] <Kaleo> timp:
[19:43] <Kaleo>                         if (child.anchors.top [19:44] <ahayzen> dkessel, the default media files are in the package example-content
[19:44] <timp> Kaleo: yes, a flickable that is not aligned to the top shouldn't push the header out when you scroll down
[19:45] <dkessel> ahayzen, spooky - had a look at my branch? :) thanks for the info
[19:45] <Kaleo> timp: but by default all Item's are alighen to the top
[19:45] <Kaleo> timp: so the condition is a bit too strict
[19:45] <ahayzen> dkessel, yep :)
[19:45] <Kaleo> aligned*
[19:45] <ahayzen> was just scanning through
[19:45] <kenvandine> Kaleo, https://bugs.launchpad.net/ubuntu-ui-toolkit/+bug/1201936
[19:45] <Kaleo> timp: ie. by default y == 0
[19:45] <ubot2`> Ubuntu bug 1201936 in Ubuntu UI Toolkit "highlightRangeMode in a ListView hides the page header" [Undecided,New]
[19:45] <Kaleo> timp: on all Items
[19:45] <Kaleo> kenvandine: thanks
[19:46] <Kaleo> timp: I think we really need something more explicit
[19:46] <Kaleo> timp: maybe even something like "ScrollablePage"
[19:46] <Kaleo> timp: that you use if you want the header to hide
[19:46] <Kaleo> timp: and for which you have to set the flickable
[19:46] <timp> Kaleo: ah I didn't think of that. I assumed if you don't set anchors or y, the position is not defined
[19:46] <Kaleo> timp: right
[19:47] <mhall119> Kaleo: do you happen to have screenshots showing the different available themes?
[19:47] <Kaleo> timp: I find lots of apps that either don't have a direct child being the flickable
[19:47] <Kaleo> timp: or don't set anchors
[19:47] <timp> Kaleo: we have the flickable property. If you want it explicit, we could remove the automatic detection of that
[19:47] <Kaleo> timp: maybe yeah
[19:47] <Kaleo> timp: we need to market it somehow
[19:47] <timp> Kaleo: it would save us some hassle, and remove some code
[19:48] <Kaleo> timp: so that everybody knows you need to set it
[19:48] <Kaleo> timp: I'm thinking that's not enough though
[19:48] <Kaleo> timp: I'm thinking if you have to use a ScrollablePage to make it work it's better
[19:49] <mhall119> Kaleo: timp: add it to askubuntu.com as a question and subsequent answer, then we can add it to the developer.u.c cookbook
[19:49] <Kaleo> timp: that way people make a conscious choice of it
[19:49] <Kaleo> mhall119: yeah, but we need an API trick first :)
[19:50] <Kaleo> timp: and first line of the documentation of Page we talk about ScrollablePage
[19:50] <Kaleo> timp: or something
[19:50] <timp> Kaleo: so remove all this flicking-stuff from page, and add a subclass of Page called ScrollablePage where you set the flickable property?
[19:50] <Kaleo> timp: and ScrollablePage raises an exception if no flickable is set
[19:50] <Kaleo> timp: yeah
[19:50] <Kaleo> timp: it's an idea
[19:50] <Kaleo> timp: maybe there is better
[19:50] <timp> the other option is to talk about the flickable property in the first line of Page, and not try to detect a flickable automatically
[19:50] <Kaleo> timp: htmmm yeah
[19:51] <Kaleo> timp: the other option is to provide ready made Pages
[19:51] <Kaleo> timp: one with a ListView for example
[19:51] <timp> I've thought of putting a Flickable by default in a Page as a default property, but then you get problems if you have a custom Flickable (such as a LisView)
[19:52] <Kaleo> timp: right
[19:52] <Kaleo> timp: how about we don't have Page
[19:52] <Kaleo> no, that's crazy
[19:52] <Kaleo> timp: I'm out of ideaas
[19:52] <timp> FlickablePage and ListViewPage would be an option, but I'm not sure if that is enough
[19:52] <mhall119> Kaleo: do you happen to have screenshots showing the different available themes?
[19:52] <timp> Kaleo: we used to have no Page.
[19:52] <Kaleo> mhall119: not at hand, ask Rosie
[19:52] <timp> Kaleo: but you need to set the tools and title(or header contents) somewhere
[19:54] <timp> if custom subclasses of Flickable and ListView are rarely used, FlickablePage and ListViewPage might be an option
[19:55] <kenvandine> Kaleo, i hate to keep you around longer than needed... but would you mind giving a quick review to https://code.launchpad.net/~ken-vandine/friends-app/page_for_flickable/+merge/175114
[19:55] <timp> we can set parameters such as the topMargin for the flickable then inside the page, instead of setting it for the flickable property when that is updated
[19:55] <kenvandine> Kaleo, you've basically seen it already :)
[19:56] <timp> Kaleo: I also thought about incorporating the functionality of PageStack in the MainView
[19:57] <timp> then you always have something like a stack available (for example if a search is triggered from outside the app, and the search view should have a back button)
[19:57] <timp> but that's a different topic
[20:06] <timp> kenvandine: your MR looks good but I didn't build/run it because I don't have the dependencies now
[20:06] <timp> kenvandine: I would remove the anchors from the Timeline in friends-app.qml
[20:07] <timp> kenvandine: also the PageStack in that file doesn't need anchors. it is automatic.
[20:07] <Kaleo> kenvandine: approved sir
[20:08] <kenvandine> Kaleo, thanks
[20:08] <kenvandine> timp, i probably have way too many anchors :)
[20:08] <kenvandine> i'll remove those
[20:09] <kenvandine> timp, i would love to have an expert take a look at the delegate in that listview to see how it can be optimized
[20:09]  * Kaleo is gone now.
[20:09] <timp> ciao
[20:09] <timp> me too
[20:09] <kenvandine> good night!
[20:09] <Kaleo> kenvandine: don't( use DropShadow
[20:09] <Kaleo> kenvandine: that's the bigggest drag
[20:10] <kenvandine> i'll try disabling that and compare
[20:10] <Kaleo> kenvandine: use QML_RENDER_TIMING=1
[20:10] <kenvandine> but i think there is some sizing issues
[20:10] <Kaleo> kenvandine: and look at render time
[20:10] <kenvandine> which also makes the transitions chunky
[20:11] <Kaleo> kenvandine: if on your laptop it's above 5ms you can be sure that's it's too much
[20:11] <Kaleo> kenvandine: and going to be laggy on the phone
[20:11] <kenvandine> it's actually smoother on the phone
[20:11] <kenvandine> which is weird!
[20:11] <Kaleo> kenvandine: ah ah
[20:11] <Kaleo> kenvandine: that I know why
[20:11] <Kaleo> kenvandine: it's using a different QtQuick renderer
[20:12] <Kaleo> kenvandine: (it's using multiple threads on the phone, not on the desktop
[20:12] <kenvandine> ah... so nothing i'm doing wrong )
[20:12] <Kaleo> )
[20:12] <kenvandine> :)
[20:12] <Kaleo> kenvandine: which will change
[20:12] <kenvandine> awesome
[20:12] <Kaleo> kenvandine: try QML_FORCE_THREADED_RENDERER=1 on your desktop
[20:12] <Kaleo> kenvandine: that will give you what the phone uses by default
[20:12] <Kaleo> anyway most improtantly: profile with QML_RENDER_TIMING=1
[20:13] <Kaleo> and profile with the profiler in QtCreator
[20:13] <Kaleo> :)
[20:13] <Kaleo> on that note, byyyyyyyyyyyyyyyyye