Closed GoogleCodeExporter closed 9 years ago
I think they should have one proxy responsible for the instantiation of it's
presenters, but that proxy is only here for code-splitting purpose. It should
act
like a place.
Instead a parent should be used to be able to cutomize the general layout of
its
presenters. (Ex : Verticaly, Horizontaly, rows and colums). In that parent you
could
use a Place and then generating the right list of child elements.
Like you said in the end, the instantiation should be done by his parent
presenter,
but a proxy would be usefull in case of really large non singleton presenters.
Original comment by goudreau...@gmail.com
on 8 Mar 2010 at 11:33
It should act like a place. I meant shouldn't
Original comment by goudreau...@gmail.com
on 9 Mar 2010 at 12:32
Makes more sense now. But I'm not even sure it needs a proxy for code
splitting. Just
inject and AsyncProvider<> into the parent provider.
Original comment by philippe.beaudoin
on 9 Mar 2010 at 12:36
I finally decided not to use a proxy. I think the result is pretty neat and
intuitive. See MainPagePresenter for an example on how to use the new
non-singleton
PresenterWidget.
Original comment by philippe.beaudoin
on 9 Mar 2010 at 4:50
Original issue reported on code.google.com by
philippe.beaudoin
on 4 Mar 2010 at 7:08