Hi guys, I've been following your issue for this, Brian, with hopes somebody is pained enough by this as I (and Gal) is by this issue.
My dev experience is excruciating with this issue as it stands, so I'm willing to try and patch it if somebody could point me in the right direction. Is this a GWT compiler thing, or part of the IncrementalGenerator for SuperDevMode, or is it a short coming in the custom generator itself? My app is built using Mvp4g so my specific question is - is the bug in GWT/SDM, or Mvp4g's generator? Thanks! On Tuesday, June 12, 2012 2:55:41 PM UTC-4, Brian Slesinsky wrote: > > I haven't done anything special to try to make this work, but it sounds > like a nice performance win. I created an issue for this: > > > http://code.google.com/p/google-web-toolkit/issues/detail?id=7422&thanks=7422&ts=1339527186 > > On Thursday, June 7, 2012 6:25:20 AM UTC-7, Gal Dolber wrote: >> >> Are IncrementalGenerators working on the SuperDevMode? >> >> I'm trying to make my gwt generators cacheable, and everything is working >> on DevMode, but when running on SuperDevMode >> context.isGeneratorResultCachingEnabled() is always false. >> >> Right now the biggest project I have is taking 35s to refresh on >> SuperDevMode(when it takes a few seconds on DevMode). And I'm hoping this >> will speed up things. >> >> Any help is appreciated >> >> -- >> Guit: beautiful gwt applications >> >> https://github.com/galdolber/Guit >> >> >> >> >> -- 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/-/_k8gD6rkMykJ. To post to this group, send email to google-web-toolkit@googlegroups.com. To unsubscribe from this group, send email to google-web-toolkit+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
