Hi GWT developers, There are some concerns on 2.1 MVP approach, which have been raised here http://groups.google.com/group/google-web-toolkit/browse_thread/thread/44cc77811080a288/f53f9d29ebb9257d?lnk=gst&q=mvp#f53f9d29ebb9257d and here http://groups.google.com/group/gwt-platform/browse_thread/thread/862cab91ccb28d40
To summarize, here are some quotes: * It's extremely fast to build an initial scaffold (CRUD for all entities), but I'm not sure how easy it is to customize it for real world usage * When skimming the generated sources I saw A LOT of artifacts, which I don't feel comfortable with because it means that although "officially" my code is not coupled with Roo, if I were to drop it I would have to manage all these generated artifacts myself. * This expenses example is a nightmare to follow. The bindings/ wiring of all the pieces both client and server is nuts. * In M2, things have been cleaned up a bit I'm just trying to make sure the final MVP implementation will be usable without Roo and without automatic code generation, and will be at least as easy to use and understand as http://code.google.com/p/gwt-platform/ . Otherwise, should it be left as a separate project rather than default GWT approach? What do others, more knowledgeable persons than me, think? -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. 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.
