GitLab

BUG: 387680

Discover qml plugin is included in the application now

Make it possible to selectively hide the transactions that are part of the
update

They get removed from the model through their status, they get added by
the class who requested them. Will allow for simpler code and more
semantics for the Transactions.

This way clicking anywhere else closes it, and it's not like it makes sense
to interact with the drawer anyway.

BUG: 378566

As we are a Kirigami application, this makes use of the Kirigami
icon item, which in turn allows us to use more types of icons,
and not just QIcons. This also allows for remote icons (once a
patch has been added to Kirigami to allow for this, and until
then it fails gracefully by simply failing to load any icon).

Differential Revision: https://phabricator.kde.org/D5769

Here model represents the delegate data

All seems to work fine, tests pass

Technically update is a transaction...

Let the transaction itself deal with it

It was instantiated in many places, it had an impact especially on
delegates.

It interferes with the theme uber-object in Plasma

Use a ColumnLayout and removed some workarounds

It's not really acceptable to need to set the sourceSize on all of the
elements with an icon inside.

Depending on org.kde.plasma.* components is problematic at the moment as
plasma-framework is not coinstallable (or kactivities for that matter) and
it has stopped a couple of people who were trying to contribute to the
project.
Furthermore, it was not a good idea to depend on it anyway. It wouldn't
integrate with the application look and feel settings and we had to juggle
to make it look acceptable.
Counter-side is that most of our components are provided in plasma
framework, so development will be needed to get all needed components in
shape either in Qt or KDeclarative.

REVIEW: 120265
CCMAIL: plasma-devel@kde.org

This way Plasma won't get the system tray icons but the system ones,
which is the ones we're looking for.

BUG: 331375

It works reasonably better and I don't know a reason not to. (I like
convincing commit messages to).

It had been broken since the transitions refactoring
Basically it restores the usage of the ListModel instead of using the
transaction model that does a different thing anyway.