It almost sounds too good to be true.
It almost sounds too good to be true.
It's a canvas-like implementation for terminal apps written in Dart 🤷
Lovely. S-tier any day!
OSS! Give us something!
I think it depends, for my use case, an inherited widget would also work but it depends on if you are already dealing with mostly render object widgets, making a custom element or even just a subclass of the existing implementations just feels more in the same domain.
You caught me 😅
Special case when working with RenderObjects and in need of a custom behavior during the lifetime of the widget without needing to rely on the widget layer (StatefulWidget). In order words, holding state in the render object layer without relying on the widget layer
I have but only in very specific situations
Thank you!
I’m not going to lie, I’m starting to feel like i could stay here. I just need bookmarks and it would be golden.
Hey #Flutter sky,
I know, this is not the airport so no need to announce an arrival but this seems like a good first #FlutterDev post #SaturdaysAreForFlutter
saturdays-are-for-flutter.vercel.app