19:33 <popey> #startmeeting Ubuntu Touch clock app meeting
19:33 <meetingology> Meeting started Fri Jun 21 19:33:17 2013 UTC.  The chair is popey. Information about MeetBot at http://wiki.ubuntu.com/meetingology.
19:33 <meetingology> 
19:33 <meetingology> 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:33 <popey> blueprint: https://blueprints.launchpad.net/ubuntu-phone-commons/+spec/initial-clock-development
19:33 <popey> reviews: https://code.launchpad.net/ubuntu-clock-app/+activereviews
19:33 <popey> bugs: https://bugs.launchpad.net/ubuntu-clock-app/+bugs
19:33 <popey> burndown: http://status.ubuntu.com/coreapps-13.10/
19:34 <popey> How's you?
19:34 <nik90> I am good. you?
19:34 <popey> Good thanks ☻
19:34 <nik90> I see someone has added zsombi's blueprint as dependency
19:34 <popey> yes, that should keep us focussed
19:35 <nik90> I was planning to add few others like the sdk's future widgets
19:35 <popey> (and him)
19:35 <nik90> will do so tomorrow
19:35 <popey> feel free
19:35 <popey> great
19:35 <popey> are the month 3 work items up to date?
19:35 <nik90> so yeah today I got the visual designs for stopwatch and timer from michal
19:35 <nik90> sort of
19:36 <nik90> I may need to add couple of workitems that I am currently working on
19:36 <popey> what's that?
19:36 <nik90> the visual designs for individual functionalities, some data caching
19:37 <popey> ah ok
19:37 <popey> yes, please add them. of course that's going to make the burndown chart go in the wrong direction
19:38 <popey> but that can't be helped, I'd rather we track everything
19:38 <nik90> yeah, its just that I have got know about that as I started working on certain features
19:38 <popey> yeah, it happens
19:39 <nik90> I also talked to thomas vobb regarding the timezone API this week, and also to get the system's timezone
19:39 <popey> excellent Thomas is a good person to keep in contact with
19:40 <nik90> yeah very friendly and he is working on many stuff
19:40 <popey> yeah
19:40 <nik90> so he has added some of them to hhis work items.
19:40 <popey> excellent
19:40 <popey> I'll catch up with him on monday
19:41 <nik90> at the moment, the world clock depends a lot on the online API. However we can reduce that with the use of tzdata present in ubuntu by default
19:41 <nik90> so he told me he is working on getting a qml api for me to use for that
19:41 <nik90> I will try to get the status of the theming support from florian on monday
19:41 <popey> ok.
19:42 <nik90> but overall things are much easier now since the backend is mostly ready
19:42 <nik90> so I am just rearranging the ui which is quite simple
19:42 <popey> how about autopilot?
19:42 * popey pokes balloons ☻
19:42 <balloons> :-p
19:43 <balloons> We're still waiting to get the first merge in
19:43 <balloons> me
19:43 <nik90> Since I was working on the clock world clocks last week, I did not write autopilot test for it. But now that it is ready I will get some autopilot tests for that done
19:43 <nik90> balloons: How does one test if the stopwatch/timer keeps time?
19:44 <nik90> balloons: we had cases where it lagged behind when ran for few minutes
19:44 <balloons> if the timer keeps time? Well heh, that's probably more in the unit test world
19:44 <nik90> hmm..totally forgot about those unit tests
19:44 <balloons> it's a line.. for autopilot i would want to make sure the timer increments and starts and stops
19:44 <balloons> ensuring the time value is correct is at a lower level imho
19:45 <nik90> well the timer does increment however sometimes it lags behind by a very small amount..this over time integrates to a big delay
19:45 <nik90> so I am guessing I will have to use unit tests or manual tests to ensure that they dont happen
19:46 <nik90> I havent written unit tests before. Can you I ping you if I have any questions about them?
19:47 <nik90> balloons: ?
19:48 <balloons> nik90, you can ping me indeed. But I'm not a champion at qml :-)
19:48 <balloons> on the lag issue, well sadly that is a difficult problem
19:48 <popey> I'm sure we can find someone, pig me if you need to find help nik90
19:48 <balloons> autopilot can't actually "see" what's on the screen in the traditional sense
19:49 <nik90> popey: sure
19:49 <balloons> it's one of the downsides of testing this way..
19:49 <balloons> the upsides are numerous and mean we don't have to rewrite things for UI changes :-)
19:49 <nik90> balloons: ok. That's alrite
19:50 <popey> ok. anything else ?
19:50 <nik90> not that i can think so.
19:51 <popey> great. lets wrap up..
19:51 <popey> thanks nik90 / balloons
19:51 <popey> #endmeeting