Re: [gwt-contrib] Chrome LiveEdit and SDM

['Daniel Kurka' via GWT Contributors]

Hi Ivan,

why would you want to edit the JavaScript instead of editing your Java code?

How long does your compile take with the current GWT 2.7 Snapshot?

-Daniel





On Sun, Aug 31, 2014 at 7:15 PM, Ivan Markov  wrote:

> (Background: I'm trying to further shorten the edit-compile-debug cycle by
> playing with hot-code swapping of recompiled JavaScript in Chrome (via
> Eclipse / SDBG))
>
> GWT 2.7.0-SNAPSHOT, SDM mode, xsiframe linker (obviously), playing with
> LiveEdit from within Chromedevtools initially:
> - Editing ".nocache.js" works
> - However editing "-0.js" does not work (big surprise)
>
> Problem 1: I think the "sourceURL=-0.js" line at the end of the
> script should be present only if CrossSiteIframeLinker is running in
> "non-pretty /  production" mode. In pretty mode, where the 

Re: [gwt-contrib] Chrome LiveEdit and SDM

[Ivan Markov]

Daniel,

I'm not planning to edit the generated JavaScript by hand. My idea is to 
remove the need to do webapp *reloading*. The problem with reloading the 
webapp is NOT that it takes a lot of time (it probably doesn't), but that 
if the webapp is a stateful one, reloading it on each SDM recompile means 
the developer has to essentially "start over" in reproducing the problem 
being debugged (e.g. navigating in the webapp, opening the relevant 
screens, clicking here and there, etc.).

This problem is not something new. It is well known and addressed when 
doing e.g. server-side or rich client development (HotSpot hot code 
replace; JRebel; "edit-and-continue" in the .NET / Win32 world, etc.)

How can webapp reloading be removed? By integrating SuperDevMode in Eclipse 
in such a way that:
(a) The SDM recompilation to be transparent and part of the regular IDE 
project build (
https://github.com/ivmarkov/sdbg/blob/master/com.github.sdbg.integration.jdt/src/com/github/sdbg/integration/jdt/gwt/GWTSDMBuilder.java
)
(b) The JavaScript generated by the recompilation should be automatically 
pushed to Chrome via the Chrome Debugger wire protocol - without reloading 
the webapp
(
https://github.com/ivmarkov/sdbg/blob/master/com.github.sdbg.integration.jdt/src/com/github/sdbg/integration/jdt/gwt/GWTSDMBuilder.java
 
https://github.com/ivmarkov/sdbg/blob/master/com.github.sdbg.integration.jdt/src/com/github/sdbg/integration/jdt/gwt/GWTSDMDOMResourceTracker.java
)

Both (a) and (b) are easy, except that (b) does not work. It does not work, 
because the way the xsiframe linker injects the permutation script in the 
DOM is not compatible with Chrome LiveEdit.

P.S. As for my SDM recompilation times - see here: 
https://groups.google.com/forum/#!topic/google-web-toolkit-contributors/1EYSq2QZ51s

 

-- 
You received this message because you are subscribed to the Google Groups "GWT 
Contributors" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/69679d80-0294-493c-b703-c2d2caf3ceb5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Chrome LiveEdit and SDM

[Ivan Markov]

Ray,

Using the xs linker seems like a bad idea, as it combines the disadvantages 
of sso and the xsiframe: :)
(a) Like xsiframe, it injects 

Re: [gwt-contrib] Re: SDM "-XcompilePerFile": initial feedback

[Arnaud TOURNIER]

Thanks to all of you who participated to this very good things !

I am now able (from the trunk) to have a great experience debugging with 
Gwt + Eclipse + Sdbg + Chrome.

I cannot be quantitatively very precise but the latest optimization 
(-XcompilePerFile) seems to give good results. My project on which i test 
that is not so big so the compilation takes about 10 seconds. Improvements 
are obvious !

Thanks a lot!

