Generator Script Optimizations

When creating the JavaScript output for an application, the generator supports several optimizations. These optimizations can be enabled in the generator configuration using the code/optimize key, a subkey of compile-options. The best way to set this key is by setting the OPTIMIZE macro in your config's global let section. What the individual optimizations do is described here in detail.


Calls to this.base(), which invoke the corresponding superclass method, are inlined, i.e. the superclass method call is inserted in place of the this.base() call.


The comments optimization is automatically included in any of the other optimizations, so really only makes a difference when given as the only optimization key for the given build. In that case, comments are stripped from the source code, and the resulting text is passed to the script output, also retaining (most of the) white space of the source version. What you get is a near-source code version in the running application that allows you to focus on the code, and is lighter in terms of transfer size.


This is less an optimization in space or time, but rather a way to enforce privates. Private members of a class (those beginning with "__") are replaced with generated names, and are substituted throughout the class. If some other class is accessing those privates, these references are not updated and will eventually fail when the access happens. This will lead to a runtime error.

There is a caveat with privates optimization: Apart from identifier references to the private, also string references in the class code will be replaced. That means if a string literal contains of the exact sequence of characters as the private key, the contents of the string will also be replace. This only affects complete matches, not partly matches in a larger string.

__foo : function () {
  this.debug("__foo called");

If __foo is replaced by, say, __a by the private optimization, the code will look like this after the optimization:

__a : function () {
  this.debug("__foo called");

The reason for this behaviour is that members, including private members, of a class are sometimes referenced by their name string, particularly in definitions of properties, and as arguments to dispose methods, as used in the destruct member of a class. Here is a longer code fragment to show where name references to members can be used:

properties : {
  myprop : {
    apply : "__myapply",
    validate : "__myvalidate"

members : {
  __foo : ...,
  __myapply : function () {...},
  __myvalidate : function () {...}
destruct : function () {

For more details where string references can occur, see e.g. the class and property quick refs.


With the string optimization, strings are extracted from the class definition and put into lexical variables. The occurrences of the strings in the class definition is then replaced by the variable name. This mainly benefits IE6 and repetitive references to the same string literal.



The statics optimization tries to remove unused ("dead") code, namely the code of methods of static classes. The reason for this is that static methods are often invoked with their complete class name, e.g. as, which is easy to detect. Often, an application would only call a single method of a static class, so the other methods of this class are unused, and can be removed.

As removing a method reduces the dependencies this method has to other classes, those dependencies are checked themselves. If there are no other dependents, the dependent class feature can be removed as well. This pattern is applied recursively until no more code can be removed. Classes which are no longer used at all are removed entirely. (Technically, the generator uses reference counting to track the "usage count" of a class feature, and eventually constructs a reachability graph to remove entire trees of classes and their dependencies if they are not reachable by the main application classes).

In the context of a dynamic language this is a very aggressive optimization, and the problem is the occurrence of false positives. I.e. methods are judged as "not used" when in fact they are. This hinges on the highly dynamic nature of JavaScript where methods can be aliased, passed around as parameters to other functions, stored as map values, and so forth, all of which is hard to detect at compile time.

The cure is to add @require hints to force the inclusion of those methods that you know are used, although the generator cannot detect this. E.g. in a class that has an undetected runtime dependency on you should add an appropriate hint in the this class:



The statics optimization is highly experimental, and is not for use in normal application development. If you use it, you should expect manual work and multiple iterations to get your classes working again. You best provide a good test coverage in advance so you can convince yourself that all classes are indeed working when this optimization is enabled.


Local variable names are made short. Scoped variables (those declared with a var statement in a function) are replaced by generated names that are much shorter (1-2 characters on average). Depending on the original code, this can result in significant space savings.


With giving the variants optimization key, code will be removed that is not relevant for the current build. The decision about relevance is based on the settings given in the job configuration's environment key. Often, these settings will be queried in class code to select a certain code branch. If the value of the setting is known at compile time, the correct branch can be selected right away, and all other branches be removed. This allows to omit code that wouldn't be executed at run time anyway ("dead code removal").

The way environment settings are queried in class code is through certain APIs of the qx.core.Environment class. These API calls are searched for, and depending on context safe optimizations are applied. Here are the different calls and how they are treated.


qx.core.Environment.get() references the environment key as its first parameter. If this parameter is a literal, i.e. a string, representing a known environment key, the call can be replaced by the environment key's value. This is applied in all situations, and saves the method call at run time:

var a = qx.core.Environment.get("");

If the value of the environment key is "bar", the expression is thus reduced to a simple assignment, where a is assigned the value "bar":

var a = "bar";

If the call happens inside the condition of an if statement, and the call is the only expression, it is evaluated and the whole if statement is replaced by either its then or its else branch, depending on the truth value of the environment key.

if (qx.core.Environment.get("")) {
  // some code if evaluates to true
} else {
  // some code if evalutates to false

The same holds true if the call to qx.core.Environment.get() is not the only expression in the if condition, but is part of a simple compare where

  • the condition operator is one of ==, ===, !=, !===
  • the other operand is a literal value (like "foo", 3, or true)
if (qx.core.Environment.get("") == "bar") {
} else {

Again, the branch of the if statement is chosen according to the outcome of the comparison. If the condition evaluates to false and there is no else branch, the if statement is removed.


With you can choose an expression from a set of expressions according to the current value of an environment key. The first parameter to the call is again the environment key, the second is a map that maps possible values to arbitrary expressions.

Again, if the key is a literal string and can be found in the environment settings known to the generator, the whole expression is replaced by the corresponding expression from the map parameter.

var a ="", {
  "bar" : function (x) { return x+3;},
  "baz" : 24

Depending on the value of, the variable a will be assigned a function, or the number literal 24.

You can include the special key "default" in the map parameter to .select(). Its expression will be chosen if the value of the environment key does not match any of the other concrete map keys. If the generator comes across a .select() call where the environment value does not match any of the map keys and there is no "default" key, it will raise an exception.


Similar to .select(), qx.core.Environment.filter() takes a map. But this time the map keys are different environment keys (not possible values of a single key).

include : qx.core.Environment.filter({
  "module.databinding" :,
  "module.logger"      : qx.core.MLogging,
  ""      : qx.core.MEvent,
  ""    : qx.core.MProperty,
  "qx.debug"           : qx.core.MAssert

Each key is checked, and if its value resolves to a true value, the corresponding map value is added to an array. At the end, this array is returned. That means, .filter() turns a set of environment keys into a list of corresponding expressions. For the generator, this means that if an environment value is known to be false at compile time, its entry can be safely removed from the filter map. The benefit of this is that code dependencies that are in the map values are removed, again saving dependencies that would never be used at runtime.


Mind, though, that variants optimization somewhat conflicts with the qx.allowUrlSettings environment key. See there for more information.


Whitespace (spaces, tabs, newlines) is removed. Semi-colons are inserted where necessary.