Download Offline Manual - Docs

qooxdoo Documentation, Release 4.1.1
There are two variants of the source job available which you might find interesting. One is called source-all and
will include all available classes of all involved libraries, the other is source-hybrid which improves loading speed by
concatenating some of the class code. See their respective entries.
source-all
Create a source version of the application, with all classes.
source-all will include all known classes, be they part of your application, the qooxdoo framework, or any other qooxdoo library or contribution you might be using. All those classes are included in the build, whether they are currently
required or not. This allows you develop your code more freely as you don’t have to re-generate the application when
introducing new dependencies to existing classes. All classes are already there. You only have to re-run this job when
you add an entirely new class that you want to use.
The downside of this job is that due to the number of classes your application is larger and loads slower in the browser,
so it is a trade-off between development speed and loading speed.
source-hybrid
Create a source version of the application, concatenating some of the class code.
The source-hybrid job concatenates the contents of the classes that make up the application into a few files, only
leaving your own application classes separate. Having the other class files (framework, libraries, contribs) chunked
together you get the loading speed of nearly the build version, while at the same time retaining the accessibility of your
own application files for debugging. This makes this job ideal for fast and focused development of the applicationspecific classes.
Only the classes that are actually needed for the application are included, so you have to re-run this job when you
introduce new dependencies.
To review the three different source jobs, if you are just getting started with qooxdoo development, use the source-all
version, which is the most convenient if you are not too impatient. If you are concerned about loading speed during
development, but don’t mind hitting the up and return keys in your shell window once in a while, go with the default
source-hybrid job. If your emphasis on the other hand is on inspection, and you want to see exactly which class files
get loaded into your application and which code they provide, the source version will be your choice.
source-server
(experimental)
Run a mini web server that serves the source version of an application. The web server will export as document root
a root path common to all libraries used by the source version. This overcomes e.g. restrictions by modern browsers
that do not allow XHR requests over the file:// protocol by default.
By default the server will randomly pick a free port on the local machine to run at. You can assign it a
fixed port by setting the SOURCE_SERVER_PORT macro, e.g. like generate.py source-server -m
SOURCE_SERVER_PORT:44161.
source-server-reload
(experimental)
Same as source-server, but adds an automatic reload feature. The web server watches the loader file of the exported
source version (usually source/script/<application>.js), and triggers an automatic reload of the application in the
browser if this changes. You usually want to use this job together with the watch job (running separately) which
11.3. Tooling
521