Description: I just compiled the new CVS-Version of x.org which now supports the Composite-Extensions which enables a lot of nice eyecandy-features. Here we got a little setting created by me showing different stages of transparency. What do you think?
IMO it's not worth it unless your a developer and want to do some debugging yourself.
Oh it looks nice but looks a whole lot better in a screenshot than it runs. For most folks there is not an interval that passes that xcompmgr does not crash in some way or another.
If you don't want the headaches then just wait for the final release. ;-)
please, please, an How-To!
i installed xcompmgr and transset and they work perfectly on Gnome (i'm on a double WM system: ubuntu/kubuntu, default is kubuntu).
but not on KDE.
if i say 'sudo xcompmgr' the Konsole locks up as it were starting something, but nothing appears...
have I to editate the kdm-session startup list? how can i do it?
thanks to all ^_^
I've just installed the same thing on a
Pentium 4 (hp pavilion zd7000)
512 megs of ram running
slackware 10
kde 3.3
NVIDIA FX 5200 GO 128meg
It crashes immediately if xcompmgr is as a user.
It runs fairly stable but very well while its running if xcompmgr is ran as root. Superkaramba apps look terrible because there is a dropshadow around the app that shouldn't be there. The transparencies and dropshadows are very fast.
This is going to be amazing after they work the bugs out!
I'm trying to figure out how to modify the width of the dropshadow. Does anyone know how?
-Chris
I have a 700Mhz/256Mo and a Geforce2... With the driver Nvidia with Render activated it's great!! Fast !!!.. But only with transparency, now with shadow or others options the speed radicaly decrease.
When I drag fast full screen windows I can see that the window is 1/3s late that my mouse WITH OR WITHOUT TRANSPARENCY because drawing is now doing by client/xcompmgr. So transparency is fast (with NVIDIA/RENDER driver). But the xcompmrg is less fast that all in server. OH
HO AND I AM IN 1600x1200... so xcompmg is great, fast enough !!
But some artifact with KDE persists, sometimes widwows are not paint (like minimize windowd to show only handler and come back, konsole fullscrenn and come back...).
DAMAGE (like uncover) ARE VERY VERY SLOW !!!! but becausse the RENDER driver don't support resize, so the resize it make by client. But I have modify uncover to don't scale (1:1) and show only one windows and with this I can't view 1 Mplayer and one Uncover duplicate OR 20 AMAROK UNCOVER DUPLICATES !!!!!! so DAMAGE IS FAST TOO ;-) that's aim !! but resize is slow ! sometimes with mplayer and uncover X crashs...
EXTENSIONS ARE GREAT AND IMPLEMENTATION IS NOT SO BAD ! ;-)
Go to freedesktop and test the 903 ;-)
Hi,
the X server runs pretty stable but due to some problems with the new X.org and ATI I can't use the ATI-Drivers for rendering. So I gotta use VESA (radeon and ati are not working with my card) and it isn't really fast but still usable.
The greatest speed problems occure while starting and moving a program - once it is started or moved it runs perfect and without any problems.
Ratings & Comments
7 Comments
Will you please post a howto for those of us that are not as experience.
IMO it's not worth it unless your a developer and want to do some debugging yourself. Oh it looks nice but looks a whole lot better in a screenshot than it runs. For most folks there is not an interval that passes that xcompmgr does not crash in some way or another. If you don't want the headaches then just wait for the final release. ;-)
please, please, an How-To! i installed xcompmgr and transset and they work perfectly on Gnome (i'm on a double WM system: ubuntu/kubuntu, default is kubuntu). but not on KDE. if i say 'sudo xcompmgr' the Konsole locks up as it were starting something, but nothing appears... have I to editate the kdm-session startup list? how can i do it? thanks to all ^_^
I've just installed the same thing on a Pentium 4 (hp pavilion zd7000) 512 megs of ram running slackware 10 kde 3.3 NVIDIA FX 5200 GO 128meg It crashes immediately if xcompmgr is as a user. It runs fairly stable but very well while its running if xcompmgr is ran as root. Superkaramba apps look terrible because there is a dropshadow around the app that shouldn't be there. The transparencies and dropshadows are very fast. This is going to be amazing after they work the bugs out! I'm trying to figure out how to modify the width of the dropshadow. Does anyone know how? -Chris
What's the stability and speed like? Matt
I have a 700Mhz/256Mo and a Geforce2... With the driver Nvidia with Render activated it's great!! Fast !!!.. But only with transparency, now with shadow or others options the speed radicaly decrease. When I drag fast full screen windows I can see that the window is 1/3s late that my mouse WITH OR WITHOUT TRANSPARENCY because drawing is now doing by client/xcompmgr. So transparency is fast (with NVIDIA/RENDER driver). But the xcompmrg is less fast that all in server. OH HO AND I AM IN 1600x1200... so xcompmg is great, fast enough !! But some artifact with KDE persists, sometimes widwows are not paint (like minimize windowd to show only handler and come back, konsole fullscrenn and come back...). DAMAGE (like uncover) ARE VERY VERY SLOW !!!! but becausse the RENDER driver don't support resize, so the resize it make by client. But I have modify uncover to don't scale (1:1) and show only one windows and with this I can't view 1 Mplayer and one Uncover duplicate OR 20 AMAROK UNCOVER DUPLICATES !!!!!! so DAMAGE IS FAST TOO ;-) that's aim !! but resize is slow ! sometimes with mplayer and uncover X crashs... EXTENSIONS ARE GREAT AND IMPLEMENTATION IS NOT SO BAD ! ;-) Go to freedesktop and test the 903 ;-)
Hi, the X server runs pretty stable but due to some problems with the new X.org and ATI I can't use the ATI-Drivers for rendering. So I gotta use VESA (radeon and ati are not working with my card) and it isn't really fast but still usable. The greatest speed problems occure while starting and moving a program - once it is started or moved it runs perfect and without any problems.