Le vendredi 29 août 2014 18:16:40 UTC+2, juan_pablo_gardella a écrit :
>
> Great news!! Thanks a lot for the effort.
>
>
> On 29 August 2014 13:02, Ivan Markov > 
> wrote:
>
>> BTW using a more recent laptop seems to make a difference and nearly 
>> doubles the performance:
>> MacBook Pro model 2013 (I7 2.7 GHz):
>> - 2 to 3 seconds for recompiling changes to a single file
>> - 2 to 3 seconds for linking
>> - Changes to more types of course again results in a growth of the 
>> recompilation time; this time it is 8 instead of 13 seconds for the same 
>> set of around 10 changed files. Linking still 3 seconds.
>>
>> I think you are getting there!
>>
>>  -- 
>> You received this message because you are subscribed to the Google Groups 
>> "GWT Contributors" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to google-web-toolkit-contributors+unsubscr...@googlegroups.com 
>> .
>>  To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/google-web-toolkit-contributors/c646cebb-005a-42fd-9f9d-62334e1a3189%40googlegroups.com
>>  
>> 
>> .
>>
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>

-- 
You received this message because you are subscribed to the Google Groups "GWT 
Contributors" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/2e4c1342-cd60-48c8-b6c0-eb286350b36b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Re: SDM "-XcompilePerFile": initial feedback

['Daniel Kurka' via GWT Contributors]

Hi Arnaud,

are those 10s after the changes we made or before?

-Daniel


On Mon, Sep 1, 2014 at 12:02 PM, Arnaud TOURNIER  wrote:

> Thanks to all of you who participated to this very good things !
>
> I am now able (from the trunk) to have a great experience debugging with
> Gwt + Eclipse + Sdbg + Chrome.
>
> I cannot be quantitatively very precise but the latest optimization
> (-XcompilePerFile) seems to give good results. My project on which i test
> that is not so big so the compilation takes about 10 seconds. Improvements
> are obvious !
>
> Thanks a lot!
>
> Le vendredi 29 août 2014 18:16:40 UTC+2, juan_pablo_gardella a écrit :
>>
>> Great news!! Thanks a lot for the effort.
>>
>>
>> On 29 August 2014 13:02, Ivan Markov  wrote:
>>
>>> BTW using a more recent laptop seems to make a difference and nearly
>>> doubles the performance:
>>> MacBook Pro model 2013 (I7 2.7 GHz):
>>> - 2 to 3 seconds for recompiling changes to a single file
>>> - 2 to 3 seconds for linking
>>> - Changes to more types of course again results in a growth of the
>>> recompilation time; this time it is 8 instead of 13 seconds for the same
>>> set of around 10 changed files. Linking still 3 seconds.
>>>
>>> I think you are getting there!
>>>
>>>  --
>>> You received this message because you are subscribed to the Google
>>> Groups "GWT Contributors" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to google-web-toolkit-contributors+unsubscr...@googlegroups.com
>>> .
>>>  To view this discussion on the web visit https://groups.google.com/d/
>>> msgid/google-web-toolkit-contributors/c646cebb-005a-
>>> 42fd-9f9d-62334e1a3189%40googlegroups.com
>>> 
>>> .
>>>
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>>  --
> You received this message because you are subscribed to the Google Groups
> "GWT Contributors" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/google-web-toolkit-contributors/2e4c1342-cd60-48c8-b6c0-eb286350b36b%40googlegroups.com
> 
> .
>
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Google Germany GmbH
*Dienerstr. 12*
*80331 München*

Registergericht und -nummer: Hamburg, HRB 86891
Sitz der Gesellschaft: Hamburg
Geschäftsführer: Graham Law, Katherine Stephens

-- 
You received this message because you are subscribed to the Google Groups "GWT 
Contributors" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CALLujipnmokiRVxtpE1g%2BF%2BccZbkt0nZYf3jKsDm3ogvmN52%3DA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Re: SDM "-XcompilePerFile": initial feedback

[Arnaud TOURNIER]

Basically the compile took 10s before and 9s now, but this is a very tiny
project, so that's why i am saying the improvement is here but not
quantitatively measurable on my particular project. I will send better
stats when working with bigger projects.

Thanks
Arnuad


2014-09-01 12:25 GMT+02:00 'Daniel Kurka' via GWT Contributors <
google-web-toolkit-contributors@googlegroups.com>:

