Re: SuperDevMode not so super
Thanks Jens for clarifying that. /Adrian Den onsdagen den 26:e november 2014 kl. 17:09:06 UTC+1 skrev Jens: I just got started with SDM but it seems like one cannot inspect variables in the java source maps, maybe I missunderstood the whole thing. It's nice that you can see the java source and step debug, but I really need to be able to inspect variables. For instance I somewhere read that you're supposed to be able to inspect overlay types, which I don't seem to be able to. Have I got something wrong, or did I hope for too much ? Always keep in mind that source maps just overlays javascript to make it look familiar to you. You do not deal with java at all, it is still all javascript. In Chrome dev tools you can see the Scope Variables section on the right which shows you all variable values of the current scope. These are JavaScript variable names but should be easy to identify. When using Source Maps the code viewer in Chrome is more or less read only, so you can not hover anything to get more information about a variable. You also can't navigate your code inside Chrome dev tools by ctrl + click on a java class name of something like that. If you want that then use the experimental Eclipse plugin SDBG or use IntelliJ which both are able to connect to Chrome and show you debugging informations of Chrome inside your IDE. That way you get code navigation back and you can set breakpoints in your IDE instead of Chrome dev tools. -- 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: SuperDevMode not so super
I just got started with SDM but it seems like one cannot inspect variables in the java source maps, maybe I missunderstood the whole thing. It's nice that you can see the java source and step debug, but I really need to be able to inspect variables. For instance I somewhere read that you're supposed to be able to inspect overlay types, which I don't seem to be able to. Have I got something wrong, or did I hope for too much ? /Adrian -- 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: ExceptionInInitializerError when using add-linker name=xsiframe /
Unfortunately my customer thinks otherwise :P -- 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: ExceptionInInitializerError when using add-linker name=xsiframe /
Thanks, i'll have a look -- 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.
ExceptionInInitializerError when using add-linker name=xsiframe /
As the subject states, I get weird initialization errors when using add-linker name=xsiframe / one of the weird errors is : dateField = new DateField(); where DateField is a GWT-Ext component. a clue is the following: Caused by: com.google.gwt.core.client.JavaScriptException: (null) @com. gwtext.client.widgets.Component::checkExtVer()([]): null All the failed tests seemt to point to some gwtext initialization problem. Maybe someone is interested in this /Adrian -- 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. java.lang.ExceptionInInitializerError at com.SE.webstation.client.webhelp.WebHelpModelTest.setUpFixture(WebHelpModelTest.java:40) at com.SE.webstation.client.webhelp.WebHelpModelTest.testFreeTextSearch(WebHelpModelTest.java:45) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at com.google.gwt.junit.client.impl.GWTTestAccessor.invoke(GWTTestAccessor.java:39) at com.google.gwt.junit.client.impl.GWTRunner.executeTestMethod(GWTRunner.java:266) at com.google.gwt.junit.client.GWTTestCase.doRunTest(GWTTestCase.java:150) at junit.framework.TestCase.runTest(TestCase.java:62) at com.google.gwt.junit.client.GWTTestCase.runBare(GWTTestCase.java:144) at com.google.gwt.junit.client.GWTTestCase.__doRunTest(GWTTestCase.java:109) at com.google.gwt.junit.client.impl.GWTRunner.runTest(GWTRunner.java:354) at com.google.gwt.junit.client.impl.GWTRunner.doRunTest(GWTRunner.java:287) at com.google.gwt.junit.client.impl.GWTRunner.access$11(GWTRunner.java:281) at com.google.gwt.junit.client.impl.GWTRunner$TestBlockListener.onSuccess(GWTRunner.java:105) at com.google.gwt.junit.client.impl.GWTRunner$TestBlockListener.onSuccess(GWTRunner.java:1) at com.google.gwt.user.client.rpc.impl.RequestCallbackAdapter.onResponseReceived(RequestCallbackAdapter.java:232) at com.google.gwt.http.client.Request.fireOnResponseReceived(Request.java:259) at com.google.gwt.http.client.RequestBuilder$1.onReadyStateChange(RequestBuilder.java:412) at sun.reflect.GeneratedMethodAccessor48.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at com.google.gwt.dev.shell.MethodAdaptor.invoke(MethodAdaptor.java:103) at com.google.gwt.dev.shell.MethodDispatch.invoke(MethodDispatch.java:71) at com.google.gwt.dev.shell.OophmSessionHandler.invoke(OophmSessionHandler.java:172) at com.google.gwt.dev.shell.BrowserChannelServer.reactToMessagesWhileWaitingForReturn(BrowserChannelServer.java:338) at com.google.gwt.dev.shell.BrowserChannelServer.invokeJavascript(BrowserChannelServer.java:219) at com.google.gwt.dev.shell.ModuleSpaceOOPHM.doInvoke(ModuleSpaceOOPHM.java:136) at com.google.gwt.dev.shell.ModuleSpace.invokeNative(ModuleSpace.java:576) at com.google.gwt.dev.shell.ModuleSpace.invokeNativeObject(ModuleSpace.java:284) at com.google.gwt.dev.shell.JavaScriptHost.invokeNativeObject(JavaScriptHost.java:91) at com.google.gwt.core.client.impl.Impl.apply(Impl.java) at com.google.gwt.core.client.impl.Impl.entry0(Impl.java:354) at sun.reflect.GeneratedMethodAccessor47.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at com.google.gwt.dev.shell.MethodAdaptor.invoke(MethodAdaptor.java:103) at com.google.gwt.dev.shell.MethodDispatch.invoke(MethodDispatch.java:71) at com.google.gwt.dev.shell.OophmSessionHandler.invoke(OophmSessionHandler.java:172) at com.google.gwt.dev.shell.BrowserChannelServer.reactToMessages(BrowserChannelServer.java:293) at com.google.gwt.dev.shell.BrowserChannelServer.processConnection(BrowserChannelServer.java:547) at com.google.gwt.dev.shell.BrowserChannelServer.run(BrowserChannelServer.java:364) at java.lang.Thread.run(Unknown Source) Caused by: com.google.gwt.core.client.JavaScriptException: (null) @com.gwtext.client.widgets.Component::checkExtVer()([]): null at com.google.gwt.dev.shell.BrowserChannelServer.invokeJavascript(BrowserChannelServer.java:249) at
Re: ExceptionInInitializerError when using add-linker name=xsiframe /
I forgot to mention, this happens when run from a GWTTestCase -- 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: The method isCompleteHtml(String) is undefined for the type SafeHtmlHostedModeUtils
Thanks for the quick answer. I don't seem to have anything pre-2.5.0 - which libraries could cause this ? the only gwt-servlet.jar I found was the new one from 2.6.0 Den tisdagen den 1:e april 2014 kl. 11:09:05 UTC+2 skrev Thomas Broyer: isCompleteHtml is public since 2.5.0. Make sure you don't have some pre-2.5.0 libraries (e.g. gwt-servlet.jar) in your classpath that could conflict with your updated GWT 2.6.0 libs. On Tuesday, April 1, 2014 10:06:17 AM UTC+2, Adrian Bastholm wrote: Hi everyone, I just upgraded GWT to 2.6 and I'm trying to use the SafeHtml utilities. Under debug the following message is thrown: Uncaught exception: java.lang.Error: Unresolved compilation problem: The method isCompleteHtml(String) is undefined for the type SafeHtmlHostedModeUtils Eclipse Kepler doesn't find the SafeHtml classes on Open Resource, but the editor is finding them. What am I doing wrong ? /A -- 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: The method isCompleteHtml(String) is undefined for the type SafeHtmlHostedModeUtils
Yes, I was calling it directly from my code. I thought I could use it to check if the display data contains open HTML tags. No problem, I'll file a bug. Thanks for clearing that up Den onsdagen den 2:e april 2014 kl. 12:20:11 UTC+2 skrev Thomas Broyer: Oh sorry, I misunderstood: you're directly calling isCompleteHtml from your code? Yes, it happens that this method is not emulated for prod mode, and will thus fail to compile to JS. Note that if it were, it would always return 'true', so you'd better use maybeCheckCompleteHtml in your client-side code. Would you mind filing a bug so we remember to get it fixed for GWT 2.7? (again, remember that fixing here means compiling, the method would always return 'true' when compiled to JS) On Wednesday, April 2, 2014 12:01:08 PM UTC+2, Adrian Bastholm wrote: I'm adding a log - running with -logLevel DEBUG -- 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: The method isCompleteHtml(String) is undefined for the type SafeHtmlHostedModeUtils
done : https://code.google.com/p/google-web-toolkit/issues/detail?id=8656 Den onsdagen den 2:e april 2014 kl. 12:48:05 UTC+2 skrev Adrian Bastholm: Yes, I was calling it directly from my code. I thought I could use it to check if the display data contains open HTML tags. No problem, I'll file a bug. Thanks for clearing that up Den onsdagen den 2:e april 2014 kl. 12:20:11 UTC+2 skrev Thomas Broyer: Oh sorry, I misunderstood: you're directly calling isCompleteHtml from your code? Yes, it happens that this method is not emulated for prod mode, and will thus fail to compile to JS. Note that if it were, it would always return 'true', so you'd better use maybeCheckCompleteHtml in your client-side code. Would you mind filing a bug so we remember to get it fixed for GWT 2.7? (again, remember that fixing here means compiling, the method would always return 'true' when compiled to JS) On Wednesday, April 2, 2014 12:01:08 PM UTC+2, Adrian Bastholm wrote: I'm adding a log - running with -logLevel DEBUG -- 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.
The method isCompleteHtml(String) is undefined for the type SafeHtmlHostedModeUtils
Hi everyone, I just upgraded GWT to 2.6 and I'm trying to use the SafeHtml utilities. Under debug the following message is thrown: Uncaught exception: java.lang.Error: Unresolved compilation problem: The method isCompleteHtml(String) is undefined for the type SafeHtmlHostedModeUtils Eclipse Kepler doesn't find the SafeHtml classes on Open Resource, but the editor is finding them. What am I doing wrong ? /A -- 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.
