#title #ubuntu-touch-meeting: Ubuntu Touch Clock App Meeting Meeting started by popey at 20:35:44 UTC. The full logs are available at http://ubottu.com/meetingology/logs/ubuntu-touch-meeting/2013/ubuntu-touch-meeting.2013-03-15-20.35.log.html . == Meeting summary == ** Review work items and ensure everyone is happy with them and there are no blockers ''ACTION:'' popey check with design on ETA of clock designs (popey, 20:49:07) Meeting ended at 20:51:26 UTC. == Votes == == Action items == * popey check with design on ETA of clock designs == Action items, by person == * popey ** popey check with design on ETA of clock designs == People present (lines said) == * Riussi (39) * popey (38) * meetingology (4) == Full Log == 20:35:44 #startmeeting Ubuntu Touch Clock App Meeting 20:35:44 Meeting started Fri Mar 15 20:35:44 2013 UTC. The chair is popey. Information about MeetBot at http://wiki.ubuntu.com/meetingology. 20:35:44 20:35:44 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 20:36:26 what's the agenda? 20:37:06 one mo 20:37:09 sorry, flaky internet 20:37:17 #topic * Review work items and ensure everyone is happy with them and there are no blockers 20:37:26 so https://blueprints.launchpad.net/ubuntu-clock-app/+spec/initial-clock-development 20:37:51 those items which have nobody assigned, we need to find people for.. and make sure they're accurate, 20:38:09 any progress on the alarm / settings views? 20:38:46 we had a design hangout last week (missed the one today) and they promised more designs for us, but i haven't heard anything 20:39:02 i'm going to visit canonical next tue and talk with some of the designers there 20:39:26 but settings has a local storage ready, people can add their settings to store into it 20:39:35 currently it stores the last tab index between app launces 20:39:38 no ui yet 20:39:46 because no idea what's coming there 20:39:53 the design guys are working on clock at the moment 20:40:09 i spoke with them earlier about it, they should have something published next week 20:40:14 alarm page is pending a bit on nick's branch since he's componentizing his analogclockface so i can use it for analogtimechooser 20:40:20 ok great 20:40:25 so that's what we are waiting for 20:40:37 that should move things along a bit 20:40:41 yes 20:41:38 are there any timezone related things we need to consider? 20:41:48 well, we'll get there 20:41:51 or are we just representing whatever time / timezone the system gives us? 20:42:01 but there are some issues related to how we can achieve everything in qml/js 20:42:35 how so? 20:42:36 we can't do alarms in qml only, we need something outside the app to keep track of them and invoke us when we need to show the alarm. the clock app might not be running all the time 20:42:47 and you can't read files from local filesystem in qml 20:43:08 so we need cron? ;) 20:43:09 e.g. if we want to read /etc/timezone and show the value from there, you have to have a bit of c++ 20:43:12 eys 20:43:13 yes 20:43:42 we've done all this stuff a few years back when writing apps for symbian/meego with qt/qml 20:44:00 hmm, i wonder how the calculator guys do it 20:44:07 we'll check it out 20:44:11 i think they grab the unix time 20:44:19 Fri Mar 15 20:44:19 GMT 2013 20:44:22 a tried to make the local storage as similar as possible to theirs 20:44:23 so you get something like that 20:44:49 but we need to address the handling of c++ plugins to core apps at some point 20:44:51 they get the time and print it on the receipt roll that scrolls up the screen 20:45:00 i'm not so sure we can achieve all of them without c++ 20:45:10 if we have to, we have to 20:45:13 but yes, we'll check the calculator as well 20:45:19 of course we'd rather not, but if we have to than so be it 20:45:23 yes 20:46:22 i'm a bit unclear on the platform on the clock front, is there a clock shown somewhere in the top somewhere, and if there is, what runs it, where does it get the time 20:46:33 well all of the platform integration to be frank 20:46:36 no, there's no clock up there 20:46:41 i know qml/qt but not ubuntu 20:47:01 there is a clock on the welcome (i.e. lock) screen 20:47:10 who's doing that? 20:47:26 who as in which developers? 20:47:29 yes 20:47:42 that would have been canonical internal, not sure who, can find out 20:48:02 we have had instances in demos where you can see two clocks on screen and one is wrong 20:48:12 ok 20:48:13 well, they're not in sync with eachother 20:48:21 which highlights the issue you're raising I think? 20:48:30 but anyway. we will be coming to these issues soon. most important one now is the design 20:48:35 agreed 20:48:42 so if they are working on it now, we'll get it in a few weeks? 20:48:50 no, should be next week 20:48:55 ok, great 20:48:56 then they're moving on to weather I think 20:49:00 but I'll check 20:49:06 i see us moving fast when we get the design 20:49:07 #action popey check with design on ETA of clock designs 20:49:07 * meetingology popey check with design on ETA of clock designs 20:49:08 at least the ui 20:49:13 excellent 20:49:30 anything else ? 20:49:43 heh, listening to the sdk days youtube and they said excellent at exactly the same time as you ;) 20:49:45 nothing else for me 20:50:43 ok, great. I'll mail the list with what I find out, but that wont be till next week, designers are probably all out in trendy london wine bars :D 20:51:02 yep, i won't be, i'll be in some local pub here in paddington 20:51:23 cool, have a good weekend 20:51:26 #endmeeting Generated by MeetBot 0.1.5 (http://wiki.ubuntu.com/meetingology)