similar to: patch to set start- and end-color-stop for the skydome fallback gradient

Argl, this was meant to go to the list and not only to Hanno! -- email - macslow@bangang.de www - http://macslow.thepimp.net lowfat - http://macslow.thepimp.net/sponsor-it -------------- next part -------------- An embedded message was scrubbed... From: Mirco =?ISO-8859-1?Q?M=FCller?= <macslow@bangang.de> Subject: Re: [compiz] compiz coding style Date: Fri, 06 Oct 2006 01:53:46 +0200 Size:

Hi all, I've searched all over to the answer for this but no luck. In short, skydome doesn't seem to be working, I only have a black background. Skydome is pointing at the following: $ file plaza.png plaza.png: PNG image data, 2048 x 1024, 8-bit/color RGB, non-interlaced In the "Gnome Compiz Preferences" app, on the "Workspaces" tab, under "Cube", I

Greetings everybody! For about two weeks I'm now a happy owner of an intel-powered laptop (chipset, wifi, gfx) and wanted to give it a full test-drive of compiz and other GL-intensive programs. The laptop runs Xorg 7.1.1 and the i810 driver that comes with it (stock rpm from FC6). I'm forced to start compiz 0.3.4 with these options... --use-cow --strict-binding --indirect-rendering

Greetings everybody! Here's a patch (against compiz from CVS-head about 30 min. ago) that adds a shadow_color option to the parameters of the decoration-plugin. I only needed to add a few lines to decoration.c and gnome-window-decorator.c. The only thing missing is the compiz.schema. I dare not touch that XML-file manually. So after you applied the patch, recompiled compiz and restarted

Greetings everybody! I just git pull'ed compiz and after compiling and installing it, I started experiencing the decorations flashing and windows not being updated correctly. Sofar I was not able to revert to a state identifying which commit introduced this flaw. This is happening to me on an i915 and a GeForce7900GT. Using git revert <some commit> is the right way to work oneself

Greetings everybody! I'm trying to figure out how to get compiz install error-free in a prefix other than /usr. Because I currently don't "trust" compiz-packages on Ubuntu EdgyEft I have it install upstream to /home/mirco/compiz. I call configure like this: ./configure --prefix=/home/mirco/compiz --enable-librsvg --enable-gtk --enable-metacity --enable-dbus

Hi there again! I wanted to give a brief glimpse of the look of the new/customizable drop-shadows for compiz. In contrast to my earlier post today I currently follow the brute-force approach. 9 elements for the shadow... top-left top top-right left middle right bottom-left bottom bottom-right For the middle shadow-part there is a 2D-vector as parameter to allow growing or shrinking

Argl... I'm to stupid to hit the right buttons in evolution. -- email - macslow@bangang.de www - http://macslow.thepimp.net lowfat - http://macslow.thepimp.net/sponsor-it -------------- next part -------------- An embedded message was scrubbed... From: Mirco =?ISO-8859-1?Q?M=FCller?= <macslow@bangang.de> Subject: Re: [compiz] patch for colored drop-shadow Date: Wed, 03 May 2006

Greetings everybody! For anybody working on blur-related things, take a look at this glitch I encountered: https://bugs.freedesktop.org/show_bug.cgi?id=10275 Best regards... Mirco "MacSlow" M?ller -- email - macslow@bangang.de www - http://macslow.thepimp.net lowfat - http://macslow.thepimp.net/sponsor-it

Greetings everybody! I've created a patch to get compiz (upstream about 2 hours old) away from libsvg and libsvg-cairo. Those two libraries, which are regarded as "dead meat" by their initial developer Carl Worth, are replaced with librsvg 2.14.x (e.g. part of Gnome 2.14.x) by this patch. The patch is rather small and only touches these three files: compiz/configure.ac

Hello there everybody! Terrific... a mailing-list for compiz with David on board! Ok, I started off with writing some functions using cairo to draw me the needed elements for drop-shadows (atm stand-alone to focus on the proper generation of the shadow-parts) and currently still fiddle with the tweakable parameters. Right now I have... shadow-radius (e.g. 20 pixels) 2D-offset vector (e.g. 10

I am writing a configuration front end for the compiz gconf plugin at the moment, but it's proving harder than it should be because gconf does not record what type of compiz option the key is. For example, say i want a color picker for each color option the only way I can tell with gconf if it is color is if it has a # at the beginning, but there could be string option which also have a # at

Greetings everybody! I started looking more thoroughly at gnome-window-decorator.c and now my head spins and "hurts" and believe that I'm not going to achieve anything serious in terms of tweakable shadows anytime soon. It's far more difficult than I expected. While I (believe) to understand now the shadows are drawn, I currently don't get why there are 12 shadow-quads and

Guys, One thing that could be improved with skydome when it is animated is to have it 'centered' behind desktop 1 when you initiate rotation or show the desktop wall, etc. Many times when you want to take a screenshot, you naturally will want to have the central feature of your skydome in view. If you have cubecaps, then the orientation of the cubecaps gets all messed up when you rotate

Adding new options to a plugin is a pain. There is a lot of code that has allways to be changed for that. This is the reason why I've created the Beryl/Compiz XML options parser (bcop). Bcop allows you easily to describe options in XML and will autogenerate the needed Beryl/Compiz C code for you. The only think that needs to be changed in a existing plugins is to include the xxx_options.h

Hey everyone, I like to get the AUTHORS file updated before the next release. I suggest that we add the name and email of anyone who contributed some piece of code to compiz. For people who have contributed such a significant piece of code that it can be considered an algorithm or some functionality (e.g. Mirco's sky dome support in the cube plugin or S?ren's plane plugin), that should

I'd like to get all of you updated on the compiz related things discussed at the X developer conference that was held last week. The slides I used for my talk are available from here: http://people.freedesktop.org/~davidr/xdevconf07/ and you can also find some notes from all talks here: http://wiki.x.org/wiki/XDC2007Notes My talk was mainly focused on "what's next" and how

Compiz and Beryl merge: What's really going on? Recently Quinns post to the beryl-dev mailing list entitled 'Merge on' has led to a lot of discussion, some of which has been good and some of which has led to a lot of misinformation, to clear things up I'd like to give the story of the merge, and the justification for some of the more peculiar aspects. Basically lets try to avoid

0.2.0 release of compiz. http://xorg.freedesktop.org/archive/individual/app/compiz-0.2.0.tar.bz2 http://xorg.freedesktop.org/archive/individual/app/compiz-0.2.0.tar.gz Git tag: compiz-0.2.0 (568a0434f8a958800b2f0255b012c4b5a691ab82) MD5 Sums: 286a36ddb5d5b05534eb809eab541ec8 compiz-0.2.0.tar.bz2 41625de6c2a2b5109b420d7523446f54 compiz-0.2.0.tar.gz SHA1 Sums:

Hello, I'm on a Gentoo machine with the latest beta nVidia 9625 Drivers, trying to get Compiz to work with AIGLX... simply running 'compiz', or even with the addition of any options other than version, causes compiz to detect that it is indeed not XGL, and then segmentation faults... please note that I have only currently tried this with Compiz-Quinnstorm (the latest package available