== Meeting information == * #ubuntu-touch-meeting: Docviewer meeting, 28 May at 14:00 — 14:32 UTC * Full logs at [[http://ubottu.com/meetingology/logs/ubuntu-touch-meeting/2015/ubuntu-touch-meeting.2015-05-28-14.00.log.html]] == Meeting summary == == Vote results == == Done items == * (none) == People present (lines said) == * popey (23) * sverzegnassi (17) * meetingology (3) * kenvandine (2) == Full Log == 14:00 #startmeeting Docviewer meeting 14:00 Meeting started Thu May 28 14:00:37 2015 UTC. The chair is popey. Information about MeetBot at http://wiki.ubuntu.com/meetingology. 14:00 14:00 Available commands: action commands idea info link nick 14:00 How are you sverzegnassi ? 14:01 I've been much busy last week, didn't do much :/ 14:01 Just did something on zoom pinch gesture. I really hope to finish it next week 14:03 ok. 14:03 I uploaded latest version to the store as you probably saw. 14:03 Yes, I saw! Glad to hear positive feedback! :D 14:03 Yeah. 14:04 will you also have chance to look at https://code.launchpad.net/~verzegnassi-stefano/ubuntu-docviewer-app/fix-1418648/+merge/256354 ? 14:05 no, sorry 14:06 ok 14:06 I don't have much to discuss this week, I'd just like to start some discussion on some future plans (libreoffice stuff and content hub) 14:08 ok, sure. 14:08 I poked our libreoffice guy to get a status update for his small test build 14:09 good! so does we already a test build? 14:09 does we have* 14:10 no reply yet 14:12 ok, the content-hub question is related to the migration from C++ APIs to QML ones 14:14 ok. 14:14 Do you have a specific question or issue around that? 14:14 The general advice from kenvandine last time we discussed this was "don't use the C++ API", right? 14:15 popey, right 14:15 qml only 14:15 Yes, but I'm not sure about what to do with all the other C++ code. 14:15 I mean, is it worth to keep the entry point in C++, so we don't have to re-write the autopilot stuff, etc? 14:16 What's the effect of removing it? What needs re-creating for autopilot? 14:18 We should handle the command line arguments from QML (maybe re-using the current code in another plugin), probably we should manage the full-screen code in a different way, and the tests may need to be updated to use "qmlscene [qml_file_path]" as path to launch 14:20 Hmm, that's unfortunate that we have to re-do all that. 14:20 Better than breaking when the C++ API for content hub changes though. 14:22 yeah, before using all that C++ code, there was an issue with the app pages management (basically, docviewer used to push a page in the stack, but if a signal was emitted from content-hub, it used to clean the whole stack and push another page again) 14:23 since we have a document page now, we won't have that issue again, so I'm thinking to move only content-hub stuff to qml 14:24 Ok 14:24 that makes sense. 14:26 ok, I'll start the branch during the weekend then 14:27 I'm building a new PC, hopefully tomorrow I'll have the last missing component, so I should be fully operative next week :D 14:29 oooh! 14:30 Great. Anything else to discuss? 14:30 No, that's all. Sorry again for being not active this week 14:30 No worries. It was great to get an update in the store. 14:32 yes, it was. have a nice weekend popey! 14:32 you too! 14:32 #endmeeting Generated by MeetBot 0.1.5 (http://wiki.ubuntu.com/meetingology)