I liked examples.. lots of coding examples just simple ones which then enables people to get something working without much thinking, from then on its easy to add.
Looking for feedback from those that have written plugins for CF or RR. What did you like and what didn't you like about how they did plugins?
examples is allways good, and documentation... With those two keywords, the imagination is the only stopper for a great plug-in
As someone who's coded for both RR and CF i find RRs method far more flexible. RR's plugin interface also has few easily to understand functions which provide a wealth of interaction between source and plugin whereas CF's interface required a bunch of methods just to get CF to see the plugin. Course i havent written a CF plugin in some time so that could have changed by now. RevFE's interface is nice too.. but VERY complex in the manner that you are basically transmitting/receiving calls on the fly.
How could you forget Ada? If it's good enough for the DoD, it's good enough for me.
(Does the DoD even use Ada anymore?)
So, where are we at as far as a plugin SDK goes?
And for designing skins (for serialization based plugins) - Have a look here:
And then let me know what else you had in mind...or whats missing...
Cheers, will have a look when I am on my .net PC.