Commit message (Collapse) | Author | Age | |
---|---|---|---|
* | change wrapMode to WordWrap | Michael Bohlender | 2017-06-29 |
| | |||
* | do not hardcode fontPointsize | Michael Bohlender | 2017-06-29 |
| | |||
* | hide date on hover so the buttons can shine | Michael Bohlender | 2017-04-26 |
| | |||
* | Made the maillistview a focus scope | Christian Mollekopf | 2017-04-26 |
| | | | | and automatically select an index an aquiring focus | ||
* | introduce icon button, use it in maillistview | Michael Bohlender | 2017-04-26 |
| | |||
* | Keyboard focus for toolbar and folder list | Christian Mollekopf | 2017-04-25 |
| | |||
* | Show mail delegate buttons on hover | Christian Mollekopf | 2017-04-24 |
| | | | | Currently hides the date, so that will need fixing. | ||
* | Ported more actions to the fabric | Christian Mollekopf | 2017-04-24 |
| | |||
* | Use the fabric to wire up search | Christian Mollekopf | 2017-04-24 |
| | |||
* | Added the Fabric as an in application message bus | Christian Mollekopf | 2017-04-24 |
| | |||
* | remove toolbar and move enable the buttons in the mailListDelegate | Michael Bohlender | 2017-04-21 |
| | |||
* | add dummy button to maillist delegate | Michael Bohlender | 2017-04-21 |
| | |||
* | Fixed enabling of actions | Christian Mollekopf | 2017-04-20 |
| | |||
* | use kube.label in maillistview and center nothing-here message | Michael Bohlender | 2017-04-19 |
| | |||
* | remove filter bar, allow filter through the global search | Michael Bohlender | 2017-04-17 |
| | |||
* | 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. | ||
* | Only show relevant toolbuttons in the maillist view | Christian Mollekopf | 2017-04-13 |
| | |||
* | A single framework plugin | Christian Mollekopf | 2017-04-05 |
| | |||
* | One framework plugin to rule them all | Christian Mollekopf | 2017-04-04 |