Kirigamifying the Summary
Open, Needs TriagePublic

Description

This task is intended as a redesign of the Kontact summary using Kirigami and Qml. Here are some non-functional screenshots of a prototype.

With material design:

With QT_QUICK_CONTROLS_STYLE=”org.kde.desktop” :

For the moment the prototype is only qml with boilerpate. I'm using some qml elements from Itinerary. I pushed the prototype to https://invent.kde.org/carlschwan/kontact-experience.

Related Objects

StatusAssignedTask
OpenNone
OpenNone
ognarb created this task.May 7 2019, 2:07 PM

@mlaurent what do you think? I quite like the idea of using Kirigami to display the Summary, it looks pretty good and cleaner than the overcrowded HTML-based summary we have now .

Hi,
Indeed it's a good idea to improve summary page, but with kirigami we add a new dependancy (only for summary)
How it will work in other desktop ? kirigami under other environment (gnome xfce etc.)
In current summary we can reorganize items, it will be still possible in kirigami ?

At the moment we have a lot of information with a tooltip as calendar/duration/reminders etc. How we will implement it ?

dvratil added a comment.EditedMay 9 2019, 7:31 AM

Kirigami is a KDE Framework and we already depend on many of them, so I don't see a problem there. Adding a dependency on one more fairly small Framework is harmless IMO.

Kirigami has a default style that would be used outside of Plasma, it's the same as running a QWidget-based application under another environment without Breeze.

Tooltips in QML are not a problem, but I think currently they are used in the Summary mostly because there's no other way to do this in HTML (without tons of JavaScript). With QML the Summary can be made much more interactive and useful and provide even more information than we can just through tooltips.

vkrause added a subscriber: vkrause.May 9 2019, 8:06 AM

Right, given the choice of technologies of HTML/QTextBrowser (very constraint), HTML/WebEngine (heavy, hard to maintain JS), custom QPainter code (inflexible and hard to maintain) or Kirigami/QQC2/QML the latter looks like the most convincing option to me if I had to implement the summary view today. And QML does not automatically imply "mobile UI" or "alien UI" if you look at systemsettings for example, I need GammaRay to tell widgets and QML parts apart there. So I wouldn't discard anything just based on technology here, but focus on what features we actually want in the summary view.

I hardly ever use the summary view, as the current layout doesn't really scale ("Upcoming events" is 3 pages long and needs scrolling here, while the other elements have only a handful of entries), and the entries are just links, I can't even close tasks in there. QML would easily enable more interactivity I think.

The new mail summary is even more constraint, it just shows me unread message in a folder (which for me is always large numbers and thus not providing much information), seeing e.g. the subjects and having a delete action would be a big improvement IMHO. And I think this is where "mobile" came in: The summary view could cover a similar usecase as a mobile phone client: e.g. focus primarily on screening (and deleting) emails, while everything else is done in the full KMail (which would actually be a feature increase over the current summary view). That's at least how I use K9 Mail on the phone vs. KMail on the desktop.

ognarb added a comment.May 9 2019, 8:57 AM

Hi,
Indeed it's a good idea to improve summary page, but with kirigami we add a new dependancy (only for summary)
How it will work in other desktop ? kirigami under other environment (gnome xfce etc.)

Kirigami also works in another desktop environment.

In current summary we can reorganize items, it will be still possible in kirigami ?

I didn't know this feature was available, but QML support Drag and Drop (see for example: https://doc.qt.io/qt-5/qtquick-draganddrop-example.html).

I will try this weekend to extend the prototype with more interactive elements.