I made a lot of changes for using this with a client's app that had a mapview with tableview that slides up from the bottom:
allow the top view, the mapview in my case, to stay fullscreen with the bottom view above it (because resizing map view while panning scrollview looks bad, keeping it fixed size & recentering it while panning looks better)
allowed automatic setup from storyboard using custom segues to reference top & bottom view controllers, setting the top view controller as the delegate if it conforms to protocol
allowed setting height, max of bottom view instead of the top view
allowed setting a snap position, a threshold for snapping to this height or to max or min when panning stops
had problems with scrollview delegate methods, changed to have the bottom view controller just explicitly forward delegate calls to its parent view controller
I'll put what I have into a simple fork for now, but wondered if you'll be interested in taking these changes as pull requests? If so, I'll need to re-implement some of them to be based on your code as starting point rather than the experimental hack & rewrite I did.
But if some of those changes don't fit with your ideas, then I'd rather rename my fork to avoid confusion and let it live as a new cocoapod for my client's app, from which you or any of your users can back-port any of my work as desired.
I made a lot of changes for using this with a client's app that had a mapview with tableview that slides up from the bottom:
I'll put what I have into a simple fork for now, but wondered if you'll be interested in taking these changes as pull requests? If so, I'll need to re-implement some of them to be based on your code as starting point rather than the experimental hack & rewrite I did.
But if some of those changes don't fit with your ideas, then I'd rather rename my fork to avoid confusion and let it live as a new cocoapod for my client's app, from which you or any of your users can back-port any of my work as desired.
Can I get your opinion?