Hello Newsgroup People!
The Question is:
What do you consider good and bad in the various 2D APIs that you might
have used? I am looking for features that made your programming easier
and those features that seemed to just be a horrible decision on the
part of the one who designed the API.
Bonus Question for those who might have an opinion on OOP:
I am half-considering an Object-Oriented API. It is tempting and my OO
raytracer was awesome but I am not sure if it is appropriate here. The
benefits are pretty nice but I am not sure about the performance and
usability. I guess it is all in the design. I still have to decide
how the API is going to be implemented though
The Reason:
For my final semester project I have volunteered to take on the daunting
task of creating a cross-platform 2D API. I am probably going to regret
the decision but I am determined to stick with it. I don't want to be
overly complex since time is limited and I want to make it work in linux
using the my own basic functions, in DOS using my own basic functions
again, and in Windows using GDI. I plan to keep the implementation
simple but extending the API for more advanced operations shouldn't be
to difficult if it is well designed. I could copy the OpenGL API, the
older DirectX 2D API, SDL, or some other API but I want it to be as
original as possible.
BTW, hints and tips are greatly appreciated and will be received with
open arms and a big smile.
Thanks!
Matthew Hanna
|
