LeeW
Settler
Registered: Jun 2005
Location:
Posts: 5 |
quote: Originally posted by muxec
Isn't SDL simplier to code due to it's intuitive API? |
Do you mean use SDL instead of the Mary Engine, or use SDL as the OpenGL renderer.
I'll answer both those questions, so it leaves no-one in any doubt.
Using SDL Instead of the Mary Engine
Using SDL instead of the Mary Engine would not be easier. SDL, which is a wrapper for OpenGL and has support for music and input, does not have the feature set of the Mary Engine.
The Mary Engine covers all the basics like sound support (using FMod and when they get into gear OpenAL), input support using the native system controls, rendering using DX (and as i said OpenGL in the future).
But the Mary Engine also has solid debugging tools, excellent support (with bugs being fixed within the hour in most cases), additional features such as an entire GUI set, texture and model viewers, heap management, all which make life easier for the programmer.
The interface is also pretty intuative, with standard naming convensions, standard ways of working etc.
While SDL is a solid wrapper for OpenGL, and is more than suited for people beginning to programmer, it doesn't, in my opinion, have enough features for a more advanced, or more complicated implementation.
Using SDL Instead of OpenGL in the Mary Engine
SDL is a wrapper for graphics, sound, input and more. The Mary Engine is a high level wrapper for graphics, sound and input.
Using SDL instead of OpenGL would lead to a whole world of toe stepping, and would increase the run time size of the Mary Engine an unacceptable amount.
SDL also covers a lot of the low level implementation, which the Mary Engine needs to access.
Hope that answers any questions
Lee
The Mary Engine
Report this post to a moderator |
|