On Saturday 13 June 2009, Akmanalp, Mehmet A wrote:
> On Sat, Jun 13, 2009 at 4:36 PM, Akmanalp, Mehmet A
wrote:
> > Actually, I was just looking at that *right* now and thinking that.
> > AnimatorPrivateOld? AnimatorPrivate1? Ugh.
>
> Marco suggested AnimatorLegacyPrivate in #plasma, which seems
On Sat, Jun 13, 2009 at 4:36 PM, Akmanalp, Mehmet A 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
On Sat, Jun 13, 2009 at 3:58 PM, Marco Martin wrote:
> uuh, is nevessary to mark deprecated AnimatorPrivate ince is well.. private?
> we could even rename it to something else and keep animatorprivate for the new
> stuff i suppose?
Actually, I was just looking at that *right* now and thinking that
On Friday 12 June 2009, Akmanalp, Mehmet A wrote:
> >> * mark all the methods currently in Animator as KDE_DEPRECATED
>
> Did so. I also marked the enums and the AnimatorPrivate deprecated
> too, and added @deprecated s to the comments. It compiles and runs
> fine afaik. Have I missed anything? (Ch
On Sat, Jun 13, 2009 at 2:32 AM, Aaron J. Seigo wrote:
> On Friday 12 June 2009, Akmanalp, Mehmet A wrote:
>> >> * mark all the methods currently in Animator as KDE_DEPRECATED
>>
>> Did so. I also marked the enums and the AnimatorPrivate deprecated
>> too, and added @deprecated s to the comments. I
On Friday 12 June 2009 18:21:30 Aaron J. Seigo wrote:
> On Friday 12 June 2009, Petri Damstén wrote:
> > On Thursday 11 June 2009 18:43:39 Aaron J. Seigo wrote:
> > > great; we still need to fix the plasmoid (or the python scriptengine,
> > > which is broken) but it's good to know we can handle the
