Jean-Noel,
the 'export' key filters the jobs of the config for the outside world -
"outside" being either another config or the generator itself. But you
are right, this is not in the documentation for 0.8 (it's already fixed
in the 1.0 documentation).
If you don't want to list a new job in the 'export' key, you can remove
the 'export' key all together, but then you'll also see all kinds of
auxiliary jobs when you do a 'generate.py x'. Otherwise, you have to add
the new job to the 'export' list.
T.
Jean-Noël Rivasseau wrote:
Hello, I have been using Qx for about 9 monthes and I spent two hours
on this. I simply tried to add a job to my config.json file. But the
generator kept telling me the job was not there.
After two hours I realized I had to add the job key to "export". This
is probably because on a default project the project's config file is
included by another one.
Please update the documentation with respect to this as it is really
not intuitive that on a sample project you have to add both the job
key AND take care of exporting it.
Thanks
Jean-Noël Rivasseau
------------------------------------------------------------------------
------------------------------------------------------------------------------
Return on Information:
Google Enterprise Search pays you back
Get the facts.
http://p.sf.net/sfu/google-dev2dev
------------------------------------------------------------------------
_______________________________________________
qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
------------------------------------------------------------------------------
Return on Information:
Google Enterprise Search pays you back
Get the facts.
http://p.sf.net/sfu/google-dev2dev
_______________________________________________
qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
