13:01 <popey> #startmeeting Calendar meeting
13:01 <meetingology> Meeting started Thu Aug 28 13:01:45 2014 UTC.  The chair is popey. Information about MeetBot at http://wiki.ubuntu.com/meetingology.
13:01 <meetingology> 
13:01 <meetingology> Available commands: action commands idea info link nick
13:03 <popey> Looking at http://people.canonical.com/~dpm/core-apps-sponsoring/ we have a few merges in flight
13:03 <popey> one from a new contributor, twstd-dev
13:04 <popey> https://code.launchpad.net/~pkunal-parmar/ubuntu-calendar-app/YearView-curmonth-scroll/+merge/230781 seems to have failed jenkins...
13:04 <mihir> kunal: hi doing great too
13:04 <mihir> hey popey
13:05 <popey> heya!
13:05 <mihir> popey: this one is I have tested, https://code.launchpad.net/~twstd-dev/ubuntu-calendar-app/1359323/+merge/232140
13:05 <mihir> popey: regarding this , i will test on device, https://code.launchpad.net/~twstd-dev/ubuntu-calendar-app/1357312/+merge/232132
13:05 <popey> looks like the test can't find the months because we autoscroll down?
13:06 <kunal> popey, yes, it looks like so
13:07 <mihir> kunal: did you merge after balloons and I fixed the AP /
13:07 <popey> should we add twistd-dev to the calendar team? that way their merges will get to trigger jenkins jobs
13:09 <kunal> I am not sure, I can merge
13:11 <popey> well, we need jenkins to test first
13:11 <popey> i have asked for it to be triggered
13:11 <mihir> kunal: hmm , may be because I commented that, after that i don't see any merge
13:12 <kunal> I am merging now, lets see
13:15 <kunal> ok ,merged
13:15 <kunal> popey, any date for RTM ?
13:15 <popey> No.
13:16 <popey> So for calendar I'd say we need to just keep on top of bugs, and polish.
13:16 <popey> I wouldn't be landing anything new right now, just fixes.
13:16 <popey> I'll keep pushing to the store frequently.
13:17 <mihir> popey: nik90 and I are working for changing UI for new event
13:17 <mihir> popey: kunal this is how it looks now http://imgur.com/QCunV7M
13:17 <popey> Yeah, that's a very welcome change...
13:17 <mihir> popey: so shall we consider this for RTM ?
13:18 <popey> If you think we can get it landed within the next few days yes.
13:18 <kunal> That slider, are we showing actual value some where ?
13:18 <popey> you get a popup when you slide, but nothing shows when not sliding?
13:18 <nik90> popey: nope
13:19 <mihir> kunal: yup , shall we keep one label ?
13:19 <nik90> popey: I mean the slider popup doesn't appear when not sliding it
13:19 <nik90> kunal: it should be visible when the user views the event, just not when editing or creating an event
13:20 <kunal> I would  expect it actual value somewhere, without sliding
13:20 <popey> agreed
13:20 <mihir> i'll put a label showing it's value at right corner
13:20 <mihir> is that fine?
13:21 <kunal> May be we can add lable below "recurrences" saysing something "After XXX occurence(S)"  or something better
13:21 <kunal> and that changes when slider value changes
13:22 <popey> occurrences feels clumsy to me.
13:22 <popey> but that's what google call it, so that must just be me ☻
13:22 <nik90> kunal: like a ListItem.Subtitled ?
13:22 <popey> any reason it's not just a field you type in?
13:22 <kunal> nik90, that sounds great
13:22 <popey> rather than a slider?
13:23 <nik90> and then below that the slider
13:23 <nik90> popey: because it felt strange to type it in
13:23 <mihir> popey: google says TIMES in dispaly ehhehe
13:23 <popey> it says occurrences here
13:23 <nik90> popey: common usage is that it is after a few occurrences
13:24 <nik90> popey: if the user cant tell how many occurrences, then he should use the "stop after certain date" option
13:24 <popey> https://i.imgur.com/JVXrcMX.png
13:24 <popey> they use both in that dialog
13:24 <mihir> popey: i read the summary :|
13:25 <nik90> popey: true, but on the phone they don't do that because it is cumbersome
13:25 <popey> right
13:25 <nik90> popey: actually on phone they also use a textfield, strange :/
13:25 <nik90> I suppose we could use them
13:26 <nik90> I previously told mihir to change to a slider :P
13:26 <popey> well, on mobile sliders are easier to manipulate of course
13:26 <mihir> nik90: heheheh ..
13:26 <mihir> i thought to push other MR but did in this only.
13:26 <mihir> should revert back ?
13:27 <nik90> mihir: just realised that the branch you are hacking on is a common calendar app branch, so I can code right in it as well to make this faster :D
13:28 <kunal> mihir, I left some comment there, to avoid that save issue/problem you described yesterday, did that helped ?
13:28 <nik90> popey: should we revert to a textfield
13:28 <mihir> nik90: yup i did it in calendar-dev
13:28 <mihir> nik90: i was little busy in office these days, just finished this task today
13:28 <mihir> kunal: yup i did consider that
13:29 <mihir> kunal: i create fresh RULE object each time.
13:29 <kunal> ok,
13:29 <nik90> mihir: I just noticed some small anchor issues, I will fix that and continue testing. You should be able to see my commit history to see exactly what changed
13:30 <mihir> nik90: (y) thanks
13:30 <mihir> kunal: could you again review and provide some review comments on new push
13:30 <mihir> i am still testing this , but if you're able to find code review.
13:30 <nik90> kunal: btw, I noticed that the new event page takes a few seconds to open both in trunk and in our revamp page
13:30 <nik90> kunal: anything we can do to improve that?
13:30 <mihir> also, I observed this too
13:30 <kunal> I can try to profile it, but in general lot of code makes QML slower
13:31 <kunal> moving stuff to seperate component will help
13:31 <mihir> kunal: nik90 i'll saperate Remember code as well
13:31 <mihir> so we'll have very required stuffs at New Event Page
13:31 <nik90> kunal: mihir and my branch helps this a bit since we have moved them to separate files.
13:31 <nik90> kunal: let's see where else we can improve this
13:32 <kunal> yes, I left one comment some time before, I think we should only keep Time, Title, place on main page
13:32 <mihir> nik90: i would suggest to change some order in Main event,
13:32 <mihir> nik90: can we put date on TOP, it looks lil messay in between
13:32 <kunal> other to separate page
13:32 <popey> sorry, had a power cut again.
13:32 <popey> nik90: guess we need to try it and see..
13:33 <nik90> mihir: sure
13:33 <nik90> popey: ok we will revert back to textfield
13:33 <mihir> So it will Date,Title , Desc,Loc & Guest rest in saperate pages
13:34 <nik90> mihir: yes, but not in your branch.
13:34 <nik90> mihir: let's try to merge your branch asap after the revert to textfield and some anchors changes
13:34 <nik90> mihir: so take care of the revert
13:34 <mihir> nik90: i'll do that now
13:35 <nik90> mihir: I will take care of the anchor stuff
13:35 <kunal> mihir, may be description as well, unless we have better idea for placing description somewhere
13:35 <nik90> mihir: awesome
13:39 <popey> Ok. So would be good to get a build of the calendar in before the weekend with as much of this in as possible.
13:39 <popey> now we have 6 merges in flight. Would be great to get those finished off so we don't have too many to juggle.
13:40 <popey> reckon that's achieveable?
13:41 <mihir> popey: yup we can try to do that by this week
13:41 <nik90> +1
13:41 <popey> thanks guys.
13:41 <mihir> popey:
13:41 <mihir> nik90: was suggesting we should remove mom-wed-fri and tue-thu from options
13:42 <nik90> popey: yeah above that ^^
13:42 <nik90> popey: it seems really really random that we show "Every Mon, Wed, Fri" and "Every Tue, Thu"
13:42 <kunal> mihir, I think we should keep it, as we merged it in response to some bug
13:42 <kunal> nik90, actually we copied it from google cal
13:42 <nik90> IMO it just clutters up the option selectors
13:42 <popey> it's to match google
13:42 <nik90> kunal: I knw
13:42 <nik90> but why
13:43 <mihir> kunal: i was thinking that we should use Narrow format instead of full day name
13:43 <nik90> do we have a proper reasoning other than the fact that google does it
13:43 <popey> because google is the only calendar we sync with (currently)
13:43 <kunal> I think jono requested it, not sure why
13:43 <mihir> kunal: i see it is not visible on device
13:43 <nik90> btw google does not do in the phone
13:43 <popey> interesting, i thought it did..
13:43 <nik90> popey: true, but even if we sync from google, in our UI, we can show it with the weekdays option
13:45 <kunal> my Blackberry says, every day, every weekday, every friday
13:45 <kunal> every month and year
13:46 <popey> we could hide the m-t-w and tu-th options if it looks to cluttered?
13:47 <nik90> We could try
13:47 <nik90> mihir: again not in your branch :D
13:47 <mihir> nik90:  :D yup i won't change in my branch
13:49 <popey> Ok, anything else to discuss?
13:50 <mihir> popey: nope , nothing from my side
13:50 <kunal> yes, now that we are modifying the newevent
13:51 <kunal> I was thinking to change DatePicker to show both date and time,
13:51 <kunal> so we can get rid of those 4 text fields
13:51 <kunal> and use only two
13:51 <popey> do we have an sdk component for that?
13:52 <kunal> I don't thin so
13:52 <nik90> kunal: can the datepicker show both date and time at the same time?
13:52 <kunal> looking from code, no
13:53 <kunal> so I was planning to create custom one
13:53 <nik90> hmm that would require custom AP helpers which could be flaky
13:53 <nik90> Not sure I would recommend more custom components
13:54 <popey> +1
13:54 <nik90> if anything we should strive for more sdk components than go the custom route
13:54 <kunal> well, SDK component is not good enough atleast for calendar case
13:55 <nik90> tbh the current situtation seems fine with the separate date and time widgets
13:55 <kunal> inputing 4 field to set two dates is not good
13:55 <nik90> google calendar does that as well
13:55 <nik90> on the phone
13:55 <kunal> that was hack, because it was not supported
13:55 <kunal> is it, BB does not do that
13:55 <kunal> will check iOS
13:57 <popey> ok
13:58 <popey> Anything else?
13:58 <kunal> no
13:59 <nik90> nope
13:59 <popey> Magic. Thanks chaps! Lets get these final bits landed!
14:01 <popey> #endmeeting