GWT itself hasn't changed substantially in many years - improvements have
mostly been language features, adding support for incremental compilation,
the jsinterop system, etc, so for the most part the optimizations haven't
changed.
That said, the best way is almost certainly to take a look at
Is there an up-to-date documentation of optimisations the compiler applies?
An older page [1] discusses some topics but it isn't clear what of that has
been implemented.
(apologies for posting here, I asked this question on the user forum [2]
but didn't get any replies)
[1]
hi,
I have a GWT web app that I would like to make more reactive by moving some
heavy computation code into web workers. This code doesn't need the context
of the application to run, I just need to pass it a few input parameters so
it should be a good fit for a web worker.
I see how the web
Hmm, we've got client and server code in separate packages, but I don't
know exactly what the configuration would look like for separate project
classpaths. If you feel like having a peek with me over a zoom call to look
further, let me know!
On Wednesday, September 30, 2020 at 1:06:10 PM
Yes, you're right I wrote bad unit tests I updated im my repo with better
unit tests:
https://github.com/lofidewanto/jsinterop-simple-example/blob/master/src/test/java/com/github/lofi/CalculatorTest.java
Thanks!
deja...@googlemail.com schrieb am Donnerstag, 1. Oktober 2020 um 16:02:02
UTC+2:
You better ask here, this is a special chat for GWT Material Design:
https://gitter.im/GwtMaterialDesign/gwt-material
All the experts of GWT Material Design are there in the Gitter Channel
pierre...@gmail.com schrieb am Donnerstag, 1. Oktober 2020 um 17:41:30
UTC+2:
> Hi,
> I am using
Hi,
I am using MaterialSearch component
https://gwtmaterialdesign.github.io/gwt-material-demo/#search
This component displays the SearchObject list when the keyword contains the
user's text field.
Is there a way to change this behavior?
Typically, I would like by typing "black cat" to obtain
Am Mi., 30. Sept. 2020 um 22:48 Uhr schrieb lofid...@gmail.com <
lofidewa...@gmail.com>:
>
> The check on page 42 is about the "values", so the input param
>
>
The null check assumes that "values" can be null. If it is null you will
get a NullPointerException before this check takes place
There are performance implications (AFAICT) but you should be able to
access all arguments through Js.arguments().
…or you could use your own Promise interface mapping to their specific API.
On Thursday, October 1, 2020 at 11:58:56 AM UTC+2, Elhanan wrote:
>
> hi...i'm consuming cockpit api
If you want a fast answer, go to https://gitter.im/gwtproject/gwt
All the experts are over there...
Elhanan schrieb am Donnerstag, 1. Oktober 2020 um 11:58:56 UTC+2:
> hi...i'm consuming cockpit api promises, but it would seem they are using
> a non standard form which i cannot use with
... because IMO the weak point of GWT / J2CL today is the JsInterop
implementation of all those JS libs... I always need to google to find it,
which is ok but it would be great to be able to see what JS libs we already
have as JsInterop integrations...
lofid...@gmail.com schrieb am Donnerstag,
hi...i'm consuming cockpit api promises, but it would seem they are using
a non standard form which i cannot use with elemental2
https://github.com/cockpit-project/cockpit/issues/14682
their fail method returns multiple paramters, which elemental2 doesn't
have.
so they recommended using done
Hi Thomas,
thanks for the clue... yeah something like "awesome gwt" but like you said
we already have it. I know this one https://gwt.zeef.com/awesomegwt (great
links collection) and I already put this in GWT Padlet --> "GWT Links
Collection"
I thought it is just a simple one pager "Only
yes, that would be also a very good way... Thanks for the tip Thomas.
t.br...@gmail.com schrieb am Donnerstag, 1. Oktober 2020 um 09:54:25 UTC+2:
>
>
> On Wednesday, September 30, 2020 at 9:58:33 PM UTC+2, lofid...@gmail.com
> wrote:
>>
>> Yes, this is nice, since GWT home page is developed (in
On Wednesday, September 30, 2020 at 10:48:34 PM UTC+2, lofid...@gmail.com
wrote:
>
> Thanks a lot for the info.
>
> I added the Gradle plugin, wow we have 3 Gradle plugins is it not
> better just to have one?
>
> The check on page 42 is about the "values", so the input param
>
> I will
On Wednesday, September 30, 2020 at 9:58:33 PM UTC+2, lofid...@gmail.com
wrote:
>
> Yes, this is nice, since GWT home page is developed (in small part) with
> GWT...
>
> To the Debugging with Chrome:
>
>- Actually you still could read the variable name because it is
>readable... and
First of all, when updating GWT SDK you should delete your gwtUnitCache
directory. Historically there has always been some hiccups with the cache
when upgrading GWT. By deleting it you make sure to start a fresh compile
without any cached information.
If that does not help you should take the
17 matches
Mail list logo
