thron7-2 wrote: > > > On 04/18/2010 07:58 PM, Jim Hunter wrote: >> So where exactly do you add this? I have tried making it it's own >> section and that didn't work (build version) then I tried adding it to >> the jobs section and that didn't work either. > > It's a *job* key (like most config keys), so you have to add it to a > job. Christian added it to the (unsupported, undocumented, unpublished) > "common" job, which seems to work for him. I'd rather recommend a > dedicated job like "source-script" and/or "build-script". > > T. > >
Ok, good to know it is not a supported key. I assumed it was simply forgotten in the documentation. If you're thinking about it, +1 from me to make it official - if just for being convenient. If not, no big deal. If nothing has changed, by the way, it seems like I didn't make myself clear when we had this discussion a few weeks ago - my point was that I needed to load custom scripts from the contrib libraries, and I understood you as saying that this was not possible, they had be be loaded from an absolute url. So seems like there was no problem in the first place. I'll volunteer to write a snippet for the wiki since this seems to be to be a common scenario. Thanks, Christian -- View this message in context: http://n2.nabble.com/Plugging-custom-code-in-the-loader-tp4916089p4924242.html Sent from the qooxdoo mailing list archive at Nabble.com. ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
