[Compcomm] Building and using the compiz-plugins-premerge stuff

[Erkin Bahceci]

Avoiding the option processing code altogether looks like a better way
to me than autogenerating that code with bcop. Have a look at the
example usage:
http://gitweb.freedesktop.org/?p=xorg/app/compiz.git;a=blobdiff;h=34023eb99a190421bdad14b15b77683ed5951ecc;hp=f933602da6792bd0aa07759dfc0e8ba54a3d433d;hb=294fd0a2133d4c8f37c3f60e4b35ca3bcb235f64;f=plugins/annotate.c

Regards,
Erkin

On 4/25/07, Erkin Bahceci <erkinbah at gmail.com> wrote:
> I was talking about this when I said bcop was becoming obsolete (at
> least for code generation):
>
> http://lists.freedesktop.org/archives/compiz/2007-April/002038.html
>
> I think I'll go with this instead of introducing a bcop dependency.  :)
>
> (Yes I know I still need to provide an xml, I can use the one Dennis
> pointed as a starting point).
>
> Cheers,
> Erkin
>
> On 4/24/07, Danny Baumann <dannybaumann at web.de> wrote:
> > Hi,
> >
> > > What about the new metadata stuff (that Annotate already uses for
> > > example)? Doesn't that make bcop obsolete? Is it the better way to do
> > > options now? I want to simplify the option processing in Animation,
> > > and am wondering what the better way is (I'd prefer not having extra
> > > dependencies though).
> >
> > No, it doesn't make it obsolete. You have to generate some metadata XML
> > file in any case in order to make future settings tools happy. BCOP uses
> > that XML and generates the option handling source code from it so the
> > code is automatically updated whenever you update the XML files. To add
> > an option, you just add it to the XML - which you have to do anyway -
> > and run BCOP. After that, you can start using it right away.
> > In my opinion, BCOP is the best way to handle option processing which is
> > available at the moment - but I am obviously a bit biased ;-)
> > The best idea most likely really is to have a short peek at a plugin
> > using BCOP (such as group as the complexity of group is similar to
> > animation) and the generated header files (e.g. group_options.h) to see
> > how the source code usage looks like and if it fits your needs.
> >
> > Regards,
> >
> > Danny
> >
> > _______________________________________________
> > CompComm mailing list
> > CompComm at Rock3d.org
> > http://www.ubaight.com/mailman/listinfo/compcomm
> >
>