Splitting code
LS,
I am looking at Code splitting of GWT (
http://www.gwtproject.org/doc/latest/DevGuideCodeSplitting.html).
Looking at the size of our js files, they might/could or should be splitted.
Looking at the documentation, is it just adding a wrapper around the call?
GWT.runAsync(new RunAsyncCallback() { public void onFailure(Throwable
caught) { } public void onSuccess() { } });
--
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 view this discussion on the web visit
https://groups.google.com/d/msgid/google-web-toolkit/CABwrp8KG%2B%3DE6LJCQiEXnAmj1wKPU-F-wz7Q86_KpKD612syyJg%40mail.gmail.com.
Re: GWT Server and debug
Gwt by default converts my(your) code to javascript (JS). With the "old" browser plugin we were able to add breakpoints in the client java code and when running the app, the debugger stopped at those points. I understand, that when running in superdevmode, this works differently. Does anyone has een extended example on how to set this superdevmode up and do the debugging with browser's developer tools? Op woensdag 8 juli 2020 12:20:46 UTC+2 schreef Thomas Broyer: > > > > On Wednesday, July 8, 2020 at 6:46:28 AM UTC+2, Jasper Suijker wrote: >> >> Ok, >> I removed -nosuperDevMode and started the server via debug of eclipse. >> I made some breakpoints in the code, but somehow they are not triggered. >> With the plugin and using internet explorer i see a "unknown" tab showing >> in the GWT development Mode. But when running "just" in the superdevmode i >> don't see that. >> Maybe i am missing or using a configuration in one of the xml files, >> which is preventing debugging? >> > > → “Your code will then run in JS in your browser, and you'll debug it from > your browser's developer tools, leveraging source maps (Chrome or Edge work > better, likely Safari too; Firefox used to be sluggish but that was > supposed to be better in recent versions, haven't tried it yet though).” > > Breakpoints in server code will work as before though. > -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/50587a03-02d5-4d0f-a595-594a41967d5do%40googlegroups.com.
Re: GWT Server and debug
Hi, This SDBG plugin assumes you are using the gwt plugin in eclipse. We have our projects as "normal" java projects and when we want to test, we run an eclipse launch with the correct parameters. I have tried converting the project to a gwt project, but then a run into (gwt) classpath errors, which i am not able to fix. If i want to debug the application in web and not use Internet explorer, i need to use the eclipse plugin or is there an other way? regards, Jasper Op wo 8 jul. 2020 om 07:19 schreef Mbuso Kotobe : > Run the code using Debug as and Choose Open With SDBG Chrome JS Debugger > > It will trigger breakpoints > > I also had the same problem few weeks ago but using that helped so Try it > > Cheers > > On Wed, 08 Jul 2020, 06:46 Jasper Suijker, wrote: > >> Ok, >> I removed -nosuperDevMode and started the server via debug of eclipse. >> I made some breakpoints in the code, but somehow they are not triggered. >> With the plugin and using internet explorer i see a "unknown" tab showing >> in the GWT development Mode. But when running "just" in the superdevmode i >> don't see that. >> Maybe i am missing or using a configuration in one of the xml files, >> which is preventing debugging? >> >> Regards, >> >> Jasper >> >> Op di 7 jul. 2020 om 15:10 schreef Colin Alworth : >> >>> Yes, remove -nosuperDevMode. >>> >>> On Tuesday, July 7, 2020 at 5:02:19 AM UTC-5, Jasper Suijker wrote: >>>> >>>> Hi, >>>> >>>> We are running with 2.8.2 and want to migrate to 2.9.0 later on. >>>> this is my current gwt server start with arguments: >>>> Main class: >>>> com.google.gwt.dev.DevMode >>>> arguments: >>>>com.test.demo.webclient >>>> -war GWT/war >>>> -nosuperDevMode >>>> -startupUrl demo >>>> >>>> What do i need to change to make it start in superdevmode? (remove >>>> -nosuperDevMode?) >>>> >>>> regards, >>>> >>>> Jasper >>>> >>>> >>>> Op dinsdag 7 juli 2020 02:14:06 UTC+2 schreef Thomas Broyer: >>>>> >>>>> gwt.codesrv is a sign that you're using the deprecated so-called >>>>> "classic" DevMode, that relies on a browser plugin, that indeed only works >>>>> in Internet Explorer nowadays. >>>>> If you haven't already, then first upgrade to at least GWT 2.7.0 (of >>>>> course 2.9.0 would be a lot better), >>>>> then you'll be able to use SuperDevMode the same way as you're used to >>>>> run DevMode, except you don't have to install any plugin: just load the >>>>> page in your browser and it'll automatically trigger the compilation of >>>>> your code. >>>>> Your code will then run in JS in your browser, and you'll debug it >>>>> from your browser's developer tools, leveraging source maps (Chrome or >>>>> Edge >>>>> work better, likely Safari too; Firefox used to be sluggish but that was >>>>> supposed to be better in recent versions, haven't tried it yet though). >>>>> See http://www.gwtproject.org/articles/superdevmode.html to learn >>>>> more about SuperDevMode. >>>>> >>>>> On Monday, July 6, 2020 at 5:05:13 PM UTC+2, Jasper Suijker wrote: >>>>>> >>>>>> LS, >>>>>> >>>>>> We are using GWT to get our Swing gui available in web. >>>>>> This works nicely. After compiling, we deploy our application in >>>>>> tomcat and it runs and shows the same screens as we have in Swing. >>>>>> >>>>>> Now we want to debug the web parts through the gwt Jetty server. (GWT >>>>>> development mode) >>>>>> To be able to debug, you Start the jetty server and it will give you >>>>>> a url like: http://127.0.0.1:/?gwt.codesvr=127.0.0.1:9997 >>>>>> The part after the question mark is the magic of the GWT server, >>>>>> being able to debug your code. As far as i know this only works in >>>>>> Internet >>>>>> Explorer, is that correct? >>>>>> >>>>>> Internet Explorer is terrible to work with, the javascript engine is >>>>>> terrible and large memory usage, etc >>>>>> Microsoft is already pushing users towards Edge, so Internet explorer >>>>&g
Re: GWT Server and debug
Ok, I removed -nosuperDevMode and started the server via debug of eclipse. I made some breakpoints in the code, but somehow they are not triggered. With the plugin and using internet explorer i see a "unknown" tab showing in the GWT development Mode. But when running "just" in the superdevmode i don't see that. Maybe i am missing or using a configuration in one of the xml files, which is preventing debugging? Regards, Jasper Op di 7 jul. 2020 om 15:10 schreef Colin Alworth : > Yes, remove -nosuperDevMode. > > On Tuesday, July 7, 2020 at 5:02:19 AM UTC-5, Jasper Suijker wrote: >> >> Hi, >> >> We are running with 2.8.2 and want to migrate to 2.9.0 later on. >> this is my current gwt server start with arguments: >> Main class: >> com.google.gwt.dev.DevMode >> arguments: >>com.test.demo.webclient >> -war GWT/war >> -nosuperDevMode >> -startupUrl demo >> >> What do i need to change to make it start in superdevmode? (remove >> -nosuperDevMode?) >> >> regards, >> >> Jasper >> >> >> Op dinsdag 7 juli 2020 02:14:06 UTC+2 schreef Thomas Broyer: >>> >>> gwt.codesrv is a sign that you're using the deprecated so-called >>> "classic" DevMode, that relies on a browser plugin, that indeed only works >>> in Internet Explorer nowadays. >>> If you haven't already, then first upgrade to at least GWT 2.7.0 (of >>> course 2.9.0 would be a lot better), >>> then you'll be able to use SuperDevMode the same way as you're used to >>> run DevMode, except you don't have to install any plugin: just load the >>> page in your browser and it'll automatically trigger the compilation of >>> your code. >>> Your code will then run in JS in your browser, and you'll debug it from >>> your browser's developer tools, leveraging source maps (Chrome or Edge work >>> better, likely Safari too; Firefox used to be sluggish but that was >>> supposed to be better in recent versions, haven't tried it yet though). >>> See http://www.gwtproject.org/articles/superdevmode.html to learn more >>> about SuperDevMode. >>> >>> On Monday, July 6, 2020 at 5:05:13 PM UTC+2, Jasper Suijker wrote: >>>> >>>> LS, >>>> >>>> We are using GWT to get our Swing gui available in web. >>>> This works nicely. After compiling, we deploy our application in tomcat >>>> and it runs and shows the same screens as we have in Swing. >>>> >>>> Now we want to debug the web parts through the gwt Jetty server. (GWT >>>> development mode) >>>> To be able to debug, you Start the jetty server and it will give you a >>>> url like: http://127.0.0.1:/?gwt.codesvr=127.0.0.1:9997 >>>> The part after the question mark is the magic of the GWT server, being >>>> able to debug your code. As far as i know this only works in Internet >>>> Explorer, is that correct? >>>> >>>> Internet Explorer is terrible to work with, the javascript engine is >>>> terrible and large memory usage, etc >>>> Microsoft is already pushing users towards Edge, so Internet explorer >>>> will stop at some point.. >>>> Is there another way to debug GWT? >>>> >>>> Regards, >>>> >>>> Jasper >>>> >>>> >>>> -- > 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 view this discussion on the web visit > https://groups.google.com/d/msgid/google-web-toolkit/057e4f32-d3ce-4401-ac04-40db4c2d3141o%40googlegroups.com > <https://groups.google.com/d/msgid/google-web-toolkit/057e4f32-d3ce-4401-ac04-40db4c2d3141o%40googlegroups.com?utm_medium=email_source=footer> > . > -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/CABwrp8JzP9b3LQBms2qqCE9eiJLbRG70eiFBZQkRWf%2BrZAPELA%40mail.gmail.com.
Re: GWT Server and debug
Hi, We are running with 2.8.2 and want to migrate to 2.9.0 later on. this is my current gwt server start with arguments: Main class: com.google.gwt.dev.DevMode arguments: com.test.demo.webclient -war GWT/war -nosuperDevMode -startupUrl demo What do i need to change to make it start in superdevmode? (remove -nosuperDevMode?) regards, Jasper Op dinsdag 7 juli 2020 02:14:06 UTC+2 schreef Thomas Broyer: > > gwt.codesrv is a sign that you're using the deprecated so-called "classic" > DevMode, that relies on a browser plugin, that indeed only works in > Internet Explorer nowadays. > If you haven't already, then first upgrade to at least GWT 2.7.0 (of > course 2.9.0 would be a lot better), > then you'll be able to use SuperDevMode the same way as you're used to run > DevMode, except you don't have to install any plugin: just load the page in > your browser and it'll automatically trigger the compilation of your code. > Your code will then run in JS in your browser, and you'll debug it from > your browser's developer tools, leveraging source maps (Chrome or Edge work > better, likely Safari too; Firefox used to be sluggish but that was > supposed to be better in recent versions, haven't tried it yet though). > See http://www.gwtproject.org/articles/superdevmode.html to learn more > about SuperDevMode. > > On Monday, July 6, 2020 at 5:05:13 PM UTC+2, Jasper Suijker wrote: >> >> LS, >> >> We are using GWT to get our Swing gui available in web. >> This works nicely. After compiling, we deploy our application in tomcat >> and it runs and shows the same screens as we have in Swing. >> >> Now we want to debug the web parts through the gwt Jetty server. (GWT >> development mode) >> To be able to debug, you Start the jetty server and it will give you a >> url like: http://127.0.0.1:/?gwt.codesvr=127.0.0.1:9997 >> The part after the question mark is the magic of the GWT server, being >> able to debug your code. As far as i know this only works in Internet >> Explorer, is that correct? >> >> Internet Explorer is terrible to work with, the javascript engine is >> terrible and large memory usage, etc >> Microsoft is already pushing users towards Edge, so Internet explorer >> will stop at some point.. >> Is there another way to debug GWT? >> >> Regards, >> >> Jasper >> >> >> -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/de43b871-43d9-448d-b7ca-2c4725e79f62o%40googlegroups.com.
GWT Server and debug
LS, We are using GWT to get our Swing gui available in web. This works nicely. After compiling, we deploy our application in tomcat and it runs and shows the same screens as we have in Swing. Now we want to debug the web parts through the gwt Jetty server. (GWT development mode) To be able to debug, you Start the jetty server and it will give you a url like: http://127.0.0.1:/?gwt.codesvr=127.0.0.1:9997 The part after the question mark is the magic of the GWT server, being able to debug your code. As far as i know this only works in Internet Explorer, is that correct? Internet Explorer is terrible to work with, the javascript engine is terrible and large memory usage, etc Microsoft is already pushing users towards Edge, so Internet explorer will stop at some point.. Is there another way to debug GWT? Regards, Jasper -- 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 view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/CABwrp8KBf_Zf16hamoEq37PuO13KNO2Cs_MHwsbY-bPvvL7UqQ%40mail.gmail.com.
