Seeing Closure Script packaged as a single .jar motivated me to spend
the last two weeks on it. The entire welcome process has been
smoothed over and the example scaffold expanded to four starting
points: Hello World (soy), modules, jQuery, and Rails 3.
Working with modules has been greatly simplified. I added a feature
so that you don't have to count the number of files in every module.
The modules example from the plovr tests is used for the scaffold.
Closure Library is no longer bundled with Closure Script. Library
being updated daily now, it seems. An example of a complex Script
that can update a subversion repository in a background thread is part
of the scaffold. It is automatically started as part of the welcome
process. I'd like to make one for git and hg too but not before I get
some feedback. Or maybe someone will beat me to it.
The Subversion updater got me thinking about how folks share Closure
code (non-Google folks, specifically). Others languages and
frameworks have some kind of multi-user repository: CPAN, RubyGems,
PEAR, etc. Not everyone is comfortable signing a CLA and releasing
under Apache 2.0 so I think Closure will need something other than the
Library repository in the long run.
Closure Script not only provides a platform for developing a feature-
rich repository client directly in the build tool, but it helps get
the compiler options out of a central config or platform-specific
shell programs and into context for easier sharing. It also provides
a common platform for advanced build steps, like CSS and SVG
transforms, that will work even under Windows.
Closure Script 1.3 is now at RC1. Please help test.
Step 1: Download to a new folder:
https://github.com/dturnbull/closure-script/downloads
Step 2: Run from the new folder with Java:
-david