== Meeting information == * #ubuntu-touch-meeting: Calendar app meeting, 15 May at 13:03 — 13:31 UTC * Full logs at [[http://ubottu.com/meetingology/logs/ubuntu-touch-meeting/2014/ubuntu-touch-meeting.2014-05-15-13.03.log.html]] == Meeting summary == ''LINK:'' https://code.launchpad.net/~mihirsoni/ubuntu-calendar-app/limitFunctionality/+merge/211536 is also causing me concern. ''LINK:'' https://bugs.launchpad.net/ubuntu-calendar-app/+bug/1319373 ''LINK:'' https://bugs.launchpad.net/ubuntu-calendar-app/+bug/1319382 == Vote results == == Done items == * (none) == People present (lines said) == * popey (31) * pkunal-parmar (15) * mihir_ (4) * meetingology (3) * mihir (2) * renato (1) == Full Log == 13:03 #startmeeting Calendar app meeting 13:03 Meeting started Thu May 15 13:03:26 2014 UTC. The chair is popey. Information about MeetBot at http://wiki.ubuntu.com/meetingology. 13:03 13:03 Available commands: action commands idea info link nick 13:03 Hi renato pkunal-parmar too ☻ 13:03 Hi 13:03 hey all :) 13:04 I see renato was looking at https://code.launchpad.net/~pkunal-parmar/ubuntu-calendar-app/CalManagement/+merge/213355 yesterday and created https://code.launchpad.net/~renatofilho/qtorganizer5-eds/fix-engine-crash/+merge/219586 13:04 renato: who can review https://code.launchpad.net/~renatofilho/qtorganizer5-eds/fix-engine-crash/+merge/219586 ? 13:06 https://code.launchpad.net/~mihirsoni/ubuntu-calendar-app/limitFunctionality/+merge/211536 is also causing me concern. 13:06 As I wrote in my comment, it's eating up cpu on my device when i scroll around in the app. 13:06 popey: i am not sure how can i fix it :( 13:06 Yeah, I don't know if it's also an EDS thing 13:06 EDS eats 100% CPU when I refresh the calendar by moving around. 13:07 Moving arund will cause some QML object creation as well 13:07 but yes, model will also get refreshed 13:07 so that will also take time 13:08 I have a fair amount in my calendar. 13:08 but I don't know if that's the issue, or something else? 13:08 but I expect, EDS stuff happening in seperate thread then thread in which QML makes call 13:09 yes, you see the spinner in calendar, and in the background UDS is busy 13:09 you can see two processes on the phone, eds calendar factory and qmlscene, as expected 13:10 but what about model, does it also run operation in seperate thread 13:10 i couldn't tell. 13:10 if I call some model function, can it hang QML code 13:10 right 13:11 I thought renato might know 13:11 I suspect renato is having his morning coffee right now ☻ 13:11 so as we dead with more and more data in calendar, we will need to work out those things 13:11 yes. 13:12 hi guys I am in a meeting right now, sorry 13:12 morning, np 13:13 BTW, how do you test branch on device, I am facing some issue now, testing on device 13:13 pkunal-parmar: https://code.launchpad.net/~pkunal-parmar/ubuntu-calendar-app/CalManagement/+merge/213355/comments/523841 13:13 see that comment, that's what I do 13:13 ok 13:14 I also wanted to push an update to the store, as the store is 24 revs behind trunk. 13:14 Unfortunately the autopilot tests failed. 13:14 ok 13:14 https://bugs.launchpad.net/ubuntu-calendar-app/+bug/1319373 13:14 https://bugs.launchpad.net/ubuntu-calendar-app/+bug/1319382 13:15 balloons: did you have a chance to look at that? 13:17 pkunal-parmar: have you started new design for Event ? 13:18 do we have new design ? 13:19 nope, i thought you were trying to convert in page wise 13:19 no, I think we need some proper design, with usability and other thing considered 13:20 okay :) 13:23 So my goal is really to get those AP problems fixed ASAP, so we can get an update in the store 13:23 Then we need to make sure we bleed renato dry of all eds fixes, land those, and then land calmanagement and limitfunctionality branches. 13:23 Hmm okay. 13:26 Anything else we need to discuss? 13:30 no, not from me, this week I was busy, so I was not able to do anything useful 13:30 No problem. 13:31 Ok, I'll keep on top of the outstanding merges, see if we can get those landed as soon as possible. 13:31 Thanks guys 13:31 #endmeeting Generated by MeetBot 0.1.5 (http://wiki.ubuntu.com/meetingology)