|
One major difference between SVG and Avalon/XAML is, SVG is interpreted while executables for the Avalon/XAML is compiled binary. SVG viewer interprets SVG documents; while, Avalon/XAML document must be compiled in advance to create an exe file to run.
Avalon/XAML is next generation vector-graphics technology announced by Microsoft and Adobe committed to support this technology in their products. This is a setback for Elansoft’s Agileblox to leverage future Avalon infrastructure and boon for FusionCharts.
Java-classes in Agileblox need run-time data in advance before generating SVG-chart or file. To create SVG-file for each chart, the Java classes use the run-time data at server to calculate various display-elements, such as size of bars in a bar-chart, or size of each slice of a pie-chart etc.
On the other hand, FusionCharts use external XML-data at client to create the Flash-chart. The FusionCharts are akin to binary-exe files, and they won’t change for each different chart. Only file that changes between two different charts is the external XML-data file.
The server sends client, both static binary-swf file and dynamic XML-data created at run time. At the client, the binary-swf file reads the data and creates Flash-chart. This fits perfectly with Microsoft’s Avalon framework. Avalon platform needs compiled Avalon-EXE; which could be programmed to read external XML-data.
You could easily replace the binary-swf file with a compiled Avalon-EXE file. Since, XAML is super set of SWF and far more powerful, the FusionCharts could easily be translated from SWF files to XAML files and compile the XAML-files to create binary-EXE files. Also XAML won’t support some SVG-features, such as CSS and JavaScript etc.
|
Previous Message
Up
