RFC: Removing PUD Actions
Maximilian Kossick
maximilian.kossick at googlemail.com
Fri May 8 14:24:13 CEST 2009
There's going to be one "let's break amarok" weekend anyway when we
implement the changes to Meta.h that we agreed on in Berlin. So we
might as well fix the QActions then as well
On Fri, May 8, 2009 at 12:54 PM, Jeff Mitchell <mitchell at kde.org> wrote:
> Hey guys,
>
> Yesterday I spent about 15 minutes and removed PopupDropperAction from
> libpud trunk. It was pretty easy as most of the functionality
> originally there was already moved into PopupDropperItem and
> PopupDropper itself.
>
> For post-2.1 Amarok (not sure if it will be 2.1.1 or 2.2...any
> requests?) I'll import that change into Amarok. The question I have is:
>
> * Do people want me to go and replace PDAs with QActions everywhere I
> find them, or...
> * Should I let the various module maintainers decide how they want to
> structure their code, now that they are free of having to cast
> everything to PDAs?
>
> Obviously the second option means I'd make the change and break trunk
> until people fixed up the various parts; the advantage is that if anyone
> did hacky things that they wanted to fix once PDAs went away, they can
> properly fix it instead of me doing guesswork.
>
> Thanks,
> Jeff
>
>
> _______________________________________________
> Amarok-devel mailing list
> Amarok-devel at kde.org
> https://mail.kde.org/mailman/listinfo/amarok-devel
>
>
More information about the Amarok-devel
mailing list