settings qml module

Aaron J. Seigo aseigo at kde.org
Wed Oct 17 18:35:12 UTC 2012


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
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/plasma-devel/attachments/20121017/256b40d6/attachment.sig>


More information about the Plasma-devel mailing list