On Saturday, March 14, 2015 at 2:52:45 PM UTC+11, AndyR wrote:
On Friday, March 6, 2015 at 11:28:59 PM UTC-5, Mike Thompson wrote:
re-frame is a pattern for writing SPAs, using Reagent.
https://github.com/Day8/re-frame
[...]
- pushes Reagent's FRP capabilities (via use of reaction)
On Friday, March 6, 2015 at 11:28:59 PM UTC-5, Mike Thompson wrote:
re-frame is a pattern for writing SPAs, using Reagent.
https://github.com/Day8/re-frame
[...]
- pushes Reagent's FRP capabilities (via use of reaction)
The magic thing about a reaction is that the computation it wraps
On Tuesday, March 10, 2015 at 2:03:00 PM UTC+11, Mike Thompson wrote:
On Tuesday, March 10, 2015 at 2:14:42 AM UTC+11, Mike Haney wrote:
I'm really enjoying re-frame. I've tried several different architectures
over the last 6 months and ended up with something about 80% similar to the
I'm really enjoying re-frame. I've tried several different architectures over
the last 6 months and ended up with something about 80% similar to the re-frame
approach. The key piece missing for me was reactions - there is absolutely no
documentation on them in Reagent, but knowing about them
Hi Mike/Mike,
What are reactions? and where in re-frame are they used or documented (at
least in code)?
I'm very curious as to why Dan hasn't documented them. re they
experimental or supposed to be for Reagent's own internal use?
Marc
On Mon, Mar 9, 2015 at 8:14 AM, Mike Haney
On Sunday, March 8, 2015 at 10:11:43 PM UTC+11, Mike Thompson wrote:
How would you allow an event handler to register for all events? Right now
each one is required to explicitly register for each event via keyword. I
have modified re-frame to allow handlers to also register a function
How would you allow an event handler to register for all events? Right now
each one is required to explicitly register for each event via keyword. I
have modified re-frame to allow handlers to also register a function that
does the test.
re-frame is quite a flexible base. You should be
