Thanks for the info! That clears up a lot of stuff. Some of this information should go up on http://projects.gnome.org/rhythmbox/ IMO
Thanks again! ~Mark On Fri, Oct 28, 2011 at 1:57 AM, Jonathan Matthew <jonat...@d14n.org> wrote: > On Fri, Oct 28, 2011 at 12:20 PM, Mark Baldridge > <marktbaldri...@gmail.com> wrote: > > A few questions: > > 1. Is it true that all the old third party plugins are now broken with > the > > new plugin infrastructure? > > Yes. > > > 2. What all has changed with the python plugin API? > > Python plugins must use introspected bindings now rather than static > bindings, for rhythmbox and gtk+ and anything else they call. Plugins > now use libpeas base classes rather than rb.Plugin. Package and class > names have all changed, and many method names have changed too. > > It's pretty easy to update a python plugin to work with rhythmbox 3, > but some aspects of the plugin API are still changing and some parts > of rhythmbox are being redesigned in ways that affect plugins. > > > 3. Are there any plans to update the plugin writing guide? > > When the plugin API stops changing. >
_______________________________________________ rhythmbox-devel mailing list rhythmbox-devel@gnome.org http://mail.gnome.org/mailman/listinfo/rhythmbox-devel
