Hi all,
Can anybody point the way to using mixins with reagent?
Discovering om-tools mixins don't work with om 0.8
(https://github.com/Prismatic/om-tools/issues/58) might just tip me over the
edge into reagent :). I realise I could go back to om 0.7.1 but then I would
have to give up the
Hi Jamie,
Yep, that is the conclusion I came to as well.
I know what you mean about the om simple/easy curve. In the past two weeks
since I started with om I have almost daily run into something that seems
harder than it needs to be, or at least more verbose, particularly around
channels
I have code which references the fully qualified goog.events.EventType/RESIZE.
I haven't required goog.events.EventType.
When it compiles, I get a WARNING: Use of undeclared Var
goog.events.EventType/RESIZE ... but the code works fine (e.g. reacts
correctly to the browser resizing).
If I
Quick update - om-tools and 0.8.0-alpha2 does appear to work with mixins, I
must have had a dodgy cache somewhere...
On Wednesday, 19 November 2014 17:22:08 UTC, Colin Yates wrote:
Hi all,
Can anybody point the way to using mixins with reagent?
Discovering om-tools mixins don't work with
Well yes, the compiler only needs to produce .js from .cljs.
The second phase is packaging everything together, this is where Closure
kicks in. That part needs externs, preamble and the like. I would agree that
does not need to be in ClojureScript itself, the whole Closure part ist not
I agree that these are not things I'd want to see incorporated into the
CLJS compiler, for sure. I think that it's the role of build tooling to do
this stuff. Boot does just fine driving the CLJS compiler, telling it where
externs are and so forth, and this is the way I'd most prefer, in a perfect