6 Comments

1. 

   Rezmason February 1, 2011 at 5:52pm

   If by “bounds support” you mean implementing methods such as Flash’s getBounds(), I’m stunned. EaselJS is already a huge deal. Implementing getBounds() would be a giant leap forward, considering all the things that it is useful for.

   Some kind of filter support would be neat, but it’d be a low priority compared with what you’re currently working on.

   Keep up the good work!

2. 

   CaioToOn! February 2, 2011 at 4:13am

   Good, Grant! Awesome library. It’s a shame such a huge advance on HTML/CSS and Javascript still be so poor in dev features.

3. 

   Daniel Ribeiro February 2, 2011 at 7:18am

   Hi,

   Having support for Coffeescript would be nice as well (When extending a class like Shape and invoking it’s super method, it only invokes the DisplayObject constructor, not the Shape’s).

   Also, a better implementation for _testHit might be:
   
Container.prototype._testHit = function(x, y, ctx) {
try {
return ctx.getImageData(x, y, 1, 1).data[3] > 1;
} catch (e) {
return null;
}
};


   This way, firefox will not throw error on every tick when using drag and drop, like the drag and drop example.

4. 

   tstrokes February 2, 2011 at 11:22am

   I was wondering if the new interaction model will including touch events. It would be great if drag and drop worked on iOS and android. I was also curious if you could give a sneak peek of the API for new interaction model. Anyway, easel is looking great and I hope to use it on an upcoming physics simulation project I’ll be working on. Thanks.

5. 

   Daniel Ribeiro February 3, 2011 at 7:40am

   I solved the lack of recursive clone on container. I’ve uploaded on github’s gist the patch:

   * Coffeescritp version: https://gist.github.com/809538

   * Its compiled (in JS) version: https://gist.github.com/809539

6. 

   NanoMind February 7, 2011 at 12:01am

   Thank you !! I love AS3 and I’am still looking for ways to move beyond flash alone…..

   Thanks again

   NanoMind