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