Re: [Rhythmbox-devel] gmenu, plugins and you

[David Mohammed <davidmohammed gmail com>]

Jonathan,

  whilst I fully appreciate that stuff needs to keep advancing, removing the link between the shell, ui-manager, actiongroups etc is quite fundamental to many external devs plugins - at least that is what I can see when I managed to compile RB today.

An early heads up on such a fundamental change here via the mailing list would have been appreciated.  Watching & understanding the implications of commits on such a vast project as rhythmbox is quite an undertaking for any external dev.  

I do understand you cannot keep track on everyones external plugin and should correctly maintain the standard inbuilt plugins.  That is going to be my reference point until tutorials, python documentation etc catch up (hopefully)

Anyway, there is little to be earned to discuss now - the decision has been made, the release is to be made this weekend.

Please, please, please throw up a mailing list thread when you are considering/have decided fundamental changes to the API - at least we have an early sight and can advise you on the extent of any impacts as well as factoring in design changes to our own developments.

thanks

David

On 6 April 2013 22:20, Jonathan Matthew <jonathan d14n org> wrote:

On Sun, Apr 7, 2013 at 6:17 AM, David Mohammed <davidmohammed gmail com> wrote:
> Jonathan,
>
>   I would like to express my utter amazement and deep disappointment that
> you made this decision.

What decision? What do you think I should have done instead?

> From what I can see, there was no warning about this.  This really does
> break several very useful external plugins including my plugin CoverArt
> Browser.

All changes are pushed to the public git repository that anyone can
view. This particular change landed over a month ago. If you're
concerned about plugin API changes, you need to be watching.