Hi,
I am aware of native (JSNI) approach doing this. Involves attaching
unload listener to window. This triggers both on refresh or hard
navigation to different url.
public final class MyRefreshListener {
public static void onUnload() {
detachOnUnloadListener();
// Do your
Hi,
Downloaded GWT 2.1 distribution and recompiled one of our mid-sized
(~1500 classes) Web apps, which is developed against 2.0 version.
Compilation time has not changed. I managed to get the same timing
However I see a significant increase in resulting obfuscated
JavaScript size.
The total size
There is a project called swfupload-gwt, which embeds multi-file
upload capabilities into gwt application.
We are using that in several applications, so it is quite stable.
Without Flash you can opt for HTML5 upload, which also supports multi-
file selection.
I will rephrase a bit...
By default each browser tab shares same session if you are using
Cookie based sessions (which are in turn default on most of the Web
containers).
In IE6 there where no tabs to my knowledge and that's why it is
impossible to implement session sharing for this browser.
One
To my knowledge the adoption rate is increasing constantly. Three
years ago only enthusiasts heard of that framework. Today, every
decent developer coming to interview either heard or used GWT in a
project or prototype. But this could be only our local situation.
GWT main limitation right now is
Hello,
Wanted to share an approach we are using in large scaled enterprise
level applications since GWT 1.4 and up to now.
http://buzdin.blogspot.com/2010/05/gwt-dynamic-model.html
Would be great to know opinion of the community on the Dynamic Model
(Generic Transfer Object) approach and
Hi,
Please share your HTTP headers for cache.html.
Also check your GZIP filter if it is not overriding some of the
settings already set by cache filter.
Dmitry
On Nov 23, 1:04 pm, pepgrifell pepgrif...@gmail.com wrote:
Hi,
the problem is that *.css,*.js and images are cached but the only
Hello Alexey,
Unfortunately this is a typical situation in large GWT application
which uses a lot of custom Widgets and DOM/native code.
We have found no tooling which would efficiently show us the exact
places of memory leaks and the only approach left is to cut you
application into two halves
