similar to: Minutes of the Compiz Conference Call, 2009-02-02

Greetings everyone, Here are the minutes of the very first Compiz Conference Call, which took place today 2009-01-21. This was a combined IRC & phone meeting, huge thanks to Novell and Michael Meeks for setting up the conference call. The next Conference Call will take place on 2009-01-28. Feel free to comment these minutes and ask questions to be sorted out during the next meeting.

Greetings ! Here are the minutes of today's Compiz Conference Call. The next one will take place next week, time and date aren't frozen yet, we'll keep you up to date about this. Feel free to comment and stack new questions for next week. Regards, Guillaume ------------------------------------------------------------------------------ Conference Call 2009-01-28 Discussing the

Greetings, I'm pleased to announce that the compiz "core" repository has been moved from Freedesktop to the Compiz server. You'll find it at : git://git.compiz-fusion.org/compiz/core A few changes were made on the branches : * the former master is now compiz-legacy * the compiz++ branch was move to master * the compiz++ branch is still there, but just for legacy Some commits

On Sun, Sep 26, 2010 at 09:19:41AM +0800, Sam Spilsbury wrote: >> So I was looking forward to starting my day on a positive note until I >> scroll through the commit logs and see this: >> >> http://git.compiz.org/compiz /plugins/ezoom/commit/?id=aec55753c2b99764dbad6cd77832f0725b62ddcd >> >> Is this seriously how we can expect the project to function? > >

The Compiz 0.8.0 release will be the first release to include what was formerly known as Compiz Fusion. A complete feature and string freeze for Compiz 0.8 is in effect from Friday 5th of February, 23:59 GMT. I urge anyone with patches to submit them ASAP, regardless of their state. During most of Saturday, possibly spilling into Sunday, Compiz 0.8 will be branched and made ready for release.

Hi, I've currently pushed a new branch called "compiz++" to the freedesktop repository, with some features I've been working on during last months. Because most of the features also require (BIG) changes to the plugins, I've decided to put them all together. - No direct access to member variables: Everything is now done with getter and setter functions. This helps with the

Where are we going? It's time to start thinking ahead and really figure out how to make Compiz survive, specially in lieu of Dennis' suggestion. The reality is that there has been the equivalent of no progress since the merge. We've basically only been in maintenance mode. The reason for this, from my point of view, is a complete lack of direction and leadership. We've

Hi, I've currently pushed a new branch called "compiz++" to the freedesktop repository, with some features I've been working on during last months. Because most of the features also require (BIG) changes to the plugins, I've decided to put them all together. - No direct access to member variables: Everything is now done with getter and setter functions. This helps with

Hi, Suppose I have a compiz key-binding (let's say Ctrl and +) that performs a particular action (let's say maximization) and the current active application (say xterm) also does something with the same key-binding (zoom in xterm) - compiz handles the event and does not pass it on to the application. Is this desired behavior? Is the behavior configurable? Shouldn't compiz handle it

Sorry, I actidentally replied to the sender, sending copy to the list, because it might be relevant for others... Sorry for the confusion. Vojtech Kral -------- Original Message -------- Subject: Re: [compiz] multiscreen Date: 2013-01-09 23:59 From: Vojtech Kral <vojtech at kral.hk> To: "Brian J. Murrell" <brian at interlinx.bc.ca> Hello Brian, I actually use compiz on

I'm wondering what the status of multiscreen support is supposed to be in 0.9.7.12. Using Ubuntu Precise, it seems that compiz only manages 1 screen and if you want compiz on both screens of a dual screen set up you need to start two compiz sessions as such: $ DISPLAY=:0.0 compiz --replace $ DISPLAY=:0.1 compiz --replace What makes this all so strange is that even when one starts only the

I've been working on compiz++ ports during last weeks and I'm here to ask access to compiz++ plugins. I've already ported maximumize, put(+putplus) and grid. Can I get access? P.S.: Sorry for bad english. -- Eduardo Gurgel Pinho (GELSoL-UFC) (Gentoo) Linux User #415930 http://edgurgel.wordpress.com http://alu.dc.ufc.br/~eduardo -------------- next part -------------- An HTML

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

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

Compiz 0.8.4 is released! This is the second stable release of Compiz 0.8 series. This release brings two new plugins, translation updates, many bug fixes, improved stability, and better screen resolution change handling. Also included is additional integration work for KDE 4. In particular, window thumbnails are now supported in Plasma window tooltips with the new KDE compatibility plugin, the

hi, a small patch inspired from Kristian H?gsberg compiz-aiglx patch, to use compiz with xorg aiglx with tftp_damage patch and gl-include-inferior patch. this patch add command-line option to force bind and release whenever the texture is used. to use it you must start xorg in 16 depth mode, and start compiz with LIBGL_ALWAYS_INDIRECT environnement variable PS : sorry for my bad english

Hi, Compiz++ uses CompRegion instead of XRectangle, right? This patch tries to improve CompRect usability *First* I was using CompRect, but I've found that the only way to modify a CompRect is using setGeometry function: void CompOutput::setGeometry (int x1, int x2, int y1, int y2); So I created setX1, setY1, setX2, setY2 functions *Second* As you can see above, setGeometry uses:

I just branched for 0.8, since Danny told me there was no reason not to. There are still some bugs to work out of course, but since development has been quiet lately, I figure it's time to branch so that we can: 1. Eventually get to the next stable release 2. Allow people to work more freely on master On my personal list of things I want to see working better before a 0.8 release, I have

Last night I reworked compiz-aiglx patch from Kristian H?gsberg to get it working (i.e. patching and running) with latest compiz cvs. Most plugins and features are working again now : wobbly, minimize, resize, cube, rotate, move, fade, scale, place, zoom. However the last two plugins, switcher and decoration are broken. Decoration just draws nothing, I found that the problematic function call is

Danny, Kristian, All, First let me tell you guys whatever you are doing with compiz, keep it up! It's looking great! I have a new error on ArchLinux when running compiz 0.8.2.1 that I have never seen before. I installed Archlinux on 2 boxes to check it out. One on a x86_64 box with the nvidia driver (no problems there) and one on an i686 box with onboard intel video. When connecting over