Call it what you want but the views trigger new Actions that manipulate the model. In the presentation they use the Chat example where marking a message read in a chat thread must update the unse...
There is no 2-way data binding in Flux. All data flows in a unidirectional fashion. This is one of the key strengths of the Flux architecture.
The action dispatcher calls are call collected in "TodoActions" which is then called from within the components to trigger the actions. e.g. Header -> TodoActions.create
> The central component, the model, consists of application data, > business rules, logic and functions. I think the flux dispatcher really just dispatches message to the subscribe...
After watching the presentation and taking a look at the TodoApp sample code I'm still a bit confused what the goal of flux is. It really does seem like MVC with an emphasize of the model as th...
The dispatcher has no app specific code in it
It seems like this is more related to the MVC (or MVP, MVVP, etc) that has come about as client-side javascript frameworks have become more popular. The attempt to make client-side javascript eas...
Instead of the view going back to the model, the view can go back to the controller as an action, and it now looks just like Flux.
> A controller can send commands to the model to update the model's > state (e.g., editing a document). It can also send commands to its > associated view to change t...
Yeah, that was a tricky slide, partly because there's not a lot of consensus for what MVC is exactly - lots of people have different ideas about what it is. What we're really arguing against is b...