21:03:07 <mhall119> #startmeeting File Manager App
21:03:07 <meetingology> Meeting started Thu Mar 28 21:03:07 2013 UTC.  The chair is mhall119. Information about MeetBot at http://wiki.ubuntu.com/meetingology.
21:03:07 <meetingology> 
21:03:07 <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
21:03:36 <mhall119> so to get started, I wanted to let everybody know that I made some changes to the blueprint
21:03:56 <mhall119> all of the core apps blueprints have been moved into the ubuntu-phone-commons app, to make things easier to track for popey and I
21:04:12 <ajalkane> Aye, I saw the e-mail
21:04:18 <mhall119> we also now have milestones for every month between now and the 13.10 release, to match the monthly planning cycle that's been introduced into Ubuntu itself
21:04:33 <mhall119> so month-0 is April, and it goes all the way to month-6 for October
21:04:42 <mhall119> what used to be called alpha-1 milestone is now month-1
21:07:26 <mhall119> so I've moved all of the DONE work items to month-0, and anything we think will be finished in April we should move there too
21:07:50 <mhall119> everything else that was marked for alpha-1 I've left in the month-1 milestone
21:08:12 <mhall119> and things that we know will take longer, such as getting a final icon set, are under just "Work items"
21:08:18 <mhall119> any questions on this setup?
21:09:17 <mhall119> oh, I should have mentioned, popey couldn't be here for this meeting, so I'm filling in for him
21:09:20 <ajalkane> I'd say no... I guess it's more what functions to prioritize for next sprint.
21:09:40 <ajalkane> But if there's no objections I'd go for easiest to implement first
21:09:48 <mhall119> ajalkane: yeah, it also let's us break a big list of work items into smaller, more digestible chunks of work
21:10:16 <mhall119> #topic progress update
21:10:24 <ajalkane> That's always good...
21:10:30 <mhall119> ok, so can you guys catch me up on what's been done since the last meeting
21:10:32 <mhall119> ?
21:10:45 <mhall119> I got a chance to play with the app on my Nexus 7, btw, and it's really nice to have
21:11:09 <ajalkane> I haven't done much, just small refinements to the UI. Scrollbar, some other minor stuff maybe
21:11:32 <CarlosMazieri> I pushed a new version of the model, I think it has a good shape
21:11:35 <ajalkane> Merging stuff upstream
21:12:30 <mhall119> I noticed that the ability to go up a directory wasn't working, is that just not implemented yet, or a bug?
21:12:31 <ajalkane> CarlosMazieri: does it have my changes and yours merged yet? Ie. usable with the UI?
21:12:47 <ajalkane> mhall119: It should work. So bug if so
21:12:58 <ajalkane> But if you're using Timo's deb package version then it's probably not up to date
21:13:24 <ajalkane> I am not at all sure of the correct way to update his repo
21:13:28 <mhall119> I'm running from trunk of the ubuntu-filemanager-app, rev 15, but using the package in the PPA for the nemo plugin
21:13:46 <CarlosMazieri> ajalkane:  which your changes?
21:13:49 <ajalkane> Yeah that probably don't work as it doesn't have the latest version of the plugin
21:14:24 <ajalkane> CarlosMazieri: from this branch https://code.launchpad.net/~ajalkane/ubuntu-filemanager-app/qml-folderlistmodel
21:14:25 <mhall119> ok, so the plugin package should be built whenever it's branch is updated
21:14:30 <CarlosMazieri> I think that the trunk does not have any of our changes
21:14:37 <mhall119> is the plugin branch newer than the plugin package?
21:15:02 <ajalkane> mhall119: it is newer... but the deb build branch is different
21:15:16 <ajalkane> it's basically, if I understood correctly, a snapshot of upstream with some .patch files to apply our changes
21:15:21 <mhall119> ok, do you guys have access to update the deb build branch?
21:15:29 <mhall119> oh, I see
21:15:42 <ajalkane> Even if I had access I would not know the correct procedure to update it
21:15:48 <CarlosMazieri> I do not think so
21:15:56 <ajalkane> There's probably some document somewhere
21:16:01 <mhall119> ok, I'll check with timo to see how we can automate this, if we can automate this
21:16:28 <ajalkane> It seems smart - use upstream sources, and our patches. Most of our patches should go upstream so patches go away
21:16:40 <ajalkane> But the exact procedure of building the patches etc. is not familiar to me
21:17:11 <ajalkane> I'm sure this is just common Ubuntu/debian stuff but I haven't done it before
21:17:15 <mhall119> if we can't automate it, maybe we can find somebody to teach you guys how to update it
21:19:08 <ajalkane> That's good. It's just procedural things. I could do a good guess, but I'm wary of using much time on it as I'm sure there's good procedures already in place
21:19:59 <mhall119> agreed, I'll do my best to find a low-work solution
21:20:35 <mhall119> so I was just talking to seb128 about how to open files in external apps
21:20:51 <mhall119> and it seems we should assume it'll be the same as the desktop unless and until we hear otherwise
21:20:57 <mhall119> so calling xdg-open with the file to be opened
21:21:26 <ajalkane> Ok good. With quick tests I think that's what the UI does now.
21:21:55 <mhall119> also, popey and spoke with the design team this morning about icons
21:22:27 <seb128> xdg-open or native api, the logic should be the same
21:22:38 <mhall119> and basically they are going to provide artwork that we need, but they have a lot of other things to deliver to, so we should use whatever we can for now, until the new artwork is available
21:23:00 <seb128> the mimetype/handle is a freedesktop spec and GNOME/KDE/XFCE/... respect it
21:23:01 <ajalkane> seb128: I'm using QML's Qt.openExternalUrl, I think it's basically xdg-open
21:23:08 <seb128> k
21:23:15 <seb128> that should work just fine
21:23:16 <mhall119> cool, that should work then
21:23:19 <mhall119> heh
21:23:32 <ajalkane> mhall119: that's good news about icons...
21:23:46 <mhall119> #topic next steps
21:24:13 <ajalkane> relating to icons, a bit more advanced, but do we want thumbnails to be generated to for example pictures or videos etc... I know Nemo has a thumbnail module but I don't know it's capabilities.
21:24:42 <mhall119> hmmm, would that be too resource consuming for mobile devices?
21:25:50 <ajalkane> Depends on caching and if there's some background process doing it automatically. Personally I've never needed or wanted such.
21:26:21 <mhall119> let's put that off for a later date
21:27:26 <mhall119> is there anything currently blocking your work, or that you need popey or I too look into for you?
21:27:55 <CarlosMazieri> No, only the upstream stuff
21:28:14 <mhall119> ok, I took a work item to get that done
21:28:26 <CarlosMazieri> OK, thanks
21:28:29 <mhall119> #action mhall119 to look into automating new builds of the nemo plugin
21:28:29 * meetingology mhall119 to look into automating new builds of the nemo plugin
21:28:48 <mhall119> anything else before we wrap up?
21:28:58 <CarlosMazieri> No
21:29:08 <ajalkane> Me neither
21:29:20 <mhall119> awesome, thanks guys!
21:29:23 <mhall119> #endmeeting