faq
flatforty
contribute
subscribe
configure
search
rdf
main
parent
thread
|
Re: Aquamarine + beryl
by kwilliam on Wednesday 30/May/2007, @14:21
|
Some examples of how KWin is better integrated with KDE than Beryl are:
* the KDE Desktop Pager doesn't work with Beryl (at least it didn't originally - there's a patch available now I think). The "single desktop 4x as wide" paradigm threw it off.
* KWin has a DCOP interface, allowing other KDE programs to communicate with KWin in a standard way. KWin 4 will probably use DBus (DCOP's successor) now that the rest of the Linux world has caught on, but DCOP was around for years before DBus.
* I personally experienced a lot of problems with Beryl+KDE. The window decorations would disappear for no reason, windows wouldn't get focus events properly (I would have to hit F12 *twice* to bring the Yakuake console to the front), etc. So maybe Beryl worked perfectly for you, but you were one of the lucky ones. I wasn't, so I'll enjoy Kwin. |
|
|
The Fine Print: The following comments
are owned by whomever posted them.
( Reply )
|
Re: Aquamarine + beryl
by Chaoswind on Thursday 31/May/2007, @00:06
|
> * KWin has a DCOP interface, allowing other KDE programs to communicate with
> KWin in a standard way
Hm, I checked KWin's interface with kdcop, but only found some neat things for configure the desktop and opacity. So, is this really all, or is there somewhere a switch to expose a mighty interface for poweruser and their scripts?
|
[
Reply To This | View ]
|
Re: Aquamarine + beryl
by gnumdk on Thursday 31/May/2007, @00:10
|
To use kwin with dcop, just call dcop on an window, not on kwin...
|
[
Reply To This | View ]
|
Re: Aquamarine + beryl
by Chaoswind on Thursday 31/May/2007, @00:18
|
What?
I can't call dcop a window. I can only use the interfaces, exposed by the applications, and there is nowhere an advanced window-managing interface to found.
|
[
Reply To This | View ]
|
Re: Aquamarine + beryl
by tendays on Thursday 31/May/2007, @11:25
|
As far as I know you can't address an arbitrary window. However all kde applications have a dcop module (or whatever that's called) that corresponds to their window.
For instance if I type dcop konsole-4414 konsole-mainwindow\#1 (4414 being my konsole pid atm)
I get a list of 135 functions, like setSize, focus, maximize, raise, etc etc.
|
[
Reply To This | View ]
|
Re: Aquamarine + beryl
by Chaoswind on Thursday 31/May/2007, @12:15
|
Exactly. But not every application is a kde-application. And in fact, there are also kde-application which does'nt offers this interface, ktorrent oder dialogs for example.
So, a complete scriptable interface, for every window, would be nice. I know, there exist wmctrl, but this prog has limits.
|
[
Reply To This | View ]
|
|
Re: Aquamarine + beryl
by litb on Wednesday 06/Jun/2007, @01:16
|
your problem with yakuake not showing up immediately is probably because you first start kwin, and then replace it with beryl at the time yakuake is already up. i had the same problem and i solved it by writing a file ~/.kde/env/use_beryl in which i wrote the single line KDEWM=/usr/bin/beryl . (and remove beryl from autostart after that manually!) startkde will source that file and will read that variable to start beryl instead of kwin. that solved all the windows-are-not-working-for-me problems i had before.
but, nevertheless, i also think it is right to extend kwin instead of using beryl, which still has alot of problems. :)
|
[
Reply To This | View ]
|
The Fine Print: The previous
comments are owned by whomever posted them.
( Reply )
|
|
![[KDE Dot News]](http://www.kde.org/dot/Images/kdedotnews.gif)
