Eihort Support

I've recently been testing Mogre for use in a project, and I've been really impressed with its features and stability. However I also would like to use some of the new features of eihort. Are there plans to synchronize mogre with eihort, or is support of eihort a bit uncertain? I really would prefer to use Mogre, but if I feel like it will lose support like Ogre .NET, I'm going to have to go with the stable but less productive route, and keep using Ogre.

Bekas is waiting for Eihort to be released before supporting Eihort. It makes sense from a maintainance standpoint.. as, there is no garuntee Eihort API will not change several times until then, making more work for Bekas.

Ok thanks pjcast. All I wanted to do was ensure there WILL be eihort support. It makes sense to wait until the interfaces are frozen so he doesn't have to redo work.

After being spoiled using ogre in a managed language I'm glad I don't have to go back.

Hopefully, whoever takes the responsibility for the future of Mogre will be able to handle the conversion of Eihort.

I realize I am a relative newcomer, so my advice is just merely a suggestion.

Bekas, perhaps if you provided the tools and instructions to more than 1 individual... then the chance of the project disappearing would be much lower after you leave in May.

A really nice an through wiki article or series of articles would probably go a long way.

BTW, I just read this on the Ogre mainpage:

For those of you eagerly awaiting the next stable version, codenamed 'Eihort' or 1.4.x, rest assured it's coming. We're working really hard to make sure it's a killer - whilst we didn't manage the end of the year as we'd tentatively planned, the small amount of extra waiting will be worth it, and a release candidate is very close. We still encourage any experienced users to grab the latest from CVS and play with it - it's really very stable the majority of the time and testing is always welcome. Please just check the Porting Notes for the things you need to know to upgrade your applications.

Bekas, perhaps if you provided the tools and instructions to more than 1 individual... then the chance of the project disappearing would be much lower after you leave in May.
If nobody steps up before Eihort, I'll put all the tools and instructions on sourceforge. In that case I'll remove the auto-generated files and in order to build Eihort-Mogre you'd have to use the tools.

It will complicate the build process but those who get it right will likely be able to update to new versions of Ogre by their own (and hopefully somebody will offer to put out a SDK for the others).

I've worked with some automatic wrapping code before, but if your tools do what I think they are doing (namely the unmanaged/managed internal object references), you've got a very nice set of features to make public, not just for wrapping Ogre. I, for one, would like to look at them.