In this chapter, we'll setup our system to run Clojure. We'll install all the required dependencies and run the "Hello World" program.

Clojure Tutorial - Installing and Testing Required Dependencies

We need help from our editors to tame the LISPy syntax. This chapter walks through the tools we will need and why.

Editor Tools

How to Set up Visual Studio Code for Clojure Development

Setup IntellJ IDE for Clojure development.

Clojure IDE Setup - Using the Cursive Plugin With IntelliJ

How to Use Emacs with Clojure - 6 Packages You'll Need

Getting Started

Clojure is neither compiled nor has its own VM. Instead, it runs on VMs of other languages. In this lesson, we'll learn about official and unofficial ports and support status.

Understanding the Benefits of Clojure's Hosted Nature

Let's get our hands dirty with native data types and common operations.

Clojure Basics - Syntax and Native Data Types

C-style languages invisibly impose a syntax, whereas Lisps do not. This makes Lisps more expressive and easier to grasp.

What is Syntaxlessness? How to Write More Expressive Code

Since Clojure is hosted, it can tap into ecosystems of other languages. This has led to multiple build tools for different ecosystems. Choosing the right build tool might get tough for a beginner as the pros and cons might not be known. In this module, we'll learn about the general state of build tools in Clojure and choose the right tool for our project.

Clojure Build Tools - Leiningen, Boot, Shadow CLJS & Figwheel

Enough talking, let's create a new repository and set up a project from scratch, using Shadow CLJS.

How to Set Up a Shadow CLJS Project From Scratch

Our first project is now in place. In this chapter, we'll learn how to build and run it. We'll also explore some other build targets and explore Shadow with Reagent, a ClojureScript wrapper to React.

Getting Familiar With The Shadow CLJS API

The REPL is an essential element of a Lisper's toolkit. In this chapter, we'll solidify our grasp of the REPL and editor integration. We'll also learn about some problems that come with the REPL.

An Introduction to Clojure REPL and Evaluating Code Inline

Paredit is a tool to help with structural editing. It helps you write and modify S-Expressions with so much ease that the brackets will almost disappear! In this chapter, we'll learn fundamental Paredit commands.

A Clojure Beginner's Guide to Structural Editing with Paredit

Language Semantics

Clojure offers many control flow conditionals, like if-else blocks. In this chapter, we'll study the API of a few such methods.

Clojure Conditionals - Understanding Flow Control Operators

Atoms are thread-safe containers for handling mutable state. In this chapter, we'll learn how to create and manipulate atoms. We'll also learn how to hook into an atom's lifecycle and execute side-effects.

Atoms in Clojure - How to Create and Manipulate Them

There are many ways to define a function and parse arguments. In this chapter, we'll learn more about function definition, destructuring and some helpful higher-order functions.

Clojure Functions - Definitions, Distinctions, and Examples

Clojure sequences are abstract. In this chapter, we'll make sense of what exactly we mean by that, and learn about common operations.

Sequence Operations

Nested calls can become hard to manage. Threading macros help us take control. In this chapter, we'll learn about the concept of threading macros and study three commonly-used versions.

Threading Macros in Clojure - Thread-Last vs Thread-First vs As

Clojure lets you write code close to the metal ie the host language. In this chapter, we'll learn about constructs and techniques to interact with JavaScript within Clojure.

Clojure Constructs and Techniques to Interact with JavaScript

Standard Library

Walkthrough the components and concepts we will implement, with a video demo of the final app.

Overview

In this chapter, we will bootstrap a project using create-cljs-app and understand the code generated. We'll also study Hiccup, a CLJS alternative for JSX, and various ways to require namespaces.

Clojure Project Setup with create-cljs-app

Reagent is a minimalist Clojure wrapper for React. It exposes all React APIs including hooks and is one of the most popular Clojure projects. This chapter is a theoretical introduction to Reagent. We'll learn about components, third-party integrations and local state.

What is Reagent? The Minimalist Clojurescript React Wrapper

We have already learned how third-party components fit with Reagent. In this chapter, we'll implement React Router in the Tinycanva app.

How to Install React Router from NPM and Set Up Routes

In this chapter, we'll set up our UI library and CSS build process using PostCSS.

How to Set Up a UI Library & CSS Build Process Using PostCSS

Reframe is a flux-like library for uni-directional data flow. In this chapter we'll study the six-step Reframe loop.

