SVG:Data Storage: Difference between revisions

Jump to navigation Jump to search
m
SVGPathList -> SVGPathSegList
(add issue)
m (SVGPathList -> SVGPathSegList)
Line 3: Line 3:
== Introduction ==
== Introduction ==


This page contains thoughts regarding how we might redesign the way we store the typed values associated with the attributes of SVG elements. E.g., the SVG 'transform' attribute is mirrored by an SVGAnimatedTransformList object, which contains baseVal and animVal lists of SVGTransform objects, where each SVGTransform owns an SVGMatrix. (Many other attribute values are also represented by different types of object trees such as SVGLength[List], SVGPointList, SVGAngle, SVGColor, SVGPreserveAspectRatio, SVGPathList, etc.)  
This page contains thoughts regarding how we might redesign the way we store the typed values associated with the attributes of SVG elements. E.g., the SVG 'transform' attribute is mirrored by an SVGAnimatedTransformList object, which contains baseVal and animVal lists of SVGTransform objects, where each SVGTransform owns an SVGMatrix. (Many other attribute values are also represented by different types of object trees such as SVGLength[List], SVGPointList, SVGAngle, SVGColor, SVGPreserveAspectRatio, SVGPathSegList, etc.)  


We don't want to parse the values out of the attributes every time we (re)render the graphic so we store these typed value trees and keep them in sync with the attribute values.
We don't want to parse the values out of the attributes every time we (re)render the graphic so we store these typed value trees and keep them in sync with the attribute values.
Confirmed users, Bureaucrats and Sysops emeriti
969

edits

Navigation menu