| Commit message (Collapse) | Author | Age | |
|---|---|---|---|
| * | Reset the flickable speed to it's original | Christian Mollekopf | 2017-06-11 |
| | | | | | | | | It's still not very usable, but we'll have to find a solution that is applicable everywhere and perhaps it is just a hardware problem. Increasing the deceleration just makes scrolling very slow, so that's no solution either. | ||
| * | Use Kube.Units | Christian Mollekopf | 2017-05-24 |
| | | |||
| * | A simple debug view | Christian Mollekopf | 2017-05-23 |
| | | |||
| * | All of the MailViewer in one place | Christian Mollekopf | 2017-05-23 |
| | | |||
| * | Don't try to mark null mails as read | Christian Mollekopf | 2017-05-03 |
| | | |||
| * | Removed controller in conversation view | Christian Mollekopf | 2017-04-24 |
| | | |||
| * | 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 |
| | | |||
| * | use Kube.Label in Conversationview | Michael Bohlender | 2017-04-19 |
| | | |||
| * | 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. | ||
| * | Allow setting the current item via mouse | Christian Mollekopf | 2017-04-13 |
| | | |||
| * | add id for goDown button | Michael Bohlender | 2017-04-06 |
| | | |||
| * | remove obsolete code | Michael Bohlender | 2017-04-06 |
| | | |||
| * | A single framework plugin | Christian Mollekopf | 2017-04-05 |
| | | |||
| * | One framework plugin to rule them all | Christian Mollekopf | 2017-04-04 |
 |
index : kube | |
| A personal information and collaboration application |
| summaryrefslogtreecommitdiffstats |