This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-02-16
Channels
- # aws (6)
- # beginners (129)
- # calva (9)
- # cider (4)
- # cljs-dev (2)
- # clojure (41)
- # clojure-beijing (2)
- # clojure-dev (3)
- # clojure-spec (23)
- # clojure-uk (46)
- # clojurescript (38)
- # community-development (20)
- # core-async (4)
- # cursive (12)
- # data-science (7)
- # datascript (13)
- # datomic (15)
- # duct (11)
- # emacs (18)
- # figwheel-main (5)
- # fulcro (26)
- # off-topic (4)
- # pathom (28)
- # pedestal (3)
- # reagent (8)
- # reitit (6)
- # shadow-cljs (32)
- # specter (3)
@metasoarous with respect to chart editing, they use this web app for editing your json/chart https://github.com/plotly/react-chart-editor they have an option where you can retrieve the json file doing the visualization.
@jsa-aerial I totally agree with composition and dashboard and interactivity. (Although plotly does have some functionality as well). The point where I come from is I have been asked to produce numerous dashboards with user interactivity already at the level where I need to use reagent+reframe to handle these.
So I guess Hanami and Oz are mainly aimed to have a lightweight libraries to handle most visualization without needing reagent/reframe.
@neo2551 Hanami uses a reagent component as part of its canonical way of rendering Vega(Lite). And it pretty much 'buys into' the whole reactive flow thing. And it uses re-com components to structure things like picture frames, automatic tab layout, and for 'external' plot/chart instrumentation (https://github.com/jsa-aerial/hanami#instrumented-barchart). The idea of external instrumentation would fit pretty much with 'user interactivity outside of the actual visualization'. Of course, there is no reason that this could not be combined with the great internal Vega(Lite) interactivity. I've done that in several cases.
Vega-Lite/Vega's interactive features are still super useful even if you are using Reagent/Re-frame. In particular, you can plug into the stream of interaction data, and have it influence things at the React/Reagent level. You can see an example of this in a JS app I'm working on: http://olmstedviz.org. As you select a range of points in the scatterplot, it acts as a filter on the React table (grid actually) right below it. It's true though that if you have Reagent/Reframe, you can push some of the interactivity into that layer, especially useful when you want to control some aspect of the viz spec itself programatically. But there are parts of the interactive space that either aren't covered by those patterns, and when that's the case, you'll find Vega-Lite/Vega's interactivity a nice complement.
@neo2551 Hanami uses a reagent component as part of its canonical way of rendering Vega(Lite). And it pretty much 'buys into' the whole reactive flow thing. And it uses re-com components to structure things like picture frames, automatic tab layout, and for 'external' plot/chart instrumentation (https://github.com/jsa-aerial/hanami#instrumented-barchart). The idea of external instrumentation would fit pretty much with 'user interactivity outside of the actual visualization'. Of course, there is no reason that this could not be combined with the great internal Vega(Lite) interactivity. I've done that in several cases.
@metasoarous I think you are thinking of crossfiltering when you say interactivity?
@neo2551 Not just crossfiltering. You could use it for selecting individual data points, for example. Take a peak at the examples to see what's possible on the interactive front.