What to do with the old Plasma::Animator?

[Aaron J. Seigo]

On Saturday 13 June 2009, Akmanalp, Mehmet A wrote:
> On Sat, Jun 13, 2009 at 4:36 PM, Akmanalp, Mehmet A<makmanalp at wpi.edu> 
wrote:
> > Actually, I was just looking at that *right* now and thinking that.
> > AnimatorPrivateOld? AnimatorPrivate1? Ugh.
>
> Marco suggested AnimatorLegacyPrivate in #plasma, which seems in
> place. Although, he also suggested AnimatorOldStinkyPrivates :)

AnimatorPrivateDeprecated?

if done the simple way, then we would have to allocate _two_ objects, which 
isn't great.

but this way, if it's allocated only when one of the deprecated method calls 
is used, we can eventually (once nothing is using the deprecated Animator 
calls) avoid the overhead of those old private members at runtime.

so .. i think this is a good idea indeed.

-- 
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: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: This is a digitally signed message part.
Url : http://mail.kde.org/pipermail/plasma-devel/attachments/20090613/6af03601/attachment.sig