Hello,
I have a suggestion regarding the release of the toolkit.
I downloaded dojo 1.0 version of the toolkit yesterday and found the examples, themes, demos are also along with the toolkit which is very important to understand how this works.
What I would like to mention is that, if you separate the core working part of the toolkit from the examples and demos then it would be easier to deploy the dojo toolkit in a web application and that too not occupying space for the irrelevant. I prefer not to have any other code apart from the core part of the dojo toolkit being used to be present in the web application and could be the same case with lot of people in the community.
I wish some more suggestions and improvements would come on in.
Thanks,
Uresh :-)
In general...
...the expectation is that when you done developing, you would create a build of the toolkit and simply push that build to your production server, along with any specific items you might need, such as templates and CSS files from Dijit. We'd never expect you to deploy our tests and demos, and it's for that reason that they are isolated the way the are with the Dojo Core and Dijit.
DojoX is a different story, mostly because each item in it is usually some sort of "mini-project", and meant to be self-contained.
Echoing what ttrenka said
Echoing what ttrenka said above, I initially had the 20 MB of dojo code that you probably have. After part way into development, I had a good grasp of what widgets would be used/needed, so I created a Custom Build/Distribution, specifying not to copy tests (includes examples), shrinksafe, etc.
The created directory structure still included 20 MB, so I created a "copyResults.cmd" to copy only the needed files to my distribution directory structure. In my case, the files were, as ttrenka implied above:
robocopy dojo ..\..\..\dojo1\dojo dojo.js
robocopy dojo ..\..\..\dojo1\dojo eqdojo.js <<my custom build
robocopy dojo ..\..\..\dojo1\dojo eqdojo2.js <<my custom build
robocopy dojox\gfx ..\..\..\dojo1\dojox\gfx /e
robocopy dojo\nls ..\..\..\dojo1\dojo\nls eqdojo_en-us.js
robocopy dojo\nls ..\..\..\dojo1\dojo\nls eqdojo2_en-us.js
robocopy dojox\grid\_grid ..\..\..\dojo1\dojox\grid\_grid tundraGrid.css
robocopy dijit\themes\tundra ..\..\..\dojo1\dijit\themes\tundra /e
robocopy dijit\themes\a11y ..\..\..\dojo1\dijit\themes\a11y /e
robocopy dojo\resources ..\..\..\dojo1\dojo\resources dojo.css
robocopy dojo\resources ..\..\..\dojo1\dojo\resources blank.gif
This created a custom distribution of 2 MB...much better!
Pete Higgins has been
Pete Higgins has been working on a "mini" script that strips out all the extraneous stuff like the demos and tests folders. Hopefully we can get something official in the buildscripts dir for Dojo 1.2 that will do the work for you.