Implementing KTextEditor interfaces in KDevelop

Sven Brauch svenbrauch at googlemail.com
Mon Sep 15 16:50:12 UTC 2014


> Think of createView() as "hey loaded plugin, if you want to hook into the
> mainwindow (xml gui client, tool views), do this now".
The specific problem we're facing is that our API works like "if you
want a toolview, register a toolview factory which can construct a
widget when I, the view controller, tell you to" which is very hard to
map to your API. When a plugin asks me to create a toolview, I
basically have to construct a widget in advance and store it in the
factory, then register the factory, and then let the toolview populate
the widget. That seems to work, but it smells a lot like it will
create ugly ownership issues and is generally not pretty at all.

Ideas? :)


More information about the KDevelop-devel mailing list