Re: Info: how to enable NPAPI in chrome
As per the GWT Announcements (Release note 2.6), · GWT Development Mode will no longer be available for Chrome sometime in 2014, so we improved alternate ways of debugging. There are improvements to Super Dev Mode, asserts, console logging, and error messages. So Lunching the Application in Chrome Newer Version with Classic Dev Mode is Disabled, because they have disabled NPAPI Plug-in in Chrome Newer Version. Now it’s time to use Super Dev Mode *SuperDev mode as default in GWT 2.7**:* The Main feature in GWT 2.7 is SuperDev mode(SDM), with Dev mode now deprecated. You use the browser’s built in debugger and don’t need to use any browser plug-in. With SDM, all of your debugging happens right inside your browser, making it easier to debug mixed Java/JavaScript code. If you are familiar with Super Dev Mode in 2.6, you will also notice that you no longer need any bookmarklets to enable/recompile when using Super Dev Mode*, the code is recompiled automatically when you reload the page*. Other Workaround to Launch the Apps in Chrome Newer Version With Classic Dev Mode is to Enable NPAPI Flag, Follow the Below Steps 1.Open New Tab and Enter *chrome://flags/#enable-npapi* 2.Enable this *Enable NPAPI Mac, Windows* 3.Then bottom of the page click "*Relunch*" button. **NPAPI is scheduled to be removed from Chrome(version 45) in September 2015 and this workaround will be supported up to chrome 44 version only. On Wednesday, April 22, 2015 at 11:44:22 PM UTC+5:30, Juan Pablo Gardella wrote: > > For some people that want to use classical dev mode in chrome (super > devmode works very well indeed), you can enable NPAPI plugins accesing > chrome://flags/#enable-npapi. > > Recently, Google Chrome (version 42) disabled the use of NPAPI plugins. > > > *Background:* > > https://www.chromium.org/developers/npapi-deprecation > > > > *Workarounds:* > > From https://www.chromium.org/developers/npapi-deprecation : > > This is a one-off method, unless using group policy with Chrome > > “*Although plugin vendors are working hard to move to alternate > technologies, a small number of users still rely on plugins that haven’t > completed the transition yet. We will provide an override for advanced > users (via chrome://flags/#enable-npapi) and enterprises (via Enterprise > Policy) to temporarily re-enable NPAPI (via the page action UI) while they > wait for mission-critical plugins to make the transition.”* > > [image: cid:image002.png@01D07D03.539FF470] > > > > > -- 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+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: Incremental Build
As I understand it seams that incremental build is only available in Super Dev Mode. So its always a real compile cycle. Beside from the mentioned options to speed things up are there any other things I can do in order to win some seconds on each recompile? I am using a SSD so I guess there is nothing much to gain if I use a ram drive or something. Am Mittwoch, 22. April 2015 15:09:26 UTC+2 schrieb Martin Kersten: > > I am currently creating a transparent GWT compiler adapter which compiles > the libraries if code changes on start of application / test automatically. > > I managed to just drop in some module code in any package and add > additional information using annotations. So everything is working fine > right now. > > What makes me still curious is that I do not know how incremental building > works. How can I use it to speed up the compiler. > > > I understand that compiling only for a single browser will speed things up > (It just gives 0.5 sec), that setting a high level of optimization cost > more time > and also I am using the draft version to speed it up. The linking is > reported to cost .2 seconds and I guess this is the tree shakedown (the > temp js is 500kb > but the final version is 150kb while high optimization results in 60kb). > > > So if someone point me to information regarding incremental build would be > great. > > > Regards. > -- 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+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.
Info: how to enable NPAPI in chrome
For some people that want to use classical dev mode in chrome (super devmode works very well indeed), you can enable NPAPI plugins accesing chrome://flags/#enable-npapi. Recently, Google Chrome (version 42) disabled the use of NPAPI plugins. *Background:* https://www.chromium.org/developers/npapi-deprecation *Workarounds:* >From https://www.chromium.org/developers/npapi-deprecation : This is a one-off method, unless using group policy with Chrome “*Although plugin vendors are working hard to move to alternate technologies, a small number of users still rely on plugins that haven’t completed the transition yet. We will provide an override for advanced users (via chrome://flags/#enable-npapi) and enterprises (via Enterprise Policy) to temporarily re-enable NPAPI (via the page action UI) while they wait for mission-critical plugins to make the transition.”* [image: cid:image002.png@01D07D03.539FF470] -- 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+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: GWT compiler hangs when "Compiling permutation 0"
Related issues for reference, it's hard to find them. https://code.google.com/p/google-web-toolkit/issues/detail?id=7857 https://code.google.com/p/google-web-toolkit/issues/detail?id=9184 -- 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+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: SDM and client debugging with eclipse debugger?
Here's the web-page of the plugin: http://sdbg.github.io/ Drop me a note if you can't get it running. сряда, 22 април 2015 г., 16:23:32 UTC+3, Jens написа: > > With SDM your client side code only runs in the browser and you have to > set break points in the browser's dev tools. Launching the JVM in debug > mode does not give you anything for client side debugging. > > There is an Eclipse plugin called SDGB on Github that allows Eclipse to > connect to Chrome browser and then you can set break points in Eclipse (and > Eclipse synchronizes them with Chrome browser). > > > -- J. > -- 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+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: SDM and client debugging with eclipse debugger?
With SDM your client side code only runs in the browser and you have to set break points in the browser's dev tools. Launching the JVM in debug mode does not give you anything for client side debugging. There is an Eclipse plugin called SDGB on Github that allows Eclipse to connect to Chrome browser and then you can set break points in Eclipse (and Eclipse synchronizes them with Chrome browser). -- J. -- 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+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.
SDM and client debugging with eclipse debugger?
Hi all, I am new to Super Dev Mode in GWT and currently try to use SDM in combination with Client Side Debugging, but it is not working (no break point activation on client side code). My setup is the following: * IDE: Eclipse Luna Service Release 1 (4.4.1) with GWT Plugins 3.8.0 * GWT project based on 2.7.0 * Deployment to local JBOSS (Wildfly) via JBOSS Maven Plugin (mvn wildfly:deploy) * Browser: Chrome 42 The procedure is: * start the code server via maven --> mvn gwt:debug * Start a debug configuration in eclipse that connects to the (code server?) debug port 8000 -> Debug connection successfully established * Compile and deploy project with maven -> mvn clean compile package wildfly:deploy * Start the GWT-App in Chrome (URL pointing to GWT App running on local JBOSS) * Turn "Dev Mode On" with previously created bookmarks -> Recompile Option appears -> Click it --> Recompilation * Trigger Client-side functionality (e.g. click a button) that should trigger a break point activation (e.g. in buttonClicked Handler) ==> NO Break Point Halt in Eclispe Debugger :-( Any hints what could be wrong with my setup? Thanks Kristian -- 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+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.
Incremental Build
I am currently creating a transparent GWT compiler adapter which compiles the libraries if code changes on start of application / test automatically. I managed to just drop in some module code in any package and add additional information using annotations. So everything is working fine right now. What makes me still curious is that I do not know how incremental building works. How can I use it to speed up the compiler. I understand that compiling only for a single browser will speed things up (It just gives 0.5 sec), that setting a high level of optimization cost more time and also I am using the draft version to speed it up. The linking is reported to cost .2 seconds and I guess this is the tree shakedown (the temp js is 500kb but the final version is 150kb while high optimization results in 60kb). So if someone point me to information regarding incremental build would be great. Regards. -- 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+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.
Creating new project GWT in intellij
Hi everyone, I have a problem just making a new GWT projectin Intellij(13.1), would you please just step by step tell me what to do for making a new project? and is there any difference between making project having tomcat or not having tomcat? any help would really be appreciated. -- 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+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.
