Yes, exactly:
{
"name": "...",
"jobs": {
"common" : {
"settings": {
"your.setting": "abc"
}
}
}
}
qx.core.Setting.get("your.setting");
You'll have to generate your source again (generate.py source).
On Thu, Sep 30, 2010 at 3:26 PM, b a wrote:
"app_name": {
"jobs": {
"common": {
"settings" : {
}
}
}
}
On 9/30/10, b a wrote:
> so how does my config.json need to look ?
>
> On 9/30/10, Guilherme Aiolfi wrote:
>> Are you sure that you are calling "this.base(arguments); " in your main
>> metho
so how does my config.json need to look ?
On 9/30/10, Guilherme Aiolfi wrote:
> Are you sure that you are calling "this.base(arguments); " in your main
> method?
>
> And your keys should be inside the "jobs > common > settings" entry in your
> config.json.
>
> On Thu, Sep 30, 2010 at 2:14 PM, b a
Are you sure that you are calling "this.base(arguments); " in your main
method?
And your keys should be inside the "jobs > common > settings" entry in your
config.json.
On Thu, Sep 30, 2010 at 2:14 PM, b a wrote:
> so is there any way for me to get at runtime things from config.json ?
>
> On 9/
so is there any way for me to get at runtime things from config.json ?
On 9/30/10, b a wrote:
> actually now I put some alerts and realized that even in the code sections
> that
> I thought I was getting config values from qx.core.Setting , I wasn't.
> I am getting undefined on
> qx.core.Setting.
actually now I put some alerts and realized that even in the code sections that
I thought I was getting config values from qx.core.Setting , I wasn't.
I am getting undefined on
qx.core.Setting.get("some_key_that_exists_in_config.json");
and getting undefined on qx.core.Setting.some_key_that_exists_
Hi,
I have a native Qooxdoo app which I wrote and I noticed that in main {}
I don't have access to qx.core.Setting(which from what I've seen
exposes the contents of config.json).
I need to have access to qx.core.Setting, so I want to move part of my
code from main {} to some listener on some even
