On Tue, 17 May 2011 17:51:22 +1200, Sean Healy <jalopeura@xxxxxxxxxxx> wrote:
Basically my idea at this point is to get some kind of interface generator framework going, and smooth out the wrinkles by creating the interfaces for a number of classes for two target languages. Then adding new classes is as easy as writing a new interface definition, and supporting new languages is as "easy" as writing a new generator.
Probably its not that easy (but almost :) ). I would assume that the be-api is not 100% consistent but a interface definition must be 100% sound. Because of that there is no 1:1 mapping be-api <-> IDL thus you need some wrapper to fix it.
Otherwise I really like the idea because you also can generate other cool stuff from the IDL. For example a scripting interface e.g. to automatically enable scripting support for all interface properties, this is a bit tedious to implement at the moment. Or proxy classes for an interprocess call framework, or even internetwork calls... Sorry for repeating me.
cheers,
Clemens
