18:33 <mhall119> #startmeeting Weather App 18:33 <meetingology> Meeting started Thu May 30 18:33:47 2013 UTC. The chair is mhall119. Information about MeetBot at http://wiki.ubuntu.com/meetingology. 18:33 <meetingology> 18:33 <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 18:34 <mhall119> alright, link time 18:34 <mhall119> Bugs: https://bugs.launchpad.net/ubuntu-weather-app 18:34 <mhall119> Blueprint: https://blueprints.launchpad.net/ubuntu-phone-commons/+spec/initial-weather-development 18:34 <mhall119> Burndown: http://status.ubuntu.com/coreapps-13.10/ubuntu-weather-dev-coreapps-13.10-month-2.html 18:35 <mhall119> only 1 open bug, that's good, and it for supporting F instead of just C, which there is already a work item for 18:35 <neokore> hi all 18:35 <m-b-o> hi 18:35 <mhall119> hi neokore 18:36 <mhall119> alright, so let's take a look at the burndown chart real quick 18:36 <mhall119> so we're blocked on artwork from design 18:36 <mhall119> I know they're working on visual designs, starting with Clock, so hopefully we'll get that soon 18:36 <mhall119> what other assets are you waiting on from them? 18:37 <m-b-o> I'Ve added a blocked blueprint yesterday after the design meeting 18:37 <m-b-o> "Show weather for last known location at first start" 18:37 <mhall119> what does it do currently? 18:37 <mhall119> first location on the list? 18:37 <neokore> yeah 18:37 <mhall119> and what's that blocked on? 18:37 <m-b-o> last known location of the device 18:38 <m-b-o> after first start, when no locations where already added by the user 18:38 <mhall119> oh, I thought you meant last one you were looking at before closing it 18:38 <m-b-o> so there's no blank tab 18:38 <mhall119> ok 18:38 <mhall119> so you're waiting on location data to be supported? 18:38 <m-b-o> yes 18:38 <mhall119> ok 18:39 <m-b-o> any news about this? 18:39 <mhall119> only that there is a Qt Mobility API that should be used 18:39 <mhall119> which support multiple backend sources, one of which will be GPS on devices (eventually) 18:39 <neokore> I started investigating it, but by now with no success 18:39 <mhall119> but on desktop it should use geoip 18:40 <m-b-o> it would work on desktop with QtMobility? 18:40 <mhall119> in theory, that's what I've been told 18:40 <mhall119> http://doc.qt.digia.com/qtmobility/qml-location-plugin.html is the API 18:42 <m-b-o> it's alright to target with the blueprints for desktop, like this blueprint? It would not be blocked anymore 18:43 <mhall119> sorry, I didn't understand that 18:43 <mhall119> you mean if you can target the same API on the desktop, then it's not blocked? 18:43 <m-b-o> yes? 18:43 <m-b-o> yes! 18:43 <mhall119> ok, cool 18:44 <mhall119> next work item is the Chart Component 18:44 <mhall119> is that something we're still doing? I thought it was dropped from the design 18:45 <m-b-o> as far as i understood, yes 18:45 <neokore> I don't really know, but in the lastest designs I've seen there is no charts 18:46 <mhall119> can one of you send an email to calum and see if we still need to implement that? If not, I'll drop the work item from the list 18:46 <neokore> Ok 18:46 <mhall119> thanks neokore 18:47 <mhall119> u1db integration, m-b-o have you started on this? 18:47 <m-b-o> I'm still waiting for a new u1db build 18:47 <mhall119> I know the u1db-qt package has been broken for a while 18:47 <mhall119> we're moving it to the SDK team's PPA, because that one uses real ARM hardware to build, instead of a virtual environment 18:47 <m-b-o> codewise, the most things are ready, but would not work 18:47 <mhall119> that should get working packages again 18:48 <m-b-o> I'm unsure if month-2 will be possible 18:48 <mhall119> ok, we can move that back to month-3 18:49 <mhall119> I see the packages are in the new PPA, but still failing to build, I'll try and get that resolved for you guys 18:49 <mhall119> until then I'll mark the work item as BLOCKED too 18:49 <m-b-o> I'll look in next build and will decide if month-2 will be possible 18:49 <m-b-o> okay 18:49 <mhall119> next up, unit tests 18:49 <m-b-o> I've started with autopilot 18:49 <mhall119> awesome! 18:50 <mhall119> we still have to run them manually as far as I know, but eventually jenkins will run them 18:50 <m-b-o> I've tried to reach an action in the toolbar, but found no way, except be setting absolute pixel 18:50 <mhall119> hmmm, might need to ask balloons about that 18:51 <m-b-o> another problem is localstorage 18:51 <m-b-o> at least on desktop 18:51 <m-b-o> should be cleared at setUp, but I don'* know how 18:52 <mhall119> hmmm...I wonder if we can make it use some temporary location when running a test 18:52 <m-b-o> yes, that would be ideal 18:53 <mhall119> alright, ability to change units (C/F) 18:53 <mhall119> neokore: has that started? 18:54 <neokore> yes 18:54 <mhall119> INPROGRESS still, or DONE? 18:54 <neokore> inprogress 18:55 <mhall119> ok 18:55 <mhall119> anything blocking you on that one? 18:55 <neokore> I just have finished the "screen" but not yet where to save it 18:55 <mhall119> ok 18:55 <m-b-o> gconf will be used, right? 18:56 <mhall119> dconf, eventually 18:56 <m-b-o> okay 18:56 <neokore> ok 18:56 <mhall119> they plan on using an upstream component to wrap it 18:56 <mhall119> QPropertyMap 18:56 <mhall119> but there's currently a bug with accessing it from QML 18:56 <mhall119> they're going to use it for the SystemSettings app too, so I know they're following up on it 18:57 <mhall119> for now it can just go into the same LocalStorage as the locations 18:57 <neokore> ok 18:57 <mrqtros> Hi all 18:57 <m-b-o> okay, I'll add a function for that 18:57 <m-b-o> in Storage.qml 18:57 <balloons> m-b-o, #ubuntu-autopilot is great for help :- 18:58 <neokore> great m-b-o 18:58 <mhall119> and that's all the work items for month-2 18:58 <mhall119> I'll update the blueprint with what we discussed 18:58 <m-b-o> balloons: thanks 18:58 <mhall119> things are looking good guys, thanks for your work 18:59 <neokore> thanks 18:59 <mhall119> #endmeeting