jankuca/ng-scroller

ng-scroller

Performant infinite scrolling AngularJS directive with UITableView-like element reusal

http://ngscroller.herokuapp.com

ng-scroller's Issues

The behavior of ng-scroller-repeat differs from ng-repeat

While an element with the ng-repeat directive itself acts as a clone template, an element with the ng-scroller-repeat directive is itself a container to the clone template instead. This deviation in API design is bound to cause confusion.

It is better to change the API design so that ng-scroller-repeat mimics the usage experience of ng-repeat - or, if not possible/feasible, consider changing the name of the directive so that it no longer falsely hinting at a resemblance to ng-repeat.

Error while building

I got a fresh copy from master and ran npm install. I got the following error:

Running task deps
ok
path.js:360
        throw new TypeError('Arguments to path.join must be strings');
              ^
TypeError: Arguments to path.join must be strings
    at path.js:360:15
    at Array.filter (native)
    at Object.exports.join (path.js:358:36)
    at /home/climatewarrior/coding/ng-scroller/node_modules/closure-runner/main.js:38:20
    at /home/climatewarrior/coding/ng-scroller/node_modules/closure-runner/lib/runner.js:231:16
    at /home/climatewarrior/coding/ng-scroller/node_modules/closure-runner/tasks/deps.js:60:9
    at fn (/home/climatewarrior/coding/ng-scroller/node_modules/closure-runner/node_modules/async/lib/async.js:579:34)
    at Object._onImmediate (/home/climatewarrior/coding/ng-scroller/node_modules/closure-runner/node_modules/async/lib/async.js:495:34)
    at processImmediate [as _immediateCallback] (timers.js:330:15)
npm ERR! weird error 8
npm ERR! not ok code 0

Any help would be appreciated. Thanks!

Needs mobile / touch support

A lot of finicky behavior on mobile devices.

I will fork this and see if I might can help on the touch support. If I make progress, I'll submit a PR.

When scrolling quickly in up direction, See only white space

Mac OS X 10.8.4
Google Chrome 28.0.1500.95

When using "fling" type scrolling, or scrolling very quickly, it is easy to "confuse" the scroller. This begins to happen especially when scrolling back up a page. You end up in a situation where when scrolling down, just as you start to see posts appear, they disappear. It almost looks as though the directive thinks I am in a different position than I actually am. Sometimes all you see is 2 scrollbars.

Heroku site is not up

Error while installing the ng-scroller package as bower dependency

I have added ng-scroller dependency to my bower.json and tried npm install.
Unfortunately it seems that Google Closure dependency cannot be satisfied:

bower closure-library#*     not-cached git://github.com/steida/google-closure-library.git#*
bower closure-library#*        resolve git://github.com/steida/google-closure-library.git#*
bower closure-library#*        ECMDERR Failed to execute "git ls-remote --tags --heads git://github.com/steida/google-closure-library.git", exit code of #128

Additional error details:
fatal: remote error:
  Repository not found.

I am not sure if this problem is specific to ng-scroller or any bower package that depends on Google Closure.

Could you please write some installation instructions?

I'm not very familiar with bower, and don't know what to do here in order to use ng-scroller in my website. Apparently bower search scroller doesn't return ng-scroller, so I can't just do: bower install ng-scroller

Request Commit Distribution Files to Git or Fix Build Process

Currently, dist is empty, and the build process fails (see truncated output below).

$ npm install
npm WARN package.json ng-scroller@ No repository field.

> ng-scroller@ postinstall ng-scroller
> ./build.sh

sh: ./build.sh: Permission denied
npm ERR! weird error 126
npm ERR! not ok code 0

Set proper permissions on the script, and it still fails.

$ chmod +x build.sh 
$ ./build.sh 
-----------------------------------------
Update available: 1.2.6 (current: 1.2.5)
Run npm update -g bower to update
-----------------------------------------

Building app dist
Running task compile
  Cannot find Closure Library DepsWriter

Can you commit a build? Or, better yet, add GitHub releases?

Fetching data from the server again when scrolling up is glitch-inducing

Check out this video:

https://vimeo.com/72580467

Simply put, users will feel weird when they discover they gotta wait for the content they just scrolled pass through to load again, and as can be seen inside the video, it can cause a very noticeable disruption to the browsing experience.

Why not simply use the cached removed content inside the memory?

The video also shows the white space issue reported in #2.

The example scrollers exhibit strange behaviour (don't work well)

If you go to http://ngscroller.herokuapp.com/examples/twitter.html with either Firefox (on Linux) or Chrome (on Linux), then this happens:

Scroll some amount downwards (as much as you want)

Scroll back upwards - the scrollbar never reaches the start, while the scrolling div doesn't let me scroll upwards more than a small amount.

Now try to scroll downwards: it will only scroll a tiny bit, won't let you scroll any further, and you're trapped (in both directions)