17:05:31 <popey> #startmeeting ubuntu calendar app
17:05:31 <meetingology> Meeting started Thu Mar 21 17:05:31 2013 UTC.  The chair is popey. Information about MeetBot at http://wiki.ubuntu.com/meetingology.
17:05:31 <meetingology> 
17:05:31 <meetingology> Available commands: #accept #accepted #action #agree #agreed #chair #commands #endmeeting #endvote #halp #help #idea #info #link #lurk #meetingname #meetingtopic #nick #progress #rejected #replay #restrictlogs #save #startmeeting #subtopic #topic #unchair #undo #unlurk #vote #voters #votesrequired
17:05:35 <popey> hi frankencode
17:05:45 <frankencode> hi
17:06:47 <frankencode> the others are all busy today
17:07:04 <mhall119> good thing we'll have meeting minutes
17:07:32 <popey> so I saw the video showing events..
17:07:38 <popey> is that what's in https://code.launchpad.net/~frankencode/ubuntu-calendar-app/data-service/+merge/154240
17:07:42 <popey> ?
17:07:51 <frankencode> video?
17:08:13 <popey> mhall119: do you have the link to the video?
17:08:14 <frankencode> no, event view lives in EventView_smth
17:09:01 <mhall119> popey: no, but I could find it
17:09:42 <frankencode> i was doing some foundation work in the data-service branch
17:09:42 <mhall119> https://plus.google.com/u/0/111980561516715514914/posts/TVjNnYZ41Hb
17:09:56 <popey> http://www.youtube.com/watch?v=rphstrhXTYc
17:10:35 <popey> Ah it was Kunal.. sorry.
17:10:48 <popey> So are you currently blocked on anything frankencode ?
17:10:58 <frankencode> no
17:11:14 <frankencode> the video shows current state in EventAPI_EventView branch
17:11:23 <frankencode> there was a problem of integrating it
17:11:47 <frankencode> firstly it wouldn't scale to more than a few hundret events entered (sql inefficiency...)
17:12:07 <frankencode> secondly the flickable for the events kills the ability to draw the events view up
17:12:24 <frankencode> but the solution is already found....
17:12:30 <popey> oh?
17:12:34 <mhall119> frankencode: is the sql problem on inserting, or pulling back out and displaying?
17:12:44 <frankencode> select for display
17:12:57 <mhall119> hmmm, sqlite should be efficient for that
17:13:20 <frankencode> yes clear, the solution of kunal was not meant to serve for more than testing his part
17:13:35 <frankencode> so i made a more complete sqlite solution in the data-service branch
17:13:47 <frankencode> i also fixed the issue with the overlapping flickables
17:13:50 <mhall119> ok, so you think that will fix the scaling issue?
17:14:02 <frankencode> think about it: we have 3 tightly interlinked flickables!
17:14:11 <frankencode> yes, it scales now
17:14:18 <mhall119> awesome
17:14:21 <popey> sweet!
17:14:26 <frankencode> who can add some billion events, if you can
17:14:38 <mhall119> yeah, the designs for the calendar app are pushing past what the defualt SDK provides
17:14:47 <frankencode> not much
17:14:55 <mhall119> but you guys are doing a fantastic job with it
17:15:13 <frankencode> i feel the tab widget needs to be improved
17:15:17 <popey> agreed, I'm impressed how far it's come in just a few weeks
17:15:43 <popey> frankencode: does that need design input?
17:16:00 <frankencode> i think mika promised some assets by eastern
17:16:07 <mhall119> so for the storage of events, is there any system-wide store we should be using?
17:16:13 <mhall119> like, we have evolution-data-server on the desktop
17:16:27 <mhall119> which is where the Unity datetime indicator looks for events
17:16:40 <mhall119> popey: do you know what the plan is for that on UnityNext?
17:16:45 <frankencode> ok, eds is running on the phone?
17:16:55 <mhall119> frankencode: I don't know
17:17:04 <mhall119> that's what I was asking
17:17:32 <frankencode> i'm still not worried about the backends
17:17:41 <popey> I don't, but I think there are some sessions on hangouts coming up where we may be discussing it
17:17:43 <frankencode> worst case we have to hack our own indicator
17:17:53 <frankencode> beside that we need a reminder service
17:18:00 <frankencode> and need to access contacts and maybe places
17:18:21 <popey> ah, no it's a secure credentials storage hangout
17:18:25 <mhall119> contacts should go through libfolks I think
17:18:53 <mhall119> at least that's what I heard from Ken months ago
17:19:06 <frankencode> yes the phone-app uses libfolks
17:19:23 <frankencode> but it looks excessively complex
17:19:31 <popey> yes, i had a chat with kevin about scheduling stuff
17:19:40 <popey> aka cron
17:21:03 <mhall119> if it's e-d-s, I think it'll handle notifications
17:21:19 <frankencode> i'm dreaming of some central system service speaking json, that takes care of everything
17:21:19 <popey> but we don't have anything yet for system wide storage or system wide scheduling
17:21:30 <frankencode> at best on local sockets
17:22:07 <mhall119> ok, I'll try and get an answer on backend storage
17:22:45 <frankencode> at the end these apis will need to be open for app developers
17:22:48 <popey> #action mhall119 investigate backend storage
17:22:48 * meetingology mhall119 investigate backend storage
17:23:05 <frankencode> you can't tell anyone to write a Qtmobility plugin the way it is done in the phone-app
17:24:28 <frankencode> i also got used opening nodejs console, when i need to play aroud with javascript
17:24:50 <frankencode> maybe somethink like nodejs could run the services for the phone
17:25:07 <popey> i can imagine a few people will like that
17:25:58 <popey> #action popey investigate scheduling service for events wake-up
17:25:58 * meetingology popey investigate scheduling service for events wake-up
17:26:55 <popey> frankencode: anything else you need from us?
17:27:14 * frankencode merge EventView branch into date-service into trunk
17:27:23 <frankencode> i'm fine
17:27:54 <popey> sweet. mhall119 have anything else?
17:28:09 <mhall119> nothing from me
17:28:20 <mhall119> other than a general "great work" to all the developers
17:29:25 <frankencode> ahh
17:29:30 <frankencode> one thing
17:29:36 <popey> go for it
17:29:42 <frankencode> we have to look into holidays
17:29:55 <frankencode> eastern is next week? damn that unity calendar won't show it
17:30:29 <mhall119> I think there are public holiday icals you can import
17:30:34 <frankencode> anyway, if someone is going to read this log, let me know your ideas about it
17:30:45 <mhall119> is ical importing something we have on the feature list?
17:30:49 <frankencode> mhall119: really?
17:31:09 <popey> not on https://blueprints.launchpad.net/ubuntu-calendar-app/+spec/initial-calendar-development
17:31:30 <mhall119> maybe for alpha-2?
17:32:09 <popey> yeah
17:32:43 <popey> be nice if you could click on an ical and it open in the calendar app
17:32:59 <frankencode> yes, i googled ical and holidays
17:33:16 <frankencode> lots of hits
17:33:19 <popey> pretty sure the official google calendars are public too
17:33:21 <frankencode> offering download links
17:33:28 <popey> those are the ones I subscribe to in google anyhow
17:33:45 <popey> yeah, i dont think finding the icals will be the problem here :D
17:34:40 <popey> ok, lets wrap up
17:34:43 <popey> thanks frankencode
17:34:52 <popey> (and mhall119 )
17:34:55 <popey> #endmeeting