19:02 <mhall119> #startmeeting Music App 19:02 <meetingology> Meeting started Fri Jun 7 19:02:26 2013 UTC. The chair is mhall119. Information about MeetBot at http://wiki.ubuntu.com/meetingology. 19:02 <meetingology> 19:02 <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 19:02 <mhall119> Blueprint: https://blueprints.launchpad.net/ubuntu-phone-commons/+spec/initial-music-development 19:03 <mhall119> vthompson: how is the work going to merge your and Daniel's branches? 19:03 <vthompson> The merge is complete 19:03 <mhall119> \o/ 19:04 <vthompson> Right now I'm trying to work through how we are going to populate the music library in LocalStorage 19:04 <mhall119> ok, here's the list of work items from the blueprint: http://pad.ubuntu.com/X9yf5Jss8C 19:04 <vthompson> When we switch over from reading tracks from the filesystem to reading tracks from the LocalStorage the app will need a lot of changes 19:05 <mhall119> are other parts of the app highly dependent on the filesystem data? 19:06 <vthompson> Once we're reading from LocalStorage, only selecting the Music folder can/will be. 19:06 <mhall119> ok 19:06 <mhall119> so the only TODO work items for month-2 are design related 19:06 <vthompson> I'm going on the assumption right now that we'll use a metadata aware version of the nemo FolderListModel to scan the directory 19:06 <vthompson> Which month are we in now? 19:07 <mhall119> month-2 19:07 <mhall119> so we're ahead of what we had scheduled 19:07 <vthompson> So, my main push right now is to get local storage populated reliably and to read from localstorage to get tracks on the screen 19:08 <mhall119> I'd like to pick some of the ones from the bottom list to target for month-3 19:08 <vthompson> that isn't very design related 19:08 <mhall119> btw, were you able to view that etherpad document? 19:08 <vthompson> Yep, I'm in it now 19:09 <mhall119> ok, feel free to edit it too 19:09 <mhall119> do you know which of these daniel is currently working on, or going to be working on next? 19:09 <vthompson> Not quite sure 19:10 <vthompson> I might try to get some help with the LocalStorage scheme from him. (he was the one who originally created it) 19:11 <mhall119> ok 19:11 <mhall119> so what currently works, after merging the two branches? 19:11 <vthompson> We also need to flush out if what we want to change in the nemo plugin will go into what ubuntu-filemanager-app is using 19:12 <mhall119> we should keep everything in the one plugin 19:12 <vthompson> Getting metadata from tracks via a modified nemo plugin works. Cover art works. Shuffle works. 19:12 <vthompson> Agreed. Are these changes also getting pushed upstream? 19:13 <mhall119> vthompson: they've been submitted, we're going to work on getting them accepted 19:13 <vthompson> the Filemanager might now want to have music metadata being read--it could slow down the responsiveness of the app if the data is large 19:14 <vthompson> *might not want 19:14 <vthompson> So we'll have to continue working with Carlos to see what we can push upward 19:14 <mhall119> hmmm, can you do the metadata reading outside of the folderlist plugin? 19:14 <vthompson> Not in QML. We could make our own plugin though 19:15 <vthompson> I sent an email earlier today that broke down what I see as our 2 options to get this data in the database. 19:15 <mhall119> that might be a better option if it'll impact the performance of others 19:15 <vthompson> 1) an external binary that scanns the directories or 2) what we are talking about now. 19:16 <vthompson> We could always try to provide a switch in the plugin to not read the data... readMetadata defaults to false 19:16 <vthompson> Then there'd be no impact other than the clutter of our needs in the code 19:17 <mhall119> ok, you'll work that out with Carlos? 19:17 <vthompson> I will 19:17 <vthompson> I hope to get this figured out by the end of the week. 19:18 <vthompson> end of next week that is... since it is almost the weekend. :) 19:19 <balloons> mhall119, we ready to talk about autopilot stuff? 19:20 <vthompson> Does autopilot depend on certain QML elements? If so, it might be too early to setup such testing 19:21 <balloons> vthompson, hello.. I'm not sure we've met yet, as the music app is new to the bunch 19:21 <vthompson> Once the app switches over to reading local storage, we'll have more options for dlsplaying data. So we'll need to work with the design team to figure out how we'll display it all 19:21 <balloons> vthompson, so autopilot keys off of QML defined objects.. The only code changes are to name the objects you want to test 19:22 <vthompson> Ah, so you don't need to create specic test cases? 19:22 <vthompson> *specific 19:22 <balloons> vthompson, oh you still have to make the specific test cases indeed :-) Just in the main source those are the only changes.. 19:23 <balloons> since you were asking if it was possible to have an autopilot test(s) yet or not 19:23 <balloons> as long as you have a UI that loads and runs, we can add autopilot tests to it and grow it as you add stuff 19:23 <vthompson> It sounds possible, I just don't think it's worthwhile until we know what will be on the glass 19:24 <balloons> sure.. I'd like to just setup a basic test for the app until you start to dev a bit more.. I'm not sure of the state of progress as much as mhall119 19:24 <vthompson> We could put autopilot into the mini player control at the bottom of the app, however. 19:24 <balloons> ahh ok 19:24 <vthompson> That may be more stable 19:27 <balloons> ok well can you think of what features could be tested as part of that? 19:27 <mhall119> hey,sorry, had to step away for a minute 19:28 <vthompson> balloons, probably the following: Play, pause, forward. There's a now playing page that might be stable as well. We could test play, pause, forward backward, swipe to go forward, swipe to go backward. 19:29 <balloons> vthompson, perfect. I'll make those the initial set of tests 19:29 <mhall119> balloons: how would we test that a song actually plays? 19:29 <balloons> what we going to do is file a bug for each one as part of this if you haven't seen it 19:29 <balloons> http://www.theorangenotebook.com/2013/06/autopilot-tests-for-ubuntu-touch-core.html 19:30 <vthompson> It uses the QML MediaPlayer element. I'm assuming we could test the state of the player (playing, paused, stopped) 19:30 <balloons> there's a recipe talking about how to do autopilot with qml and how to contribute on that page.. and we're having a hackfest at this time next thursday if you can join us :-) https://wiki.ubuntu.com/QATeam/Hackfest 19:30 <mhall119> vthompson: that would work 19:30 <balloons> vthompson, mhall119 yes we can check to ensure that it registers as playing, etc 19:31 <balloons> as far as checking if there is audio output there are tricks for that too :-) 19:31 <balloons> we'll start simple 19:31 <mhall119> so let's get work items and bugs to test the functionality that currently exists 19:31 <balloons> yep, I'll wait for your WI's mhall119 so things line up 19:31 <mhall119> then we'll just make it standard practice to add tests with any new features 19:32 <vthompson> Shuffle might be hard to test... but it might be worthwhile 19:32 <mhall119> ok, so I have 4 work items on the etherpad now 19:32 <mhall119> balloons: http://pad.ubuntu.com/X9yf5Jss8C 19:32 <balloons> etherpad hates me 19:32 <balloons> it keeps dc'ing 19:33 <mhall119> ok, we need to wrap up for the clock meeting 19:34 <mhall119> vthompson: do you have any concerns or blockers that popey or I can help with? 19:34 <vthompson> Sounds good 19:34 <vthompson> No, not at the moment. I think the main thing is working with Carlos... and we're already in touch. No facilitation needed. :) 19:35 <mhall119> ok, sounds good 19:35 <mhall119> #endmeeting