如果基本的，样本GWT应用程序需要30秒的浏览器加载，是正常的吗？将真正的应用程序需要2分钟？ [英] if basic, sample GWT app takes 30sec to load in browser, is that normal? will real apps take 2 mins?

问题描述

我已经能够运行64位Windows 7那么怎么来的任何时候我停止的发展模式，编辑和重新启动需要30秒，在浏览器成为响应一个小样本GWT应用程序的一个体面的机器，无论是在最新的Firefox和最新的Chrome？

I have a decent machine capable of running 64 bit Windows 7. So how come any time I stop a small sample GWT app in "development mode", edit it and restart it it takes 30 sec to become responsive in the browser, both in latest Firefox and latest Chrome?

时的那种基于糖蜜 - 编辑 - 编译循环只是正常的，预计GWT开发的东西越来越大呢？

Is that sort of molasses-based edit-compile cycle just the normal, expected thing for GWT developers nowadays?

它会得到更真实的应用更糟糕或者是整个这30秒的只是框架的开销，和我自己的code不会让它变得比这更臃肿任何时间很快？

Will it get much worse for more realistic apps or is the whole of those 30 sec just the framework overhead, and my own code would not make it much more bloated than that any time soon?

能否这一问题通过使用一些其他的模式或以任何其它TWEAK的解决方案可缓解？

Can this problem be alleviated by using some other "mode" or by whatever other tweak solution?

做谷歌的人有更快的机器比我好上，这是少了痛苦或做他们遭受像我们其他人呢？

Do Google people have much faster machines than I do on which this is less of a pain or do they suffer like the rest of us?

推荐答案

我想我的答案是一个问题的形式，你确定你真的需要不惜一切重新开始吗？

I guess my answer is in the form of a question, "Are you sure you're really needing to restart at all?"

假设你正在运行它主办的浏览器（这听起来像你是），那么大多数的变化是热几乎就在你完成他们之内。我昨天花了做各种变化的主要code文件的模块中，并没有重新启动服务器的任何人。

Assuming you're running it hosted within the browser (which it sounds like you are) then most changes are "hot" almost as soon as you've finished them. I spent yesterday doing all kinds of changes to the main code file in a module and didn't have to restart the server for any of them.

我经常不得不重新加载浏览器中的网页看到的变化，但是这是一个不同的问题。

I often had to reload the page within the browser to see the changes, but that's a different issue.

这篇关于如果基本的，样本GWT应用程序需要30秒的浏览器加载，是正常的吗？将真正的应用程序需要2分钟？的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！