Introduction to React State Management

Let's implement the concepts learned in the chapter on Reagent and React Router to build a login page..... plus the magic of REPL!

App Structure and Authentication UI

Set up Firebase project and configure authentication.

Setting Up Firebase Projects and Authentication for Clojure Apps

In this chapter, we'll initiate the Reframe loop for our login form, dispatch form submit events and handle them, ie implement steps 1 and 2.

Auth Event Handlers

We dispatched an event and wrote a handler. The handler returned an effects map, with a custom effect `:firebase/email-auth`. In this chapter, we'll create the custom effect handler and initialize the Firebase app.

Auth Effects and Firebase Initialization

In this chapter,  we'll connect the UI to the Reframe loop and create loading indicators and subscriptions to check if the user logged in successfully.

How to Create Firebase Data Subscriptions in Reframe

We have authenticated our users, but now they're stuck on the login screen. This chapter is about building re-usable containers to redirect users to authorized pages.

How to Build Reusable Containers for Clojure Apps with Reagent

In this chapter, we will integrate Reframe and Firebase to save the graphic "entity". This is analogous to a POST request with a traditional REST API.

How to Store Reframe Data in Firebase Without a REST API

Create Reframe handlers to read and delete graphics. Analogous to GET and DELETE in a REST API.

Read and Delete Graphics

Integrate Reagent and Reframe to create UI for listing and deleting graphics.

How to Integrate Reagent and Reframe With Clojure to Create a UI

Making graphic list items clickable; and the editor(detail) route. In the process, we'll learn how to use React's Higher Order Components with Reagent.

Using React Higher Order Components to Frame a Canvas Editor

In this chapter, we will integrate FabricJS with our app and create an HTML canvas-based editor.

How to Create an HTML Canvas Editor with Clojure and FabricJS

We have an editor in place, but it doesn't save data to Firebase. It is also not equipped to load data from Firebase. In this chapter, we'll create Reframe components to store data. We'll then update the editor to load data from Firebase. We will also extend the editor functionality.

Saving graphics

Tinycanva

Packaging an app consists of multiple steps, like configuration, minification etc. In this chapter, we'll package our app with production configuration and create an optimized JS bundle, that can be deployed on any CDN.

Production packaging

Large apps degrade user experience and one way to control that is to split our code into chunks. This chapter will walk through tools afforded by Shadow to split our app code. We'll also implement the splits and analyze performance gains.

Code splitting

Shadow comes bundled with a test runner. Clojure comes bundled with a unit testing library. In this chapter, we'll implement the two and learn about testing techniques for Reframe handlers.

Unit Testing with Clojure - Techniques for Reframe handlers

Going forward - information about online Clojure communities, server-side Clojure concepts, companies and job boards.

Conclusion

Advance Concepts

Clojure is a functional hosted LISP known for its expressiveness, which has excellent interop with Javascript, Java, and Microsoft's Common Language Runtime (CLR). 

Many developers praise the elegance and productivity Clojure allows, but for many it seems like an esoteric language with an "ugly" syntax that is impossible to get started with. This course will change that view and show you how to be productive with this marvelous language.

In this course, we'll build a web-based graphics editor similar to Canva. We'll explore Clojure from the perspective of a JavaScript developer. Along the way, we'll also explore state management, authentication, API integration with Google Firebase and interop with NPM.

This course takes you from zero to an understanding of Clojure semantics, LISP tools, and building a production-ready React application in just a few hours. 

We'll start with the basics and build up to writing a fullstack app with both frontend and backend in Clojure. 

The frontend, built using ClojureScript (Clojure that runs on JavaScript) will be a single page React application with routing, key-based authentication and API integration, which will save, list, edit and delete graphics.
 

The backend is hosted on Google Firebase. 

Throughout the course, we'll learn about tools like REPL that aid development. Towards the end, we'll learn about advanced concepts like code splitting and end-to-end testing.

Clojure is unlike other languages as it is hosted on, and can leverage, existing VMs. This means that you can learn Clojure once and write it on the backend with JVM or CLR, and the frontend with JavaScript. If a new technology like Rust takes over the world tomorrow, you will probably be able to continue to write Clojure because a Rust port is already in the making.

By the end of this course, you'll have a superpower: the ability to write fullstack Clojure applications.

