After experimenting, my config.json looks like this:

{
  "name"    : "bfly",

  "include" :
  [
    {
      "path" : "../../qooxdoo-svn/tool/data/config/application.json"
    }
  ],

  "let" :
  {
    "APPLICATION"  : "bfly",
    "QOOXDOO_PATH" : "../../qooxdoo-svn/framework",
    "QOOXDOO_URI"  : "/res/bfly/qx",
    "QXTHEME"      : "qx.theme.Modern",
    "LOCALES"      : [ "en" ],
    "ROOT"         : ".",
    "BUILD_PATH"   : "${ROOT}/build",
    "CACHE"        : "cache"
  },

  "jobs":
  {
    "common" :
    {
      "library" :
      [
        {
          "manifest" : "${QOOXDOO_PATH}/Manifest.json",
          "uri"      : "${QOOXDOO_URI}"
        },

        {
          "manifest" : "${ROOT}/Manifest.json",
          "uri"      : ".."
        }
      ],

      "include" :
      [
        "qx.*",
        "${QXTHEME}"
      ],

      "exclude" :
      [
        "qx.legacy.*"
      ],

      "cache" :
      {
        "compile" :  "${CACHE}"
      },

      "settings" :
      {
        "qx.version"     : "${QXVERSION}",
        "qx.theme"       : "${QXTHEME}",
        "qx.application" : "${APPLICATION}.Application"
      }
    },

    "compile-qx-debug" :
    {
      "extend" : ["common"],

      "compile-dist" :
      {
        "file" : "${BUILD_PATH}/script/qx-debug.js",
        "root" : "."
      }
    },

    "compile-qx-build" :
    {
      "extend" : ["common"],

      "variants" :
      {
        "qx.debug" : ["off"],
        "qx.aspects" : ["off"]
      },

      "compile-dist" :
      {
        "file" : "${BUILD_PATH}/script/qx-build.js",
        "root" : ".",
        "optimize" : [ "variables", "basecalls", "privates", "strings" ]
      }
    },

    "compile-qx-resources" :
    {
      "extend" : ["common"],

      "copy-resources" :
      {
        "target"          : "${BUILD_PATH}",
        "resource-filter" : true
      }
    },

    "compile-qx" :
    {
      "run" :
      [
        "compile-qx-resources",
        "compile-qx-debug",
        "compile-qx-build"
      ]
    }
  }
}

then I can run generate.py compile-qx and I have qooxdoo distribution
compiled in two files. I have introduces also debug and build variants
so I'm able to optionaly switch to debug (with debug=true URI).

Only one note to say: It was easy and straighforward !

- Petr

2008/8/26 Petr Kobalíček <[EMAIL PROTECTED]>:
> Hi,
>
> is there any option to build complete qooxdoo 0.8 distribution ?
>
> I'm developing application that uses modular architecture and it's
> designed that administration interface contains only installed
> modules. These modules are added to html as <script></script> blocks,
> so I have control about this.
>
> I qooxdoo 0.7.3 I was setup the makefile to create complete qooxdoo
> distribution, but I don't know if in 0.8 is something like:
>
>    APPLICATION_COMPLETE_BUILD = true
>
> Anyway, I must say that setup application in qx 0.8 is a lot better
> than 0.7.3 -- GOOD WORK:)
>
> BTW:
> I have qooxdoo 0.8 (trunk) in this directory:
>  C:\My\_\javascript\qx\qooxdoo-svn\
> Application in this:
>  C:\My\_\javascript\qx\build-svn\dist\
> And QOOXDOO_PATH in generate.py is:
>  QOOXDOO_PATH = '../../../../../../my/_/javascript/qx/qooxdoo-svn'
> Shouldn't it be only:
>  QOOXDOO_PATH = '../../qooxdoo-svn' ?
>
> Cheers
> - Petr
>
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
qooxdoo-devel mailing list
qooxdoo-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel

Reply via email to