adnanullah / atmospherejs Goto Github PK

Currently a reference to the canvas context is being passed into each library function. This means all objects share the same context which can potentially cause a performance bottleneck.

TODO:

1. Change the function signatures to accept a DOM node instead of a Canvas object
2. Dynamically create a Canvas node per object and store the reference to that node internally.

See http://stackoverflow.com/questions/8205828/html5-canvas-performance-and-optimization-tips-tricks-and-coding-best-practices for more info.

Each component of AtmosphereJS should be a plugin module, similar to the way YUI and JQuery allow custom extensions to be written. This will also help keep file sizes down as you should only need to include items you're referencing.

This will probably require some re-architecture of library and should probably be tied to a new milestone.

Make use of bezier curves to draw a single cloud shape rather than use compound shapes. This allows for better detailing/shadows/transparency etc.

The beizer curves used for moon rendering are a little off (see lhs of object rendered), need investigate why and how to fix.

Stick to the DRY principle!

Check commits against JSLint site to validate adherence to JS coding standards.

Currently, the x, y and ratio values have a different weighting per object need to standardise this behaviour. To ensure consistent rendering.