Thanks for sharing. Very interesting!
Is this issue still around with the latest version of GWT and IE?
On Monday, September 26, 2011 12:29:15 PM UTC+2, Rokesh Jankie wrote:
Hi All,
I've been working on GWT for a while now and noticed something important
and peculiar.
In GWT you code in
Hello can someone please help complete this sample. Maybe it is obvious to
everyone out there but me but
callback c=createCallback();does not seem to work. Exactly how do I
instantiate my call back.
Do I have to
static AsyncCallbackMYOBJECT myCallback=null;
private AsyncCallbackMYOBJECT
You have a static variable that is instantiated when its needed (lazy
instantiation).
private static AsyncCallbackPerson findPersonCallback;
private AsyncCallbackPerson createFindPersonCallback() {
if(findPersonCallback == null) {
findPersonCallback = new AsyncCallbackPerson() {
Hi All,
I've been working on GWT for a while now and noticed something important and
peculiar.
In GWT you code in Java and almost automatically assume Java garbage
collection (because that's how you code).
In this code sample:
Thanks for share!!!
2011/9/26 Rokesh rjan...@gmail.com
Hi All,
I've been working on GWT for a while now and noticed something important
and peculiar.
In GWT you code in Java and almost automatically assume Java garbage
collection (because that's how you code).
In this code sample:
interesting,
Would it be possible to implement this optimization at the compiler level,
so that programmers don't have to care about this? I mean, only on the IE
permutations, or for all permutations if it doesn't have negative effects on
other browsers
Not something specific to callback, but
so just to understand just replace anonymous in call callback with a
variable will fix the problem ?
instead of:
call(new callback(){});
use :
callback c = new callback(){};
call(c);
?
On Sep 26, 1:29 pm, Rokesh rjan...@gmail.com wrote:
Hi All,
I've been working on GWT for a while now and
Almost there...
method doSomething (){
callback c = createCallback();
}
static AsyncCallback? callback = null;
AsyncCallback? createCallBack(){
if (callback==null){
callback = new AsyncCallbackObject() {
// implement onSuccess
// implement
Interresting. But in this case, is not it the same problem for all anonymous
classes ?
Do not you have this problem with event handler ?
myButton.addClickHanler(new ClickHandler() {
public void onClick(ClickEvent e) {...}
}
2011/9/26 Rokesh Jankie rjan...@gmail.com
Almost there...
method
No definitely not: This is only with the callback Class (and in combination
with a lot of data).
Somehow the callback is not garbage collected properly in IE.
The GWT team covered this part (of (new ClickHandler)...)
See this link
10 matches
Mail list logo
