13:01 #startmeeting Calendar Meeting 13:01 Meeting started Thu Sep 18 13:01:01 2014 UTC. The chair is popey. Information about MeetBot at http://wiki.ubuntu.com/meetingology. 13:01 13:01 Available commands: action commands idea info link nick 13:01 hello popey nik90 :) 13:01 hello 13:01 is kunal joining as well? 13:01 Hi guys, hows it going? 13:01 If he's around. 13:02 popey: going good and busy :D 13:02 going grrt 13:02 hi kunal 13:02 hey kunal :) 13:02 hey kunal ! 13:03 HI all 13:03 wow nice to be in a meeting with many people ;) 13:04 Shall we take a look at http://people.canonical.com/~dpm/core-apps-sponsoring/ to start? 13:04 Sure 13:04 we are down to only 5 merges, but a couple are over 2 weeks old. 13:05 out of that , one is for Translator 13:06 it is left with merge in trunk, nik90 i guess we can push another branch with change 13:06 lets start at the top.. 13:06 https://code.launchpad.net/~pkunal-parmar/ubuntu-calendar-app/YearView-curmonth-scroll/+merge/230781 13:06 * popey pokes balloons with the above 13:07 * davmor2 so want that to read, pokes balloons with pin and watches them explode 13:08 davmor2: hahaha 13:08 kunal: do you know what needs to be done with the MP ^^ ? 13:08 looks like some AP changes, right balloons ? 13:09 yes, I suggested some workaround , balloons thinks test needs to be modified, 13:10 ok 13:12 how about the next one? https://code.launchpad.net/~ubuntu-calendar-dev/ubuntu-calendar-app/add-tests-for-future-and-past-events/+merge/232150 13:12 popey: it is incomplete 13:13 ahh yes, the yearview. I need to push the branch changes I have. I think given kunal's changes, we should add another test to check the default view and make sure the current month is in view on load 13:13 popey: i made comment , last..no changes have been made afterwards 13:13 ok. 13:13 mihir, popey: I think it should be marked as wip since it is 13:13 * mihir puts branch in WIP 13:14 is it still blocked? 13:14 yes, -> WIP +1 13:14 oh, its the 2038 issue. fun. 13:14 popey: nope i believe as I understood bug correctly, as balloons mentioned regarding large timestamp 13:14 lets put that off until 2036 to be safe 13:14 if you won't to use datepicker, yes. 13:14 balloons: what if we use date picker and choose 2017 , will this cause an issue? 13:15 mihir, you would need to set a limit inside the qml to avoid the error 13:15 https://code.launchpad.net/~uriboni/ubuntu-calendar-app/fix-translations-with-arg/+merge/232903 needs trunk merge? 13:16 popey: yes 13:16 not seen Ugo about... 13:16 * popey pokes bfiller 13:16 poked 13:17 how about https://code.launchpad.net/~ubuntu-calendar-dev/ubuntu-calendar-app/filesRestructure/+merge/234365 ? 13:17 is that WIP? 13:17 doesn't look complete 13:18 popey: It requires CMake updates, we'll work on this now, we can put in WIP. nik90 is that correct? 13:18 popey: it is a WIP 13:18 it requires CMAKE updates, however me and mihir have been occupied with the view redesigns 13:19 it will take some time before it can be merged 13:19 ok 13:23 i'll put that in WIP 13:23 thanks 13:23 Then there's the ongoing UI updates. 13:23 done 13:24 I really appreciate you guys all making effort to make the app more usable and better looking. 13:24 yw 13:24 popey: :) 13:25 kunal: can you review the new design and code ? 13:25 kunal: https://code.launchpad.net/~ubuntu-calendar-dev/ubuntu-calendar-app/ViewRedisign/+merge/234680 13:25 mihir, on the datepicker issue, it might be worth setting the limit to work around the problem, but you won't be able to set an event date later than 2036 13:26 balloons: that is for AP right ? so how about we make AP and choose dates lesser than 2036 until we get fix ? 13:26 sure will have alook 13:26 kunal: thanks :) 13:26 mihir, the limit must be set in the qml 13:27 but I have to talk to the AP guys , the merge has been setting there but they are concerned about it breaking things like calendar 13:27 balloons: okay 13:27 sadly https://bugs.launchpad.net/ubuntu-calendar-app/+bug/1291225 makes it hard to tell 13:28 so they aren't sure they want to merge it, and I'm not sure of the status of what they will do. 13:28 kunal: that branch is under cal-dev , so you can push directly to that branch 13:28 ok 13:33 balloons: okay , we can try limit as of now ,but it may create problem while syncing if there are any events beyond it :| not sure weather it is valid usecase or not 13:33 kunal: quick question, when you import a calendar from google, do you set the calendar color to what was set in google? Or you convert it to one of the 8 colors you defined in the calendar app? 13:34 does google expose those colours? 13:34 erm not sure 13:34 kunal: ^^ 13:34 actually we dont do anything 13:34 we set color to collection 13:35 and EDS when sync events from google 13:35 associate those events with certain collection 13:35 and then we use that collection;s color with event 13:35 so the colors are from google? 13:35 no 13:36 our own color 13:36 i see nothing in the ical or xml output from google to show the colour a calendar uses. 13:36 unless it's encoded in some special way 13:37 ah ok 13:37 yes, I think its not something comes from google or ical 13:37 that makes what I am about to do a bit easier :) 13:37 it depends on users's choice 13:38 kunal: also we only sync google's primary calendar? 13:38 yes 13:38 kunal: is it possible to get other calendars of the user as well? 13:38 popey: is that a design decision or a technical limitation? 13:38 be good to pull the others if we could but I think that's something eds determines 13:38 the latter I _think_ 13:38 ah ok 13:38 renato___: may know... ☻ 13:39 yes, that depends on EDS 13:40 although I'm pretty sure EDS on the desktop can sync multiple calendars 13:41 * popey tests 13:43 renato___: when you get time can you look at this bug https://bugs.launchpad.net/ubuntu-calendar-app/+bug/1362781 when you get time? 13:43 mihir, sure, I am in a meeting right now, I will take a look later 13:44 no issues, thanks renato___ :) 13:44 yeah, checked by installing evolution and setting an online accounts account for my company gmail and it seems to only sync my main calendar, no option to sync more. 13:44 popey: so we need change in EDS for multiple calendar support , is that correct? 13:45 mihir, I left https://code.launchpad.net/~ubuntu-calendar-dev/ubuntu-calendar-app/add-tests-for-future-and-past-events/+merge/232150/comments/574923. I hope that makes sense 13:45 balloons: thanks , i'll update trunk and then will try to work on AP 13:45 https://help.ubuntu.com/community/SyncEvolution/synchronize-multiple-google-calendars-with-evolution-calendars 13:46 looks cumbersome and not default. 13:46 hey guys, need your quick opinion on https://imgur.com/4imDDaQ 13:46 mihir: longer term yes, but not for right now. 13:46 ooh 13:46 nik90: great, but they are calendar color or event color ? 13:46 mihir: calendar color 13:47 nik90: amazing :) 13:47 mihir: that's what the current calendar app also does 13:47 yup :) this looks great :D 13:47 evolution does this too 13:47 events are black text on light coloured background 13:47 this looks nice, it was also part of one of original design 13:47 Currently the calendar app denotes it with a small circle and default to white bg for events. I removed that small circle and changed the event background instead 13:48 http://i.imgur.com/QwVLnvX.png for comparison 13:48 makes it more eventful (pun intended) :) 13:48 (also note the dark/light colours for day/night) 13:48 nik90: great :) looks great :) 13:49 popey: Akiva also proposed the light and dark backgrounds in the timeline view based on the time of the day 13:49 but it doesn't apply everywhere though...for instance in summer here in netherlands it is bright until like 19:00 13:49 or even later 13:49 nik90: that was i suppose based on working hours 13:50 mihir: that could work 13:50 like 8-5 will be active and rest will be dull 13:50 in google _you_ set your working hours 13:50 that's what most of calendars does 13:50 its not assumed to be 8-5 13:50 mihir: perhaps we could explore that, however the colors shouldn't be too distinct since it might take the user's attention away from the events 13:50 s/distinct/strong 13:50 popey: yup we have to make it configurable , i remember kunal has mentioned this in comment 13:51 we don't... we sync from google. 13:51 it can be set there. 13:51 Settings -> General -> Working hours. 13:51 popey: hmmm , 13:51 popey: but does google send this over to EDS? 13:51 I have mine set to 9-18 which is why evolution uses the colour there 13:52 but in our case we can put setting option in calendar i guess 13:52 i dont see how else evolution knows my working hours? 13:52 ah, evolution has its own setting 13:52 ignore me 13:52 so yes, we'd need to set that locally, bum. 13:52 calendar v 2.0 i think ㋛ 13:52 popey, mihir: we can perhaps add a settings option in the calendar app for this 13:53 but yes 2.0 :) 13:53 maybe later, lets stabilise what we have rather than add settings IMO 13:53 popey nik90: exactly :) 13:53 This would be a nice feature to add in a future version 13:53 speaking of which, I intend to do a version bump of calendar app..its stuck at 0.3 or something 13:53 along with setting working hours, days etc 13:53 yes 13:53 \o/ 1.0! 13:53 popey: okay. 13:53 nik90: lets merge all pending MRs , and put minor changes till the RTM 13:54 btw is this THE Jane Silber -> https://bugs.launchpad.net/ubuntu-calendar-app/+bug/1370603 13:54 bug fix & polish for now, yes. 13:54 +1 13:54 that is indeed the boss. 13:54 wow 13:54 instant critical bug status ㋛ 13:54 ahhh , that's great :D 13:55 hehe 13:55 lets try and debug that. events not showing up in the calendar make it less than useful. 13:55 yup 13:55 I am preparing a comment atm 13:56 Great , 13:56 ok. Anything else? 13:56 we overran a little ☻ 13:56 popey: nope nothing from my side 13:56 nothing much from my end 13:57 not from me as well 13:57 Great! 13:58 Thanks guys! Looking forward to seeing these updates landing! 13:58 have a great weekend. 13:58 #endmeeting