mike chambers | about

Why Adobe chose FXG over SVG

I am currently on a speaking and press tour in Asia talking about some of the new stuff we are doing in Flex 4. One of the things that people seem to be really excited about is FXG and Thermo, and the improved designer / developer workflow that they promise. However, I have received a couple of questions about why we didnt just choose to use SVG instead of creating a new format.

This is actually addressed in the specification:

When initial work on an XML-based graphics interchange format began, the natural first thought was to use SVG. However, there are key differences between SVG and Flash Player’s graphics capabilities. These include core differences in SVG and Flash’s rendering model with regards to filters, transforms and text. Additionally, the interchange format needed to be able to support future Flash Player features, which would not necessarily map to SVG features. As such, the decision was made to go with a new interchange format, FXG, instead of having a non-standard implementation of SVG. FXG does borrow from SVG whenever possible.

Essentially, SVG didnt map well to the Flash world.

Our initial work around the format actually focused on SVG and Mark Anders has just posted a blog post describing in detail some of the issues that we ran into that led us to finally decide to pursue FXG over SVG.

You can read his post here.

twitter github flickr behance