Google Closure Template Project – Getting Started Quickly with Google Closure Tools

One of the hardest things about getting started properly with Google Closure Tools is that it has a huge amount of framework boilerplate that needs to be organised in order to write your first line of code. I have found that the effort is definately worthwhile but the process can definatelly be simplified.  These views are shared by many in the community and projects like plovr from Michael Bolin (author of the most awesome Closure: The Definitive Guide) offer alternatives to get started in a more efficient and intuitive way.

I created this sample project to get you going on your own closure project very quickly.  I did not use plovr as I’m not a fan of the additional server (hence additional deployment step, hence one more thing that can go wrong) design.

To get started with this sample project you need to do the following:

  1. Download this zip and extract somewhere on your dev box <installdir>.
  2. Download (if required) python 2.6 or 2.7.  Note: do not download 3+ as the script does not work in 3 without modifications.
  3. SVN Checkout ‘’ to <installdir>\lib\closure-library (which is currently empty).  You may want to set up externals if you are using svn in your project.  Once this step is completed you should have the following directory tree in your project <installdir>.
    • <installdir>\src\…
    • <installdir>\lib\soy\…
    • <installdir>\lib\closure-library\
    • <installdir>\lib\closure-library\closure\…
    • <installdir>\lib\closure-library\third_party\…
  4. Edit <installdir>\build.bat, ensure python install path is correct
  5. Run <installdir>\build.bat
  6. If everything above worked and both <installdir>\index.html and <installdir>\index.compiled.html show the following text:SumExpected Value: 15Actual Value: 15

Thats it, you have a running closure project, you can now use goog.require / goog.provide in your own source and have the above scripts manage all your dependencies.  You can also use soy templates without any additional work.

Now just look around the code and familiarise yourself with the structure of the code.  I’ll go through the main items here:

build.bat: The build file.  I used a windows batch file as using Ant is too java specific, using NAnt or MSBuild is too .Net specific.  Apologies to non win people but changing this to any other build tool should be very easy.

externs.js: If your source requires access to external APIs then they need to be defined in this file.  See here for documentation on extern files (

index.html: A development html file.  This is used in development mode to debug your application.

index.compiled.html: Production html file.  This file includes the compiled javascript and soy files

requirements.js: This file defines the entry point into the application.  This is required as the closure compiler and do not accept html files as valid input files.

deps.js: This file is created during the build process and its role is to define the dependencies of the application.  This dependency tree is used in development mode (index.html) to load all the neccessary js files.

lib\: Contains the compiler, the closure library, soy library files, etc

lib\closure-library\: An svn extern link to (You need to set this up yourself as its 20+ MB)

src\: Your source code.  It is recommended you use a Java like namespace directory structure.  Eg.  Class should live in src\picnet\ui\tools\Grid.js file.  Note: google use lowercase file names (i.e. grid.js) but this makes little sense to me so I choose to spit in the face of conventions.

Thanks All

Guido Tapia


About The Author

Guido Tapia

Over the last 2 years Guido has been involved in building 2 predictive analytics libraries for both the .Net platform and the Python language. These libraries and Guido's machine learning experience have placed PicNet at the forefront of predictive analytics services in Australia.

For the last 10 years Guido has been the Software and Data Manager at PicNet and in that time Guido has delivered hundreds of successful software and data projects. An experience architect and all round 'software guy' Guido has been responsible for giving PicNet its 'quality software provider' reputation.

Prior to PicNet, Guido was in the gaming space working on advanced graphics engines, sound (digital signal processing) engines, AI players and other great technologies.

Interesting Links:

Leave a Reply

Your email address will not be published. Required fields are marked *


You may use these HTML tags and attributes: <a href="" title=""> <abbr title=""> <acronym title=""> <b> <p> <ul> <li> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <strike> <strong>