Hi Thomas,
The docs say that the key is "script" but you mentioned
"compile-options/uris/source" in an email in february so I thought I'd test
for any possible typos before asking but I had missed that the script key
only applied to build. I guess I was tired and rushing when I read it,
apologies
I'm aware that the Uri for libraries can be set (I use it in every app) and
that's a really useful feature because our URIs have little relation to
where on disk a particular library is stored; the same is true for our apps,
that the location on disk does not necessarily relate to the URI in the
address bar this is because the app is created on the fly by content
management. Until Qx1.5 there was only one file that was served from the
source/script and if you don't use the generated index.html (we don't), that
can be easily overridden but now there are other files from source/script
this is a problem for us during development.
I've solved my problem by providing a decode-uris-plug script but I'm
curious why does source job not support custom uris for the application
when the build job does? An application is very similar in concept (and
presumably implementation in the generator) to a library and I don't
understand the logic that says that the resource and script URIs will
_always_ be relative to the web page that invoked the app when in
development but could be anywhere when deployed. Isn't it normally the
other way around, ie that for deployment you package everything up into as
small and discrete package as possible?
John
From: thron7 <[email protected]>
Reply-To: qooxdoo Development <[email protected]>
Date: Fri, 22 Jul 2011 18:41:49 +0200
To: qooxdoo Development <[email protected]>
Subject: Re: [qooxdoo-devel] Problem setting sourceUri for default
application
On 07/22/2011 05:22 PM, John Spackman wrote:
>
> Hi,
>
>
>
>
> I need to change the sourceUri for the current application but can't get it to
> work; in my app's config.json I've tried setting:
>
>
>
>
>
> jobs/source/compile-options/uris/script
>
>
>
> jobs/source/compile-options/uris/source
>
>
>
> jobs/source/compile-options/uris/sourceUri
>
>
>
>
>
> But it doesn't work what am I doing wrong?
>
John,
first, don't guess, but see the config ref in the manual :).
This would have told you that there are just 'script' and 'resource'
sub-keys, but neither 'source' nor 'sourceUri'. Also, it would have told you
that these keys are only relevant for the *build* version of your app.
Why? In the build version, everything is collected under build/script and
build/resource, but these two paths might look different if you move the
index.html to another place. You use these two keys to adjust that.
The source version is totally different, and those keys are ignored there.
In the source version, you have *multiple* script and resource URIs - one
for each involved library -, and they are calculated for each library
individually, as they are found on the file system.
If you must tweak the URIs in the source version, you need to set them on a
per-library base. This can be achieved using the "library/<lib>/uri" key of
each library (consequently, the build version ignores *those*). But mind
that you only specify the URI to the *root* directory of the library;
beneath that, 'script' and 'resource' entries from the lib's Manifest.json
apply.
See [1] for an in-depth treatment of URIs (there is a little document bug
in the example involving blank.gif that needn't bother you).
HTH,
T.
[1]
http://manual.qooxdoo.org/1.5.x/pages/tool/generator_config_articles.html#ur
i-handling
----------------------------------------------------------------------------
-- 10 Tips for Better Web Security Learn 10 ways to better secure your
business today. Topics covered include: Web security, SSL, hacker attacks &
Denial of Service (DoS), private keys, security Microsoft Exchange, secure
Instant Messaging, and much more.
http://www.accelacomm.com/jaw/sfnl/114/51426210/____________________________
___________________ qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
------------------------------------------------------------------------------
Magic Quadrant for Content-Aware Data Loss Prevention
Research study explores the data loss prevention market. Includes in-depth
analysis on the changes within the DLP market, and the criteria used to
evaluate the strengths and weaknesses of these DLP solutions.
http://www.accelacomm.com/jaw/sfnl/114/51385063/
_______________________________________________
qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
