This is absolutely true, but we are not talking about day to day GWT development, we are talking about extraordinary circumstances where some amount of optimization is needed.
Under every normal circumstance you would simply develop using widgets, but that becomes impossible if some use case says you need to fill a 100,000 cell grid all at once. That sort of thing puts you into a position where normal GWT development techniques just aren't able to do the job. If you are simply displaying (read only) data, there may be no reason to add all the overhead of a heavyweight object like a widget, and straight html may be the better option. -jason On Apr 16, 2009, at 11:13 AM, Vitali Lovich wrote: > The widgets save so much on development efforts. First of all, > refactoring is trivial & won't break anything. It's trivial to build > up new, complex* widgets using the framework & you don't have to worry > about breaking your HTML generator. You don't need to assign unique > ids to every single widget so that you can access them. The API for > modifying widgets is far easier & more extensible to use than building > up the HTML from scratch. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. 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 -~----------~----~----~----~------~----~------~--~---
