Replies: 3 comments 1 reply
-
This sounds good. I am sure we can all enjoy this. Whether or not to use separate views, it all depends. If it is just something that a property can do, then no need to add views. But, if for some reason things require many different thibgs we could see what is better. |
Beta Was this translation helpful? Give feedback.
-
I see in main repo that skiasharp uses GL renderer for iOS and Metal only on Catalyst, does it? |
Beta Was this translation helpful? Give feedback.
-
Implemented iOS Metal retained-mode renderer as proof of concept so far, works fine. |
Beta Was this translation helpful? Give feedback.
-
Hello,
Actually using SkiaSharp for UI construction. Working on optimizing the speed. Noticed that the current SkiaSharp handlers/renderers are recreating/clearing surfaces on every frame. This is neat overall but is a stopper for implementing retained mode rendering, where we could fast-draw only dirty/changed regions over an existing rendering result.
The current implementation of SKGLTextureRenderer, SKSwapChainPanel, SKMetalView, and Blazor SKGLView are all similar in acting in immediate mode:
Would like to attack the creation of retained mode renderers to change this to:
Profit:
Faster rendering, especially for UI
Less GPU consumption
Less battery consumption on mobile
Reduce memory bandwidth usage
Closer to classic UI rendering techs, especially Flutter
Would propose to share thoughts and opinions about this.
Is it acceptable to be incorporated inside SkiaSharp?
If yes, should we have separate views for that or add options/props to existing ones?
Unleash hell.
Beta Was this translation helpful? Give feedback.
All reactions