[gwt-contrib] Re: Hide GWT Development Mode window

2016-08-25 Thread Paul Stockley
Thanks, I just ran the code server. The main reason I did this is because Idea runs both the code server and Jetty Server together and passes the same class path to both. Our app has a lot of server dependencies and not too many client specific ones. By breaking them up I was able to tailor the

[gwt-contrib] Re: Hide GWT Development Mode window

2016-08-21 Thread Brandon Donnelson
Figured I'd addon. If you're familiar with the GWT Eclipse plugin, a fork of GPE there are launchers for both GWT and the CodeServer. Both of the GWT launcher types can run Super Dev Mode without a remote ui window and do so by default. The launchers just make launching the Java process with a

[gwt-contrib] Re: Hide GWT Development Mode window

2016-08-21 Thread Jens
You can also just launch CodeServer.main() unless you somehow need the embedded Jetty server launched by legacy DevMode class for your server side code (although IMHO its better to have CodeServer and Servlet container in two different processes so you can relaunch them separately). CodeServer

[gwt-contrib] Re: Hide GWT Development Mode window

2016-08-20 Thread David Becker
Yes, just run in headless mode by adding "-Djava.awt.headless=true" to your VM arguments. I do this all the time on mac. http://www.oracle.com/technetwork/articles/javase/headless-136834.html On Friday, August 19, 2016 at 11:56:24 AM UTC-7, Paul Stockley wrote: > > When launching the SDM code