Re: Autoboxing
Please excuse my ignorance, I'm surprised to see the emulator code is Java. I'd have thought it would be in JavaScript. Is the point that the emulator is Java that the translator can handle? I wonder what Integer.valueOf looks like in JavaScript? Perhaps by explicitly writing Integer.valueOf I am forcing the creation of additional JavaScript that would otherwise be omitted as unnecessary?! (I'm well aware of the premature optimisation adage. If by arming yourself with a little knowledge you can avoid writing code that you know might harm performance without sacrificing readability or implementation time, that has to be a good thing.) On Sep 12, 10:56 pm, Thomas Broyer t.bro...@gmail.com wrote: Generally speaking, it's a waste of time to worry about performance implications of such small things until you've proven that it's a performance issue for your app. Choose the right type for the job, and forget about autoboxing implications until it comes knocking at the door. “premature optimization is the root of all evil” — Donald Knuth Seehttp://en.wikipedia.org/wiki/Program_optimization#When_to_optimize FYI, Integer.valueOfhttp://code.google.com/p/google-web-toolkit/source/browse/trunk/user/...is not trivial, but I believe there are many other places in your app (and unfortunately within GWT itself) that needs to be optimized before thinking about autoboxing; starting with DOM manipulation, which is awfully slow in many browsers (much slower than creating a new JS object that wraps a number). -- 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.
Autoboxing
Doe the fact that my client side Java code gets compiled into JavaScript mean that it's a waste of time to worry about possible performance problems caused by autoboxing? -- 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.
Re: Eclipse Analyzing Sources Slow
Hmm, all I can suggest is that you try the XML Catalog workaround. On Jul 31, 12:22 am, Alex Luya alexander.l...@gmail.com wrote: I have installed this one,but problem still existed. On Thu, 2011-07-28 at 20:30 -0700, gutto wrote: Pulled down an update for GPE today. Google Plugin for Eclipse 3.7 2.3.3.r37v201107211953 com.google.gdt.eclipse.suite.e37.feature.feature.group Google, Inc. Problem appears to have disappeared! On Jul 29, 11:27 am, gutto thomas.gutteri...@gmail.com wrote: Thanks, that's interesting. Obviously related. I had noticed that content assist in templates is slow the first time I tried to use it. I was quite pleased to see that in Indigo it will actually auto- complete, whereas in Helios it did nothing when I selected an entry from the suggestion list. On Jul 26, 8:17 pm, Thomas Broyer t.bro...@gmail.com wrote: They did:http://code.google.com/p/google-web-toolkit/issues/detail?id=5265 Maybe not that many times, and *a priori* not at the same time (not when building the project, but when opening the XML files), but still. -- 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.
Re: Eclipse Analyzing Sources Slow
Thanks, that's interesting. Obviously related. I had noticed that content assist in templates is slow the first time I tried to use it. I was quite pleased to see that in Indigo it will actually auto- complete, whereas in Helios it did nothing when I selected an entry from the suggestion list. On Jul 26, 8:17 pm, Thomas Broyer t.bro...@gmail.com wrote: They did:http://code.google.com/p/google-web-toolkit/issues/detail?id=5265 Maybe not that many times, and *a priori* not at the same time (not when building the project, but when opening the XML files), but still. -- 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.
Re: Eclipse Analyzing Sources Slow
Pulled down an update for GPE today. Google Plugin for Eclipse 3.7 2.3.3.r37v201107211953 com.google.gdt.eclipse.suite.e37.feature.feature.group Google, Inc. Problem appears to have disappeared! On Jul 29, 11:27 am, gutto thomas.gutteri...@gmail.com wrote: Thanks, that's interesting. Obviously related. I had noticed that content assist in templates is slow the first time I tried to use it. I was quite pleased to see that in Indigo it will actually auto- complete, whereas in Helios it did nothing when I selected an entry from the suggestion list. On Jul 26, 8:17 pm, Thomas Broyer t.bro...@gmail.com wrote: They did:http://code.google.com/p/google-web-toolkit/issues/detail?id=5265 Maybe not that many times, and *a priori* not at the same time (not when building the project, but when opening the XML files), but still. -- 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.
Re: Eclipse Analyzing Sources Slow
Over the weekend my build times have reduced! Perhaps we were having some network issues which were exacerbating the problem. However, it's still slow. I have tracked the cause down to repeated requests for the DTD document http://dl.google.com/gwt/DTD/xhtml.ent that is referenced by each UI Binder templates. I have 80 XML template files and the DTD doc is request 178 times during a clean build. The workaround I have found is to download and store this document locally and add it to the Eclipse XML Catalog. Doing this reduces my build time from approx. two minutes to under 15 seconds. Wouldn't it be sufficient to fetch such things once per build? Would be interesting to know if the previous GPE and Helios request this DTD so many times. (I used Wireshark to watch what was going on.) On Jul 23, 1:18 am, Ionuț G. Stan ionut.g.s...@gmail.com wrote: I've had the same problem and the times improved a bit after downgrading to Eclipse Helios. It seems there are some problems with Indigo. On Jul/22/2011 14:36, Alex Luya wrote: Same problem here,even reusing old workspace On Jul 22, 6:55 am,guttothomas.gutteri...@gmail.com wrote: Hi Has anyone ever encountered the analyzingsources stage of an eclipse build taking an inordinately long time? It seems to be required each time I make a change to the dependencies of the project. It takes roughly 5 minutes, which is unacceptable. Does anyone know what is happening during this stage? I'm assuming its building Eclipse metadata or something. Can you suggest what I might try to find the cause of the slow running? Eclipse Indigo (3.7), Google Plugin for Eclipse 3.7, GWT SDK 2.3.0, OpenJDK 1.6.0_22, Ubuntu 11.04 x84_64, Thanks -- Ionuț G. Stan | http://igstan.ro -- 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.
Eclipse Analyzing Sources Slow
Hi Has anyone ever encountered the analyzing sources stage of an eclipse build taking an inordinately long time? It seems to be required each time I make a change to the dependencies of the project. It takes roughly 5 minutes, which is unacceptable. Does anyone know what is happening during this stage? I'm assuming its building Eclipse metadata or something. Can you suggest what I might try to find the cause of the slow running? Eclipse Indigo (3.7), Google Plugin for Eclipse 3.7, GWT SDK 2.3.0, OpenJDK 1.6.0_22, Ubuntu 11.04 x84_64, Thanks -- 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.
