Yo
Just doing my weekly bsky check 😂
hi
I could make some, but I thought everyone came here to get away from people like me. I don't want to crash the party 😂
Checking back to see if anyone started posting here yet. Seems a bit more dead every time I come back.
Flutter is trending today. All the AI startups need cross platform tooling.
shadcn-ui #99 update
Released the v0.17.3
- FIX: `ShadTable` protect `onExit` from setting value after dispose (thanks to @jezell.bsky.social)
Very cool. Tailscale really is awesome for distributed teams.
Still pretty quiet on the blue app.
shadcn-ui #96 update
Released the v0.16.3
- FEAT: Add `ShadInputOTP` and `ShadInputOTPFormField` components.
- BREAKING CHANGE: The `ShadBorder` no longer has default values, if you want to see the border rendered provide a color and a width greater than 0.
The #flutter tree is merged and open again. Thank you to all that helped out!
github.com/flutter/flut...
So awesome
Hmm... what's this:
github.com/loic-sharma/...
Maybe it's that thing everyone is talking about? 🤣
GG
A sign of the times
Love seeing a flurry of monorepo related commits coming through the flutter notifications.
Flutter AI SDK sucks. Do better. If anyone thinks this is gonna make people use Flutter for AI, they are smoking something. Next.JS vs Flutter samples:
Official Javascript Chatbot Sample (NextJS):
minimal-chatbot.vercel.app
Official Flutter Chatbot Sample:
flutter-ai-toolkit-examp-60bad.web.app
Yeah I love Flutter. It's my favorite framework. I just want it to be better!
Lies. Flutter crashes on Ultrawide high resolution displays. It also doesn't support VisionOS or AndroidXR. I wish this were true, but it's so far from the truth that it's embarrassing.
Engine is now part of the #Flutter monorepo
groups.google.com/g/flutter-an...
#FlutterDev
This is the best thing to happen to Flutter this year.
I should have said Controller is a "Change Notifier" not "Value Notifier". Extra value prop is weird for the controller.
Two options:
1) In simple cases the controller is just a value notifier because that's all you need
2) In more complex cases, the controller publishes events and allows the user to subscribe to them (either via a Stream or controller provided subscription mechanism).
Well it is, but if I see a widget with a bunch of value notifiers for every property I'm gonna think someone as putting way too much logic in their widget and they should have just built a controller class. It's hard to pass around groups of value notifiers, easy to pass around a controller.
They are decent for theming, media queries, and UI framework concerns. Still tend to fall apart with overlays but the less of them you have to manually copy into a new tree when you need screenshots or use overlays, the better. Also can be an escape hatch when you don't own all the code.
FFI isn't supported on web where these issues are really problematic. I actually had to contribute changes to the web engine to make it possible though.
Maybe if you want to handle those cases. In practice keys tend to be an easier solution to handle property changes in stateful widgets though. How much code do you want to type for something so basic?
The late final is also bound to the lifecycle. it won't get executed until it is accessed from build since late is lazy. Since a promise can't return in the current run of the event loop, the result will be returned after the first build either way. So in practice it's almost identical.
I don't mind streams for data from servers, but for event streams I don't like the complication compared to JS EventEmitter.
I avoid ValueNotifiers because they are overly complicated to use for what they do. Controllers can definitely use ChangeNotifier if you don't need granular notifications.
