{var%20f='http://v.t.sina.com.cn/share/share.php?appkey=1515056452',u=z||d.location,p=['&url=',e(u),'&title=',e(t||d.title),'&source=',e(r),'&sourceUrl=',e(l),'&content=',c||'gb2312','&pic=',e(p||'')].join('');function%20a(){if(!window.open([f,p].join(''),'mb',['toolbar=0,status=0,resizable=1,width=440,height=430,left=',(s.width-440)/2,',top=',(s.height-430)/2].join('')))u.href=[f,p].join('');};if(/Firefox/.test(navigator.userAgent))setTimeout(a,0);else%20a();})(screen,document,encodeURIComponent,'','','https://www.manongdao.com/data/attach/logo/logo.png', '推荐 祖国的老花朵 的问题《GWT Super Dev Mode》','https://www.manongdao.com/q-714193.html','页面编码gb2312|utf-8默认gb2312'));){kind=link}
I am very concerned for this new alternative for development life-cycle. Actually by this feature we are compiling Java file to Js in a super draft mode but what happens for very large projects that normal compilation takes over 45min (my last project) ?! every time I change something in UI I should recompile all codes?!
Optimistic speaking, it should take over 5mins to recompile in super mode!
Please let me know if I am wrong. Regads,
The difference between SuperDevMode and compiling in draft mode is that SuperDevMode uses a resident compiler, so it doesn't start from scratch when it needs to recompile your app. SuperDevMode also only compiles one permutation (the one that your browser will use).
That said, compilation is still monolithic. In the next version, GWT will introduce incremental compilation: modules will be pre-compiled on their own, so modules that don't change don't need to be recompiled and only need to be "linked" with the others to produce the final JS.