Build a Fullstack Web Graphics Editor in Clojure and React

This is a course on Clojure for React developers in which we'll build a web-based graphics editor similar to Canva.

Tinycanva: Clojure for React Developers

The concept of tree-based codes aka LISPs

Editor integrations that make writing LISPs easy

Mental models for Clojure's rich standard library

Understanding of tools like NREPL to aid fast feedback

Hosted nature of Clojure and its ability to tap into JVM, JavaScript, CLR and other language ecosystems

Syntaxlessness and expressiveness of the language

How to create React applications with Clojure

Integration with APIs using Google Firebase

Key-based authentication and access control

Integration with React Router and Fabric JS

Map of communities and resources that can help when you get stuck

We have an editor in place, but it doesn't save data to Firebase. It is also not equipped to load data from Firebase. In this chapter, we'll create Reframe components to store data. We'll then update the editor to load data from Firebase.

Saving a graphic via details page is technically an 

 event, since the graphic node already exists in Firebase. Updating a Firebase object includes making a call to the 

 method with a node and keys to edit. Our graphic currently has two keys: 

 function overwrites or creates new key-value pairs, ie if we pass 

 will be overwritten. But if we pass a non-existent field like 

We have so far dispatched an event before writing a handler. But we'll create the handler first in this case, because we don't have a UI yet:

(rf/reg-event-fx
 ::update-graphic
 (fn [{:keys [db]} [_ graphic-id new-graphic]]
   {:db (assoc db ::updating-graphic? true)
    :firebase/update {:node (str "/graphics/" (-> db ::user :uid) "/" (name graphic-id))
                      :data new-graphic
                      :on-success [::update-graphic-success graphic-id new-graphic]
                      :on-error [::update-graphic-error]}}))

(rf/reg-event-db
 ::update-graphic-success
 (fn [db [_ graphic-id new-graphic]]
   (-> db
       (assoc-in [::graphics graphic-id :fabric-json] (-> new-graphic :fabric-json js->clj))
       (dissoc ::updating-graphic?))))

(rf/reg-event-db
 ::update-graphic-error
 (fn [db [_ err]]
   (js/console.log err)
   (dissoc db ::updating-graphic?)))

 handler. We set the loading indicator and request to call the 

 events are dispatched in response to the SDK call. Notice how we pass the 

 handler. This is required to update the 

 when the Firebase update call is successful.

 handler, we take the freshly-saved graphic and update the value of 

