Hi Nigel, Sounds like the image/canvas world is in limbo. Which brings 2 questions to my mind.
1. What is required to get one of the 2 APIs into the release? You mentioned that you are not committed to supporting either API. How do we get that commitment to move the project forward? 2. If canvas is the better of the 2 APIs (or more likely to be released), is there a list of action items to complete on the canvas API? Personally, I would imagine that designing and solidifying the Imaging API seems easier and simpler. That is, a set of APIs surrounding image access and manipulation are fairly well-bounded problem. The world of HTML 5 is still evolving and changing. As a result, it might be the better long term candidate, but it also might be years before HTML 5 solidifies into a deployed (or deployable) form. Thanks Dave On Jan 14, 5:12 pm, Nigel Tao <[email protected]> wrote: > In my understanding, the key point is that both the Imaging or Canvas > APIs are still considered experimental. > > In particular, their APIs aren't frozen, and until we finalize an API > that we want to commit to maintaining, neither API has been publically > released. Also, there is enough overlap between the two APIs (the > Canvas API arguably offers a superset of the Image API's > functionality) that it seems silly to try to launch both, and whilst > the Image API (which came first) is more or less complete, the > (currently partially implemented) Canvas API is probably the better > long-term candidate, given that the <canvas> that inspired it is part > of the HTML5 specification. > > Unfortunately, I don't know anyone who is actively working on this. > But if you were to pick one API to contribute code to, I would > recommend the Canvas API.
