== Meeting information == * #ubuntu-touch-meeting: Docviewer meeting, 31 Mar at 14:01 — 14:36 UTC * Full logs at [[http://ubottu.com/meetingology/logs/ubuntu-touch-meeting/2016/ubuntu-touch-meeting.2016-03-31-14.01.log.html]] == Meeting summary == == Vote results == == Done items == * (none) == People present (lines said) == * sverzegnassi (31) * popey (30) * JMulholland (11) * meetingology (3) == Full Log == 14:01 #startmeeting Docviewer meeting 14:01 Meeting started Thu Mar 31 14:01:27 2016 UTC. The chair is popey. Information about MeetBot at http://wiki.ubuntu.com/meetingology. 14:01 14:01 Available commands: action commands idea info link nick 14:01 JMulholland: a bit of flu, anyway yes, i had a good weekend! 14:01 hey popey! 14:01 o/ 14:01 How is the world of document viewing? 14:02 testing things right now at lesson! :) 14:02 heh 14:02 * popey will keep his voice down so nobody notices 14:03 anyway, we've slowed the workflow a bit down... i'm waiting for a new review of the UITK stuff 14:03 all the other things we've planned for the next release won't be ready in time for the ota-10 14:04 (pdf plugin and thumbnailer) 14:04 OTA 10 is due in a couple of weeks. I don't think there's pressure to land docviewer before then 14:05 yes... the new pdf viewer won't be ready for that time anyway... we need to fix performance first (tiled rendering slow on device) 14:06 okay 14:06 do you have any ideas on how to improve that? 14:08 well, at the moment I think we should get something that works like the current viewer. So, we shouldn't use tiled rendering but rendering the whole page at once 14:08 right 14:08 agreed 14:08 Also, we should review how the overlay is painted on the scene (i.e. overlay shows where hypertexts are on the page) 14:09 + we could cheat a bit on hi-res screens, but that is something we could do in future 14:10 ok 14:11 JMulholland: you back? 14:11 I am :) 14:11 :) 14:12 JMulholland: any news on https://bugs.launchpad.net/ubuntu-docviewer-app/+bug/1545142 ? 14:12 Hm, well I’ve assigned it to myself for starters now… :P 14:13 great, thank you! 14:14 It’s a tricky one, but I think we have three options that imediately come to mind, all with pro’s and cons: 14:14 we've been talking about a toast notification (android-style) some week ago IIRC 14:14 1: Educate on the double tap (which we can only really do once, people hate constant dialogues/reminders) 14:15 2: Use the bottom edge (which would be odd as it only becomes active when in FS mode, meaning we would probably need to educate again) 14:15 3: add a new UI element like a floating button at the top-left - where back/exit usually is (but this could get between the user and the content theyre trying to fullscreen...) 14:16 I’ve made a note, assigned the bug to myself and will have a think/ chat with the other designers 14:16 ok, great 14:17 popey: news from the user testing of dekko, terminal, etc.? 14:18 I expect to get the results tomorrow! 14:18 Our researcher is presenting her findings to the deisgn team tomorrow :D 14:18 as soon as I have them, you'll have them 14:19 asked almost in time... :P 14:19 looking forward for them 14:22 :) 14:22 me too! 14:22 promisses to be interesting :) 14:24 going off-topic a bit: terminal-app. I've started to complete the porting fromqwidget to qtquick 14:24 Ok.. 14:25 I've exposed 14 new properties to qml, but there are a lot of changes that could make it worth to start a new branch/series 14:26 Sounds like a good plan anyway. 14:26 Especially for the new UI stuff you keep teasing :) 14:27 yes... it would be much easier to handle all that changes on a separate branch (e.g. as done for docviewer) 14:27 I will wait for the current MPs to be approved, then shall we start a 'refactor/reboot bis' branch? 14:28 Yup! Need a better name than reboot 14:28 we keep using that 14:28 I'll let you think of a cool name :) 14:28 you're choosing the wrong person :D 14:29 ok, let's start it after ota-10! 14:29 okay :) 14:30 since we're in topic now, do you have news about the background processes 14:30 ? 14:31 Well, the only news we have is that there will be a small set of specific use cases dealt with first 14:31 I'll raise the topic again though, and see what progress has been made 14:31 (I doubt much) 14:31 I hope they will allow us to add that setting if the developer mode is enabled on device 14:33 yeah, that's what I'm pushing for 14:34 good, that would be the best solution we can get 14:34 yeah, agreed 14:35 anything else to discuss? 14:35 Nope 14:36 nothing here 14:36 ok. thanks popey, JMulholland :) 14:36 Thanks sverzegnassi ! 14:36 cheers sverzegnassi! 14:36 #endmeeting Generated by MeetBot 0.1.5 (http://wiki.ubuntu.com/meetingology)