20,741
edits
Howto:Serializing a Canvas to SVG: Difference between revisions
Jump to navigation
Jump to search
Howto:Serializing a Canvas to SVG (view source)
Revision as of 07:30, 30 October 2016
, 30 October 2016→Challenges
| Line 214: | Line 214: | ||
Once we do that, it would also be straightforward to even dispatch events between the browser sessions and FlightGear session. | Once we do that, it would also be straightforward to even dispatch events between the browser sessions and FlightGear session. | ||
In general it would be a very worthwhile goal to specifically target SVG because it's an existing standard, so that any Canvas/MFD related efforts could reuse tons of existing tools to help design, develop and maintain avionics or other SVG based functionality. This is also the only sane mechanism to render avionics remotely without replicating tons of code and without requiring a full OpenSceneGraph/osgviewer-based software stack (as per [[FGCanvas]]). | In general it would be a very worthwhile goal to specifically target SVG because it's an existing standard, so that any Canvas/MFD related efforts could reuse tons of existing tools to help design, develop and maintain avionics or other SVG based functionality. This is also the only sane mechanism to render avionics remotely without replicating tons of code and without requiring a full OpenSceneGraph/osgviewer-based software stack (as per fgpanel or [[FGCanvas]]). | ||
A working canvas->serialization scheme would also allow Phi to reuse Canvas-based MFDs without much effort. | |||
Ultimately, it would be up to the client-side to determine if and how to deal with such a streamed SVG, so that even a remote FlightGear instance could simply decide to render a corresponding SVG in a master/slave fashion. | Ultimately, it would be up to the client-side to determine if and how to deal with such a streamed SVG, so that even a remote FlightGear instance could simply decide to render a corresponding SVG in a master/slave fashion. | ||