Commit message (Collapse) | Author | Age | |
---|---|---|---|
* | Mailviewer | Christian Mollekopf | 2017-05-02 |
| | |||
* | Trigger a sync when opening the addressbook | Christian Mollekopf | 2017-05-01 |
| | |||
* | Don't load the imap resource as carddav resource. | Christian Mollekopf | 2017-05-01 |
| | |||
* | Function name cleanup | Christian Mollekopf | 2017-04-25 |
| | |||
* | Dropped the now unused action framework | Christian Mollekopf | 2017-04-24 |
| | |||
* | Another bunch of controllers gone | Christian Mollekopf | 2017-04-24 |
| | |||
* | Removed notification plugin | Christian Mollekopf | 2017-04-24 |
| | | | | ...which is replaced by the fabric | ||
* | Ported more actions to the fabric | Christian Mollekopf | 2017-04-24 |
| | |||
* | Added the Fabric as an in application message bus | Christian Mollekopf | 2017-04-24 |
| | |||
* | Fixed enabling of actions | Christian Mollekopf | 2017-04-20 |
| | |||
* | Hide trash from non-trash conversations. | Christian Mollekopf | 2017-04-16 |
| | | | | | ...and indicate in the conversation view if a mail has been sent or is a draft. | ||
* | Don't thread drafts and sent | Christian Mollekopf | 2017-04-16 |
| | | | | | | | | | | | | | | | | | | | | | | | | | | To do this we: * Expose from the model wether or not the model is threaded * Set the relevant properties from the model on the controller (so we can switch between aggregate and non-aggregate versions) * Keep the controller in the view it belongs to. While this works it highlights a couple of issues: * Controllers are view specific and should be kept within the view. * The actions we execute in the controller are closely related to the model. The model is essentially what the user sees, and therefore what he operatees on. * Sink should perhaps expose aggregates better. We have to pass around the values from the model because the model dispatches between aggregate and non-aggregate property depending on the threaded state. Similary the controller operates on the thread or not depending on the threaded state. Perhaps it would be more useful if sink actually returned the aggregate somehow, with the regular properties. That way the controller could use the regular properties from the entity it gets (which would simply either be the aggregate or non-aggregate depending on the executed query). If the aggregate already contains all matched ids, then we would also not have to execute an additional query to get the thread again, the modification would simply be applied to all ids originally returned. | ||
* | Ported away from webkit and to webengine | Christian Mollekopf | 2017-04-13 |
| | |||
* | Only show relevant toolbuttons in the maillist view | Christian Mollekopf | 2017-04-13 |
| | |||
* | CLeanup | Christian Mollekopf | 2017-04-12 |
| | |||
* | Move back to trash or drafts. | Christian Mollekopf | 2017-04-12 |
| | | | | | The move back to drafts should also trigger an edit of the mail, but that's not implemented yet. | ||
* | Cleanup | Christian Mollekopf | 2017-04-05 |
| | |||
* | Moved cpp code into src directory | Christian Mollekopf | 2017-04-05 |