12:02 #startmeeting Dekko meeting 12:02 Meeting started Thu Sep 24 12:02:55 2015 UTC. The chair is popey. Information about MeetBot at http://wiki.ubuntu.com/meetingology. 12:02 12:02 Available commands: action commands idea info link nick 12:02 How we doing? 12:03 full house! 12:03 Doing great thanks. You? 12:03 tickety boo 12:03 all good here, accosted Dan for his community interview this morning ;) 12:03 Aside from Xorg crashes which have caused me to lose data twice this week, but hey ho 12:03 i'm being bitten by the wrath of wily today. It's not playing fair 12:04 hah, same! 12:04 popey: ouch 12:05 so to kick things off how about a little video of progress on this thread view https://drive.google.com/file/d/0BwhxYaiA7z1qNmJxN18ycnlXR0U/view?usp=sharing 12:05 so yeah, I'll get your manual tests ovet to you once I stop my laptop going nuts 12:05 * popey looks 12:05 ooh, video! 12:05 davmor2: ^^ sorry it's taken so long :-) 12:06 wow, that’s some nice progress DanChapman 12:06 DanChapman: \o/ videos 12:06 So i have a few new questions at the bottom of https://dekkoproject.atlassian.net/wiki/pages/viewpage.action?pageId=11272199 which I have come across while implementing it 12:06 cool stuff DanChapman :) 12:06 are you mouse wheel scrolling there? 12:06 I’m making a note to get a ‘message thread’ icon for us to use (I’m guessing the one in there is a placeholder,, looks a lot like a contextual menu icon) 12:06 (because it looks great) 12:06 popey: yeah you can drag and scroll 12:07 ok 12:08 JMulholland: Yeah that just points out which message has children. It will change to showing the list of names in the top label once i get to it. 12:08 so no need for a ‘threaded messages’ icon then? 12:08 nope :-) 12:08 nice, cheers Dan! 12:10 I'm trying to figure out at what point should a message be marked read. It's no longer a case of once the message has been opened start the mark read action as it may still be off screen 12:10 if more than one message is unread 12:10 so should it be like once X percentage is visible then mark it or wait for it to fill the screen or at least all be visible 12:11 Gmail marks entire thread read if you open it (the thread)... 12:11 which seems the sensible thing to do 12:12 yeah 12:12 until a new mail comes in which is part of the thread 12:12 messages in a thread are largely regarded as a single ‘thing’ after all, so we should have the same behaviour for single messages and thread (i.e. once opened, marked as read) 12:13 That would make it simpler :-) So as soon as a thread is opened just mark them all 12:13 is it that straight forward? 12:13 (just want to be sure) 12:14 so if we mark a thread as read when opened, does that interfere with our ability to have previously read messages in that thread collapsed, and unread ones open? 12:14 if you switch to non-thread view, then it marks individual messages read as they are read, like a "traditional" (i.e. crap) mail client 12:15 but in threaded, yes, I think all messages in a thread go "read" once thread opened 12:15 No the expanded/collapsed is decided on instantiation the marking is done once that is complete 12:16 what should be the behaviour of newly arrived messages in a thread while reading it. Should it silently add it to the end and hope you find it or should it automatically focus it in the view? 12:17 I think silently adding, but reverting/marking the thread as unread (if pos) 12:17 that way there’s the additional cue of an unread message in thread when looking at/ going back to the inbox list 12:17 i dont think you should silently add 12:18 gmail notifies you there's new mail, but lets you choose whether to add it 12:18 gmail notifies you at the bottom 12:18 yeah 12:18 hm, i can see your point popey 12:18 as long as its not view stealing/ moving the users position in the thread when a new message arrives... 12:18 if I know the thread is 3 messages long, and close it, I won't have seen 4 and 5 which arrived after 12:18 that has the potential to be very anoying 12:19 if we can have some kind of animation which lets you know new stuff is below, then sure 12:19 but it needs to be obvious there's more content down there 12:19 or, you do as gmail does and don't show it 12:19 agreed, I’ll see if theres anything we can use to notify the user a new message has been added to a thread (not a notification though, that would be way too much) 12:20 sure 12:20 something nudging up from beneath maybe 12:20 * popey doesn't know :) 12:20 I was thinking something wiggling at the bottom 12:20 i’ll have a think, check the current planned components as well as have a word with visual-design 12:21 super thanks. 12:21 if we don’t have anything suitable we might just have to come up with something new :) 12:22 Next.... how should attachments be displayed as it's missing from the current designs? (this is also probably one for jouni?) 12:23 you mean, how do you display the fact that there _is_ an attachment (paperclip)? 12:23 or do you mean, how do we show the content? 12:23 both :-) 12:24 right, i did wire-frame that in the convergence spec, but I’ll ask visual-design to take a look to at my sketches and see if it still lines up with the ongoing visual style overhaul 12:26 ok then that would be great. 12:27 paperclips... paperclips everywhere 12:28 :-) 12:28 I'd imagine some file formats (the simple ones) to be renderable inside dekko (images, plain text, html)? 12:28 as long as the dont grow eyes and start saying things like ‘i looks like youre trying to read an email…’ 12:28 as a pop over? 12:28 ;-D 12:28 hah 12:28 "It looks like you're trying to distrupt the mobile phone industry..." 12:28 I would like to have something like that 12:28 ahaha 12:29 But any other file format should go -> content hub imo 12:29 it would be lovely to preview the obvious content types inline, I agree 12:29 oh, inline yeah, scroll down, and attachments underneath the body of the mail maybe? 12:29 pretty sure that's how it works on ios 12:29 when i get photos I just scroll past teh mail and the pics are all right there, preview size 12:30 that’d be nice, wouldnt ruin the reading flow in threads that way (for example) 12:30 + 12:30 1 12:34 Ok, anything else? 12:35 I don't think I have anything else right now. Priority is to get everything moved to uitk 1.3 atm 12:35 nothing at my end! 12:35 super! 12:35 Thanks chaps! 12:35 #endmeeting