20,741
edits
Canvas SVG parser: Difference between revisions
no edit summary
(Switched to {{gitorious source}} and {{fgdata source}} to fix the broken Gitorious links.) |
No edit summary |
||
| Line 18: | Line 18: | ||
The '''scripted SVG parser''' basically just maps the SVG xml structure to the property tree by adding corresponding Canvas elements as child nodes. It is implemented in [[Nasal]] on top of the XML parsing facilities already provided by FlightGear/Nasal (see $FG_ROOT/Nasal/io.nas). | The '''scripted SVG parser''' basically just maps the SVG xml structure to the property tree by adding corresponding Canvas elements as child nodes. It is implemented in [[Nasal]] on top of the XML parsing facilities already provided by FlightGear/Nasal (see $FG_ROOT/Nasal/io.nas). | ||
There's a tiny Nasal module named svg.nas (see $FG_ROOT/Nasal/Canvas) that will read those SVG/XML files and convert them into Canvas nodes (OpenVG/ShivaVG paths) - in other words, depending on the nature of the differences in the output, it should be possible to patch up the svg parser to also support the new format. | |||
To make changes to that module, you need to understand how parsing works and how a stack works (the data structure). | |||
<ref> {{cite web | |||
| url = http://forum.flightgear.org/viewtopic.php?p=280763#p280763 | |||
| title = <nowiki>Re: Strange thing with font mapper</nowiki> | |||
| author = <nowiki>Hooray</nowiki> | |||
| date = Mar 28th, 2016 | |||
| added = Mar 28th, 2016 | |||
| script_version = 0.25 | |||
}} | |||
</ref> | |||
== Vector Image Support == | == Vector Image Support == | ||