19:06 <popey> #startmeeting Ubuntu RSS Reader App meeting
19:06 <meetingology> Meeting started Thu Jun 13 19:06:06 2013 UTC.  The chair is popey. Information about MeetBot at http://wiki.ubuntu.com/meetingology.
19:06 <meetingology> 
19:06 <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:06 <popey> blueprint: https://blueprints.launchpad.net/ubuntu-phone-commons/+spec/initial-rssreader-development
19:06 <popey> bugs: https://bugs.launchpad.net/ubuntu-rssreader-app/+bugs
19:06 <popey> reviews: https://code.launchpad.net/ubuntu-rssreader-app/+activereviews
19:06 <popey> burndown: http://status.ubuntu.com/coreapps-13.10/
19:06 <popey> so hows it going?
19:07 <dragly> I don't know exactly. Been busy with my exams, so I was hoping to hear from the others, hehe.
19:07 <dragly> But I think Joey and Roman has had some progress with the database.
19:07 <popey> ah
19:08 <dragly> And I spoke to Lisette from the design team two weeks ago, about the design which she posted some days later.
19:08 <popey> I think I was away when that was posted
19:08 <dragly> Let me see if I can find it, hang on.
19:08 <popey> http://design.canonical.com/2013/05/shorts-rss-reader-app/ that?
19:09 <dragly> Yes, but I think she followed it up with some more details.
19:11 <dragly> Here we go: https://lists.launchpad.net/ubuntu-touch-coreapps/msg00376.html
19:12 <dragly> Joey started some work on implementing it, but I think that is still unfinished.
19:13 <popey> ah yes, saw that one. thanks.
19:14 <dragly> Apart from that, I'm planning to sit down and try out the Autopilot testing framework to see if I can implement some of the tests listed in the bugs.
19:14 <popey> Oh that would be awesome!
19:15 <dragly> They will of course have to be changed later on, but I could try to get some ready for practice
19:15 <dragly> I think that's all from my end for now.
19:16 <popey> ok. I'll send a mail to the list, following up from Lisette and see if we can get an update from everyone that way ☻
19:16 <popey> do you have a device dragly ?
19:16 <mrqtros> Hi guys, sry I am late
19:17 <popey> heya
19:17 <popey> hows it going?
19:17 <mrqtros> my little summary - I am working hard on alpha
19:17 <mrqtros> all is ok, I will implement working version before 15 June
19:17 <dragly> popey: No, I don't
19:18 <dragly> mrqtros: Hi! Great to see you ;)
19:18 <mrqtros> But I will no use "shorts",because it's still concept and we need think about it.
19:18 <mrqtros> I focused on new database
19:18 <dragly> mrqtros: So you're basing it on a listview for now?
19:18 <mrqtros> <dragly>: me 2
19:18 <mrqtros> dragly: yep
19:19 <popey> if you want any on-device testing, let me know, I have a nexus 7 and nexus 4
19:19 <mrqtros> dragly: I think we need listview in final version too - a lot of users want clear and simple list
19:19 <dragly> mrqtros: Sounds like a good plan. It seems like Joey is working on the design. I'll try to experiment with that too.
19:19 <mrqtros> while "shorts" is very new concept, may be frustrated for a lot of users
19:20 <dragly> mrqtros: Having an option to show everything in lists shouldn't be too hard to maintain, so I think that's a good idea too.
19:21 <dragly> Although our main focus should probably be on making the main design as good as possible in the end.
19:21 <popey> yeah, a "simple" view and a "shorts" view on the same data?
19:21 <mrqtros> Yep!
19:21 <mrqtros> Just separate Tabs
19:21 <mrqtros> My crazy idea :D
19:21 <mrqtros> Or something like that :)
19:22 <mrqtros> We can't try new database and same time new concept
19:22 <dragly> popey: It's great that you are available to test things out. Is it okay for you to pull and test branches?
19:22 <mrqtros> First database on "trusted" lists, later "shorts"
19:23 <popey> sure dragly
19:23 <popey> just poke me on irc or mail me, no problem
19:24 <mrqtros> What I have done few days ago - ability to manage feeds with new database. And parsing articles.
19:24 <popey> is that landed in trunk?
19:25 <mrqtros> Tomorrow I will implement list of articles and operations with them :)
19:25 <popey> sweet!
19:25 <mrqtros> no no, only in my separate thread for a while
19:25 <popey> ok
19:26 <mrqtros> I will merge soon
19:27 <mrqtros> today is Thursday... That's mean I can develop whole Saturday, June 15 :)
19:27 <mrqtros> I think we will see alpha in time :)
19:27 <dragly> mrqtros: Great
19:28 <mrqtros> So, if you haven't any question to me, I'll afk )
19:28 <dragly> Sounds like you've got that part under control. Keep the good work up!
19:29 <mrqtros> Yeah! I hope someone will develop demo of "shorts" layout to discuss it with designers team. Because in near days I can't do this :)
19:30 <popey> yeah, lets talk more about that on the list perhaps
19:32 <popey> anything else?
19:33 <dragly> I think that's all.
19:33 <mrqtros> +1
19:33 <mrqtros> W8
19:33 <mrqtros> I have one question)
19:33 <popey> go for it
19:33 <mrqtros> Near to forget))) Guys in mailing list says, that we can use C++ when we want
19:34 <popey> we can, we prefer not to, but if you have to, you can
19:34 <popey> the file manager uses a c++ plugin for example
19:34 <mrqtros> But before they told us that we need to use QML where is possible
19:34 <popey> and there's a game or two which use C++
19:34 <popey> yes, QML is _preferred_
19:34 <mrqtros> Ok :)
19:34 <popey> if there's a good reason to use C++ then do it
19:34 <popey> e.g. performance
19:34 <mrqtros> Now I have clear vision how to do all RSS Reader work in QML
19:35 <popey> sweet!
19:35 <popey> rocking!
19:35 <mrqtros> So it was only question :)
19:35 <popey> ok, thanks guys!
19:35 <popey> #endmeeting