Feedback, code patches, etc.

Ultimately, I'd like to have the users of AnsiGL be the top contributors to the direction the project takes. The more stable, easy-to-use, and feature-complete things are, the nicer everything will be for all of us. :)

So with that in mind, to all of those who might be already be using AnsiGL: Please, don't be afraid to post feedback! There are multiple kinds of feedback that are absolutely valuable to the project. The discussion area has a few forums available for this already, and feedback about this project page is also welcome!

• Generic Overall Feedback

Feedback of all kinds is welcomed (yes, even scathing hate mail), but keep in mind, constructive feedback will far more valuable and is absolutely the preferred feedback format. I'd love to know if AnsiGL is being used, how much of the library is actually utilized, what parts you like, dislike, etc. This can range from feedback on the overall design of the project all of the way to what the default options should be for window borders and everything in-between.

• Bug Reports / Code Patches

In the case of bugs, reporting is the fast way to get them on the developer radar so they can be fixed, and fixing them yourself and submitting a code patch is probably the fast way to get them resolved.

Because of my personal project-handling style, bug fixes will take priority over new features more often than not (for a variety of reasons).

• Feature Requests

Feature requests are absolutely essential to the growth of the project. I can only dream up so much before I'm just about out of ideas...fresh ideas of any kind have the potential to kick up some interesting development goals that might not be quite as out of reach as you might think.

• Unit Testing

This may seem out of place, but the AnsiGL project is now actually a sum of multiple projects, and each plays a critical role to the quality of the overall project as a whole. This is a special request for feedback and improvement specifically for this (and other future) AnsiGL developer tools.

While it isn't directly a part of the project, I have to mention again about how helpful unit testing has been. The library as a whole should be much more stable, and perhaps most important, it should act as expected. The foundation classes for the whole project have been rather thoroughly tested at this point, and the "higher-level" classes are next.

Let me know what you think!