Merging KAuth into KDELibs

[Aaron J. Seigo]

On August 29, 2009, Nicola Gigante wrote:
> > will classes in libkdecore such as KAUthorized use it in the future?
>
> KAuthorized is used for kiosks, right? 

Kiosk is the lock down system in KDE. it's not just for kiosks but for general 
administration (though it was developed originally by people building kiosk 
systems). so KAuthorized, Kiosk and KAuth have a huge amount of overlap.

> > will any widget in kdeui need access to it?
>
> Other widgets, no. But there are already one widget and a KAction
> subclass, provided by my kauth project, that are currently in that
> branch under kdeui.
>
> Also, I've made modifications to KCModule class to support authorized
> kcmodules and those modifications simply can't be split in another lib
> without rewriting all the kcm support.
>
> I'd propose to leave the UI part of the project in kdeui.

talking with Dario here at T3, it's probably possible to merge 
KAuthorizedAction into KAction (the cost would be sizeof(void*) to the dptr 
and one more public method) and similarly with KPushButton. the benefit is 
that it would mean fewer symbols in the libraries.

Dario and I will be looking at the API in more detail this evening, but i 
think it's most natural to have it in kdecore/kdeui as you currently have it 
in your branch, though it should probably be kdecore/auth rather than 
kdecore/kauth :)

> > (and the first stop of libkauth would be kdereview :)
>
> It has been in kdereview for three weeks before I started working on
> the kdelibs integration.

ah, sorry i missed that. i suck :)

-- 
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/051d2b0f/attachment.sig>