Question 1

How do I use Oz in a ClojureScript web app?

Accepted Answer

Use the Reagent components `oz.core/vega` and `oz.core/vega-lite` in your ClojureScript code. Ensure data is not nil, and merge spec maps as described in the README for dynamic rendering.

Question 2

Oz vs Vega-Lite directly in JavaScript: which is better for Clojure projects?

Accepted Answer

Oz is ideal if you're already in Clojure, as it provides seamless integration with REPL and hiccup. For pure JavaScript projects, using Vega-Lite directly might be simpler without the Clojure overhead.

Question 3

Can I update Vega versions in Oz for new features?

Accepted Answer

Yes, but it requires cloning Oz, updating the `package.json`, and rebuilding with Shadow-CLJS. The README suggests this for debugging, but it adds maintenance burden.

Question 4

How to set up authentication for publishing gists with Oz?

Accepted Answer

Create a GitHub OAuth token with gist scope, save it as `{:oauth-token 'your-token'}` in `~/.oz/github-creds.edn`, and secure the file with `chmod 600`, as detailed in the sharing section.

Question 5

Is Oz good for building production static sites?

Accepted Answer

Yes, with features like `build!` and live reloading, it's capable for static sites. However, the alpha version status and dependency on Vega may require testing for stability.

Question 6

What are the limitations of Oz with real-time data?

Accepted Answer

Oz doesn't have built-in support for real-time streaming; visualizations update via REPL or file changes, so for live data, you'd need to manually refresh or use client-side JavaScript tricks.

Oz

What is Oz?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions