Mainloop
Posted: Mon Nov 19, 2007 1:15 pm
I figured I should write about my progress as well.
Let's first look what we have done until now:
From the tutorials from the Ogre wiki we got to know the engine and how to use it. One tutorial dealt with omitting the "ExampleApplication"-Framework which is used in every tutorial in also in the examples. The result there was our orxonox main class at the moment.
Then 1337 tried to put the Ogre stuff into separate functions and classes, but in the end wasn't that satisfied with what he did.
I work right now on the game's main classes and functions and I came to the conclusion that 1337's approach isn't that bad actually. Some things he did cannot be done easier and are inevitable, so I guess I do it like him. With an eye on the old Orxonox implementation I came to a small framework which works great, but will need a lot other classes that are under development right now (like the class hierarchy) or are not developed at the moment.
I'm not sure yet if some stuff which is missing (like file and directory handling or command line interpretation) should be developed again (needs lot's of time) or just adopted from the old implementation.
I myself think, that the evil stuff which broke the old Orxonox code did not happen that far down in the framework so it should be save to use those things.
On the other hand there may be libraries which help (also for the two examples I mentioned).
Let's first look what we have done until now:
From the tutorials from the Ogre wiki we got to know the engine and how to use it. One tutorial dealt with omitting the "ExampleApplication"-Framework which is used in every tutorial in also in the examples. The result there was our orxonox main class at the moment.
Then 1337 tried to put the Ogre stuff into separate functions and classes, but in the end wasn't that satisfied with what he did.
I work right now on the game's main classes and functions and I came to the conclusion that 1337's approach isn't that bad actually. Some things he did cannot be done easier and are inevitable, so I guess I do it like him. With an eye on the old Orxonox implementation I came to a small framework which works great, but will need a lot other classes that are under development right now (like the class hierarchy) or are not developed at the moment.
I'm not sure yet if some stuff which is missing (like file and directory handling or command line interpretation) should be developed again (needs lot's of time) or just adopted from the old implementation.
I myself think, that the evil stuff which broke the old Orxonox code did not happen that far down in the framework so it should be save to use those things.
On the other hand there may be libraries which help (also for the two examples I mentioned).