The tutorial you refer to was created before
GWT 1.6.4 was released. As stated in the tutorial itself, it was created with GWT 1.5.3 and works exactly as described in that environment. Google completely changed the default GWT project structure in GWT 1.6.4 which made several things that worked in 1.5.3 not work in 1.6.4. We have spent much of the last two months or so adding full 1.6.4 support to the product. The problem you ran into was caused by one of the changes to GWT that we had not yet adapted to. It was more of a missing feature than a bug, and it was addressed the night of the 16th (the same day it was reported to us). The latest build as of the 17th had this fix as stated (you were using the build from the 13th). If you had updated to the latest build immediately as I suggested rather than waiting until the 20th, it might have "cost you" only one day rather than four. BTW, it didn't actually cost you any "free trial" days as you can request more days any time you want. In fact, here's a new activation key that will extend your eval an extra week for the inconvenience: GWTDesignerEval-5D0TJ-MM1AP-JY1UJ
We use the same general build naming convention as Eclipse itself
and append a build date to the major version number (a very common practice in the Eclipse world). The major version number itself gets incremented every few months in response to major milestones. If you install using the update site (as recommended for Eclipse 3.4 or 3.5) you can get the "latest build" any time you want. When I tell someone on this forum to use the "latest build" that means that the bits on the update site as of that moment contain the fix or feature being discussed.