Well, I hope this will be sorted out, because debugging on a monolithic
code of hundreds of thousands lines of code simply doesn't work - the
browser hangs as expected.
There's the following statement on
http://www.gwtproject.org/articles/superdevmode.html : "Currently, Super
Dev Mode doesn't w
Maybe there are technical reasons for this since trying to use SourceMaps
with CodeSplitting in a production environment gave me debugging problems
(see https://groups.google.com/forum/#!topic/google-web-toolkit/kUpx5pOkqJs
).
--
You received this message because you are subscribed to the Googl
I've reported
https://code.google.com/p/google-web-toolkit/issues/detail?id=8581
regarding this.
It is very important for large projects to work with SuperDevMode.
So, if anyone has the same problem, please, start the issue.
Best regards, Luis
Em 15-02-2014 10:53, Thomas Broyer escreveu:
On
On Friday, February 14, 2014 8:50:22 PM UTC+1, Luis Fernando Planella
Gonzalez wrote:
>
> Well, after patching CompilerOptionsImpl in gwt-codeserver.jar to return
> true in isRunAsyncEnabled(), the code server started splitting the code,
> but source maps were only generated for the initial fr
Well, after patching CompilerOptionsImpl in gwt-codeserver.jar to return
true in isRunAsyncEnabled(), the code server started splitting the code,
but source maps were only generated for the initial fragment.
I don't know the internals, but shouldn't be terribly hard to have the
source maps for e
Hi.
I'm recently attempting to use SuperDevMode, but our project is quite
large, and the generated compiled .js has ~12MB.
Chrome struggles (and hangs) when attempting to download source maps,
making the whole debugging unpractical.
Without SuperDevMode, we use code splitting, and the fragments a
