similar to: initial metacity theme support for compiz

I played a little bit yesterday with adding metacity theme support to gwd and it looks like it's not going to be very hard. Hopefully I'll have it working in the next couple of days. What I've done is to rip out all the parts of the metacity code that is required for theme support (boxes.c, gradient.c, theme-parser.c, theme.c, util.c). Ideal would be if we could put this part of

I have downloaded compiz-0.2.0 and tried to compile it. The INSTALL file talks about autgen.sh, but I am unable to locate it. I tried ./configure but it complains about a number of missing packages. Is there any docs on how to compile compiz on SLED 10 ? I have searched in a lot of places, but have not been able to dig up anything. A detailed list of what packages is required (and where to locate

hi, I made a small a patch for gtk-window-decorator which define default border alpha to zero when it use metacity theme. That allows while playing with the alpha attributes of the metacity themes to have transparent borders. here too the modified ?Human Ubuntu? theme and a screenshot to show the result. ps: sorry for my bad english -------------- next part -------------- A non-text attachment

I pushed out some changes to gwd that makes it possible to properly set an overall opacity value for any metacity theme. Making the complete decorations translucent can look bad with some themes. However, I've made it possible to have the opacity fade from opaque to the selected opacity value in a similar way to how the built-in decorations look. This usually looks a lot better. I'll add

Look at it, and you'll see the black outline is missing on the right side of the minimise button. This has been bugging me for a while. I've attached a zoomed in shot, so you can see easily what I mean. It's not a bug in the theme, but in gtk-window-decorator's Metacity theme support, as the border displays perfectly in Metacity. Does it happen with other themes? --------------

A new compiz release 0.8.0 is now available from: http://releases.compiz.org/core/compiz-0.8.0.tar.gz which can be verified with: http://releases.compiz.org/core/compiz-0.8.0.tar.gz.sha1 52c30ac2ca0dfe2ba2d027d80ee6be038a844958 compiz-0.8.0.tar.gz http://releases.compiz.org/core/compiz-0.8.0.tar.gz.sha1.asc (signed by ) Additionally, a git clone

Compiz 0.9.14.0 has been officially released today. Major changes in this release include: - Development has switched from Bazaar (back) to Git [1]. - CCSM has been ported to PyGObject, GTK 3 and Python 3. - compizconfig-python has been ported from Pyrex to Cython. - Restored the Color Filter plugin by porting it to the new plugin API. - Added support for loading configuration from multiple

My head hurts from trying to figure this out for the past several hours . . . I want to determine what provider to use based on a fact (thanks for the suse version fact btw) but I ain''t gettin it: What''s wrong? Am I going down the completely wrong path? Is there a better way? # suse-yum.pp case $suse_repo_name { #sled10-i586: {Package{ provider => rug}} sled10-i586:

Our previous attempts to select a project name for CompComm have not gone well. We tried a poll but the names in the poll were not pre-qualified to determine if they were usable and the ?winning? name was also a strongly disliked name. Kristian and I each proposed a plan to select a name, but that effort got sidetracked by a massive flame war on the mailing list. While our community has some

Hi Everyone, I'm going to make some big structural cleanups to core which is likely to affect everyone here, but I believe is for the better, so I am posting this mail now to get some feedback and make sure that we don't tread on anyone's toes when I merge all of this stuff. 1st Change: Decorators are going in their own repo ========================================= The decorators

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Yesterday I sent a patch (http://paste.ubuntu-nl.org/24252/) against the latest compiz ubuntu gutsy source package to Amaranth, to make compiz compile (and package, of course) the gtk-window-decorator in two ways: 1) as gtk-window-decorator (= compiz-gtk package) using these configuration parameters: --disable-gnome \

Hi. libwnck broke API with the 2.19.3 release. This effects compiz as the WNCK_WINDOW_MODAL_DIALOG is no longer supported by it. The attached patch allows compiz to build against the library. Thanks. -- Saleem Abdulrasool compnerd (at) compnerd (dot) org -------------- next part -------------- --- configure.ac 2007-06-07 10:33:17.000000000 -0500 +++ configure.ac 2007-06-07 10:35:41.000000000

Hello, I'm developing a fancy screenshot application for the GNOME-desktop using GTK and GDK libraries (and some Xlib stuff too). When taking a screenshot of a window, my code first finds out in which desktop the window lies (resides) and then moves to that desktop and takes a screenshot. This is quite easy to do under the Metacity window manager, but I cannot make this work right in Compiz

Both amgeex (from the forum and wiki) and myself (of the same) are having some rather severe issues with 0.3.6. Both of us built it, and much to our amazement, no matter what we did, something seemed wrong with the Compiz gconf settings. Even after uninstalling Compiz, deleting schemas, reinstalling schemas, reinstalling Compiz 0.3.4, and several other hopeful solutions, we were left with a

I have configured compiz to use 1 workspace and 4 viewports and metacity to use 4 workspaces. When I start compiz while metacity was running it uses 4 workspaces and 4 viewports (ignoring the gconf settings). When I restart X so that compiz is started before metacity this does not happen (it uses what its configured for). bug or feature? if feature can it be disabled? switching

With the Magical Jelly Bean Keyfinder running in Wine in Linux with Gnome/Metacity, the syncing of the "Always On Top Status" is one-way. Under tools, Keyfinder has an "Always On Top" option. If you put the window into "Always On Top" mode via the keyfinder's option under tools, when you right-click on the window bar, you will see that, according to

I have installed compiz with metacity support, my metacity libs are 2.16.3 and I used this command to on theme support gconftool-2 -s /apps/gwd/use_metacity_theme -t bool true but I can`t change border of windows in gnome-theme-manager I can change theme only. Is metacity support functionall yet ? Or I maked something wrong.

A new compiz release 0.7.6 is now available from: http://xorg.freedesktop.org/archive/individual/app/compiz-0.7.6.tar.gz which can be verified with: http://xorg.freedesktop.org/archive/individual/app/compiz-0.7.6.tar.gz.sha1 be55dada77dc0716a040c2b9e2d16a0fbc736180 compiz-0.7.6.tar.gz

Hi I would like to help with metacity testing/development. I think I may help with the 3D development of metacity but I don't know with whom I should contact. Hope someone will help. Regards MichalDavidR

CentOS Errata and Security Advisory CEEA-2005:454 https://rhn.redhat.com/errata/RHEA-2005-454.html The following updated files have been uploaded and are currently syncing to the mirrors: s390: updates/s390/RPMS/gnome-panel-2.2.2.1-10.s390.rpm updates/s390/RPMS/metacity-2.4.55-7.15.s390.rpm s390x: updates/s390x/RPMS/gnome-panel-2.2.2.1-10.s390x.rpm