similar to: "Which version should I use?"

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

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

compiz.org hasn't been updated properly in almost half a decade, and there's a lot of misleading or downright wrong information out there right now. There's a launchpad ticket on it [1], but the subject isn't quite covered by a simple bug as it stands. First thing first: Compiz has been using version 0.9 for almost half a decade, and clearly deviated from past conventions of

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

Hi, I've been experiencing serious tearing in compiz when screen is painted only partly. Either "Sync To Vblank" option in compiz doesn't work or copying repainted parts from backbuffer to frontbuffer is too slow. And since many people rely on driver's implementation of Sync to Vblank, it would be optimal to always use glXSwapBuffers. This can be accomplished via keeping

On 11/10/2014 12:45 PM, Kristian Lyngstøl wrote: > > First thing first: Compiz has been using version 0.9 for almost half a decade, and clearly deviated from past > conventions of using 0.<odd> for development and 0.<even> for stable. In addition, a fourth digit has been added. > > In the long run I'd like to see the project drop the fourth digit and instead go

For any that are interested, I am assuming position as maintainer of upstream 0.8 stable branches. More details here: http://blog.northfield.ws/wordpress/ Thank You, Scott Moreau -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.freedesktop.org/archives/compiz/attachments/20141120/8710845c/attachment.html>

Here's a compiz patch to assume the presence of a sane glXSwapBuffer implementation (i.e. one that uses page flips synchronized to vblank). It adds --no-wait and --always-swap options, which, if used with the swapbuffers patchset, will make compiz use the page flipping path for tear-free drawing. Jesse -------------- next part -------------- A non-text attachment was scrubbed... Name:

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

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

On 7/27/07, dragoran <drago01 at gmail.com> wrote: > On 7/27/07, Matthias Clasen <mclasen at redhat.com> wrote: > > Given that test1 is around the corner, I thought it might be a good idea > > to give a little status update on the features that the desktop team has > > been working on for F8: > > what happend to compiz-fusion? I've been punting this

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

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 just updated compiz in fedora rawhide and wanted to post a quick overview of the patches we still carry. Patch details are available here: http://cvs.fedora.redhat.com/viewcvs/rpms/compiz/devel terminate-move.patch restart.patch These are already upstream, but not yet in a released version. aiglx-defaults.patch tfp-server-extension.patch These two paper over a problem in

Hi, I've revisited compiz on aiglx and at this point, if you're running rawhide (fedora development), it's a matter of installing the i386 RPM found here: http://people.redhat.com/krh/compiz/ There's a SRPM there too for other architectures, rebuild using rpmbuild --rebuild compiz-0.0.13.fedora1-3.src.rpm To run compiz, first start the gnome-window-decorator process in

I've been using compiz on KDE for a while now and I like the eye candy. Thanks to all who made this possible. I'm usually a no-nonsense guy who doesn't care about eye candy (I'm not even using a background picture because I'm worried about the memory it'll use (on a machine with 2 GB of RAM) :) ) but compiz stormed (sic!) my defences. Now for my questions: 1. compiz is a

As 0.9 will contain numerous core-changes which are likely to affect both behavior and plugin development, the recommended way of developing new plugins throughout 0.9 will be to use the released developer versions, NOT master. The exceptions are plugins that are already part of the release and plugins that depend on functionality that only exist in master. This will allow plugin developers to

Hi, We've been fixing a few bugs and glitches in our fedora compiz rpm and I wanted to post them here for review, in the hope that we could get them included before the upcoming release. Without further ado: cow.patch - add support for using the composite overlay window for GL output instead of rendering to the root window. This is lets compiz run on AIGLX without the

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: