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

List:       kde-core-devel
Subject:    Re: dcop interfaces, standard ?
From:       Simon Hausmann <shaus () helios ! med ! Uni-Magdeburg ! DE>
Date:       1999-12-07 22:06:29
[Download RAW message or body]



On Wed, 8 Dec 1999, Simon Hausmann wrote:

> 
> 
> On Tue, 7 Dec 1999, Bernd Gehrmann wrote:
> 
> > On Tue, 07 Dec 1999 Simon Hausmann wrote:
> > >On Tue, 7 Dec 1999, Bernd Gehrmann wrote:
> > >
> > >> On Tue, 07 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.
> > >> 
> > >> Which reasons?
> > >
> > >If the component, which is to be controlled, has a graphical user
> > >interface, then embedding is probably the way to go.
> > 
> > If I would want to have everything in one window, I would use Emacs
> > in a console, not X11.
> 
> You didn't get the point :-)

Oooops, it seems that was me ;-)
Sorry, I mixed up things :)

My point was that if I have an application which I want to control
"remotely" (process wise, not necessarily over networks) , and that
application has a GUI, then I will probably want to embed it, as it might
look confusing IMHO (like if a game wants to play some midi (during
playing) and that'd bring up KMidi's gui and activate certain
buttons/actions ;-)

Ciao,
 Simon


> If you want to do embedding, then you will also want to merge GUIs. If you
> want to merge GUIs, then using DCOP or CORBA is the wrong thing (that was
> David's point I think) .
> 
> Ciao,
>  Simon
> 

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