This is the typical directory structure of a qooxdoo project. The bold names mark folders and files that are either already included (e.g. in the qooxdoo skeletons) or have been added by the user. All other folders and files are generated through the make shell commands.

The generated build/ folder is self-contained and includes everything that is needed for a working custom application. This folder could be moved to any other file location, be synced to any external hosting solution via FTP, be deployed into a Tomcat, and so on. Whatever your requirements are in your existing production environment, qooxdoo can easily be integrated. To change the location of the build/ folder, simply adjust the Makefile.

• build/ (generated by make)
  • script/
    • custom.js (optimized and compressed application code)
  • index.html (production version of application start page)
• source/
  • class/
    • custom/ (custom application namespace; this needs to be unique if used together with other libraries, contributions, etc.)
      • Application.js (custom application class; name spaces should be rather flat; do not try to replicate the often deep namespaces in the qooxdoo framework)
      • theme/
        • classic/
          • Appearance.js (custom theme class; if you need enhancements to the default themes, they should be placed in the appropriate subdirectories, like currently classic or ext)
        • ext/
  • resource/ (custom resource files, like CSS files or images needed by the application classes)
  • script/ (generated by make source)
    • custom.js (includer of original source script files)
  • index.html (development version of application start page)
• Makefile
• Manifest.js