[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-devel
Subject:    Re: dcop interfaces, standard ?
From:       Greg Lee <lee () hawaii ! edu>
Date:       1999-12-07 18:42:53
[Download RAW message or body]


On Tue, 7 Dec 1999, David Faure wrote:

> I think that when one applications wants to use another one,
> it should use KParts (the next one) and load the other app's shared lib,
> instead of using DCOP - for the same reasons that we dropped CORBA.
> And KParts provides open, close, save, ...
> 
> Of course if you are talking about scripting, then this doesn't apply :-)
> You don't really say what those DCOP interfaces would be used for.

I wanted to provide a way for games or whatever to have kmidi (or some
program) play midifiles.  A game probably doesn't need to provide
any way for the player to control the playing -- well, maybe volume,
but not rewind, fast forward, select patch set, ...  So it doesn't
have to provide controls or any sort of view.  Just "play this".
The dcop interface provides a very simple way to do this (but with
some details to be worked out).  Providing for kmidi to be embedded
seems like overkill.

I'd like to be able to use kparts, too, for applications that do need
at least come control buttons (like "play").  Perhaps konqueror.  Trouble
is, the examples I can find all seem to assume that the embedded
application will provide a visual view, instead of just sound.  If
anyone could offer some pointers, that would be helpful.


Greg Lee <lee@Hawaii.edu>

[prev in list] [next in list] [prev in thread] [next in thread]