- From: Robert O'Callahan <robert@ocallahan.org>
- Date: Mon, 14 Sep 2009 20:37:50 +1200
On Mon, Sep 14, 2009 at 7:43 PM, Ian Hickson <ian at hixie.ch> wrote: > I agree that sometimes antialiasing leads to seams, though; the solution > to that isn't to disable antialiasing, though (that would just replace one > problem with another), the solution is to provide new features that allow > you to create composite paths that are stroked or filled in one operation > (with one single antialiasing step) instead of requiring multiple distinct > operations (each with their own antialiasing). > That often isn't possible because the information required is not available. For example, if you were implementing a Postscript interpreter on top of canvas, you couldn't do this. Rob -- "He was pierced for our transgressions, he was crushed for our iniquities; the punishment that brought us peace was upon him, and by his wounds we are healed. We all, like sheep, have gone astray, each of us has turned to his own way; and the LORD has laid on him the iniquity of us all." [Isaiah 53:5-6] -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.whatwg.org/pipermail/whatwg-whatwg.org/attachments/20090914/3c8dde9f/attachment.htm>
Received on Monday, 14 September 2009 01:37:50 UTC