Refactoring

[mwoc]

The code is starting to feel messy. It might be an idea to sit together and look at how it can be improved.
I'd like to start grouping the variables and functions (except the binding logic) better, for instance moving them into two or three objects which are placed outside the 'init' scope ideally - like in knockout.selection
Do you have any ideas on this yet @sunesimonsen ?

[sunesimonsen]

I completely agree and I'm sorry that I'm usually too busy to get around to do these kind of things. But I think it would be great to agree on a refactoring stategy together.

[mwoc]

A major win with refactoring would be the possibility of doing actual unit tests, whereas the current tests are almost exclusively integration tests.

I think we can have three objects, possibly 1 and 2 could be seen as one model though.

1. ListModel - config, dataSource
2. ListViewModel - tile dimensions, calculation logic
3. ListRenderer - viewport dimensions, the various caches, stuff like indexRange, functions for updating the content of those, calibrate height/width, scroll handling etc

This is just brainstorming but I wanted to note my ideas down anyways