For source builds instead of patching the loader, it is also possible to
inject a script into the loader; extend your "source-script" job like this:
"source-script" : {
"compile-options" : {
"code": {
"decode-uris-plug": "decode-uris-plug.js"
}
}
},
And create decode-uris-plug.js in the same folder as config.json; the code
in it will have a variable "euri" set to the URI to change; for example:
euri = euri.replace(/^script/, "/path/to/my/source/script");
I'm only using this on my "source" job but I guess it will work for "build"
jobs too?
John
From: thron7 <thomas.herchenroe...@1und1.de>
Reply-To: qooxdoo Development <qooxdoo-devel@lists.sourceforge.net>
Date: Monday, 9 July 2012 15:06
To: qooxdoo Development <qooxdoo-devel@lists.sourceforge.net>
Subject: Re: [qooxdoo-devel] QX 2.0 source build: absolute __out__ uri ?
On 07/09/2012 03:40 PM, david leray wrote:
> On Mon, Jul 9, 2012 at 3:31 PM, thron7 wrote:
>
>
>>
>> As long as the loading HTML file is on the same server as your app and the
>> qooxdoo libraries, there is a much simpler approach that was designed for
>> such situations, and also alleviates you from adding 'libraries/library/uri'
>> keys for each library you use. Set the application root for your application
>> to the divergent path of the HTML file, relative to the config.json, via
>> source-script/compile-options/paths/app-root. All relative URIs in the loader
>> will then be calculated relative to this HTML file.
>>
>> T.
>>
>>
>>
>>
>>
>>
>
>
>
>
>
>
>
> Yes, I understood that, but my problem is that the loading HTML file is not
> and can not be on the same server as my app (because it is controlled by a
> client not by us). I am willing to use the not-so-simple approach, if you
> could only point me in the right direction?
>
>
Then, I'm afraid, you will have to patch the sourceUri entry of the __out__
lib in the loader, under "var libinfo", after it has been generated. But be
so kind and open an enhancement bug for this in our bugzilla, describing
your situation.
T.
>
>
>
>
>
>
>
>
>
>
>
>
>
>>
>>
>>
>>
>> On 07/06/2012 02:34 PM, david leray wrote:
>>
>>
>>>
>>>
>>> Hi everyone,
>>> I am still migrating our qooxdoo app to 2.0, and it seems now when I build
>>> in source mode, there is not one myapp.js file created but two: myapp.js
>>> and myapp-randommd5.js. My problem is that myapp.js sources
>>> myapp-randommd5.js using a relative link. Since we host our source
>>> application on a web server and at a different uri than the HTML file which
>>> loads the application. "myapp.js" is then correctly loaded, but
>>> "myapp-randommd5.js" is not.
>>> We solved the problem for other resources by adding the
>>> "libraries/library/uri" key in the configuration, but I looked into the
>>> build configuration, and it seems the uri for "myapp-randommd5.js" is taken
>>> from a dynamically generated __out__ library. Is there any way to configure
>>> the uri for this __out__ library? If not, what is the correct way to solve
>>> this problem?
>>>
>>>
>>>
>>> --
>>> David Leray
>>>
>>>
>>>
>>>
>>>
>>>
>>> ----------------------------------------------------------------------------
>>> --
>>> Live Security Virtual Conference
>>> Exclusive live event will cover all the ways today's security and
>>> threat landscape has changed and how IT managers can respond. Discussions
>>> will include endpoint security, mobile security and the latest in malware
>>> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
>>>
>>>
>>>
>>> _______________________________________________
>>> qooxdoo-devel mailing list
>>> qooxdoo-devel@lists.sourceforge.nethttps://lists.sourceforge.net/lists/listi
>>> nfo/qooxdoo-devel
>>>
>>
>>
>>
----------------------------------------------------------------------------->>
-
>> Live Security Virtual Conference
>> Exclusive live event will cover all the ways today's security and
>> threat landscape has changed and how IT managers can respond. Discussions
>> will include endpoint security, mobile security and the latest in malware
>> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
>> _______________________________________________
>> qooxdoo-devel mailing list
>> qooxdoo-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
>>
>>
>
>
>
>
>
>
> --
> David Leray
>
>
>
>
> ------------------------------------------------------------------------------
> Live Security Virtual Conference
> Exclusive live event will cover all the ways today's security and
> threat landscape has changed and how IT managers can respond. Discussions
> will include endpoint security, mobile security and the latest in malware
> threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
>
>
>
> _______________________________________________
> qooxdoo-devel mailing list
> qooxdoo-devel@lists.sourceforge.nethttps://lists.sourceforge.net/lists/listinf
> o/qooxdoo-devel
>
----------------------------------------------------------------------------
-- Live Security Virtual Conference Exclusive live event will cover all the
ways today's security and threat landscape has changed and how IT managers
can respond. Discussions will include endpoint security, mobile security and
the latest in malware threats.
http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/___________________
____________________________ qooxdoo-devel mailing list
qooxdoo-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and
threat landscape has changed and how IT managers can respond. Discussions
will include endpoint security, mobile security and the latest in malware
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
qooxdoo-devel mailing list
qooxdoo-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
