search for: dransfield

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

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:

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

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

It seems to me that the plugin dependencies are not flexible enough for most plugins. The particular problem I am thinking about is animation/group and fade. They both specify RuleAfter but compiz interprets that as 'load after AND require it', there is a Require rule, but this relates to features not plugins. I would like to propose these changes and definitions, they seem more logical

Resending this as the message size limit for the list is 100 KB, and uncompressed, the attached plugin code is 150 KB. ---------- Forwarded message ---------- Date: Thu, 12 Oct 2006 23:47:25 +0300 (EEST) From: Tuukka Hastrup <Tuukka.Hastrup@iki.fi> To: Mike Dransfield <mike@blueroot.co.uk> Cc: compiz@lists.freedesktop.org Subject: Re: [compiz] Privates example? On Thu, 12 Oct 2006, Mike Dransfield wrote: > I have looked around but I cannot find an example of how to use the > privates system. > > Could someone give me a quick example of the usa...

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

Here are a few extra attributes which I have not seen mentioned yet which I think would be useful. Any comments would be appreciated. *Version* The version of the plugin, I think the reasons for this are obvious. <version> <major>0</major> <minor>1</minor> <patch>0</patch> </version> *Addition to features* Just add an attribute to

There's now an extensible window matching interface in head. Initial commit message: Add extensible match interface. Match objects can be used for window matching but other objects than windows will likely be supported sometime soon. A match object contains a boolean tree of expressions and each expression can be implemented by a different plugin. The core interface only

I have just updated the place plugin to use integers rather than strings with restrictions (as per the other plugins). The only thing which is now using the N_ macro is windowTypeString which I think can be removed. I think some plugins may still be using this so I have not removed it just yet. Once this is gone it will be possible to remove the N_ macro as well, is this OK? Regards Mike

I think I have a slight problem with the new hookable plugins and the ini plugin. I haven't looked into it too much, but the plugins use an option to store their abi version. This value is stored so that when the cube/scale plugins are updated it will not be changed and things will not work. Do we need some sort of flag to tell ini not to save these options? I assume that it is OK for

I am fairly sure that this is just a bug in the codes logic, but I thought I should check first I noticed that the function was always returning true if only one grab is checked for (maybe other cases too) If nobody shouts I shall commit it because the behaviour in my plugin is now as expected. -------------- next part -------------- diff --git a/src/screen.c b/src/screen.c index

There is a problem with some window specific actions like scale_group and rotate_with_window when they are activated by an edgebutton. The basic problem is that each of those actions use the window option provided to the action. When an edgebutton is used the window id sent is actually the id of the edge window, this means that actions which rely on this stop working. The obvious solution would

Here is a quick patch for dbus to make it try to load the metadata from a file if the plugin is not loaded. I have tested it and it works fine, but I wanted to check to see if you had something else in mind. -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: dbus-offline-descriptions.txt Url:

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

Here are some example plugins for anyone who is interested in developing. They are helloworld - uses an action to write hello world to the terminal blackandwhite - just makes all windows black and white triangle - paints a triangle to the screen http://www.anykeysoftware.co.uk/compiz/plugins/example-plugins.tar.gz If anyone has any other simple examples, please can you send them to me and I