KIconEngine

[Matthias Kretz]

That'd be great.

What's the rationale for making KIconEngine private? Or perhaps the other way 
around: what does the KIconEngine API allow in addition to other classes 
(e.g. KIcon)? - if there's nothing and it's only an implementation detail 
than that's the answer I wanted. :-)

On Tuesday 27 March 2007 09:29, Simon Hausmann wrote:
> I'd like to make KIconEngine private API and port it to QIconEngineV2
> (which was necessary to introduce to support streaming and implicit
> sharing). Any objections?
>
> Now I see that there's some code in playground/pim/recipientspicker that
> uses it, but it doesn't really have to. May I port this off of KIconEngine
> now and make KIconEngine private before monday?
>
> It's not used in /trunk according to lxr.kde.org (and of course it
> shouldn't be) and it's easy to port to plain KIcon.
>
> Simon

-- 
________________________________________________________
Matthias Kretz (Germany)                            <><
http://Vir.homelinux.org/
MatthiasKretz at gmx.net, kretz at kde.org,
Matthias.Kretz at urz.uni-heidelberg.de
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://mail.kde.org/pipermail/kde-core-devel/attachments/20070327/c3dbf160/attachment.sig>