On Tuesday, September 25, 2012 7:59:16 AM UTC+2, maticpetek wrote:
>
> Hi,
> We are testing Super Dev mode and the following questions rise to me :
> 1) every time we change Java code, we have to hit "Dev mode on" button and
> then "Compile". In best times it took 40 seconds on my computer. And then I
> have to refresh my browser window. This is not really a magnitude of speed
> increase agains FF Dev more. Reload usually takes around 50-60 seconds. We
> have around 160k lines of client code. Is this expect behavior?
>
The goal is 10secs max, but there are known issues (IIUC, generators need
to be updated to take advantage of CachedGeneratorResult, and only RPC and
ClientBundle generators seem to have been updated for now; but maybe that's
expected: they are those generators that generate static files, not only
Java classes)
> 2) When we get exception in client code, Dev mode will print out full
> stacktrace. Is something like this available in SuperDev mode? For example,
> the following code :
>
> String bla = null;
> bla.length(); // Exception
>
> will print "Uncaught TypeError: Cannot read property 'length' of null" in
> Chrome Console windows, you can get source of compile JS code, but matching
> this with Java code is practical imposible.
>
> 3) Chrome Development Tools. We have let say 500 java source code files in
> different packages. How can I find specific class in tree structure? You
> can find right up the search field ("Search Sources"), but you cannot
> search by source files.
>
Ctrl+O will search by filename.
--
You received this message because you are subscribed to the Google Groups
"Google Web Toolkit" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/google-web-toolkit/-/0rjpt2CFoJkJ.
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.
