vampie wrote:Switching source and design page ( on big projects ) sometimes can be pain.
So can compiling and launching a GWT app using hosted mode. Especially the first time you switch to Design mode during a session, quite a bit of GWT compilation needs to take place and GWT hosted mode needs to be initialized. It should be faster after that, but ultimately it is gated by the speed of GWT itself. If you have a project that takes a long time to launch in hosted mode, it will take a long time to initially open in design mode. In fact, due to some optimizations that we make, we should be able to switch to design mode faster than GWT can launch hosted mode.
vampie wrote:Where is the bottleneck ? CPU bound or Disk IO bound? or both?
It is CPU and memory bound. After a couple of edit cycles all the needed information will be in the cache in any case, so disk speed is not so important. GWT hosted mode start up is performed in the SWT main thread, without parallelization, so, right now a CPU with 2 fast cores is better than a CPU will 4 cores but at lower speed. The more memory you can assign to Eclipse, the better. In any case, you can monitor your system during opening the Design page using, for example, the Windows "Resource Monitor" from the Task Manager (I'm sure there is something similar for Linux as well).
vampie wrote:what is your opinion?
Commercial software should be paid for rather than being borrowed indefinitely.