Hi everybody.
I have a doubt about MVP approach in the Expenses app. In the
ExpensesFactory, the main components of the ExpensesShell (ExpensesTree,
ExpensesReportList and ExpensesReportDetails) are created. They get the
requestFactory instance in their constructor in order to communicate with
the
In other words, the ExpensesTree component does not use MVP. It's a choice
made by the developer. No-one and nothing force you to split your components
into a view and a presenter.
--
You received this message because you are subscribed to the Google Groups
Google Web Toolkit group.
To post
Of course no-one and nothing forces me to use MVP pattern, but that´s the
way. I mean, it´s a kind of coding philosophy. The MVP pattern is supposed
to be followed in the whole application... right? Now, I´m a bit more
confused... what´s the way the application has to behave? MVP here and
there?
On Friday, February 11, 2011 5:00:37 PM UTC+1, ernesto.reig wrote:
Of course no-one and nothing forces me to use MVP pattern, but that´s the
way. I mean, it´s a kind of coding philosophy. The MVP pattern is supposed
to be followed in the whole application... right?
Well... no.
There are
