Disable loading entries via infinite scroll when we know there are no more en...
The old version could get stuck in an infinite look checking for more entries. This look didn't actually perform ajax calls but still was a waste of cpu cycles.
View ArticleWhen there is an unexpected error loading entries, set a flag to indicate...
When there is an unexpected error loading entries, set a flag to indicate there are no more entries available to load. This disables the infinite scroll, this is desirable to avoid an infinite loop of...
View ArticleMore correct behavior for the loading_entries_busy flag.
We no longer check this flag before loading entries. It is entirely possible that e.g. while entries for a feed are loading, the user clicks on a different feed. In this case we do want to load...
View ArticleNavbar button animation now works every time the button is clicked.
The problem was that after the animation ran once, the background opacity was set to 0. This meant that trying to animate the button again had no visible effect, because the animation changed the...
View ArticleMoved loading feeds to a new angularjs service, loadFeedsSvc.
Before this the code that loaded feeds and folders was in a single service, feedsFoldersSvc.
View ArticleFixed bug.
The flag that indicates if the feeds pagination is busy should be set to false when a feeds page loading finishes with an error (e.g. 404). This was already implemented but was removed by mistake in...
View ArticleWIP: load feeds in a web worker.
Moved code that runs when the web worker finishes returning an error to separate functions for each of the possible operations the worker can perform (load a single feed, load a page of all feeds, or...
View Article
