12:05 #startmeeting Dekko 12:05 Meeting started Thu Sep 17 12:05:46 2015 UTC. The chair is popey. Information about MeetBot at http://wiki.ubuntu.com/meetingology. 12:05 12:05 Available commands: action commands idea info link nick 12:05 Right, I’ll go ahead and get something set up for Tuesday then, thanks! 12:06 :-) 12:07 I have a couple of questions i'd like to go over with the thread view. see https://dekkoproject.atlassian.net/wiki/pages/viewpage.action?pageId=11272199 and right down the bottom. Saves me typing it all here :-) 12:08 * JMulholland has a read 12:09 I do like the way mailbox does it. 12:09 but does that lend itself better to longer mails? 12:09 reading a bunch of mails in the thread might get tedious going forwards and back? 12:10 Well you still see all the content in the thread. Just if you want to zoom, copy text etc you need it to be full screen 12:12 ah okay 12:13 There's a couple of other android apps that when you try to zoom it changes to a fullscreen view. Can't remember which they were now. So it's not an out of the ordinary solution 12:13 The ‘step into specific message/ step back to thread view’ UX cost doesn’t seem too high to me, given the benefits - Seems a workable compromise given the tech-issue you’ve hit 12:13 (or so it seems to me) 12:13 hey 12:14 hey jounih_ 12:14 how are you dan 12:14 sorry im a bit late 12:14 I'm great thanks. Yourself? 12:14 lo jouni 12:14 not too shabby thanks :) 12:14 hey james 12:14 i was wondering, how can we get the latest build to test on our xps 13 laptop? 12:15 DanChapman - should have mentioned, faenil sends his apologies but can’t attend today 12:15 jounih_: you can get it from the core-apps ppa or from my jenkins builds. Although that's not available until later today 12:15 yeah no rush 12:15 nice 12:15 next week is fine 12:16 would you be able to email me and james instructions? 12:16 Sure thing :-) 12:16 thanks :) 12:16 brilliant, thanks 12:16 jounih_: we were just discussing the thread view I have a couple of questions at the bottom of this page https://dekkoproject.atlassian.net/wiki/pages/viewpage.action?pageId=11272199 12:17 ah the thread view 12:17 ok 12:17 yeah i think we touched on this the last time 12:17 i need to update the design 12:18 to show a dropdown menu selection for reply/reply all/forward 12:18 in both the thread view and compose view 12:19 JMulholland: I also like what mailbox does with being able to navigate through the thread from the full message view so you wouldn't need to step back out to go to the next in thread 12:19 let me read the whole writeup 12:21 how do you do that navigation dan? can you scroll outside the compose view to see the other messages in the thread? 12:21 DanChapman Using the up/down carets I assume? 12:22 My previous comment on this topc, FYI jounih_ : 12:22 JMulholland: The ‘step into specific message/ step back to thread view’ UX cost doesn’t seem too high to me, given the benefits - Seems a workable compromise given the tech-issue you’ve hit 12:23 isn’t the design we have now the same as mailbox? (didn’t know dropbox have their own email client btw) 12:23 jounih_, not sure I understand. The navigation to the full message view containing a single message? 12:24 ie. read messages in a thread -> reply/edit in full screen mode 12:24 and back button to get back to the thread 12:24 shall we hangout :) 12:25 jounih_: the issue is touch interaction with the messages in the thread view. There's limitations with not being able to click links, zoom and copy text. 12:26 So what i'm suggesting is to interact in that way the message needs to be made full screen so that oxide can receive all our touch inputs 12:26 ah because the qml steals the events? 12:26 yeah :-) 12:26 jounih_ the design is fairly close, but based on Dans findings regarding an oxide webview inside a qml flickable, we’ll likely need a little more thought/ finesing 12:26 right 12:26 would you be able to pass the events through from qml to oxide 12:28 I did try but oxide doesn't seem to use Qt for it's input events so I couldn't get the events to propagate 12:29 I had hoped to pick faenils brain on that one. I'll try grab him later today/tomorrow 12:30 olivier would be a good one too 12:30 he is the main dev for oxide 12:30 you know him? 12:31 is that osomon? 12:31 yes 12:31 ok i'll do that as well 12:31 cool 12:31 yeah i don’t know if it’s possible to bridge the events 12:32 but olivier might have come across the same in the browser before 12:32 with things like copy/paste which uses our SDK text selection on top of webview 12:32 not currently they don’t jounih_ ;) 12:32 but that’s probably better addressed by Oli 12:33 it’s pretty broken but i remember seeing the QML text selection handles there 12:33 if we can solve this by propagating the events then we wouldn’t need to adjust the design 12:33 in terms of design for the thread 12:34 do you like the Gmail style threading i’ve done, or the more card like design on some of these others? 12:35 They both have their merits I suppose 12:35 I like the current gmail style of it. And yes if we can figure out the event propagation then the design won't need adjusting 12:36 coolio 12:36 Gmail style is perhaps ‘tidier’, but the card-like approach would be clearer if navigating to a different view were necessary for interacting with message bodies (copy, open URL, etc) 12:36 I’ll send you a design with the dropdown menu for reply/all/forward 12:36 anything else guys? 12:37 look forward to testing the thing on real hardware :) 12:37 Super, thanks! 12:37 I don't have anything else right now. 12:37 Awesome 12:37 nothing from me either, thanks chaps! :) 12:37 alright, thanks dan & james! 12:37 Thanks guys! 12:38 have a good weekend! 12:38 Thanks guys 12:38 #endmeeting