Closed GoogleCodeExporter closed 8 years ago
Original comment by bfatt...@gmail.com
on 9 Nov 2010 at 2:32
Changing priority to low
Original comment by bfatt...@gmail.com
on 23 Nov 2010 at 5:16
The decision has been made to drop support for SVG. It is not as
programmatically competent as Canvas and has issues which don't make it
appropriate for game development.
Original comment by bfatt...@gmail.com
on 2 Jun 2011 at 12:54
Could you please provide more information? In what way is SVG not as
"programmatically competent" as Canvas? What issues make it inappropriate for
game development?
I'm not arguing that renderengine should support SVG, but you seem to be
claiming that _no one_ should use SVG for games, which I can't accept without
some evidence.
Thanks ...
Original comment by code.mon...@gmail.com
on 2 Jun 2011 at 9:33
I make no claim that people shouldn't use SVG for games. However, SVG is,
for all intents and purposes, a first-class HTML extension. It isn't meant
to be addressed programmatically via JavaScript in the same way the Canvas
is. It presents many of the same challenges as the HTML rendering context
already in The Render Engine. That being said, someone could write a SVG
rendering context for The Render Engine and contribute it back, but I won't
be the one to do it. Three things that I feel make it inappropriate for
game development:
1) There is no state or transform stack like Canvas
2) There isn't a simple way to do sub-image manipulation in SVG
3) There isn't any pixel-level manipulation
- Brett
Original comment by bfatt...@gmail.com
on 13 Jun 2011 at 7:28
Original issue reported on code.google.com by
bfatt...@gmail.com
on 3 Aug 2010 at 2:02