13:03 #startmeeting Trojita meeting 13:03 Meeting started Fri Jul 11 13:03:55 2014 UTC. The chair is popey. Information about MeetBot at http://wiki.ubuntu.com/meetingology. 13:03 13:03 Available commands: action commands idea info link nick 13:03 How are you boren DanChapman ? 13:04 popey, just done a blog post http://blog.dpniel.com/ should aggregrate to planet in a little while i presume 13:04 I'm good thanks. making the most of the quiet before summer holidays. Oh yeah yours are already off aren't they? 13:04 :-/ 13:05 yeah, today is their first day off 13:05 nice blog post! 13:07 yeah i tried my best to make it clear what Dekko is, and that Trojita will replace it 13:07 Great, yes, that's clear. 13:09 DanChapman, Is there anything I can help with dekko? 13:09 * popey shares the blog about a bit 13:11 Well, technically we should be helping with trojita, but testing that in dekko, right? 13:12 right. 13:13 yes that's right. So I think the displaying of multipart messages is a big part. Minus the html part issues, how can we display all other message parts/attachments? 13:15 I'm inclined to agree. 13:15 Also handling of attachments say images or word documents how do we handle those? where do they go? do they go through contenthub? 13:17 DanChapman: yes, they would go through content hub 13:17 images you could display inline ifyou wanted 13:18 The desktop gui uses a widget factory where it iterates over the message parts and builds a component base on it's mime type. Looking at it i don't see how we can use that in anyway, except using some kind of model that contains paths to qml components and use the model in a repeater and use the path from the model to create the delegate. That might not even work actually 13:20 the different parts are things like text, html, and images, right? 13:20 mhall119, ok cool, i'll look more at content hub then. I think we can only display images inline if the Content disposition in the header states it is inline 13:21 mhall119: and signing blobs 13:21 right, and signing 13:21 DanChapman: so why couldn't we just convert those parts into QML components in the same way the desktop gui does? 13:24 mhall119, do you mean create qml components in c++? The desktop gui basically iterates over the message and creates a specific tab widget for each part and adds it to a tab view 13:25 could we do something similar, only instead of tabs using a different way of showing/hiding parts? 13:28 hmm looking the onemessagemodel it has the attachments model, which is basically a flattened model of the whole message. It contains paths to parts and mime/types that looks like it should do 13:29 DanChapman: for mail box switching you can default to inbox and have the drop down draw on the left for other folders similar to reminders app 13:30 according to the rfc specs the higher quality mime-type should always be displayed unless opted out by the user. So text/html over text/plain for example. So do we basically stack the parts on top of each other and only show the highest quality ( if it's a viewable message part and not a download) 13:32 DanChapman: that would work 13:32 makes sense, didnt realise the rfc spec detailed that. 13:34 * mhall119 suspects email related RFC detail every possible scenario and several impossible ones 13:36 heh 13:36 mhall119, popey yes the specs are very detailed on what an email client MUST (they like using uppercase must's) do 13:37 davmor2, that's an interesting idea. boren what do you think to defaulting to inbox? 13:37 Ok, so is that something you're planning on working on, or are there other features that are higher priority? 13:37 boren ^^ 13:37 i'm still doing smtp stuff atm 13:38 DanChapman: I noticed what I assume is a bug the other day 13:38 DanChapman, I think that is a cool feature. The inbox get reset a lot. 13:39 when you highlight text to reply, the reply message will have only the highlighted bit, but then when you focus on the message text field, all of the original message is added back (I assume because the highlight on the original goes away when it loses focus) 13:39 DanChapman: so it looks like this http://blog.dpniel.com/?attachment_id=43 infact but with a nice list of folders not sure if that list is browsable though 13:40 scrollable sorry not browsable 13:40 DanChapman: what about sub-folders? 13:42 mhall119, yes so my idea was that if you only want to reply to a specific part of a message you just have to highlight it rather than deleting all the parts in the composer. But if nothing is selected then it should display the whole original message 13:43 DanChapman: right, which I think is brilliant, but it seems to be reacting to the lost highlight after opening the reply, so I can't in practive quote just the highlighted part 13:43 * DanChapman tries 13:46 mhall119, your right it's resetting on lost focus. 13:47 it just need a conditional, if the composer is opened and i've highlighted then don't reset it 13:47 btw, our GMail webapp broke in a recent build, dekko has been my saving grace :) 13:47 without it, I wouldn't have email on my phone 13:47 heh 13:48 davmor2, yeah i'm not sure how easy that would be using the tray popover especially with nested folders,. i wish there was a qml treeview type component. Now that would be cool 13:49 UbuntuListView has an expandable delegate type that might work 13:50 you'd be nesting listviews in listviews though 13:51 alternately you could flatten the tree and use some Javascript to show/hide items that are technically nested 13:51 wouldn't that be problematic with two folders of the same name? 13:52 popey: you wouldn't have two folders of the same name at the same level 13:52 so I wouldn't think so 13:52 oh, i thought you were talking about taking subfolders from other folders and flattening them 13:54 popey: only in the model, they would be displayed nested 13:56 Hmm yes that is an idea, I'm sure the is a qml data model component somewhere for displaying nested abstractitemmodel so you can step down the model in qml. I wonder if we could use that and the listview 13:57 guys i've got to shoot off, got to get my boy from school can't believe an hours gone 13:57 for my reddit app I simulated comment threads this way, they're a flat list in the data model, but I kept the nesting level data so I could indent them to make it look like a tree 13:57 DanChapman: no problem 13:58 and thanks again, to you and boren 13:58 mhall119, ahh ok i'll ping you about that when i get back :-D 13:58 See you DanChapman. 13:58 Thanks DanChapman & boren 13:58 Shall we wrap ? 13:58 hah, just noticed the topic 13:58 i think it's broken 13:59 Sure 13:59 thanks guys speak to you later o/ boren just go wild and implement something :-D 13:59 o/ 13:59 #endmeeting