> Hi Arnaud,
>
> are those 10s after the changes we made or before?
>
> -Daniel
>
>
> On Mon, Sep 1, 2014 at 12:02 PM, Arnaud TOURNIER 
> wrote:
>
>> Thanks to all of you who participated to this very good things !
>>
>> I am now able (from the trunk) to have a great experience debugging with
>> Gwt + Eclipse + Sdbg + Chrome.
>>
>> I cannot be quantitatively very precise but the latest optimization
>> (-XcompilePerFile) seems to give good results. My project on which i test
>> that is not so big so the compilation takes about 10 seconds. Improvements
>> are obvious !
>>
>> Thanks a lot!
>>
>> Le vendredi 29 août 2014 18:16:40 UTC+2, juan_pablo_gardella a écrit :
>>>
>>> Great news!! Thanks a lot for the effort.
>>>
>>>
>>> On 29 August 2014 13:02, Ivan Markov  wrote:
>>>
 BTW using a more recent laptop seems to make a difference and nearly
 doubles the performance:
 MacBook Pro model 2013 (I7 2.7 GHz):
 - 2 to 3 seconds for recompiling changes to a single file
 - 2 to 3 seconds for linking
 - Changes to more types of course again results in a growth of the
 recompilation time; this time it is 8 instead of 13 seconds for the same
 set of around 10 changed files. Linking still 3 seconds.

 I think you are getting there!

  --
 You received this message because you are subscribed to the Google
 Groups "GWT Contributors" group.
 To unsubscribe from this group and stop receiving emails from it, send
 an email to google-web-toolkit-contributors+unsubscribe@
 googlegroups.com.
  To view this discussion on the web visit https://groups.google.com/d/
 msgid/google-web-toolkit-contributors/c646cebb-005a-
 42fd-9f9d-62334e1a3189%40googlegroups.com
 
 .

 For more options, visit https://groups.google.com/d/optout.

>>>
>>>  --
>> You received this message because you are subscribed to the Google Groups
>> "GWT Contributors" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
>>  To view this discussion on the web visit
>> https://groups.google.com/d/msgid/google-web-toolkit-contributors/2e4c1342-cd60-48c8-b6c0-eb286350b36b%40googlegroups.com
>> 
>> .
>>
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
>
> --
> Google Germany GmbH
> *Dienerstr. 12*
> *80331 München*
>
> Registergericht und -nummer: Hamburg, HRB 86891
> Sitz der Gesellschaft: Hamburg
> Geschäftsführer: Graham Law, Katherine Stephens
>
> --
> You received this message because you are subscribed to a topic in the
> Google Groups "GWT Contributors" group.
> To unsubscribe from this topic, visit
> https://groups.google.com/d/topic/google-web-toolkit-contributors/1EYSq2QZ51s/unsubscribe
> .
> To unsubscribe from this group and all its topics, send an email to
> google-web-toolkit-contributors+unsubscr...@googlegroups.com.
>  To view this discussion on the web visit
> https://groups.google.com/d/msgid/google-web-toolkit-contributors/CALLujipnmokiRVxtpE1g%2BF%2BccZbkt0nZYf3jKsDm3ogvmN52%3DA%40mail.gmail.com
> 
> .
>
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups "GWT 
Contributors" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CANjaDneM-U8n56Kjr36Ce5D7_HRvaCcCqExFM4QB%2B-TsQdKNTg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Re: SDM "-XcompilePerFile": initial feedback

[Seamus McMorrow]

Hi guys, 

I have just tried out the 2.7-SNAPSHOT. I have a fairly large multi-module 
maven project. 
For development, I am using STS 3.6, windows7, SSD, i7 3720qm 2.6Ghz, 

Starting SuperDevmode:
Unification traversed 147422 fields and methods and 11825 types. 11773 are 
considered part of the current module and 11773 had all of their fields and 
methods traversed.
Compilation succeeded -- 113.359s
Linking succeeded -- 2.768s
120.982s total -- Compile completed

Changing One File in one module project/jar:
Unification traversed 5282 fields and methods and 2440 types. 238 are 
considered part of the current module and 238 had all of their fields and 
methods traversed.
 Compilation succeeded -- 9.081s
 Linking succeeded -- 1.566s
 13.436s total -- Compile completed

Some other things to note:

When using GWT 2.6.1, a recompile used to take about 45 secs or so.
Sourcemap debugging in Chrome now works perfectly! I can now debug the 
javascript via java in chrome and all the line numbers match. (This was not 
the case with 2.6.1)
On the third compile I tried changing 3 files, however it gave me errors 
about not finding some class files.
I will try to keep using this, and report any other findings.

