actionscript3 isometric library (v1/v2)
One of the mistakes I made in making the as3isolib.v1 was going at it alone. I did my research and investigated best practices but I didn’t engage a community like I should. The result is a great library, but a flawed library with many architectural issues. While these issues can be circumvented with minimal effort, it’s bothersome to me as the architect of this project that they are present.
I don’t want to make the same mistake in developing v2. Since April 2010, I have engaged several prolific flash game developers: in helping me inspect v2 code; discuss architectural ideas; and getting the best performance out of the Flash Player. Now it’s time to start engaging the community. I want your input to help drive the as3isolib.v2.
In order to kick this off I want to start taking polls. Then once the as3isolib.v2.core gets to a testable state, I will engage some of the community in closed testing. That testing will help me to develop the tools for the as3isolib.v2.builder app.
Without further adieu I present the first poll.
Now I am somewhat OCD and can mull over naming something for months. Rather than wasting precious development time hem-hawing over a good naming convention, I’d much rather get your input on it. There are 4-5 core classes that are used to create content with the as3isolib.v2: an engine, a camera, a canvas, a scene which contains entities. While most developers could care less about the verbosity of how something is named (thanks to code-completion technology), there is something to be said about readability. Parsing hundreds of lines of code is tough enough. Having to pick out hard-to-read strings of text in that code is tougher. So here are the naming conventions I am thinking about: