20,741
edits
Canvas Nasal/JavaScript Subset: Difference between revisions
Jump to navigation
Jump to search
m
Canvas Nasal/JavaScript Subset (view source)
Revision as of 18:48, 21 February 2016
, 21 February 2016→Canvas: http://forum.flightgear.org/viewtopic.php?f=6&t=24490&p=226881&hilit=subset+javascript#p226881
m (→Canvas: http://forum.flightgear.org/viewtopic.php?f=36&t=24979&p=228397&hilit=subset+javascript#p228397) |
m (→Canvas: http://forum.flightgear.org/viewtopic.php?f=6&t=24490&p=226881&hilit=subset+javascript#p226881) |
||
| Line 13: | Line 13: | ||
== Canvas == | == Canvas == | ||
=== MFDs === | |||
Before any significant amount of time is spent on re-implementing functionality available available on Gijs' ND, I'd suggest to seriously consider collaborating whenever possible - all the artwork and animation logic can be easily made platform-agnostic, i.e. there's nothing Android/FlightGear or Canvas-specific about updating a SVG element and animating/transforming it. To make this work, you would merely need to use a tiny subset of JavaScript and Nasal and add a few of helper functions as wrappers for platform-specific functionality (think property tree access) - TorstenD has already written most of the code required for this as part of his mongoose work. | |||
That way, you could easily reuse the same SVG/artwork that's internally used by the Canvas ND. | |||
=== Remote GUI === | |||
The only way for the Canvas UI to provide a remote UI would be to serve SVG files via httpd/mongoose and hook them up to a subset of Nasal/JavaScript that both languages "understand", i.e. to set/get properties and invoke RPC functionality (e.g. fgcommands). | The only way for the Canvas UI to provide a remote UI would be to serve SVG files via httpd/mongoose and hook them up to a subset of Nasal/JavaScript that both languages "understand", i.e. to set/get properties and invoke RPC functionality (e.g. fgcommands). | ||