Thanks for the tip, but my IE problem is that scripts are 100 times
slower, and one process at time make RPC impossible to work with...
and my application deals with huge amounts of data (obejcts) received
through RPC.
Regards,
Edson.
On 2 fev, 15:56, Eric edimickeast...@gmail.com wrote:...
--
I'm working with the following environment:
a) Windows 7 Home Premium 64bit
b) Sun Java JDK 1.6.0_22 32bit and JRockit 4 (1.6.0_20) 32bit
c) NetBeans 6.9.2 on Sun JDK 1.6.0_22 32bit
d) Apache Tomcat 6.0.30 on Sun JDK 1.6.0_22 or JRockit 1.6.0.20 (both
32bit)
e) Front-end Google Chrome
Hi, Chris!
Thanks for your answer - even if I hit the Ignore or Continue
button (I don't remember the exact text appears in the button face,
because I do use Portuguese Brazilian here...), Chrome fronzen until
it dies with the Crash page.
The NPObject error did not happen since latest plugin. If
I've a development environment composed by NetBeans, Apache Tomcat
6.0.30 and GWT 2.0.4.
In the client side, I've Google Chrome and Mozilla Firefox. I gave up
on testing Internet Explorer due the amount of bugs (in IE, to be
clear).
Google Chrome is the fastest and stable browser I've been using
I was dealing with a ton of IE-specific bugs until I changed the
DOCTYPE of my html file to:
!DOCTYPE html
html
head
meta http-equiv=X-UA-Compatible content=IE=IE7
...
It seems my old DOCTYPE of ...4.0.1 Transitional..., which I copied
out of some example 18 months ago, was causing IE to act as
@Edson, what operating system are you using out of curiosity?
I take it the debug mode you're talking about is development mode?
I've been using the development mode plugin in Chrome in both Gentoo Linux
and Kubuntu since December 2010, before that I was having problems as well -
maybe upgrade
Transitional doctype won't work if you're using *LayoutPanels.
--
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-toolkit@googlegroups.com.
To unsubscribe from this group, send email to
Is that for all layout panels (the simple ones like horizontal and vertical
panel included) or just specific ones that fall under the more comlex layout
panels like DockLayout?
On Wed, Feb 2, 2011 at 8:36 PM, Jeff Larsen larse...@gmail.com wrote:
Transitional doctype won't work if you're using
That goes for anything that has Layout in the name.
see more info here.
http://code.google.com/webtoolkit/doc/latest/DevGuideUiPanels.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
Thanks Jeff, this will save me plenty of headaches later this year when I
deploy my app, the default generated by Spring Roo uses transitional even
though the docs explicitly says that the doctype should be !DOCTYPE html
Is this something that I need to log with GWT or with the Spring guys?
The
There isn't a requirement to use layout panels, and I haven't used the Roo
stuff enough to know if they use layout panels in the autogenned stuff that
gets created. Assuming they don't use layout panels, then transitional is a
valid doctype (although still probably a bad idea).
--
You
A DockLayoutPanel is being used in the generated scaffold, which means that
if it's breaking in IE when using transitional (as mentioned in the docs),
the generated scaffold will not work properly in IE.
On Wed, Feb 2, 2011 at 10:00 PM, Jeff Larsen larse...@gmail.com wrote:
There isn't a
The Chrome plugin model slows down development mode a fair amount. Note that
you can ignore those hang timeout warnings that the Chrome UI surfaces--the
dialog will go away once the codeserver hands control back to JS (e.g. while
waiting for a long refresh).
What NPObject error specifically are
13 matches
Mail list logo
