I've read that tutorial. It's basically the case that GWT and GAE both use Ant as a build system. They both use rather different default build.xml files. That tutorial tells you how to take GWT's build system and modify it to plug in GAE and JDO. Since I have already got GAE's build system set up the way I like it, and with JDO working, I figured I would do it the other way around, by plugging all the GWT stuff in to the existing build system.
I wasn't planning to use Eclipse though, so if you can figure out how to get it building with Eclipse (without interfering with the existing Ant build system), that would be good. In any case, try playing around with the GWT tutorial separately from MUGLE. I think it would be good to get some experience with it before starting a "real" project (David and I have done three separate GWT projects to get a feel for it first). Don't worry about the HTML. Since we can get GWT working tomorrow, I don't think it will be worth learning how do do non-GWT HTML with Java. -- You received this bug notification because you are a member of MUGLE Developers, which is subscribed to MUGLE. https://bugs.launchpad.net/bugs/722957 Title: Add GWT to project Status in Melbourne University Game-based Learning Environment: Triaged Bug description: Add GWT to the project for creating game management user interface and for supporting GWT RPC APIs. -- Mailing list: https://launchpad.net/~mugle-dev Post to : [email protected] Unsubscribe : https://launchpad.net/~mugle-dev More help : https://help.launchpad.net/ListHelp
