some quick tips:
1. Hardware: U need to increase your CPU power over memory. Adding
gigs of ram is not going to help much. Instead use dual/quad
processors with higher configurations. Also use a faster HD and a
higher FSB(try to match with your RAM speed).
2. Compile for one browser using user-agent mentioned earlier.
3. Code design! This is the biggest area where you can speed things
up. Use lazy initialization in every possible class. There are many
threads that explain this concept. I will give you a quick example:
public class MyPopup extends DialogPanel{
public DialogPanel(){
...
}
private void initialized = false;
private void init(){
setWidget(createWidget());
}
@Override
public void show(){
if (!initialized){
init();
initialized = true;
}
}
}
With the current GWT toolkit #3 is your key to significantly reduce
the load time. It also makes your application design better.
Rakesh Wagh
On Nov 7 2008, 5:06 pm, surfer <lorenzo.naza...@gmail.com> wrote:
> since often the main development of an application is viewed and
> debugged with one single type of browser and only sometimes verified
> on the others, does anybody know if it's possible to force GWT
> compiler to build javascript code for just one single target browser,
> in order to increase compiling phase performance ?
>
> thanx
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Google Web Toolkit" group.
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
-~----------~----~----~----~------~----~------~--~---
