このチュートリアルでは、domina libraryを使って、もっとClojureっぽい ログインフォームのバリテーションを実現してみよう。
A series of tutorials to guide you in creating and setting up ClojureScript (CLJS) projects.
If you ask yourself why the series has been named
if the ClojureScript language is only a couple of years old, you're
right. It just happens that I started this series while trying to port
on ClojureScript few examples from the
should have been
current-cljs. Now it's too late to change it.
If you don't know anything about Clojure (or Lisp), I strongly recommend to study it before to start reading this series.
Even if the net is plenty of outstanding resources on Clojure programming language, you can't understimate the benefit of reading few books on Clojure and on other Lisp dialects:
- SICP - Structure and Interpretation of Computer Programs: this is still the best book I have ever read about Computer Programming in my very long carrier, even if it uses the Scheme programming language (a Lisp dialect);
- On Lisp: if you want to make your hands dirty with macros, this is the place to start from even if it uses CommonLisp (a well known Lisp dialect);
- Clojure Programming: written by three of the most heroics clojureans, it contains everything you need to know about Clojure and its ecosystem;
- Programming Clojure: written by another legendary clojurean, it represents the easiest path to approach Clojure;
- The Joy of Clojure: the title speaks by itself. A must read
- The Annotated Clojure Reference Manual by Rich Hickey: The most missed book on Clojure :).
More people asked me which operating system and editor/IDE are most appropriated for developing Clojure/ClojureScript code. I personally use Mac OS X and Ubuntu. On top of those I use Emacs with the standard stuff to be productive with Clojure programming. Because I'm aged, *nix and Emacs are the OS/Editor I know better. That said, in this series you're not going to find any suggestion about any OS or IDE/Editor. Use whatever tool fits better your habits. I have too much respect for people developing IDE/plugins for Clojure/ClojureScript to say that one is better than another.
This series of tutorials will guide you in creating, setting up and running simple CLJS projects. The series follows a progressive enhancement of the project itself.
NOTE 1: I suggest to code yourself the content of the series. In my experience it is always the best choice if you are not already fluent with the programming language you have under your fingers.
That said, assuming you already have installed leiningen 2, to run the latest available tutorial without coding:
git clone https://github.com/magomimmo/modern-cljs.git
lein cljx once # used from tutorial-16 forward
lein ring server-headless
- open a new terminal and cd in the modern-cljs main directory
lein cljsbuild once
lein trampoline cljsbuild repl-listen
- visit login-dbg.html and/or shopping-dbg.html
- play with the repl connected to the browser
NOTE 2: If you want to access the code of any single tutorial because you don't want to
copy&pasteit or you don't want to write it yourself, do as follows:
git clone https://github.com/magomimmo/modern-cljs.git
git checkout tutorial-01 # for tutorial 1, tutorial-02 for tutorial 2 etc
In this tutorial we're going to explore CLJS/CLS compilation modes by
using the usual
lein-cljsbuild plugin of
leiningen, but we'll
discover a trouble we'll solve by using a new feature of the
In this Tutorial we're going to introduce domina events which, by wrapping Google Closure Library event management, allows to follow a more clojure-ish approach in handing DOM events.
In this tutorial we're going to face the need to programmatically manipulate DOM elements as a result of the occurrence of some DOM events.
In this tutorial we're going to extend our comprehension of CLJS by introducing Ajax to let the CLJS client-side code to communicate with the CLJ server-side code.
In this tutorial we're going to enrich our understanding of Domina
events by applying them to the
login form example we introduced in
the 4th Tutorial.
In this tutorial we're going to cover the highest and the deepest layers of the Login Form example we started to cover in the previous tutorial.
One of our long term objectives is to eliminate any code duplication from our web applications. That's like to say we want firmly stay as compliant as possible with the Don't Repeat Yourself (DRY) principle. In this tutorial we're going to respect the DRY principle by sharing validators between the client (i.e. CLJS) and the server (i.e. CLJ).
In this tutorial we are going to prepare the stage for affording the
unit testing topic. We'll also introduce the
Enlive template sytem
to implement a server-side only version of the Shopping Calculator
aimed at adhering to the progressive enanchement implementation
strategy. We'll even see how to exercize code refactoring to satisfy
the DRY principle and to solve a cyclic namespaces dependency problem.
In this tutorial, after having added the validators for the
shoppingForm, we're going to introduce unit testing.
In this tutorial we make unit testing portable from CLJ to CLJS (and
vice-versa) by using the
clojurescript.test lib and the
To be respectful with the progressive enhancement strategy, in this tutorial we're going to integrate the form validators for the server-side Shopping Calculator into the corresponding WUI (Web User Interface) in such a way that the user will be notified with the right error messages when the she/he types in invalid values in the form.
In this tutorial we're going to digress about two topics. The setup of
a more comfortable browser REPL based on nREPL. The setup of a more
comfortable project structure by using the
profiles features of
Copyright © Mimmo Cosenza, 2012-2013. Released under the Eclipse Public License, the same as Clojure.