i believe the the very nature of GWT's JRE emulation to javascript with combination with java's lack of closures, is the one causes the large code base. this is because the style of writing itself is extremely different then "regular" java writing.
take for example the mandate to write every function call to a server (RPC,JSON,RF etc..) as asynchronous, in other frameworks, you would have no calls to the server, just page reloads, (or jsp forwards), so it not exactly you gave much thought to actual process of calling a server resource, you just did it, it's like blinking, try to focus on each time you blink and becomes very annoying. add to that, that for each AsyncCallBack you have to write an anonymous class (a poor standin for closures, which java scripts DOES have), and you get even MORE code. and speaking of server client, communication, because of the JRE emulation, you discover on many instances you can't really reuse some of the code or models you wrote on the server as they contain features which are not present client side, and the ONLY way to have some sort of linkage between the 2 sides is via use of annotations, so once again, something you took for granted, comes right back at ya. so now you have to double the code for client server models, and use crap load amount of brackets just for fun of it. and when you try to reuse using generics , you find out the hard way that in some cases you have go through lots of hoops just to get that working right, once again because of the nature of GWT compile process. so in a sense one might say that programming java in gwt, is unlike programming in other web frameworks, although the syntax is the same, you have to un-learn something you got used to over the years. so far i see that the current trend is to create "generators" for the boilerplate codes, via annotations, either to domain models or proxies, and i think that at least to make the work more streamlined google should (off-course) fix major bugs, but also load the GPE with a whole lot more of wizards, generators, re-factoring tools, to bridge this "gap" between regular java and gwt java, i mean it doesn't even have a wizard for creating RPC's not to mention other calls like request factory. not to mention to COMPLETE lack of ide support the module xml file , but that's another rant entirely. and although i took a look at MVP4G and the likes, the problem is they were created prior to activities and places, so if you that with the current gwt, you actually have 2 frameworks for mvp. also places don't really replace history, i think they actually use it behind the scenes. -- 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/-/PEmTMp1P0iAJ. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
