You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@@ -14,8 +15,25 @@ Use the directives found in `igniteui-angular.js` to use [Ignite UI](http://igni
14
15
15
16
> **Note:** The Ignite UI Angular directives *do not* work with the Ignite UI ASP.NET MVC Helpers
16
17
18
+
#Install
19
+
20
+
You can install this package either with `npm` or with `bower`. This is a development repo!
21
+
22
+
### npm
23
+
24
+
```shell
25
+
npm install igniteui-angular
26
+
```
27
+
28
+
### bower
29
+
30
+
```shell
31
+
bower install igniteui-angular
32
+
```
33
+
17
34
#Building
18
35
Build will produce an obfuscated and minified version of the `src/igniteui-angular.js` in the `dist/igniteui-angular.min.js`.
36
+
The build will also put the original and the minified version of the `src/igniteui-angular.js` in the `dist/npm` for distribution to npm.
19
37
The build uses [Grunt](http://gruntjs.com/), so you need [Node.js](http://nodejs.org/) installed on your machine.
20
38
To build the project use the following steps:
21
39
@@ -57,33 +75,34 @@ Each control implements a custom tag directive where the tag name is formed by s
57
75
**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).
58
76
59
77
#### Examples:
60
-
Control Name | Tag
61
-
--- | ---
62
-
igCombo | `<ig-combo>`
63
-
igGrid | `<ig-grid>`
64
-
igDataChart | `<ig-data-chart>`
65
-
igDialog | `<ig-dialog>`
66
-
igDateEditor | `<ig-date-editor>`
67
-
igEditor | `<ig-editor>`
68
-
igMaskEditor | `<ig-mask-editor>`
69
-
igNumericEditor | `<ig-numeric-editor>`
70
-
igPercentEditor | `<ig-percent-editor>`
71
-
igTextEditor | `<ig-text-editor>`
72
-
igDatePicker | `<ig-date-picker>`
73
-
igTree | `<ig-tree>`
74
-
igMap | `<ig-map>`
75
-
igUpload | `<ig-upload>`
76
-
igVideoPlayer | `<ig-video-player>`
78
+
79
+
| Control Name | Tag |
80
+
|-----------------|-----------------------|
81
+
| igCombo |`<ig-combo>`|
82
+
| igGrid |`<ig-grid>`|
83
+
| igDataChart |`<ig-data-chart>`|
84
+
| igDialog |`<ig-dialog>`|
85
+
| igDateEditor |`<ig-date-editor>`|
86
+
| igEditor |`<ig-editor>`|
87
+
| igMaskEditor |`<ig-mask-editor>`|
88
+
| igNumericEditor |`<ig-numeric-editor>`|
89
+
| igPercentEditor |`<ig-percent-editor>`|
90
+
| igTextEditor |`<ig-text-editor>`|
91
+
| igDatePicker |`<ig-date-picker>`|
92
+
| igTree |`<ig-tree>`|
93
+
| igMap |`<ig-map>`|
94
+
| igUpload |`<ig-upload>`|
95
+
| igVideoPlayer |`<ig-video-player>`|
77
96
78
97
### Configuring Control Options
79
98
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.
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 Angular normalization process) and the attribute value corresponds to the scope object holding the control options.
0 commit comments