Moving Parts of Baloo into the Workspace

[Kevin Krammer]

On Wednesday, 2014-06-11, 15:43:34, Vishesh Handa wrote:
> On Wed, Jun 11, 2014 at 3:30 PM, Aleix Pol <aleixpol at kde.org> wrote:
> > Doesn't that tie Baloo usage to exclusively Plasma? If you want it to be a
> > framework, won't framework users need to configure the things in the KCM?
> 
> Hmm, you have a point.
> 
> I was only thinking about it from a non-kde point of view. If you want a
> file indexer, you probably don't want to drag in KCMUtils. Additionally, it
> would be nice to combine the (hypothetical) runners kcms with the baloo one.
> 
> For now, lets leave the kcm in Baloo.

An alternative would be a configuration API in the framework, e.g. something 
like a KConfigXT generated class.
Such a think would allow applications using the framework to provide UI 
without having to know internal config details.

Basically a separation of the KCM in UI and Config API.

Cheers,
Kevin
-- 
Kevin Krammer, KDE developer, xdg-utils developer
KDE user support, developer mentoring
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 190 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/plasma-devel/attachments/20140611/7281c131/attachment.sig>