== Meeting information == * #ubuntu-touch-meeting: calendar meeting, 02 Jul at 13:00 — 13:59 UTC * Full logs at [[http://ubottu.com/meetingology/logs/ubuntu-touch-meeting/2015/ubuntu-touch-meeting.2015-07-02-13.00.log.html]] == Meeting summary == ''LINK:'' https://bugs.launchpad.net/ubuntu-calendar-app/+bug/1470583 looks like a potential easy fix :) ''LINK:'' https://marvelapp.com/122jc5e#6859633 ''LINK:'' http://design.canonical.com/2015/05/to-converge-onto-mobile-tablet-and-desktop-think-grid-units/ ''LINK:'' https://www.dropbox.com/sh/leq9yomp46358qz/AABByOVKVTTsnafW49M9QmMFa?dl=0 ''LINK:'' https://bugs.launchpad.net/ubuntu-calendar-app/+bug/1369543 == Vote results == == Done items == * (none) == People present (lines said) == * popey (65) * JMulholland (47) * kunal (41) * meetingology (3) * faenil (1) == Full Log == 13:00 #startmeeting calendar meeting 13:00 Meeting started Thu Jul 2 13:00:47 2015 UTC. The chair is popey. Information about MeetBot at http://wiki.ubuntu.com/meetingology. 13:00 13:00 Available commands: action commands idea info link nick 13:00 o/ 13:01 Hows it going guys? 13:01 Hi faenil. How are you holding up popey? 13:02 ok :) 13:02 one for you JMulholland https://bugs.launchpad.net/ubuntu-ux/+bug/1469656 13:02 interesting suggestion, to change the icon per day of the month 13:02 hi 13:02 hi kunal 13:02 sounds good, I can’t seem to assign it to myself though 13:03 hi kunal 13:03 (iOS does this, android does not) 13:03 managed to self assign, just had to log in again 13:04 yes, this is standard behavior now days 13:04 I think it’s a nice little touch 13:04 Agreed 13:05 * popey sets medium 13:05 https://bugs.launchpad.net/ubuntu-calendar-app/+bug/1470583 looks like a potential easy fix :) 13:06 (it pings you a reminder about an event 3 multiple by default, which is no good if you say you only want to be reminded when the event starts, as it keeps reminding you afterwards) 13:07 so how we are handling snooze ? 13:07 I thought if we hit snooze it will keep firing two more time 13:07 before expiring 13:07 if we dont snooze it will expire right now 13:09 hmm. 13:09 I'm not sure how to handle this one. 13:10 In my mind I shouldn't get told about something after it's happened - in the calendar 13:10 for the clock - it's different. An alarm can snooze and I can be reminded again and again 13:10 but for calendar events I feel like we should stop pinging the person once the thing starts 13:11 So when saving an event, the repeat should be zero, _if_ the alert is set as "on time" 13:11 if it's any time before that, we should repeat. 13:11 What do you guys think? 13:11 Sounds logical to me 13:11 I think this can be done 13:12 now that we are discussing about reminder, what should be time gap between reminder ? 13:13 what is it by default on other platforms? :) 13:13 same as for our clock alarms? 13:13 i dont remember, do you know ? 13:13 5min seems sane to me 13:13 ok 13:13 so a reminder at 10, 5 and 0 mins 13:13 5 mins sounds right 13:13 let me check what is current 13:14 google defaults to PING! 10 mins, and PING! 0 mins 13:17 anything else? I’ve been making some progress with the convergent calendar UX if we need another topic :) 13:18 ooh! 13:18 Anything to show? 13:19 So I’d been trying to come up with a sensible/good schema for using panels to combine views (as we are doing for other convergent apps) 13:19 And put together a simple click through demo to see how what I’d settled on felt: 13:20 https://marvelapp.com/122jc5e#6859633 13:20 Hint: click anwyehere onscreen and you’ll see blue boxes that show the clickable areas 13:21 short version - large main panel for year/month/week/day view, narrow right panel for agenda/view event/ edit event/ new event views 13:21 I think it’ll feel pretty good and makes more practical use of the space than some of my earlier designs 13:22 i like 13:23 Pretty clean, right? And (hopefully) capitalises on what we’ve already got without introducing loads of new stuff 13:23 Yes, I appreciate the idea of re-using what we have, rather than a rewrite 13:24 so right hand side is _always_ agenda, edit, display event 13:24 until the window gets smaller, in which case we do what? lose the side "stage"? 13:24 that, or we proscribe that the window can’t be reduced beyond a certain size 13:25 otherwise it behaves like a phone, with some snapping 13:25 (as you suggested) 13:26 We have some other behaviours to consider 13:26 what if you're on a high resolution phone so have room for your view, and then you rotate the phone, do you lose the side or the main part 13:26 fire away 13:26 lots to think about there 13:26 if you're editing an event and then rotate your phone, you probably don;t want to lose the edit dialog 13:26 but if you're not editing, maybe you don't care so much 13:27 we’ve been considering that for the convergent browser recently, funnily enough 13:27 maybe if you go to portrait you always switch to whatever was in the right side? 13:27 Anyway, yes, I like it, and look forward to it being more fully fleshed out. thanks JMulholland 13:28 experimenting with the rotation to portrait switching the app to ‘phone’ mode, showing what was in focus (i.e. something you were editing before the switch) 13:28 no worries popey . I’m overhauling the spec with this latest design and will share it with you and kunal ASAP 13:29 ok, thanks. 13:29 alread covered off some other stuff too (e.g. what portrait orientation on phones will look like/ how we could use the space. Medium form factor design for tablets/ non-windowed environments, etc...) 13:30 Nice tool by the way, great for demoing stuff like this. 13:30 another one for you JMulholland https://bugs.launchpad.net/ubuntu-ux/+bug/1470001 13:31 where to put the week number in month view 13:32 Hm, I dont see how we can other than to introduce a new column on the right… 13:33 but then the screen is getting rather crowded 13:33 I’ll have a think 13:33 wb kunal! 13:33 you might have missed this kunal : 13:33 [2:20pm] JMulholland: And put together a simple click through demo to see how what I’d settled on felt: 13:33 [2:20pm] JMulholland: https://marvelapp.com/122jc5e#6859633 13:33 [2:20pm] kunal left the chat room. (Ping timeout: 264 seconds) 13:33 [2:20pm] JMulholland: Hint: click anwyehere onscreen and you’ll see blue boxes that show the clickable areas 13:33 [2:21pm] JMulholland: short version - large main panel for year/month/week/day view, narrow right panel for agenda/view event/ edit event/ new event views 13:33 thanks :) 13:34 yeah, the screen is cramped, i thought we had a bug for this already actually 13:34 aha, we do 13:35 maybe not. 13:36 yes, I was not aware that I got disconnected, some problem with IRC client 13:36 but thanks, I just looking at demo 13:36 no worries, the conversation is logged, you'll see the log url at the end. 13:36 popey, did you received this 13:36 kunal> popey, 13:36 https://code.launchpad.net/~pkunal-parmar/ubuntu-calendar-app/ReadOnlyCal/+merge/261075 13:36 there seems some issue with Jenkins 13:36 or latest EDS patch is not available to Jenkins 13:36 and that's why its failing 13:37 hm 13:37 no, didnt see that 13:37 will take a look 13:38 ok, thanks 13:39 so for this, we will adapt view as per available screen size ? 13:39 or how we need to decide how to layout screen ? 13:40 some primer info here kunal : 13:40 http://design.canonical.com/2015/05/to-converge-onto-mobile-tablet-and-desktop-think-grid-units/ 13:40 (courtesy of my boss) 13:41 the demo one of our prototypers put together may also be informative, you can get it here: 13:41 https://www.dropbox.com/sh/leq9yomp46358qz/AABByOVKVTTsnafW49M9QmMFa?dl=0 13:42 ok, thanks 13:42 will have look 13:42 once we have a crisp set of designs and transitions, we can break this work down 13:42 sure 13:43 Anything else we need to talk about? 13:43 BTW do you have any opinion about 13:43 https://bugs.launchpad.net/ubuntu-calendar-app/+bug/1369543 13:44 * popey looks 13:44 hmm 13:44 * popey adds ubuntu-ux 13:45 * JMulholland assigns to self 13:45 in my opinion the list of calendars should have a radio button next to the enabled ones which is the default 13:45 so you can enable them with one button, and then tick the button next to it (maybe on left?) to set default? 13:46 not sure if we have a pattern like that in the SDK, will need to take a look 13:46 I dont think we have API to change default calendar 13:46 not by Qt 13:46 couple of other things come to mind: 13:46 maybe just remember the last selection made in a new event and keep it as the default until changed again? 13:47 or perhaps place it in the app settings? 13:47 but we need to add some other mechanization to support changing default calendar 13:47 JMulholland, that can be possible 13:47 (That’s once we’ve addressed the issues just highlghted by kunal of course … :P ) 13:47 i like remembering the most recent default 13:47 its least effort in UI 13:48 also, should we show muted calendar in newevent/edit event view ? 13:50 I don't understand the question. 13:50 in calendar management view, we can enable/disable certain calendar 13:51 so we will show event from enabled calendar only 13:51 right 13:51 in edit event, should we show all available calendar 13:51 or just enabled one 13:51 Ooh, good question. 13:51 Should I be able to add to my work calendar even if I never show the calendar. That seems odd 13:52 sorry guys, I’m being turfed out of this meeting room and have to move for the next meeting 13:52 brb 13:53 popey, right 13:55 So in my mind, yes, we should hide them kunal 13:55 ok, 13:57 Anything else? 13:58 nothing else 13:59 Thanks kunal ! 13:59 thanks 13:59 bye 13:59 #endmeeting Generated by MeetBot 0.1.5 (http://wiki.ubuntu.com/meetingology)