Keep up the great work guys, GWT development is going to get so much 
cooler. :)
Looking forward to the official release 
 

-- 
You received this message because you are subscribed to the Google Groups "GWT 
Contributors" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/f300a560-19e8-44bd-ba39-b2e48abb8522%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[gwt-contrib] GWT 2.7 snapshot and Eclipse Plugin

[Matic Petek]

Hi,
 I would like to test new compile per file option, but we run our project 
from Eclipse and we don't use Maven. So I have perform the following steps :
1) Download JAR files 
from 
https://oss.sonatype.org/content/repositories/google-snapshots/com/google/gwt/
gwt-servlet.jar
gwt-user.jar
gwt-dev.jar
gwt-codeserver.jar

on 1.9.2014 date

2) Create new "Google" -> "Web Toolkit" configuration

3) select this configuration on my Eclipse project.

But when I run hosted mode, I get the error below. Any idea if I'm doing 
something wrong or Plugin (Kepler SR2, Google Plugin for Eclipse 
4.3 3.7.0.v201407290035-rel-r43) is not update-ed with the latest version 
of GWT. Thank you.
Regards,
   Matic

Exception in thread "main" java.lang.NoSuchMethodError: 
com.google.gwt.dev.javac.CompilationStateBuilder.init(Lcom/google/gwt/core/ext/TreeLogger;Ljava/io/File;)V

at com.google.gwt.dev.DevModeBase.doStartup(DevModeBase.java:943)

at com.google.gwt.dev.DevMode.doStartup(DevMode.java:498)

at com.google.gwt.dev.DevModeBase.startUp(DevModeBase.java:1097)

at com.google.gwt.dev.DevModeBase.run(DevModeBase.java:863)

at com.google.gwt.dev.DevMode.main(DevMode.java:379)

-- 
You received this message because you are subscribed to the Google Groups "GWT 
Contributors" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/74541e9d-c4cb-4ea0-b40b-85a901fc968b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[gwt-contrib] Re: GWT 2.7 snapshot and Eclipse Plugin

[Matic Petek]

For now, I can run my app in Eclipse hosted mode with GWT 2.6.1 and run SDM 
server with GWT 2.7 snaphost. It look nothing has change in GWT-RPC 
protocol so it is working.
Regards,
   Matic

On Monday, September 1, 2014 3:09:18 PM UTC+2, Matic Petek wrote:
>
> Hi,
>  I would like to test new compile per file option, but we run our project 
> from Eclipse and we don't use Maven. So I have perform the following steps :
> 1) Download JAR files from 
> https://oss.sonatype.org/content/repositories/google-snapshots/com/google/gwt/
> gwt-servlet.jar
> gwt-user.jar
> gwt-dev.jar
> gwt-codeserver.jar
>
> on 1.9.2014 date
>
> 2) Create new "Google" -> "Web Toolkit" configuration
>
> 3) select this configuration on my Eclipse project.
>
> But when I run hosted mode, I get the error below. Any idea if I'm doing 
> something wrong or Plugin (Kepler SR2, Google Plugin for Eclipse 
> 4.3 3.7.0.v201407290035-rel-r43) is not update-ed with the latest version 
> of GWT. Thank you.
> Regards,
>Matic
>
> Exception in thread "main" java.lang.NoSuchMethodError: 
> com.google.gwt.dev.javac.CompilationStateBuilder.init(Lcom/google/gwt/core/ext/TreeLogger;Ljava/io/File;)V
>
> at com.google.gwt.dev.DevModeBase.doStartup(DevModeBase.java:943)
>
> at com.google.gwt.dev.DevMode.doStartup(DevMode.java:498)
>
> at com.google.gwt.dev.DevModeBase.startUp(DevModeBase.java:1097)
>
> at com.google.gwt.dev.DevModeBase.run(DevModeBase.java:863)
>
> at com.google.gwt.dev.DevMode.main(DevMode.java:379)
>
>

-- 
You received this message because you are subscribed to the Google Groups "GWT 
Contributors" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/913709c2-0ba4-47cf-bd75-1ca6286635ea%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Chrome LiveEdit and SDM

['John Stalcup' via GWT Contributors]

