I thought that a value notifier is just a change notifier for a single value. I'm not sure why it's more complicated. I'm interested in how you implement a controller 🤔 So what's your go to solution for event streams? - ThreadSky

About ThreadSky

gawi151.bsky.social • 161 days ago

I thought that a value notifier is just a change notifier for a single value. I'm not sure why it's more complicated.

I'm interested in how you implement a controller 🤔

So what's your go to solution for event streams?

Comments

jezell.bsky.social•161 days ago

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.

gawi151.bsky.social•161 days ago

Yeah so basically the controller will hold all the Value notifiers. Then the widget will read those value notifiers from the passed controller? Or it's not what you would do?

jezell.bsky.social•161 days ago

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).

jezell.bsky.social•161 days ago

I should have said Controller is a "Change Notifier" not "Value Notifier". Extra value prop is weird for the controller.

gawi151.bsky.social•161 days ago

Thx for all the answers I really appreciate it. It's good to see how others approach those things.

gawi151.bsky.social•161 days ago

I'm used to a controller/view model with stream of state where you simply subscribe to it from the widget.

Posting Rules

Be respectful to others
No spam or self-promotion
Stay on topic
Follow Bluesky's terms of service

Comments

Posting Rules

Reply