Skia evolved a lot these last years (mainly because Google (and others like Mozilla or Microsoft) decided to use it as the common rendering engine for all its top products, and specifically Chrome and Flutter that are cross-platforms) So yes Skia is now capable to run on top of GPU hardware rendering libs like OpenGL or Vulkan (or others) and to make call to these when relevant Concerning the support of Metal by Skia, this is WIP and is expected to be achieved for summer 2019 (https://bugs.chromium.org/p/skia/issues/detail?id=8050) I don't think replacing only the currend AndroidImplementation rendering by Skia would be worth it though. It would be a lot of work for only a few degrees of control gained (the Android API already expose most of the Skia capabilities. Actually, when you make a graphic Android API call, that is Skia that is called under the hood and that then call OpenGL when relevant) Furthermore, as Android do not directly expose the Skia API (saddly), you have to embed Skia in your app apk, which increase your minimal apk size by 1 or 2 Mb. On the other hand, using Skia (or any other cross-platform 2D graphic lib, but I don't know if there are some that compete with Skia in terms of efficiency and range of supported platforms) for many targets is a whole different story as, doing so, only one renderer needs to be written and debugged for all these targets at once (and can then be run on any platform, where Skia works) and you are delegating the hard work of keeping your rendering engine up to date with these platforms to the Skia developpers. This is a significant advantage as it allows you to move faster to new targets (when Skia support a new target, your Skia renderer would immediately work to it. Else you still have the solution to writte a specific renderer for this target as this is actually the case) Furthermore, you partially free yourself from the rule of the "least capable" that usually prevails when writting cross-platforms API. For example, if the Android java API do not allows you to access some specific graphic capabilities, like shape shadowing that could exist on the API of another platform like iOS (I don't know if it is the case, it is just an example), as long as Skia others you this possibility and run on both platforms, you can expose this capacity in your API This is probably one of the reasons why Flutter was able to be develloped so quickly and why other Frameworks, like Xamarin, are moving in the same direction and now offer the possibility to use Skia (via SkiaSharp) as a rendering engine on most of its targeted platforms.
On Thursday, September 27, 2018 at 6:47:30 AM UTC+2, Shai Almog wrote: > > Skia on iOS would be a lateral move as they don't work on top of metal. It > won't be an improvement. When we initially evaluated SKIA a few years ago > it was only a software renderer on Android and so it wasn't practical in > terms of performance. Adding the complexity of native component integration > would have made it even less desirable. > > FYI Apple deprecated OpenGL on iOS & Mac OS so the migration path is Metal. > -- You received this message because you are subscribed to the Google Groups "CodenameOne Discussions" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. Visit this group at https://groups.google.com/group/codenameone-discussions. To view this discussion on the web visit https://groups.google.com/d/msgid/codenameone-discussions/5a56b902-ed48-481f-b962-fb27d6414fa3%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
