IE7 and 9 don't like METHOD_POST
My GWT app uses a FormPanel with method set to 'METHOD_POST' in ui.xml. This causes both IE7 and 9 to complain about it saying invalid argument. If I change it to 'POST' manually, it works. What gives? I'm having trouble that this is an oversight on GWT's part. Is there anything I am missing? -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/JOLPqmwS2EEJ. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
Re: Re : IE7 and 9 don't like METHOD_POST
On Friday, July 1, 2011 11:37:26 AM UTC-7, Thomas Broyer wrote: METHOD_POST and METHOD_GET are constants of type String; setAction on FormPanel takes a String argument. So the value you put in the ui.xml is the String value you set directly, so you should use POST, not METHOD_POST. In that case, it's the GWT Desinger's fault, because I chose a value from the drop-down. Nonetheless, thanks. -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/n-Ug4zXV6UAJ. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
GWT generated UI Binder code says Field xxx has no corresponding field in template file
If I generate a new UI Binder, add a named field to the .xml template, in the .java file, the java compiler complains Field xxx has no corresponding field in template file The field is of-course defined in the .ui.xml template. Having said that, the code compiles fine. But, it's just annoying because my project shows errors and it makes it harder to navigate to real errors. Anybody else seeing the same issue? Resolution? Here are the details of software installed on my Eclipse Google Web Toolkit SDK 2.3.0 2.3.0.r35v201105191506 com.google.gwt.eclipse.sdkbundle.e35.feature.feature.group GWT Designer 2.3.2.r35x201106201114 com.google.gdt.eclipse.designer.feature.feature.group WindowBuilder Core Documentation 1.0.0.r35x201106161114 org.eclipse.wb.doc.user.feature.feature.group WindowBuilder Core UI 1.0.0.r35x201106161114 org.eclipse.wb.core.ui.feature.feature.group Eclipse Platform 3.5.2 Eclipse Platform Google Plugin for Eclipse 3.5 2.3.2.r35v201106211634 com.google.gdt.eclipse.suite.e35.feature.feature.group -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/ek8Z6fWnGYEJ. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
Re: GWT generated UI Binder code says Field xxx has no corresponding field in template file
On Friday, July 1, 2011 2:02:24 PM UTC-7, slowpoison wrote: If I generate a new UI Binder, add a named field to the .xml template, in the .java file, the java compiler complains Field xxx has no corresponding field in template file Too bad I was only concentrating on compiling. This problem resolved itself after I pressed F11 to build and run in hosted mode. -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/aJ89qJ3GwskJ. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
Re: Dev plugin for firefox 3.7
On Sep 14, 8:21 am, John Tamplin j...@google.com wrote: I am working on it right now. I have it working on FF40, but I am still trying to get it where one XPI will work on both FF3 and FF4. Any update about this, John? -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To post to this group, send email to google-web-tool...@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
Tree, setFocus and TextBox
I have run into the same problem that has been discussed time and again. For example, here: http://groups.google.com/group/google-web-toolkit/browse_thread/thread/a998b2165103dd60 Basically, the problem is, if you have a GWT Tree, and on a selection event on one of its items, you want to replace the TreeItem's widget with a TextBox to let the user enter text, you run into focus problems. After you instantiate the TextBox and set focus to it, it loses focus the first time user presses a key. If the user focuses on it again manually, everything works fine. I have tried a variety of ways to set the focus on TextBox, including a DeferredCommand, but it always loses it. Can somebody help demystify workings of a Tree with TextBox widgets? -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To post to this group, send email to google-web-tool...@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
Re: compile problems with GWT 2.1
I have the same problem!! Any clues? -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To post to this group, send email to google-web-tool...@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
Unsafe Javascript running GWT tutorial on Chrome
I'm using Chrome 5.0.342.9 beta The same app works fine in Firefox. Here's the full error I see: Unsafe JavaScript attempt to initiate a navigation change for frame with URL about:blank from frame with URL file:///StockWatcher/war/StockWatcher.html. -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To post to this group, send email to google-web-tool...@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
Re: Unsafe Javascript running GWT tutorial on Chrome
I do want to add that http://sticky.appspot.com/ is a sample application built using GWT that works in Chrome. This makes me think that the difference may be due to GWT version. I'm running GWT 2.0.3. Is there any way to find out what version the sample app is running? -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To post to this group, send email to google-web-tool...@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
Re: Unsafe Javascript running GWT tutorial on Chrome
On Apr 29, 9:26 pm, Sripathi Krishnan sripathikrish...@gmail.com wrote: You are trying to run the page from the file system (file://..), which won't work. You should copy the files to a webserver like tomcat and then access the page. Or you could run stockwatcher from eclipse and then test from chrome. Not really. I created a version of stockwatcher that doesn't need any backend service. And as I said before, it works in Firefox, fails in Chrome only. It's not a Chrome problem, because sticky, which I mentioned in my previous post, works in Chrome. That leaves me GWT version differences or some switch in GWT that changes the cross-frame scripting behavior. -- You received this message because you are subscribed to the Google Groups Google Web Toolkit group. To post to this group, send email to google-web-tool...@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
