Author Topic: Object Oriented Plugin API PoC  (Read 5866 times)

quick_wango

  • Jr. Member
  • **
  • Posts: 108
  • Software Engineer
This is something I thought about while I wrote LyricsReloaded plugin. MusicBee's plugin API is really well structured. There are a bunch of undocumented callbacks in the partial plugin class and a huge load of delegates in a struct.
From my current project (a module framework) I know quite a bit about object oriented API design.
So I quickly came up with this in a couple of minutes: https://gist.github.com/quickwango/4d0fe6fe08a0fb7ccf8a
The API would be provided by a dll which plugins would reference in their projects. MusicBee would provide the implementations of the classes.
This could easily be implemented without breaking backwards compatibility for existing plugins using the existing API.
Such an API wouldn't require detailed documentation as method and class names should be quite self explanatory and callback methods can be found via completion by Visual Studio or by looking at the library.

quick_wango

  • Jr. Member
  • **
  • Posts: 108
  • Software Engineer
any comment on this?

The API itself could be developed separatly from MusicBee.