similar to: Advice to plugin developers during 0.9

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

I thought we removed place, or was that something that was agreed but never executed? The plugin has been virtually untouched since wall and expo got popular, and I don't really want to support it for 0.8. Unless someone has any strong objections, it'll be removed later this evening. I'm sorry about the short notice, but I'm fairly sure this has been briefly discussed before

This is a somewhat controversial subject which I only reluctantly bring up. I honestly believe that open discussion is the only way to run a project, and I apologize in advance if I offend anyone. I got what should have been an easy question on #compiz a few days ago. A user came in and asked "What version do you recommend I use?". I honestly didn't know what to say. >From a

On Mon, Nov 17, 2014 at 11:11 AM, Sam Spilsbury <smspillaz at gmail.com> wrote: > > On Thu, Nov 13, 2014 at 3:28 AM, Kristian Lyngstøl > <kristian at bohemians.org> wrote: > > So to sum up: Equal stability, fewer features, but actively maintained. > > > > In the end I told the user in question that 0.9.12.0 is the latest > stable version, but 0.8.9 has

Hi, On Thu, Nov 13, 2014 at 3:28 AM, Kristian Lyngstøl <kristian at bohemians.org> wrote: > > Feature-wise, Compiz 0.9.12.0 actually has fewer features as I understand it. With the move to OpenGL ES, several plugins got dropped. I understand some of that has been remedied, but 0.9 still does not come out ahead if my understanding is correct. I have asked around and this is what

I've been trying to come up with some good coding standards, but I've realized that most of us already know most of this. So instead of trying to define every aspect of how we code Compiz-code, I'll try to outline some of the finer points. For a more complete list, you can review any of the many coding-standard documents out there (For Linux, FreeBSD or any other project). Part of

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

For the last few weeks I've been fiddling with the 0.8 code-base, mostly because compiz got nuked in my distro and I had to do something, if for no other reason than to have a running WM. You can find my work at: https://github.com/KristianLyng/compiz (I'm also tracking issues there) I've done what I felt like doing, some of which would've been controversial/problematic 5 years

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 Kristian, On Fri, Nov 21, 2014 at 1:37 AM, Kristian Lyngstøl <kristian at bohemians.org> wrote: > For the last few weeks I've been fiddling with the 0.8 code-base, mostly > because compiz got nuked in my distro and I had to do something, if for no > other reason than to have a running WM. You can find my work at: > > https://github.com/KristianLyng/compiz >

At the moment, Compiz draws each head at a time, shifting the glViewport() for every head in a xinerama-like setup. However, the projection matrix is NOT adjusted. This means any translation along the z-axis will cause problems and any rotation along the x/y axis, because the projection matrix is centered around the viewport, not the actual X screen as it has to be to keep the scenery together. I

We were a little imprecise in our original announcement with regards to moving away from freedesktop.org, which seems to have caused some confusion. We are only moving away from the freedesktop.org infrastructure. NOT the standards. By moving away from freedesktop.org, we are: - Shutting down bug-submission on bugs.freedesktop.org. We will be using bugs.opencompositing.org which will soon be

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

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.

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

Hi, The attached core patch makes the 'isFocussable' getter in CompWindow wrappable. This way, plugins such as winrules can make core's getter function return a different value to the one stored internally without actually having to modify the value. Kind Regards, Sam -- Sam Spilsbury -------------- next part -------------- A non-text attachment was scrubbed... Name:

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

Hi, currently, we have a bunch of stuff in compiz core that is entirely Gnome specific, though it's designed to be general. What I mean is - arbitrary command bindings - terminal and screenshot command bindings - "main menu" and "run dialog" toolkit actions Neither of those is handled by the window manager outside of Gnome. Hence I propose doing the following: - Add a

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