On Jan 2, 10:01 am, gregor <[email protected]> wrote:
> On Jan 2, 2:42 pm, ussuri <[email protected]> wrote:
>
>
>
> > In general, I'm beginning to question the promised productivity
> > savings - pure javascript approach does not entail compiling at all,
>
> If you are editing your client side code you just press refresh in the
> dev shell browser which will respond in seconds - you don't need to
> recompile unless your server side code has changed.
That's a good tip, thanks! Unfortunately, it won't help me very often
when I do UI things, as layouts render differently in, for example, IE
and FF (e.g. setWidth()/setHeight() differences re: including/
excluding margins/padding) and thus I need to test my edits to layout
in different browsers every time I make them. What's ironic here (at
least to me), is that I mostly test in FF/Chrome, as IE is too slow
currently to handle our "rich client" (heavy client-side data
processing), but GWT hosted browser is IE based in XP, so I do need to
compile things rather then run them in hosted mode most of the time,
even when I do non-UI stuff.
But to my first question: is there a reasonable HW set-up (a reference
system from Dell or HP would work, or a general system config such as
storage type, processor type, memory, OS, etc.) that will make
myproject-compile.bat run in seconds instead of minutes?
Thanks!
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
