hi... fyi, i just pushed a merge of the develsettings branch in plasma-mobile along with a few other little fixes here and there.
one thing that i noticed was that the active-settings app used a component
that is in plasma-mobile/components/settings/. this was only usable by active-
settings, so i didn't see why it was in the top level components director at
all. instead of moving it, however, i made it reasonably reusable :)
so now any app can use it, like:
import org.kde.active.settings 0.1 as ActiveSettings
ActiveSettings.SettingsModulesModel {
id: settingsModulesModel
application: myAppName
}
then only settings modules with X-KDE-ParentApp=mAppName in their .desktop file
will be used to populate the model.
if we actually do want to use this in applications (i'd like to avoid
application settings dialogs in Plasma Active if at all possible), we may also
want to make the QML used by active-settings reusable as well...
--
Aaron J. Seigo
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Plasma-devel mailing list Plasma-devel@kde.org https://mail.kde.org/mailman/listinfo/plasma-devel
