On Mon, Jun 20, 2011 at 09:26, Derrell Lipman <
derrell.lip...@unwireduniverse.com> wrote:

> On Mon, Jun 20, 2011 at 06:44, thron7 <thomas.herchenroe...@1und1.de>wrote:
>
>>
>> What do you want to achieve anyway?
>>
>
> I'm writing an interface for control of a small robot. This is used for
> educational purposes, and I want to make it possible for the interface to be
> modified by end users. Therefore, what I really want is qx-oo.js, rpcjs.js,
> and the individual source files in my application namespace. It's the
> application namespace files I expect people to fiddle with, whereas qx-oo.js
> and rpcjs.js will just be "libraries" that will remain untouched.
>
> If I could create a qxrpc.js that contains everything from qx-oo.js and a
> concatenation of everything in the rpcjs (contrib) namespace, I'd be in
> fabulous shape. A single "library" (include file) with everything except the
> code from the application namespace would be perfect. I'll look at the
> framework's config.json to see if I can figure out how to create a job
> similar to qx-oo that includes a contrib as well, but any hints would
> certainly be useful.
>

For anyone else looking to do something similar, this seems to have worked:

I added these two lines to the "export" array:
    "qxrpc-build",
    "qxrpc-noopt"

I then added these blocks to the "jobs" section:
    "qxrpc" :
    {
      "library" :
      [
        {
          "manifest" : "${QOOXDOO_PATH}/framework/Manifest.json",
          "uri" : ".."
        },
        {
          "manifest" : "${CONTRIB_PATH}/RpcJs/trunk/Manifest.json"
        }
      ],

      "extend" : [ "cache" ],

      "include" :
      [
        "qx.Class",
        "qx.Mixin",
        "qx.Interface",
        "rpcjs.*"
      ],

      "exclude" :
      [
        "qx.event.GlobalError"
      ],

      "environment" :
      {
        "qx.debug" : false,
        "qx.aspects" : false,
        "qx.globalErrorHandling" : false
      },

      "compile-options" :
      {
        "paths" :
        {
          "loader-template" :
"${QOOXDOO_PATH}/tool/data/generator/oo.loader.tmpl.js"
        },
        "uris" :
        {
          "script"   : ".",
          "resource" : "."
        }
      }
    },


    "qxrpc-build" :
    {
      "desc" : "a basic qooxdoo OO library",
      "extend" : [ "qxrpc" ],

      "compile-options" :
      {
        "paths" :
        {
          "file" : "build/script/qxrpc.js"
        },
        "code" :
        {
          "format"   : true,
          "optimize" : [ "variables", "basecalls", "privates", "strings",
"variants" ]
        }
      },
      "compile" : { "type" : "build" }
    },


    "qxrpc-noopt" :
    {
      "desc" : "a basic qooxdoo OO library (non-optimized)",
      "extend" : [ "qxrpc" ],

      "compile-options" :
      {
        "paths" :
        {
          "file" : "build/script/qxrpc-noopt.js"
        },
        "code" :
        {
          "format"   : true,
          "optimize" : [ ]
        }
      },
      "compile" : { "type" : "build" }
    },

Maybe that'll save someone some time.

Cheers,

Derrell
------------------------------------------------------------------------------
EditLive Enterprise is the world's most technically advanced content
authoring tool. Experience the power of Track Changes, Inline Image
Editing and ensure content is compliant with Accessibility Checking.
http://p.sf.net/sfu/ephox-dev2dev
_______________________________________________
qooxdoo-devel mailing list
qooxdoo-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel

Reply via email to