similar to: Extensible logging framework

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 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

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 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

I've started work on a rewrite of sorts for the dbus plugin that changes how it listens/responds to messages to make it possible to generate introspection data. The main changes are registering every plugin, screen, option, etc with dbus_connection_register_object_path and using libxml2 to generate the introspection data. This more or less works I just need to hook up the rest of the methods

FYI, I have put up a forum post [1] where I am going to maintain information about the netwm api for the dbus plugin. I have gone through the EWMH spec [2] and broken it down into a dbus compatible api, it seems to be good and roughly compatible with the existing compiz one. I think everything should be self explanitory, if there are any comments or if there is anything I have misunderstood or

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

0001-Do-not-use-shareList-for-multiple-screens.txt This is essential to get compiz to control multiple screens. I assume there's a better way though. We can either remove the shareList support entirely or we should check if it's supported or not. Improvements on this patch might be a good idea. In Beryl we chose to leave this as an option, but that doesn't strike me as the best

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

My recent work on Compiz-scheme has brought to my attention several problems preventing a real compiz extension language. Note that when I refer to an extension language, I am not referring to the ability to add plugins in some other languages, but more of something in the vein of emacs lisp. The major problem right now is extension languages are locked in to one plugin and what core exposes.

First, there are two fundamentally diffrent types of doing multihead: The "one big screen" solution, usually achieved with xinerama , twinview or similar. This provides us with one Screen, and therefor one CompScreen structure. The output extens are retrieved from xinerama, or possibly randr (in the future?), I would assume. Then there is the less used "multiscreen" way, which

I seem to be having problems with the latest dbus code. Here is a backtrace. This is happening at startup. Program received signal SIGSEGV, Segmentation fault. [Switching to Thread 47449612229888 (LWP 28353)] 0x00002b27b87991c0 in strlen () from /lib/libc.so.6 (gdb) bt #0 0x00002b27b87991c0 in strlen () from /lib/libc.so.6 #1 0x00002aaaac1b0657 in dbus_watch_handle () from

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

Linked is a version of the Beryl resize plugin which I have modified to work with Compiz. It seems to work better and has a few more options to help speed up things (the outline mode is good). http://www.anykeysoftware.co.uk/compiz/plugins/resize/resize.c Could you have a quick look at the code to see if it would be worthwhile preparing a diff? There are quite a few changes plus a lot of

For some reason all mozilla and open office menus are Normal type. This causes problems with all plugins which use the window type. This patch is applied to all plugins and seems to work flawlessly. I am submitting it for blur because the first window of all firefox menus are blurred. I know its a hack, but at least it should be fairly harmless inside each plugin. It is always marked with

Hi, well after some ever further investigation of some bugs, I ended up cleaning up the code, again. I also fixed some really heavy memory leaks in csvToList and made it in general more stable. Regards, Patrick "Marex" Niklaus -------------- next part -------------- A non-text attachment was scrubbed... Name: ini.c.patch Type: text/x-patch Size: 8275 bytes Desc: not available Url :

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

Here are my patches to add edge + button functionality. I still feel that there is a problem with gconf, but I have just made it so that the edge button functionality works. I have included a patch for gconf to display AnyButton if it is set to 0. There is also a patch to make the edge size configurable because 1 pixel was too small and the mouse keeps slipping off when using it for the

I'm trying to use custom functions for loaderLoadPlugin and loaderUnloadPlugin to register/unregister plugin paths in the dbus plugin as needed but I need to get access to a CompDisplay or DbusDisplay in order to do so. Is there any way to get access to this? -- Travis Watkins http://www.realistanew.com

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