About the movieClip, I’ll test if it’s possible to pass the document class as a Sprite. If it is possible, maybe Sprite can be a solution.

We won’t have foruns or versioning with BPE but I’d love to hear from everyone. From the feedback we received, we could change the whole blit engine (and probably will make some changes) and we made the code available to help but also, to hear from other devs.

Feel free to pass your email in the Contact Us form so we can exchange other info and thanks.

I guess I’m probably coming at this from a strange place, as I’ve never used (and don’t have plans to use) the Flash Authoring Environment. I use straight AS3 and generally use a Sprite as my main class, since I have no need for the time line.

Since MovieClip extends Sprite, I would think that having a main Sprite, rather than main MovieClip would be more flexible, since then either should be able to be passed to Manager.startupToolkit().

Your library, though, so it’s obviously your call.

I have lots of other questions (and possible suggestions) regarding the code, but I assume this isn’t the forum in which to discuss things in detail.

I do have a couple general questions, though:

Will you be setting up a forum and publicly readable repo (hg or git, perhaps) for BPE?

Are you interested in detailed feedback (perhaps including patches)? If so, how would you like that feedback (email, here, a forum to come, etc.?).

Regardless of all that, thanks so much for releasing this code!

I love the concepts of simplicity, flexibility, and “use what you need”. As cool as some of the other libraries currently out there for AS3 are, I think they all have issues with being either overly complex, overly constrained to their own way of doing things, or both. BPE (that name’s gonna be easy to mix up with PBE! ;P ) seems not to have gone down either of those paths, yet.

There are two main reasons for it: 1. the movieclip can be the document class, which is ok for fast prototyping and; 2. it can be the holder where you put all the stuff for preloading.

The Loop manager originaly had a sprite to take care of the ENTER_FRAME event, but since we had that movieclip around, I put all in the same plate.

Regarding Engine, I’m wondering if you meant the Scene class… IIRC Engine doesn’t need a movieclip.

One thing that jumps right out as I begin looking over the source is that the ToolKit classes Loop and Engine assume the use of a MovieClip.

Could you perhaps address your reasons for using MovieClip instead of the more general (and less costly) Sprite?

private const RECT:Number = 1; // Straight path cost
private const DIAG:Number = Math.sqrt(RECT * 2);// Diagonal path cost

But still, nice little framework! Perfect for getting started.

Tough question… the idea started building up with the Music class that was created with Tech Wars, our first flash game. Most of the toolkit exists since the original Atomik Kaos, but the tricky part is the blit engine and in my opinion, it is the blit engine that defines this v1.

Our current contract is a three game project of which we are in charge of two of them and those two have the v0.9 of the engine present, blit included. That’s why we delayed the release, because we wanted the engine to go through a tough test before it was out. So answering your question directly, these two games have a fully function BPE running. In fact if it wasn’t for these two, we wouldn’t have the blit engine running.