11–20 of 24 posts
Check out the capabilities of the specification. http://www.w3.org/TR/SVGMobile12/ It appears I just discovered a valuable, free, resource with untapped potential. Happy Hacking!
Writing a specification with awesome capabilities is a lot easier than writing the software.
Earlier quoted context omitted.
A more pressing problem with SVG is that it is like every other W3C standard: bloated, unwieldy, and obfuscated. Not to mention that SVG does not have all the capabilities of PS. PS is a complete turing complete language specialized for drawing vector graphics. SVG is more restricted and certainly slower to work with, not as well supported, and very very verbose.
> [...] and very very verbose it's possible to write compact SVG. For example, it has a simple and very compact sub-language for specifying paths (with one-letter commands): http://www.w3.org/TR/SVG/paths.html#PathDataBNF What do you mean by 'not as well supported'? SVG is supported by Firefox, Opera and Webkit (Safari / Chrome). I'm not aware of any Browser that supports Postscript. As for turing complete: SVG is fu…
Earlier quoted context omitted.
A more pressing problem with SVG is that it is like every other W3C standard: bloated, unwieldy, and obfuscated. Not to mention that SVG does not have all the capabilities of PS. PS is a complete turing complete language specialized for drawing vector graphics. SVG is more restricted and certainly slower to work with, not as well supported, and very very verbose.
> [...] and very very verbose it's possible to write compact SVG. For example, it has a simple and very compact sub-language for specifying paths (with one-letter commands): http://www.w3.org/TR/SVG/paths.html#PathDataBNF What do you mean by 'not as well supported'? SVG is supported by Firefox, Opera and Webkit (Safari / Chrome). I'm not aware of any Browser that supports Postscript. As for turing complete: SVG is fu…
As for Silverlight and AIR, well, they might taste like pumpkin pie, but I wouldn't know, etc.
( p.s. for anybody using WebKit nightlies: http://webkit.org/blog-files/animation-demo.svg )
Considering the standard has been in development ( http://en.wikipedia.org/wiki/Svg ) since 1999 (10 years ??) this is a sad state... the future of app development? The article thankfully mentions IE exactly once. Microsoft does not officially support SVG, you need a plugin. Even Chrome does not support the SVG 1.1 standard fully, as per the wikipedia article. Browsers need a standard, natively supported graphics lib…
I had never heard about vml. According to wikipedia it is used by google maps as a replacement for svg in ie. That surprised me too: svg is actually being used by a very useful site.
Check out the capabilities of the specification. http://www.w3.org/TR/SVGMobile12/ It appears I just discovered a valuable, free, resource with untapped potential. Happy Hacking!
SVG itself has no good implementations. Does SVG mobile? Writing a specification with awesome capabilities is a lot easier than writing the software.
Earlier quoted context omitted.
A more pressing problem with SVG is that it is like every other W3C standard: bloated, unwieldy, and obfuscated. Not to mention that SVG does not have all the capabilities of PS. PS is a complete turing complete language specialized for drawing vector graphics. SVG is more restricted and certainly slower to work with, not as well supported, and very very verbose.
> [...] and very very verbose it's possible to write compact SVG. For example, it has a simple and very compact sub-language for specifying paths (with one-letter commands): http://www.w3.org/TR/SVG/paths.html#PathDataBNF What do you mean by 'not as well supported'? SVG is supported by Firefox, Opera and Webkit (Safari / Chrome). I'm not aware of any Browser that supports Postscript. As for turing complete: SVG is fu…
As to the turing completeness of SVG, how efficiently can JS transform vectors in comparison to PS. Not very fast.
Also, nobody wants to draw just paths.
Earlier quoted context omitted.
> [...] and very very verbose it's possible to write compact SVG. For example, it has a simple and very compact sub-language for specifying paths (with one-letter commands): http://www.w3.org/TR/SVG/paths.html#PathDataBNF What do you mean by 'not as well supported'? SVG is supported by Firefox, Opera and Webkit (Safari / Chrome). I'm not aware of any Browser that supports Postscript. As for turing complete: SVG is fu…
Every linux box in existence supports PS, very well. So does every PDF reader. That covers over 80% of all computers. Extending this support could be done through a plugin. Compare this to the fact that IE does not support SVG and PS is a far better standard to work with in terms of vector drawing. As to the turing completeness of SVG, how efficiently can JS transform vectors in comparison to PS. Not very fast. Also,…
I don't think every PDF reader supports PostScript very well. Is that what you meant to say?
worthwhile comment by jonathansnook: "The problem with the current state of HTML is that it’s elements for interactivity are quite limited without JavaScript. We have a limited set of form elements and then we fall back to the page request/response of old. This is a problem that SVG does not solve. Sure, it might make certain presentation elements easier to create but that’s more of a CSS issue than an HTML issue. Th…
A more pressing problem with SVG is that it is like every other W3C standard: bloated, unwieldy, and obfuscated. Not to mention that SVG does not have all the capabilities of PS. PS is a complete turing complete language specialized for drawing vector graphics. SVG is more restricted and certainly slower to work with, not as well supported, and very very verbose.
