RESOLVED FIXED Bug 207048
Allow different back-ends for ImageBuffer
https://bugs.webkit.org/show_bug.cgi?id=207048
Summary Allow different back-ends for ImageBuffer
Said Abou-Hallawa
Reported 2020-01-31 08:59:48 PST
This will decouple the platform specifics and the back-end details from the interface "ImageBuffer". In following patches new types of ImageBuffers backed by new ImageBufferBackends will be added. These new ImageBufferBackends will implement DisplayList drawing and synchronize remote rendering.
Attachments
Patch (345.99 KB, patch)
2020-01-31 09:10 PST, Said Abou-Hallawa
no flags
Patch (347.00 KB, patch)
2020-01-31 09:17 PST, Said Abou-Hallawa
no flags
Patch (351.11 KB, patch)
2020-01-31 09:46 PST, Said Abou-Hallawa
no flags
Patch (352.85 KB, patch)
2020-01-31 14:22 PST, Said Abou-Hallawa
no flags
Patch for review (293.21 KB, patch)
2020-01-31 19:00 PST, Said Abou-Hallawa
no flags
Patch (298.48 KB, patch)
2020-02-18 09:58 PST, Said Abou-Hallawa
no flags
Patch (298.49 KB, patch)
2020-02-18 10:17 PST, Said Abou-Hallawa
no flags
Patch (302.65 KB, patch)
2020-02-18 15:34 PST, Said Abou-Hallawa
no flags
Patch (299.30 KB, patch)
2020-02-18 16:08 PST, Said Abou-Hallawa
no flags
Said Abou-Hallawa
Comment 1 2020-01-31 09:10:49 PST
Said Abou-Hallawa
Comment 2 2020-01-31 09:17:26 PST
Said Abou-Hallawa
Comment 3 2020-01-31 09:46:18 PST
Said Abou-Hallawa
Comment 4 2020-01-31 14:22:08 PST
Said Abou-Hallawa
Comment 5 2020-01-31 19:00:23 PST
Created attachment 389449 [details] Patch for review
Tim Horton
Comment 6 2020-02-18 00:45:13 PST
Comment on attachment 389449 [details] Patch for review View in context: https://bugs.webkit.org/attachment.cgi?id=389449&action=review I think this is fine, except the name. > Source/WebCore/WebCore.xcodeproj/project.pbxproj:834 > - 2DDE1D081F574D0E00D1A365 /* JSVRStageParameters.h in Headers */ = {isa = PBXBuildFile; fileRef = 2DDE1CF61F574BFF00D1A365 /* JSVRStageParameters.h */; }; > + 2DDE1CE31F574AE500D1A365 /* (null) in Headers */ = {isa = PBXBuildFile; }; This all doesn't look good > Source/WebCore/platform/graphics/ContextualImageBuffer.h:33 > +class ContextualImageBuffer : public ImageBuffer { I'm not sure I follow the "Contextual" name (but maybe you can explain) (also, I'm not sure why it exists? Why isn't this just all IN ImageBuffer?) (reading more... is it so you can hide BackendType from ImageBuffer clients? why not just `using` it away?) > Source/WebCore/platform/graphics/ContextualImageBuffer.h:145 > + const_cast<ContextualImageBuffer&>(*this).flushContext(); Maybe we should just bite the bullet and de-const getImageData if it's a lie?
Said Abou-Hallawa
Comment 7 2020-02-18 09:58:06 PST
Said Abou-Hallawa
Comment 8 2020-02-18 10:17:14 PST
Said Abou-Hallawa
Comment 9 2020-02-18 13:34:23 PST
Comment on attachment 389449 [details] Patch for review View in context: https://bugs.webkit.org/attachment.cgi?id=389449&action=review >> Source/WebCore/WebCore.xcodeproj/project.pbxproj:834 >> + 2DDE1CE31F574AE500D1A365 /* (null) in Headers */ = {isa = PBXBuildFile; }; > > This all doesn't look good This was fixed in the latest patch. >> Source/WebCore/platform/graphics/ContextualImageBuffer.h:33 >> +class ContextualImageBuffer : public ImageBuffer { > > I'm not sure I follow the "Contextual" name (but maybe you can explain) > > (also, I'm not sure why it exists? Why isn't this just all IN ImageBuffer?) > > (reading more... is it so you can hide BackendType from ImageBuffer clients? why not just `using` it away?) Contextual here means an ImageBuffer which can provide a GraphicsContext. ContextualImageBuffer is a template class which is derived from ImageBuffer. All the callers can still keep a. pointer to an ImageBuffer which represents the interface of all the ContextualImageBuffers. It is also a bridge design pattern. As you said it hides the backend type from the callers. The creator can choose the backend type but caller which receives an std::unique_ptr<ImageBuffer> does not have to know any details about this backend. Other names: BackendedImageBuffer, ImageBufferWithBackend, PhysicalImageBuffer, ConcreteImageBuffer, ImageBufferImpl, ImageBufferBridge.. >> Source/WebCore/platform/graphics/ContextualImageBuffer.h:145 >> + const_cast<ContextualImageBuffer&>(*this).flushContext(); > > Maybe we should just bite the bullet and de-const getImageData if it's a lie? I think it is okay to keep the function const. flushContext() is an internal function which does nothing expect in the case of IOSurface backed ended ImageBuffer and the remote ImageBuffer.
Said Abou-Hallawa
Comment 10 2020-02-18 15:34:51 PST
Said Abou-Hallawa
Comment 11 2020-02-18 16:08:36 PST
WebKit Commit Bot
Comment 12 2020-02-18 17:12:54 PST
Comment on attachment 391114 [details] Patch Clearing flags on attachment: 391114 Committed r256892: <https://trac.webkit.org/changeset/256892>
WebKit Commit Bot
Comment 13 2020-02-18 17:12:56 PST
All reviewed patches have been landed. Closing bug.
Radar WebKit Bug Importer
Comment 14 2020-02-18 17:13:29 PST
Note You need to log in before you can comment on or make changes to this bug.