Shaun Cutts

Nice @kornelski ... I thought that `superagent.parse.image` must have something to do with images... :)

My thinking was that the user does know about the buffer, as its a settable parameter, so can react appropriately. If they want to react to content displayed, they don't...

`on-enter-viewport, on-exit-viewport` a little more awkward for my use case, but I could live with it. **EDIT** you could call the callback `displayedSliceDidChange` if you were worried that it included...

Hmm... listeners don't cost very much if they aren't used. How about if we create the `sliceDidChange()` now, and we could add itemwise enter/exit (or ...`chunksDidChange` or whatever is appropriate)...

@raytiley -- do you still fancy `on-enter-viewport`, `on-exit-viewport`? If the collection is displaying 20K data items, and the user drags the scroll bar from top to bottom, do you expect...

I have been using a fork w/ sliceDidChange in one place yes... but so -- not very extensively (but that place is embedded in several other things and it works...

nb -- proposed "viewport" object for layout-bin-packer https://github.com/stefanpenner/layout-bin-packer/issues/10#issuecomment-131199819 ... got it in partially in a branch ... now will need to fit it with the code refactor. That would work...

How about also: - [ ] layout that supports callbacks for item height and width

If we did need to work with data with strict security requirements, this could become a blocker for us, though I'd have to think through it in more detail. Of...

Hmm... maybe adaptation options should be *made* part of `dask.distributed`? :) Seems odd to separate these off. I am hoping to specify clusters by "profile" (and maybe by user) [as...