> OK. Answering to myself. I could just use {my.variant} in config.json.
>
>
I'm not sure - is it working on your side?! I'd be surprised. This
"{variantOrSettingsName}" replacement only works for compile output file
names. I don't think it will be applied to a string value of the "shell"
key.
Moreover, there is no such thing as the "current variant" for any job
other than a compile job. So even more doubt about the shell value being
expanded correctly.
You can use standard config macros in the shell command, like "shell" :
"echo ${myval}", which should be expanded before running the command.
But this is fixed at edit-time of the config file(s), and cannot reflect
a dynamic variants value.
T.
> Cheers,
> Cajus
>
> PS: Is qooxdoo.org down in the moment?
>
> Cajus Pollmeier schrieb:
>
>> Btw.: is it possible to pass the current variants to a shell script in the
>> generator? I.e. inside a build "shell" :
>> "/usr/bin/do-what-ever-is-needed.sh", so that do-whatever-is-needed.sh is
>> able to react on the variants?
>>
>> Greetings,
>> Cajus
>>
>> thron7 schrieb:
>>
>>>> If I modify the config.json to build custom-mshtml.js, custom-webkit.js,
>>>> etc.: what is the proposed way to get the correct
>>>> build/scripts/custom-whatever.js script loaded in index.html?
>>>>
>>>>
>>> I don't know of a better way than rolling your own, e.g. by taking
>>> advantage of the browser identification that comes with the request to
>>> your server and the server returning the right variant, or by adding JS
>>> code to your index.html that does that, or by creating a small loader
>>> script that is loaded by the index.html and that then loads the correct
>>> application script.
>>>
>>> I've added a bug to have such logic provided by qooxdoo
>>> (http://bugzilla.qooxdoo.org/show_bug.cgi?id=2290).
>>>
>>> Anybody else?
>>>
>>> T.
>>>
>>>
>>>>
>>>>
>>> ------------------------------------------------------------------------------
>>> Stay on top of everything new and different, both inside and
>>> around Java (TM) technology - register by April 22, and save
>>> $200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco.
>>> 300 plus technical and hands-on sessions. Register today.
>>> Use priority code J9JMT32. http://p.sf.net/sfu/p
>>> _______________________________________________
>>> qooxdoo-devel mailing list
>>> [email protected]
>>> https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
>>>
>> ------------------------------------------------------------------------------
>> Stay on top of everything new and different, both inside and
>> around Java (TM) technology - register by April 22, and save
>> $200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco.
>> 300 plus technical and hands-on sessions. Register today.
>> Use priority code J9JMT32. http://p.sf.net/sfu/p
>> _______________________________________________
>> qooxdoo-devel mailing list
>> [email protected]
>> https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
>>
>
>
> ------------------------------------------------------------------------------
> Stay on top of everything new and different, both inside and
> around Java (TM) technology - register by April 22, and save
> $200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco.
> 300 plus technical and hands-on sessions. Register today.
> Use priority code J9JMT32. http://p.sf.net/sfu/p
> _______________________________________________
> qooxdoo-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
>
>
>
------------------------------------------------------------------------------
Stay on top of everything new and different, both inside and
around Java (TM) technology - register by April 22, and save
$200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco.
300 plus technical and hands-on sessions. Register today.
Use priority code J9JMT32. http://p.sf.net/sfu/p
_______________________________________________
qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
