ClosureBuilder 0.3.7 (beta)

The Closure Builder is a simple dependency management tool for The Closure compiler

Installation Instructions

pip install closurebuilder

Configuring project to use with PasteScript

Create new python package

$ paster create MyPackage

Modify MyPackage/setup.py

from setuptools import setup, find_packages
import sys, os

version = '0.1'

setup(name='MyProject',
      .....
      paster_plugins=['ClosureBuilder'],
      .....
)

Go to the MyPackage folder and execute

$ python setup.py egg_info

Now, the ClosureBuilder commands are available.

Run the following command to create the ClosureBuilder folder structure

$ paster init

This command will create the following files in mypackage folder

closure\
    sources.txt
    compiler-settings.txt
    closure-top.txt

Download latest Closure Library source files and move them into MyPackage/mypackage/closure/closure-library folder. Open sources.txt file and uncomment include directive

#
# Directories where source files can be found
#

include closure-library

include directive tells the ClosureBuilder to search source files in specified folder (in our case in closure-library folder). You can specify more than one include directive, e.g.

#
# Directories where source files can be found
#

include closure-library
include /home/andrey/some_other_library
include /home/andrey/my_library_1 strictly
include "/home/andrey/my library 2" strictly

Now we are ready to create and compile javascript application.

Creating application

Just execute the following command to create application

$ paster create-app helloworld

This command will create the following files in closure folder

helloworld\
    helloworld.js
    helloworld.css
    manifest.txt

Modify helloworld.js

.....

/**
 * helloworld.Helloworld bootstrap point
 * @final
 */
helloworld.Helloworld.prototype.entrypoint = function()
{
  alert('Hello World!!!');
}

.....

Compiling application

Execute the following command to compile your application

$ paster compile helloworld

After successful command execution the compiled files will be placed in closure/compiled/helloworld/ folder.

The ClosureBuilder standalone

If you do not want to use paster, you can use closure-builder command-line script. closure-builder has absolutely the same commands.

To initialize ClosureBuilder folder structure execute the following commands

$ mkdir MyProject
$ cd MyProject
$ closure-builder init

Now you can use closure-builder in the same manner as described above.

File closure-top.txt

NOTE: This file is used only if you use closure-builder command-line script instead of paster

The ClosureBuilder reads this file to obtain meta information of the project. At this moment only 3 fields are used: Author, Author-mail and License.

File compiler-settings.txt

This file declares common compiler settings for all applications in project.

File sources.txt

This file declares where to search sources files.

To include/exclude all sources in specified folder (recursively):

• include PATH
• include PATH loosely (same as include PATH)
• include PATH strictly
• exclude PATH

To include/exclude specified source:

• include source SOURCE
• include source SOURCE loosely (same as include source SOURCE)
• include source SOURCE strictly
• exclude source SOURCE

Distinction between strict and loose inclusion is that strict inclusion causes an error if source provides more than one namespace.

For example, we have A, B, C and D folders. B is A's subfolder. C is B's subfolder. D is C's subfolder.

To include all sources in these folders:

include A

To include all sources in A and B folders only:

include A
exclude C

To include all sources in A and D folders only:

include A
exclude B
include D

File manifest.txt

Example

#
# Application manifest
#

compile application myapp
set target ../public

define goog.DEBUG=false

compile module myapp.Module1:
    set uri "/public/js/module1.js"
    set metadata:
        set somemeta1 "meta1"
        set somemeta2 "meta2"
    write to js/module1.js

compile module myapp.Module2:
    set uri "/public/js/module2.js"
    write to js/module2.js

compile module myapp.Module3:
    set uri "/public/js/module3.js"
    depends on myapp.Module1
    depends on myapp.Module2
    write to js/module3.js

write to js/main.js
write css to css/main.css

CSS compilation

The ClosureBuilder can obfuscate CSS-files and generate CSS renaming map for using with goog.getCssName() function. The given feature turns on automaticly, if you use function goog.resource() in your source files. For more information see goog.getCssName().

Example

goog.provide('myapp')

goog.resource('myapp.css')
...
// now you can use goog.getCssName() to get obfuscated css class name

Module compilation

Add compile module directive to the application manifest file to tell the ClosureBuilder to compile application with specified module. The ClosureBuilder automatically adds the module info and the module url in ModuleManager. Thus, you should not do it manually.

To load the module from your application you can use the following code

goog.module.ModuleManager.getInstance().execOnLoad('myapp.Module1',
  function() {
    alert('myapp.Module1 is loaded');
  }
);

Note: Do not forget to call goog.module.ModuleManager.setLoaded() to tell the ModuleManager that module was loaded completely

Usefull links

Closure Compiler Documentation

Closure Library

Feedback

Issue tracker

Mail

Changes

0.3.7:

• Bug fix: Module information should be added immediately after goog.module.ModuleLoader

0.3.6:

• Bug fix: Modules with the same dependency does not compile

0.3.5

• Bug fix: Using directives "include"/"exclude" in the manifest.txt causes an error.

0.3.4

• New directives are available: "include source" and "exclude source"

0.3.3

• Directive "scan" was deprecated
• New directives are available instead of "scan" directive: "include" and "exclude"

0.3.2

• New compiler-settings directive "compiler"

0.3.1

• Bug fix: directive "add extern" supports now relative and absolute paths