Re: Basic SuperDevCompiler + SuperDevModeUI Library

[Ben Dol]

That worked thanks, Jens. Makes this library less useful for me now haha oh 
well might find more use for it at some point.

Appreciate the help.

On Sunday, September 13, 2015 at 2:47:19 AM UTC+12, Jens wrote:
>
>
> Using intellij GWT run configuration with Tomcat7
>>
>
> I assume you have an exploded war artifact configured in IntelliJ that you 
> deploy it using a Tomcat7 server which is also configured inside IntelliJ. 
> In that case add "-war /path/to/war-artifact" to your GWT run configuration 
> as DevMode parameter. Once you do that all public resources as well as a 
> special .nocache.js file will be copied to your IntelliJ artifact 
> which you can then deploy to Tomcat7.
>
> If you don't add that "-war" parameter yourself in the GWT run 
> configuration then IntelliJ will use some temp folder for it which 
> obviously will not be the folder of your exploded war artifact configured 
> inside IntelliJ and that you are going to deploy. Thats probably why you 
> had problems with it.
>
> -- J.
>

-- 
You received this message because you are subscribed to the Google Groups "GWT 
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: Basic SuperDevCompiler + SuperDevModeUI Library

[Jens]

> Using intellij GWT run configuration with Tomcat7
>

I assume you have an exploded war artifact configured in IntelliJ that you 
deploy it using a Tomcat7 server which is also configured inside IntelliJ. 
In that case add "-war /path/to/war-artifact" to your GWT run configuration 
as DevMode parameter. Once you do that all public resources as well as a 
special .nocache.js file will be copied to your IntelliJ artifact 
which you can then deploy to Tomcat7.

If you don't add that "-war" parameter yourself in the GWT run 
configuration then IntelliJ will use some temp folder for it which 
obviously will not be the folder of your exploded war artifact configured 
inside IntelliJ and that you are going to deploy. Thats probably why you 
had problems with it.

-- J.

-- 
You received this message because you are subscribed to the Google Groups "GWT 
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: Basic SuperDevCompiler + SuperDevModeUI Library

[Jens]

Either launch (other parameters omitted)

DevMode -noserver -war /path/to/exploded_war

or

CodeServer -launcherDir /path/to/exploded_war

with /path/to/exploded_war being your build tool's output war directory or 
your GWT-Project/war folder. At work we do this for ages because we always 
use the exact same servlet container as we use in production. So we 
literally never used GWT's bundled jetty server.

What problems did you encounter? When coming from GWT 2.6 classic DevMode 
it should actually just work without any changes to your configuration.

-- J.

-- 
You received this message because you are subscribed to the Google Groups "GWT 
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: Basic SuperDevCompiler + SuperDevModeUI Library

[Ben Dol]

Using intellij GWT run configuration with Tomcat7

"C:\Program Files\Java\jdk1.7.0_65\bin\java" -Xms2048m -Xmx2048m 
-XX:MaxPermSize=1024m -Didea.launcher.port=7536 
"-Didea.launcher.bin.path=E:\Jetbrains\IntelliJ IDEA 14.1.4\bin" 
-Dfile.encoding=windows-1252 -classpath 
"C:\Users\Ben\.m2\repository\com\google\gwt\gwt-codeserver\2.7.0\gwt-codeserver-2.7.0.jar;
 

..."lots of jars"...
com.intellij.rt.execution.application.AppMain com.google.gwt.dev.DevMode 
-superDevMode -war 
C:\Users\Ben\.IntelliJIdea14\system\gwt\xxx-project.e34dc554\xxx.dcb6c866\run\www
 
-noserver -remoteUI 7903:IntelliJIdea -startupUrl http://127.0.0.1:8080/xxx 
nz.co.doltech.xxx

Runing CodeServer with parameters: [-noprecompile, -port, 9876, 
-sourceLevel, 1.7, -bindAddress, 127.0.0.1, -launcherDir, 
C:\Users\Ben\.IntelliJIdea14\system\gwt\xxx.e34dc554\xxx.dcb6c866\run\www, 
-logLevel, INFO, nz.co.doltech.xxx]
Super Dev Mode starting up
   workDir: 
C:\Users\Ben\AppData\Local\Temp\gwt-codeserver-4027014467612992043.tmp
   Loading Java files in nz.co.doltech.xxx.
Linking modules
   Bootstrap link for command-line module 'nz.co.doltech.xxx'

On Sunday, September 13, 2015 at 1:10:30 AM UTC+12, Jens wrote:
>
> Either launch (other parameters omitted)
>
> DevMode -noserver -war /path/to/exploded_war
>
> or
>
> CodeServer -launcherDir /path/to/exploded_war
>
> with /path/to/exploded_war being your build tool's output war directory or 
> your GWT-Project/war folder. At work we do this for ages because we always 
> use the exact same servlet container as we use in production. So we 
> literally never used GWT's bundled jetty server.
>
> What problems did you encounter? When coming from GWT 2.6 classic DevMode 
> it should actually just work without any changes to your configuration.
>
> -- J.
>

-- 
You received this message because you are subscribed to the Google Groups "GWT 
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Basic SuperDevCompiler + SuperDevModeUI Library

[Ben Dol]

So I wanted to invoke SuperDevMode compilations myself removing the need 
for the bookmarks so I wrote an emulated wrapper for the dev_mode_on.js 
compiler interface. Then added some useful features to a SuperDevModeUI 
like auto compile on F5, display compile errors in the same window and an 
optional ghost button to invoke a recompile in the top left corner of the 
application.

https://github.com/BenDol/SuperDevModeUI 



































Anyway, someone might find it useful. I find it helps in my development so 
thought I'd share it.

Enjoy!

-- 
You received this message because you are subscribed to the Google Groups "GWT 
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: Basic SuperDevCompiler + SuperDevModeUI Library

[Jens]

Are you aware that GWT 2.7 already has automatic recompilation on browser 
reload by default?

-- J.

-- 
You received this message because you are subscribed to the Google Groups "GWT 
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: Basic SuperDevCompiler + SuperDevModeUI Library

[Ben Dol]

Not when you are using Tomcat. I know there are ways to get it working with 
Tomcat, but I didn't have any luck with it yet.

On Saturday, September 12, 2015 at 7:27:35 AM UTC+12, Jens wrote:
>
> Are you aware that GWT 2.7 already has automatic recompilation on browser 
> reload by default?
>
> -- J.
>

-- 
You received this message because you are subscribed to the Google Groups "GWT 
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.