status-im/re-frame
2
0
Fork 0
mirror of https://github.com/status-im/re-frame.git synced 2025-02-21 14:28:07 +00:00
Code Issues Projects Releases Wiki Activity

Update Changes doc

Browse Source
This commit is contained in:
Mike Thompson 2017-07-14 17:53:34 +10:00
parent a0ca8cf2c4
commit 131e0ba30c
2 changed files with 14 additions and 11 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
CHANGES.md
View File

@ -1,9 +1,14 @@
## Unreleased
#### New
- improved [testing docs](https://github.com/Day8/re-frame/blob/master/docs/Testing.md)
- added [a new mental model](https://github.com/Day8/re-frame/blob/master/docs/MentalModelOmnibus.md#dsls-and-vms)
#### Fixes
- #357
- #340
- [#357](https://github.com/Day8/re-frame/pull/357)
- [#340](https://github.com/Day8/re-frame/pull/340)
## 0.9.4 (2017.06.01)

16
docs/MentalModelOmnibus.md
View File

@ -104,7 +104,7 @@ Sincerely, The Self-appointed President of the Cursor Skeptic's Society.
`Events` are central to re-frame's architecture. Nothing happens without a dispatched event.
Every app will have a different `events`, indeed, part of your job will be to
Every app will have a different `events`. Indeed, part of your job will be to
design exactly the right set of them. For your app,`events` will be the "language of the system".
They capture intent (generally the user's intent). They provide the eloquence.
@ -132,15 +132,13 @@ mov BYTE PTR [ebx], 2
Assembler instructions are data, right? They have to be "executed" by a machine. I'd
like you to look back at the collection of events above the same way.
> Events are the assembly language of your app. They are instructions. These instructions
are data. One after another gets executed by your functioning app.
> Collectively, the events you design form a Domain Specific Language (DSL). The language of your system.
Mental Model:
- Events are the assembly language of your app. They are instructions.
- These instructions are data. One after another gets executed by your functioning app.
- Collectively, the events you design form a Domain Specific Language (DSL). The language of your system.
- And, collectively, the Event Handlers you register create the Virtual Machine (VM) on which this DSL executes.
> And, collectively, the Event
Handlers you register create the Virtual Machine on which this DSL executes.
> Data is executed by the VM you create. All very Clojure.
> So, data is executed by the re-frame VM you create. Which is all data oriented and Clojurian.
I find James Reeves' talks to be excellent (video): [Transparency through data](https://www.youtube.com/watch?v=zznwKCifC1A)