To make a windows store app, as far as I understand, we would have to use the following:
http://doc.qt.io/qt-5/winrt-support.html

In T1826#87121, @cmollekopf wrote:

While that may be true I think we still have to fix the issue of focusing a single mail as it will be equally relevant for keyboard navigation/shortcuts.

In T1826#87116, @mbohlender wrote:

I think we can get away with marking the whole thread as unread once the user clicked on it and stayed on it for a short time.

I think we can get away with marking the whole thread as unread once the user clicked on it and stayed on it for a short time.

I have experimented with ways to determine the current mail, which can then be used to mark the mail as read and implemented a first version.
It's fairly difficult to achieve a system that works reliably though. The system as it currently is always has a single mail as current mail (and all other mails get slightly grayed out to indicate that). The current implementation only set's the current index based on the scrolling position, which becomes problematic when we have many small mails in the conversation view (especially at the beginning and the end):

Any new on this?

Absolutely!
You're more than welcome to work on anything that doesn't seem to be very active, just let us know via phabricator (as you did now), and claim the task.

I was wondering if it would be OK for me to take this on? (I've already got the read/unread button working properly in a local build, I still need to work on marking messages read when opening them.)

• No user interaction shall take longer than 100ms at any time (also not under load). Of course asynchronous operations may take longer, but should not block the user in any way.
• Memory usage: No process should use 100MB
• Disk usage: No more than twice the payload size (e.g. mime message in utf8 * 2). That includes secondary indexes and hopefully fulltext indexing (although that might be too ambitious initially)
• A resync check without anything to actually sync on localhost should not take any longer than 5s.

git://anongit.kde.org/scratch/sars/kate-windows.git

See git://anongit.kde.org/android-builder.git

api.kde.org/doc/kube and api.kde.org/doc/sink

A list of features we have to implement:

• automatically mark as read after having viewed a mail for some time
• Accessible maildir resource setup & configuration
• A possibility to save a mail as draft in the maildir
• Resume draft editing
• Sending of mails from the composer
• Deleting of mails