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
[](https://gitter.im/angular-ui/ui-scroll?utm_source=badge&utm_medium=badge&utm_campaign=pr-badge&utm_content=badge)
7
7
8
8
<pdir="rtl">
@@ -81,7 +81,7 @@ viewport has to be the table or tbody. dl as a repeated tag is not supported.
81
81
The viewport is an element representing the space where the items from the collection are to be shown. Unless specified explicitly with
82
82
the [uiScrollViewport](#uiscrollviewport-directive) directive, browser window will be used as the viewport.
83
83
84
-
_Important!_ The viewport height must be constrained. If the height of the viewport is not constrained
84
+
_Important!_ The viewport height must be constrained. If the height of the viewport is not constrained
85
85
(style="height:auto") it will pull the entire content of the datasource and may throw an Error depending on the number of items
86
86
in the datasource. Even if it does not, using the directive this way does not provide any advantages over using ng-repeat, because
87
87
item template will be always instantiated for every item in the datasource.
@@ -143,16 +143,16 @@ Currently we have 2 regular modules which can be added to the angular-app you ar
Also, there is one more additional module in a separate file:
148
148
-__ui.scroll.jqlite__ module (it is empty since it was deprecated in v1.6.0)
149
-
150
-
149
+
150
+
151
151
-------------------
152
152
153
153
154
154
## uiScroll directive
155
-
155
+
156
156
157
157
```html
158
158
<divui-scroll="item in myDatasource"
@@ -164,7 +164,7 @@ Also, there is one more additional module in a separate file:
164
164
```
165
165
166
166
### Parameters
167
-
167
+
168
168
***uiScroll – scroll expression** – The expression indicating how to enumerate a collection. Only one format is currently supported: `variable in datasource` – where variable is the user defined loop variable and datasource is the name of the data source to enumerate.
169
169
***buffer-size - expression**, optional - number of items requested from the datasource in a single request. The default is 10 and the minimal value is 3.
170
170
***padding - expression**, optional - extra height added to the visible area for the purpose of determining when the items should be created/destroyed. The value is relative to the visible height of the area, the default is 0.5 and the minimal value is 0.3.
@@ -269,7 +269,7 @@ Adapter object implements the following methods
269
269
270
270
isEmpty()
271
271
272
-
Returns `true` if the dataset is empty and the internal buffer length = 0. Returns `false` otherwise. Mind that isEmpty() will return `true` during the **first** request is pending, so maybe it should be used together with `isLoading` property.
272
+
Returns `true` if the dataset is empty and the internal buffer length = 0. Returns `false` otherwise. Mind that isEmpty() will return `true` during the **first** request is pending, so maybe it should be used together with `isLoading` property.
273
273
274
274
* Method `reload`
275
275
@@ -433,19 +433,19 @@ because of ES6 modules (since v1.6.0), they should be built. The build process i
433
433
There are some npm scripts available for developing.
434
434
435
435
__1__. To run dev-server use
436
-
436
+
437
437
```
438
438
npm start
439
439
```
440
-
440
+
441
441
This should start development server on 5005 port over the [./demo](https://github.com/angular-ui/ui-scroll/tree/master/demo) folder. The dev-server proxy is configured to provide work with temporary distributive files (which are being built in-memory each time the sources from ./src have been changed) despite the direct links to public distributive files form ./dist folder. So the dist-folder should stay clear until the development is finished.
442
-
442
+
443
443
__2__. To run tests in keep-alive mode use
444
-
444
+
445
445
```
446
446
npm test
447
447
```
448
-
448
+
449
449
This runs Karma testing against temporary distributive files that are being built in-memory by the Webpack. We created a number of specifications which consist of more than 200 tests. They are living at the [./test](https://github.com/angular-ui/ui-scroll/tree/master/test) folder. Karma watches both for ./src and ./test folders and automatically re-runs tests after the source code has been changed.
450
450
451
451
__3__. To run both dev-server and tests in keep-alive mode use
@@ -457,29 +457,32 @@ npm run dev
457
457
This is the combination of first two scripts running in concurrently mode. This allows you to work with the ui-scroll examples on 5005 port during continuous tests running.
458
458
459
459
__4__. To run full build process use
460
-
460
+
461
461
```
462
462
npm run build
463
463
```
464
-
464
+
465
465
After developing and testing are completed, the build process should be run to
466
466
a) pass through jshint (both of ui-scroll and test specifications sources),
467
467
b) generate compressed and uncompressed versions of the ui-scroll distributive in the public [./dist](https://github.com/angular-ui/ui-scroll/tree/master/dist) folder,
468
468
c) run tests over minified distributive files.
469
469
470
470
Pull Rerquest should include source code (./scr) changes, may include tests (./test) changes and may not include public distributive (./dist) changes.
471
-
471
+
472
472
473
473
-------------------
474
474
475
475
476
476
## Change log
477
477
478
+
### v1.7.2
479
+
* Fixed IE compatibility issues.
480
+
478
481
### v1.7.1
479
482
* Fixed [Babel dependencies](https://github.com/angular-ui/ui-scroll/pull/195) and [CSS insertRule](https://github.com/angular-ui/ui-scroll/issues/201) issues.
480
483
481
484
### v1.7.0
482
-
* Reduced dygest cycles amount.
485
+
* Reduced digest cycles amount.
483
486
* Refactored some core classes (Adapter, Padding).
0 commit comments