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

List:       kde-core-devel
Subject:    Re: A new framework for embedding ... without CORBA
From:       Matthias Elter <me () main-echo ! net>
Date:       1999-09-29 9:23:27
[Download RAW message or body]

On Mit, 29 Sep 1999, Reginald Stadlbauer wrote:
> On Wed, 29 Sep 1999, Matthias Elter wrote:
> >On Mit, 29 Sep 1999, Reginald Stadlbauer wrote:
> >> On Wed, 29 Sep 1999, Waldo Bastian wrote:
> >> >On Wed, 29 Sep 1999, Simon Hausmann wrote:
> >> >> > So instead of moving to an open standard for desktop components we move
> >> >> > closer to a Qt/TrollTech-only solution? 
> >> >
> >> >[Snip]
> >> >
> >> >> So this is no removal of an open desktop component standard IMHO, the idea
> >> >> of components remains! It's just a matter of using fast and efficient C++
> >> >> interfaces and shared libraries instead of CORBA.
> >> >
> >> >Like I said: We're moving to a proprietary Qt solution instead of to a solution
> >> >based on open standards. I find that a sad development.
> >> 
> >> But everybody who played (I can't say used) embedding in current OpenParts,
> >> knows that it is not useable at all (It _never_ really worked!!!!). So as long
> >> as we use that, embedding is just a dream but can't be used. So I think a
> >> working and fast solution is preferable over a slow, unstable, not really
> >> useable one.
> >
> >Embedding works for me and is quite useable. And as I mentioned earlier there
> >are ways for performance improvements other than dropping the IDL interface.
> 
> Come on! Embedding crashes a lot! And if it doesn't crash, embed 20 parts in
> KPresenter, save it and load it. If it doesn't crash during that, you will
> notice how slow it is.

Yes embedding 20 parts is slow...but dropping the IDL interface is not the only
way to improve performance. And yes it crashes a lot but...it's alpha and
what makes you think that a shared libs solution is naturally more stable?

Greetings, Matthias

--
Matthias Elter
me@kde.org / me@main-echo.net
KDE developer

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