My qooxdoo application is a Chrome browser plugin. As such I have two
applications living in the same source tree. This is necessary as the
Chrome applications can consist of up to 3 separate HTML/JavaScript
applications dwelling in the same directory (one is injected directly
into browser tabs, one is a stand-alone frame the user can summon, and
one dwells in the background). I am utilizing two of these - the
foreground GUI application and the background application. The main
foreground UI application is the main application I created under 1.3
with the standard GUI framework provided by qx. The background is a
second application whose entry point is in the file Background.js
which sits in parallel with Application.js.
The background application is generated by a call to ./generate.py
build-backend and has an entry in the config.json that looks like
this:
// An extra job that we have to build the Chrome background script
"build-background" :
{
"extend" : ["build"],
"=include" :
[
"${QXTHEME}",
"${APPLICATION}.Background"
],
"settings" : {
"qx.application" : "${APPLICATION}.Background"
},
"library" : [{
"manifest" : "${CHROMEPLUGIN}"
}],
"compile-options" :
{
"paths" : { "file" : "source/script/${APPLICATION}_background.js" }
}
},
Under 1.3 this worked fine, copying the contents of
"source/script/${APPLICATION}_background.js" into the build/ folder at
build time. However, under 1.5 this file is now regenerated every time
I execute generate.py build-backend. However, instead of executing
"${APPLICATION}.Background" like it used to, it is generating the file
which executed "${APPLICATION}.Application". This is, of course, the
default behavior but it is not what I want.
"${APPLICATION}.Application" is the target of my ${APPLICATION}.js
file and runs in the foreground. ${APPLICATION}.Background is supposed
to be executing in the background as a type of service dispatcher.
I realize that the non-regeneration of ${APPLICATION}_background.js
was probably a bug in 1.3 which has since been fixed, but this fix
does not properly honor the value of settings.qx.application (or
perhaps that key value has changed since 1.3?). Does anyone have any
advice on what is going wrong here?
--Greg
------------------------------------------------------------------------------
BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA
The must-attend event for mobile developers. Connect with experts.
Get tools for creating Super Apps. See the latest technologies.
Sessions, hands-on labs, demos & much more. Register early & save!
http://p.sf.net/sfu/rim-blackberry-1
_______________________________________________
qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
