The user may have information about the input path which can save significant preprocessing if known. E.g. it may be known that all curves are quadratic, or that the path follows certain convention for determining inside/outside. Add API to allow the user to specify this.
Currently we tear down everything (all nodes) whenever something changes (DirtyGeometry). Implement more finegrained flags (DirtyPath/DirtyOutline) to save unnecessary recalculation
Cleanup to facilitate the above: avoid the kludge of passing the entire pathData object to addPathNodes
Ideally do something about debugNodes - problematic for the above that it is common for fill & stroke
Technical task
P2: Important