summaryrefslogtreecommitdiffstats
path: root/components/package
Commit message (Collapse)AuthorAge
* port attachment delegate to kube themeMichael Bohlender2017-03-29
|
* port notifications to kube themeMichael Bohlender2017-03-29
|
* port outbox to kube themeMichael Bohlender2017-03-29
|
* use kube theme colors in people.qmlMichael Bohlender2017-03-29
|
* Show folder sync statusChristian Mollekopf2017-03-27
|
* Avoid scrolling to the end of the view if we don't have enough contentChristian Mollekopf2017-03-27
| | | | | | items Because then we would essentially overscroll up
* Use states for the account status iconChristian Mollekopf2017-03-27
|
* Update email statusChristian Mollekopf2017-03-26
|
* Show something if the data is not yet available.Christian Mollekopf2017-03-23
| | | | | | | | We're still missing: * For empty folders we have to differentiate between truly empty folder, and folders that have not been synchronized yet. Further an indicator when the fetch is in progress would be useful. * For mails we need to indicate when the mail is being fetched.
* Document why we're not setting the currentIndexChristian Mollekopf2017-03-23
|
* Made addressbook scrollableChristian Mollekopf2017-03-22
|
* Mark the currently viewed mail as read.Christian Mollekopf2017-03-22
| | | | | | | | | | | The listview is absolutely useless with non-uniform entries. We have to do or own tracking of the current index, we have to do our own scrolling, the flickable scrolling is horrible with a mouse, and even though caching all delegates somewhat improves the situation, it's still laggy every now and then. However, this now at least works somewhat correctly. But we'll really have to look for a new solution for this eventually.
* Filtering for maillistmodel and peoplemodelChristian Mollekopf2017-03-21
| | | | | | | | Works surprisingly well and is very useful for testing. The searchbar in the maillistmodel is a temporary solution as the global searchbar has some usability issues. E.g. how do we reset the search? As an intermediate step we could just hide the searchbar and make it visible by clicking on the search button.
* Disable the button we only use to show an iconChristian Mollekopf2017-03-20
|
* move positioning anchors out of Notificaion.qmlMichael Bohlender2017-03-20
|
* change notificaiton colorMichael Bohlender2017-03-20
|
* Support synchronizing individual accountsChristian Mollekopf2017-03-20
|
* notification.qml more coding styleMichael Bohlender2017-03-20
|
* make Notification.qml follow coding styleMichael Bohlender2017-03-20
|
* remove } to make it work againMichael Bohlender2017-03-19
|
* add firstname and lastname roles to peoplemodel, update ui to display themMichael Bohlender2017-03-19
|
* show email in person viewMichael Bohlender2017-03-19
|
* new people uiMichael Bohlender2017-03-19
|
* Use spacing instead of gridunitChristian Mollekopf2017-03-17
|
* A first notification popupChristian Mollekopf2017-03-16
|
* Simple peoplemodel for addressbookChristian Mollekopf2017-03-10
| | | | | Currently just queries for a flat list of contacts. Read-only.
* remove unessesary roles from outbox model. introduce status roleMichael Bohlender2017-03-09
|
* bring back outboxMichael Bohlender2017-03-09
|
* remove account on discardMichael Bohlender2017-03-07
|
* Avoid "Unable to assign...." errorsChristian Mollekopf2017-03-01
| | | | | | | | | | | i.e. "Unable to assign [undefined] to Sink::ApplicationDomain::Folder::Ptr" Because qml does not know how to assign a default-constructed value we have to use conditional bindings. The !! operator checks for availability of the property which then triggers the binding. I assume an alternative viable approach would be to expose all controller properties as QVariants only, in which case an assignment from null would work (it doesn't for Folder::Ptr).
* rename singlemailview to conversationviewMichael Bohlender2017-02-28
|
* Removed the old mailviewer.Christian Mollekopf2017-02-28
| | | | | That way I also don't try to edit outdated invisible components to fix bugs...
* Less noiseChristian Mollekopf2017-02-28
|
* Autoscroll to the end of the conversationChristian Mollekopf2017-02-24
|
* less debug outputChristian Mollekopf2017-02-23
|
* Resolved binding loopChristian Mollekopf2017-02-23
|
* Fixed component pathChristian Mollekopf2017-02-22
|
* Fixed kolabnow account setup page.Christian Mollekopf2017-02-22
| | | | | | | | | | The account plugin supplies the configuration UI, the application supplies the scaffolding. That way we ensure the application doens't contain any account specific code and account configurations are free to offer specialized UI's that work best for them. We're not currently using a standardized controller, but if we did those controllers would have to live with the plugin, not the framework or the components.
* better mark-as-read iconMichael Bohlender2017-02-21
|
* The singlemail view should operate on mails, the rest on threads.Christian Mollekopf2017-02-16
|
* Use currentItem to bind the current mailChristian Mollekopf2017-02-13
| | | | | | | The binding would occasionally result in temporary changes resulting in a lot of queries for the conversationview during a sync. currentItem works a lot better that way is also a generally cleaner solution.
* People.qml: Fix typoHeiko Becker2017-02-13
| | | | | | | | Summary: s/Krigami/Kirigami/ Reviewers: #kube Differential Revision: https://phabricator.kde.org/D4450
* better people layoutMichael Bohlender2017-02-03
|
* but name and avatar in same rowMichael Bohlender2017-02-03
|
* add initial contact controller and contact detail viewMichael Bohlender2017-02-02
|
* do not allow maillistdelegte to move back into the old positoon after a ↵Michael Bohlender2017-02-02
| | | | successful drag&drop move
* A more suitable scrolling behaviour for the mouse.Christian Mollekopf2017-02-01
|
* Implement move to folder per D&DChristian Mollekopf2017-01-25
| | | | | | | | | | | | | | | We have to trigger the drop explicitly in onReleased. Interestingly if we use "Drag.dragType: Drag.Automatic" then we don't need to explicitly call drop() and the drag and drop behaviour works as expected, but we end up no longer dragging the actual item from the listview, which is what we wanted to do (although we'll have to deal with the item reappering in the list only to then vanish from the actual move). It seems Drag.Automatic triggers a new style of drag that is now recommended but entirely undocumented, and we're doing some old-style/ backwardscompatible drag...
* make mouspointer the drag hot spotMichael Bohlender2017-01-25
|
* Merge branch 'dev/imapsync' into developChristian Mollekopf2017-01-24
|\
generated by cgit v1.2.3 (git 2.25.1) at 2025-05-20 14:43:11 +0000