On Saturday, September 24, 2011 12:48:02 PM UTC+2, Aidan OK wrote: > > I havn't read the MVP docs in a while, but it should probably be > better explained that its just *one* way of doing GWT development, not > *the* way, and your free to use part of it, none of it, all of it, > depending on what you actually need. >
GWT is a toolkit, not a framework, so it cannot be otherwise. You're free to not use widgets at all too (I believe most GWT-Query projects do not use widgets); and you could, technically, even replace the whole JRE emulation with your own (except for Longs probably). And BTW, MVP is a design pattern, and there's no one single way of implementing it (the MVP articles in the GWT doc makes it kind of clear). And the fact that Activities and Places (which people sometimes erroneously call "MVP framework") are quite new makes it clear that it's not "the" way to build GWT apps: there must have been ways to do it before they're introduced! Are we expecting to see GPE provide Proxy/RequestContext generation in > > the future for non-android apps? > See https://groups.google.com/d/topic/google-plugin-eclipse/L4rzC5xnzW4/discussion -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/oKfby3zLqUcJ. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
