Mozilla Gets (Beta) Native SVG support
Rushuru writes "Mozilla is getting a beta native SVG support. Previously one had to use 3rd party plugins such as that from Adobe, and they only worked on windows. SVG is similar in scope to Flash, but it is a W3 recommendation (i.e. a standard) and uses an open format. The project page has more info."
SVG is a great format for reporting. A much cleaner & potentially more interactive way of displaying complex data than just "static, text and jpgs". Check out the adobe SVG site (http://www.adobe.com/svg), they have some great examples.
And yes, people will use it as a flash wannabe. But that's a good thing as far as I'm concerned - moving from a semi-proprietary format (I know the flash format is *kinda* open) to a standards based format - and XML based, no less.
Read reviews of shopping cart software
*Finally*, I can start saying SVG is going to be supported natively in a browser, and pushing through projects on that basis.
..."
Until now, I've had to say you can use IE, then get an addon from Adobe. "What? Why doesn't MS support this SVG thing natively? What if Adobe decides to drop support for SVG; then what happens?
This is the best news I've read on Slashdot for a while
There's nothing inherently wrong with the technology just because some people will use it for stupid things.
... get one that looks good on screen and also prints well, instead of the horrible blocky printed crap you get with GIF/JPG.
Your post was stupid, but I don't think we should abolish the alphabet because of it.
Some things are better represented in vector graphics and this can be a great tool for that type of thing. Why waste bandwidth transmitting the same map over and over (for different zooms) when you could just get one that is zoomable on the client end? Need a printable diagram
and yet people still use IE. As a web designer, I have to ask, "WHY!?"
Quid festinatio swallonis est aetherfuga inonusti?
Africus aut Europaeus?
and why? because there is no cross platform working websolution for it. ... and make it what it is supposed to be, a webstandard.
:)
So if it's by default in mozille (firebird), it might finally push SVG
And finally you don't have to use our redmonds frieds beloved software, to create dynamic( read: flash ( like )) pages.
damn if this ain't going to be standart (maybe you can get a option in Firebird or a compiler option like '--disable-svg' ) but might be you want '--disable-art-*' too... what ever
i'd be very sad if this would not become a part of mozilla.( firebird ) by default.
I do, however, pray thay SVG isn't included into standard mozilla (or any other browser) until it's reached maturity (which its page indicates it's pretty far from). I spend too much of my time working around the half-assed CSS implementations of older netscape and IE browsers, and I don't want another decade of worrying about which part of the SVG standard was implemented buggily (sp?) by which version of which browser.
I'm all for beta releases, developer's builds, etc., as the team needs as much feedback from as full an SVG authoring community as it can. But as soon as someone starts authoring sites that depend on the weird vagaries of one browser or another's SVG misimplementation, we'll be going down a painfull bug-for-bug compatibility road. Caveat.
## W.Finlay McWalter ## http://www.mcwalter.org ##
I believe the current Mozilla and the Firebird branch share a codebase. In either case you can always decide to compile this in if you so wish but at least for now it shouldn't be compiled in by default. As always you have the choice of what comes in Mozilla.. because you have the source.
SVG makes as much sense to have compiled in as support for jpeg, gif, or png graphics. It's just a vector based image format.
At what price learning? At what cost wisdom? The price is a man's peace of mind, and the cost is his life.
A common technique in web development is to serve things in a compressed format. Virtually all browsers support this by transparently decompressing the files after they are recieved. This is part of HTTP (content-encoding).
Binary, already-compressed file formats don't benefit from this, but XML-based formats benefit a great deal. In practice, there won't be much difference in size between SVG and Flash, for the vast majority of people.
SVG is really much, much more than a vector based image format though; it's an entire animation/effects plugin which will work seamlessly with current standards such as XHTML, MathML, CSS, and JavaScript (ECMAScript if you wish to be technical).
Adobe has already placed some very nice demos of embedding SVG within standard web pages. Take a look at some of the things that can be done with it, and you'll quickly see how the SVG standard can
As far as the extra size in download goes, most people have to download Acrobat Reader to read PDF files, which are very common on the web. If SVG ever achieves the same status, I will be very encouraged as a web designer.
Now, if they would only get X3D in order...
I just want to point out that Flash is an open format - you can download the specs from Macromedia.
.swf files) and its scripting language is quite powerful.
/.-ers hate it so much. Just because it's not GNU/Flash?
I think SVG is very promising, but Flash already is available for 95% of the computers. It's reasonably fast, extremely compact (both the plugin and the
What I don't understand is why so many
So maybe I'm just a web Luddite who wants plain old text and images, but if the Mozilla developers manage to put default SVG support in Firebird while keeping it small and fast it'll be a good thing, even if it's still a while before we see widespread use of SVG. As long as there's a runtime option to turn it off. ;-)
People hate Flash for many reasons. The one that stands out for me is that it just doesn't work right. I'm used to tabbing through links on a page. I'm used to middle-clicking to open in a new window. I'm used to right-clicking and getting a useful set of options. I'm used to my browser remaining quiet, instead of blaring out music over the top of whatever I am already listening to.
There are a hundred different ways in which it doesn't work right. Flash just doesn't fit well with the web. It's a good format for presentation, or for HSR-style sites, but for everyday interaction with the web, it's terrible. However, many web developers haven't actually realised this, and litter the web with monstrosities that give Flash a bad name.
I think of Flash as being in the same boat as Java applets. In certain circumstances, they can be the best tool for the job. But using them as part of a website's infrastructure, as opposed to merely being something that is on a website, is virtually always a mistake.
There are numerous problems with Flash, and SVG has the potential to solve all of them. Many people hate Flash so much because of the countless sites that have been rendered unreadable and unusable by gratuitous use of Flash.
"The invisible and the non-existent look very much alike." -- Delos B. McKown
So blame the developer, don't blame the tool.
The world moves for love. It kneels before it in awe.
First, being able to download the specs does not make the format "open". An open format is defined in an open, relatively transparent process with input from multiple players including vendors and end-users. As long as Macromedia maintains sole control over the direction of the specification, it is not open. You can also download specs for the Word .DOC format.
Second, you cannot download the specs without agreeing to a license agreement. The license agreement is specifically designed to allow you to create SWF files but not to create a viewer. Macromedia has not sued anyone who created a viewer but that's because nobody has done a good enough job to compete with them seriously. Imagine if an open source product competed so well that more people wanted the open source version than the Macromedia version. First, they could sue. Then, they could change the format to make the open source version obsolete. That's why Flash is not an open format.
If Macromedia wants it to be open it should remove the licensing agreement and say that the specification is in the public domain for anybody to do anything with it.