status-im
/
re-frame
mirror of https://github.com/status-im/re-frame.git
2
0
Fork 0
Code Issues Projects Releases Wiki Activity

Pass 4.1 review

This commit is contained in:
Gregg8 2014-12-18 01:53:11 +11:00
parent cf1cb64422
commit 3b1f0d481e
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
README.md
View File

@ -471,7 +471,7 @@ app-db --> components --> Hiccup --> Reagent --> VDOM --> React -->
``` ```
Generally, when the user manipulates the GUI, the state of the application changes. In our case, Generally, when the user manipulates the GUI, the state of the application changes. In our case,
that means the `app-db` will change. After all, it **is** the state. And the DOM presented to the user is a function of that state. So that tends to be the cycle: DOM events dispatch, handlers mange them, which cause `app-db` changes, which then cause a re-render, and the users sees something different. That's our water cycle. that means the `app-db` will change. After all, it **is** the state. And the DOM presented to the user is a function of that state. So that tends to be the cycle: DOM events dispatch, handlers manage them, which cause `app-db` changes, which then cause a re-render, and the users sees something different. That's our water cycle.
So handlers, which look after events, are the part of the system which do `app-db` mutation. You So handlers, which look after events, are the part of the system which do `app-db` mutation. You
could almost imagine them as a "stored procedure" in a could almost imagine them as a "stored procedure" in a