Best Practices for Getting Started with SVG

re: Best Practices for Getting Started with SVG

Klimax — Sun, 30 Oct 2011 10:59:22 GMT

Just a small note: If you need compatibility with IE6-8 then you can use instead of SVG VML for old browsers - I think there are libraries to enable that. (conversion,creation of SVG/VML from other input,...)

re: Best Practices for Getting Started with SVG

Who — Sat, 29 Oct 2011 19:23:33 GMT

I knew Texas of the year 3013 would vote for the Xorbits.

re: Best Practices for Getting Started with SVG

Moderator — Sat, 29 Oct 2011 17:47:15 GMT

bashers and trolls desevers to be punished.. MS spank some butts here

re: Best Practices for Getting Started with SVG

Anthony Starks — Sat, 29 Oct 2011 14:07:57 GMT

At SVG Open 2011, I presented SVGo, a Go programming language library for generating SVG:

[1] SVGo Workshop slides from SVG Open 2011: speakerdeck.com/.../svgo-workshop

[2] Pictures generated with SVGo: www.flickr.com/.../72157623441699483

[3] Github repo: github.com/.../svgo

re: Best Practices for Getting Started with SVG

giuseppe — Sat, 29 Oct 2011 03:27:32 GMT

Harry Richter,

I wrote a clone of a simple, yet popular game in 2001. This was for adobe svg viewer 3 plugin.

Ten years later, the game (unmodified) runs on IE.

Not much has changed IMHO. Even playing soundeffects was not worse back then (different code though). Infact, porting the sound code to (early and wrong) html5 audio required far less modifications than trying to make a standards compliant html page work in IE6.

you quote "Better late and correct than early and wrong!".

"Early and wrong!" what? My experience, as outlined above suggests otherwise.

I wont upload my game as proof. But in 2001, much like today, there were few websites focusing on SVG development. One that made life noticably easier was by Kevin Lindsey:

http://www.kevlindev.com/

The samples are from 2004 or earlier. The ones sans SMIL appear to work in IE9.

Early but not so wrong.

Thus I believe this one is more appropriate: "Better now [soon] than never".

However, I will not be thankful to MSFT just for finally allowing the world to benefit from something, it could have had for years.

MSFT does a lot of great things. Holding back the web was not one of them. No valid excuses. And no clear signs that this won't be attempted again.

I do not know how your post or opinion was motivated. Maybe you know valid technical reasons for the late arrival of SVG, but those might not be obvious to others, e.g. me, and thus it requires further explaination, ideally a priori.

re: Best Practices for Getting Started with SVG

TheSmurfs — Sat, 29 Oct 2011 00:32:29 GMT

Hey Microsoft, I'd like to point out a problem with the quality of Direct2D's implementation of shape rendering:

www.youtube.com/watch

1:33 to 2:40

nvidia calls this problem "conflation" meaning you're conflating opacity information and coverage information instead of keeping them separate. (This page also talks about the problem too: http://www.antigrain.com/svg/ ).

Also worth mentioning is that the 4:37 mark of the youtube video shows what happens when Direct2D renders high frequency textures - ugly Moire artifacts.

Could you guys pass these problems onto the D2D team, I have no idea how to contact them.

re: Best Practices for Getting Started with SVG

Ivan — Fri, 28 Oct 2011 18:59:32 GMT

How long as css2 been out?

.opaque1 { // for all other browsers

opacity: .5;

}

.opaque2 { // for IE5-7

filter: alpha(opacity=50);

}

.opaque3 { // for IE8

-ms-filter:"progid:DXImageTransform.Microsoft.Alpha(Opacity=50)";

}

re: Best Practices for Getting Started with SVG

Harry Richter — Fri, 28 Oct 2011 13:07:58 GMT

If I understand you correctly the real issue is "Better late and correct than early and wrong!".

That has been the Microsoft way for a long time, and I prefer it to the OpChroFox way of having features that are either not finalized or implemented in a wrong way. The trouble is, many so-called tests on the web (e.g. html5test.com) simply check for the availability of a feature and not the correctness of the implementation. This leads to the oversimplified “Stupid IE – this and that feature is missing!”. However I think that a feature that is incorrectly implemented is as bad (or even worse) than a missing feature.

So in the end the score on SVG is IE: 1 vs. OpChroFox: 0!

Harry

re: Best Practices for Getting Started with SVG

Richard — Fri, 28 Oct 2011 10:27:35 GMT

@Helen - Yeah, stupid IE holding back SVG while everyone implemented properly. Oh, except neither Chrome (14) or Firefox (7) deals with the changing-CSS on the map above (and even inconsistantly with each other) and Chrome draws a scrollable area around the fruit, inconsistant with Firefox.

Stupid IE.

re: Best Practices for Getting Started with SVG

Stifu — Fri, 28 Oct 2011 06:03:47 GMT

@Helen: haha, indeed.

I like how the IE team only started to acknowledge and mention SVG once IE9 started supporting it. Before that, they wouldn't answer questions about it, and acted like it didn't exist.