KDCOPServiceStarter Class Reference
A generic DCOP service starter, using KTrader. More...
#include <kdcopservicestarter.h>
Public Member Functions | |
int | findServiceFor (const QString &serviceType, const QString &constraint=QString::null, const QString &preferences=QString::null, QString *error=0, QCString *dcopService=0, int flags=0) |
virtual int | startServiceFor (const QString &serviceType, const QString &constraint=QString::null, const QString &preferences=QString::null, QString *error=0, QCString *dcopService=0, int flags=0) |
Static Public Member Functions | |
KDCOPServiceStarter * | self () |
Friends | |
class | KStaticDeleter< KDCOPServiceStarter > |
Detailed Description
A generic DCOP service starter, using KTrader.The default implementation starts new processes, but this interface can also be reimplemented by specific applications to provide dlopened in-process DCOP objects.
- Author:
- David Faure <faure@kde.org>
Definition at line 34 of file kdcopservicestarter.h.
Member Function Documentation
|
Check if a given DCOP interface is available - from the serviceType it's supposed to implement. The trader is queried to find the preferred application for this serviceType, with the constraint that its X-DCOP-ServiceName property must be defined. Then the DCOP server is checked. If the service is not available, this method will call startServiceFor to start it.
References QString::arg(), endl(), QValueList::first(), QValueList::isEmpty(), QString::isEmpty(), kdDebug(), kdWarning(), and startServiceFor(). |
|
Find an implementation of the given The default implementation uses KTrader to find the preferred Application, and then starts it using kapp->startService... However applications (like kontact) can reimplement this method, to provide an in-process way of loading the implementation for this service type.
References endl(), QValueList::first(), QValueList::isEmpty(), and kdDebug(). Referenced by findServiceFor(). |
The documentation for this class was generated from the following files: