Besides foreign files we have included in the project, we also want to list the tools we use to either produce or consume genuine files of our source tree (beyond basic text editors ;-), so it is easy to oversee all the project's dependencies.
These are components that are integrated into the framework class code. I.e. if you are using classes from the framework to create your custom application, chances are that these components will make it into the deploy version of your application.
Static resource files, like images, CSS, etc. Static resources are frequently included in custom application, so it is very likely some of them will make it into your own custom application.
|Tango Icons||CC BY-SA 2.5|
These are the Python modules we use that are not self-written nor part of a vanilla Python 2.6 SDK. While they are shipped with our SDK they are only used while the tool chain runs, and never become part of the resulting custom application.
|argparse||Python License 2|
|elementtree||old-style Python (HPND)|
These are the Node.js modules we use that are not self-written nor part of a vanilla Node.js v0.10+. While they are shipped with our SDK they are only used while the tool chain runs, and never become part of the resulting custom application.
Components or tools that are not included with the SDK¶
These tools we use on our development machines, e.g. to prepare the qooxdoo SDK, run automated tests, create reports, and the like. They are not required to use any of qooxdoo's deliverables, but can be interesting for users that pursue specific interests.
|Make||GPL 3.0 or later|
|Mozilla Rhino||MPL 1.1/GPL 2.0, Unnamed License|
|Selenium||Apache License 2.0|
|TeX Live||mixed free licenses|