Slashdot Mirror

← Back to Stories (view on slashdot.org)

WVG : The New Scalable Vector Graphics

Posted by timothy on from the actually-its-name-is-homer dept.

jafro_svg writes "While the press has discussed Microsoft's upcoming 'Sparkle' as a potential Flash-killer - the technology arena on which Microsoft's new technology is having the most impact is SVG. SVG (now a W3 standard for 3 yeras) was itself billed as a Flash-killer some years ago, and speculation about how it might be accepted into the mainstream for developers (i.e. incorporated into IE) now seems inevitable -- you see, Sparkle's real name is WVG and is 90% identical to SVG." Jafro_svg also points out this online SVG tutorial.

3 of 432 comments (clear)

  1. Damn Microsoft! by Temporal · · Score: 4, Funny

    As usual, Microsoft ignores the standards and does its own thing. Why can't they be standards-compliant for once?

    Wait a minute...

    On a serious note, someone once submitted some art to an open source video game project I run in SVG format. I thought it was pretty neat that I could resize the image without losing visual quality, but I was rather put off by the size. The file just seemed way too big for the data it contained. On a whim, I opened it up in a text editor, and what did I find? DUM DUM DUUUMMMMM.... XML!

    Arg! Why!? What's next, raster images in XML? I can see it now...

    <rasterImage>
    <pixel>
    <color>
    <red type="hexidecimalValue">FF</red>
    <green type="hexidecimalValue">FF</red>
    <blue type="hexidecimalValue">00</red>
    </color>
    </pixe l>
    <pixel>
    <color>
    <red type="hexidecimalValue">FF</red>
    <green type="hexidecimalValue">80</red>
    <blue type="hexidecimalValue">80</red>
    </color>
    </pixe l>
    ...
    </rasterImage>

    Your comment violated the "postercomment" compression filter. Try less whitespace and/or less repetition. Comment aborted. Your comment violated the "postercomment" compression filter. Try less whitespace and/or less repetition. Comment aborted. Your comment violated the "postercomment" compression filter. Try less whitespace and/or less repetition. Comment aborted.

  2. 90 Percent SVG, huh? by PourYourselfSomeTea · · Score: 5, Funny
    That means the other 10% will break down like so...
    • 5% obfuscating the namespace with ties to the .NET Framework
    • 2% smart tags. These will make your WVG document "smart" -- that is, allow MS to rewrite part of your graphics that might offend them. I see penguins looking longingly out of windows in your future, Mr Graphic Designer!
    • 1% "extensions" Like, it would be really cool if you got a new <wvg:clippy> tag that would pop up every time you opened an wvg document in I.E!
    • 1.99% Buzzwords that make WVG sound like a revolutionary B2B 99.999% uptime .NET-aware DRM-enabled, secure techonology solution for "helping you reach your creative potential in today's competitive marketplace." These, of course, will all be patented and made freely available under an obscure license which will confuse early adopters into implementing them, hopefully putting them directly into the Linux kernel and opening up a brand new SCO-like can of legal worms! These will also make WVG documents playable ONLY in Windows Media Player
    • 0.1% Security enhancements. Like ties to VBScript objects that can execute arbitrary code on your box.
  3. Re:So... by dimator · · Score: 4, Funny

    I'll take a Microsoft standard, which at least is answerable to market forces; over stuff published by unimaginative committees anyday

    It is to laugh! Unimaginative committees? Microsoft is damn near duping a standard created through the W3, and you call the committee unimaginative?

    You're right, though. Who nees open standards and peer review, when there's a monopolist we can all follow like sheep.

    --
    python -c "x='python -c %sx=%s; print x%%(chr(34),repr(x),chr(34))%s'; print x%(chr(34),repr(x),chr(34))"