Matt Greenfield

Is this for a scroll view that scrolls horizontally? Fixed position was never tested for those, so it's highly likely that never worked. So yeah, sounds like a bug if...

Looks good to me. @staminajim you want to double check then merge? I don't have any MGBoxKit projects active at the moment, because Swift.

Problem is no one's got time to do it. We're all flat out with the day jobs, and the only time we get for MGBoxKit is for fixing bugs or...

Thanks Greg :) We depend on it pretty heavily too. The lack of internal use of Auto Layout is making it show its age though, so that's a necessary change.

Yeah, horizontally expanding layouts aren't built in yet. The two built in layout algorithms (grid and table) are designed to expand vertically. They base their content width off the width...

I'd prefer to eventually have it available for both layout modes. There are some use cases. But no sense in building something you don't need, so if it's not useful...

This functions the same as UITableView cell reuse, but with a less awkward API and less code requirements. ### Why Block Properties Instead of Protocols The use of block properties...

To initialise the table/grid, you should call `layout`. It should also be called again inside the controller's `willAnimateRotationToInterfaceOrientation:` to update positions during rotation. It's roughly analogous to UITableView's `reloadData`. ```...

As of 3.2.0 boxes will now have their `appeared` `disappeared` methods fired (which by default fire their respective `onAppear` `onDisappear` block properties) when automatically added / removed by box reuse...

Something that's missing from the above examples is how to cope with the underlying data changing. ~~For now the API for that is two step, when it really should be...