Plugins depending on the standardoutputview with no Ui

[Andreas Pakulat]

On 23.03.11 11:18:18, Julian Bäume wrote:
> Hi,
> 
> Am Mittwoch, 23. März 2011, 09:45:22 schrieb Andreas Pakulat:
> > PS: The KDevPlatform codebase has not been written with non-gui apps in
> > mind, hence you can always run into code-paths where suddenly ui is
> > needed. As the no-ui mode usually is used without KApplication or at
> > least without X11 connection, that means your app will crash at that
> > point.
> 
> What’s the use for KDevelop::Core::NoUi then?

To get kdevplatform loaded into an app that uses KApplication without X11
connection (or QCoreApplication+KComponentData as the tests do). That
however is a hack and you've to be rather careful what you do with the
kdevplatform libs as not all code-paths have been tested or examined for
necessity of this flag to disable certain things. In particular when errors
occur the code may still try to show message-boxes or what-not to the user.

That flag is simply a hack to satisfy the needs of things like duchainify
and other similar tools that don't want a GUI app, but the more its being
used the more you increase the potential to run into cases as with the
original post in this thread.

To really support non-gui apps the kdevplatform code needs to be split
into gui and non-gui libs. And similarly some of the plugins would need to
be split into two. Then non-gui apps can really make sure that no gui-code
is being run when they only use the non-gui parts of kdevplatform+plugins.

Andreas