It seems like a use case that is not going to be around for too long.  My
recommendation would be to use OOPHM- you get to use your target browser
(I've only tried Firefox - haven't been able to get IE working), but run
with all the benefits of Hosted mode such as dynamically updated client (hit
refresh) & server (restart the jetty server which costs nothing) code &
step-through/breakpoint debugging of both client & server Java code.

On Mon, Mar 16, 2009 at 9:16 AM, Michael Wyraz <[email protected]> wrote:

>
> That's my use-case: developing and testing in the target browser(s).
> The alternative is to develop in the hosted mode and test later in the
> target browser. I use to develop in the target browser to see directly
> if something's going wrong.
> >
>

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Google Web Toolkit" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/Google-Web-Toolkit?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to