Each modern browser has its own DOM inspector. After a couple of tense non-stop coding month I've made a clue, that Opera-browser's got the most user-friendly debug tool among others. Sad to accept the fact it's got no GWT development plug-in. From the other hand web-kit based browsers are a lot faster, and it's a big part of a deal, when you debugging your app intensively. That is, the chromium one suffice the needs pretty close.
Concerting run-time scope annotations like the @Condition one, it's a sequential sacrifice of end-user processor resources upon the page-loading stage, since in a commonplace GWT best practice cases, this part of preprocessing lies upon the deferred-binding shoulders. But still, good job, since it's fair to mention, that far not all projects have a profit of cascading or MVP. -- 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/-/yxdnBmzZZjcJ. 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.