Add option for verifying and minifying files

[dethe]

bin/build should have command-line options for minifying the resulting files and for verifying the javascript and css files.

Maybe even an option to build the html files to load css/js files directly without concatenating, so they don't have to be continually rebuilt in dev mode?

[CelticMinstrel]

Also, why does it report success when (for example) a JSON file has been found to have incorrect syntax?

[dethe]

That would be a bug.

[ztsai]

Just wondering if it's possible to have a dev environment where we don't need to run bin/build every time we make changes? It's especially annoying when I'm debugging, because I'll need to rebuild every time after I make some minor js changes. (and I'll often forget to do that......)
I'm thinking about a watch option that watches changes in js files and rebuild automatically, or even better, ability to run the server without building (I am not sure if it's feasible as I only scan through the build file, but maybe we can chain js files with requriejs?)

[dethe]

I think that's one of the next things I'll work on.

[CelticMinstrel]

I get the impression that running without building first is pretty infeasible, but there might be a way I've not thought of.

[dethe]

Now that we build the html files from templates, we could insert tags to load all the files in dev mode. We could have flags on bin/build to optionally lint/validate/minimize the files before linking them. For the runtime files it's a bit trickier, but in order to support offline we're going to have to use our local iframerunner.html anyway (not as secure, but it may be premature to worry about that), so we could templatize that too and load the runtime files directly instead of passing a link to the library from IDE to iframe. The hardest bit will be the code generated from blocks, but if we get enough value from this, that may be do-able.

One thing that came up when talking to students was whether we should standardize on var functionName = function functionName(/* args */){ /* body */); or on function functionName(/* args */){ /* body */ and now I remember why it should be the first (and unfortunately more verbose) one: In strict mode, function statements inside functions are prohibited. Since we're wrapping everything in IIFEs, we'll need to use var functionName = function ....

[dethe]

All of this is part of #269

[dethe]

As of the current developer branch there is no need for a build step any more.