This project provides widgets for lists of data, including simple sets of scrolling rows, grids of data, on-demand lazy-loaded data, and various plugins for additional functionality. This project also provides touch scrolling for mobile devices with native style momentum, bouncing, and scrollbars.
The dgrid project is available under the same dual BSD/AFLv2 license as the Dojo Toolkit.
Automatic Download with CPM
dgrid can be installed via CPM using the following command:
cpm install dgrid
The above command will automatically find the highest tagged version of dgrid and install it. Alternatively, the latest development version of dgrid can be installed by instructing CPM to install from the master branch:
cpm install dgrid master
Note that while dgrid lists the dojo package as a dependency, it does not install dijit, as it is not a hard requirement. Dijit can be additionally installed by running:
cpm install dijit
Alternatively, dgrid and its dependencies can be downloaded individually:
The Dojo Toolkit SDK version 1.7 or higher
- Out of the DTK components, Dojo core is the only hard dependency for dgrid; however, some of the test pages also use components from Dijit, and Dojox (namely grid for a comparison test, and mobile for a mobile page).
It is recommended to arrange all dependencies as siblings, resulting in a directory structure like the following:
dijit(optional, dependency of some dgrid tests)
dojox(optional, dependency of some dgrid tests)
util(optional, e.g. if pursuing a custom build)
dgrid works best with the latest revision of Dojo 1.7 or higher. As of this writing, Dojo 1.9.3 is recommended.
Note that while dgrid supports Dojo 1.8 and 1.9 and may take advantage of features or fix issues specific to them where possible, it does not have any hard dependency on APIs new to 1.8 or 1.9, so as to maintain compatibility with 1.7.
If upgrading from a previous dgrid release, please be sure to read the release notes.
Note: Commands listed in this section are all written assuming they are
run in the parent directory containing
Install the latest geezer version of Intern, which supports IE 6, 7, and 8 in addition to modern browsers.
npm install intern-geezer
Running via the browser
- Open a browser to http://hostname/path_to_dgrid/test/intern/runTests.html
- View the console
Running via Sauce Labs
Make sure the proper Sauce Labs credentials are set in the environment:
export SAUCE_USERNAME=<your_sauce_username> export SAUCE_ACCESS_KEY=<your_sauce_access_key>
Then kick off the runner with the following command:
node node_modules/intern-geezer/runner config=dgrid/test/intern/intern
Running via local Selenium server
Obtain the latest version of the Selenium server and the IE driver server from Selenium's Download page. (The IE driver server needs to be placed in a folder on your PATH.)
The Selenium server can be started by executing:
java -jar path\to\selenium-server-standalone-<version>.jar
Mac OS X
The easiest way to obtain the Selenium standalone server for Mac OS X is by using Homebrew. Once Homebrew is installed, run the following commands:
brew update # ensure you have the lastest formulae brew install selenium-server-standalone brew install chromedriver # for automating tests in Chrome
Recent versions of
selenium-server-standalone install a
script which can be used to start up the server. For additional information
(e.g. how to start the server at login), see the output of
brew info selenium-server-standalone.
Running the tests
Once the Selenium server is running, kick off the Intern test runner with the following command (run from the directory containing dgrid):
node node_modules/intern-geezer/runner config=dgrid/test/intern/intern.local
The configuration in
intern.js to not use
Sauce Connect, and to attempt to run Firefox and Chrome by default (this can
be customized as desired according to the browsers you have installed).
Bugs or enhancements can be filed by opening an issue in the issue tracker on GitHub.
When reporting a bug, please provide the following information:
- Affected browsers and Dojo versions
- A clear list of steps to reproduce the problem
- If the problem cannot be easily reproduced in an existing dgrid test page, include a Gist with code for a page containing a reduced test case
If you would like to suggest a fix for a particular issue, you are welcome to fork dgrid, create a branch, and submit a pull request. Please note that a Dojo CLA is required for any non-trivial modifications.