This is the roadmap of Kube.
We intent to maintain the high level roadmap here, with all the details being managed in the Sink and Kube projects.
The tasks/milestones are roughly in chronological order (and of course subject to change).
This is the roadmap of Kube.
We intent to maintain the high level roadmap here, with all the details being managed in the Sink and Kube projects.
The tasks/milestones are roughly in chronological order (and of course subject to change).
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.)