On 04/13/2009 02:48 PM, pohl wrote:
> Thank you for your responses.   I see that the build-gwt.xml ANT
> script in my GWT4NB-based project does have a "-noserver" argument in
> the block that invokes GWTShell, so at least one compile step is
> necessary, as per Jeff's observation, to copy those resources to the
> server.
>
> I'm still at a loss in my attempt to understand exactly what
> conditions are necessary to get this much-promised "fast turnaround"
> in hosted mode.   If I stop the debugger and debug my project again
> (even if I make absolutely no changes to the source code) the
> GWTCompiler runs again.   Is this a failing in Netbeans and/or GWT4NB?
>    

I'm not a GWT expert, but I'm pretty sure that if you exit hosted mode, 
whatever dynamic structures are created to communicate w/ your IDE are 
lost. Hence the need to recompile on the next invocation.
> Or is my only avenue to try to get the debugger to hot-fix the code
> using the "Apply Code Changes" button (in the Netbeans debugger) and
> then clicking the "refresh" button in hosted mode?
>
> The reason that I ask this last question is that, even if I make a
> trivial change like just changing some text that appears in my
> interface, I get an exception when I click "Apply Code Changes".  (In
> the example below, I merely changed a label on my login panel from
> "Username" to "Usern4me" so that I could visually see that the hotfix
> was applied):
>    

Yeah, I've noticed this too, only I haven't had the impetus to ask it of 
the list. I just assume that the restart is necessary. Maybe some GWT 
pundit knows what we're doing wrong...

Do you know about the <set-property> tag? If not, try adding the 
following to your module.gwt.xml file:
<set-property name="user.agent" value="gecko"/>

using the appropriate browser ID for "value". At least you'll only wait 
for one permutation rather than the (probably) default five. Don't 
forget to remove the tag before compiling for production. I think Vitali 
wrote in some earlier discussion describing how to make this 
set-property a compile-time decision.

--~--~---------~--~----~------------~-------~--~----~
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