(export! spec filepath & {:as opts :keys []})
In alpha; Export spec to an html file. May eventually have other options, including svg, jpg & pdf available
In alpha; Export spec to an html file. May eventually have other options, including svg, jpg & pdf available
(gist! spec & {:as opts :keys [name description public] :or {public false}})
Create a gist with the given spec.
Requires authentication, which must be provided by one of the following opts:
:auth
: a Github auth token the form "username:password":auth-token
: a GitHub OAuth1 / Personal access token as a string (recommended):client-id
: an oauth2 client id property:access-token
: oauth2 access tokenCAUTION: Note that running these options from the REPL may leave sensitive data in your ./.lein-repl-history
file.
Thus it's best that you avoid using these options, and instead create a single edn file at ~/.oz/github-creds.edn
with these opts.
You can run chmod 600
on it, so that only the owner is able to access it.
If you want to specify a different path use:
:auth-file
: defaults to ~/.oz/github-creds.edn
.Additional options:
:public
: default false:description
: auto generated based on specCreate a gist with the given spec. Requires authentication, which must be provided by one of the following opts: * `:auth`: a Github auth token the form "username:password" * `:auth-token`: a GitHub OAuth1 / Personal access token as a string (recommended) * for oauth2: * `:client-id`: an oauth2 client id property * `:access-token`: oauth2 access token CAUTION: Note that running these options from the REPL may leave sensitive data in your `./.lein-repl-history` file. Thus it's best that you avoid using these options, and instead create a single edn file at `~/.oz/github-creds.edn` with these opts. You can run `chmod 600` on it, so that only the owner is able to access it. If you want to specify a different path use: * `:auth-file`: defaults to `~/.oz/github-creds.edn`. Additional options: * `:public`: default false * `:description`: auto generated based on spec
(kill-watcher! filename)
Kill the corresponding watcher thread.
Kill the corresponding watcher thread.
(kill-watchers!)
(kill-watchers! filenames)
Kill all watcher threads if no args passed, or just watcher threads for specified filenames if specified.
Kill all watcher threads if no args passed, or just watcher threads for specified filenames if specified.
(live-reload! filename)
Watch a clj file for changes, and re-evaluate only those lines which have changed, together with all following lines. Is not sensitive to whitespace changes, and will also always rerun reference forms included in the ns declaration.
Watch a clj file for changes, and re-evaluate only those lines which have changed, together with all following lines. Is not sensitive to whitespace changes, and will also always rerun reference forms included in the ns declaration.
(live-view! filename & {:keys [host port format] :as opts})
Watch file for changes and apply load
& view!
to the contents
Watch file for changes and apply `load` & `view!` to the contents
(load filename & {:as opts :keys [format]})
Reads file and processes according to file type
Reads file and processes according to file type
(publish! spec & {:as opts :keys [mode return-full-gist] :or {mode :vega-lite}})
Publish spec via gist! and print out the corresponding vega-editor or ozviz.io url.
Requires authentication, which must be provided by one of the following opts:
:auth
: a Github auth token the form "username:password":oauth-token
: a GitHub OAuth1 / Personal access token as a string (recommended):client-id
: an oauth2 client id property:access-token
: oauth2 access tokenCAUTION: Note that running these options from the REPL may leave sensitive data in your ./.lein-repl-history
file.
Thus it's best that you avoid using these options, and instead create a single edn file at ~/.oz/github-creds.edn
with these opts.
You can run chmod 600
on it, so that only the owner is able to access it.
If you want to specify a different path use:
:auth-file
: defaults to ~/.oz/github-creds.edn
.Additional options:
:public
: default false:description
: auto generated based on spec:return-full-gist
: return the full tentacles gist api response dataPublish spec via gist! and print out the corresponding vega-editor or ozviz.io url. Requires authentication, which must be provided by one of the following opts: * `:auth`: a Github auth token the form "username:password" * `:oauth-token`: a GitHub OAuth1 / Personal access token as a string (recommended) * for oauth2: * `:client-id`: an oauth2 client id property * `:access-token`: oauth2 access token CAUTION: Note that running these options from the REPL may leave sensitive data in your `./.lein-repl-history` file. Thus it's best that you avoid using these options, and instead create a single edn file at `~/.oz/github-creds.edn` with these opts. You can run `chmod 600` on it, so that only the owner is able to access it. If you want to specify a different path use: * `:auth-file`: defaults to `~/.oz/github-creds.edn`. Additional options: * `:public`: default false * `:description`: auto generated based on spec * `:return-full-gist`: return the full tentacles gist api response data
(start-plot-server!)
(start-plot-server! & [port])
Start the oz plot server (on localhost:10666 by default).
Start the oz plot server (on localhost:10666 by default).
(vega spec)
Reagent component that renders vega
Reagent component that renders vega
(vega-lite spec)
Reagent component that renders vega-lite.
Reagent component that renders vega-lite.
(view! spec & {:keys [host port mode]})
View the given spec in a web browser. Specs for which map? is true are treated as single Vega-Lite/Vega specifications.
All other values are treated as hiccup, and are therefore expected to be a vector or other iterable.
This hiccup may contain Vega-Lite/Vega visualizations embedded like [:vega-lite spec]
or [:vega spec]
.
You may also specify :host
and :port
, for server settings, and a :mode
option, defaulting to :vega-lite
, with :vega
the alternate option.
(Though I will note that Vega-Embed often catches when you pass a vega spec to a vega-lite component, and does the right thing with it.
However, this is not guaranteed behavior, so best not to depend on it (wink, nod))
View the given spec in a web browser. Specs for which map? is true are treated as single Vega-Lite/Vega specifications. All other values are treated as hiccup, and are therefore expected to be a vector or other iterable. This hiccup may contain Vega-Lite/Vega visualizations embedded like `[:vega-lite spec]` or `[:vega spec]`. You may also specify `:host` and `:port`, for server settings, and a `:mode` option, defaulting to `:vega-lite`, with `:vega` the alternate option. (Though I will note that Vega-Embed often catches when you pass a vega spec to a vega-lite component, and does the right thing with it. However, this is not guaranteed behavior, so best not to depend on it (wink, nod))
cljdoc is a website building & hosting documentation for Clojure/Script libraries
× close