Arthur, Way to keep your cool against that flamer! Good, clear-headed advice.
All, On our project we've integrated GWT with spring really nicely - and I'd recommend this to anybody planning on creating a large project. Makes unit testing a reality, and configuration a breeze. We've thus far avoided using any third party gwt-libs for the reasons Arthur has already mentioned. Aside from the dependencies on potentially unreliable third parties that this creates, you may not be able achieve the same level of desired functionality compare to rolling your own composites. Using just a bit of CSS and the gwt widgets, you can create your own functional widgets suited to a particular task as need. Showing some search results? Create a search result POJO and a searchResultWidget to match. It really doesn't get any easier. Because GWT so kindly works with the MVC paradigm, it's often very convenient the code the VIEW to match your MODEL (or vice versa) which is not as easy with a third-party lib. Our modest-sized project is easily a 250kb download on the landing page. If we were to add a third party lib to this, our users would not be able tolerate the (down)load times. -lukehashj On Dec 23, 12:53 am, IO <[email protected]> wrote: > Arthur, > Arthur, > I actually find your input very helpful. I saw that you’ve been > criticized for posting it so… I wanted to thank you. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
