Thought about going to Google Closure?

[kevmoo]

I've used it a bunch for the box2d work we've done at Pixel Lab.

Not only do you get amazing compression, but it's wonderful at finding bugs and tightening up documentation.

https://github.com/thinkpixellab/box2dWeb

I didn't see a discussion forum for Easel, so my apologies for opening an issue.

[gskinner]

We are currently using google closure for compiling / minifying the EaselJS source.

[kevmoo]

Ooo...

Thoughts about using the Closure object model? -> http://code.google.com/closure/compiler/docs/js-for-compiler.html

You get a lot more love when you define types as closure requires. You can use their libraries, their vector types, etc.

Very very nice.

[mikechambers]

Thanks for pointing this out. As Grant mentions, we currently use Google Closure for compiling and minification, and are converting docs over to Yui Doc format. Doing a quick scan, it looks like they are pretty compatible.

Once I finish the doc conversion, I will work on making sure that it is compatible with Google Closures annotation tags.

More infon on Yui Doc on our wiki:
https://github.com/gskinner/EaselJS/wiki/Documentation

[kevmoo]

...and to double down.

As a user of Easel, one can just include the git repo as a submodule.

Then when I build my app w/ Easel, the compiler only includes the bits of Easel I use, which makes everything much smaller.

[kevmoo]

To be clear: using closure's doc format is not enough.

You need to move from
(function(window){ var p = x.Foo.prototype; ... }

to

goog.provide("Foo");
Foo.prototype.method = function() {};

[kevmoo]

...and I'm happy to help. :-)

[mikechambers]

Wont that require that anyone that uses EaselJS use the Google library stuff?

mike

[kevmoo]

Not at all, which really rocks.

There is a bit of work flagging your public surface area, but once that's done you get a completely contained library

...with whatever features of google closure JS you use (but only the features you use) baked in

If a user wants to just use your js file, great. No issues.

If a user wants to build against the Easel Sources w/ their own Closure project, then the above benefits (only include what they use, etc) come along.

[kevmoo]

Imagine you want to change the type of an API to be more specific...you get build errors on your samples if they don't comply with the new requirement.

...but you don't have to build as you're hacking if you don't want...the code works just great un-compiled.

It's magic. Makes me love JS.

...and it plugs in nicely with Coffee Script (http://jashkenas.github.com/coffee-script/) too