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

List:       kde-core-devel
Subject:    Re: KDE libraries feature freeze and problems
From:       Mosfet <mosfet () jorsm ! com>
Date:       1999-11-06 18:49:09
[Download RAW message or body]

Yes, this *should* only affect the window manager modules, kicker, and
kwin which we are all actively developing so I would say go for it. At
worst, kicker will be acting strangely for a couple days, and kwin will
be buggy. It doesn't affect applications in general.

Matthias Ettrich wrote:
> 
> My personal schedule got a bit delayed, so kwin/kicker still do not work
> together properly. I promised to do this this weekend and am working on that
> currently.
> 
> However, I don't want to make kwin simply KDE-aware (old model). Reason: I'm
> working together with the other window manager authors on a new wm-spec
> standard. The specs should have been finished long time ago, but things take
> time. They are, however, evolving nicely and it is certain that KDE-2.0 will
> support these as native window manager interface. We will soon have another
> draft that is supposed to be quite close to the final standard.
> 
> Introducing the new interface into kwinmodule (and killing
> KWMModuleApplication) in the KDE libraries is not completely compatible
> _for_window_manager_modules_. However, there's not much point in releasing krash
> with stuff in it that will definitely dissappear in KDE-2.0 either.
> 
> Mosfet is helping with that, i.e. we will have kicker/kpager/kwin working
> nicely together next week --- and finally kdesktop integrated in the desktop.
> 
> May I continue commiting? Keep in mind it only affects window manager modules.
> 
> If not I'm asking for a branch.
> 
> Matthias

-- 
Daniel M. Duley - Unix developer & sys admin.
mosfet@mandrakesoft.com
mosfet@kde.org
mosfet@jorsm.com

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