Version 1.0.0

.gitignore

@@ -1,6 +1,4 @@
 node_modules
 .DS_Store
-tmp
-tmp-npm
-
 npm-debug.log
+lerna-debug.log

README.md

@@ -1,10 +1,16 @@
 # Infinite Scroll for Mithril on mobile and desktop
 
-Compatible with Mithril 0.2.
+Compatible with Mithril 1.0.
 
 * [Documentation](https://github.com/ArthurClemens/mithril-infinite/tree/master/packages/mithril-infinite)
 * [Examples](https://github.com/ArthurClemens/mithril-infinite/tree/master/packages/examples)
 
+
+## Older release
+
+* [Infinite Scroll for Mithril 0.2](https://github.com/ArthurClemens/mithril-infinite/releases/tag/v0.6.2)
+
+
 ## Licence
 
 MIT

index.js

@@ -1 +1 @@
-export { infinite } from "./src/index";
+export { infinite } from './src/index';

lerna.json

@@ -1,5 +1,5 @@
 {
-  "lerna": "2.0.0-beta.34",
+  "lerna": "2.0.0-beta.36",
   "packages": [
     "packages/*"
   ],

packages/examples/README.md

@@ -1,6 +1,7 @@
 [Infinite Scroll documentation](https://github.com/ArthurClemens/mithril-infinite/tree/master/packages/mithril-infinite)
 
 
+
 # Infinite Scroll examples
 
 
@@ -10,6 +11,8 @@
 [View Infinite Scroll examples](http://arthurclemens.github.io/mithril-infinite/index.html)
 
 
+
+
 ## Viewing locally
 
 * `git clone https://github.com/ArthurClemens/mithril-infinite.git`
@@ -31,34 +34,41 @@
 Demonstrates support for unequal content heights and dynamic resizing of content elements, including options `before` and `after`.
 
 
+
+### Horizontal
+
+This is a bit more tricky because the horizontal width needs to be set ("auto" or "100%" doesn't work).
+In the demo we use `pageSize` that returns the `item width * item count`, making sure we have a default width in case the count is 0 (which happens when no data has been received yet).
+
+With CSS, the blocks `mithril-infinite__content`, `mithril-infinite__padding-before` and `mithril-infinite__padding-after` need to be set to `inline-block`.
+
+
+
 ### Grid
 
 A grid of `inline-block` items. A naive approach would be to use the principle of the image list, but scrolled up pages are removed including all of its elements. This would easily lead to gaps in the row, causing all kinds of jumping around of the remaining images.
 
 The trick here is to get neat blocks as "pages" by loading page data with 12 images at a time, and laying them out on a grid of 2, 3, 4 or 6 columns. This way pages are always displayed (and removed) as complete rows.
 
 
+
 ### Table
 
 Demonstrating a list of simple table like data. To prevent redrawing issues, instead of `<table>` tags, we use divs with table styling.
 
 
+
 ### Short content
 
-Traditional approaches use a div at the bottom of the content; when it is scrolled into the viewport, new data is fetched. This example demonstrates that this can be done faster. Infinite calculates the remaining space and increases the `preloadPages` count.
+Traditional approaches use a div at the bottom of the content; when it is scrolled into the viewport, new data is fetched. This example demonstrates that an alternative approach is much faster. Infinite calculates the remaining space and increases the `preloadPages` count.
 
 
-### Horizontal
 
-This is a bit more tricky because the horizontal width needs to be set ("auto" or "100%" doesn't work).
-In the demo we use `pageSize` that returns the `item width * item count`, making sure we have a default width in case the count is 0 (which happens when no data has been received yet).
-
-With CSS, the blocks `mithril-infinite__content`, `mithril-infinite__padding-before` and `mithril-infinite__padding-after` need to be set to `inline-block`.
+### Fixed
 
+Sometimes it is useful to present the user predictable scrollbar behavior: scrolling the scroll knob all the way down leads to the last content page. This is only possible when you know the size of the content (calculated by the number of pages times the height of each page). This example shows how to get the total page count from a request, and use that to calculate the total content height.
 
-### Fixed
 
-Sometimes it is useful to present the user predictable scrollbar behavior: scrolling the scroll knob all the way down leads to the last content page. This is only possible when you know the size of the content (calculated by the number of pages times the height of each page). This example demonstrates the use of the option `contentSize` together with `pageSize`.
 
 
 ### Paging