There are certainly redundant pieces when using Om & d3 together, like
data-binding and DOM management. I experimented (briefly) with the idea of
using Om/React as much as possible and only using d3 basically to create
functions for generating paths. This avoids having to sync the redundant part
You may also find this helpful:
https://github.com/seancorfield/om-sente/blob/master/src/cljs/om_sente/core.cljs
It builds graphs three ways:
* using Om to do animation
* using D3 "raw"
* using NVD3 "raw"
Sean
On May 29, 2014, at 3:41 AM, Juan Manuel Gimeno Illa wrote:
> Thanks for the detail
Sorry, did I say Vars? I meant syms.
On Thu, May 29, 2014 at 11:41 AM, Gary Trakhman wrote:
> #1, CLJS macros must use fully-qualified vars. It is possible to resolve
> using analyzer state, but that requires internal knowledge of the CLJS
> compiler.
> #2, it would be going to whatever the bin
#1, CLJS macros must use fully-qualified vars. It is possible to resolve
using analyzer state, but that requires internal knowledge of the CLJS
compiler.
#2, it would be going to whatever the binding of *out* is in the current
thread, likely it's ending up in the compiled CLJS source code because
I know ClojureScript doesn't support run-time Vars, but reading the CLJS
code I thought it supported Vars at compile-time, when all is executed
inside the CLJ/JVM runtime. The following code compiles without
assertexceptions for CLJ/JVM but when compiling CLJS the
assert in the macro fails:
;;; sr
Thanks for the detailed answer !!!
Juan Manuel
--
Note that posts from new members are moderated - please be patient with your
first post.
---
You received this message because you are subscribed to the Google Groups
"ClojureScript" group.
To unsubscribe from this group and stop receiving ema
