Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
Message from discussion Proper help on closure compiler
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
John Lenz  
View profile  
 More options Nov 14 2009, 1:51 am
From: John Lenz <concavel...@gmail.com>
Date: Fri, 13 Nov 2009 22:51:27 -0800
Local: Sat, Nov 14 2009 1:51 am
Subject: Re: [closure-compiler-discuss] Proper help on closure compiler

Until we have the documentation ready, here is a simple overview.  The
compiler supports compiling multiple javascript source files together (so
they are renamed and optimized as a unit) but the output divided into
"modules" that can be loaded separately.  The idea is that core
functionality can be part of the initial module that is initially loaded and
less used features can be loaded later.

Here is an example:

  java -jar compiler.jar --js src1.js --js src2.js  --js src3.js --module
first:2 --module second:1:first

This will create to modules:
  first.js
  second.js

The first module, I've named "first", contains the 2 file (the first two
--js parameters listed).  The second module, I've named "second", contains
one file, the next --js entry following those included in the first module,
the second module depends on the first.

"--module_output_path_prefix" is straightforward.

"--module_wrapper" is simply a way to add some extra text before and or
after the compiler output.  For example, if you wanted to add a comment to
the top of the file:

--module_wrapper "/* copyright 2010 */ %s"

Have fun.

-John

On Fri, Nov 13, 2009 at 1:09 AM, DotNetWise <alonec...@gmail.com> wrote:
> At this stage, there is no help other than command line help about
> these:
>  --module A javascript module specification. The format is
>    <name>:<num-js-files>[:[<dep>,...][:]]]. Module names must be
>    unique. Each dep is the name of a module that this module
>    depends on. Modules must be listed in dependency order, and js
>    source files must be listed in the corresponding order. Where
>    --module flags occur in relation to --js flags is unimportant.;
>    default:
>  --module_output_path_prefix Prefix for filenames of compiled js
>    modules. <module-name>.js will be appended to this prefix.
>    Directories will be created as needed. Use with --module.;
>    default: ./
>  --module_wrapper An output wrapper for a javascript module
>    (optional). The format is <name>:<wrapper>. The module name must
>    correspond with a module specified using --module. The wrapper
>    must contain %s as the code placeholder.; default:

> http://code.google.com/p/closure-library/issues/detail?id=50
> What about proper help with good examples?
> -Laurentiu


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.