> > Different developers will have different priorities. HD image data and async > readback both have potential benefits in image quality and nonblocking > responsiveness respectively. Here is an example of an application using > getImageData which would clearly benefit from HD, but it's not obvious that > async would be useful: > > http://mudcu.be/sketchpad/
This seems to be a use case for SVG and not canvas :) Dirk > > Here is another where HD helps but benefits of async are unclear, since it > does a pixel read-write-modify cycle: > > http://nerget.com/pressure/pressure.html > > Tying HD to async may hurt the adoption of both by requiring developers to > take two different code change hits when they only care about one. In > particular, the async change is likely to be more invasive to code structure. > If developers are discouraged, they may end up using neither. Thus, in my > opinion, these two enhancements to ImageData should stand and fall on their > own merits. > > Regards, > Maciej > > > > _______________________________________________ > webkit-dev mailing list > [email protected] > http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev _______________________________________________ webkit-dev mailing list [email protected] http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
