hein added a comment.
I totally get your argument, but this two-steps-forward-one-step-back code is
still so ugly - we need some sort of new approach to composability here. It's
more work but may lead us into a better direction long-term.
QML like this would be nice:
FooModel {
id: foomodel
RecentUsageModel {}
RecentAppsModel {}
}
View {
model: foomodel
}
I.e. be able to define your own menu structure in QML by writing a model that
adds child objects to its own entry list.
REPOSITORY
R119 Plasma Desktop
REVISION DETAIL
https://phabricator.kde.org/D4792
EMAIL PREFERENCES
https://phabricator.kde.org/settings/panel/emailpreferences/
To: subdiff, #plasma
Cc: hein, plasma-devel, progwolff, lesliezhai, ali-mohamed, jensreuterberg,
abetts, sebas, apol
