Updates 11/28/05

I got a bunch of updates from Rastaman over the past few weeks... I just didn't have the time to do it all until now.

There is one small bug in OgreNet... I'm not sure of the cause, so I'll post the errors here.

\ogredotnet\ogrenet\controllervaluefloathandler.cs(56,15): error CS0246: The type or namespace name 'CVFHGetValueDelegate' could not be found (are you missing a using directive or an assembly reference?)
\ogredotnet\ogrenet\controllervaluefloathandler.cs(73,15): error CS0246: The type or namespace name 'CVFHSetValueDelegate' could not be found (are you missing a using directive or an assembly reference?)
\ogredotnet\OgreNet\ControllerFunctionFloatHandler.cs(51,15): error CS0246: The type or namespace name 'CFFHCalculateDelegate' could not be found (are you missing a using directive or an assembly reference?)
\ogredotnet\OgreNet\ControllerFunctionFloatHandler.cs(69,15): error CS0246: The type or namespace name 'CFFHGetAdjustedInputDelegate' could not be found (are you missing a using directive or an assembly reference?)


Anyone have any ideas?

there should be a OgreNet/Custom/ControllerFloatDelegates.cs
Not seeing it in cvs. It also needs to be added to the OgreNet Project.

Got it... CVS updated...

It's all compiling now.

Awesome job leading EagleEye! Great seeing all those jumping in to help, great work guys.
Sorry I was gone for so long. I'll have to grab cvs update asap.

Awesome job leading EagleEye! Great seeing all those jumping in to help, great work guys.
Sorry I was gone for so long. I'll have to grab cvs update asap.

Hey Danno! Have you heard from Maleficus at all?

I'm back too. Been away developing a complimentary open-source project called Lu4Net at www.lu4net.com. It's v0.8, and I'll be incorporating it into Realmforge. I'll be working with the OgreNet stuff again this weekend, and try to pick up where I left off. You'll see me posting again soon, as I make progress or run into issues.

Hey Danno! Have you heard from Maleficus at all?

No, I haven't. Sure wish he'd come back though.

Hey Danno! Have you heard from Maleficus at all?

No, I haven't. Sure wish he'd come back though.

Ya know, I honestly don't think it's in his nature to just drop off the face of the earth... I fear he may have had something bad happen to him.

Where do you guys stand with leadership of the project?

I'm an avid SWIG, C++, and C# developer. If you guys need some help on things I'd be more than happy to pitch in.

Edit: Do you guys generate the code that is in the CVS? It seems like a lot of work to manually rename every ogre function.

hay Clay
yes we need people that know swig. I only started using swig about 4 weeks ago.
we make the .i files and a few custom things. Is there another way? I think the renaming is allot of work too. that's why I haven't done much in the updates I made.

I know you like python, have you tried boo http://boo.codehaus.org/
I just converted the DemoCEGUI to boo get it here http://www.ceejs.com/eric/DemoCEGUI.Boo.zip

If you tell SWIG to output to XML instead of C#, it will give you an XML file describing every class/function it finds. Then you can parse the XML to auto-generate the %rename files. I would suggest adding an empty file to CVS called OgreRename.i, and generate it every time you make a major change. Another thing is you are writing the attributes (or whatever you call them in C#) manually:

public override string Name {
get
{
return GetName();
}
}

That's also a LOT of typing. You should define a macro. This is what it looks like in PyOgre's archive:

%ogre_attribute(Entity, string, name, getName);
And this generates the attribute. In the long run, doing everything manually like this is going to kill you. It takes too much effort to keep it up-to-date.

With a few #defines I would be willing to bet the swig source for PyOgre will compile for C#. It has a lot more of the library wrapped that the current CVS for ogredotnet. It might be worth while to see if we can combine efforts to make a universally compilable SWIG interface to generate C#, Python, Java...what-have-you.

Anywho. I have finals for the next few weeks...ending around the 16th (sigh college). After that I'll see what I can do to help out.

thanks for the info on #define gotta check that out.

I think combinning pyogre's and ogredotnet's swig interface would be cool. we defninitly need to work on this. I did check out PyOgre but could not make heads or tails of it . When you get a chance please explain a bit on how it works. look like the .pyste file are like .i file and you use another tool to build it all. well in the next couple of days ill take a look at it again.

Wrong source tree. =)

The one that's in Ogre's addons directory is the "old" pyogre, which used Boost.Python. The "new" pyogre is located here:
https://developer.berlios.de/projects/pyogre/

As soon as I get out of class for the semester I'll start work trying to get it to compile for C#.

Right now almost every .i file is Python specific. I'll need to go through and put
#ifdef PYTHON_BUILD
...
#endif
Around those sections (or convert them to be language neutral). Then add those #def gaurds around the ogre_attribute macros, and create a set of macros for #define CS_BUILD.

Just as soon as finals are over...

Hi Clay,

I could'nt download pyogre 2 times.
Maybe your server has been off over the weekend.
I have compiled ogredotnet from ogresdk-1.0.6 and the cvs-2005-11-04.
By using VS2005 there are still some memory leaks in there.
So I hope your swig-ing is better for me. Otherwise I have to start from
zero.

mamba

BerliOS can do that sometimes. Are you talking about subversion checkout? I've seen it down once, but never twice in one weekend.

Don't forget there might be mem leaks in SWIG as well. It's sometimes hard to track down where memory leaking occurs in a library generated by SWIG. Sometimes it's the user's fault, sometimes it's SWIG's fault.

OK

?good to know about swig?
but the swig examples are working ...

then I try to find some leaks.
So I can train myself with swig-ing.

Also I will have a look at pyogre.

mamba

Ooops, since I posted a note above saying "I'm back", I wanted to post a note saying the opposite now. With the loss of Maleficus and loss of momentum on OgreNet (and the personal headaches I had with the RealmForge port to use it), and the increased interest in completing Axiom, we're now switching back to Axiom, for now. Borillis is leading the Axiom development, and taking volunteers. We're dividing up the namespaces of Ogre, and doing it collaboratively.

I wish you best of luck, and wanted to tell you "we'll be back" and are looking forward to seeing your success. Hopefully, others will work out the kinks, and we can ride on their coat-tails. For now, we're (me and dannomite) are migrating back to help out with the completion of the Axiom port of Ogre 1.06.

... in case you were interested. We're planning to implement the DotNet3D namespace interfaces in both Axiom and Cegui#, fyi.