19:32 #startmeeting Ubuntu Touch Clock app meeting 19:32 Meeting started Fri May 31 19:32:34 2013 UTC. The chair is popey. Information about MeetBot at http://wiki.ubuntu.com/meetingology. 19:32 19:32 Available commands: #accept #accepted #action #agree #agreed #chair #commands #endmeeting #endvote #halp #help #idea #info #link #lurk #meetingname #meetingtopic #nick #progress #rejected #replay #restrictlogs #save #startmeeting #subtopic #topic #unchair #undo #unlurk #vote #voters #votesrequired 19:32 yeah, nice to be back 19:32 (am away again next week though) ☻ 19:32 oh 19:32 blueprint: https://blueprints.launchpad.net/ubuntu-phone-commons/+spec/initial-clock-development 19:33 bugs: https://bugs.launchpad.net/ubuntu-clock-app/+bugs 19:33 reviews: https://code.launchpad.net/ubuntu-clock-app/+activereviews 19:33 how are things? 19:33 I wanted to ask..do you face the performance issues on the nexus 4 or 7 with the latest build? 19:33 both 19:33 month-2 burndown: http://status.ubuntu.com/coreapps-13.10/ubuntu-clock-dev-coreapps-13.10-month-2.html 19:33 to a greater degree on the nexus 7 19:34 did you see the video? 19:34 which video? 19:34 http://www.youtube.com/watch?v=nuE9R81ex-Q 19:34 nik90: it ticks off about 45 seconds in each actual minute 19:35 ok 19:35 like each second tick takes about 1.25 seconds 19:36 me and renato_ have been cleaning up code before we start working on the performance improvement. 19:36 to be honest, I might need someone to review the code to see where the bottleneck is 19:37 We have disabled some animations and hoping to see an improvement but from the video doesnt seem to have improved it at all.. 19:37 nik90: is it just updating itself once a second, or is it calculating the time-since-start once a second? 19:38 looks like it's incrementing on a timer 19:38 * nik90 looks at code 19:38 http://bazaar.launchpad.net/~ubuntu-clock-dev/ubuntu-clock-app/trunk/view/head:/stopwatch/AnalogStopwatch.qml#L76 19:39 so instead of incrementing decimalsTotal when the Timer is triggered, it should be calculating currentTime - startTime to see how many seconds *actually* passed 19:39 ok basically it keeps track of a variable called decimalsTotal which is updated 100 ms 19:39 since the timer doesn't guarantee accuracy 19:39 yeah 19:39 so it may be 100ms, or it may be 120ms 19:40 mhall119: I can try that approach this weekend to see if it improves the situation 19:40 nik90: cool, it should work better 19:41 mhall119, popey: Do you test the timer on the devices? 19:41 since it uses a similar code logic 19:41 nope, but I can ☻ 19:41 popey: please do. Then it might part of a bigger problem which needs to be addressed asap 19:41 a timer which cant keep time is useless 19:42 doing it now 19:42 agreed 19:42 heh, stopwatch on my iphone was still running 19:42 hehe 19:42 52:42:42:50 19:42 lol 19:42 nik90: I ran the timer for 30 seconds, it took about 36 seconds to complete 19:43 so looks like the same problem 19:43 mhall119: ok..so issue confirmed 19:43 will definitely look to solving it this weekend 19:43 found another bug in timer 19:44 grab the hand and pull round to 59 19:44 when you go past 59 it changes from 00:59 to 59:59 19:44 sometimes 19:45 popey: I will try to reproduce it later. I couldnt trigger the bug now 19:46 popey, mhall119: Do you know how to use the QtMobility package? I finally figured how to get the current location however, 19:46 import QtMobility 2.0 gives an error 19:46 also, spin hand round fast and you have to spin multiple times to get minutes to clock over 19:46 lemme do it on video 19:46 ahem 19:47 yeah, I don't think it's called QtMobility anymore, they split it up in Qt5 19:47 nik90: did you try import QtLocation? 19:48 popey: yeah moving the hand too fast sometimes doesnt increment the minutes. I think that is because your hand probably leaves the circle at which it doesnt accept input 19:48 not sure, possibly 19:48 mhall119: tried import QtLocation 2.0 19:48 doesnt work 19:48 the n7 is painfully slow 19:49 on the n4 the start button is off screen 19:49 i cant start the timer 19:50 nik90: do you have qtdeclarative5-qtlocation-plugin installed? 19:50 mhall119: yes 19:50 popey: will take a look at the positioning logic 19:51 will file a bug 19:51 popey: awesome 19:52 mhall119: I tried pinging florian but I think I missed the timing since it is already friday evening. Will try again on Monday. 19:52 https://bugs.launchpad.net/ubuntu-clock-app/+bug/1186395 19:52 nik90: try import QtLocation 5.0 19:52 nik90: he's in brazil, so not his evening yet 19:53 that's what /usr/lib/i386-linux-gnu/qt5/qml/QtLocation/plugins.qmltypes shows 19:53 popey: oh 19:53 mhall119: that works :) 19:54 \o/ 19:54 ok, almost out of time here 19:54 the month-2 burndown shows all TODO: http://status.ubuntu.com/coreapps-13.10/ubuntu-clock-dev-coreapps-13.10-month-2.html 19:54 are any of those inprogress yet? 19:54 also, did you ever find where calum send the visual design? 19:54 alrite, so 4 bugs to sort out..(lags in timer ansd stopwatch, start timer button positioning, 00:59 t0 59:59 issue) 19:55 mhall119: I have sent the email..so waiting on the reply 19:55 popey: do you happen to know where he sent them? 19:55 ? 19:55 oh, yes, mail sent today 19:56 popey: but did he say where the designs are? 19:56 Jouni sent them via email 19:56 popey: you might want to see the email sent by Jouni 19:56 "I've pushed the designs to ubuntu-clock-app/design." 19:56 popey: didnt see the assets in the email nor in ubuntu-clock-app/design 19:56 hmm 19:57 david suggested that he commited but probably forgot to push it 19:57 wonder where that went 19:58 i dont know, sorry 19:58 no worries, I already sent a mail to jouni. 19:58 so we're still technically blocked on visual design 19:58 nik90: how about the other work items? 19:59 I am a bit overwhelmed at the moment. I will be postponing the autopilot tests to next month 19:59 need to first address the critical bug and also implement the visual designs 19:59 ok 19:59 thats fine ☻ 19:59 nik90: FYI, found these qtlocation docs: http://qt.developpez.com/doc/5.0-snapshot/index-qtlocation-module/ 19:59 might be helpful 19:59 thnx 19:59 nik90: how is the rest of the dev team doing? 20:00 well technically it is me, alessandro and renato 20:00 alessandro was working on the world clock, but I havent heard much from the work done on it 20:01 renato and me have been spending the past 2 weeks cleaning and organiszing the code base 20:01 ok 20:01 renato is occupied at the moment, so I am trying to get fixes done when I can 20:02 that's fine, you guys are already ahead of schedule on this app 20:02 true, but we need to meet the beta milestone 20:02 I expect that we'll run into some questions or blockers while implementing the visual design,but that will hopefully make it easier for the other dev teams when it's their turn 20:03 true :-) 20:03 anything else? 20:04 not from me, popey ? 20:05 https://bugs.launchpad.net/ubuntu-clock-app/+bug/1186396 20:05 sorry, new bug 20:05 but new blurry video which is good 20:05 ok 20:05 nothing else 20:06 Thanks for coming to the hangout yesterday, realise it was difficult as you were at Uni 20:06 much appreciated 20:06 was awkward but couldnt miss the visual designs :) 20:06 ☻ 20:07 did you get them via the dropbox links? 20:07 I got 1 video and 4 pics 20:07 I missed the other video link. 20:07 well, we can wait for the reply to your mail for the "official" ones 20:07 yeah exactly 20:07 ok, nothing more from me.. 20:07 alrite then 20:07 bye mhall119, popey 20:07 i was waiting for mhall119 to endmeeting then realised I started it 20:07 #endmeeting