[01:19] <sleepy-owl> hello folks, i am trying to set up a Qt development environment on my system. i saw qtcreator in the repos but before i go and wreck my system with whatever those packages install by default, i came here for advice. are there any packages in  particular that i have to avoid or get ?
[04:07] <Mirv> I wonder which app..
[04:19] <Akiva-Thinkpad> hey all
[04:19] <Akiva-Thinkpad> back from me uncles wedding
[04:25] <Akiva-Thinkpad> Bye all. Be back in 9ish hours.
[06:45] <dholbach> good morning
[06:50] <nik90> Mirv: the new clock ap ;)
[06:50] <nik90> Good morning everyone
[07:31] <mihir> popey: ping
[08:44] <vitimiti> Hi
[08:50] <nik90> popey: can you ping me when you are online.
[08:57] <nik90> davmor2: there you go clock reboot should be available as an update in the daily image.
[09:10] <davmor2> nice
[09:10] <davmor2> nik90: not quite the day you said though right ;)
[09:11] <Saviq> nik90, I'm afraid clock reboot fails to start on two of my devices :/
[09:11]  * Saviq gets out logging
[09:11] <nik90> Saviq: did you search for "Clock" since apps don't usually launch after an update. Search somehow refreshes the desktop file I think
[09:12] <Saviq> nik90, indeed
[09:12] <Saviq> nik90, just noticed it's trying the wrong app id
[09:13] <nik90> Saviq: hmm it seems to work for me atm
[09:13] <Saviq> nik90, yeah, false alarm
[09:13] <Saviq> nik90, sounds like a bug in click scope
[09:13]  * nik90 sighs a relief :)
[09:13] <sergiusens> Saviq: I've seen that more when installing with pkcon
[09:13] <Saviq> nik90, looking real good!
[09:14] <sergiusens> Saviq: if installed from the scope; I guess it triggers a signal or something to refresh
[09:14] <Saviq> sergiusens, yeah, that as well, but I upgraded from settings
[09:14] <sergiusens> ok
[09:14] <sergiusens> then ignore me :-P
[09:14] <davmor2> Saviq: do a search it will refresh the click scope old bug that still needs fixing damn it ;)
[09:14] <Saviq> sergiusens, yes it does, so we need a hook that will kick the dash to refresh
[09:15] <sergiusens> wow, bottom swipe and top swipe
[09:15] <davmor2> Saviq: of course I automatically blame you entirely for it being broken still  ;)  That should fix it :)
[09:15] <Saviq> davmor2, lemme just deflect quickly
[09:16] <Saviq> davmor2, dash can't assume there even *is* a click scope, let alone refresh it on app updates ;P
[09:16] <Saviq> nik90, looking first class!
[09:16] <nik90> thnx
[09:17] <Saviq> nik90, one nitpick, it's slightly too easy to go into "add city" mode when just scrolling around
[09:18] <Saviq> nik90, maybe it should check for a maximum movement velocity on release
[09:18] <Saviq> nik90, this way you'll make sure that the user stopped moving their finger before release
[09:18] <davmor2> Saviq: right but I'm assuming that the updater on finishing an update could trigger the scope to refresh right?
[09:19] <Saviq> davmor2, the click scope should install a click hook to trigger a refresh on all click operations, yes
[09:21] <Saviq> nik90, ah, and one more - volume slider hint is semi transparent (and should probably say %)
[09:21] <Saviq> nik90, /me will file bugs
[09:22] <nik90> Saviq: go ahead, I am in a design meeting atm
[09:25] <popey> nik90: yo
[09:35] <nik90> popey: hi
[09:35] <popey> nik90: heya
[09:35] <nik90> popey: just had a meeting with the designers
[09:35] <nik90> popey: so the click package has been uploaded and approved!
[09:35] <popey> \o/
[09:35] <nik90> popey: can you change the screenshots and the description for it.
[09:36] <popey> I cant.
[09:36] <nik90> oh
[09:36] <popey> I dont have access to do that, I have to get someone else - sergiusens, mirv or balloons to do it
[09:37] <nik90> ok
[09:37] <nik90> depending on who it is, I can send the screenshots and descriptions to them
[09:37]  * popey pings sergiusens 
[09:38] <Mirv> popey: not me, at least I don't know that I'd have
[09:38] <popey> ok
[09:39] <popey> nik90: I'd recommend emailing sergiusens the details as I know he can certainly do it.
[09:39] <nik90> popey: will do so now
[09:47] <zyga> nik90: clock reboot is PRETTY, good work!
[09:47] <md6sum> nik90, since you released the new version of the clock-app, will it be part of the next promoted image on the devel channel?
[09:51] <nik90> zyga: thnx
[09:51] <nik90> md6sum: it should already be available as an update in the current promoted image
[09:52] <nik90> md6sum: in the next promoted image, it will come by default
[09:54] <zyga> nik90: I installed the update
[09:54] <zyga> nik90: but it would crash
[09:54] <zyga> nik90: I then removed clock app
[09:54] <zyga> nik90: and installed clock reboot
[09:54] <zyga> nik90: I don't know if that's intended
[09:54] <zyga> nik90: this was on rtm-8
[09:55] <md6sum> thx, I just did the update. Does the new clock app rely on the system clock time to toggle the alarm?
[09:55] <nik90> md6sum: yes
[09:55] <nik90> zyga: hmm
[09:55] <nik90> zyga: apps don't launch after an update
[09:55] <md6sum> The old clock app did not start the alarm due to the system time being stuck when the phone is sleeping
[09:55] <md6sum> So the alarm will not work?
[09:56] <zyga> nik90: oh
[09:56] <zyga> nik90: so what should I have done instead?
[09:56] <nik90> md6sum: that was fixed in the system, the clock app alarms work as expected
[09:56] <nik90> zyga: you need to search for the "Clock app" which refreshes the click scope
[09:56] <zyga> nik90: ah
[09:56] <zyga> nik90:  should I remove the clock reboot app, reinstall clock app and search again then?
[09:56] <md6sum> I am on r203 so I need to wait for the next promoted image anyway?
[09:57] <zyga> nik90: or will clock reboot keep being updated?
[09:57] <nik90> zyga: clock reboot will not be removed from the store actually :D. I say reinstall clock app
[09:57] <nik90> md6sum: that bug shouldn't be there in 203
[09:57] <nik90> md6sum: in my testing, the alarm worked (on N4) in 203.
[09:58] <md6sum> Ok, I will test this and let you know tomorrow. ;)
[09:58] <md6sum> thx and bye
[09:58] <nik90> md6sum: sure. bye
[09:59] <nikwen> nik90, md6sum: I've had that yesterday as well (on image 207), today (on r208) it worked fine.
[10:00] <nik90> nikwen: I haven't tried 207 yet, I went straight to the rtm images
[10:00] <nik90> nikwen: oh btw phablet-record is cool
[10:00] <zyga> nik90: thanks!
[10:00] <nik90> nikwen: is there any way to increase the frame rate a bit?
[10:00] <nikwen> nik90: Thanks. :)
[10:01] <nik90> zyga: sry, I may be a typo in my statement. Clock reboot tech preview *will* be removed from the store.
[10:01] <nik90> zyga: I just read what i typed before :P
[10:01] <nikwen> nik90: I don't think that it can be increased with the current implementation. It uses phablet-screenshot to take screenshots and pull them from the device.
[10:02] <nik90> nikwen: ah so the framerate depends on how fast the phablet-screeshot takes the pictures?
[10:02] <popey> oooh, where is phablet-record?
[10:02] <nik90> nikwen: np, still helpful to create a gif quickly
[10:02] <nikwen> nik90: Sadly, mirscreencast crashes at the moment, otherwise we could switch to using that one.
[10:02] <popey> I wrote a script yesterday but 14.10 is missing ffmpeg so i couldnt convert
[10:02] <nik90> popey: https://github.com/nikwen/phablet-record
[10:02] <nikwen> I'll post a link to the bug report.
[10:02] <popey> thanks
[10:03] <zyga> nik90: ah, ok
[10:04] <zyga> heh
[10:04] <zyga> I cannot install it
[10:04] <zyga> clock is "installed" in the store
[10:04] <nikwen> nik90: Here you go: https://bugs.launchpad.net/mir/+bug/1358191
[10:04] <ubot2`> Ubuntu bug 1358191 in mir "[regression] Clients are crashing (SIGSEGV) on mir_connect()" [Critical,In progress]
[10:04] <zyga> but doesn't show up in searches in the dash
[10:06] <zyga> ok, another uninstall / reinstall fixes that
[10:06] <zyga> nik90: is there a bug for the click scope not refreshing?
[10:06] <nik90> zyga: I think so..not sure
[10:07] <zyga> nik90: ok, I'll try searching and file one just in case
[10:07] <zyga> nik90: awesome design and implementation :-)
[10:07] <nikwen> zyga: There is one. One moment...
[10:08] <nikwen> zyga: https://bugs.launchpad.net/qtmir/+bug/1361998
[10:08] <ubot2`> Ubuntu bug 1361998 in qtmir "When applications update, a reboot is needed to open them" [Undecided,New]
[10:10] <nik90> nikwen: thnx. marking as confirmed
[10:10] <nik90> zyga: thnx
[10:10] <nikwen> nik90: You're welcome. ;)
[10:10] <zyga> thanks!
[10:20] <nik90> t1mp: ping
[10:22] <t1mp> nik90: hi
[10:23] <nik90> t1mp: Hi, I am seem to be having an interesting issue.
[10:23] <nik90> t1mp: https://imgur.com/Uehbzm1
[10:23] <nik90> t1mp: the slider value popup is transparent.. any idea why?
[10:23] <nik90> t1mp: I am using standard sdk component. no changes to it
[10:24] <nik90> t1mp: on further testing, it seems that if the slider value popup is over the header, it becomes transparent
[10:25] <nerochiaro> oSoMoN: release process question: how do I know if a bug marked "fix released" is actually in the image that i get when i flash with channel ubuntu-touch/ubuntu-rtm/14.09-proposed ?
[10:25] <nik90> t1mp: I replicated that same component, put it at the bottom of the list and it is opaque
[10:26] <t1mp> nik90: strange
[10:26] <oSoMoN> nerochiaro, shell into the device, and check the version of the package
[10:26] <sergiusens> nik90: popey I was going to ask for new assets :) just send them my way (links or attachments)
[10:26] <t1mp> nik90: perhaps the popover is behind the header, and the header is transparent
[10:27] <nik90> sergiusens: already sent you assets
[10:27] <nik90> sergiusens: well 5-10 mins ago ;)
[10:27] <nik90> t1mp: hmm that could be it
[10:27] <oSoMoN> nerochiaro, or check the commit logs at http://people.canonical.com/~lzemczak/landing-team/
[10:27] <nik90> t1mp: let me play with the z value of the slider itself to see
[10:27] <t1mp> nik90: still it is wrong the popup should go on top of everything else
[10:28] <nik90> t1mp: +1. I will file a bug report with a sample app
[10:28] <t1mp> nik90: thanks
[10:36] <Saviq> nik90, sorry for the inflow of bugs, wanted to register everything I could find :)
[10:36] <Saviq> nik90, the app looks real great regardless
[10:37] <nik90> Saviq: no worries :) .. many of them require design feedback which could take some time.
[10:38] <nik90> Saviq: so its good to see them reported early
[10:38] <nik90> t1mp: bug 1362115
[10:38] <ubot2`> Launchpad bug 1362115 in ubuntu-ui-toolkit "Slider popup is hidden beneath the header" [Undecided,New] https://launchpad.net/bugs/1362115
[10:38] <Saviq> nik90, yup, I knew that
[10:40] <nik90> Saviq: I am aware of the accidental world city trigger bug. Unfortunately I am a bit stuck on how to fix it. I might need your expertise on it when you have some time later.
[10:41] <nik90> Saviq: btw, the alarm volume slider shows the alarm volume in db. So should it say 50 db rather than 50% ?
[10:43] <Saviq> nik90, I don't think users deal well with dB :)
[10:43] <nik90> :)
[10:43] <Saviq> nik90, I think it should use % then, that's something people can relate to
[10:44] <t1mp> nik90: confirmed https://bugs.launchpad.net/ubuntu-ui-toolkit/+bug/1362115
[10:44] <ubot2`> Ubuntu bug 1362115 in ubuntu-ui-toolkit "Slider popup is hidden beneath the header" [Undecided,Confirmed]
[10:44] <Saviq> nik90, it does go from 0 to 100, are you sure it's dB?
[10:44] <Saviq> nik90, or well, it goes from 1 to 100 actually ;)
[10:44] <nik90> Saviq: well from the indicator-datetime spec, https://bazaar.launchpad.net/~indicator-applet-developers/indicator-datetime/trunk.14.10/view/head:/data/com.canonical.indicator.datetime.AlarmProperties.xml
[10:44] <nik90> Saviq: I remember charles saying it was db. I will have to check with him
[10:45] <Saviq> nik90, wonder if we need the value at all
[10:45] <Saviq> nik90, I think it should play the sound as you're changing the volume though :)
[10:45] <nik90> Saviq: that's interesting and more useful yes
[10:46] <Saviq> nik90, lemme amend the bug
[10:51] <nik90> t1mp: is it possible to not show the popup at all for a slider?
[10:51] <sergiusens> popey: nik90 new screenies are now avail
[10:51] <nik90> sergiusens: sweet. thnx
[10:52] <popey> thanks sergiusens
[10:53] <popey> nik90: http://people.canonical.com/~ogra/touch-image-stats/210.changes ☻
[10:54] <t1mp> nik90: why would you want that?
[10:54] <t1mp> nik90: ah you already added a screenshot I see.. I was doing the same thing :)
[10:54] <nik90> t1mp: https://bugs.launchpad.net/ubuntu-clock-app/+bug/1362078
[10:54] <ubot2`> Ubuntu bug 1362078 in ubuntu-ux "Alarm volume slider should lose the hint and play the alarm sound while changing volume" [Undecided,New]
[10:55] <nik90> popey: woohoo .. big jump 1.0.492 to 3.1.69
[10:55] <popey> yeah ☻
[10:55] <nik90> popey: btw do you have alarm that you created in the old clock app?
[10:56] <nik90> popey: I am trying to confirm https://bugs.launchpad.net/ubuntu-clock-app/+bug/1362083
[10:56] <ubot2`> Ubuntu bug 1362083 in ubuntu-clock-app "Can't delete alarm" [Undecided,New]
[10:56] <nik90> ermm why two ubots?
[10:56] <nik90> ubot5 go home
[10:56] <nik90> 12:56 PM <ubot5> Sorry, I don't know anything about 'go home'
[10:56] <nik90> lol
[10:56] <popey> yeah, will get one muted
[10:58] <popey> nik90: i was able to delete them
[10:58] <Saviq> nik90, on the "too easy to get into add city" I think it should be as easy as checking Flickable.velocity onRelease
[10:58] <Saviq> nik90, and only going through if velocity is small enough (I'd say really minimal)
[10:59] <nik90> Saviq: I did something like https://code.launchpad.net/~nik90/ubuntu-clock-app/fix-accidental-worldcity-trigger/+merge/231230
[10:59] <nik90> Saviq: but it fails when there are less than 3 cities added
[11:00] <nik90> Saviq: also mzanetti wasn't happy about changing the listitem edge behavior. I will try your solution to see if that works
[11:00] <Saviq> nik90, yeah, I think it'd be better with velocity, you still get all the behaviour as usual, with overshoot and such, but it will only trigger the Add City mode if you stopped for a moment
[11:01] <Saviq> nik90, http://qt-project.org/doc/qt-5/qml-qtquick-flickable.html#verticalVelocity-prop
[11:01] <nik90> Saviq: So I should be looking at http://qt-project.org/doc/qt-5/qml-qtquick-flickable.html#verticalVelocity-prop
[11:01] <nik90> Saviq: :)
[11:01] <Saviq> nik90, yup :)
[11:02] <nik90> Saviq: thnx. Will give that a shot. For me that is the most annoying bug atm
[11:02] <Saviq> nik90, it is indeed :)
[11:09] <popey> bug 1362083
[11:13] <t1mp> nik90: I guess you need a feature request in UITK for bug 1362078
[11:16] <nik90> t1mp: yes
[11:23] <t1mp> kalikiana: if you can join on mumble, we'll divide the rtm14 bugs
[11:23] <t1mp> zsombi: here is the list https://bugs.launchpad.net/ubuntu-ui-toolkit/+bugs?search=Search&field.assignee=tpeeters
[11:30] <mihir> popey: ping
[11:46] <popey> mihir: yo
[11:50] <kunal> zsombi, Hi
[11:50] <zsombi> kunal: hai
[11:50] <kunal> I was looking at this bug
[11:50] <kunal> https://bugs.launchpad.net/ubuntu-calendar-app/+bug/1357303
[11:50] <kunal> can you provide some information/background for this
[11:51] <mihir> popey: WE NEED SOME INPUTS ON THIS https://code.launchpad.net/~ubuntu-calendar-dev/ubuntu-calendar-app/revamp-repetition-deisgn/+merge/231967
[11:51] <mihir> nik90: suggested to remove mon-wed-fri & tue-thu
[11:51] <mihir> repeat option
[11:52] <nik90> mihir: I suggest you don't get blocked on it since it is a small thing.
[11:52] <mihir> kunal: he suggested to use abstract button , as the property we're using will depreciate in next release
[11:52] <nik90> mihir: if you can fix the functionality, then we can proceed with the merge.
[11:52] <mihir> nik90: i am not blocked , just if we can resolve can merge in same branch :)
[11:52] <zsombi> kunal: the idea is not to use a TextField for a purpose that is not designed for it. Placing a MouseArea over it just to get what you need is a bit overkill, so it must be done with a different approach
[11:53] <kunal> so we are talking this only for Time/Date picker, right ?
[11:53] <zsombi> kunal: beside that the highlighted property will be deprecated, there will be no such a state anymor eon the text inputs
[11:53] <zsombi> kunal: yes
[11:53] <mihir> kunal: yes only for dates & time
[11:53] <kunal> I am using highlighted for other text field as well, like title,location
[11:54] <mihir> nik90: i am stuck at one bug , as soon as i resolve it , we should be good to go.
[11:54] <zsombi> kunal: that will also suffer. There will be visuals for disabled, enabled and focused, no more highlighted
[11:54] <nik90> mihir: then we should move ahead since it is a matter of removing a few lines. I say we keep it for now then
[11:54] <kunal> zsombi, in that case I will use focused
[11:55] <kunal> zsombi, focused will change appearance as well ?
[11:55] <nik90> kunal: fyi, only the date textfield use them. In the new design revamp me and mihir are working we removed that from other textfield since it breaks ubuntu design
[11:55] <zsombi> kunal: ok, but make sure you don't set it, just react on teh property. The text inputs will get focus when touched over them
[11:55] <zsombi> kunal: yes, when a text input is focused, the background gets light and the text cursor will appear
[11:56] <zsombi> kunal: if the OSK is hidden, text input will lose focus
[11:56] <kunal> zsombi, ok
[11:56] <kunal> nik90, http://bazaar.launchpad.net/~ubuntu-calendar-dev/ubuntu-calendar-app/trunk/view/head:/NewEventEntryField.qml
[11:57] <zsombi> kunal: also, if you tap on a different control, the focus will be grabbed from teh text input
[11:57] <nik90> kunal: I know I saw
[11:57] <kunal> nik90, we are not using that anymore ?
[11:57] <nik90> kunal: I don't use NewEventEntryField else where
[11:57] <nik90> kunal: well in the revamp MP atleast. We are still reviewing it
[11:57] <kunal> nik90, ok
[11:58] <nik90> kunal: don't worry, all this will make into trunk only after your approval when it is ready :)
[11:58] <mihir> kunal: i believe we are not , as far as newevent is concern
[11:58] <nik90> kunal: so we won't push something without your permission :D
[11:58] <mihir> kunal: we have used page instead of dialog now
[11:59] <kunal> nik90, I am not worried, if you are looking at it
[11:59] <kunal> mihir, I saw comment , but not code yet
[12:00]  * nik90 grinns
[12:00] <kunal> I was facing major crisis with my laptops, could not work with code, it just got ok now, still facing some problem
[12:02] <kunal> nik90, mihir , so you guys are also working on new timepicker stuff ?
[12:02] <nik90> kunal: we didnt change that afaik
[12:02] <nik90> kunal: what's wrong with it?
[12:03] <kunal> nik90, regarding the same thing, which uses textedit, hightlighted and timepicker
[12:03] <kunal> https://bugs.launchpad.net/ubuntu-calendar-app/+bug/1357303
[12:03] <kunal> this bug
[12:03] <nik90> kunal: ah that. I think we should go with what you suggested which is to use focussed instead of highlighted
[12:03] <nik90> kunal: so on focussed, change the color etc etc
[12:04] <nik90> kunal: I think we will do that after this MP since the code diff is getting big as it is
[12:04] <kunal> nik90, that's better
[12:04]  * nik90 is not a fan of big code diff..harder to spot issues in the code
[12:05] <kunal> i agree
[12:05] <kunal> review is lot difficult
[12:05] <mihir> kunal: nope , we haven't change it yet.
[12:05] <kunal> mihir, ok
[12:06] <nik90> mihir: ok lets try getting your branch merged into my branch then if you think it is ready
[12:06] <nik90> mihir: leave the alarm repeat days as it is
[12:07] <kunal> nik90, my QtCreate will not start, you know the issue ?
[12:07] <kunal> *QtCreator
[12:08] <nik90> kunal: on laptop or VM?
[12:08] <nik90> kunal: I had the issue of QtC crashing on my VM. On the laptop, it doesn't crash
[12:08] <kunal> laptop
[12:09] <kunal> you were able to solve it ?
[12:09] <nik90> it was due to my VM GL graphics or something. I removed a driver and it started worked correctly
[12:09] <nik90> maybe launch qtc from terminal and see what the error is?
[12:10] <kunal> I tried, I dont understand it
[12:10] <kunal> let me see more closely
[12:10] <kunal> BTW,
[12:10] <kunal> ** (qmlscene:3934): WARNING **: Unable to register app: GDBus.Error:org.freedesktop.DBus.Error.InvalidArgs: Invalid application ID
[12:10] <kunal> <Unknown File>: Invalid empty URL
[12:10] <kunal> Fail to connect with sync monitor: QDBusError("org.freedesktop.DBus.Error.ServiceUnknown", "The name com.canonical.SyncMonitor was not provided by any .service files")
[12:10] <kunal> intel_do_flush_locked failed: Invalid argument
[12:10] <kunal> you know about this ?
[12:10] <nik90> hmm no
[12:11] <kunal> ok,
[12:18] <kunal> renatu, hi
[12:18] <renatu> hi
[12:18] <kunal>  Fail to connect with sync monitor: QDBusError("org.freedesktop.DBus.Error.ServiceUnknown", "The name com.canonical.SyncMonitor was not provided by any .service files")
[12:18] <kunal> do you know about this
[12:18] <kunal> ?
[12:19] <kunal> it came when running calendar.qml
[12:21] <renatu> kunal, do you have sync-monitor running?
[12:21] <renatu> this is used by the interface that activate the manual sync
[12:21] <kunal> how can I check ?
[12:21] <kunal> or how to run it ?
[12:21] <renatu> are you running on device?
[12:22] <kunal> no
[12:22] <kunal> on laptop
[12:22] <renatu> or you can ignore it or you can install sync-monitor package
[12:22] <kunal> I am setting up new laptop and facing issue there
[12:22] <kunal> let me check
[12:24] <kunal> yes, now its gone
[12:25] <zsombi> popey: howdy, we have two bugs for the Button text alignment and color, which got tagged for RTM: bug #1357323 and bug #1357332
[12:26] <mihir> nik90: sure , we can do that.
[12:26] <mihir> nik90: after i fix and test all the functionalities, after that i'll work on Autopilot tests.
[12:27] <nik90> mihir: yes AP is last
[12:27] <nik90> zsombi: I don't think those bugs would affect calendar app any more. Mihir can you confirm ^^
[12:27] <zsombi> popey: mihir: are those really that critical? I'd suggest to use AbstractButton
[12:27] <zsombi> nik90: if not, I'll mark them as wish and untag them
[12:28] <mihir> nik90: i believe if we use abstract button we should good to go.
[12:28] <nik90> zsombi: I agree, but let me confirm with mihir
[12:28] <zsombi> mihir: +1
[12:28] <nik90> mihir: since with the new design we don't use abstract buttons, those bugs are not required for rtm
[12:28] <nik90> mihir: agree/
[12:28] <nik90> ?
[12:28] <mihir> zsombi: if it is easy fix in UI kit , then we can easily use button , but we have an option. so not that criticial
[12:29] <mihir> nik90: agreed.
[12:29] <nik90> mihir: it might be easy to fix, but there are other critical bugs which need attention.
[12:29] <zsombi> mihir: it perhaps can be easy, but a proper fix would take long... and I would not open some API which we will regret the next few years :)
[12:29] <nik90> zsombi: let's mark them as wishlist and move them post RTM
[12:29] <zsombi> nik90: yea, agree
[12:30] <mihir> zsombi: agreed , we can move it to wish list
[12:31] <zsombi> nik90: mihir: ok, done, thx!!
[12:31] <nik90> zsombi: :)
[12:33] <zsombi> nik90: picking up bug #1362115
[12:33] <nik90> zsombi: can I make a request for that bug?
[12:34] <nik90> zsombi: would it be possible to add a option to hide the popover?
[12:34] <zsombi> nik90: that's API change, no way now
[12:34] <nik90> zsombi: the indicator-sound in the phone, has a slider which does not show the popover
[12:34] <nik90> zsombi: ack
[12:39] <zsombi> nik90: and there we have a problem: the z-order of the header is higher than the z-order of the popover
[12:39] <zsombi> t1mp: ^
[12:39] <nik90> zsombi: yup
[12:40] <zsombi> nik90: and that cannot be solved any other ways just by using a Window, so must be modal :/
[12:40] <zsombi> nik90: and that may imply API breakage
[12:40] <nik90> zsombi: If I could access the header, I would have done popover.z = header.z + 1
[12:40] <nik90> zsombi: oh
[12:40] <zsombi> nik90: it doesn't work
[12:40] <nik90> zsombi: don't worry about it for RTM, I will move it to the middle of the list to ensure the popover doesnt touch the header
[12:40] <zsombi> nik90: I've set the popover's z-order Number.MAX_VALUE, still teh same
[12:41] <zsombi> nik90: I don't give up that fast ;)
[12:42] <nik90> zsombi: also tbh, I might make my own slider since I might need that to fix bug 1362078
[12:44] <t1mp> zsombi: yes, the z-order of the header must be higher than the z-order of its contents.
[12:44] <t1mp> zsombi: why it cannot be solved except with a Window? Popovers go on top of everything right?
[12:44] <zsombi> t1mp: so that's the problem, that's why the popover goes under it
[12:45] <zsombi> t1mp: goes above the MainView in event handling, but that's a different order
[12:45] <t1mp> zsombi: ohh.. the popover does not go on top of everything it seems?
[12:46] <zsombi> t1mp: hold on... that's not a Popover :D
[12:46] <zsombi> t1mp: it just looks like
[12:46] <t1mp> zsombi: I know, it is a BubbleShape
[12:46] <zsombi> t1mp: then we have a different story... no wonder changes on Popover do not help :D
[12:47] <t1mp> :)
[12:48] <zsombi> t1mp: well, still doesn't help :(
[12:50] <zsombi> t1mp: where do you set the z-order of the header?
[12:50] <t1mp> zsombi: nowhere
[12:50] <t1mp> zsombi: it is added after the contents item in MainView
[12:51] <zsombi> t1mp: then how can it be that goes over it? or is the BubbleShape opaque?
[12:52] <zsombi> t1mp: actually it is... the same effect is there in the toolkit's gallery in teh Sliders
[12:52] <zsombi> nik90: ^
[12:53] <zsombi> t1mp: or not.. maybe my eye is bad...
[12:53] <nik90> zsombi: it is opaque in the gallery
[12:53] <nik90> :D
[12:54] <zsombi> nik90: so it could be that it is not under the header, but it's opaque...
[12:54] <nik90> zsombi: could be, I was guessing in the bug report
[12:55] <t1mp> zsombi: you mean semi-transparent? Opaque means not transparent at all
[12:55] <t1mp> nik90: ^
[12:56] <zsombi> nik90: ehh, yes, semitransparent, not opaque
[12:56] <nik90> erh yes
[12:56] <zsombi> t1mp: ^
[12:56] <t1mp> nik90: ah then your initial guess that it was on top of the header was good
[12:57] <nik90> t1mp: yes but that seems a bit strange that when it is over a specific component (header) its opacity changes?
[12:57] <t1mp> indeed
[13:00] <shuric80> ping
[13:05] <t1mp> shuric80: who is that ping aimed at?
[13:14] <zsombi> t1mp: nik90: ok, so even if I have a Rectangle instead of that BubbleShape, it goes under the Header
[13:15] <zsombi> t1mp: so it's not the item's transparency, but the header position in teh z-order
[13:15] <nik90> ack
[13:16] <nik90> t1mp: so you were right, the header is transparent and over the popover
[13:16] <zsombi> nik90: t1mp: and the Window doesn't help either
[13:17] <zsombi> t1mp: updated https://code.launchpad.net/~zsombi/ubuntu-ui-toolkit/dialog-title-fix/+merge/232386
[13:18] <nik90> zsombi, t1mp: Clock started using QtQuick 2.3. Is that okay?
[13:18] <nik90> I didnt notice any issue after the transition
[13:18] <zsombi> nik90: sure, why not?
[13:18] <nik90> zsombi: well it seemed like SDK, and other apps stopped at 2.2.
[13:18] <zsombi> nik90: have you seen anything that comes in 2.3 you need?
[13:19] <nik90> zsombi: nope, just keeping up to date
[13:19] <zsombi> nik90: :)
[13:19] <nik90> zsombi: since I rewrote clock, might as well do it
[13:19] <zsombi> nik90: yep, good idea...
[13:20] <nik90> zsombi: btw I think you might like bug 1360840 (post-rtm ofc)
[13:20] <zsombi> nik90: but seems the slider vs header is not an easy beast to solve... might need some rewrites here'n'there
[13:20] <nik90> zsombi: as I said before, no worries. Feel free to untag it.
[13:21] <zsombi> nik90: yeah, I've been wining about that long time :D
[13:22] <nik90> zsombi: well things I look forward to post-rtm :D
[13:22] <zsombi> nik90: but that's not enough, you need an invisible (or maybe a small frame around) component that drives the radio effect
[13:23] <nik90> zsombi: I just created an exclusiveGroup { id: group } and set that for a group of checkboxes and it seemed to work.
[13:23] <nik90> I suppose that's the invisible frame
[13:24] <nik90> kalikiana: hey btw would I benefit moving from u1db to qt.labs.settings to get a startup performance boost?
[13:24] <zsombi> nik90: that's the invisible handler :) yes
[13:24] <nik90> kalikiana: it looks like a lot of startup time is spent on getting the value from the u1db document
[13:25] <zsombi> nik90: for app settings yes, go that way
[13:25] <nik90> zsombi: yeah just for app settings like which clock mode to show (dig or analog) etc
[13:26] <nik90> zsombi: will give that a try
[13:26] <zsombi> nik90: yep.... and perhaps we will provide a U1DB backend at some point for it....
[13:26] <nik90> zsombi: it seems offloading the alarm model to loading a bit later improves startup by 0.6 secs :)
[13:26] <zsombi> nik90: some day ... in the future....
[13:26] <nik90> :)
[13:27] <zsombi> nik90: well... :) that's quite some time tbh
[13:27] <mihir> zsombi: also , checkbox doesn't have any text property, I feel it is very important :|
[13:27] <zsombi> mihir: on desktop is, definitely
[13:28] <nik90> zsombi: I know..Kaleo gave me a script to measure app startup time..it is working wonders in seeing if something I did changes the startup time.
[13:28] <mihir> zsombi: i reported it , but in wishlist
[13:28] <mihir> https://bugs.launchpad.net/ubuntu-ui-toolkit/+bug/1323238
[13:28] <zsombi> mihir: the whole instantiation, i.e. Checkbox does not derive from Button is bad
[13:29] <zsombi> mihir: yeah, it is not taken into account... and that is bad!!!
[13:30]  * popey pokes balloons with https://code.launchpad.net/~nskaggs/ubuntu-filemanager-app/add-lxml-depends/+merge/231457
[13:31] <popey> nik90: can https://code.launchpad.net/~nik90/ubuntu-clock-app/implement-location-finding/+merge/231793 land now?
[13:32] <nik90> popey: not until bug 1359866 is fixed
[13:38] <popey> ah okay
[13:39] <popey> nik90: did you tell me about some magical speed up for app starts, or did i dream it?
[13:40] <nik90> popey: this branch https://code.launchpad.net/~nik90/ubuntu-clock-app/conditionally-load-alarmmodel reduces startup time by 24% :D
[13:43] <popey> nice!
[13:44] <zsombi> nik90: it is wise to use 1 alarm model in the whole app ;)
[13:44] <nik90> popey: I am planning to run Kaleo's script which measures startup time against my MRs to ensure we don't regress on it.
[13:44] <nik90> zsombi: I do use only 1 alarm model
[13:44] <nik90> zsombi: I put it in its own file to avoid cluttering my main ubuntu-clock-app.qml file
[13:45] <zsombi> nik90: but one instance I mean... one AlarmModel instance
[13:45] <zsombi> nik90: especially if the backend is EDS...
[13:45] <nik90> zsombi: not sure I follow
[13:46] <nik90> zsombi: I instantiate one AlarmModel and pass it around to the different pages
[13:46] <zsombi> nik90: the MP above shows a removed AlarmModel... so I assume there were more than one instance in the app
[13:47] <nik90> zsombi: ah no, I removed it, and then made it load using a Loader right below it.
[13:47] <nik90> 272	+ Loader {
[13:47] <nik90> 273	+ id: alarmModelLoader
[13:47] <nik90> 274	+ asynchronous: true
[13:47] <nik90> 275	+ }
[13:47] <nik90> once the startup animation is complete, I set alarmModelLoader.source = Qt.resolvedUrl("../alarm/AlarmModelComponent.qml")
[13:47] <zsombi> nik90: ah, ok, that's fine as well
[13:50] <nik90> t1mp: quick question, your Mp https://code.launchpad.net/~tpeeters/ubuntu-ui-toolkit/10-headAnimate/+merge/232201 what does it animate?
[13:51] <nik90> t1mp: the app header entering the page? Or the app header contents when one changes them?
[14:05] <popey> zbenjamin: bzoltan is there a way to re-run the qtcreator wizard?
[14:05] <zbenjamin> popey: yes "rm ~/.config/ubuntu-sdk/firstrun"
[14:06] <popey> thanks! I'll remove the whole directory ☻
[14:07] <zbenjamin> popey: if you want to reset the qtc configuration you also have to remove ~/.config/QtProject/qtcreator i think
[14:07] <zbenjamin> yes, that should completely reset it
[14:07] <popey> zbenjamin: https://imgur.com/yQM0eWM font there looks odd (title)
[14:07] <popey> thanks
[14:07] <zbenjamin> popey: yes i know, that came after a Qt update
[14:08] <popey> k
[14:15] <mhall119> nik90: on http://askubuntu.com/questions/344831/how-to-access-geolocation-information-on-ubuntu-touch you said "worked with segfaulting" did you mean without?
[14:16] <nik90> mhall119: shite yes :D
[14:16] <mhall119> :)
[14:16] <dholbach> jdstrand, shall we do another upload of c-r-t to utopic and backport to the sdk release ppa?
[14:17] <nik90> mhall119: fixed
[14:18] <jdstrand> dholbach: makes sense
[14:18] <dholbach> will do
[14:18] <jdstrand> thanks
[14:23] <dholbach> zbenjamin, ^ an updated click-reviewers-tools (with click-review, which has the --json option) is ~now available in utopic and the sdk release ppa
[14:23] <zbenjamin> dholbach: ok thx!
[14:24] <dholbach> zbenjamin, if you want any other options or any other changes, it should be very easy to accommodate that now
[14:25] <zbenjamin> dholbach: ok i'll check it out. Thanks
[14:44] <nik90> popey: woohoo translations work https://translations.launchpad.net/ubuntu-clock-app
[14:45] <nik90> popey: I guess we need to change the development focus for this
[14:45] <popey> ooh!
[14:50] <justcarakas> is akiva around ?
[14:58] <mihir> zsombi: yup
[14:59] <mihir> zoopster: i understand that, either we should remove that to reduce ambiguity for all the developers
[15:00] <zoopster> mihir: wrong "z" by chance?
[15:00] <mihir> zoopster: sorry :|
[15:00] <mihir> zsombi: ^^
[15:01] <zoopster> mihir: no worries
[15:01] <zsombi> mihir: ?
[15:04] <mihir> zsombi: nothing i read your bug comment
[15:04] <zsombi> mihir: ah, ok :)
[15:04]  * zsombi eod now
[15:09] <matv1> I am seeing error opening shm /lttng-ust-wait-5 in my app log but i have no idea what shm does. should i be bothered?
[15:13] <matv1> ah i see other app logs generate the same messages now.
[15:14] <matv1> matv1 is not so worried anymore
[15:18] <nik90> popey: Hey have you tried the app DowNow ?
[15:18] <nik90> popey: how is it downloading a torrent in the background?
[15:18] <nik90> popey: I downloaded a music file and it opens in the music app and plays it beautifully
[15:18] <popey> not tried that, no
[15:22] <nik90> fginther: ping (if you got some time to discuss an idea)
[15:23] <nik90> fginther: ping (if you got time to discuss an idea)
[15:23] <fginther> nik90, sure
[15:23] <nik90> bah my internet is crappy
[15:24] <nik90> fginther: I remember at malta where you mentioned the possibility of jenkins running the core app AP tests on the device? Is that still the goal?
[15:25] <nik90> fginther: I was given this script http://pastebin.ubuntu.com/8153032/ by Kaleo which measures the app startup time. I wonder if jenkins could run that and let the app devs know if they current MP is increasing/decreasing that start up time.
[15:25] <nik90> fginther: it will be an ideal way to prevent app startup time regressions
[15:26] <fginther> nik90, yes in a limited capacity. I can add mako testing as part of the autolanding process and have been working with balloons the past week to add some more projects to this list.
[15:27] <nik90> fginther: Is adding the script to the test results a possibility? (just checking to see if feasible)
[15:27] <nik90> s/a possibility/possible
[15:27] <fginther> nik90, the app-startup test is out of scope for what we can do right now because the work involved in running it is just behind other higher priority work. It's being run on a per image basis, just not per MP.
[15:28] <nik90> fginther: ah ok
[15:30] <fginther> nik90, we're still blocked on emulator support to add device testing as part of every MP test. It's something that kind of works, but not in the cloud environment we need it too.
[15:31] <nik90> fginther: ah yes, I remember following on a discussion about that in ci-eng
[15:45] <Kaleo> nik90, fginther, we have better measurements being gathered automatically already
[15:45] <Kaleo> I'm going to talk to some people about getting them to the devs
[15:45] <nik90> Kaleo: cool
[15:45] <Kaleo> popey, is dpm off?
[15:45] <nik90> fginther: quick question, why do I see two comments by jenkins https://code.launchpad.net/~nik90/ubuntu-clock-app/conditionally-load-alarmmodel/+merge/232412
[15:45] <nik90> fginther: it seems one is for lp:ubuntu-clock-app and the other for clock-app-dev/ubuntu-clock-app/utopic-3.0
[15:46] <popey> Kaleo: yes, for 1.5 more weeks
[15:47] <fginther> nik90, ugh, the MP maps to both. I'll just need to disable the reboot jobs
[15:48] <fginther> nik90, disabled now, you shouldn't see that any more
[15:50] <nik90> Kaleo, kalikiana: Do you guys know where Qt.labs.settings stores the setting values of apps? I cannot find it inside the com.ubuntu.clock folder.
[15:51] <nik90> fginther: :)
[15:51] <Kaleo> popey, next in line would be?
[15:53] <popey> Kaleo: mhall119
[15:55] <Kaleo> popey, thanks!
[15:57] <DanChapman> nik90 I would presume it to be the same location as the QSettings default. i.e ~/.config/com.ubuntu.clock/com.ubuntu.clock.conf
[15:58] <nik90> DanChapman: ah yes there it is...weird though since U1db stores it in .local/share/com.ubuntu.clock/user-preferences
[15:58] <nik90> DanChapman: hope I dont run into any permission issues
[16:01] <popey> nik90: oh, i know why i havne't tested DownNow - tpb is blocked here!
[16:02] <DanChapman> nik90, It's a standard local path so it should be fine. :-)
[16:02] <nik90> popey: ah yes
[16:02] <nik90> DanChapman: ok
[16:14] <popey> davmor2: are you on virgin or O2 or giffgaff? if so can you confirm https://bugs.launchpad.net/downow/+bug/1355996
[16:17] <davmor2> popey: I'm on ee for phone and virgin for BB so i can have a look but might not be able to confirm
[16:18] <popey> ok
[16:19] <popey> nik90: does it actually work in the background?
[16:19] <nik90> popey: no I checked with a bigger torrent
[16:19] <popey> ah
[16:20] <t1mp> nik90: the headAnimate MR animates a transition between old and new header when you switch pages
[16:21] <nik90> t1mp: ah ok
[16:21] <t1mp> nik90: seems like that MR broke the coloring of the header icons.. I need to fix that before we land the next staging
[16:21] <nik90> t1mp: isnt the next already in?
[16:22] <nik90> staging*
[16:22] <t1mp> nik90: yes it is in staging, I mean before we land the staging to trunk (and image)
[16:23] <nik90> t1mp: ah yes..I thought your branch also made it into the recent landing in image. I was wrong
[16:23] <nik90> t1mp: if the old page didnt have a header, would that still animate the header in the new page?
[16:26] <davmor2> popey: I see nothing on ee or virgin bb
[16:26] <popey> ok, pls confirm the bug then, thanks
[16:27] <dholbach> beuno, jdstrand: if you could review https://code.launchpad.net/~dholbach/click-reviewers-tools/modules-module-plus-tests/+merge/232444 I'd appreciate it
[16:27] <dholbach> beuno, ^ now with tests to make sure we don't forget to run certain checks on modules
[16:27] <beuno> the "with tests" part is what sold it
[16:27] <beuno> looking
[16:39] <elopio> nik90: I've just found that you can add cities from the top of the app
[16:40] <nik90> elopio: oh you didnt see it yesterday
[16:40] <elopio> that's nice but hard to find. Will there be a clue for that?
[16:40] <nik90> elopio: not for the action itself, but the clock app is supposed to have 2 cities added by default
[16:40] <elopio> not at all. I found it today because I confused up and down :)
[16:41] <nik90> elopio: this way the user will know there is the world city feature
[16:41] <nik90> elopio: if you report a bug I can assign it to the design team and see if they have any inputs
[16:42] <elopio> nik90: I'll report the bug.
[16:43] <elopio> it looks pretty nice the small clock next to the city. I was wondering why so much empty space, now it all makes sense.
[16:43] <nik90> elopio: It is easy to add 2 sample cities, but I was told that the 2 preset cities would be based on which manufactures sells it
[16:43] <balloons> ahh, you want a graphical hint about the action? for reference I found it very easily..
[16:44] <elopio> nik90: that makes sense too.
[16:44] <beuno> dholbach, I like this very much
[16:45] <elopio> balloons: how did you know you had to swipe down?
[16:45] <dholbach> beuno, so... is it good to go, or anything missing?
[16:46] <elopio> no other app has gestures on the top like that.
[16:46] <beuno> dholbach, nitpicking and will submit my review soon
[16:46] <dholbach> beuno, all right... wfm
[16:46] <dholbach> I'll take care of it tomorrow morning then
[16:46] <dholbach> my EOD is calling :)
[16:46] <dholbach> see you tomorrow!
[16:46] <dholbach> and thanks for the review!
[16:47] <beuno> dholbach, sent
[16:47] <beuno> night!
[16:47] <dholbach> :)
[16:48] <balloons> elopio, I'm not sure eaxctly. I do remember my first run as confusing because I couldn't find any way to interact with the app. When I saw the bottom swipe, I thought I'd try the top as well. And it immeadiately tells you what it does
[16:48] <balloons> I think a graphical hint there would aid discovery
[17:07] <marcamon> hi
[17:11] <nerochiaro> bfiller: please when you have time don't forget to look at https://code.launchpad.net/~phablet-team/gallery-app/gallery-app-restrict-pick-content-type/+merge/230776
[17:11] <bfiller> nerochiaro: yup, on my list
[17:19] <balloons> ahayzen, how's https://code.launchpad.net/~andrew-hayzen/music-app/ap-helper-refactor-002/+merge/231815?
[17:20] <ahayzen> balloons, good we just had an issue where upstream ms2 db schemas changed...just waiting for https://code.launchpad.net/~vthompson/music-app/patch-mediascanner-db-ap-tests/+merge/232337 to land :)
[17:20] <ahayzen> balloons, but if u could review the autopilot one I would really appreciate it as i don't wanna make the tests worse than they already are ;)
[17:22] <balloons> ahayzen, sure thing. I'll do so now
[17:22] <ahayzen> balloons, thanks :)
[17:22] <ahayzen> balloons, i'll merge it with trunk when victor's mp lands
[17:22] <balloons> I'm stealing victor's changes too
[17:22] <ahayzen> balloons, will you and/or popey be able to push to the store when victor's mp lands? as we are failing in CI until then?
[17:23] <balloons> ahayzen, will your changes be ready to go also?
[17:23] <ahayzen> balloons, if u like them :) i'll merge with trunk as soon as victor' s is merged
[17:23] <nik90> t1mp: is what is suggested in bug 1362081 even possible?
[17:23] <balloons> ahayzen,  that's the plan then.. take everything
[17:23] <ahayzen> balloons, i can ping victor to check if he thinks it is ok
[17:25] <balloons> ahayzen, did you not plan to seperate out the tests into new py files?
[17:25] <balloons> like test_nowplaying or something like that
[17:25] <balloons> maybe it doesn't make sense
[17:25] <ahayzen> balloons, i plan to go through the tests in separate(s) mp ... this mp is just setting up the helpers really
[17:26] <ahayzen> balloons, that sounds like a good plan though i may try it in one of the next mps
[17:26] <balloons> kk
[17:26] <ahayzen> balloons, the problem we have is that it is hard to test just one page as for us u usually click on 2/3 pages to do things so as u said may not make sense
[17:27] <ahayzen> but i guess a few would
[17:27] <balloons> ahayzen, right, which is why I think leaving it as one might be just fine
[17:28] <ahayzen> balloons, yeah :) i'm trying to get the helpers split up first :)
[17:34] <ahayzen> balloons, victor says he is good with merging in ap-refactor-002 ...so up to u now :)
[17:40] <balloons> ahayzen, just trying to figure out what the deal is with the device runs
[17:42] <ahayzen> balloons, as in it isn't running on device for u?
[17:46] <ahayzen> balloons, FYI the ap-refactor-002 passed jenkins with the merge of victors mp
[17:59] <balloons> ahayzen, I'm having a lot of trouble getting the app to launch on device and run tests
[17:59] <ahayzen> balloons, which image are you on?
[17:59] <ahayzen> balloons, u'll have to be latest for ms2 db changes to take affect
[17:59] <balloons> latest proposed or rtm..
[17:59] <ahayzen> balloons, errr i'm on latest devel-proposed
[17:59] <balloons> but the app just isn't launching
[17:59] <ahayzen> balloons, what does it say in the log?
[18:00] <balloons> it's introspect error.. nothing to do with the tests themselves
[18:00] <ahayzen> balloons, yeah thats what i got until i upgraded to the latest image
[18:00] <balloons> I guess to be fair I got it running, but it failed on flo
[18:00] <balloons> let me upgrade the mako
[18:02] <balloons> and it fails on rtm for the same reason you mentioned
[18:04] <balloons> ahayzen, I approved
[18:04] <ahayzen> balloons, yey thanks :)
[18:05] <ahayzen> balloons, i've top approved... so when that merges are we able to push it to the store?
[18:05] <balloons> ahayzen, yes I will
[18:06] <ahayzen> balloons, awesome thanks
[18:06] <balloons> I'm just concerned about it failing on rtm
[18:23] <ahayzen> balloons, yeah but i assume rtm will get the new ms2 package soon?
[18:23] <balloons> ahayzen, I just requested it so we are good
[18:23] <ahayzen> balloons, and how are we supposed to deal with this in the future? ... we've had the chicken and egg problem before
[18:24] <ahayzen> balloons, eg CI fails unless we update music-app to new ms2 api .... stable music-app will fail due to music-app using new api...
[18:24] <balloons> ahayzen, same as we always have.. just keep your eyes open for this ;-) But honestly it should be fairly sane since rtm is locked down much more, and soon utopic will be too
[18:25] <ahayzen> balloons, yeah i guess... at least this is only autopilot failing and not the whole app as we some previous
[18:25] <ahayzen> balloons, anyway gtg i'll be back in a bit :) thanks for reviewing
[18:25] <balloons> yes, test failures are easy to deal with
[18:25] <balloons> you're welcome
[18:25] <balloons> ttyl
[18:36] <balloons> ahayzen, ok finally got a good run on a device and I see a lot of errors
[18:38] <balloons> everything but 1 test fails
[18:46] <nik90> Saviq: Can you check https://code.launchpad.net/~nik90/ubuntu-clock-app/fix-worldcity-trigger-try2/+merge/232461 to see if it solves the accidental world city trigger.
[18:47] <nik90> Saviq: I was thinking of hiding the add city button as well, however practically it doesn't turn out so good when the user slows down the movement and the add city button appears out of no where.
[18:47] <nik90> Saviq: but it has definitely solved the issue of the add world city triggers.
[18:48] <nik90> popey: shall I remove clock reboot from the store?
[18:49] <Saviq> nik90, I don't think you need to hide it (although it could fade in to full opacity with the distance of the overshoot)
[18:50] <nik90> Saviq: at the moment it grows in size based on the distance of the overshoot
[18:50] <nik90> Saviq: is the fade required on top of that?
[18:50] <Saviq> nik90, "required" is a hard word :)
[18:51] <Saviq> nik90, I'm just rambling here :)
[18:51] <Saviq> nik90, maybe it doesn't even matter, but in any case that sounds like a UX decision to make
[18:52] <nik90> Saviq: Can you test the interaction? If it is acceptable, I will get a code review. Not sure how to get design to test this since it is a interaction issue and not just something UI.
[19:09] <popey> nik90: yes, i would.
[19:09] <nik90> popey: ?
[19:10] <popey> 19:48:45 < nik90> popey: shall I remove clock reboot from the store?
[19:11] <nik90> popey: ah yes
[19:28] <ahayzen> balloons, wha? have you got a log?
[19:29] <ahayzen> balloons, oh and thanks for the comment on my decorator ;) hopefully i can use that on some of the other helpers as well
[19:30] <balloons> ahayzen, http://paste.ubuntu.com/8162115/
[19:31] <ahayzen> balloons, have you got the latest UITK autopilot helpers?
[19:31] <balloons> it's possible I don't
[19:31] <balloons> I didn't update today, heh
[19:31] <ahayzen> balloons, i think i had to update mine manually IIRC
[19:31] <balloons> ahayzen, ohh wait, no it's not possible
[19:32] <balloons> adt pulls them
[19:32] <balloons> you can see that at the top
[19:32] <ahayzen> hmmm let me run that specific test again maybe something has changed in the latest image that has broken things
[19:32] <ahayzen> balloons, is that on mako latest devel-proposed?
[19:33] <balloons> image 210, mako
[19:33] <balloons> I haven't pushed to the store because of it
[19:34] <ahayzen> ok let me check my device...
[19:35] <ahayzen> balloons, just ran the first one that failed on yours on my device http://pastebin.ubuntu.com/8162156/
[19:36] <ahayzen> hmmm unless something bad is happening
[19:36] <ahayzen> uhoh hang on let me clear my ~/autopilot/music_app
[19:37] <ahayzen> balloons, also note i'm running via $ phablet-test-run -v music-app music_app.tests.test_music.TestMainWindow.test_artists_tab_album > /tmp/out.log
[19:38] <balloons> ahayzen, glad it working for you!
[19:39] <ahayzen> balloons, but why isn't it working for u?
[19:39] <balloons> well I can try a bit more now
[19:39] <ahayzen> balloons, all i am doing is installing via click-buddy and then doing phablet-test-run
[19:40] <balloons> ahayzen, bah, I forgot to build it first
[19:40] <balloons> lol
[19:40] <ahayzen> hah
[19:40] <balloons> I used the pre-existing click
[19:40] <ahayzen> that makes sense
[19:40] <ahayzen> as i changed the objectName's
[19:40] <balloons> yep.
[19:41] <ahayzen> balloons, hopefully it'll pass this time then :)
[19:49] <balloons> ahayzen, passing now ;-)
[19:50] <ahayzen> balloons, few thanks :) guess ur gonna push to store now?
[19:57] <balloons> ahayzen, I do see some graphical artifacts.. do you see them?
[19:57] <balloons> part of the app is transparent to the dash
[19:57] <balloons> in the now playing screen
[19:57] <ahayzen> balloons, like being able to see the dash?
[19:57] <balloons> yep
[19:58] <ahayzen> balloons, yeah some funky stuff happens in autopilot...never seems to happen when running the real app
[19:58] <Saviq> nik90, I'll try it out tomorrow
[19:58] <balloons> ll
[19:58] <nik90> Saviq: sure
[19:59] <Saviq> nik90, ideally you should be able to just send a designer the click package, right now it's not as easy as tapping on it somewhere in the ui
[19:59] <ahayzen> balloons, its like transparency doesn't quite work as the listitem actions bg used to be (probably still is) incorrect
[19:59] <Saviq> nik90, but it shouldn't be too difficult to get them to use pkcon-install
[19:59] <nik90> Saviq: true, I will do that
[20:01] <ahayzen> balloons, but it is only seen when running inside autopilot...i wonder what actually causes it?
[20:04] <twstddev> nik90, ping
[20:04] <nik90> twstddev: pong
[20:04] <twstddev> nik90, http://lousy-puppy-2058.vagrantshare.com/?lat=51.507351&long=-0.127758
[20:04] <twstddev> url will expire in an hour
[20:05] <twstddev> oh, actually in 8
[20:05] <nik90> twstddev: 8 hrs? I can test in about 30 mins.
[20:05] <twstddev> should be fine. let me know when you are done
[20:05] <nik90> twstddev: btw, I need only one result
[20:13] <popey> twstddev: nice one!
[20:14] <twstddev> nik90, ok. let me reindex data and remove different languages first
[20:14] <twstddev> popey, thanks. but sphinx is not that fast with coordinates search :\
[20:15] <balloons> ahayzen, sadly UI visual issues are SO hard to find via automated testing
[20:15] <ahayzen> balloons, yeah :/ oh well i'll continue ignoring them then :)
[20:15] <balloons> ahayzen, so I don't know persay, but it could be a weird interaction with the components, or maybe just a hardware specific thing
[20:15] <twstddev> nik90, I have to close the connection for couple of minutes
[20:16] <nik90> twstddev: go ahead.
[20:16] <nik90> twstddev: I cannot test yet fully
[20:16] <twstddev> nik90, ok
[20:21] <balloons> ahayzen, I will note it also happens on flo, so it's not specific to mako
[20:21] <md6sum> nik90, ping?
[20:22] <ahayzen> balloons, magic :)
[20:22] <ahayzen> balloons, did the flo tests pass in the end?
[20:22] <nik90> md6sum: pong
[20:22] <md6sum> The alarm in the new clock-app does not work
[20:22] <md6sum> due to the system time being stuck
[20:22] <md6sum> You mentioned this morning it was fixed in 203
[20:22] <nik90> md6sum: What device are you running this on?
[20:23] <md6sum> mako
[20:23] <nik90> md6sum: so your system time does not update at all?
[20:23] <md6sum> Right now it says 7:54 in the upper left
[20:23] <md6sum> In reality it is 10:23
[20:23] <md6sum> *upper right
[20:24] <nik90> md6sum: I am not sure why that is. I use my mako almost like a clock to check time and so on.
[20:24] <nik90> md6sum: its being spot on
[20:24] <popey> md6sum: what image number you on?
[20:24] <md6sum> r203
[20:25] <md6sum> It takes some time to update the time (Now it is showing 10:25 correctly)
[20:25] <popey> pretty sure this is a known bug.
[20:26] <nik90> popey: the system time is never off by so many minutes.
[20:26] <nik90> I agree it is sometimes off by a few seconds
[20:26] <popey> 203 is old
[20:27] <nik90> isnt 203 the current promoted image?
[20:27] <popey> yes
[20:27] <popey> ☻
[20:27] <popey> but I'm sure it's fixed in a newer image..
[20:27] <nik90> I don't believe a bug as serious as this was left in the promoted image
[20:27] <nik90> md6sum: would you be able to test the latest-devel image?
[20:27] <md6sum> It is an old bug
[20:29] <md6sum> Not sure why you dont see it, though.
[20:29] <twstddev> nik90, http://anxious-jerboa-3503.vagrantshare.com/?lat=51.507351&long=-0.127758
[20:29] <nik90> md6sum: I am running the rtm images atm
[20:33] <daker> nik90: if i define two alarms with 1min difference, they start to play both their alarm sounds
[20:33] <daker> i suppose the alarm is not using media-hub
[20:33] <daker> alarm backend*
[20:34] <nik90> daker: why does that matter?
[20:34] <nik90> daker: https://bugs.launchpad.net/indicator-datetime/+bug/1358890
[20:34] <daker> yes that one
[20:34] <nik90> daker: we are still discussing what should happen if 2 alarms ring at the same time
[20:35] <daker> the first one stops & the second one start
[20:36] <nik90> daker: is that what happens or what should happen?
[20:37] <md6sum> nik90, not sure if I have the time to do the latest-devel switch back and forth now. Let's just hope we get an promotion on Thursday or Friday and I will test again.
[20:37] <md6sum> Another note: I can't seem to create an alarm which does not repeat
[20:38] <nik90> md6sum: yes atm only recurring alarms are supported. However I am working atm on enabling single type alarms. It is almost done :-)
[20:38] <popey> i have two phones on proposed
[20:38] <popey> (and a tablet)
[20:38] <popey> they all show the right time
[20:39] <nik90> md6sum: ^^
[20:39] <nik90> told you
[20:40] <md6sum> If only I hadn't sold my old phone and could video it...
[20:49] <twstddev> nik90, previous link is closed, was very inaccurate, here is another http://brazen-dugong-9871.vagrantshare.com/?lat=51.765606&long=-1.246990
[20:51] <nik90> twstddev: this seems much better
[20:51] <nik90> twstddev: did some web searches
[20:51] <nik90> yet to try with code
[20:54] <nik90> popey: do you know if jhodapp is US or EU timezone?
[20:54] <jhodapp> nik90, US
[20:54] <nik90> jhodapp: :)
[20:54] <nik90> jhodapp: I had a quick question
[20:55] <nik90> jhodapp: I noticed that the Audio{} component offers a volume property which goes from 0.0 (silent) to 1.0 (max). Does this simulate the min and max platform volume levels correctly?
[20:56] <nik90> jhodapp: In the clock app, we are including an alarm volume slider which has a range between 1-100 db. I was hoping to connect that to the Audio component's volume property.
[20:56] <jhodapp> nik90, that's not hooked up to anything
[20:57] <nik90> jhodapp: just wondering if that was the way to go.
[20:57] <popey> balloons: ahayzen approved music into the store
[20:58] <nik90> jhodapp: I don't expect it to actually change the platform volume since I am guessing confined apps cant do that.
[20:58] <ahayzen> popey, thanks :)
[20:58] <nik90> jhodapp: but would it simulate it on the sound it plays through the component somehow
[20:58] <jhodapp> nik90, so what do you want it to do then?
[20:58] <nik90> jhodapp: I am trying to solve https://bugs.launchpad.net/ubuntu-clock-app/+bug/1362078
[20:59] <balloons> popey, fyi, until the next rtm image the test will break
[20:59] <nik90> jhodapp: when the user moves the alarm volume slider, it should play a sample alarm ringtone in the appropriate volume for the user to judge if it loud enough or not.
[21:00] <nik90> jhodapp: I will be obviously playing it using Audio{}, but not sure really how to change the volume of the playback to help the user
[21:02] <jhodapp> nik90, oh I see, well that would be needing to set the volume on the pulse audio stream type
[21:02] <jhodapp> nik90, it's currently not supported, but you might ping rsalveti for his thoughts...he's doing the pulse audio work right now
[21:03] <nik90> jhodapp: ah will do
[21:03] <jhodapp> nik90, I'm in the process of adding different stream types to media-hub right now that an app would set on the MediaPlayer or Audio classes
[21:03] <jhodapp> nik90, so in theory, we could hook up the volume for certain stream types
[21:03] <nik90> jhodapp: but wouldn't the work you do in media-stream be sufficient for me?
[21:03] <nik90> jhodapp: since the alarm slider is supposed to only emulate the alarm volume loudness
[21:04] <nik90> jhodapp: the actual setting of the alarm volume will be done by indicator-datetime which rings the alarm
[21:04] <jhodapp> nik90, yes, but I just recommend talking to rsalveti because he has more of a comprehensive view of how this should all work...he's been thinking about this specific issue a lot more than me so far
[21:04] <nik90> jhodapp: understood
[21:04] <jhodapp> nik90, yeah and in that case, we might want another stream type such as "preview" or something like that
[21:05] <nik90> jhodapp: hmm wouldn't it automatically come under the ubuntu-clock-app stream? like every other app that creates sound?
[21:05] <nik90> plays a sound*
[21:05] <jhodapp> nik90, it would if you didn't set the stream-type property in QML
[21:07] <nik90> ok
[21:15] <daker> is it me or the transfert indicator is buggy for more than a month ?
[21:15] <nik90> the transfer indicator is buggy
[21:15] <nik90> but I heard that a ton of fixes are incoming..so be prepared ;)
[21:16] <daker> ah ok
[21:53] <ahayzen> balloons, should i be doing get_count() or @property count in the python helpers?
[21:54] <balloons> elopio, preference ^^?
[21:54] <elopio> ahayzen, balloons: I prefer methods to properties.
[21:54] <balloons> good, we agree :-)
[21:55] <ahayzen> elopio, balloons cool i'll continue doing get_count() then :) thanks just wanted to check before i go one way
[21:55] <elopio> but in that case, I don't have a good argument. Do the one that gives you consistency on the module.
[21:55] <balloons> we've already used methods, hehe
[21:55] <ahayzen> heh yeah i have like get_track(i) so get_count() makes sense
[21:57] <ahayzen> balloons, how would you recommend to get a track by a title/artist etc before we used to do select_many_retry() then for the objects until the title/artist matched....i'm thinking of doing for i in range(count) get_track(i) then compare the label in that row
[21:58] <ahayzen> balloons, or should the test just use known rows/positions and not search for things
[21:59] <balloons> ahayzen, we should be in control of all the data so there should be no reason to search
[21:59] <ahayzen> balloons, that was my thought
[21:59] <balloons> if it should be the third track, it should be the third track right?
[22:00] <ahayzen> one would hope
[22:00] <ahayzen> balloons, then we could get rid of things like....
[22:00] <ahayzen> def get_songs_tab_tracktitle(self, trackTitle):
[22:00] <ahayzen>         tracktitles = self.select_many_retry(
[22:00] <ahayzen>             "Label", objectName="tracktitle")
[22:00] <ahayzen>         for item in tracktitles:
[22:00] <ahayzen>             if item.text == trackTitle:
[22:00] <ahayzen>                 return item
[22:00] <ahayzen> balloons, which are pretty nasty ;)
[22:00] <balloons> ohh yes please
[22:01] <ahayzen> balloons, ok i'll do that :) ...i guess it will speed up the tests as well?
[22:01] <balloons> mm.. it should simplify things I guess
[22:01] <ahayzen> :)
[22:01] <balloons> not sure how much speedup we'll see, but some
[22:02] <ahayzen> balloons, at least this code is finally disappearing :)
[22:26] <danielholm> Hi, is it possible to show QML components in an online account plugin Main.qml? like a web view or textfields, or what ever other QML API syntax?
[22:35] <danielholm> never mind
[23:23] <Randy_O> are there any QML ubuntu SDK programmers around?
[23:23] <Akiva-Thinkpad> Randy_O, yah
[23:23] <Akiva-Thinkpad> hold on
[23:24] <Randy_O> Akiva-Thinkpad, have you worked with orientation in the phone?
[23:24] <Akiva-Thinkpad> Randy_O, as in what? what does the app look like when it is oriented differently?
[23:24] <Akiva-Thinkpad> Say, landscape vs portrait?
[23:25] <Randy_O> Akiva-Thinkpad, I'll explain, I'm trying to lock the orientation in either portrait or landscape. Using auto orient value forces the app to stay in portrait.
[23:25] <Randy_O> Akiva-Thinkpad, know any tricks to lock in landscape?
[23:25] <Akiva-Thinkpad> Randy_O, hmmmm good question. I have never gone about making my app lock to an orientation.
[23:26] <Akiva-Thinkpad> Randy_O, sorry for this question, but why is it important to have your app appear sideways when you use it in landscape?
[23:26] <Randy_O> Akiva-Thinkpad, It's for a reader app, locking orientation (in wither orientation) is a good feature when moving around with a phone or tablet
[23:27] <Akiva-Thinkpad> ah this is a feature then?
[23:27] <Randy_O> Akiva-Thinkpad, like reading sideways in bed
[23:27] <Akiva-Thinkpad> okay that makes sense
[23:27] <Randy_O> Akiva-Thinkpad, yes, trying to find a way to lock (one way or the other way)
[23:27] <Akiva-Thinkpad> Randy_O, Do me a favour; ask this on askUbuntu, and use the tags qml, ubuntusdk, programming, qtcreator, ubuntu-touch
[23:28] <Akiva-Thinkpad> send me the link once you do
[23:28] <Randy_O> Akiva-Thinkpad, will do
[23:28] <Randy_O> Akiva-Thinkpad, send link here?
[23:28] <Akiva-Thinkpad> yah just post it here
[23:28] <Akiva-Thinkpad> this helps the community at large when you ask there
[23:29] <Randy_O> Akiva-Thinkpad, for sure, I'm a huge fan of ask ubuntu
[23:29] <Akiva-Thinkpad> oh good :)
[23:29] <Akiva-Thinkpad> i'll give it an upvote and a bounty if you wish
[23:29] <Akiva-Thinkpad> shouldnt take too long to get it answered.
[23:33] <Randy_O> Akiva-Thinkpad, http://askubuntu.com/questions/516947/how-to-lock-ubuntu-device-orientation-in-portrait-or-landscape-from-user-input
[23:33] <Akiva-Thinkpad> ty
[23:33] <Randy_O> Akiva-Thinkpad, any help is apprecaited, thanks.
[23:35] <ahayzen> balloons, should dialogues have their own helpers? or should the methods go in the page they are spawned from?
[23:46] <rpadovani> mzanetti, ok, if you don't mind we'll do hangout on friday