Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>A couple thoughts.</p> <ol> <li>You can avoid building most of dojo (dijit, dojox) but I imagine you already know that</li> <li>This restriction you are facing seems odd. Isn't there some way you can just upload the specific JS files you are editing during development?</li> </ol> <p>Maybe if you give more details on the client setup, I can help you brainstorm a way around this problem.</p> <p><em>Update</em> Here's what I think you need: <a href="http://dojotoolkit.org/reference-guide/build/customBase.html#build-custombase" rel="nofollow">Customize Dojo Base in Build</a>. This allows you to specify particular bits of the dojo base to include.</p> <p>This works in pre-1.7, so you should be good.</p> <p>Appears to be exactly what you want:</p> <pre><code>layers: [ { name: "dojo.js", customBase: true, dependencies: [ ] }, // ... remainder of profile ] </code></pre> <p>This will give you the absolute bare minimum of dojo (which you still don't need for your dev scenario, but which will drastically reduce the amount of files processed). </p> <p>For other use cases, you can use the <code>dependencies</code> attribute to add in other stuff from dojo core.</p> <p><em>Update 2:</em> Here's a couple build-time optimization suggestions:</p> <p>1) Don't intern strings, and don't compress, when in dev. There are arg values you can pass to avoid these time-consuming steps (example is for ant build):</p> <pre><code>&lt;arg value="internStrings=false"/&gt; &lt;arg value="layerOptimize=false"/&gt; </code></pre> <p>2) Build to a ram disk to speed copying of files</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload