similar to: Modified resize

hi, I saw that Mike Dransfield tried to port 'state' plugin from beryl. What does it do? It should be able to place windows, based on name, class etc., to specific viewports. I recently converted to compiz window manager from WindowMaker (used it for 8 years), and I miss automatic 'pinning' of specific windows to particular workspace (or viewport in this case). Mike's

Attached is a quick patch which adds a logging framework to compiz. I think it should be fairly self explanitory. I think it should allow plugin writers to extend it for any purpose, but I would appreciate any feedback or comments before going any further. Regards Mike -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: logging.diff Url:

Here is my python loader plugin which loads plain python scripts as full plugins. There is not much documentation, but I have included a few examples to get you going. triangle - Just a basic plugin which shows a triangle on a button press. This shows using ctypes to pass values from compiz to the python opengl bindings. basiczoom - Zooms in on the screen (basically) inactive - This is a port

I have written an initial flat file configuration backend for Compiz. At the moment it is using FAM for monitoring of files (it can be compiled without monitoring support for now). It is working fine but there are a couple of problems. 1. It looks like I should use addFileWatch rather than directly accessing FAM, is this correct? I notice dbus uses addFileWatch rather than

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

This was a private mail and not supposed to go to the compiz list. Please don't don't read it unless you're on the compiz admin list. :) I've apologized to Jeff, Mike, Rico and Arturo for making this mistake and I'd like to apologize to anyone else who might have been offended by it. I guess the good part is that you get an uncensored view of what we feel about the community

Here are a few plugins I wrote. The put plugins gives you bindings to move windows around. I set it up so the numeric keypad is like the area of the screen. So <Super>KP_Home will move the window to the top left, etc ... It also does viewport moves which is handy when used with the plane plugin. I like the plane plugin in a 3x3 matrix matching the keypad, so with the keypad and some

Hi, some of you might noticed that there was recently some discussion on the Beryl ML about an interface which provides sharing functions and allows us to do library plugins. One example for this kind of plugins is text, which was recently ported to that system. I now want to explain here how it works in general. Core does save the shared library functions in a CompLibraryFunction struct: struct

Hi, is anybody already working on porting the extra plugins (those ported over from beryl) to compiz 0.5.0? I'm especially thinking about the animation plugin. Or is this something to be addressed post-unification? CU all Matthias -- Matthias Hopf <mhopf@suse.de> __ __ __ Maxfeldstr. 5 / 90409 Nuernberg (_ | | (_ |__ mat@mshopf.de Phone

Hi all, attached is a patch which extends the window resize notify function: Instead of just passing the CompWindow*, additionally the resize difference information is passed (difference of position, width and height). Originally, I wrote this one for Beryl as we needed it for the group plugin, but I think it makes sense that Compiz also has this for the sake of plugin interoperability;

Hello, I just tried compiz-0.5.0 on my asus laptop with a intel 945gm chipset using intel_drv on the latest FC6 and get the following messages: The latest release of beryl does have this problem. How can I fix compiz to make it work? $ compiz --replace --indirect-rendering libGL warning: 3D driver claims to not support visual 0x4b compiz: GLX_EXT_texture_from_pixmap is not supported by

Hi, I have ported various improvements of Beryl's resize to Compiz: - multiple resize modes (aside to the standard "normal" mode those are "Stretch", "Outline" and "Filled Outline") - better aspect ratio constraining (you now also can resize aspect constrained windows from other edges than the lower right) - avoiding of mouse pointer desynchronization

It is a common request and I think it can be useful. The problem with beryl blur is that it is way too slow. I haven't poured through all of their code but I strongly suspect that there is some intensive code to work out where to blur. I would be happy with just a basic blur under transparent windows. Is there anything that can be done in the core to make effects underneath transparent

I was writing a simple plugin a while ago which just sets the paint values on inactive windows. The plugin is very simple and the main part is below. When I load this plugin it blocks dbus and fuse plugins so that they only reply to requests when the active window changes. Is there anything obvious here that would cause that? static Bool inactivePaintWindow (CompWindow *w, const

Hi, while porting "Group with tabs" to Compiz (http://forum.go-compiz.org/viewtopic.php?t=649), I noticed some things which are available in Beryl, but not in Compiz and which I believe Compiz should have, too: - Remembering of the last window state inside the state change notify This is useful for properly tracking down the window state changes (e.g. has the window been maximized in

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

Hello, I'm new to compiz and to this list but I'd like to contribute. I couldn't find a more appropriate place to ask a few questions about the compiz project (which is actually my first question). 1. Since the apparent compiz/beryl fork I don't see a compiz "community" site. Is there one? 2. Is compiz going to continue to be developed, and if so, is there a road

Greetings everybody! I was asked by someone (from the beryl-forum) if/how one could alter the values for the two color-stops used by the fallback-gradient of the skydome (for the case the supplied image could not be found). Up to now they were hardcoded, but with this patch they can be set via... /apps/compiz/plugins/cube/screen0/options/skydome_gradient_start_color

After several weeks of discussion the leaders of Compiz and Beryl have agreed that the two communities shall reunite. This decision is supported by both David and Quinn and represents the majority decision of the administrators and developers in each community. At this early stage not a lot has been decided, but these are the main points of the agreement: - As had previously been decided,

Beryl has a --skip-gl-yield ( I think now managed by --force-nvidia, dont really know though), that eases the use of beryl under heavy CPU load. Is this implemented in compiz? Cause compiz is _REALLY_ slow under heavy cpu use for me. Thanks, Joel -------------- next part -------------- An HTML attachment was scrubbed... URL: