In the last months, more and more use cases of custom behavior appeared.
PhotoView as a generalist zoomable widget of zoomable must be more customizable, but in another way, cover a world of features is not our main objective here.
Customize PhotoView should be easy but use it without any config should be too.
After reading some issues, I think the best pattern to provide an optional, flexible and simple API would be a Controller.
Controller is a patter where a class define parameters of behavior and controlls state outside the widget, this would enable methods like reset (#67).
Due to the amount of issues, this is priority.
After Some work, the controller is starting to take form. #89 will be the PR where the evolution of the controller will be placed at. Once all goals has been achieved, we will merge and release it as 0.2.0.
To summarize its goals:
reset method to make PhotoView go back to its initial values #67 In order to set the next release small and let the controller with a specific concern (controlling state), we shall not include items "Customize the clamping position behavior #68" and "Customize the clamping scale behavior #85"
Merged, sorry for the absurd long time.
Just launched as 0.2.0
Most helpful comment
After Some work, the controller is starting to take form. #89 will be the PR where the evolution of the controller will be placed at. Once all goals has been achieved, we will merge and release it as 0.2.0.
To summarize its goals:
resetmethod to make PhotoView go back to its initial values #67