KDevPlatform Plugin loading

[Branan Riley]

I was talking about this with Apaku in IRC, and he suggested I send a message
here so others could join the discussion, so I am.

Right now, plugin loading isn't quite decided on for KDevPlatform. That's a
rather important (IMHO) thing to get done, as it will really define how
everything works together. I have a few ideas for enumerating plugins, and
for loading them.

PLUGIN LISTING IDEAS:
1) Have a list of plugins needed in the .kdev4 file.
2) Define project types that contain lists of plugins, and then just
 reference that project type in the .kdev4 file
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
2) Let a plugin-loader plugin do it from either of the listing ideas
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)

I would suggest using (2) for listing, and (1) for loading. This also
implicitly allows (3) to be done, since you could define a project type with
only one plugin - your custom loader.

Any comments would be very welcome.

Branan

-------------------------------------------------------