19:30:26 #startmeeting Ubuntu Touch Clock / Alarm / Stopwatch app meeting 19:30:26 Meeting started Fri Apr 12 19:30:26 2013 UTC. The chair is popey. Information about MeetBot at http://wiki.ubuntu.com/meetingology. 19:30:26 19:30:26 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:30:29 Some handy links.. 19:30:44 blueprint: https://blueprints.launchpad.net/ubuntu-phone-commons/+spec/initial-clock-development 19:30:56 reviews: https://code.launchpad.net/~ubuntu-clock-dev/ubuntu-clock-app/trunk/+activereviews 19:30:58 hi 19:31:06 bugs: https://bugs.launchpad.net/ubuntu-clock-app/+bugs 19:31:08 hi nik90 19:31:29 who's here for the clock meeting? 19:31:32 * popey tickles mhall119 19:31:56 not heard from frals and Riussi_ since last week 19:32:25 I'm here 19:33:11 renato wrote some initial autopilot tests which you can find in the MR currently being reviewed 19:33:29 however I couldnt get it to work on my *new* 13.04 19:33:50 where did you get autopilot from? 19:33:53 we tried some debugging together..perhaps you could try it out in your system and let us know what is wrong 19:34:01 I got it from the official autopilot ppa. 19:34:22 me and renato have the same packages (libautopilot-qt and autopilot-phablet) installed 19:34:36 for some reason the test fails on my machine alone 19:34:48 what are the steps to reproduce? 19:35:30 popey: the MR at https://code.launchpad.net/~renatofilho/ubuntu-clock-app/autopilot/+merge/157982 describes the commands which you need to run 19:35:48 essentially you need to run autopilot run clock_app inside the tests/autopilot folder 19:36:20 ok, I'll have a go 19:36:26 but not right this moment 19:36:40 #action popey try out autopilot tests as per https://code.launchpad.net/~renatofilho/ubuntu-clock-app/autopilot/+merge/157982 19:36:40 * meetingology popey try out autopilot tests as per https://code.launchpad.net/~renatofilho/ubuntu-clock-app/autopilot/+merge/157982 19:36:48 mhall119: were you able to find any info about the Base Clock , Timer API from last week's meeting? 19:37:01 no, sorry 19:37:15 I think we should just remove that work item 19:37:28 ok 19:37:40 we can always add them later if needed 19:37:48 yeah 19:37:57 I'm pretty sure it was Kevin just thinking of what was probably needed 19:38:09 +1 19:38:12 yeah I guess so 19:38:51 this month todo is basically the core of Alarm and Clock. However we might have some blockers with them 19:39:06 are there any items on hte milestone which we need to bump, or something you're blocking on? 19:39:32 for clock, to get the timezone info we need to read files from the ubuntu system.. So Riussi_ was in the process of writing a C++ plugin for that 19:39:53 however he wasnt sure of how to modify the debian folder for that 19:40:32 * nik90 having a look at blueprints 19:40:37 nik90: have you talked to anybody on the SDK team? 19:40:44 this seems like something the platform should be providing 19:41:12 mhall119: no I havent talked to anyone yet about that..whom should I contact regarding this? 19:41:23 can we not use QTimeZone / QTimeZoneOffset / QTimeZoneTransition ? 19:42:06 nik90: bzoltan to start with 19:42:15 or use one of those ^^ 19:42:25 popey: I think we can use it..however we need to know which timezone a specific city is in ... 19:42:33 to be honest I need to take a look at them 19:43:29 http://www.developer.nokia.com/Community/Wiki/How_to_get_list_of_Time_Zones_in_Qt_Maemo_application is interesting 19:43:53 an, not qt native. nvm 19:44:18 #action nik90 contact bzoltan regarding timezone API 19:44:18 * meetingology nik90 contact bzoltan regarding timezone API 19:44:26 wise 19:44:42 #action nik90 Investigate the use of QTimeZone, QTimeZoneoffset for timezone implementation 19:44:42 * meetingology nik90 Investigate the use of QTimeZone, QTimeZoneoffset for timezone implementation 19:44:51 * popey remembers he left the stopwatch running on his desktop about 3 hours ago 19:45:06 popey: I'll have a look at them this weekend 19:45:08 lol 19:45:15 popey: lol 19:45:18 I'm going to leave it running overnight 19:45:31 ← example of people who do odd things 19:45:36 nik90: I've noticed that on my N7, the clock's second hand will every so often skip 2 seconds at a time 19:45:54 mhall119: hmm.. 19:46:03 I think it's because the interval is 100ms, but in reality it's probably 1001ms or so 19:46:14 related to that I've noticed the timer at the top changes before the hand moves 19:46:16 actually I have noticed that happen on my S3 running Android as well..I think it is something to do with the animation 19:46:17 maybe setting it to 500ms will fix it 19:46:38 the digital time should change _after_ the hand arrives at the right digit, not as it leaves the previous digit 19:47:20 popey: I think I might know the cause of that..I will have a look 19:47:32 otherwise it looks fantastic 19:48:13 oh yeah, lets not be too negative ☻ 19:48:48 #action nik90 Experiment with different Clock Time (related to second hand skipping etc) and Timer 19:48:48 * meetingology nik90 Experiment with different Clock Time (related to second hand skipping etc) and Timer 19:49:00 Today's visual design made me so happy 19:49:12 which actually raises one question 19:49:34 I am assuming some of them will be done using images...how do images scale across devices? 19:49:55 excellent question 19:49:56 no idea 19:49:57 Right now, everything you see visually are qml elements which handle different screen resolution properly 19:50:23 I remember us having problem when using images at the beginning 19:50:33 popey: Any idea who I should ask this to? 19:50:55 kaleo or zoltan 19:51:08 i will bring it up in our meeting with them on monday 19:51:23 #action popey discuss image scaling during monday meeting 19:51:23 * meetingology popey discuss image scaling during monday meeting 19:51:26 alrite 19:52:54 mhall119: I was reading your discussion about using HUD..I am guessing we will using this for the clock as welll 19:53:10 mhall119: will you be updating your blog posts with how to use HUD? 19:54:12 nik90: once it's figured out I will, yes 19:54:31 ok 19:54:54 #action nik90 remove Base API, TImer API from blueprints 19:54:54 * meetingology nik90 remove Base API, TImer API from blueprints 19:55:48 I think I have run out of question :P 19:55:50 * popey isnt going to ask what the easter egg is 19:56:07 popey: wait u dont know? :D 19:56:25 its probably best i don't ☻ 19:56:33 hehe 19:56:50 we already have one..but I wont say 19:56:54 ok, anything else before we wrap? 19:57:03 nothing that I can think of 19:57:12 awesome, thanks nik90 19:57:17 #endmeeting