The UI-Modules project allows you to easily add Calendar Controls, Google Maps, and a bunch of editors such as TinyMCE and CodeMirror Ace.
NG-Grid allows you to add data grids in your Angular app. NG-Grid comes with quite a few customization options that allow you to place grids with sortable columns to features such as Excel-style editing, in place.
UI-Router is a new way of routing that allows you to create Nested Routing.
IDE Plugins are a bunch of plugins or extensions that provide angularjs support in various text editors.
For this, first of all, either clone or fork the repository or just download the ZIP file from https://github.com/angular-ui/ui-utils.
For simplicity, I suggest that you download the ZIP file; you can find the link on the right-hand side of the GitHub project page. Once we have unpacked the ZIP file, we first need to install the dependencies. On your command line inside the project folder, run the following commands:
$ npm install $ bower install
This will install the necessary files needed for the build process. Let’s first check whether all the tests are passing after the previous commands have run through:
$ karma start --browsers=Chrome test/karma.conf.js --single-run=true
Alternatively, you can also simply run:
The tests are part of the default task specified in
gruntFile.js. Take a moment and familiarize yourself with the file by trying to find where the default task is specified. Note that one subtask is the
karma:unit task. Try to locate this task further down in the file; it specifies which Karma configuration file to load.
If all the tests pass, as they should, we can then build the suite using the following command:
$ grunt build
This will run the following tasks specified in
modules/utils.js. Take a look at the configuration for this task; the easiest way is to search for
bower_components/angular-ui-docs/builddirectory. The configuration for the
concat:modulestask should be right below the previous one. Here, the difference is that there is no absolute file and path; instead, the name is resolved so that common parts, such as the repository name and such, are not repeated within the configuration file. This follows the DRY (don’t repeat yourself) principle and makes the configuration file easier to maintain.
clean:rm_tmptask removes the temporary file, created previously.