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 fragment.
> I don't know the internals, but shouldn't be terribly hard to have the
> source maps for each split point, right? Or isn't it at all supported by
> the compiler?
> Compiling using "-saveSource -saveSourceOutput <dir>" together with
> <set-property name="compiler.useSourceMaps" value="true" /> and
> <set-configuration-property name="includeSourceMapUrl" value="true" />
> correctly saves all sources in the output dir and sets the source map
> comments on each script...
> Also, the CompilerOptionsImpl has this:
> @Override
> public boolean shouldSaveSource() {
> return false; // handling this a different way
> }
>
> This "different way" is explicitly not handling the runAsync case.
> Is there a strong reason for this?
>
SuperDevMode loads the source code right form its classpath (the same way
as when it compiles it) when sending it to the browser (see SourceHandler
and ModuleState).
That said, copying the sources would
solve https://code.google.com/p/google-web-toolkit/issues/detail?id=7615
(but saveSource has only been added recently, and I suspect SuperDevMode
just hasn't caught up yet)
--
You received this message because you are subscribed to the Google Groups
"Google Web Toolkit" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/groups/opt_out.
