systemsettings, kde-cli-tools and other plasma components on non-Plasma/non-X11 platforms

[David Edmundson]

On Mon, Dec 21, 2015 at 1:22 PM, René J. V. <rjvbertin at gmail.com> wrote:

> Aleix Pol wrote:
>
> >> kde-cli-tools and systemsettings5 are required to configure
> >> 1 wallet settings (regardless of whether KWallet uses native KDE
> wallets or
> >> an OS X keychain backend)
> > Makes sense, probably should be moved to KWallet?
>
> Probably.
>
> >> 2 cookies and other html/browser related settings
> > What does it configure? is it only for KHtml?
>
> You can probably check better than I can at the moment, for the KF5
> version at
> least :) On KDE4 it configure what cookies to accept, allows you to edit
> the
> cookie jar, to chose the html engine and probably a bunch of other things
> that
> are evidently related to HTML and Web functionality in KDE code.
>
>
>
> >> 3 akonadi/PIM settings
> > It should probably go to PIM.
>
> Yes.
>
> As a general rule I think one can say that every application that uses a
> KCM
> module to configure part of its settings should provide a means to edit
> them.
>
> But wait, that already exists ... kcmshell :)
>
> Would it make sense to move kcmshell to a framework, replacing its payload
> with
> a kpart? Or is there some fundamental reason why kcm modules cannot run in
> the
> address space of an application other than kcmshell or systemsettings.
>
> They can be run in application space.
There's a class to load them easily as widgets. See KCMUtils framework
(KSettings::Dialog in particular)

David
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/plasma-devel/attachments/20151221/29c01fd4/attachment.html>