4 ms·
If you read the article it wasn't compiled with GWT, but with "ForPlay" which can cross-compile the game written in Java to desktop Java, webapp (via GWT), Andr
by ZoFreX 15y ago
If you read the article it wasn't compiled with GWT, but with "ForPlay" which can cross-compile the game written in Java to desktop Java, webapp (via GWT), Android or Flash.
- nl 15y agoActually, I think forplay would be best characterized as a specialized library, dependent on GWT, with other backend compilers that also depend on GWT. See, for example the instructions: http://code.google.com/p/forplay/wiki/GettingStarted http://code.google.com/p/forplay/wiki/GettingStarted (note how it's the GWT toolchain) Issues like https://code.google.com/p/forplay/issues/detail?id=12 https://code.google.com/p/forplay/issues/detail?id=12 show how the GWT is used to build the Flash version Still not convinced? flash.gwt package: https://code.google.com/p/forplay/source/browse/#svn%2Ftrunk%2Fcore%2Fsrc%2Fflash%2Fgwt https://code.google.com/p/forplay/source/browse/#svn%2Ftrunk... or https://code.google.com/p/forplay/source/browse/trunk/core/src/forplay/flash/FlashStorage.java https://code.google.com/p/forplay/source/browse/trunk/core/s... uses om.google.gwt.core.client.JavaScriptObject same class: private native String get(JavaScriptObject data, String key) /-{ // TODO Auto-generated method stub return data[key]; }-/; (Note the GWT convention for "native" code to be used by the Javascript/Actionscript runtime) Edit: also Joel Webber & Ray Cromwell are both on the GWT team at Google so it makes sense they'd use that toolchain.