Thank you
On Jan 27, 1:34 pm, Thomas Broyer wrote:
> On Jan 27, 2:22 am, dmen wrote:
>
> > How future proof are GWT compilations? For example, if I compile my
> > app today with 2.0:
>
> > 1. How it will react in a couple of years to lets say IE 9, Firefox 4,
> > etc.?
>
> > 2. How it will react
On Jan 27, 1:49 pm, Grant wrote:
> "you can define a "callback error
> function" though to have some JavaScript run in this eventuality"
>
> Do you have a link to how to define the callback mentioned above?
It's gwt:onPropertyErrorFn that you can find in the *.nocache.js
template:
http://code.g
"you can define a "callback error
function" though to have some JavaScript run in this eventuality"
Do you have a link to how to define the callback mentioned above?
Thanks
Grant
On Jan 27, 11:34 am, Thomas Broyer wrote:
> On Jan 27, 2:22 am, dmen wrote:
>
> > How future proof are GWT compila
I didn't know about the "callback error function".
How/where can I register such a callback?
On 27 Jan., 12:34, Thomas Broyer wrote:
> On Jan 27, 2:22 am, dmen wrote:
>
> > How future proof are GWT compilations? For example, if I compile my
> > app today with 2.0:
>
> > 1. How it will react in
On Jan 27, 2:22 am, dmen wrote:
> How future proof are GWT compilations? For example, if I compile my
> app today with 2.0:
>
> 1. How it will react in a couple of years to lets say IE 9, Firefox 4,
> etc.?
>
> 2. How it will react to a yet unknown, however standards compatible,
> browser?
It a
How future proof are GWT compilations? For example, if I compile my
app today with 2.0:
1. How it will react in a couple of years to lets say IE 9, Firefox 4,
etc.?
2. How it will react to a yet unknown, however standards compatible,
browser?
--
You received this message because you are subscri
