[SDL] Non-API changes I'd like to see in SDL 2.0

[Sam Lantinga]

> 1. No CMake or other Make front-ends.

Using a make front end is not planned at this point.  Maintaining the
various projects is a pain, but there are some advantages like having a
configuration on Windows that doesn't require C runtime, having a build
target that takes care of creating a DMG with custom background image, etc.

You're also always free to create your own Makefile for your own needs,
as has been done for some of the enbedded platforms.

> 2. No Libtool.

Heheh, I actually tried to ditch libtool early in SDL 1.3 development
and the scripts I ended up writing were just as messy and hard to maintain
as libtool itself.  libtool is a known quantity for the package maintainers
for various operating systems, so I ended up keeping that and ditching 
automake instead.

> 3. Lib binary should be libSDL.so.2 on Linux SDL2.dll on Windows.

See above.

Actually I hacked libtool to generate an unversioned SDL.dll on Windows
because that's what Windows developers expect.  The naming convention for
SDL 1.3/2.0 isn't finalized at this point, but I expect to call it something
like SDL2.dll.

> 4. Proper API Specification

SDL 1.3 has many of the headers converted over to doxygen friendly formatting.
Once the API is finalized and robustly tested I'll probably put out a call to
create a formal API specification to someone with extensive standards experience.

> 5. ABI Specification(s)

> Related to 4; a product developer may want to expose their own
> implementation of SDL, a clear ABI specification would be necessary to
> facilitate this, as is done with OpenGL...

Interesting idea that I hadn't considered.  First things first though. :)

See ya!
	-Sam Lantinga, Lead Software Engineer, Blizzard Entertainment