you could try changing line 182 in Recompiler.java to register the "std"
linker
https://gwt.googlesource.com/gwt.git/+/2.5.1/dev/codeserver/java/com/google/gwt/dev/codeserver/Recompiler.java


On Mon, Sep 1, 2014 at 2:43 AM, Ivan Markov  wrote:

> Ray,
>
> Using the xs linker seems like a bad idea, as it combines the
> disadvantages of sso and the xsiframe: :)
> (a) Like xsiframe, it injects 

Re: [gwt-contrib] Chrome LiveEdit and SDM

['John Stalcup' via GWT Contributors]

err, in master that would be
https://gwt.googlesource.com/gwt.git/+/master/dev/codeserver/java/com/google/gwt/dev/codeserver/Recompiler.java
and line 327


On Mon, Sep 1, 2014 at 12:58 PM, John Stalcup  wrote:

> you could try changing line 182 in Recompiler.java to register the "std"
> linker
> https://gwt.googlesource.com/gwt.git/+/2.5.1/dev/codeserver/java/com/google/gwt/dev/codeserver/Recompiler.java
>
>
> On Mon, Sep 1, 2014 at 2:43 AM, Ivan Markov  wrote:
>
>> Ray,
>>
>> Using the xs linker seems like a bad idea, as it combines the
>> disadvantages of sso and the xsiframe: :)
>> (a) Like xsiframe, it injects 

Re: [gwt-contrib] Re: SDM "-XcompilePerFile": initial feedback

['John Stalcup' via GWT Contributors]

Such a small time makes me think that you have particularly slow linkers.
What's the time split between compiling and linking?


On Mon, Sep 1, 2014 at 3:32 AM, Arnaud TOURNIER  wrote:

> Basically the compile took 10s before and 9s now, but this is a very tiny
> project, so that's why i am saying the improvement is here but not
> quantitatively measurable on my particular project. I will send better
> stats when working with bigger projects.
>
> Thanks
> Arnuad
>
>
> 2014-09-01 12:25 GMT+02:00 'Daniel Kurka' via GWT Contributors <
> google-web-toolkit-contributors@googlegroups.com>:
>
>> Hi Arnaud,
>>
>> are those 10s after the changes we made or before?
>>
>> -Daniel
>>
>>
>> On Mon, Sep 1, 2014 at 12:02 PM, Arnaud TOURNIER 
>> wrote:
>>
>>> Thanks to all of you who participated to this very good things !
>>>
>>> I am now able (from the trunk) to have a great experience debugging with
>>> Gwt + Eclipse + Sdbg + Chrome.
>>>
>>> I cannot be quantitatively very precise but the latest optimization
>>> (-XcompilePerFile) seems to give good results. My project on which i test
>>> that is not so big so the compilation takes about 10 seconds. Improvements
>>> are obvious !
>>>
>>> Thanks a lot!
>>>
>>> Le vendredi 29 août 2014 18:16:40 UTC+2, juan_pablo_gardella a écrit :

 Great news!! Thanks a lot for the effort.


 On 29 August 2014 13:02, Ivan Markov  wrote:

> BTW using a more recent laptop seems to make a difference and nearly
> doubles the performance:
> MacBook Pro model 2013 (I7 2.7 GHz):
> - 2 to 3 seconds for recompiling changes to a single file
> - 2 to 3 seconds for linking
> - Changes to more types of course again results in a growth of the
> recompilation time; this time it is 8 instead of 13 seconds for the same
> set of around 10 changed files. Linking still 3 seconds.
>
> I think you are getting there!
>
>  --
> You received this message because you are subscribed to the Google
> Groups "GWT Contributors" group.
> To unsubscribe from this group and stop receiving emails from it, send
> an email to google-web-toolkit-contributors+unsubscribe@
> googlegroups.com.
>  To view this discussion on the web visit https://groups.google.com/d/
> msgid/google-web-toolkit-contributors/c646cebb-005a-
> 42fd-9f9d-62334e1a3189%40googlegroups.com
> 
> .
>
> For more options, visit https://groups.google.com/d/optout.
>

  --
