Kahakai

[Anubis]

Has anyone been successful in getting kahakai to work as KDE's wm? I've been trying this a couple of different ways and yet to be successful. I can kind of get flubox to work in this capacity, but it basically comes up in two instances. Basically, there's a window that can be minimized and moved around, so I just kill it, and the window behind it behaves normally.

However, for kahakai, it loads up initially when KDE is setting the wm, but after that it sets the panel and kahakai disappears never to be seen again.

I'm trying to get this setup by adding the wm variable in the /usr/kde/3.1/bin/startkde file... Any suggestions would be great. Thanks.
_________________
The one who says it cannot be done should never interrupt the one who is doing it.

[mackstann]

What do you mean when you say it disappears? There's nothing to show.. unless you have some windows open, you won't see Kahakai.

[Anubis]

So, basically I orginally see the kahakai background screen image, but once kde finishes loading it switches back to the kde wm, and if I right click on the screen etc, it's not kahakai, but regular kde.

Where as previously I could right click and would get fluxbox menus, or if I simply load kahakai by itself I get it's normal menus.
_________________
The one who says it cannot be done should never interrupt the one who is doing it.

[princeofchaos]

Kahakai supports standards better than Fluxbox does, so the issue is Kahakai root (desktop) bindings being overwritten by KDE's desktop. You may want to add a different binding for opening Kahakai menu if you really want to.

[KiTaSuMbA]

Suppose you only want the kde basics and still retain some of the great kahakai features. This means you should get rid of the offending parts (e.g kdesktop, kicker, khotkeys etc.).
Now, reading through startkde I found that such stuff is loaded from the autostart directory. "Cool!" I thought and had a major cleaning frenzy inside /usr/kde/3.1/share/autostart (after backing up of course ). Strange thing is, the bastard still loads them! So, let's take a more "standard" issue: if I'm to stop using kicker in favor of a superkaramba-only setup... how could I do that?
_________________
Need to flame people LIVE on IRC? Join #gentoo-otw on freenode!

[princeofchaos]

Kdesktop is needed for superkaramba, it's non-standard unlike gdesklets in terms of transparency it uses. How about launching relevant parts, from ~/.kahakai/autostart?

[Anubis]

OK. Decided to start giving this another go (was busy playing Star Wars Galaxies). So, I tried to launch kdedesktop from the kahakai start file, and the same thing happened there that was happening when I was trying to launch kahakai from within kde. So, obviously that's the hangup, the question is how do we get around that since I would like to use SuperKaramba. I'm gonna keep fiddling to see if I can find something as well.
_________________
The one who says it cannot be done should never interrupt the one who is doing it.

[princeofchaos]

If I were you, I would try gdesklets which work every WM under the sun.

[mallchin]

[christsong84]

https://forums.gentoo.org/viewtopic.php?t=93106&highlight=gdesklets
_________________
while(true) {self.input(sugar);}

[mallchin]