For what it's worth, as a Redux maintainer I can assure you that Redux is
very stable and not going to meaningfully change (at least at the API
level) from here on out :)
On Sunday, April 30, 2017 at 8:27:10 AM UTC-4, Paul Stockley wrote:
>
> I have just released a new version of the GWTReact
I built an app using GWT and GWT-RPC in 2011-2012, but am currently working
on a clean-slate rewrite of the client using modern JS (ES6, React,
Webpack, etc). I've opted to leave the existing client codebase entirely
as-is, and have exposed my existing backend APIs over JSON-RPC as well.
Really stupid question: do you have a typo'd 'r' after the open curly?
It's there in your pasted code snippet, and with JS's automatic semicolon
insertion, I'm pretty sure it would try to use it as if you'd written
r;.
Also, yes, I think you'd want to use $wnd.ActualJSObjectName.
On
Cool, glad that was an easy fix.
Yeah, this is a good approach. See https://github.com/richkadel/cesium-gwt
for a larger-scale use of this technique for wrapping the Cesium.js 3D
globe library.
On Monday, February 9, 2015 at 5:30:45 PM UTC-5, rjcarr wrote:
Ha, not a stupid question at all
There's two general approaches:
1) Write large JSNI methods that do all the interaction in Javascript
2) Use GWT's JavaScriptObject, subclass the library's objects, and write
small JSNI methods that wrap individual methods of the JS object.
There's supposed to be better JS interop coming in GWT
Some thoughts on using SmartGWT:
* The SmartGWT developers are VERY insistent that you should develop your
application using their APIs and structure, as otherwise you are wasting
time and duplicating effort they've already put in. To be fair, they do
have a bit of a point in that they have
this affect compilation time?
Mark Erikson
On Wednesday, July 17, 2013 4:56:40 PM UTC-4, Alex Epshteyn wrote:
Dear fellow GWT users,
I would like to announce that I have finally solved what I always thought
to be GWT's greatest weakness: its lack of debugging information for
client-side
If you use emulated stack traces (including line numbers) in current GWT
your app size will roughly increase by 100%. So 45% is a lot better of what
GWT gives you today.
...
Really. I had not seen that mentioned anywhere. What sort of approach
does the current emulated stack
I've actually seen similar behavior in Firefox 17 ESR. I wound up
implementing the following horribly disgusting hack as a workaround:
myRPCInterface.logOut(new AsyncCallbackBoolean() {
public void onFailure(Throwable caught)
{
}
public
