AgateLib

Ok, I have uploaded an SVN snapshot of the next version of AgateLib here. The API is at the point where it is mostly stable, but there is still bug testing that needs to be done and there may still be some API changes. These things will go faster and be more complete if others can help out with the testing.

Edit: 0.3.0 has been released, so the preview download has been removed.

Documentation: http://www.agatelib.org/docs/docs-0.3.0/index.html

There are several breaking changes in the API if you want to migrate from 0.2.5. I'd recommend backing up your project before updating to 0.3.0. Below is a list of particular issues and fixes.

Namespaces no longer start with ERY.AgateLib, instead they are all in the AgateLib namespace
Suggested fix: Do a project or solution-wide search and replace for "ERY." and replace it with an empty string.

Classes related to drawing are moved to AgateLib.DisplayLib namespace.
Suggested fix: In any file that references Surface or Display, add "using AgateLib.DisplayLib;" to the top.

Classes related to audio are moved to AgateLib.AudioLib namespace.
Suggested fix: In any file that references SoundBuffer, Audio or Music, add "using AgateLib.AudioLib;" to the top.

Classes related to input are moved to AgateLib.InputLib namespace.
Suggested fix: In any file dealing with keyboard/mouse input add "using AgateLib.InputLib;" to the top.

Input class for interface is deprecated.
Suggested quick fix: Add "using AgateLib.InputLib.Old;" to any files using joystick input.
Long term fix: Migrate your code to use the AgateLib.InputLib.JoystickList class instead of the old Input class. The exact interface of this class might change before the real 0.3.0 release, so I suggest waiting before doing this fix.

The Sprite class has been replaced by a new version.
Suggested quick fix: Add "using AgateLib.Sprites.Old;" to any files using the Sprite class.
Long term fix: Migrate your code to use the new AgateLib.Sprites.Sprite class instead of the old Sprite class. This should be relatively painless but there may still be issues with the exact behavior.

This has not been thoroughly tested on Linux or Mac OS, so there may be problems with e.g. audio and joysticks working on those platforms. The display should work fine though.