State of the Project: Ogre.rb

[Jason Roelofs]

It looks like I have to put Ogre.rb on hold for now. I am happy with the current state of the project, but continuing with SWIG promises to get increasingly problematic. I've now run into the wall that many other SWIG projects hit: lack of support for nested classes.

I've spent a good bit of time with the SWIG source, seeing how plausible / easy it would be to build in such functionality, and what I've found is disheartening. Basically, near a quarter of SWIG needs to be rewritten, including the YACC parser. I have no motivation in doing such a massive rewrite of a source code base I know very little about.

So after more research into possible alternate solutions, I have begun developing Boost.Ruby, built from the efforts of Boost.Python and luabind. Once I get enough basic functionality I'll release version 0.1 under the name rubybind, and this name will stay until formal acceptance into the Boost library itself.

After this project is in a decent state, I'll get back into Ogre.rb, starting from the beginning again building up the Ruby equivalent of pygccxml and py++, in the end building up a suite of projects to match python-ogre, and giving the Ruby community some much needed tools.

This of course will take a while. I will definitely support the current Ogre.rb as needed, fixing small bugs or easy to add pieces of functionality, but anything major will be put on hold. If anyone wants to try their hand at continuing the SWIG wrapper, send me and email and I'll get you set up.

Jason

[JeremyW...@gmail.com]

WOW! Good luck man. I wish I could help, but my programming skills
aren't that gangsta yet. I will talk to some people and see if anyone
is interested in helping out though.



~Jeremy