Merging KAuth into KDELibs

[Aaron J. Seigo]

On August 29, 2009, Dario Freddi wrote:
> On Saturday 29 August 2009 14:02:20 Aaron J. Seigo wrote:
> > how many applications should be using this (directly or indirectly): few
> > or many? if few, a separate library is a good way to limit symbol growth
> > in our core libs; if many, avoiding another library to link in might be
> > good.
>
> Ideally many, KIO for instance. But given that is very specific, I still
> like the idea of having it separate

well, it means that the apps will open another library, which impacts start up 
time of apps.

> > will classes in libkdecore such as KAUthorized use it in the future?
>
> Surely possible, but the API of KAuth is easier, nicer and more powerful.
> KAuthorized does not seem to be mantained

thing is that KAuthorized is used. it ties into KConfig and Kiosk. 
understanding how KAuth and Kiosk should interact/intersect will be an 
important discussion to have, but even if we deprecate KAuthorized we should 
not have two completely detached systems imho and KAuthorized should hook into 
KAuth as well behind the scenes.

> > will any widget in kdeui need access to it?
>
> Only the new ones, KAuthorizedButton and KAuthorizedAction

to me, it'd be more natural to find KAuthorizedAction next to KAction. even 
more natural would be if KAction could be extended so we don't need a new 
class. i haven't looked at the API of KAuthorizedAction to know if that makes 
any sense, but maybe we can do this together here in person @ T3?

> > (and the first stop of libkauth would be kdereview :)
>
> Been there already :) we moved it to a branch first to prepare for merging
> and avoid disasters

ah, ok :)

-- 
Aaron J. Seigo
humru othro a kohnu se
GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA  EE75 D6B7 2EB1 A7F1 DB43

KDE core developer sponsored by Qt Software
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 197 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/kde-core-devel/attachments/20090829/8a94c6e1/attachment.sig>