(rf/reg-fx
 :firebase/update
 (fn [{:keys [node data on-success on-error]}]
   (-> firebase
       .database
       (.ref node)
       (.update (clj->js data))
       (.then #(when on-success (rf/dispatch on-success)))
       (.catch #(when on-error (rf/dispatch (conj on-error %)))))))

(rf/reg-sub
 ::updating-graphic?
 #(-> % ::updating-graphic?))

 component has two dependencies on the Reframe state:
1. it needs to save the current graphic to Firebase
2. it needs to render the already saved graphic to Canvas

 component and make this data available to the editor:

(defn page [props]
  (let [graphic-id (-> props
                       :match
                       (goog.object/getValueByKeys "params" "graphicId")
                       keyword)
        graphic (when graphic-id
                  @(rf/subscribe [:app.domain.firebase/graphic-by-id graphic-id]))
        ;; subscribe to updating-graphic?
        updating-graphic? @(rf/subscribe [:app.domain.firebase/updating-graphic?])]
    [:<>
     [:> router/props-elevator {:elevate-fn #(reset! route-props %)}]
     (when graphic
       [:<>
        [nav graphic-id graphic]
        [editor/editor {:f-canvas (-> editor-state deref :f-canvas)
                        :set-f-canvas #(swap! editor-state assoc :f-canvas %)

                        ;; pass Reframe state to editor
                        :saving? updating-graphic?
                        :on-save #(rf/dispatch [:app.domain.firebase/update-graphic graphic-id {:fabric-json %}])
                        :init-state (-> graphic :fabric-json)}]])]))

We have passed all the required props to the editor. Let's now modify it with the ability to save data.

 method. This method converts the canvas into a JS object which can be saved in a database and used to re-create the canvas later. We'll create a 

 component to house the save button. We'll also add the functionality to save the canvas as svg or png:

(defn export-png [f-canvas]
  (let [data-url (.toDataURL f-canvas (clj->js {:format "png"}))]
    (saveAs data-url "export.png")))

(defn export-svg [f-canvas]
  (let [svg (.toSVG f-canvas)
        blob (new js/Blob [svg] (clj->js {:type "text/plain;charset=utf-8"}))]
    (saveAs blob "export.svg")))

(defn toolbar [f-canvas saving? on-save]
  [:div.flex.justify-between.pr-3
   [:div.flex
    [:> Button {:minimal true
                :text "Export PNG"
                :icon "media"
                :on-click #(export-png f-canvas)}]
    [:> Button {:minimal true
                :text "Export SVG"
                :icon "document"
                :on-click #(export-svg f-canvas)}]
    ]
   [:> Button {:intent (.-PRIMARY Intent)
               :text "Save"
               :loading saving?
               :on-click #(on-save (.toJSON f-canvas))
               :icon "floppy-disk"}]])

---
title: Saving graphics
slug: tc-save
description: We have an editor in place, but it doesn't save data to Firebase. It is also not equipped to load data from Firebase. In this chapter, we'll create Reframe components to store data. We'll then update the editor to load data from Firebase. We will also extend the editor functionality.
code: https://gitlab.com/fullstackio/books/newline-course-apps/shivek-khurana-tinycanva-clojure-for-react-developers-app/-/tree/main/code/module_04/lesson_04.17/App/source_code/tinycanva?ref_type=heads
---

# Saving graphics

We have an editor in place, but it doesn't save data to Firebase. It is also not equipped to load data from Firebase. In this chapter, we'll create Reframe components to store data. We'll then update the editor to load data from Firebase.

## Update Firebase Reframe components

Saving a graphic via details page is technically an **update** event, since the graphic node already exists in Firebase. Updating a Firebase object includes making a call to the `update` method with a node and keys to edit. Our graphic currently has two keys: `name` and `created-at`.

`update` function overwrites or creates new key-value pairs, ie if we pass `name` to the update function, the existing `name` will be overwritten. But if we pass a non-existent field like `fabric-json`, a new key-value pair will be created.

### Event handler

We have so far dispatched an event before writing a handler. But we'll create the handler first in this case, because we don't have a UI yet:

```clojure { actualFilename=./protected/source_code/tinycanva/src/app/domain/firebase.cljs endLine=135 startLine=115 statedFilename=./tinycanva/src/app/domain/firebase.cljs url=https&#x3A;//gitlab.com/fullstackio/books/Build-Canva-with-Clojurescript/module_04/lesson_04.17/protected/source_code/tinycanva/src/app/domain/firebase.cljs#L115 }
(rf/reg-event-fx
 ::update-graphic
 (fn [{:keys [db]} [_ graphic-id new-graphic]]
   {:db (assoc db ::updating-graphic? true)
    :firebase/update {:node (str "/graphics/" (-> db ::user :uid) "/" (name graphic-id))
                      :data new-graphic
                      :on-success [::update-graphic-success graphic-id new-graphic]
                      :on-error [::update-graphic-error]}}))

(rf/reg-event-db
 ::update-graphic-success
 (fn [db [_ graphic-id new-graphic]]
   (-> db
       (assoc-in [::graphics graphic-id :fabric-json] (-> new-graphic :fabric-json js->clj))
       (dissoc ::updating-graphic?))))

(rf/reg-event-db
 ::update-graphic-error
 (fn [db [_ err]]
   (js/console.log err)
   (dissoc db ::updating-graphic?)))
```

`update` handler is similar to the `delete` handler. We set the loading indicator and request to call the `:firebase/delete` effect. The `:on-success` and `:on-error` events are dispatched in response to the SDK call. Notice how we pass the `graphic-id` and `new-graphic` map as the `:on-success` handler. This is required to update the `app-db` when the Firebase update call is successful.

In the `on-success` handler, we take the freshly-saved graphic and update the value of `fabric-json` in `app-db`. This is passed to the `editor` component as `init-state`.

### Effect handler

The `:firebase/update` effect handler calls `update` on the given `node` and dispatches `on-success` and `on-error` events respectively:

```clojure { actualFilename=./protected/source_code/tinycanva/src/app/domain/firebase.cljs endLine=202 startLine=194 statedFilename=./tinycanva/src/app/domain/firebase.cljs url=https&#x3A;//gitlab.com/fullstackio/books/Build-Canva-with-Clojurescript/module_04/lesson_04.17/protected/source_code/tinycanva/src/app/domain/firebase.cljs#L194 }
(rf/reg-fx
 :firebase/update
 (fn [{:keys [node data on-success on-error]}]
   (-> firebase
       .database
       (.ref node)
       (.update (clj->js data))
       (.then #(when on-success (rf/dispatch on-success)))
       (.catch #(when on-error (rf/dispatch (conj on-error %)))))))
```

### Loading subscription

We need the `::updating-graphic?` flag to show a loading indicator:

```clojure { actualFilename=./protected/source_code/tinycanva/src/app/domain/firebase.cljs endLine=250 startLine=248 statedFilename=./tinycanva/src/app/domain/firebase.cljs url=https&#x3A;//gitlab.com/fullstackio/books/Build-Canva-with-Clojurescript/module_04/lesson_04.17/protected/source_code/tinycanva/src/app/domain/firebase.cljs#L248 }
(rf/reg-sub
 ::updating-graphic?
 #(-> % ::updating-graphic?))
```

## Connect editor to Reframe state

The `editor` component has two dependencies on the Reframe state:
1\. it needs to save the current graphic to Firebase
2\. it needs to render the already saved graphic to Canvas

To tackle this, we need to update the `app.pages.graphics.detail/page` component and make this data available to the editor:

```clojure { actualFilename=./protected/source_code/tinycanva/src/app/pages/graphics/detail.cljs endLine=47 startLine=27 statedFilename=./tinycanva/src/app/pages/graphics/detail.cljs url=https&#x3A;//gitlab.com/fullstackio/books/Build-Canva-with-Clojurescript/module_04/lesson_04.17/protected/source_code/tinycanva/src/app/pages/graphics/detail.cljs#L27 }
(defn page [props]
  (let [graphic-id (-> props
                       :match
                       (goog.object/getValueByKeys "params" "graphicId")
                       keyword)
        graphic (when graphic-id
                  @(rf/subscribe [:app.domain.firebase/graphic-by-id graphic-id]))
        ;; subscribe to updating-graphic?
        updating-graphic? @(rf/subscribe [:app.domain.firebase/updating-graphic?])]
    [:<>
     [:> router/props-elevator {:elevate-fn #(reset! route-props %)}]
     (when graphic
       [:<>
        [nav graphic-id graphic]
        [editor/editor {:f-canvas (-> editor-state deref :f-canvas)
                        :set-f-canvas #(swap! editor-state assoc :f-canvas %)

                        ;; pass Reframe state to editor
                        :saving? updating-graphic?
                        :on-save #(rf/dispatch [:app.domain.firebase/update-graphic graphic-id {:fabric-json %}])
                        :init-state (-> graphic :fabric-json)}]])]))
```

We made two changes to the `page` component. We added a subscription to `updating-graphic?` and passed in three extra props:

-   update flag
-   function to save the graphic (dispatches the `:a.d.f/update-graphic` event) 
-   initial state of the graphic canvas. Notice the `:fabric-json` key - we don't have it yet, but we'll store the JSON representation of the canvas under this key.

We have passed all the required props to the editor. Let's now modify it with the ability to save data.

## Saving Fabric canvas to Firebase

`fabric.Canvas` ships with a `toJSON` method. This method converts the canvas into a JS object which can be saved in a database and used to re-create the canvas later. We'll create a `toolbar` component to house the save button. We'll also add the functionality to save the canvas as svg or png:

```clojure { actualFilename=./protected/source_code/tinycanva/src/app/components/editor.cljs endLine=111 startLine=86 statedFilename=./tinycanva/src/app/components/editor.cljs url=https&#x3A;//gitlab.com/fullstackio/books/Build-Canva-with-Clojurescript/module_04/lesson_04.17/protected/source_code/tinycanva/src/app/components/editor.cljs#L86 }
(defn export-png [f-canvas]
  (let [data-url (.toDataURL f-canvas (clj->js {:format "png"}))]
    (saveAs data-url "export.png")))

(defn export-svg [f-canvas]
  (let [svg (.toSVG f-canvas)
        blob (new js/Blob [svg] (clj->js {:type "text/plain;charset=utf-8"}))]
    (saveAs blob "export.svg")))