There's the list of things we do when we switch from one GWT version
to the other:
- uninstall Hosted mode plugin from the browser (it's incompatible
even if you change from 2.1.0 to 2.1.1 and this is not detected by the
framework)
- Make sure that no old gwt-user.jar (or other gwt jars) is copied
Yes I did. It's called read the release notes (or, as they say,
RTFM :-) ). Buried within the document is a small notation that the
hosted mode is renamed to development mode and that the old hosted
mode browser is no longer a part of the toolkit. Click on the
development mode tab and yo
I am having the same issue. Did you find a solution?
--
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-toolk
The development mode logs go into a separate tab titled 'Development Mode'.
Window->Show View->Other->Google->Development Mode
On Fri, Dec 10, 2010 at 6:32 PM, Rob Tanner wrote:
> Hi,
>
> I was running GWT 1.7.1 with the Eclipse toolkit (version 3.5 for
> Galileo) and upgraded to GWT 2.1.0 in or
Hi,
I was running GWT 1.7.1 with the Eclipse toolkit (version 3.5 for
Galileo) and upgraded to GWT 2.1.0 in order to get some functionality
I need on the client side. But when I try to bring up hosted mod, I
get the two standard messages about CocoaComponent compatibility mode
(my development sys
