Plugins API early sketch

[Mark Kretschmann]

On Monday 12 March 2007 19:41, T.R.Shashwath wrote:
> One question that needs to be answered is what happens if some plugin
> doesn't implement a certain function. To use your example, if a plugin
> claims to crossfade, and doesn't, what do we do? Do we check on plugin load
> and refuse to load those that don't at least implement those functions or
> handle it when trying to call that function?
>
> This won't be a problem with plugins we develop, but third-party ones,
> which are sure to appear, I don't want to trust so easily. So, what do we
> do about those?

Third party plugins are a non issue though, as we shouldn't allow external 
binary plugins at all (as I have pointed out earlier). 

All binary plugins would be developed by ourselves and bundled with Amarok, 
just like it is in 1.x. Alternatively, a third party could submit a plugin to 
us so that it can be maintained in our SVN. In both cases we would have full 
control over the implementation.

-- 
Mark