20:35:44 <popey> #startmeeting Ubuntu Touch Clock App Meeting
20:35:44 <meetingology> 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 <meetingology> 
20:35:44 <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
20:36:26 <Riussi> what's the agenda?
20:37:06 <popey> one mo
20:37:09 <popey> sorry, flaky internet
20:37:17 <popey> #topic * Review work items and ensure everyone is happy with them and there are no blockers
20:37:26 <popey> so https://blueprints.launchpad.net/ubuntu-clock-app/+spec/initial-clock-development
20:37:51 <popey> those items which have nobody assigned, we need to find people for.. and make sure they're accurate,
20:38:09 <popey> any progress on the alarm / settings views?
20:38:46 <Riussi> 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 <Riussi> i'm going to visit canonical next tue and talk with some of the designers there
20:39:26 <Riussi> but settings has a local storage ready, people can add their settings to store into it
20:39:35 <Riussi> currently it stores the last tab index between app launces
20:39:38 <Riussi> no ui yet
20:39:46 <Riussi> because no idea what's coming there
20:39:53 <popey> the design guys are working on clock at the moment
20:40:09 <popey> i spoke with them earlier about it, they should have something published next week
20:40:14 <Riussi> 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 <Riussi> ok great
20:40:25 <Riussi> so that's what we are waiting for
20:40:37 <popey> that should move things along a bit
20:40:41 <Riussi> yes
20:41:38 <popey> are there any timezone related things we need to consider?
20:41:48 <Riussi> well, we'll get there
20:41:51 <popey> or are we just representing whatever time / timezone the system gives us?
20:42:01 <Riussi> but there are some issues related to how we can achieve everything in qml/js
20:42:35 <popey> how so?
20:42:36 <Riussi> 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 <Riussi> and you can't read files from local filesystem in qml
20:43:08 <popey> so we need cron? ;)
20:43:09 <Riussi> 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 <Riussi> eys
20:43:13 <Riussi> yes
20:43:42 <Riussi> we've done all this stuff a few years back when writing apps for symbian/meego with qt/qml
20:44:00 <popey> hmm, i wonder how the calculator guys do it
20:44:07 <Riussi> we'll check it out
20:44:11 <popey> i think they grab the unix time
20:44:19 <popey> Fri Mar 15 20:44:19 GMT 2013
20:44:22 <Riussi> a tried to make the local storage as similar as possible to theirs
20:44:23 <popey> so you get something like that
20:44:49 <Riussi> but we need to address the handling of c++ plugins to core apps at some point
20:44:51 <popey> they get the time and print it on the receipt roll that scrolls up the screen
20:45:00 <Riussi> i'm not so sure we can achieve all of them without c++
20:45:10 <popey> if we have to, we have to
20:45:13 <Riussi> but yes, we'll check the calculator as well
20:45:19 <popey> of course we'd rather not, but if we have to than so be it
20:45:23 <Riussi> yes
20:46:22 <Riussi> 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 <Riussi> well all of the platform integration to be frank
20:46:36 <popey> no, there's no clock up there
20:46:41 <Riussi> i know qml/qt but not ubuntu
20:47:01 <popey> there is a clock on the welcome (i.e. lock) screen
20:47:10 <Riussi> who's doing that?
20:47:26 <popey> who as in which developers?
20:47:29 <Riussi> yes
20:47:42 <popey> that would have been canonical internal, not sure who, can find out
20:48:02 <popey> we have had instances in demos where you can see two clocks on screen and one is wrong
20:48:12 <Riussi> ok
20:48:13 <popey> well, they're not in sync with eachother
20:48:21 <popey> which highlights the issue you're raising I think?
20:48:30 <Riussi> but anyway. we will be coming to these issues soon. most important one now is the design
20:48:35 <popey> agreed
20:48:42 <Riussi> so if they are working on it now, we'll get it in a few weeks?
20:48:50 <popey> no, should be next week
20:48:55 <Riussi> ok, great
20:48:56 <popey> then they're moving on to weather I think
20:49:00 <popey> but I'll check
20:49:06 <Riussi> i see us moving fast when we get the design
20:49:07 <popey> #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 <Riussi> at least the ui
20:49:13 <popey> excellent
20:49:30 <popey> anything else ?
20:49:43 <Riussi> heh, listening to the sdk days youtube and they said excellent at exactly the same time as you ;)
20:49:45 <Riussi> nothing else for me
20:50:43 <popey> 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 <Riussi> yep, i won't be, i'll be in some local pub here in paddington
20:51:23 <popey> cool, have a good weekend
20:51:26 <popey> #endmeeting