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:05, 30 October 2016
, 30 October 2016→Challenges
| Line 57: | Line 57: | ||
This is where it is going to be particularly important to come up with dedicated Canvas elements to abstract away and encapsulate these concepts, so that we can do away with huge custom Nasal blobs, and merely introduce dedicated elements for these purposes, which can be more easily mapped to a corresponding SVG element, e.g. by serializing to an <code><animate></code> tag and a corresponding piece of ECMA/JavaScript code. | This is where it is going to be particularly important to come up with dedicated Canvas elements to abstract away and encapsulate these concepts, so that we can do away with huge custom Nasal blobs, and merely introduce dedicated elements for these purposes, which can be more easily mapped to a corresponding SVG element, e.g. by serializing to an <code><animate></code> tag and a corresponding piece of ECMA/JavaScript code. | ||
Consequently, that also means that we need to move away from tons of custom Nasal blobs, and that even if new functionality may be implemented in Nasal space, it must be registered as conventional Canvas::Element child classes implementing the corresponding interface, for all the reasons discussed at [[Canvas_Development#The_Future_of_Canvas_in_FlightGear]] | |||
== Related == | == Related == | ||