== Meeting information == * #ubuntu-touch-meeting: Docviewer meeting, 05 Mar at 15:00 — 15:38 UTC * Full logs at [[http://ubottu.com/meetingology/logs/ubuntu-touch-meeting/2015/ubuntu-touch-meeting.2015-03-05-15.00.log.html]] == Meeting summary == ''LINK:'' https://docs.google.com/document/d/1C4fXLJtugdjqYJrbDgooWBPLEbm7wE3zsHAaggpLpCo/edit?usp=sharing == Vote results == == Done items == * (none) == People present (lines said) == * popey (54) * sverzegnassi (26) * meetingology (3) == Full Log == 15:00 #startmeeting Docviewer meeting 15:00 Meeting started Thu Mar 5 15:00:14 2015 UTC. The chair is popey. Information about MeetBot at http://wiki.ubuntu.com/meetingology. 15:00 15:00 Available commands: action commands idea info link nick 15:00 How are you? 15:00 fine, thanks! 15:01 Thanks for the work yesterday to get docviewer polished for the store. 15:02 Do you have a link to the document you made for docviewer? 15:02 I can't find it 15:02 which one? do you mean the list of the things to do? 15:03 yes 15:04 (just a moment - gdrive is pretty slow on my netbook) 15:04 https://docs.google.com/document/d/1C4fXLJtugdjqYJrbDgooWBPLEbm7wE3zsHAaggpLpCo/edit?usp=sharing 15:05 thanks 15:05 np :-) 15:06 One of the simpler things in the list you have is "tap to show/hide header" 15:06 Could we do the same as browser does? Once you scroll it automatically disappears? 15:08 can't recall how it works. how it works to make it visible again? 15:08 you pull down 15:08 i.e. scroll the document 15:09 ok, it's similar to the default behaviour then 15:10 probably i will need to change something in the VerticalView C++ class, because I saw that clipping was managed in a different way 15:10 I think once you start scrolling through a book, you're less likely to need the header at all. But if you can reveal it by just scrolling down, that seems simple enough. 15:10 My idea was to make the header visible as the pdf viewer is shown. give a timer of 3 seconds and hide the header, then show/hide it on tap 15:10 It's a good idea. 15:11 But would also be good to be consistent with the other design patternss 15:11 -s 15:11 i saw there will be some changes in the design patterns (e.g. header overlay) 15:12 yeah. good point! 15:12 I will send a mail to design and cc you, to get the latest news. 15:12 That way we can make sure we don't implement something incorrectly. 15:13 ok, thank you! 15:14 i have anyway some update about the zoom. i found which was the issue that causes that strange behaviour (zoom is not centred on the gesture center) 15:14 ok, mail sent. 15:14 ah, excellent! 15:15 basically the Y position of the pages is not fixed 15:16 ahhh 15:17 it's based on the average height of the visible pages, so we need to update the zoom center any time the Y pos of the currentPage changes 15:17 understood. (I think) 15:17 that would be great to fix. 15:17 i will give a try lately this evening, i should be able to test through the double-tap-to-zoom 15:18 ooh, also great! 15:18 I have a couple of other topics.. 15:18 1) Becoming a default app.. 15:19 I'd like to start the conversation with the product manager today about whether they will consider docviewer as a default app. 15:19 I expect the answer is 'no' because the decisions on such things were done some time ago. 15:19 But my argument centres on the fact that docviewer has improved 1000% over the last few months, and is a super useful utility 15:20 We should expect some bug feedback. 15:20 But it's worth starting the conversation I think, even if the answer is 'no'. 15:23 +1 for becoming a default app. i feel like that there's still some delay in development, due to the 16 months docviewer was not maintained 15:23 but the delay with the other apps has been reduced a lot 15:23 yes 15:24 It has matured a lot in the last 3 months thanks to you. 15:24 So, I will start that conversation. 15:24 2) adding office viewer functionality 15:24 We have had this conversation a few times and it mostly comes down to licensing. 15:25 So I am going to re-start that conversation internally to see if it's okay for us to re-license docviewer to something compatible with the qt5 port of Caligra. 15:25 Do you think that's worthwhile? 15:25 Should we have a working prototype first, before we start that conversation? 15:27 there's are two things i'd like to understand first 15:27 1) ETA 15:27 2) how to integrate that huge source code (calligra) 15:27 Ok, so it's possible we become default on the nexus images, but not the bq one for now 15:28 seems reasonable to me 15:28 We don't have an ETA for office viewer functionality 15:29 for 2) I can ask if we can get some help from a canonical developer? 15:29 that would help a lot, since there are still many things i should work on 15:31 ok. 15:31 I will start that conversation then, and see if we can get some help. 15:31 it would be great! :D 15:32 One more thing. 15:33 I am planning a big blog post tomorrow to highlight the great work you and the other core apps developers have done recently 15:33 I will ask for people to test the docviewer app some more with all their PDFs. 15:33 and ask if anyone would like to get involved, as always. 15:34 sure, no problem 15:34 Ok, anything else? 15:35 yes, my new N5 is travelling through the EU. hopefully tomorrow i will get it (or on monday) 15:35 \o/ 15:36 I'll let you know how the conversations go. 15:36 ok, thank you! 15:36 Ok, shall we wrap up? 15:38 Ok, have a great weekend sverzegnassi ! 15:38 #endmeeting Generated by MeetBot 0.1.5 (http://wiki.ubuntu.com/meetingology)