#title #ubuntu-touch-meeting: Calendar App Meeting Meeting started by mhall119 at 17:03:15 UTC. The full logs are available at http://ubottu.com/meetingology/logs/ubuntu-touch-meeting/2013/ubuntu-touch-meeting.2013-03-28-17.03.log.html . == Meeting summary == *progress update *miletone targets ''ACTION:'' mhall119 to investigate performance testing on the Ubuntu UI toolkit (mhall119, 17:41:06) Meeting ended at 17:42:30 UTC. == Votes == == Action items == * mhall119 to investigate performance testing on the Ubuntu UI toolkit == Action items, by person == * mhall119 ** mhall119 to investigate performance testing on the Ubuntu UI toolkit == People present (lines said) == * frankencode (75) * mhall119 (54) * meetingology (4) == Full Log == 17:03:15 #startmeeting Calendar App Meeting 17:03:15 Meeting started Thu Mar 28 17:03:15 2013 UTC. The chair is mhall119. Information about MeetBot at http://wiki.ubuntu.com/meetingology. 17:03:15 17:03:15 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:03:38 i'm here 17:04:54 hi frankencode 17:05:27 not much happened with the calendar this week 17:05:33 but steady progress 17:05:33 so you guys may have noticed, I moved the Blueprint for the initial development to the ubuntu-phone-commons app 17:05:49 the blueprint is now at https://blueprints.launchpad.net/ubuntu-phone-commons/+spec/initial-calendar-development 17:05:52 yes, i already edited in the new location 17:06:24 i reflashed my phone last week 17:06:35 the onscreen keyboard seems not to work as expected... 17:06:36 the goal is to get work item tracking for these core apps on status.ubuntu.com 17:07:07 frankencode: file a bug for anything like that 17:07:28 yeh, i noticed there was work ongoing affecting the keyboard 17:07:31 put it on ubuntu-ui-tookit, and then the SDK devs can sort out which are SDK bugs and which are touch image bugs 17:07:36 and it already improved... 17:07:44 #topic progress update 17:07:58 ok, so what's been happening since last week? 17:08:35 i spent most of my time with the sqlite local storage 17:08:40 and getting it work in the gui 17:08:57 is that for storing events? 17:09:02 i forget how long it takes to get an sql query processed 17:09:07 yes 17:09:11 events, todos, config 17:09:32 ok, as far as I know they're still evaluating calendar backends (evolution-data-server, akonadi, etc) 17:09:54 yes, that is another component 17:09:54 is it going to be difficult to switch from sqlite to one of those once a decision is made? 17:10:20 the api is designed to fully encapsulate the sqlite stuff 17:10:31 perfect 17:10:36 the gui code shouldn't worry about where the data is coming from 17:11:20 so as far as what's in trunk right now, I noticed there was something for creating test events, but I don't know how to get that working 17:11:40 qmlscene calendarTests.qml 17:12:01 that will load the schedule of the qt devdays of last year 17:12:06 just for testing... 17:12:34 but i'm trying the get the "new event" dialog working next 17:12:48 kunal already created one, but it doesn't works on the touch 17:13:03 onscreen keyboard does not appear when focus enters a line edit 17:13:07 what day does it put them on? 17:13:24 i think the today and next day 17:13:25 hmm, keyboard should appear whenever a text input has keyboard focus 17:13:47 yes, i'm looking into that issue next 17:14:05 thereafter everyone can enter their own events... 17:14:14 ok 17:14:30 so the "create event" view is in progress? 17:14:37 yes 17:14:49 can you update the blueprint work item from TODO to INPROGRESS? 17:14:55 as i said there is already a test version, but it works only on the desktop 17:15:05 yes inprogress 17:15:35 is mariob helping with that? 17:16:15 lets see 17:17:06 for sure i set him to review the code 17:17:20 question about that bot (jenkings?) 17:17:26 how does it work? 17:17:38 sometimes it does wonders, most of the time it does nothing 17:18:07 some reviewed branches never get merged, some other get merged immediately 17:18:39 it's *supposed* to periodically check for approved MP's and automatically merge them into trunk 17:18:57 we've had some technical difficulties with it lately though 17:19:25 ok i have a feature request then: add a fat "kick bot ass" button 17:19:26 the MP needs to have a commit message, in addition to a description, so that's the first thing to check 17:19:43 commit message for merge, no conflict 17:19:49 frankencode: ping fginther on IRC, he's our "kick bot ass" button 17:19:50 yet the branch stays there for weeks 17:20:15 human interface to a bot?, COOL! 17:20:26 ok, any other work items that were worked on in the past week? 17:20:27 jokes aside 17:21:01 kunal did some experimentation on the layout change for the event view vs. the moth view 17:21:35 no idea what else went on 17:21:39 was that a work item on the blueprint? 17:21:50 yes, i put that to DONE 17:21:56 ah, ok, that one 17:22:03 how about the event API? 17:22:16 that's DONE, too 17:22:34 awesome 17:22:44 and the Implement backend data model? 17:23:05 DONE 75% 17:23:51 ok 17:24:05 #topic miletone targets 17:24:22 what milestones? 17:24:24 so part of the blueprints move is to get the coreapps on the same monthly planning cycle as the rest of Ubuntu is adopting 17:24:39 which means we'll have milestones for each month between now and 13.10 17:24:49 ok with me, though i don't plan my hobbies;) 17:25:37 next things in my pipe: a) get all the stuff from kunal working in trunk 17:25:45 frankencode: understood, it just helps organize what can be done in the near-term, and what will require longer-term work 17:25:48 b) prepare a list of assets for the designers 17:26:17 yea, understood, makes it also more transparent 17:26:56 ok, I just updated the blueprint 17:27:00 is there already a common icon set, or something? 17:27:07 there are currently 2 milestones, with work items divided between them 17:27:35 frankencode: not yet, design has told us to just use what we can find until they can provide a them 17:28:11 so, milestone coreapps-13.10-month-0 corresponds to April, so things we think we can get done next month 17:28:52 ok 17:28:54 the rest of the calendar work items are in coreapps-13.10-month-1, which is what we had originally been calling alpha-1, and represents work to be finished in May 17:29:00 i need to add a few things 17:29:16 you can move them around, or push things out to month-[0-6] 17:30:01 clear 17:31:09 so currently you're waiting on a decision on event-storage, and also waiting on design for image assets 17:31:59 is that correct? 17:32:36 yes 17:32:52 well, i'm going to wait, once i know which assets i need 17:33:07 i guess the prototype has to grow a little bit further... 17:33:34 is there anything else that you are currently either waiting on or blocked on? 17:34:05 not really 17:34:25 i'd like to see some more tests on the theme engine 17:34:27 alright, anything I or popey can do for you? 17:34:48 i've noticed progress on the theme engine in uitoolkit 17:35:21 e.g. the Ubuntu.components label is an order of magnitude to slow to be useful 17:35:36 oh, really? 17:35:57 it was even unreliable in my initial tests, so i had to work around 17:36:05 i have to check back with the latest version 17:36:31 did you file a bug? 17:36:56 yes, once i get my lazy ass into creating some reproducible tests 17:37:05 the SDK team needs us all to report bugs for things like this, so they know where they need to improve 17:37:07 or someone else does... 17:38:04 i think when i scrolled a few hundret times (i was testing something else) I got strange font attributes in the labels on the calendar 17:38:12 that sucks, difficult to reproduce 17:38:22 was that on the desktop or on a device? 17:38:40 i think on the desktop 17:38:49 anyway the real killer was performance on device 17:39:13 so i took a Text and copied over the font attributes from a single label created once 17:39:15 I'll ask and see if we have any automated performance testing for the SDK codebase 17:39:44 the tab widget is also horrible slow and the initial tab seems to be place randomly 17:40:00 yes, that's one big TODO: test the uitoolkit things... 17:40:05 I noticed that on the calendar, but not on other apps, which is strange 17:40:26 well there are lots of labels for each month;) 17:40:35 ah the tab widget 17:40:48 yes maybe a problem on how we use it... 17:41:06 #action mhall119 to investigate performance testing on the Ubuntu UI toolkit 17:41:06 * meetingology mhall119 to investigate performance testing on the Ubuntu UI toolkit 17:42:02 alright, we're well past time on this meeting, is there anything else you would like to discuss before we wrap it up? 17:42:17 that's all 17:42:30 #endmeeting Generated by MeetBot 0.1.5 (http://wiki.ubuntu.com/meetingology)