KDevPlatform Plugin loading

[Andreas Pakulat]

On 21.03.07 10:11:58, Branan Riley wrote:
> PLUGIN LISTING IDEAS:
> 1) Have a list of plugins needed in the .kdev4 file.

For most plugins this should be the list of interfaces needed in the
project (like svn-iface, qmake-manager-iface, ...)

> 2) Define project types that contain lists of plugins, and then just
>  reference that project type in the .kdev4 file

Thats the profiles stuff we already have in kdev3 and which will be
ported (somehow) to kdev4.

> 3) no data, use some other mechanism (only works with (3) below)
> 
> PLUGIN LOADING  IDEAS:
> 1) Let KDevPlatform do it from either of the listing ideas

Thats what happens atm, any part of the shell or any plugin can ask the
plugincontroller to load a plugin (preferably by asking for an extension
interface).

> 2) Let a plugin-loader plugin do it from either of the listing ideas

Uhm, there's a problem here: who loads the plugin-loader-plugin? Then we
again need something in shell and thus we have 1) again.

> 3) define the plugin-loader plugin in the .kdev4 file, and let it do
> everything else it needs to do. (only works with (3) above)

But something needs to load the plugin so we again have case 1) with a
plugincontroller to load any plugin.

So what I'm saying is that I currently think we will end up with listing
ideas 1+2 and loading way 1. 

Andreas

-- 
It was all so different before everything changed.