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

[Danny Baumann]

Hi,

> To be honest, I never really understood this part, Adding a define
> is down to personal preference and is more of a clean up exercise.
> Adding the structure in get*Options is obviously needed somewhere
> and David made a recent change so that you do not need to modify
> set*Option anymore (the most annoying part Ill agree).

You still have to add your option at a number of places:
- add it in Init(Screen|Display)Options
- add it (at least the case <foo>: part) in set(Screen|Display)Option
- depending on what option you have, add screen action handling stuff or
matchUpdate or similar

Don't you think using the metadata which must be present anyway to
generate that boring code part is much more elegant than having to write
the code by yourself?

> I thought BCOP was so that you could produce a beryl compatible
> plugin as well as a Compiz compatible one with the same source code.
> Is this not the case?

Well, this was the initial idea...but BCOP evolved away from that. I
don't think it makes too much sense to generate Beryl compatible code
now, anyway (and current BCOP isn't even able to do that) ;-)

> Would it not be possible for those using bcop to generate the required
> files when they make a change?  I think it would make everyones lives
> much easier.

What do you mean by that? I do not get that question...'make a change'
to what file? If you mean to regenerate the source when editing the XML
- this is already done.

Regards,

Danny