On Wed, Dec 29, 2010 at 6:09 PM, thron7 <thomas.herchenroe...@1und1.de> wrote:
>> This seems easy enough and like it will be perfect. An additional
>> question about it, though: if I use any Qooxdoo classes in
>> background.html, will those be picked up, or will the "copy-files"
>> merely copy the file blindly without processing it?
>
> Blindly.
>
>> I plan to use a
>> number of Qooxdoo classes and use its OO features to structure my app,
>> which will be in the two distinct sections: index.html and
>> background.html.
>
> Mh, there is no general problem in providing different .html files. But as
> you surely know, .html files in qooxdoo just load a main .js file and
> that's it; they usually don't contain actual application code, and I
> wouldn't recommend going this route.
Certainly not, I was looking for a solution like the one you provide
below. I have, indeed, the two skeleton .html file which are nearly
identical and one loads up script/${APPLICATION}.js and the other
loads script/${APPLICATION}_background.js.
${APPLICATION}_background.js is a straight copy of ${APPLICATION}.js
with the value on line 8 of ${APPLICATION}.Application replaced with
${APPLICATION}.Background which seems to be the only such reference to
my application's specific needs.
>
> Rather, you should try to provide two different .js scripts that are
> loaded by the two .html files. You can achieve this by adding a new build
> job to your config.json, specifying a new "include" directive. Something
> like
>
> "background-build" : {
> "extend" : [ "build" ],
> "=include": [
> "${QXTHEME}",
> "${APPLICATION}.Background" // or whatever alternate class name
> ],
> "compile-options" : {
> "paths" : { "file" : "script/background.js" }
> }
> }
I have nearly exactly what you say I ought to have save for a few
minor changes. Here it is:
"build-background" :
{
"extend" : ["build"],
"=include" :
[
"${QXTHEME}",
"${APPLICATION}.Background"
],
"compile-options" :
{
"paths" : { "file" : "script/${APPLICATION}_background.js" }
}
}
It seems to build a source version of the background however, as the
console for background.html is complaining about not finding
Bootstrap.js in my /opt/qooxdoo directory (same problem I had when
trying to load the front-end from a "./generate.py source").
I feel like I've missed a small setting or step somewhere. The
frontend UI portion works great with a ./generate.py build, so I am
very close to having this working.
--Greg
>
> and then invoke 'generate.py background-build' to create
> script/background.js, and <script>-include this in background.html. This,
> way you essentially maintain two individual apps in one library.
>
> T.
>
>
>
>
> ------------------------------------------------------------------------------
> Learn how Oracle Real Application Clusters (RAC) One Node allows customers
> to consolidate database storage, standardize their database environment, and,
> should the need arise, upgrade to a full multi-node Oracle RAC database
> without downtime or disruption
> http://p.sf.net/sfu/oracle-sfdevnl
> _______________________________________________
> qooxdoo-devel mailing list
> qooxdoo-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
>
------------------------------------------------------------------------------
Learn how Oracle Real Application Clusters (RAC) One Node allows customers
to consolidate database storage, standardize their database environment, and,
should the need arise, upgrade to a full multi-node Oracle RAC database
without downtime or disruption
http://p.sf.net/sfu/oracle-sfdevnl
_______________________________________________
qooxdoo-devel mailing list
qooxdoo-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
