how should the MVP pattern handle views created at runtime ?
There is a mainView (that has a model and presenter) that needs to display a list, each item in the list is represented by it's own view, listItemView (which also has it's own model and presenter).
the listItemViews need to be created at run time, along with their models and presenters and they all need to be hooked up.
The solution I have come up with is to have the mainPresenter do all the creation, it creates the presenters, models and also creates the views using an abstract factory.
The mainPresenter will then hook everything up, pass the newly created view to the mainView using an AddUiEelement method I have all views implement. The mainPresenter will also have a list of listItemPresenters which it will add all the listItemPresenters it creates at runtime.
This all works as i expect it to, it also manages to separate the UI technology from the presenter as the abstract factory encapsulates all UI creation logic, however it just feels like a bodge to me, or at least inelegant.
Am i re-inventing the wheel, is this a common problem that has been solved in a better way, I would love to see a better solution.
this is all using .net winforms but i need a solution for winforms/wpf and JavaFX