Repository files navigation

Use the directives found inigniteui-angularjs.js to useIgnite UI controls inAngularJS pages.Work with the running samples here or quickly bootstrap your AngularJS project with this preconfigured application -Ignite UI AngularJS seed.

IMPORTANT The repository has been renamed fromigniteui-angular toigniteui-angularjs. This is to avoid confusion caused by the newnaming convention of Angular.

• jQuery v1.8 and later
• AngularJS v1.0 and later
• Ignite UI 13.1 and later

Note: The Ignite UI AngularJS directivesdo not work with the Ignite UI ASP.NET MVC Helpers

You can install this package either withnpm or withbower. This is a development repo!

igniteui-angularjs depends on theignite-ui-full licensed package. Followthis guide on setting up access to the Ignite UI private npm feed and add the dependency to thepackage.json.

"dependencies": {"@infragistics/ignite-ui-full": "latest"}

npm install igniteui-angularjs

bower install igniteui-angularjs

Build will produce an obfuscated and minified version of thesrc/igniteui-angularjs.js in thedist/igniteui-angularjs.min.js.
The build will also put the original and the minified version of thesrc/igniteui-angularjs.js in thedist/npm for distribution to npm.The build usesGrunt, so you needNode.js installed on your machine.
To build the project use the following steps:

1. Open a console in the folder where theigniteui-angularjs project is located
2. Runnpm install
3. Rungrunt build

There are two ways of getting started with the Ignite UI directives. The first one is to use the Ignite UI AngularJS quick start application which is described below. The other way is to configure the application yourself following the page setup instructions step by step.

Ignite UI AngularJS seed is an application skeleton for a typical AngularJS web app using the Ignite UI directives for AngularJS. You can use it to quickly bootstrap your angular webapp projects and dev environment for these projects.

The seed contains a sample AngularJS application and is preconfigured to install the Angular framework and a bunch of development and testing tools for instant web development gratification.

In the page markup include the Ignite UI AngularJS directives file found indist/igniteui-angularjs.min.js along with the Ignite UI scripts:

<script src="jquery.min.js"></script><script src="jquery-ui.min.js"></script><script src="angular.min.js"></script><script src="infragistics.core.js"></script><script src="infragistics.lob.js"></script><script src="igniteui-angularjs.min.js"></script>

Reference theigniteui-directives in your AngularJS module:

var sample_app = angular.module('igniteui-sample-app', ['igniteui-directives']);

Controls can be initialized in two ways:

1. Markup Initialization: directly in an HTML page by using custom tags
2. Controller Initialization: a control placeholder is located in an HTML page, but its initialization options are located in the page controller

Each control implements a custom tag directive where the tag name is formed by splitting each capital letter in the control name with the- symbol (This naming convention follows the standard AngularJS normalization process).

Note: It is recommended to use closing tags (</ig-combo>) over the self-closing tags (<ig-combo/>), because the latter are known to make issues on some browsers (depending on the used document mode).

Simple type control options (string,number,bool etc.) are configured as an attributes on the control element. The options follow the same naming convention logic as the tag name.

Defining complex type control options (arrays &objects) are configured as a child elements of the main control.

<ig-grid><features><feature name="Filtering"></feature></features></ig-grid>

Binding to control events is done again with attributes. Event attribute names are prefixed with the prefixevent- followed by the event name delimited with the- symbol. Once defined the attribute values corresponds to a function name in the scope so you can gain access to the events.

Each control also implements a custom attribute directive where the attribute name is formed by splitting each capital letter in the control name with the- symbol (this naming convention follows the standard AngularJS normalization process) and the attribute value corresponds to the scope object holding the control options.

By default all controls have default element placeholders. You can configure element placeholder by setting theelement attribute to a name of a DOM element.

Example:<ig-text-editor text-mode="multiline" element="textarea"></ig-text-editor>

The following controls currently support one-way data binding:

1. igHtmlEditor
2. igDataChart
3. igSparkline
4. igFunnelChart

The following controls currently support two-way data binding:

1. igGrid
2. igCombo
3. igEditors
4. igTree

Note: When using control API methods which modify the data source outside the AngularJS framework you need to explicitly callScope.$apply() in order to see AngularJS view updated.

There are two kinds of tests in igniteui-angularjs: Unit tests and End to End tests. All of them are written inJasmine.

Simply do:

npm install

The command is preconfigured and it will also callbower install behind the scenes.

Then you need to instrument the source file with:

npm run instrument

The easiest way to run the unit tests is to use the npm script:

npm test

This will start theKarma test runner and execute the tests. By default the browser is Chrome.

To run the tests for a single run you can use:

npm run test-single

To run the tests on Firefox you can use:

npm run test-single-firefox

These tests are run with theProtractor test runner, it simulates interaction.

Before proceeding you need to download and install the latest version of the stand-alone WebDriver tool:

npm run update-webdriver

After that make sure you haveJava Development Kit (JDK) installed on your machine. It is required for the Standalone Selenium Server.

So first the web server should be brought up so that Protractor can execute the tests against it:

npm start

Running the tests is done with:

npm run protractor

Note: You will need to run the protractor on a separate bash

After running the Karma or Protractor tests by default a coverage will be created for each of them.

To combine the both reports into one single report you need to execute:

npm run cover-combined

After that the default directory where you can open the code coverage is igniteui-angularjs/coverage/final/lcov/src.

Running specific coverage:

To view only the Karma coverage you can see it undercoverage/karma/**/lcov-report/src.

To view the code coverage only for the Protractor you need to run the command:

npm run cover-protractor

After that the location is the same(igniteui-angularjs/coverage/final/lcov/src). That is because the Protractor report is not easily readable by default.

Ignite UI is an advanced HTML5+ toolset that helps you create stunning, modern Web apps. Building on jQuery and jQuery UI, it primarily consists of feature rich, high-performing UI controls/widgets such as all kinds of charts, data visualization maps, (hierarchical, editable) data grids, pivot grids, enhanced editors (combo box, masked editors, HTML editor, date picker, to name a few), flexible data source connectors, and a whole lot more. Too many to list here - check outthe site for more info and todownload a trial.

Ignite UI is not just another library created in someone's free time. It is commercial-ready, extremely well-tested, tuned for top performance, designed for good UX, and backed byInfragistics, an experience-focused company with a track record of over 24 years of experience in providing enterprise-ready, high-performance user interface tools for web, windows and mobile environments.