status-im/re-frame-10x
2
0
Fork 0
mirror of https://github.com/status-im/re-frame-10x.git synced 2025-02-10 05:03:49 +00:00
Code Issues Projects Releases Wiki Activity

Update ReplayButton.md

Browse Source
This commit is contained in:
Mike Thompson 2018-02-18 08:58:43 +11:00 committed by GitHub
parent 6effae5c70
commit a8aa92be68
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 8 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
docs/HyperlinkedInformation/ReplayButton.md
View File

@ -14,7 +14,7 @@ an "Action Replay" of "The Observed Epoch", and this happens in two Steps:
So, Step 1 is "reestablish initial conditions" and Step 2 is "do it all again". So, Step 1 is "reestablish initial conditions" and Step 2 is "do it all again".
### Further Notes: #### Further Notes:
- In Step 1, the reset of `app-db` will trigger computation and trace. - In Step 1, the reset of `app-db` will trigger computation and trace.
Subscriptions and views are run as the application returns to the "prior state", Subscriptions and views are run as the application returns to the "prior state",
but none of the associated trace is captured. It is all ignored. but none of the associated trace is captured. It is all ignored.
@ -33,17 +33,17 @@ It facilitates "The HotPlay Workflow":
- D: You click the `Replay` button - D: You click the `Replay` button
- E: Back to A - E: Back to A
Because of `Replay's` "Step 1", you effortlessly get identical "initial conditions" for Because of `Replay's` "Step 1", you get identical "initial conditions" for
each iteration of the workflow, and this is true blessing. It removes the nagging each iteration of the workflow, and this is true blessing. It removes the nagging
cognative load of "allowing for" slightly shifting state. Or the effort of manually cognative load of "allowing for" slightly shifting state and its consequences, or
reestablishing identical application state before each iteration. the effort of manually reestablishing identical application state before each iteration.
WARNING: obviously this only works when the state is contained in your SPA. When WARNING: obviously this only works when the state is contained within your SPA. When
there's remote state (a remote database?) it is more effort to return to initial conditions there's authorative remote state (a remote database?) there'll be more involved in
each iteration. returning to initial conditions each iteration.
### The Workflow Name ### The Workflow Name
The initials of this Observe/Edit/Hotload/Replay process are OEHR, which, will, it doesn't exactly roll off the tounge like REPL. The initials of this Observe/Edit/Hotload/Replay process are OEHR, which, well, doesn't exactly roll off the tounge like REPL.
So we call it "HotPlay" because "Hotload" and "Replay" are the two central pieces of tech. We love you Figwheel. So we call it "HotPlay" because "Hotload" and "Replay" are the two central pieces of tech. We love you Figwheel.