Hi Kevin, Don't worry, users will be able to see your existing and future animations. But as I said on the forums, first I want to create an extension mechanism to make it possible to use extra animations in the form of new plugins instead of adding more code/metadata to the animation plugin itself. This is to prevent the animation plugin from getting bigger and bigger, so that people who just use the basic animations (which is almost all users) don't observe longer and longer loading times with each added animation effect. Once this is done, you will be able to have a plugin, which implements your animations and which you will maintain yourself. This will also allow splitting the current animation plugin into 2 or more plugins, one of which would be an "animation-core" plugin.
For the metadata, this extension mechanism will probably require at least a change to animation option types (int -> string) and 2 new metadata tags to allow making animations from these extra plugins show up in animation selection lists in ccsm. (One in the target plugin metadata for each list option intended to be extensible, to "allow" other plugins to add extra options to that particular list, and one in the extension plugin to specify what new items to add to which plugin's which option, together with a handler in the code to handle that item). So I'd like this metadata addition to be generic enough to be usable not just for the animation plugin, but for other plugins as well (ones which would need such extensibility). I'm currently pretty busy, but I'm planning to do these in April. I can discuss this more then. I'll let you know if I need help. So, just hold on a little, and meanwhile you can work on other stuff or on new animations (and keep them as a patch for testers). Cheers, Erkin On Tue, Mar 18, 2008 at 10:36 AM, Kevin DuBois <[EMAIL PROTECTED]> wrote: > I've written a few animations (http://kdubois.net/?p=46), only to find out > that they won't get committed in an attempt to keep bloat to a minimum in > the animation plugin. From talking to the people on > [EMAIL PROTECTED], they told me that cornelius is working or > thinking of working on a way to make the animation plugin more > manageable/modular so that more animations can be introduced without > over-complicating the metadata and code base. If this is the case, and you > would like help on this, I'm volunteering I suppose : ) I'm most proficient > in C, but I can adapt if need be to deal with ccsm. Also, at the time being, > I'm working on writing a decoder for FFmpeg, and can work on this project > after that (7-10 days from now probably) With the amount of cool animations > still waiting to be coded up, I'm really looking forward to having a way > people can more easily pick what animations they deal with. > > Let me know what you think about this, and any suggestions or discussions of > how best to do this is most appreciated! > > -- > Kevin DuBois > [EMAIL PROTECTED] > PGP Key fingerprint = 80CF 7C1D 0A1C BE03 2203 95B6 1515 C3DC B6BE 7E88 > > _______________________________________________ > Dev mailing list > [email protected] > http://lists.compiz-fusion.org/mailman/listinfo/dev > > _______________________________________________ Dev mailing list [email protected] http://lists.compiz-fusion.org/mailman/listinfo/dev
