Revision: 6373
Author: tamplinjohn
Date: Wed Oct 14 12:02:28 2009
Log: Edited wiki page through web user interface.
http://code.google.com/p/google-web-toolkit/source/detail?r=6373
Modified:
/wiki/UsingOOPHM.wiki
=======================================
--- /wiki/UsingOOPHM.wiki Tue Oct 13 17:10:54 2009
+++ /wiki/UsingOOPHM.wiki Wed Oct 14 12:02:28 2009
@@ -38,26 +38,8 @@
Download and run the
[http://google-web-toolkit.googlecode.com/svn/trunk/plugins/ie/prebuilt/GwtDevModeIePluginInstaller.msi
GWT Dev Mode Plugin for IE] installer.
= Using OOPHM =
-OOPHM is currently in trunk (it is not and will not be available with any
version of GWT earlier than 2.0), but is not enabled by default because the
UI needs some work and some features are missing, plus it just hasn't had
enough testing to be sure it is completely usable as a replacement. So, to
use it now, you need to add gwt-dev-oophm.jar at the beginning of your
classpath. There are a number of ways to do it:
-
-== Getting the right Classpath ==
-
- * *webAppCreator*
- If you are creating a war-style project, you can just use webAppCreator
and it will generate an ant target "oophm" for you. You can just run "ant
oophm" and it will run your application using OOPHM instead of legacy
hosted mode. If you have an existing project, you can delete the build.xml
file and then run webAppCreator with -ignore and it won't overwrite any
existing files.
-
- * *Eclipse*
- If you have an existing launch config for Eclipse, simply edit the
classpath for that launch config and add gwt-dev-oophm.jar at the top of
the classpath.
-
-<blockquote> _Life is more complicated if you are running Eclipse on a
Macintosh, and working with GWT source rather than release jars. In that
case you will need to make sure that -XstartOnFirstThread is not in your
launch config arguments, and you will have to remove the SWT jar from your
gwt-dev-mac project._
-
-_However, if you want to run legacy hosted mode again (e.g. to run a
GWTTestCase), you will have to restore the SWT jar to gwt-dev-mac_
-
-_Here's a recipe: OophmForMacBasedGwtContributors_ </blockquote>
-
- * *Others*
- Basically, wherever you set the classpath that includes
gwt-dev-{platform}.jar, make sure that gwt-dev-oophm.jar is searched before
the platform-specific jar.
-
-== Running ==
-Just execute the GWTShell or !HostedMode classes as usual. A swing UI
will show up and it will try and launch firefox with the proper URL -- it
does this by just running "firefox URL", so if you don't have the path set
properly or if you need to run a different executable it will fail -- in
that case, just copy the URL from the log window and paste it in the
browser you want to use.
+OOPHM is currently in trunk (it is not and will not be available with any
version of GWT earlier than 2.0), and is now enabled by default.
+
+If you are using the Eclipse plugin, you may need to manually create a
plain Java launch config until version 1.2 is available (1.12 has some
support).
Note that calls between Java and JS are synchronous, and that means the
plugin has to block the browser while a Java method is executing. If you
are debugging your Java code, the browser will appear hung until you return
back to browser-side code.
--~--~---------~--~----~------------~-------~--~----~
http://groups.google.com/group/Google-Web-Toolkit-Contributors
-~----------~----~----~----~------~----~------~--~---
