14:29 <popey> #startmeeting Clock meeting
14:29 <meetingology> Meeting started Thu Sep 10 14:29:45 2015 UTC.  The chair is popey. Information about MeetBot at http://wiki.ubuntu.com/meetingology.
14:29 <meetingology> 
14:29 <meetingology> Available commands: action commands idea info link nick
14:29 <popey> Yo yo yo!
14:29 <nik90> hey hey :)
14:30 <nik90> bartosz just told me that he wouldn't be able to make it to the meeting.
14:30 <nik90> so you're stuck with just me :D
14:30 <popey> Heh, okay.
14:30 <popey> Hello Bartosz if you're reading the logs o/
14:31 <nik90> :P
14:31 <nik90> So this week, bartosz has been busy with the 3.6 milestone -> https://launchpad.net/ubuntu-clock-app/+milestone/3.6
14:32 <popey> Super.
14:32 <popey> 3 criticals...
14:32 <nik90> We're fixing some old Timezone issues affecting clock. We have identified them to be caused due to the Javascript Date object. So we're in the process of switching over to QDateTime that should stomp out these bugs for good.
14:32 <nik90> yeah we raised the Timezone issues to Critical since when it happens, clock functionality is broken until you restart the app.
14:33 <popey> Okay.
14:33 <nik90> And in the process, we're moving more and more to c++ classes and methods.
14:34 <nik90> Bartosz also used tinypng.com to reduce the total image assets by around 100 kb..so next clock update should be hopefully 1.0 Mb instead of 1.1 ;)
14:34 <JMulholland> nice :D
14:34 <nik90> Yeah we were quite surprised that clock was 1.1 MB compared to the 400 Kb music app. So we started digging at what is taking up space.
14:35 <nik90> But turns out the c++ plugins require multiple binaries for armhf, amd64 and so on.
14:35 <popey> That's good to hear.
14:35 <popey> Yeah.
14:35 <popey> Sorry about the multi-arch. I am keen to ensure desktop / phone / tablet users get the same apps
14:36 <nik90> yeah that's fine. Otherwise you can't dogfood certain apps on the desktop unity8.
14:37 <nik90> JMulholland: Any update on the clock visual designs?
14:38 <JMulholland> Yes, Rae prepared 3 or 4 new visual styles that she will be reviewing with creative director (this week as far as I know). Once she gets the feedback and a style is selected, we’ll share the visual spec & assets :)
14:38 <popey> Awesome
14:38 <nik90> Woohoo. Cool!
14:39 <nik90> Btw from your testing of the 3rd party Timer app, do you think it is worth implementing something similar in the clock app?
14:39 <nik90> Or do you want to wait on that until we get proper support from the SDK and the platform?
14:40 <nik90> s/testing/usage
14:40 <JMulholland> you might recall in the wireframe sketches I put together it had clock(&alerms), stopwatch and timer. So I’d say yes.
14:40 <JMulholland> could you remind me on what support we’re lacking from SDK/Platform?
14:41 <nik90> Sure, right now (Timer app) is essentially using the Alarms framework to create Timers. So it has some sideeffects like Timers appears as one-time alarms in the datetime indicator.
14:41 <JMulholland> aha, that’s right!
14:41 <nik90> Timers currently running will appear in the alarm's list of the clock app.
14:42 <nik90> That said, the timer functionality is still achieved.
14:43 <JMulholland> I think the indicator issues would be manageable (as one of the 3rd party timers showed, putting the icon in indicators for split second) - not exactly ‘slick’, but managable
14:43 <JMulholland> showing up in the alarms list is a bigger problem
14:43 <JMulholland> so perhaps we should hold off untill those issues are addressed...
14:43 <nik90> Ack.
14:43 <JMulholland> what are your thought’s popey? Better to have something a bit janky now, or hold off untilwe can do a proper job of it?
14:44 <popey> Hmm
14:44 <popey> I'd rather we did a proper job
14:44 <davmor2> proper job
14:44 <JMulholland> thats two votes for proper job, anyone else? :)
14:44 <popey> hah
14:44 <nik90> haha..
14:45 <JMulholland> I’d agree, the timers in alarm-list thing alone is a usability nightmare
14:45 <nik90> ok, so we wait until we get proper support. the SDK team seems busy with convergence and transitioning existing sdk components over to c++.
14:46 <nik90> So I would guess that timer support is atleast one ubuntu cycle away.
14:46 <JMulholland> in the meantime Rae and I will get it designed so you have material to work with when the time comes
14:46 <popey> indeed
14:46 <nik90> ok
14:46 <popey> we could implement the designs but hide the functionality until it's done?
14:46 <popey> (the timer functionality)
14:46 <nik90> yes, that's possible.
14:48 <nik90> cool so approx. next week we should see the new visual specs.
14:48 * nik90 is excited
14:48 <JMulholland> hopefully, I’ll certainly do eveything I can to encourage Rae/Visual Design to that end
14:49 <nik90> thnx
14:49 <nik90> Also balloons fixed the AP issue we were having. However since clock-app code has changed quite a bit since the last time the tests passed, he said he will also get the first test passing.
14:49 <nik90> At which point, me and bartosz can jump in with adding more tests.
14:51 <popey> ok
14:53 <nik90> I think that was all that I had for this week.
14:53 <popey> Any major issues after our store update? Other than those targetted for 3.6?
14:53 <nik90> Nope :D
14:54 <nik90> I see bug 1492584 reported after the update. Will need to investigate at what point it regressed.
14:54 <popey> http://pad.lv/1492584
14:54 * popey lazy
14:55 <popey> ok
14:55 <nik90> It could be the migration to the new list items. I will take a look this week.
14:55 <nik90> Should be a easy fix.
14:56 <popey> okay.
14:56 <popey> Ok, shall we wrap for this week?
14:57 <nik90> sure
14:57 <JMulholland> thanks guys, have a great weekend
14:57 <popey> you too
14:57 <nik90> enjoy your weekend
14:57 <popey> #endmeeting