RFC: Removing PUD Actions

Jeff Mitchell mitchell at kde.org
Fri May 8 12:54:50 CEST 2009


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

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 260 bytes
Desc: OpenPGP digital signature
Url : http://mail.kde.org/pipermail/amarok-devel/attachments/20090508/4913de8a/attachment.sig 


More information about the Amarok-devel mailing list