@charafau let us know if you ever publish that and I’ll add it to my spreadsheet :D
Rafal Wachol
@charafau
@eseidelGoogle i didn't think about publishing it. I I've done it just to compare the 'development feeling' of many frameworks (I've done the same app with kotlin, scala, react native and flutter) :)
Eric Seidel
@eseidel
@charafau if you ever have any thoughts to share, we’d love to hear them :)
email, issues, chat, however :)
Rafal Wachol
@charafau
Sure! The biggest problem I have so far was widget positioning
I had to use many nested layouts, but that might be due to my lack of knowledge
@eseidelGoogle I was actually thinking, how hard would that be to use the engine from C ?
it has 3 big pieces: the Dart Runtime, the Skia 2d graphics api, and a forked (and very stripped down) copy of Chrome’s text engine
Rafal Wachol
@charafau
I was thinking about writing small gui lib for C, rust for fun. From what I've seen all widgets are drawn in dart, but C engine is a renderer
Eric Seidel
@eseidel
The engine just knows the (C++ side of) the Dart runtime (GC, etc.), a copy of Skia (with only the hardware/opengl backend compiled in) and the stripped down text layout bits previously mentioned
if you’re writing a c/rust gui libary I doubt you’d start from Flutter’s engine :)
Rafal Wachol
@charafau
Ah, I thought I could reuse some part of it
_
Eric Seidel
@eseidel
we’re looking at replacing the text layout bit and that’s the only non-off-the-shelf component
well, we stripped down the dart and skia bits some, but nothing you couldn’t replicate by looking at our GN configs
I guess there is some android and iOS integration you could re-use
Writing these things is really hard, btw. :D
Mostly the pulling the whole product together is hard.
endless miles of details.
Rafal Wachol
@charafau
I know it's hard :)
I wasn't thinking about anything fancy, just for fun