I was reluctant at first to move over to SDM, but after some time with it,
I got used to it. I combine it with SDBG in eclipse and it works mostly ok.
I don't need to go in the debugger that often and the moments that I really
needed it with the old Dev Mode was because of some browser specific
>
> I was reluctant at first to move over to SDM, but after some time with it,
> I got used to it. I combine it with SDBG in eclipse and it works mostly ok.
>
What is exactly not woking well with the SDBG eclipse plugin?
And why is this working well in IntelliJ ?
What SDM brings is much faster
I don't think GWT has to do anything special for Shadow DOM support.
You might need to include the webcomponents.js (full Shadow DOM) or
webcomponents-lite.js (ShadyDOM) polyfills [1] for browser that don't
support native ShadowDOM.
Then you can use the gwt-polymer-elements [2] Polymer library
Hello,
I came across GWT when I was looking for a way to use a large java math
library on the client with javascript. GWT may be targeted as building web
apps from the ground up using java rather than porting large existing java
libraries but from what I see there have been such ports
Hello,
well, in my opinion "porting large existing java libraries" is one of the
strengths of GWT and in my experience it works really well in this.
Were to find informations.
Well, JSInterop is the way for the part "use the exposed, public classes
from Javascript."
Yes,
in the specific case of the post we essentially 'nullified' the referenced
parts of java.io and left some alert just in case we will end trying to use
it (IIRC).
Reading a file from a browser is somewhat different than in a jvm and you
probably need to work on the library itself (and
A new stable Crux Framework version is available. Crux 5.4 was released
today and brings a lot of bug fixes and nice features. One of them is the
new data binding model, similar to AngularJS but better because it is
processed at compile time. We invite all of you to take a look at our MVC
On Friday, December 18, 2015 at 10:37:59 AM UTC-5, Alberto Mancini wrote:
>
> Hello,
> well, in my opinion "porting large existing java libraries" is one of the
> strengths of GWT and in my experience it works really well in this.
>
> Were to find informations.
>
> Well, JSInterop is the way
Replying to myself to collect some info:
Seems to be a use case for jsinterop:
https://docs.google.com/document/d/10fmlEYIHcyead_4R1S5wKGs1t2I7Fnp_PaNaa7XTEk0/edit#
relevant posting:
Hi,
I'm trying to use GWT storage, to store objects locally.
The com.google.gwt.storage.client.Storage , only stores string. How do i
store objects?
TIA.
RK,
--
You received this message because you are subscribed to the Google Groups "GWT
Users" group.
To unsubscribe from this group and
The browser only offers storing String keys / values in local storage. That
means you need to serialize objects somehow. JavaScriptObject / AutoBeans
can easily be converted to a JSON string. Otherwise you probably need a
library, something like https://github.com/nmorel/gwt-jackson
-- J.
--
https://github.com/seanchenxi/gwt-storage is a nice choice. I had a small
issue when upgrading to GWT 2.8.0-beta with the Long type, but nothing that
can easily be fixed.
--
You received this message because you are subscribed to the Google Groups "GWT
Users" group.
To unsubscribe from this
12 matches
Mail list logo