kdevelop2.0

[Bernd Gehrmann]

On Tue, 12 Dec 2000, John Birch wrote:

> So... It would be nice to know where you are going with this. Having 
> introduced DCOP calls at the component level. I assume you are expecting 
> calls from external sources to manipulate the components? Or what other 
> reason did you introduce this? I don't know much about DCOP (but will have to 
> by the looks of it) Or to put it another way - how do you see the whole 
> system unfolding?

There are several uses for DCOP. On the one hand, it can be used for
'ordinary' interprocess communication. For example, it would be nice
if one could open source files from Cervisia, KBabel or even non-KDE
programs (hint: kdelibs/dcop/client). On the other hand, it can be
used for scripting. Although it's in principle possible to write a 
KDevComponent in Python (namely by writing a proxy part that communicates
with an embedded Python interpreter), it's quite heavy-weight and clumsy.
In contrast, it's very simple to write a short script that communicates
via DCOP with the make frontend to build a certain configuration of
an application and submit it to a queuing system, wait for it to finish
and then load the its data files into an editor window (this is just
an example, so don't take it too seriously ;-)

Bernd.


-
to unsubscribe from this list send an email to kdevelop-devel-request at kdevelop.org with the following body:
unsubscribe »your-email-address«