| Commit message (Collapse) | Author | Age |
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Summary: Fixes T8697
Reviewers: cmollekopf
Reviewed By: cmollekopf
Tags: #kube
Maniphest Tasks: T8697
Differential Revision: https://phabricator.kde.org/D12875
|
|
|
|
|
| |
On windows event local components are apparently instantiated
asynchronously.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
This reverts commit 56020f4335c9ad0c1f0b65690ba264d0b6d2fa3f.
This turns the background of the login view transparent on mac os....
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
One problem with the current setting is that j/k is used for scrolling
in the conversation view, but for moving to the next mail in the
maillist view. To normalize this we could be using j/k for moving to the
next conversation instead, and n/p to go to the next/previous mail,
which is also what gmail does.
|
|
|
|
| |
This helps so we have aproximately uniform movements.
|
|
|
|
|
|
|
| |
If nothing else it works as an example how we have to differentiate
between shortcuts and keyboard navigation (one is global to some extent,
the other is only when having focus), and shows that we'll need some
place to consolidate that configuration.
|
|
|
|
| |
and forward the email via an extension api.
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
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
|
|
|
|
|
| |
The new messages available info is also irrelevant for the current
folder.
|
| |
|
|
|
|
|
| |
We listen for new mail notifications, and highlight the folder
accordingly.
|
| |
|
| |
|
|
|
|
| |
...via syntax highligher or search api.
|
|
|
|
| |
This fixes marking partially unread threads as read.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Summary:
Implement attachment-based forwarding.
Some notes:
- `loadAsDraft` was removed in favor of new enum `loadType` in QML, and callback based generic programming in C++
Reviewers: cmollekopf
Tags: #kube
Maniphest Tasks: T7024
Differential Revision: https://phabricator.kde.org/D10676
|
|
|
|
| |
We still failed to make the composer large enough initially.
|
| |
|
| |
|
| |
|
|
|
|
|
| |
Otherwise we end up scrolling up the editor if the content is larger
than the initial view.
|
|
|
|
|
|
|
| |
onCompleted is apparently not guaranteed to be called after all
properties have been set (reply broke).
The onSetup handler is now the standard handler for views to setup their
initial state.
|
|
|
|
| |
Marking individual messages as read didn't really feel all that useful.
|
| |
|
|
|
|
| |
is available
|
| |
|
| |
|
|
|
|
| |
E.g. if we have two kolabnow accounts.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
The extension itself is not really usable yet, but serves as a showcase.
|