[clayasaurus]

Why did you decide on doing a full port instead of creating a C wrapper for ogre and exposing D to this?

I'm also considering pro's / cons of porting a whole C++ library vs creating a C wrapper.

If you create a C wrapper you don't have to worry about bugs introduced through the porting process, can keep up to date easily, and will take less time and effort.

If you go with a full port, you get the original beauty of the library (Object Oriented) and you get to use all the D features on it, but it takes a whole lot longer and is harder to keep up to date, plus you might manage to create new bugs in the conversion to a new language.

I'm wondering if you've thought these issues over and if so, why have you decided on doing a full port?

Thanks

~ Clay

[larsivi]

[csauls]

Basically what larsivi said. Although, in the -- what, two years?! -- since I proposed the Sinbad project, I've been wondering if I had exactly the right idea. Namely, should we port OGRE, or should we write something new and original, with a large shameless influence from OGRE, and other libraries.

Oh, and another reason I wanted to port instead of wrap, was because I was (am) invisioning an add-on library providing 3D Sound capabilities directly in the OGRE objects. So an object would not only represent, say, a radio sitting on a table, but also the sounds/music that go with it, so that volume and panning can be calculated almost automatically. Good Times had by all.

One of the hangups (possibly the biggest one) has actually been the volatile nature of the D platform. I think I mentioned in some other thread that I'm personally waiting for two things: a D release worth sitting on for the project (I actually think we're pretty close!) and more personal free time to devote to it. The latter might prove difficult, sadly.
_________________
Chris Nicholson-Sauls