You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The reason will be displayed to describe this comment to others. Learn more.
I personally think it's great the API is unified, thanks.
However I have a small worry about the name CanvasBitmap for the interface. I fear this will be confusing with the output bitmap. It's currently ill-specified while referenced a lot, but in #9537@graveljp is rewriting it all with a canvas-bitmap, a context's top-level output bitmap, and layer's output-bitmap.
Unfortunately I don't really have a better proposition at the moment.
Thanks! I, too, don't like the name. The original explainer went with
CanvasSettings, then I switched to CanvasBitmap, and, given your feedback,
I've changed it back to CanvasSettings.
I also moved the initialization of the output bitmap into CanvasSettings,
as the "canvas settings output bitmap initialization algorithm",
which makes me feel better about something named CanvasSettings being the
interface that owns the bitmap.
8927cc6
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I personally think it's great the API is unified, thanks.
However I have a small worry about the name
CanvasBitmap
for the interface. I fear this will be confusing with the output bitmap. It's currently ill-specified while referenced a lot, but in #9537 @graveljp is rewriting it all with a canvas-bitmap, a context's top-level output bitmap, and layer's output-bitmap.Unfortunately I don't really have a better proposition at the moment.
8927cc6
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.