14:31 <popey> #startmeeting Clock meeting
14:31 <meetingology> Meeting started Thu Jul 30 14:31:58 2015 UTC.  The chair is popey. Information about MeetBot at http://wiki.ubuntu.com/meetingology.
14:31 <meetingology> 
14:31 <meetingology> Available commands: action commands idea info link nick
14:32 <popey> How you going guys?
14:33 <JMulholland> I’ve been doing some work on clock, re: the matter we discussed before I was out last week. Namely, where do we put other
14:33 <JMulholland> *where do we put other clock modes
14:37 <JMulholland> I think there’s a good case for putting them on horizontal swipes, as illustrated here:
14:37 <JMulholland> http://i.imgur.com/KYA4PcV.png
14:37 <gang66> Nice
14:38 <gang66> I was thinking about the same (swiping)
14:38 <JMulholland> That still leaves the matter of how we communicate that to the users, so I’ve been experimenting with some different approacjes for that:
14:38 <JMulholland> My personal fav, using an tab-icon set: http://imgur.com/GDJg3Jc
14:38 <popey> wow, like that
14:39 <popey> like both actually, these are great
14:39 <JMulholland> alternitavely we can consider using pagination indicators (similar to what was used in the dash):
14:39 <JMulholland> version 1: http://imgur.com/0AeYkZA
14:39 <JMulholland> version 2: http://imgur.com/KlC7cnZ
14:40 <JMulholland> or alternitavely we might consider introducing more commonly used SDK navigation components via a header:
14:40 <gang66> My favourite is http://imgur.com/GDJg3Jc
14:40 <JMulholland> http://imgur.com/y0g9N7n (not too keen on this, the tab-header eats up a lot of space)
14:41 <JMulholland> or http://imgur.com/1lG1dVr
14:41 <JMulholland> cool, glad you like it gang66 :)
14:41 <JMulholland> the icons are placeholders I just sketched quickly so we’d have something
14:41 <JMulholland> but yea, I think it preserves the ‘minimal’ feel
14:41 <popey> icons > text
14:42 <popey> (fewer translations, fewer issues with text fitting on the screen)
14:42 <JMulholland> absolutely
14:42 <popey> and its what android does
14:42 <gang66> In my opinion we should leave bottom edge for alarms
14:42 <gang66> And don't put anything into it
14:43 <popey> I'm inclined to agree.
14:43 <gang66> I would like to write lap's time in the list as we already do it for Cities
14:43 <gang66> (for Stopwatch)
14:44 <JMulholland> makes sense, no strong desire to log lap times (i.e. save them for later reference) or save timers (for subsequent use)?
14:44 <JMulholland> those where the only possible uses of the bottom edge that came to mind when sketching this http://i.imgur.com/KYA4PcV.png
14:45 <gang66> Maybe I will prepare some implementation proposal, so we could test it
14:46 <JMulholland> ok, maybe we revisit that later once we have a stopwatch & timer in place
14:46 <JMulholland> ‘nice to have’ rather than urgent :)
14:46 <gang66> for now we could implement only stopwatch (according to nik90)
14:47 <JMulholland> cool
14:47 <popey> Yeah, timers is problematic
14:47 <JMulholland> I had a thought on that...
14:47 <JMulholland> (stopwatch that is)
14:47 <gang66> because we don't have notification for timer
14:47 <popey> adding one screen (stopwatch) would be good
14:47 <JMulholland> what do you guys think of having the stopwatch be digital only?
14:48 <gang66> Should we create blue print?
14:48 <JMulholland> the current analogue face would be very hard to read seconds on, so we either need to be digital only or adapt our minimal analogue clockface to show more info...
14:48 <JMulholland> (whats the timer problem out of curiosity btw :)?)
14:48 <gang66> For me it is ok, we could also consider to have both at the same time
14:49 <gang66> Inside there will be digital
14:49 <gang66> and around analog...
14:49 <JMulholland> hm, true, that’s a third option.
14:50 <gang66> (whats the timer problem out of curiosity btw :)?):  Because we don't have possibility to implement notification for timer, when you disable clock
14:50 <gang66> Use case:
14:50 <JMulholland> aha
14:50 <gang66> 1. enable timer
14:50 <gang66> 2. close clock
14:51 <gang66> Expected: alarm is ringing
14:51 <gang66> We could always implement timer without notifications
14:52 <JMulholland> understood
14:52 <gang66> Popey: What do you think about implement timer without notifications ?
14:54 <gang66> One more think: Volume preview
14:54 <gang66> https://bugs.launchpad.net/ubuntu-clock-app/+bug/1362078
14:54 <gang66> James: to have common UX across all application, could you please approve also volume preview for "System settings"?
14:55 <gang66> https://bugs.launchpad.net/ubuntu-ux/+bug/1479374
14:55 <popey> We need to speak to platform people to fix the issue with timers
14:55 <popey> and drive them to support them
14:55 <JMulholland> I’ll have a word with the UX who takes care of settings gang66
14:55 <JMulholland> see if we can get this aligned, i think your suggestion is a good one
14:55 <popey> because to be honest, if we dont push it, it will never happen
14:55 <popey> we should keep timers out of trunk until we support it on the phone
14:56 <popey> and perhaps just have stopwatch for now, and do timers once we have a plan for timers on device
14:57 <JMulholland> I need to get moving folks, ping or email me if there’s anything else I can help with!
14:57 <popey> ok
14:58 <rpadovani> seems we don't have a designer for calc meeting neither this week :/
14:58 <gang66> :-)
14:58 <popey> yeah.
14:59 <popey> so store currently has clock r305
14:59 <popey> is r315 ready for us to submit to the store?
15:00 <gang66> yes it is
15:01 <gang66> we could push it to the store
15:02 <gang66> Popey: Could you please create blueprint to sync UX design documentation with Calculator implementation
15:02 <gang66> ?
15:03 <popey> hang on, shall we finish clock first :(
15:05 <popey> I meant ":)" :)
15:06 <popey> Ok, I'll get an update to the store for clock, I guess we have no other clock things to discuss /
15:06 <popey> ?
15:08 <popey> #endmeeting