Hi I just tried out the new 0.1.0 release of beryl. Generally I do like the compiz fdo version, because I like the gconf integration and the metacity theme support in gwd. Also I think their configuration system is a complete mess, this beryl settings manager is completly bloated in my opinion. Anyway, I noticed they have quite a lot of plugins. While I found most of them nothing special, the "animation" plugin really fascinated me. It just looks awesome! Any chance, anybody with serious coding skill could have a look at it so that David will add it to the fdo tree? I'd love to use compiz with animation support! I wanted to attach the current animation.c which is in beryl svn, but it's too big. Anyway it's in the svn and it's GPL. Greets Fabio
On Tuesday 03 October 2006 6:51 pm, Fabio Berta wrote:> Hi > > Also I think their configuration system > is a complete messAnd a registry editor is better?> , this beryl settings manager is completly bloated in > my opinion.You really don't know programming to make that statement. ONE file makes it bloated? (it's all GTK+ GUI written in C, writing GTK widgets in pure C without glade and stuff tends to make code bigger). Look Fabio, beryl is a friendly fork, It's not meant to punish compiz. If you noticed, I've been making beryl support gtk-window-manager as one of the supported decorators. Debian will soon have beryl and it will support gtk-window-decorator also (once I do some more cleanups to the packaging). David is doing a great job. And, truth be told, forks foster competition but it also creates new ideas that both compiz and beryl benefit from. I would certainly like beryl's plugins to go into compiz of course as long as the ABIs don't dirverge too much. Shawn.> > > _______________________________________________ > compiz mailing list > compiz@lists.freedesktop.org > http://lists.freedesktop.org/mailman/listinfo/compiz
Attached is the animation plugin slightly adjusted for compiz rather than beryl There are 2 naughty patches for compiz.h and window.c which will need to be applied before it will compile. These should be dome with privates instead but I have just done a quick patch. In the zip is a schema file for it too, install it with gconftool-2 --install-schema-file=animation.schemas I have tested it quickly and everything seems to work properly, it was just a bit of cut and paste so the schema file might be a bit wrong. Fabio Berta wrote:> Hi > > I just tried out the new 0.1.0 release of beryl. Generally I do like the > compiz fdo version, because I like the gconf integration and the > metacity theme support in gwd. Also I think their configuration system > is a complete mess, this beryl settings manager is completly bloated in > my opinion. > Anyway, I noticed they have quite a lot of plugins. While I found most > of them nothing special, the "animation" plugin really fascinated me. It > just looks awesome! Any chance, anybody with serious coding skill could > have a look at it so that David will add it to the fdo tree? I'd love to > use compiz with animation support! > I wanted to attach the current animation.c which is in beryl svn, but > it's too big. Anyway it's in the svn and it's GPL. > > Greets > Fabio > > > _______________________________________________ > compiz mailing list > compiz@lists.freedesktop.org > http://lists.freedesktop.org/mailman/listinfo/compiz >-------------- next part -------------- A non-text attachment was scrubbed... Name: animation-for-compiz.tar.gz Type: application/gzip Size: 22492 bytes Desc: not available Url : http://lists.freedesktop.org/archives/compiz/attachments/20061004/c1351963/animation-for-compiz.tar-0001.bin
Hi, I strongly suggest taking animation.c in Beryl svn rev. 465 or later instead of the version you attached, since the code has undergone lots of improvements (including better performance and new features), fixing, and cleaning up this week. The schema file should also be updated for the new version. I admit that I should have used the "privates" facility instead of putting disablePostprocessFX in compiz.h/beryl.h (this is used to communicate with blurfx in Beryl). I'll fix that some time. But indexCount would better go in the header file next to vCount, (the "vertex count = index count" assumption of Wobbly is not valid in Animation). Also, Wobbly would better be updated too, to use indexCount (and maybe texCoordSize) as is the case in wobbly.c in Beryl now. - Erkin
On 10/4/06, David Reveman <davidr@novell.com> wrote:> I understand that it's a replacement and sure, if it proves to be stable > and well maintained I'll gladly deprecate the minimize plugin. However, > minimize effects are likely going to be implemented in other plugins and > it seems that especially the tracking of the icon geometry property > would be nice to share.Sure, makes sense. When and into which file will that function go then?> You can always host it somewhere else. I'm working on making sure that > it's easy to use plugins that aren't hosted in the compiz repository at > fdo. I'd like to avoid having a lot of code in the compiz repository > that isn't maintained.Ok, that suits me. I just won't be able to do testing and conversion for Compiz. Someone else who uses Compiz daily can do those. But I can look into problems if someone lets me know about them. - Erkin
Hi, I had thought that inter-plugin communication was possible through "privates" without adding anything to compiz.h, but apparently it's not (hence the name privates :) ). I guess this is only possible through X window properties, right? Is there a way to do this type of communication in a simpler way (and without modifying compiz.h)? Anyways. For now, I removed everything related to disablePostprocessFX for Animation to work with Compiz. I might have a go at X window properties, later. I attached the diff files that should be applied *after* you apply Mike's last diff files. Hopefully this will get Animation to work with Compiz properly. - Erkin On 10/4/06, Erkin Bahceci <erkinbah@gmail.com> wrote:> On 10/4/06, David Reveman <davidr@novell.com> wrote: > > > I understand that it's a replacement and sure, if it proves to be stable > > and well maintained I'll gladly deprecate the minimize plugin. However, > > minimize effects are likely going to be implemented in other plugins and > > it seems that especially the tracking of the icon geometry property > > would be nice to share. > > Sure, makes sense. When and into which file will that function go then? > > > > You can always host it somewhere else. I'm working on making sure that > > it's easy to use plugins that aren't hosted in the compiz repository at > > fdo. I'd like to avoid having a lot of code in the compiz repository > > that isn't maintained. > > Ok, that suits me. I just won't be able to do testing and conversion > for Compiz. Someone else who uses Compiz daily can do those. But I can > look into problems if someone lets me know about them. > > - Erkin >-------------- next part -------------- A non-text attachment was scrubbed... Name: animation-for-compiz.tar.gz Type: application/x-gzip Size: 3184 bytes Desc: not available Url : http://lists.freedesktop.org/archives/compiz/attachments/20061004/edce04b3/animation-for-compiz.tar.bin
On Wed, 2006-10-04 at 14:16 -0500, Erkin Bahceci wrote:> On 10/4/06, David Reveman <davidr@novell.com> wrote: > > > I understand that it's a replacement and sure, if it proves to be stable > > and well maintained I'll gladly deprecate the minimize plugin. However, > > minimize effects are likely going to be implemented in other plugins and > > it seems that especially the tracking of the icon geometry property > > would be nice to share. > > Sure, makes sense. When and into which file will that function go then?There should be a Rectangle for the icon geometry in CompWindow and it should be monitored like all other properties. minimize and animation plugins should just use this Rectangle instead of reading the property.> > > > You can always host it somewhere else. I'm working on making sure that > > it's easy to use plugins that aren't hosted in the compiz repository at > > fdo. I'd like to avoid having a lot of code in the compiz repository > > that isn't maintained. > > Ok, that suits me. I just won't be able to do testing and conversion > for Compiz. Someone else who uses Compiz daily can do those. But I can > look into problems if someone lets me know about them. > > - Erkin-David