Data exploration, dashboards and interactive documents; with editor support (emacs, vim, sublime, and paredit), graphics and visualization; markdown; and LaTex. 咲さいて (in bloom). Built on top of Hanami Vega/Vega-Lite library, CodeMiror, MathJax, amd Specter.

Saite is a Clojure(Script) client/server application for the dynamic exploration of data and the creation and sharing of interactive documents and dashboards. Documents fully support creation of interactive visualizations, coupled with editors, markdown and LaTex. Dashboards can use any Re-com component for interactive widgets mixed with Vega/Vega-Lite visualizations. These documents and dashboards are saved as simple text and thus may be shared via any number of ways. End user creation of documents is highly declarative in form and nature. Dashboards may use of mixture of client side widgets and visualization and server side dataset processing for the final data to use.

• Introduction
• Installation
  • Uberjar
  • Library
  • Running
• Outline
• Overview
  • Videos
  • Tutorials

toc

Saite is a Clojure(Script) client/server application for dynamic interactive data exploration, mixed server/client dashboard creation, and the creation of live shareable documents. Documents and dashboards fully support creation of interactive visualizations, coupled with editors, Re-com components, markdown and LaTex. These documents and dashboards are saved as simple text and thus may be shared via any number of ways. End user creation of documents is highly declarative in form and nature, while dashboards are a mix of declarative forms and reactive functions.

Vega-Lite (VGL) and/or Vega (VG) specifications. These specifications are declarative and completely specified by data (JSON maps). VGL compiles into the lower level grammar of VG which in turn compiles to a runtime format utilizting lower level runtime environments such as D3, HTML5 Canvas, and WebGL.

Visualizations are formed from parameterized templates which are recursively transformed into legal VGL or VG specifications. In Saite, creating and transforming these templates is generally done on the server side in typical REPL style development. Transformed templates (with their data or data source) are sent to one or more sessions (brower viewers) for rendering.

Saite also functions as an example application built with Hanami. As such it has all the capability of Hanami's template system and recursive transformation of parameterized templates.

Saite also uses the tab system provided by Hanami for automatic tab construction and updates, plus the application specific tab capabilities of that system. Further, Saite makes use of Hanami's visualization messaging system, in particular, the user-msg multimethod with implementations for application initialization, namespace creation, server side code execution, saving and reading of documents and code files, saving all visualizations, et.al.

There is a self installing/updating uberjar that makes a plug and play application of Saite. This is the quickest and easiest way to simply use Saite as a kind of "super notebook" or Clojure(Script) analog of RStudio. See aerosaite for more on this.

To install, add the following to your project :dependencies:

[aerial.saite "1.1.0"]

To get a full running system, you will first need to activate the server:

(ns aerial.saite.examples

  (:require
           ...
           [aerial.saite.core :as saite]
           ...))

(saite/start 3000) ; start the server on port 3000
;;;
;;; To stop the server:
;;; (saite/stop)

Once the server is running, in your browser, navigate to the port you used when starting it. The client will initialize and show the starting page. The default starting page is determined on the client via the header function aerial.saite.core/saite-header. The 'on page load' initialization code block is the final piece of code in aerial.saite.core.cljs.

[total new documentation being written]

An attempt at an outline for the documentation

• Overview

  • Videos

  • Tutorials

  • Capabilities

    • Dynamic data exploration
    • Interactive documents
    • Full client/server dashboards

  • startup

    • <-> convert tab
    • Scratch tab

  • Controls panel

    • Logo
    • Session marker
    • Application spinner
    • Load and save group
      • Documents
      • Code files
    • Editor visibility group
      • Open (show)
      • Close (hide)
    • Tab manipulation group
      • Add
      • Duplicate
      • Frame mgt
      • Undo and Redo
      • Left/right movement
      • Edit
      • Delete
    • Info group
      • Theme
      • Quick help
      • Documentation

  • Tabs panel

• Control panel

• Tabs

  • Editor / output
  • Editor / document body

• Editors

  • Modes
    • emacs, vim, sublime
  • Paredit
  • Keys
    • Bindings
    • Functions
    • Configuration
    • Defaults

• Namespaces

  • Per tab and/or cross tab
  • Dynamic dependencies
  • Requirements

• Document construction

  • Picture frames
  • Visualizations
  • Markdown
  • LaTex
  • Live editors
  • Tab local frame markdown and live editor defaults
  • Auto frame insertions
    • Vis
    • Text
    • Code mirror
    • Markdown

• Dashboard construction

  • Reactive components
  • Callback symbols and registry
  • Mixed client/server code

• Auto run on document load

  • Three modes
    • :clj, :cljs, :mixed
  • Order of running
  • Methods