Contrast of development of GWT and Desktop application
Despite the ease of GWT and its effort to make programming web-based application as seamless as desktop application, there is a salient difference in developing for GWT and desktop application. A Java class can be run through its main method in system console whereas GWT requires class to implement EntryPoint interface and to explicitly set in module descriptor file (EntryPoint tag in gwt.xml) prior to execute in GWT’s hosted mode browser. Although this is no fault of GWT as such capability requires explicit support in IDE, developers are likely to miss such time-saving feature. Thinking about how useful it is to able to switch EntryPoint class with ease to mock up user interface prior to testing the whole application. Currently, the work-around is often a repetitious and error-prone task of manually editing gwt.xml file and ensuring that the correct EntryPoint class name is added.
So after weeks of development and preparation, gwtClassRun is finally done along with its supporting WordPress.com site. Using this nifty application that works in tandem with GWT and IDE, one can easily switch EntryPoint class easily and productively. No more manual editing of gwt.xml file, just point-n-click interface enhanced with real-time search auto-completion capability.
Take a look at the video demonstration and watch how easy to setup and perform class switchingVodpod videos no longer available.
Find out more and download the beta application from