Browse files

added tutorial 7

  • Loading branch information...
1 parent 781b689 commit 22d25cd0e09e22eb4fe84e7352011d631d91e98b @magomimmo committed Nov 18, 2012
@@ -65,9 +65,12 @@ login form validation more clojure-ish.
In this tutorial we're going to investigate and solve in two different
ways the not so nice issue we met in the last tutorial.
-## Tutorial 7 - TO BE DONE
+## Tutorial 7 - Being doubly aggressive
+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 do not know how to manage yet.
# License
@@ -27,7 +27,7 @@ one we defined in `login.cljs`.
As we anticipated in the [previous tutorial][1], this behaviour
depends from Google Closure Compiler driven by `lein-cljsbuild`
## Introducing Google Closure Compiler (CLS)
@@ -36,7 +36,7 @@ In the [first tutorial][3], we set the `:cljsbuild` keyword of
-(defproject ....
+(defproject ....
:cljsbuild {:builds
[{:source-path "src/cljs"
@@ -49,7 +49,7 @@ options:
The `:source-path` option instructs CLS to look for any CLJS source
code in the `src/cljs` directory structure. The `:output-to` option of
the `:compiler` keyword instructs CLS to save the compilation result
-in the `"resources/public/js/modern.js` file.
+in the `"resources/public/js/modern.js` file.
I'm not going to explain every single detail of CLJS/CLS pair of
compilers. The only detail it is useful to recap to investigate and
@@ -75,7 +75,7 @@ From the above discussion the reader could start bilieving in the
statement that CLJS is good only for *single page browser
application*. Indeed, there is a very modest solution to the above
conflict between more calls setting the same `onload` property of the
-JS `window` object: duplication!
+JS `window` object: duplication!
You have to duplicate the directory structure and the corresponding
build options for each html page is going to include that single
@@ -97,10 +97,10 @@ And here is the modified fragment of `project.clj`
(defproject ...
;; login.js build
{:source-path "src/cljs/login"
@@ -142,7 +142,7 @@ Now the simple made easy way:
`shopping.cljs` files;
* add a `script` tag calling the correponding `init` function in both
`login.html` and `shopping.html` files;
-* you're done.
+* you're done.
> NOTE 2: if you do not `^:export` a CLJS function, it will be subject
> to Google Closure Compiler `:optimizations` strategies. When set to
@@ -152,7 +152,7 @@ Now the simple made easy way:
> name is annotated with `:export` metadata, its name is going to be
> preserved and can be called by standard JS code. In our example the
> two functions will be available as: `modern_cljs.login.init()` and
-> ``.
+> ``.
Here is the interested fragment of `login.cljs`
@@ -247,8 +247,8 @@ Here is the interested `login.html` fragment
<script src="js/modern.js"></script>
- modern_cljs.common.init('loginForm', modern_cljs.login.validate_form);
- </script>
+ modern_cljs.common.init('loginForm', modern_cljs.login.validate_form);
+ </script>
> NOTE 4: CLS compiler translates "-" in "_". So
@@ -281,8 +281,8 @@ Here is the interested `shopping.html` fragment
<script src="js/modern.js"></script>
- modern_cljs.common.init('shoppingForm',;
- </script>
+ modern_cljs.common.init('shoppingForm',;
+ </script>
> NOTE 6: See NOTE 4.
@@ -317,9 +317,10 @@ In a subsequent tutorial we'll introduce [domina event][6] management
to further improve our functional style in porting
[Modern JavaScript samples][7] to CLJS.
-# Next step - TO BE DONE
+# Next step - Being doubly aggressive
+In the [next tutorial][8] we're going to explore CLJS/CLS compilation modes by
+using the usual `lein-cljsbuild` plugin of `leiningen`.
# License
@@ -333,4 +334,4 @@ License, the same as Clojure.
Oops, something went wrong.

0 comments on commit 22d25cd

Please sign in to comment.