[OT] plugins and QDockWidget
kitts
kitts.mailinglists at gmail.com
Sat Mar 24 19:27:06 UTC 2007
On Sunday 25 Mar 2007 IST, Andreas Pakulat wrote:
> > So generally speaking, i assume that every plugin instance maintains a
> > pointer to the mainwindow passed to it in the constructor, holds the
> > responsibility of providing its own mainwidget (if applicable) and
> > receives activation signals to show/hide associated dockwidgets.
>
> No, at least not in KDevelop4. We'd like to hide the mainwindow from any
> plugins as we will have multiple mainwindows but only 1 instance of a
> plugin. The plugin just provides a factory to create widgets for the
> dockwidgets and hopefully it'll also provide a way to create a central
> widget if it needs to.
>
> However there are also plugins in KDev4 that don't provide any of the
> two and just "do some work", like the project managers or project
> builders.
So the plugin itself cannot initiate the creation of a new dockwidget but
will list them out when queried by the main app? The 'scope' of the plugin
is set by the main app. I have in mind the situation where perhaps a new
dockwidget is created/modified by the plugin based on the selection within
its view. Of course, this could also be achieved by it rising a signal that
is understood by the main app.
--
Cheers!
kitts
More information about the KDevelop-devel
mailing list