Recently, I have been examining various 2D html APIs. I find the oCanvas API to be excellent.<p>In comparison with Raphael, I find that both libraries are good and useful.<p>In computer graphics, there are two main approaches for 2D: vector and bitmap. Each one has their situations where it is the most convenient.
Raphael is SVG based, vector graphics. oCanvas is html canvas based, bitmap graphics. So each one will have situations where it is the most convenient.<p>For example, scalable graphics, made of solid lines and shapes, are better suited with the vector approach. While diffuse images and image processing is better suited with the bitmap approach.<p>oCanvas employs object literals to accede to the various graphic operations. I find that makes the code more readable and thus easier to maintain, than the Raphael API, which makes use of plain function parameters for that.<p>Some differences that I found: Raphael have support for paths, vector fonts, and premade charts, which oCanvas doesn’t have.<p>On the other hand, oCanvas have support for animated sprites, scenes and timeline/game loop.