Home
Simplify getting started with Dojo, by greatly decreasing the number of files and concepts needed to become productive. Gone are the days of sorting through 20,000 files and their dependencies that might be needed to use Dojo.
-
pre-defined, built/optimized layers for common sub packages of Dojo (a more logical mapping than the current fragmented projects. All Javascript files included in the pre optimized layers are removed from the build output, greatly reducing the overall number of JavaScript files needed to get started.
-
pre-packaged themes (css files & associated resources) for mobile and desktop which have individual .css files rolled up into aggregate CSS layer that's easy to include in HTML pages.
-
pre-packaged localization bundles (multiple bundles, one per language, per major sub package of dojo)
-
AMD Loader (minimal, 4k)
-
Full Core
-
Common UI F/W
-
Desktop UI (dijit)
-
Desktop Theme: Claro (claro)(cross-platform)(optimized)
-
Mobile UI (dojox/mobile)
-
Mobile Theme: iOS (iPad/iPhone)(optimized)
-
Mobile Theme: Android (2.1-3.x)(optimized)
-
Mobile Theme: Blackberry (OS6)(optimized)
-
Mobile Theme: Mobile One UI (future)(cross-platform)(optimized)
-
Vector Graphics API (dojox/gfx)
-
Business Charting (dojox/charting and it's dependencies, with a single default nice looking theme)
-
Grid (gridx)
-
Gauges (dgauge)
-
Calendar (dojox/calendar)
-
Treemap (dojox/treemap)
-
Language packs
Combinations of the above (or finer-grained groupings of modules will be created as needed)
Custom builds for Dojo are an advanced development topic, and doing builds from scratch can be very difficult to achieve because of the many variables and considerable flexibility in build options. Unfortunately, custom builds are a necessity to reduce the number of network requests for resources (the number of resources requested is now higher, due to the finer granularity of modules in Dojo 1.7+)
Because creating builds are very difficult, many new users give up when hitting this complexity barrier.
As described above, we've created a "standard" set of pre-build layers for commonly used Dojo packages. These packages are a trade-off between development complexity and performance optimization, and are intended to be a good starting point when learning Dojo. Once you've learned how to use Dojo (as a black box set of components), you can take the Dojo Build Factory project and tweak it to optimize for your app. With this approach you'll be starting from a working baseline that you can mold to your application's needs.