With regard to avoiding state in views, I've more or less followed this
practice, but sometimes find it useful to cache re-usable DOM/Widget
elements in views. In these cases, the view knows absolutely nothing
about the general application state, but may keep track of a few minimal
pieces of
Here you find all your answers:
http://martinfowler.com/eaaDev/PassiveScreen.html
- Ed
--
You received this message because you are subscribed to the Google Groups
Google Web Toolkit group.
To view this discussion on the web visit
I think you'll find help on the Dumb Views thing here:
http://code.google.com/webtoolkit/articles/mvp-architecture-2.html although
I don't really understand it fully myself yet. It seems to be further
splitting the view into two parts to avoid the view getting too 'smart'.
--
You received
On Monday, January 16, 2012 8:44:22 AM UTC+1, Qrunk wrote:
What does the following mean ??
GOALS in GWT Develeopment
We need dumb Views, not dumb UIs
(What does View mean here and whats UI in MVP ?? its confusing, , please
explain with a small example, a simple one)
A dumb view is
What does the following mean ??
GOALS in GWT Develeopment
We need dumb Views, not dumb UIs
(What does View mean here and whats UI in MVP ?? its confusing, , please
explain with a small example, a simple one)
• Avoid state within Views
(Which state is it talking about, please explain with a
