13:02 #startmeeting Calendar app meeting 13:02 Meeting started Thu Apr 24 13:02:12 2014 UTC. The chair is popey. Information about MeetBot at http://wiki.ubuntu.com/meetingology. 13:02 13:02 Available commands: action commands idea info link nick 13:02 hows it going? 13:02 going fine, how about you 13:02 Great, thanks, now the stress of 14.04 release is passed ☻ 13:03 bfiller mentioned to me that he's filed a bunch of bugs against calendar. 13:03 renato: as I understand it you're going to be working on some? 13:03 yes, I seen those 13:03 Calendar App links:- 13:03 Bugs: https://bugs.launchpad.net/ubuntu-calendar-app/+bugs 13:03 Reviews: https://code.launchpad.net/ubuntu-calendar-app/+activereviews 13:03 Blueprint: https://blueprints.launchpad.net/ubuntu-phone-commons/+spec/coreapps-1404-calendar-dev 13:03 General Links:- 13:03 Milestones: https://launchpad.net/ubuntu-phone-coreapps/+milestones 13:03 Burndown: http://status.ubuntu.com/coreapps-14.04/ 13:03 Blockers: https://wiki.ubuntu.com/Touch/CoreApps/Blockers 13:05 popey, yes I will work on some of then, but if pkunal-parmar have time he can get one of then :D 13:05 I am still working on address-book and sync bugs 13:05 :), sure I am planning to work on some 13:05 I will move to calendar as soon as I finish it 13:05 probably some day next week 13:06 Ok, do make sure you assign them to yourself when you do so we don't duplicate work. 13:07 ok 13:07 BTW I was working on Bug #1304497: Multiple events at the same time are hard to spot. 13:08 https://dl.dropboxusercontent.com/u/23815163/DayMultiEvent.png 13:08 ok.. 13:08 currently I implemeted this way, 13:08 but it would be good to have some design guideline for the same 13:08 does it just put multiple events side by side? 13:08 so if there's 3 or 4 they squish up, right? 13:08 it put event side by side if start hour is ame 13:08 same 13:09 that'll work for some use cases. I think we need to test that with some more interesting combinations of time slots 13:10 I note in Google calendar web view, it starts overlapping beyond 2 13:10 well, overlaps a shorter duration one on top of a longer duration meeting 13:10 ok 13:10 if you some screeshot for such usecase , please send 13:11 I will modify code so then 13:11 https://imgur.com/gPESXMS for example 13:12 https://imgur.com/82jaMGB 13:12 so the shorter meeting which starts at the same is overlapping the longer meetin 13:13 ok 13:13 trying to find other examples 13:14 so some them are side by side and some overlaps ? 13:14 I think the rule they're using is pretty simple, i cant find any more exceptions.. 13:14 its difficult to undetand how it decides size and position of each event 13:14 1) If meetings start at the same time they're side by side. 13:14 2) if a meeting is shorter duration at the same time slot, make it overlap other meetings at same timeslot 13:15 ok, now I understand 13:16 I am enabling lots of other calendars on my google account and I can't see anything which overrides those rules 13:16 obviously when you have more than 3 entries side-by-side in one slot, it becomes hard to read. 13:16 that's not easy to fix 13:16 ok 13:17 I will try to replicate that then 13:17 I'll try and get some design input on the colour bug that's come up a couple of times. 13:18 ok 13:21 One thing we need to identify is a list of the bugs / features which need to be complete by the releast to manufacturer date 13:21 (which I don't have) 13:21 We don't have a long time, and we need to focus on those things which are most important. 13:22 I'll try and get some guideline on when our target is, and we can focus on the things that matter 13:22 ok, that will be good 13:23 This may or may not include new designs. Not sure on that yet. 13:24 ok 13:25 pkunal-parmar: are there any things blocking you right now? 13:25 yes, those crash 13:25 I am still getting those 13:25 crash 13:25 for calendar management branch 13:26 did you try the qtpim from my ppa? 13:27 yes, I downloaded the debs and installed using dpkg -i 13:28 hmm 13:28 you're getting the same crash or a different one? 13:28 or i needed to installed by apt-get ? 13:28 no 13:28 it should work with dpk 13:28 dpkg 13:28 yes, looks same 13:29 though, when I open calendar gdb, it crash on startup 13:29 so not sure other crash are same as start up or not 13:32 Hm. 13:32 might need to get tsdgeos to take a look.. 13:33 * popey pings him 13:33 halo 13:34 yo 13:34 remember https://code.launchpad.net/~pkunal-parmar/ubuntu-calendar-app/CalManagement/+merge/213355 ? 13:34 seems pkunal-parmar is still getting crashes, even with the modified qtpim.. any ideas where to look? 13:34 popey: valgrindize the thing 13:35 to see where the crash is coming 13:35 valgrind --trace-chilren=yes qmlscene foobar.qml 13:36 ok let me try 13:36 and psate the log that you get 13:37 unfortunately it'll probably be full of ???? 13:37 as of now I am getting 13:37 valgrind: Bad option: --trace-chilren=yes 13:37 ahh 13:37 typo 13:37 shoul be --trace-children 13:37 ah yes 13:37 ironic i missed the "d" off "should" there. 13:37 broken keyboard result of trying to clean it up 13:38 i miss random key presses sometimes 13:39 so, I have log now 13:39 you want me to send mail ? 13:41 ==9633== 13:41 ==9633== Process terminating with default action of signal 11 (SIGSEGV) 13:41 ==9633== Access not within mapped region at address 0x8 13:41 ==9633== at 0xE1BD07A: QtOrganizer::QOrganizerItemFetchRequest::filter() const (in /usr/lib/i386-linux-gnu/libQt5Organizer.so.5.0.0) 13:41 ==9633== by 0x1060A796: FetchRequestData::appendResults(QList) (in /usr/lib/i386-linux-gnu/qt5/plugins/organizer/libqtorganizer_eds.so) 13:41 ==9633== by 0x1060A89C: FetchRequestData::nextCollection() (in /usr/lib/i386-linux-gnu/qt5/plugins/organizer/libqtorganizer_eds.so) 13:41 ==9633== by 0x105E6B65: QOrganizerEDSEngine::itemsAsyncStart(FetchRequestData*) (in /usr/lib/i386-linux-gnu/qt5/plugins/organizer/libqtorganizer_eds.so) 13:41 ==9633== by 0x105E6E2A: QOrganizerEDSEngine::itemsAsyncDone(FetchRequestData*) (in /usr/lib/i386-linux-gnu/qt5/plugins/organizer/libqtorganizer_eds.so) 13:41 ==9633== by 0x106506D2: ??? (in /usr/lib/libecal-1.2.so.16.0.0) 13:41 ==9633== by 0x10656B23: ??? (in /usr/lib/libecal-1.2.so.16.0.0) 13:41 ==9633== by 0x9BC7064: g_simple_async_result_complete (in /usr/lib/i386-linux-gnu/libgio-2.0.so.0.4000.0) 13:41 ==9633== by 0x9BC7106: ??? (in /usr/lib/i386-linux-gnu/libgio-2.0.so.0.4000.0) 13:41 ==9633== by 0x5BF6C4F: ??? (in /lib/i386-linux-gnu/libglib-2.0.so.0.4000.0) 13:41 ==9633== by 0x5BFA0A6: g_main_context_dispatch (in /lib/i386-linux-gnu/libglib-2.0.so.0.4000.0) 13:41 ==9633== by 0x5BFA467: ??? (in /lib/i386-linux-gnu/libglib-2.0.so.0.4000.0) 13:41 this is last part of log 13:43 tsdgeos: ^ 13:44 that looks bad : 13:44 :D 13:44 wasn't the crash i had 13:44 so maybe there were two crashes one after the other and i just fixed the first and ran away home happy 13:45 pkunal-parmar: how do you reproduce the crash? 13:45 I think, this happens because of using filter 13:45 you can try my branch 13:45 its quite frequent with that branch 13:46 https://code.launchpad.net/~pkunal-parmar/ubuntu-calendar-app/CalManagement/+merge/213355 13:46 pkunal-parmar: any special things you do? 13:47 yes, usually I go to toolbar-> calendars and then select / unselect some calendar 13:47 then it happens 13:48 i'll have some spare time in a few mins 13:48 maybe i can check 13:48 but sure i have much calendars though 13:48 ok 13:48 thanks tsdgeos 13:48 so maybe it doesn't crash for me 13:49 i may need some help with the setup 13:49 I am here for sometime, or renato will be able to help 13:50 pkunal-parmar: any other blockers? 13:50 yes, we had one, calendar import from iCal file 13:51 I forgot the framework name :), that enable content sharing 13:52 we need that so user can download or copy iCal and can be launched by calenar 13:52 *calendar 13:53 part from that, I dont remember anything else 13:53 ok. 13:54 I'll have a word with ken about that. 13:54 ok 13:55 Ok, anything else? 13:55 Once we get the calendar management branch landed, I'd like to push a new version to the store (once we test it a bit more). 13:56 yes, I think we need to test it bit before we push to store 13:57 I can certainly build a click and have more people test it 13:57 Ok, lets wrap up then.. 13:57 #endmeeting