Gecko:2DGraphicsSketch: Difference between revisions

 
Line 95: Line 95:


The bottom line is except for some small modifications (for example allowing the transform to be set on the pathbuilder to avoid a needless iteration when transforming a set of coordinates in user space, while at the same time avoiding the need for the API user to 'pre-transform'), I think the ID2D1Geometry model is much more solid than the one proposed here.
The bottom line is except for some small modifications (for example allowing the transform to be set on the pathbuilder to avoid a needless iteration when transforming a set of coordinates in user space, while at the same time avoiding the need for the API user to 'pre-transform'), I think the ID2D1Geometry model is much more solid than the one proposed here.
'''Matt''' I believe on Mac we wanted to look at using GL for content rendering in the future. Regardless of if this is using cairo-gl, or our own implementation, basing our API decisions on what Quartz does seems unnecessary.


== Clips ==
== Clips ==
Confirmed users
44

edits