Hi, I've just started on an existing project that is using GWT , well Ext GWT (I'm new to it after years of swing development) but they have been hand cranking the screens. I'd like to start using the designer. I installed the designer pluggin into eclipse and tried to open one of the java classes that has been hand coded but it complained about various Ext GWT files not found. I then right clicked on the file and said to use Ext GWT. At first it asked for the gxt.jar file, after a bit of messing around i realised I had to download the gxt.zip unzip it and then point eclipse to the unzipped directory. This seemed to help and some of the hand coded screens could now be viewed in the designer.
Now I supposed my questions are: Would I be better for an existing project using the eclipse designer, or the standalone one. The project screens make use of various imports and inheritance from other project classes will this cause the standalone viewer problems. I noticed that when I asked eclipse to open the designer on a java file it took a long time to process it. Is this just a one hit thing all is it always slow. Maybe some cache files are created, should this be stored along with the code subversion. By the way the project is using Ant to build even though its within eclipse. Is this likely to cause problems with the designer. Thanks for any advice. -- 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.
