[DO NOT MERGE]: Introduce Graphite Native Metal#1184
[DO NOT MERGE]: Introduce Graphite Native Metal#1184hub-bla wants to merge 12 commits intoJetBrains:masterfrom
Conversation
| } | ||
|
|
||
| @ExperimentalSkikoApi | ||
| fun makeFromBackendTexture( |
There was a problem hiding this comment.
An option to avoid using graphite package here - make it an extension function inside graphite package
fun Surface.Companion.makeFromBackendTexture(...)| } | ||
| } | ||
|
|
||
| internal abstract class GraphiteContextHandler( |
There was a problem hiding this comment.
Should we move it into graphite package?
There was a problem hiding this comment.
We can but ContextHandler can't be sealed then. If thats fine then sure
|
|
||
| import org.jetbrains.skia.gpu.SkiaGpuBackend | ||
|
|
||
| object SkikoFlags { |
There was a problem hiding this comment.
Currently flags are platform-dependent (built-in properties on Desktop).
I see it's used only in MacOsMetalRedrawer, so maybe it might be regular argument there
There was a problem hiding this comment.
It's currently used only in MacOsMetalRedrawer because I only made the Graphite-based context handler for native macOS for now. In general I think that flag (or flags) related to GPU backend should be available to all platforms so we know at runtime which backend is available
[SKIKO-1095](https://youtrack.jetbrains.com/issue/SKIKO-1095) Move build scripts from `skia-pack` to `skia` fork JetBrains/skia#15
2 participants
SKIKO-1128
This PR introduces the initial version of the Graphite API in Skiko using native Metal.
Please note that a separate PR for Graphite packaging must be merged before this one can be finalized