>
> "Swing approach", as in javax.swing, i.e. build a UI once and run it
> everywhere, with theming to try to blend it with the platform.
> "native UI" as in Android's android.widget.Button vs. Cocoa's NSButton or
> UIKit's UIButton, vs. WPF's System.Windows.Controls.Button vs. HTML's
> , i.e.
On Saturday, May 20, 2017 at 2:05:22 AM UTC+2, Learner Evermore wrote:
>
>
>>
> In our opinion, the "Swing" approach leads to an Uncanny Valley effect,
>> and the best approach is to use "native" UI for each platform.
>>
>
> I am not sure what do you mean by "Swing approach". Maybe you are
On Sunday, May 21, 2017 at 7:04:19 AM UTC-4, Paul Stockley wrote:
>
> I am really interested to hear how you can make a version of GWT RPC as
> fast as a pure JSON approach. We take a tree of thousands of objects and
> just use one JSON.parse / JSON.stringify call to deserialize / serialize
>
I am really interested to hear how you can make a version of GWT RPC as
fast as a pure JSON approach. We take a tree of thousands of objects and
just use one JSON.parse / JSON.stringify call to deserialize / serialize
which happens within the browser in C++ code. No other processing is
