Team,
Another thought that came to my mind is wishing I could see a graphical
representation of the config sections (in both the application and
framework) that a typical "source" or "build" job ends up examining and
evaluating. It all struck me as pretty confusing when I read through
that portio
Hi Thomas,
as you show, the information is all there and very detailed. I am not saying
that you don't provide excellent documentation! We talked about that before
- I tried the "search, don't sort" approach and came across the config key,
which then I used without a job context because this woul
panyasan wrote:
Ok, this worked, thanks. As usual, there is tons of useful information on the
website, but it is sometimes hard to figure out something basic as this
Ok, in that particular case, where did you get lost? The generator
configuration overview clearly lines out that config keys
Ok, this worked, thanks. As usual, there is tons of useful information on the
website, but it is sometimes hard to figure out something basic as this
because the generator configuration is a very complex matter that would
deserve a whole series of tutorials. As I said, the Book of Qooxdoo still
ha
panyasan wrote:
> Hello,
>
> I have a file in the script folder that I need to be copied into the built
> package. I have tried this in my config.json
>
> ...
>
> "copy-files" :
> {
> "files" : [ "script/rpcconsole.testData.js" ]
> },
>
> ...
>
> However, the file is not copied in
Hello,
I have a file in the script folder that I need to be copied into the built
package. I have tried this in my config.json
...
"copy-files" :
{
"files" : [ "script/rpcconsole.testData.js" ]
},
...
However, the file is not copied into build/script. What am I doing wrong?
T
dperez schrieb:
> Hi,
>
> When activating the --copy-resources switch in a custom build, all the
> resources are copied, not only the needed ones.
> For example, qooxdoo only uses a few icons from icon/16/*, but also
> icon/22/*, icon/128/* and so on are copied.
> I find more practical to determine
Hi,
When activating the --copy-resources switch in a custom build, all the
resources are copied, not only the needed ones.
For example, qooxdoo only uses a few icons from icon/16/*, but also
icon/22/*, icon/128/* and so on are copied.
I find more practical to determine by hand what is needed and
