Google Brings SVG Support To IE 233
stelt writes "Scalable Vector Graphics (SVG) is in most graphical tools. It is used heavily in many big projects, such as KDE and Wikipedia. But Internet Explorer's lack of built-in support for SVG was keeping it away from mainstream use on the web. Google is fixing that now with a JavaScript drop-in named SVGWeb. They've posted a quick, one-minute overview, a longer and more detailed presentation, and you can read about it on the project page."
Lame. (Score:5, Informative)
From the project page: "No downloads or plugins are necessary other than Flash ..."
Actual Link to the Demos (Score:1, Informative)
The summary misses the actual link to the demos. Here it is:
http://codinginparadise.org/projects/svgweb/samples/demo.html
Re:An interesting link.. (Score:3, Informative)
Interestingly enough, the "use your mouse to zoom" on that map does not zoom within Google Chrome.
Re:Incompatibility Problems (Score:3, Informative)
Ok, now try READING the summary instead of skimming it.
They're saying IE's lack of built-in support for SVG was keeping SVG from mainstream use.
Re:Lame. (Score:4, Informative)
My concern is that many websites that use SVG will require Flash on all browsers, not just the ones using IE.
Quote from the quick start:
You can override this manually, but why would anyone do that for other purposes than debugging...?
Re:Incompatibility Problems (Score:5, Informative)
Welcome to 2009, IE has ~60% usage and falling: http://en.wikipedia.org/wiki/Usage_share_of_web_browsers [wikipedia.org]
Re:Incompatibility Problems (Score:5, Informative)
This has the potential to do things like allow you to use the HTML5 video tag indiscriminately, and have it render natively where it's supported, and have it default to Flash where it's not. And finally, if you've ever done a lot of work with SVG, you'd notice that the Adobe plugin often renders scenes in drastically different ways than native implementations. Basically, it was to SVG what IE6 was to the web: a broken implementation. Google's project is still in it's early incarnation and already surpasses the Adobe plugin. Hopefully in the next year or so, it'll match native implementations well enough to allow web developers to use SVG and SMIL, and not have to worry about legacy browser compatibility.
And if you'd watched the one minute video running through it, you'd know most of this
Re: from the particular to the general (Score:2, Informative)
"Flash sucks bleep on Linux, because Adobe apparently hates Linux or something. "
No, your assumption is mistaken... in fact, Linux is becoming more important to Flash over the next year, as smartphones and televisions introduce new configurations.
For performance which is slower than other machines, first try checking for background processes or browser chokepoints... that's easier than checking for hardware which creates the difference.
Then look into the Player betas, feedback process. If we can make your slowdown happen in the shop too, then we'd want to try to ameliorate that situation within the common Player, thanks.
jd/adobe
Re:Incompatibility Problems (Score:2, Informative)
Re:Incompatibility Problems (Score:3, Informative)
Re:Incompatibility Problems (Score:3, Informative)
How long until Google or someone else hacks around this?
Given how often Microsoft updates IE for major changes *cough*, I'd say this won't be a problem, no.
IE 7 did minor but important changes, and IE 8 is something like an exception. Otherwise I think the lastr major engine/standards update was with, uh, IE 4?
IE 8 is MS trying desperately to hang on when browser benchmarking is this moments hot topic, with the competing browsers pushing new version with higher and higher benchmark scores. They have never release a follow-up browser so quickly before. There's nothing new and of value in IE 8 that hasn't already been seen in other browsers. What goes for IE 7, well let's be honest here, it can't be compared to IE 6 as calling IE 6 a browser should be prohibited by law.