I have went back in and re-done the work on the user defined MOJO (I
was extremely unhappy with what was done after looking at it) and it
should be done by tomorrow. It will contain a number of parameters
that the user will define. They are:
jsDirectory: the directory where the JS can be found. Default is
build output dir.
outputDirectory: the output dir for compressed files. Default is
build output dir.
=B7 replaceJavaScript: Whether to replace the files if
the input dir is the same as the output dir (default: false)
=B7 classifier: The classifier placed on the newly
created JavaScript files if the replaceJavaScript is false (default:
-compressed)
=B7 includes: Pattern of files to include in the
compression process. Default is all JS files allowed.
=B7 excludes: Pattern of files to exclude from the
compression process. Default is all JS files allowed.
=B7 licenseFiles: The license files to add in the header
of each compressed file.
The MOJO will piggy back on the current site compression MOJO, with
some minor tweaks to make it fully user defined.
Since we are adding a new goal, I would like to take this opportunity
to open up the floor for any additional features or improvements that
you believe should be done on the plugin, or would be very nice to
have. If there are none, we can go ahead with the planned 1.3 release
to only add in the new MOJO. The only one that comes to my mind is
the ability to compress CSS and/or HTML but, that seems to me to be
beyond the scope of a dedicated JavaScript compression plugin and
should be implemented in a different manner.
Adam Altemus
http://www.mobilvox.com
|
