kube - A personal information and collaboration application

	Commit message (Collapse)	Author	Age
*	Always select the first index (INBOX) in the folderlist initially.	Christian Mollekopf	2018-04-17
\|
*	A reply shortcut	Christian Mollekopf	2018-04-09
\|
*	Added scrolling shortcuts	Christian Mollekopf	2018-04-09
\|
*	A help view to list shortcuts	Christian Mollekopf	2018-04-09
\|
*	Conversation view keyboard navigation	Christian Mollekopf	2018-04-06
\|
*	Got rid of controls1 where possible, and otherwise marked it learly	Christian Mollekopf	2018-04-04
\|
*	Fixed test.	Christian Mollekopf	2018-03-25
\| \| \| \|	What we should be doing is cleaning up in between the tests.
*	An extension mechanism load qml files at generic extension points.	Christian Mollekopf	2018-03-23
\| \| \| \|	and forward the email via an extension api.
*	Automatic key import / export + Expected monad	Rémi Nicole	2018-03-09
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	Summary: There are many things going on here (perhaps a bit much for a single patch): - When an attachment is of mime type "application/pgp-keys", a button is added to import the key to GPG - When sending a mail and crypto is enabled (encryption, signing or both), the public key of the first private key found is sent as an un-encrypted attachment (T6994) - The `mailcrypto.{h,cpp}` was, for the most part, rewritten - Introduction of the expected monad, inspired by what was proposed for C++ [here](https://isocpp.org/files/papers/n4015.pdf), but not at all a strict implementation of this specification. We may want to add some more features of this standard later. The rationale for some of the choices: - I found mailcrypto a bit hard to edit to add new features, and a great part was commented code to prepare for the support the SMIME crypto format, which would (in my current knowledge) not be used for sending emails. - One thing I found that may be missing in the code base was a standardized way of handling errors in C++ code. Since exceptions are disabled I think that the functional way is the way to go. After some research I found the Expected monad / tagged union / sum type, which seemed to suit the problem particularly well. In the long run, I hope we would move the entire code base to use `Expected` to indicate if a function might fail. Of course every choice made here is to be considered as a proposition for doing things / RFC, critics wholeheartedly accepted. Reviewers: cmollekopf Tags: #kube Maniphest Tasks: T6994, T8147, T6995 Differential Revision: https://phabricator.kde.org/D11158
*	Test move to trash	Christian Mollekopf	2018-03-08
\|
*	Search in conversationview	Christian Mollekopf	2018-02-23
\| \| \| \|	...via syntax highligher or search api.
*	Demonstrate reflow problems	Christian Mollekopf	2018-02-23
\| \| \| \| \| \| \| \| \|	...and cleanup the sizes of the text/html part a bit. Html content with a <pre> tag, such as inserted by an apple mail reply, is not reflowed in the TextEdit (it is in the WebEngineView). And that causes the text edit to run off the side of the conversation view.
*	Use the new changes regarding aggregated properties.	Christian Mollekopf	2018-02-22
\| \| \| \|	This fixes marking partially unread threads as read.
*	More utf8 chars	Christian Mollekopf	2018-02-14
\|
*	Test utf-8 rendering	Christian Mollekopf	2018-02-13
\| \| \| \|	the snowflake doesn't work
*	A basic but working searchview	Christian Mollekopf	2018-02-12
\|
*	More conversationview testing	Christian Mollekopf	2018-01-11
\|
*	Create thread for conversationview	Christian Mollekopf	2018-01-11
\|
*	Inherit folder id (we can't hardcode it)	Christian Mollekopf	2018-01-10
\|
*	Run views with a test dataset using TestStore.	Christian Mollekopf	2018-01-10
\| \| \| \| \|	This allows us to start the view using qmlscene with a testdata set that is created in a test datastore (isolated from the regular data).
*	Install composer/converations/people as separate views and load them	Christian Mollekopf	2018-01-10
	dynamically.