On Sep 29, 9:38 am, Oskar Hannesson osk...@centrum.is wrote:
I recently switched from Windows to Linux/Ububtu as my main developer
platform and are quite pleased with the change.
However I’m having problem running GWT 2.0 apps in debug mode since
the lack of the Linux version of GWT
I'm running my projects under Ubuntu 64-bit (with FF plugin as the
plugin for Chrome is not available)
as mentioned by Thomas, when needed, i start a VM on Windows to
complete tests with IE (for this purpose the -bindAddress parameter
could be interesting so as to override default 127.0.0.1
hi Thomas !
i am new to GWT.
--
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
The Firefox plugin does work on Linux.
On Wed, Sep 29, 2010 at 09:38, Oskar Hannesson osk...@centrum.is wrote:
I recently switched from Windows to Linux/Ububtu as my main developer
platform and are quite pleased with the change.
However I’m having problem running GWT 2.0 apps in debug mode
PilingOn
Why run two development mode browsers? I've seen this before on the list and
I don't understand the use case. Pick a browser to debug in. All other
browsers are tested using the compiled code.
/PilingOn
On Wed, Sep 29, 2010 at 3:38 AM, Oskar Hannesson osk...@centrum.is wrote:
I
On Sep 29, 5:41 pm, Jeff Chimene jchim...@gmail.com wrote:
PilingOn
Why run two development mode browsers? I've seen this before on the list and
I don't understand the use case. Pick a browser to debug in. All other
browsers are tested using the compiled code.
/PilingOn
Totally agree!
Thanks guys, you saved the day.
I was so focused on Chrome plugin that I didn't even try to look for
the FF plugin.
Oskar H.
On Sep 29, 6:00 pm, Thomas Broyer t.bro...@gmail.com wrote:
On Sep 29, 5:41 pm, Jeff Chimene jchim...@gmail.com wrote:
PilingOn
Why run two development mode browsers?