>>> You received this message because you are subscribed to the Google
>>> Groups "GWT Contributors" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to google-web-toolkit-contributors+unsubscr...@googlegroups.com
>>> .
>>>  To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/google-web-toolkit-contributors/2e4c1342-cd60-48c8-b6c0-eb286350b36b%40googlegroups.com
>>> 
>>> .
>>>
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>>
>>
>> --
>> Google Germany GmbH
>> *Dienerstr. 12*
>> *80331 München*
>>
>> Registergericht und -nummer: Hamburg, HRB 86891
>> Sitz der Gesellschaft: Hamburg
>> Geschäftsführer: Graham Law, Katherine Stephens
>>
>> --
>> You received this message because you are subscribed to a topic in the
>> Google Groups "GWT Contributors" group.
>> To unsubscribe from this topic, visit
>> https://groups.google.com/d/topic/google-web-toolkit-contributors/1EYSq2QZ51s/unsubscribe
>> .
>> To unsubscribe from this group and all its topics, send an email to
>> google-web-toolkit-contributors+unsubscr...@googlegroups.com.
>>  To view this discussion on the web visit
>> https://groups.google.com/d/msgid/google-web-toolkit-contributors/CALLujipnmokiRVxtpE1g%2BF%2BccZbkt0nZYf3jKsDm3ogvmN52%3DA%40mail.gmail.com
>> 
>> .
>>
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>  --
> You received this message because you are subscribed to the Google Groups
> "GWT Contributors" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/google-web-toolkit-contributors/CANjaDneM-U8n56Kjr36Ce5D7_HRvaCcCqExFM4QB%2B-TsQdKNTg%40mail.gmail.com
> 

Re: [gwt-contrib] Re: SDM "-XcompilePerFile": initial feedback

['John Stalcup' via GWT Contributors]

On Mon, Sep 1, 2014 at 3:55 AM, Seamus McMorrow 
wrote:

> Hi guys,
>
> I have just tried out the 2.7-SNAPSHOT. I have a fairly large multi-module
> maven project.
> For development, I am using STS 3.6, windows7, SSD, i7 3720qm 2.6Ghz,
>
> Starting SuperDevmode:
> Unification traversed 147422 fields and methods and 11825 types. 11773 are
> considered part of the current module and 11773 had all of their fields and
> methods traversed.
> Compilation succeeded -- 113.359s
> Linking succeeded -- 2.768s
> 120.982s total -- Compile completed
>
The first compile in -XcompilePerFile is slower than a regular compile
since it has to traverse a larger set of types and traverse them more fully
(to ensure later cache accesses are correct). I'm guessing that normally
you get about an 80s first compile? Eventually we should be able to make
even this first compile faster by persisting the MinimalRebuildCache to
disk and reusing it between different SDM process launches. Also (as
Roberto pointed out recently) if we switche from whole-type linking to
per-function linking then we could probably get away with doing the
old-style partial-class traversal, which would mean faster first compiles
and a little bit smaller output.


> Changing One File in one module project/jar:
> Unification traversed 5282 fields and methods and 2440 types. 238 are
> considered part of the current module and 238 had all of their fields and
> methods traversed.
>  Compilation succeeded -- 9.081s
>  Linking succeeded -- 1.566s
>  13.436s total -- Compile completed
>
> Some other things to note:
>
> When using GWT 2.6.1, a recompile used to take about 45 secs or so.
> Sourcemap debugging in Chrome now works perfectly! I can now debug the
> javascript via java in chrome and all the line numbers match. (This was not
> the case with 2.6.1)
> On the third compile I tried changing 3 files, however it gave me errors
> about not finding some class files.
>
Can you post these error messages and whether they are related to a
Generator? Are you weren't seeing the new warning about resources being
loaded via ClassLoader instead of being registered in the .gwt.xml file and
loaded via ResourceOracle?


> I will try to keep using this, and report any other findings.
>
> Keep up the great work guys, GWT development is going to get so much
> cooler. :)
> Looking forward to the official release
>
Great! Any bugs/repro cases you can report will help us get this to
release-worthy, sooner.

>
>
> --
> You received this message because you are subscribed to the Google Groups
> "GWT Contributors" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/google-web-toolkit-contributors/f300a560-19e8-44bd-ba39-b2e48abb8522%40googlegroups.com
> 
> .
>
> For more options, visit https://groups.google.com/d/optout.
>

-- 
You received this message because you are subscribed to the Google Groups "GWT 
Contributors" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAFw3gJ_%2BMPO3eWemLf6OBqO5W8KMoPeMrKGktgm2UMiwZa7cAQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.