Re: Google Chrome 35 GWT plugin incompatibility

Hi,

For me this answer did the trick
http://stackoverflow.com/questions/18419919/how-to-launch-gwt-super-dev-mode
http://www.badlogicgames.com/wordpress/?p=3073

along with the official sdm documentation of course
http://www.gwtproject.org/articles/superdevmode.html

From that point (proof of concept) we have scripts that pickup
dependent projects, classpath, buildpath etc. from eclipse project files
in order to launch sdm codeserver correctly.


On 05/25/14 11:44, David wrote:
> Jens,
>
> I did not realize that, thanks for pointing it out. Well then I guess
> I will have to change my habits.
> Maybe the documentation of SuperDev mode should be improved in the
> next version so that it explains in more details how to debug your
> application with it.
>
> Changes to the eclipse plugin to launch the SuperDev codeserver would
> be great too (I asked the question there already, but got not much
> response).
>
>
> David
>
>
>
> On Fri, May 23, 2014 at 9:17 PM, Jens <jens.nehlmeier@gmail.com
> <mailto:jens.nehlmeier@gmail.com>> wrote:
>
> The nice thing about DevMode was that if you made client
> changes that you could test them straight away without a
> redeploy. (We are using -noserver because our server is Jboss
> Fuse).
> I will need to rebuild and redeploy the application now for
> every client code change (or am I understanding this wrongly ?)
>
>
> You understand it wrong. When you make a client code change you
> hit the recompile bookmarklet of SuperDevMode (which you can drag
> in your browser's bookmark bar) to trigger a recompile of your
> app. After the app is recompiled the page reloads automatically
> and you will see the changes. You only need to redeploy if you
> make server changes. When you activate SDM through its bookmarklet
> all client side code will be downloaded from the SDM code server
> and not from your Jboss Fuse server.
>
> With GWT 2.6 the recompile time may take some time (its similar to
> a -draft compile)...how long that greatly depends on your app.
> However GWT trunk already has initial support for
> incremental/modular compilation. With incremental compilation
> turned on GWT will only recompile the GWT modules in which you
> have made changes and the ones that depend on them. So to make
> best use of incremental compilation your app should consist of
> multiple smaller GWT modules instead of a single large one.
> --
> You received this message because you are subscribed to the Google
> Groups "Google Web Toolkit" group.
> To unsubscribe from this group and stop receiving emails from it,
> send an email to google-web-toolkit+unsubscribe@googlegroups.com
> <mailto:google-web-toolkit+unsubscribe@googlegroups.com>.
> To post to this group, send email to
> google-web-toolkit@googlegroups.com
> <mailto: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.
>
>
> --
> You received this message because you are subscribed to the Google
> Groups "Google Web Toolkit" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to google-web-toolkit+unsubscribe@googlegroups.com
> <mailto:google-web-toolkit+unsubscribe@googlegroups.com>.
> To post to this group, send email to
> google-web-toolkit@googlegroups.com
> <mailto: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.

--
You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscribe@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.