Not with inline methods.
Yes, as I said, I guess this would work. the rest was about implementation which is not inline.

Then maybe I didn't explain it clear enough. Creator doesn't use a plain QPluginLoader approach, it builds upon it. You don't need the extra part unless you want your plugins to do something more than just implement one interface. Plain QPluginLoader approach is about "pulling" functionality from plugins (which are dumb) to the main app, Creator works the other way round - the plugins (which are aware of what the main app exposes) "push" functionality to the mainstream.
Ok, I see what you mean now.
No, I need the "pulling" variant, the dumb plugin approach.
The plugin should not be aware of anything, the less it needs to know or depend on, the better.

I think we nailed it, I'll have a go at implementing this thing.

Thanks!