I am maintaining an application that I refactored using the MVP pattern. I use the passive view pattern meaning my view is as dumb as possible only forwarding its events via its interface to my presenter.
Right now my presenter got relatively big. Right now I'd like to extract some logic out of it. But that way I would get multiple presenter for a single view.
My root would then construct the view and inject it in several presenter classes, i.e. the first presenter handling only 2 radio buttons, the second presenter only textbox input validation and the third presenter only colors.
Are there any problems I will approach by passing my view around like that to several presenters? I thought view and presenter should always have a 1to1 relationship but never knew or thought about why... Right now I see no reason to not pass the view around and split the logic.
Any thoughts are welcome! Thanks i b advance.