Re: New Presentation about Modern GWT Webapp Development

2020-10-21 Thread Slava Imeshev 
Lofi, This is great, thank you for getting this together. 

On Tuesday, October 20, 2020 at 3:42:59 AM UTC-7 lofid...@gmail.com wrote:

> I added the "heart" ❤️ symbol to show that the libs / frameworks still 
> being supported... I tried to add all the hearts in which libs I know...
>
> If you want to add the heart just follow the two ways I mentioned in the 
> beginning:
> https://github.com/gwtboot/gwt-boot-awesome-lili
>
> All the supported libs / frameworks are always in the beginning of the 
> category...
> Hope to get more libs / frameworks for GWT / J2CL 
> lofid...@gmail.com schrieb am Montag, 19. Oktober 2020 um 22:48:24 UTC+2:
>
>> Hi All, 
>>
>> I changed the name of the repo for the GWT Awesome LiLi: 
>>
>> https://github.com/gwtboot/gwt-boot-awesome-lili
>>
>> PR and MR are very welcome! 
>>
>> Lofi
>> lofid...@gmail.com schrieb am Sonntag, 18. Oktober 2020 um 21:32:20 
>> UTC+2:
>>
>>> I open a new GitHub project for putting every GWT libs I know sofar...
>>>
>>> Library List (LiLi):
>>> https://github.com/gwtboot/gwt-boot-jsinterop-lili
>>>
>>> If you have libs I don't know just open a PR / MR...
>>>
>>> Thanks,
>>> Lofi
>>> lofid...@gmail.com schrieb am Donnerstag, 1. Oktober 2020 um 11:58:29 
>>> UTC+2:
>>>
 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 Libs" table with 
 following content:

 *Category / JS Lib Name / JS Lib Address / GWT Lib Name / GWT Lib 
 Address / JsInterop or JSNI*

 Example:

 maps / open-layers3 / https://openlayers.org / gwt-ol / 
 https://github.com/TDesjardins/gwt-ol / JsInterop
 diagrams / chart.js / https://www.chartjs.org / charba / 
 https://github.com/pepstock-org/Charba  
 / JsInterop
 diagrams / highchart.js / https://www.highcharts.com / gwt-highcharts 
 / https://github.com/ascendtech/gwt-highcharts / JsInterop
 ...

 That's it., so we can see whether someone already did the work with 
 JsInterop (analogy to DefinitelyTyped for the types in TS).
 And everyone could make a PR to update the one page...

 Is it worth it to try?

 t.br...@gmail.com schrieb am Donnerstag, 1. Oktober 2020 um 10:00:10 
 UTC+2:

>
>
> 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 create a new GWT libs list project to have a list of all GWT 
>> libs available... so not only UI framework... and will put everything 
>> over 
>> there... hope that the community will make some PR, so we can have a lot 
>> of 
>> libs...
>>
>
> Some kind of "awesome gwt" then? 
> https://github.com/sindresorhus/awesome
> Fwiw, a Google search for "awesome gwt" returned 
> https://awesomeopensource.com/projects/gwt and 
> https://gwt.zeef.com/awesomegwt
>
>

-- 
You received this message because you are subscribed to the Google Groups "GWT 
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit/54c62925-68ee-4591-964c-970b1023b408n%40googlegroups.com.

Re: New Presentation about Modern GWT Webapp Development

2020-10-20 Thread lofid...@gmail.com 


I added the "heart" ❤️ symbol to show that the libs / frameworks still 
being supported... I tried to add all the hearts in which libs I know...

If you want to add the heart just follow the two ways I mentioned in the 
beginning:
https://github.com/gwtboot/gwt-boot-awesome-lili

All the supported libs / frameworks are always in the beginning of the 
category...
Hope to get more libs / frameworks for GWT / J2CL 
lofid...@gmail.com schrieb am Montag, 19. Oktober 2020 um 22:48:24 UTC+2:

> Hi All, 
>
> I changed the name of the repo for the GWT Awesome LiLi: 
>
> https://github.com/gwtboot/gwt-boot-awesome-lili
>
> PR and MR are very welcome! 
>
> Lofi
> lofid...@gmail.com schrieb am Sonntag, 18. Oktober 2020 um 21:32:20 UTC+2:
>
>> I open a new GitHub project for putting every GWT libs I know sofar...
>>
>> Library List (LiLi):
>> https://github.com/gwtboot/gwt-boot-jsinterop-lili
>>
>> If you have libs I don't know just open a PR / MR...
>>
>> Thanks,
>> Lofi
>> lofid...@gmail.com schrieb am Donnerstag, 1. Oktober 2020 um 11:58:29 
>> UTC+2:
>>
>>> 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 Libs" table with following 
>>> content:
>>>
>>> *Category / JS Lib Name / JS Lib Address / GWT Lib Name / GWT Lib 
>>> Address / JsInterop or JSNI*
>>>
>>> Example:
>>>
>>> maps / open-layers3 / https://openlayers.org / gwt-ol / 
>>> https://github.com/TDesjardins/gwt-ol / JsInterop
>>> diagrams / chart.js / https://www.chartjs.org / charba / 
>>> https://github.com/pepstock-org/Charba  
>>> / JsInterop
>>> diagrams / highchart.js / https://www.highcharts.com / gwt-highcharts / 
>>> https://github.com/ascendtech/gwt-highcharts / JsInterop
>>> ...
>>>
>>> That's it., so we can see whether someone already did the work with 
>>> JsInterop (analogy to DefinitelyTyped for the types in TS).
>>> And everyone could make a PR to update the one page...
>>>
>>> Is it worth it to try?
>>>
>>> t.br...@gmail.com schrieb am Donnerstag, 1. Oktober 2020 um 10:00:10 
>>> UTC+2:
>>>


 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 create a new GWT libs list project to have a list of all GWT 
> libs available... so not only UI framework... and will put everything 
> over 
> there... hope that the community will make some PR, so we can have a lot 
> of 
> libs...
>

 Some kind of "awesome gwt" then? 
 https://github.com/sindresorhus/awesome
 Fwiw, a Google search for "awesome gwt" returned 
 https://awesomeopensource.com/projects/gwt and 
 https://gwt.zeef.com/awesomegwt



-- 
You received this message because you are subscribed to the Google Groups "GWT 
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit/ef6ea9e1-e54f-4426-9799-450c3a1cb660n%40googlegroups.com.

Re: New Presentation about Modern GWT Webapp Development

2020-10-19 Thread lofid...@gmail.com 
Hi All, 

I changed the name of the repo for the GWT Awesome LiLi: 

https://github.com/gwtboot/gwt-boot-awesome-lili

PR and MR are very welcome! 

Lofi
lofid...@gmail.com schrieb am Sonntag, 18. Oktober 2020 um 21:32:20 UTC+2:

> I open a new GitHub project for putting every GWT libs I know sofar...
>
> Library List (LiLi):
> https://github.com/gwtboot/gwt-boot-jsinterop-lili
>
> If you have libs I don't know just open a PR / MR...
>
> Thanks,
> Lofi
> lofid...@gmail.com schrieb am Donnerstag, 1. Oktober 2020 um 11:58:29 
> UTC+2:
>
>> 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 Libs" table with following 
>> content:
>>
>> *Category / JS Lib Name / JS Lib Address / GWT Lib Name / GWT Lib Address 
>> / JsInterop or JSNI*
>>
>> Example:
>>
>> maps / open-layers3 / https://openlayers.org / gwt-ol / 
>> https://github.com/TDesjardins/gwt-ol / JsInterop
>> diagrams / chart.js / https://www.chartjs.org / charba / 
>> https://github.com/pepstock-org/Charba  
>> / JsInterop
>> diagrams / highchart.js / https://www.highcharts.com / gwt-highcharts / 
>> https://github.com/ascendtech/gwt-highcharts / JsInterop
>> ...
>>
>> That's it., so we can see whether someone already did the work with 
>> JsInterop (analogy to DefinitelyTyped for the types in TS).
>> And everyone could make a PR to update the one page...
>>
>> Is it worth it to try?
>>
>> t.br...@gmail.com schrieb am Donnerstag, 1. Oktober 2020 um 10:00:10 
>> UTC+2:
>>
>>>
>>>
>>> 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 create a new GWT libs list project to have a list of all GWT 
 libs available... so not only UI framework... and will put everything over 
 there... hope that the community will make some PR, so we can have a lot 
 of 
 libs...

>>>
>>> Some kind of "awesome gwt" then? https://github.com/sindresorhus/awesome
>>> Fwiw, a Google search for "awesome gwt" returned 
>>> https://awesomeopensource.com/projects/gwt and 
>>> https://gwt.zeef.com/awesomegwt
>>>
>>>

-- 
You received this message because you are subscribed to the Google Groups "GWT 
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit/93d43573-73e9-4a1a-adbd-afea240c17d6n%40googlegroups.com.

Re: New Presentation about Modern GWT Webapp Development

2020-10-18 Thread lofid...@gmail.com 
I open a new GitHub project for putting every GWT libs I know sofar...

Library List (LiLi):
https://github.com/gwtboot/gwt-boot-jsinterop-lili

If you have libs I don't know just open a PR / MR...

Thanks,
Lofi
lofid...@gmail.com schrieb am Donnerstag, 1. Oktober 2020 um 11:58:29 UTC+2:

> 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 Libs" table with following 
> content:
>
> *Category / JS Lib Name / JS Lib Address / GWT Lib Name / GWT Lib Address 
> / JsInterop or JSNI*
>
> Example:
>
> maps / open-layers3 / https://openlayers.org / gwt-ol / 
> https://github.com/TDesjardins/gwt-ol / JsInterop
> diagrams / chart.js / https://www.chartjs.org / charba / 
> https://github.com/pepstock-org/Charba  
> / JsInterop
> diagrams / highchart.js / https://www.highcharts.com / gwt-highcharts / 
> https://github.com/ascendtech/gwt-highcharts / JsInterop
> ...
>
> That's it., so we can see whether someone already did the work with 
> JsInterop (analogy to DefinitelyTyped for the types in TS).
> And everyone could make a PR to update the one page...
>
> Is it worth it to try?
>
> t.br...@gmail.com schrieb am Donnerstag, 1. Oktober 2020 um 10:00:10 
> UTC+2:
>
>>
>>
>> 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 create a new GWT libs list project to have a list of all GWT libs 
>>> available... so not only UI framework... and will put everything over 
>>> there... hope that the community will make some PR, so we can have a lot of 
>>> libs...
>>>
>>
>> Some kind of "awesome gwt" then? https://github.com/sindresorhus/awesome
>> Fwiw, a Google search for "awesome gwt" returned 
>> https://awesomeopensource.com/projects/gwt and 
>> https://gwt.zeef.com/awesomegwt
>>
>>

-- 
You received this message because you are subscribed to the Google Groups "GWT 
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit/cb8588db-8518-4173-ba5c-0eee1501e39an%40googlegroups.com.

Re: New Presentation about Modern GWT Webapp Development

2020-10-01 Thread lofid...@gmail.com 
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:

> Am Mi., 30. Sept. 2020 um 22:48 Uhr schrieb lofid...@gmail.com <
> lofid...@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 because of the 
> call Arrays.asList(). Simply putting the first statement in the if-body 
> will solve the problem.
>

-- 
You received this message because you are subscribed to the Google Groups "GWT 
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit/6fa92f4a-8c98-4fe1-b25c-2338dcb6ae28n%40googlegroups.com.

Re: New Presentation about Modern GWT Webapp Development

2020-10-01 Thread 'Tino D.' via GWT Users 
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 because of the
call Arrays.asList(). Simply putting the first statement in the if-body
will solve the problem.

-- 
You received this message because you are subscribed to the Google Groups "GWT 
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit/CA%2Bh_a83PsUXwty03tr6KEg0c7FCEbokjtroXqEu%3DgMqc%2B7kf_w%40mail.gmail.com.

Re: New Presentation about Modern GWT Webapp Development

2020-10-01 Thread lofid...@gmail.com 
... 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, 1. Oktober 2020 um 11:58:29 UTC+2:

> 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 Libs" table with following 
> content:
>
> *Category / JS Lib Name / JS Lib Address / GWT Lib Name / GWT Lib Address 
> / JsInterop or JSNI*
>
> Example:
>
> maps / open-layers3 / https://openlayers.org / gwt-ol / 
> https://github.com/TDesjardins/gwt-ol / JsInterop
> diagrams / chart.js / https://www.chartjs.org / charba / 
> https://github.com/pepstock-org/Charba  
> / JsInterop
> diagrams / highchart.js / https://www.highcharts.com / gwt-highcharts / 
> https://github.com/ascendtech/gwt-highcharts / JsInterop
> ...
>
> That's it., so we can see whether someone already did the work with 
> JsInterop (analogy to DefinitelyTyped for the types in TS).
> And everyone could make a PR to update the one page...
>
> Is it worth it to try?
>
> t.br...@gmail.com schrieb am Donnerstag, 1. Oktober 2020 um 10:00:10 
> UTC+2:
>
>>
>>
>> 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 create a new GWT libs list project to have a list of all GWT libs 
>>> available... so not only UI framework... and will put everything over 
>>> there... hope that the community will make some PR, so we can have a lot of 
>>> libs...
>>>
>>
>> Some kind of "awesome gwt" then? https://github.com/sindresorhus/awesome
>> Fwiw, a Google search for "awesome gwt" returned 
>> https://awesomeopensource.com/projects/gwt and 
>> https://gwt.zeef.com/awesomegwt
>>
>>

-- 
You received this message because you are subscribed to the Google Groups "GWT 
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit/73fd4fa3-ac62-4a89-a35a-4b2e2abc993cn%40googlegroups.com.

Re: New Presentation about Modern GWT Webapp Development

2020-10-01 Thread lofid...@gmail.com 
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 Libs" table with following 
content:

*Category / JS Lib Name / JS Lib Address / GWT Lib Name / GWT Lib Address / 
JsInterop or JSNI*

Example:

maps / open-layers3 / https://openlayers.org / gwt-ol / 
https://github.com/TDesjardins/gwt-ol / JsInterop
diagrams / chart.js / https://www.chartjs.org / charba / 
https://github.com/pepstock-org/Charba  
/ JsInterop
diagrams / highchart.js / https://www.highcharts.com / gwt-highcharts / 
https://github.com/ascendtech/gwt-highcharts / JsInterop
...

That's it., so we can see whether someone already did the work with 
JsInterop (analogy to DefinitelyTyped for the types in TS).
And everyone could make a PR to update the one page...

Is it worth it to try?

t.br...@gmail.com schrieb am Donnerstag, 1. Oktober 2020 um 10:00:10 UTC+2:

>
>
> 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 create a new GWT libs list project to have a list of all GWT libs 
>> available... so not only UI framework... and will put everything over 
>> there... hope that the community will make some PR, so we can have a lot of 
>> libs...
>>
>
> Some kind of "awesome gwt" then? https://github.com/sindresorhus/awesome
> Fwiw, a Google search for "awesome gwt" returned 
> https://awesomeopensource.com/projects/gwt and 
> https://gwt.zeef.com/awesomegwt
>
>

-- 
You received this message because you are subscribed to the Google Groups "GWT 
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit/36ad44d0-64de-4fe7-b709-b60641d9abc2n%40googlegroups.com.

Re: New Presentation about Modern GWT Webapp Development

2020-10-01 Thread Thomas Broyer 


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 create a new GWT libs list project to have a list of all GWT libs 
> available... so not only UI framework... and will put everything over 
> there... hope that the community will make some PR, so we can have a lot of 
> libs...
>

Some kind of "awesome gwt" then? https://github.com/sindresorhus/awesome
Fwiw, a Google search for "awesome gwt" 
returned https://awesomeopensource.com/projects/gwt 
and https://gwt.zeef.com/awesomegwt

-- 
You received this message because you are subscribed to the Google Groups "GWT 
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit/cb39374b-615a-42e9-9434-2a33c84ab006o%40googlegroups.com.

Re: New Presentation about Modern GWT Webapp Development

2020-09-21 Thread Thomas Broyer 
Fwiw, without plugin (Kotlin DSL):

val gwtOutputDir = file("$buildDir/gwtc/war")
tasks {
val gwtCompile by registering(JavaExec::class) {
val companionOutputDir = file("$buildDir/gwtc")
val deployDir = file("$companionOutputDir/extra")
val extraDir = deployDir
val genDir = file("$companionOutputDir/gen") // XXX: useful?
val workDir = file("$companionOutputDir/work")


outputs.dir(gwtOutputDir).withPropertyName("outputDir")
outputs.dir(deployDir).withPropertyName("deployDir")
outputs.dir(extraDir).withPropertyName("extraDir")
outputs.dir(genDir).withPropertyName("genDir")
outputs.dir(workDir).withPropertyName("workDir")


classpath = gwt
maxHeapSize = "1g"
main = "com.google.gwt.dev.Compiler"
args(
"-failOnError",
"-XdisableCastChecking",
"-XdisableClassMetadata",
"-war", gwtOutputDir,
"-deploy", deployDir,
"-extra", extraDir,
"-gen", genDir,
"-workDir", workDir,
"com.example.app.App"
)


doFirst {
delete(gwtOutputDir, deployDir, extraDir, genDir)
}
}


register("run") {

val workDir = file("$buildDir/gwt/codeserver")


classpath = gwt
maxHeapSize = "2g"
main = "com.google.gwt.dev.codeserver.CodeServer"
args(
"-failOnError",
"-launcherDir", gwtOutputDir,
"-workDir", workDir,
"com.example.app.App"
)


doFirst {
delete(gwtOutputDir)
mkdir(workDir)
}
}


integrationTest {
val warDir = file("$buildDir/gwt/www-test")
val workDir = file("$buildDir/gwt/work")
outputs.dir(warDir).withPropertyName("warDir")
outputs.dir(workDir).withPropertyName("workDir")


isScanForTestClasses = false
include("**/*Suite.class")


maxHeapSize = "1g"
systemProperty("gwt.args", """-ea -draftCompile -batch module -war "
$warDir" -workDir "$workDir" -runStyle HtmlUnit:FF38""")

}
}


On Monday, September 21, 2020 at 2:04:38 PM UTC+2, Michael Joyner wrote:
>
> There is also this jiakuan fork of the steffenschaefer plugin:
>
> https://github.com/jiakuan/gwt-gradle-plugin
>
> Maintenance of the fork is active.
>
>
> On 9/21/20 6:55 AM, Joker Joker wrote:
>
> *Lofi,* 
>
> I tried 3 plugins and this one (esoco) is the best one among them. 2 of 
> them are abandoned. The plugin from esoco is the only one mantained at the 
> moment.
>
> https://github.com/steffenschaefer/gwt-gradle-plugin (abandoned)
> https://github.com/Putnami/putnami-gradle-plugin (abandoned)
> *https://github.com/esoco/gwt-gradle-plugin 
> *  (active)
>
> Putnami was my choise before it was abandoned.
> Now I use esoco gradle plugin on 2 my large production projects and on on 
> several gwt libraries.
>
> пятница, 18 сентября 2020 г. в 00:39:06 UTC+4, jumanor: 
>
>> Gran trabajo, muchas gracias. 
>> great job!
>>
>>
>> El lunes, 11 de mayo de 2020 a las 16:01:56 UTC-5, lofid...@gmail.com 
>> escribió:
>>
>>> Hi All, 
>>>
>>> if you need a presentation about modern GWT development as an 
>>> introduction, just take a look at this:
>>>
>>> https://bit.ly/gwtintropresentation
>>>
>>> I also added this presentation in the Modern GWT Padlet: 
>>> https://bit.ly/GWTIntroPadlet
>>>
>>> Have fun,
>>> Lofi
>>>
>> -- 
> You received this message because you are subscribed to the Google Groups 
> "GWT Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to google-web-toolkit+unsubscr...@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/google-web-toolkit/e0ed6d1f-5962-4d23-b3d4-5354270b5f79n%40googlegroups.com
>  
> 
> .
>
>
>

-- 
You received this message because you are subscribed to the Google Groups "GWT 
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit/49332d32-6a48-49a8-a66c-37f81284e512o%40googlegroups.com.

Re: New Presentation about Modern GWT Webapp Development

2020-09-16 Thread lofid...@gmail.com 
Hi Thomas,

Surely we need to do the platform specific stuffs somewhere... but not in 
my programming language as keywords --> "the abstraction level" 樂

Using platform specific super-source for GWT is fine but I don't have that 
in Java and I don't want to have that in Java. For me you have following 
level of integration:
- Programming language (like Java, Kotlin, ...)
- Frameworks and libraries (like GWT, Spring Framework, ...)
- Build tools (like Maven, Gradle, ...)

Platform specific stuffs should not go to programming language but they can 
go to frameworks or build tools, so that the programming language can be 
stable for a long time.

I'm afraid that the programming language will become "unstable" if you add 
something like "expect/actual"? But maybe I'm just too carefully The new 
generation of programming language will break everything faster 

Cheers,
Lofi

t.br...@gmail.com schrieb am Mittwoch, 16. September 2020 um 19:49:33 UTC+2:

>
> On Wednesday, September 16, 2020 at 6:49:36 PM UTC+2, lofid...@gmail.com 
> wrote:
>>
>> Hi Thomas,
>>
>> ... actually I feel that doing platform specific stuffs in my code it's 
>> not the way.
>>
>> It is comparable to GWT vs. jsweet. In GWT you have everything in Java 
>> semantic. In jsweet you actually have everything in Java but with 
>> JavaScript semantic. jsweet is for me still better than JavaScript but I 
>> lost the Java semantic.
>>
>> Putting platform specific stuffs in the code mixes the separation of 
>> concern, IMHO...
>>
>
> Last time I wrote super-source was… last week!
> Using @JsType(isNative=true,namespace=GLOBAL,name="Object") classes to 
> talk to ProseMirror, translating between some XML and those JS objects 
> (context: https://twitter.com/tbroyer/status/1303647011279966208).
> In this case, this is purely client code, but I didn't want to use a 
> GWTTestCase to test my XML↔Objects transforms, so I wrote the test to run 
> in the JVM (and also made it work in a GWTTestCase, to make sure it does 
> indeed work, but it's a lot slower).
> Now how would you handle arrays? Well, I just use a 
> @JsType(isNative=true,namespace=GLOBAL,name="Array") with a few @JsOverlay 
> methods delegating to Js.asArrayLike(this)… in the super-source, with a 
> simplement implementation wrapping an ArrayList for the JVM.
> And how to compare the object trees in the tests? I cannot use things like 
> isEqualToComparingFieldByFieldRecursively 
> ,
>  
> and I didn't want to build something equivalent just for tests, so I just 
> serialize them to JSON, using JSON.stringify() in super-source for GWT (not 
> directly JSON.stringify() though, as object fields are not in a predictable 
> order, but more 
> https://www.rfc-editor.org/rfc/rfc8785.html#name-ecmascript-sample-canonical, 
> which relies on JSON.stringify for "primitive" values), and GSON (that we 
> already have around in GWT) in the JVM.
> Of course I could have built things differently, with abstract factories 
> so I could inject a GWT-specific or a JVM-specific one, and I actually went 
> that route initially, but honestly, just so I can use a different List 
> subclass within tests?
>
> (granted, the previous time I wrote super source, besides GWT's own 
> javaemul, was a long time ago :D but I never really shared a lot of code 
> between server and client anyway: besides that rich text editor, those 10 
> other subproject dependencies are actually only there for enums and some 
> constants, and of course one of them is about RequestFactory interfaces)
>

-- 
You received this message because you are subscribed to the Google Groups "GWT 
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit/c99e20f7-84d5-4e07-9afe-7e96ea8d8fa1n%40googlegroups.com.

Re: New Presentation about Modern GWT Webapp Development

2020-09-16 Thread Thomas Broyer 

On Wednesday, September 16, 2020 at 6:49:36 PM UTC+2, lofid...@gmail.com 
wrote:
>
> Hi Thomas,
>
> ... actually I feel that doing platform specific stuffs in my code it's 
> not the way.
>
> It is comparable to GWT vs. jsweet. In GWT you have everything in Java 
> semantic. In jsweet you actually have everything in Java but with 
> JavaScript semantic. jsweet is for me still better than JavaScript but I 
> lost the Java semantic.
>
> Putting platform specific stuffs in the code mixes the separation of 
> concern, IMHO...
>

Last time I wrote super-source was… last week!
Using @JsType(isNative=true,namespace=GLOBAL,name="Object") classes to talk 
to ProseMirror, translating between some XML and those JS objects 
(context: https://twitter.com/tbroyer/status/1303647011279966208).
In this case, this is purely client code, but I didn't want to use a 
GWTTestCase to test my XML↔Objects transforms, so I wrote the test to run 
in the JVM (and also made it work in a GWTTestCase, to make sure it does 
indeed work, but it's a lot slower).
Now how would you handle arrays? Well, I just use a 
@JsType(isNative=true,namespace=GLOBAL,name="Array") with a few @JsOverlay 
methods delegating to Js.asArrayLike(this)… in the super-source, with a 
simplement implementation wrapping an ArrayList for the JVM.
And how to compare the object trees in the tests? I cannot use things like 
isEqualToComparingFieldByFieldRecursively 
,
 
and I didn't want to build something equivalent just for tests, so I just 
serialize them to JSON, using JSON.stringify() in super-source for GWT (not 
directly JSON.stringify() though, as object fields are not in a predictable 
order, but 
more 
https://www.rfc-editor.org/rfc/rfc8785.html#name-ecmascript-sample-canonical, 
which relies on JSON.stringify for "primitive" values), and GSON (that we 
already have around in GWT) in the JVM.
Of course I could have built things differently, with abstract factories so 
I could inject a GWT-specific or a JVM-specific one, and I actually went 
that route initially, but honestly, just so I can use a different List 
subclass within tests?

(granted, the previous time I wrote super source, besides GWT's own 
javaemul, was a long time ago :D but I never really shared a lot of code 
between server and client anyway: besides that rich text editor, those 10 
other subproject dependencies are actually only there for enums and some 
constants, and of course one of them is about RequestFactory interfaces)

-- 
You received this message because you are subscribed to the Google Groups "GWT 
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit/0345bd0d-f5bc-48ed-a206-e2dd0b1825b9o%40googlegroups.com.

Re: New Presentation about Modern GWT Webapp Development

2020-09-16 Thread lofid...@gmail.com 
Hi Thomas,

... actually I feel that doing platform specific stuffs in my code it's not 
the way.

It is comparable to GWT vs. jsweet. In GWT you have everything in Java 
semantic. In jsweet you actually have everything in Java but with 
JavaScript semantic. jsweet is for me still better than JavaScript but I 
lost the Java semantic.

Putting platform specific stuffs in the code mixes the separation of 
concern, IMHO...

Cheers,
Lofi

lofid...@gmail.com schrieb am Mittwoch, 16. September 2020 um 18:21:41 
UTC+2:

> Hi Thomas,
>
> thanks a lot for your insight! 
>
> Personally I like the idea of Maven to build small projects and always the 
> same, instead of doing "variant" in Gradle (if I understand it correctly). 
> Building "intermediate" artifacts in Maven is also good for me, KISS 
> Building only one project to content everything I feel like I'm using Ant 
> again At the end the complexity is there, whether you put it into the 
> "intermediate" artifacts or you put it into the Gradle "variant".
>
> I'm not sure whether I like the idea of "expect/actual" in Kotlin. I 
> thought we don't need this anymore with Java --> WORA. But now we add such 
> a feature back to the programming language thanks to "multi platform" or 
> "platform specifics. Is that not the wrong place / wrong abstraction to put 
> the "platform specific stuffs"? Is that similar to C++ preprocessor macros?
>
> @Joker: do you have real experiences with the Gradle plugin you mentioned? 
> If you think, that it is the plugin to be used, I'll add to my slides... 
> But again I never use it...
>
> Thanks,
> Lofi
>
> t.br...@gmail.com schrieb am Mittwoch, 16. September 2020 um 10:36:32 
> UTC+2:
>
>>
>>
>> On Wednesday, September 16, 2020 at 9:48:39 AM UTC+2, lofid...@gmail.com 
>> wrote:
>>>
>>> Hi, thanks for the comment.
>>>
>>> There are some Gradle plugins for GWT, which one is the "best"? Sofar I 
>>> only use Maven, so never try Gradle...
>>>
>>> Maybe others could also tell which Gradle Plugin should we propose? 
>>> @Thomas Broyer?
>>>
>>
>> I don't use any plugin for GWT in Gradle (configuring JavaExec and Test 
>> tasks "by hand").
>>
>> One thing that no plugin seems to have done yet, is use Gradle variants 
>>  for 
>> *shared* libs to expose the sources to dependent subprojects in the same 
>> build only if/when they need it, and possibly use different dependencies: 
>> in a project with 37 subprojects, the GWT app only transitively depends on 
>> 10 of those subprojects, all of which are shared with the server; and some 
>> of them then add the sources JAR of third-party dependencies to the 
>> GWT-specific classpath.
>> With Maven, you would either put the sources 
>> dependency in the server classpath as well (for simplicity), add all the 
>> transitively-needed sources dependencies down to the GWT app module, or 
>> create intermediate artifacts that "aggregate" classes and sources (and 
>> possibly add the gwt.xml), like in 
>> https://github.com/tbroyer/gwt-maven-plugin/issues/127#issuecomment-474338891;
>>  
>> whereas with Gradle, you can do that in the very same project:
>>
>> plugins {
>>   java
>>   id("local.gwt-shared-lib")
>> }
>> dependencies {
>>   implementation("org.slf4j:slf4j-api")
>>   implementation("some third party lib")
>>   gwt("some emulation lib for SLF4J")
>>   gwt("adapter lib for the other third-party lib")
>> }
>>
>>
>>
>> When the GWT app depends (at any level of transitivity) on that lib, 
>> it'll automatically have 'gwt' dependencies in the classpath when calling 
>> GWT (compilation, code server, tests); the server app will only have the 
>> 'implementation' dependencies in its classpath.
>>
>> This works well for an application project at least; it would probably 
>> have to be different for a lib that you intend to deploy to a Maven 
>> repository for others to use; which is why I never formalized this in a 
>> (public) Gradle plugin yet.
>> Ideally I think we'd want a "java-multiplatform" plugin, similar to 
>> kotlin-multiplatform, to support all of the JVM, J2Cl and/or GWT, and 
>> J2ObjC, but Kotlin has an advantage here: they made it part of the language 
>> itself: https://kotlinlang.org/docs/reference/mpp-connect-to-apis.html
>>
>> (sorry for the digression)
>>
>

-- 
You received this message because you are subscribed to the Google Groups "GWT 
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit/2ecfd469-9a66-4e34-a139-f43cb1e59b84n%40googlegroups.com.

Re: New Presentation about Modern GWT Webapp Development

2020-09-16 Thread lofid...@gmail.com 
Hi Thomas,

thanks a lot for your insight! 

Personally I like the idea of Maven to build small projects and always the 
same, instead of doing "variant" in Gradle (if I understand it correctly). 
Building "intermediate" artifacts in Maven is also good for me, KISS 
Building only one project to content everything I feel like I'm using Ant 
again At the end the complexity is there, whether you put it into the 
"intermediate" artifacts or you put it into the Gradle "variant".

I'm not sure whether I like the idea of "expect/actual" in Kotlin. I 
thought we don't need this anymore with Java --> WORA. But now we add such 
a feature back to the programming language thanks to "multi platform" or 
"platform specifics. Is that not the wrong place / wrong abstraction to put 
the "platform specific stuffs"? Is that similar to C++ preprocessor macros?

@Joker: do you have real experiences with the Gradle plugin you mentioned? 
If you think, that it is the plugin to be used, I'll add to my slides... 
But again I never use it...

Thanks,
Lofi

t.br...@gmail.com schrieb am Mittwoch, 16. September 2020 um 10:36:32 UTC+2:

>
>
> On Wednesday, September 16, 2020 at 9:48:39 AM UTC+2, lofid...@gmail.com 
> wrote:
>>
>> Hi, thanks for the comment.
>>
>> There are some Gradle plugins for GWT, which one is the "best"? Sofar I 
>> only use Maven, so never try Gradle...
>>
>> Maybe others could also tell which Gradle Plugin should we propose? 
>> @Thomas Broyer?
>>
>
> I don't use any plugin for GWT in Gradle (configuring JavaExec and Test 
> tasks "by hand").
>
> One thing that no plugin seems to have done yet, is use Gradle variants 
>  for 
> *shared* libs to expose the sources to dependent subprojects in the same 
> build only if/when they need it, and possibly use different dependencies: 
> in a project with 37 subprojects, the GWT app only transitively depends on 
> 10 of those subprojects, all of which are shared with the server; and some 
> of them then add the sources JAR of third-party dependencies to the 
> GWT-specific classpath.
> With Maven, you would either put the sources 
> dependency in the server classpath as well (for simplicity), add all the 
> transitively-needed sources dependencies down to the GWT app module, or 
> create intermediate artifacts that "aggregate" classes and sources (and 
> possibly add the gwt.xml), like in 
> https://github.com/tbroyer/gwt-maven-plugin/issues/127#issuecomment-474338891;
>  
> whereas with Gradle, you can do that in the very same project:
>
> plugins {
>   java
>   id("local.gwt-shared-lib")
> }
> dependencies {
>   implementation("org.slf4j:slf4j-api")
>   implementation("some third party lib")
>   gwt("some emulation lib for SLF4J")
>   gwt("adapter lib for the other third-party lib")
> }
>
>
>
> When the GWT app depends (at any level of transitivity) on that lib, it'll 
> automatically have 'gwt' dependencies in the classpath when calling GWT 
> (compilation, code server, tests); the server app will only have the 
> 'implementation' dependencies in its classpath.
>
> This works well for an application project at least; it would probably 
> have to be different for a lib that you intend to deploy to a Maven 
> repository for others to use; which is why I never formalized this in a 
> (public) Gradle plugin yet.
> Ideally I think we'd want a "java-multiplatform" plugin, similar to 
> kotlin-multiplatform, to support all of the JVM, J2Cl and/or GWT, and 
> J2ObjC, but Kotlin has an advantage here: they made it part of the language 
> itself: https://kotlinlang.org/docs/reference/mpp-connect-to-apis.html
>
> (sorry for the digression)
>

-- 
You received this message because you are subscribed to the Google Groups "GWT 
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit/1cdc952a-c8d7-413e-8d4d-284bad681e2cn%40googlegroups.com.

Re: New Presentation about Modern GWT Webapp Development

2020-09-16 Thread Hamid Razoki 
Great job nice présentation

Le mer. 16 sept. 2020 à 09:36, Thomas Broyer  a écrit :

>
>
> On Wednesday, September 16, 2020 at 9:48:39 AM UTC+2, lofid...@gmail.com
> wrote:
>>
>> Hi, thanks for the comment.
>>
>> There are some Gradle plugins for GWT, which one is the "best"? Sofar I
>> only use Maven, so never try Gradle...
>>
>> Maybe others could also tell which Gradle Plugin should we propose?
>> @Thomas Broyer?
>>
>
> I don't use any plugin for GWT in Gradle (configuring JavaExec and Test
> tasks "by hand").
>
> One thing that no plugin seems to have done yet, is use Gradle variants
>  for
> *shared* libs to expose the sources to dependent subprojects in the same
> build only if/when they need it, and possibly use different dependencies:
> in a project with 37 subprojects, the GWT app only transitively depends on
> 10 of those subprojects, all of which are shared with the server; and some
> of them then add the sources JAR of third-party dependencies to the
> GWT-specific classpath.
> With Maven, you would either put the sources
> dependency in the server classpath as well (for simplicity), add all the
> transitively-needed sources dependencies down to the GWT app module, or
> create intermediate artifacts that "aggregate" classes and sources (and
> possibly add the gwt.xml), like in
> https://github.com/tbroyer/gwt-maven-plugin/issues/127#issuecomment-474338891;
> whereas with Gradle, you can do that in the very same project:
>
> plugins {
>   java
>   id("local.gwt-shared-lib")
> }
> dependencies {
>   implementation("org.slf4j:slf4j-api")
>   implementation("some third party lib")
>   gwt("some emulation lib for SLF4J")
>   gwt("adapter lib for the other third-party lib")
> }
>
>
>
> When the GWT app depends (at any level of transitivity) on that lib, it'll
> automatically have 'gwt' dependencies in the classpath when calling GWT
> (compilation, code server, tests); the server app will only have the
> 'implementation' dependencies in its classpath.
>
> This works well for an application project at least; it would probably
> have to be different for a lib that you intend to deploy to a Maven
> repository for others to use; which is why I never formalized this in a
> (public) Gradle plugin yet.
> Ideally I think we'd want a "java-multiplatform" plugin, similar to
> kotlin-multiplatform, to support all of the JVM, J2Cl and/or GWT, and
> J2ObjC, but Kotlin has an advantage here: they made it part of the language
> itself: https://kotlinlang.org/docs/reference/mpp-connect-to-apis.html
>
> (sorry for the digression)
>
> --
> You received this message because you are subscribed to the Google Groups
> "GWT Users" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to google-web-toolkit+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/google-web-toolkit/2886a824-dba4-463e-bac6-29a3e1cbbe67o%40googlegroups.com
> 
> .
>

-- 
You received this message because you are subscribed to the Google Groups "GWT 
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit/CACgjETbdvXuSzSsyHYy5OX31OAuUQ%3DzLKVpxEpVUkSgJV-wsUQ%40mail.gmail.com.

Re: New Presentation about Modern GWT Webapp Development

2020-09-16 Thread Thomas Broyer 


On Wednesday, September 16, 2020 at 9:48:39 AM UTC+2, lofid...@gmail.com 
wrote:
>
> Hi, thanks for the comment.
>
> There are some Gradle plugins for GWT, which one is the "best"? Sofar I 
> only use Maven, so never try Gradle...
>
> Maybe others could also tell which Gradle Plugin should we propose? 
> @Thomas Broyer?
>

I don't use any plugin for GWT in Gradle (configuring JavaExec and Test 
tasks "by hand").

One thing that no plugin seems to have done yet, is use Gradle variants 
 for *shared* 
libs 
to expose the sources to dependent subprojects in the same build only 
if/when they need it, and possibly use different dependencies: in a project 
with 37 subprojects, the GWT app only transitively depends on 10 of those 
subprojects, all of which are shared with the server; and some of them then 
add the sources JAR of third-party dependencies to the GWT-specific 
classpath.
With Maven, you would either put the sources 
dependency in the server classpath as well (for simplicity), add all the 
transitively-needed sources dependencies down to the GWT app module, or 
create intermediate artifacts that "aggregate" classes and sources (and 
possibly add the gwt.xml), like 
in 
https://github.com/tbroyer/gwt-maven-plugin/issues/127#issuecomment-474338891; 
whereas with Gradle, you can do that in the very same project:

plugins {
  java
  id("local.gwt-shared-lib")
}
dependencies {
  implementation("org.slf4j:slf4j-api")
  implementation("some third party lib")
  gwt("some emulation lib for SLF4J")
  gwt("adapter lib for the other third-party lib")
}



When the GWT app depends (at any level of transitivity) on that lib, it'll 
automatically have 'gwt' dependencies in the classpath when calling GWT 
(compilation, code server, tests); the server app will only have the 
'implementation' dependencies in its classpath.

This works well for an application project at least; it would probably have 
to be different for a lib that you intend to deploy to a Maven repository 
for others to use; which is why I never formalized this in a (public) 
Gradle plugin yet.
Ideally I think we'd want a "java-multiplatform" plugin, similar to 
kotlin-multiplatform, to support all of the JVM, J2Cl and/or GWT, and 
J2ObjC, but Kotlin has an advantage here: they made it part of the language 
itself: https://kotlinlang.org/docs/reference/mpp-connect-to-apis.html

(sorry for the digression)

-- 
You received this message because you are subscribed to the Google Groups "GWT 
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit/2886a824-dba4-463e-bac6-29a3e1cbbe67o%40googlegroups.com.

Re: New Presentation about Modern GWT Webapp Development

2020-09-16 Thread lofid...@gmail.com 
Hi, thanks for the comment.

There are some Gradle plugins for GWT, which one is the "best"? Sofar I 
only use Maven, so never try Gradle...

Maybe others could also tell which Gradle Plugin should we propose? @Thomas 
Broyer?

Thanks,
Lofi
rov6...@gmail.com schrieb am Mittwoch, 16. September 2020 um 09:12:42 UTC+2:

> Please add to Tools slide 100% working and mantained *gwt-gradle-plugin*
>
> https://github.com/esoco/gwt-gradle-plugin
>
> среда, 16 сентября 2020 г. в 10:49:52 UTC+4, Joker Joker: 
>
>> Great job! These things help promote GWT.
>>
>> среда, 13 мая 2020 г. в 14:33:58 UTC+4, lofid...@gmail.com: 
>>
>>> I added a slide for: 
>>>
>>> *Why not server-side Java UI frameworks like Vaadin, Wicket, JSF, …?*
>>>
>>> IMHO, this is an important point too.
>>>
>>> Thanks, 
>>> Lofi
>>>
>>

-- 
You received this message because you are subscribed to the Google Groups "GWT 
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit/2fae4e32-ca93-442c-9530-b0a3e0bf889en%40googlegroups.com.

Re: New Presentation about Modern GWT Webapp Development

2020-09-16 Thread Joker Joker 
Please add to Tools slide 100% working and mantained *gwt-gradle-plugin*

https://github.com/esoco/gwt-gradle-plugin

среда, 16 сентября 2020 г. в 10:49:52 UTC+4, Joker Joker: 

> Great job! These things help promote GWT.
>
> среда, 13 мая 2020 г. в 14:33:58 UTC+4, lofid...@gmail.com: 
>
>> I added a slide for: 
>>
>> *Why not server-side Java UI frameworks like Vaadin, Wicket, JSF, …?*
>>
>> IMHO, this is an important point too.
>>
>> Thanks, 
>> Lofi
>>
>

-- 
You received this message because you are subscribed to the Google Groups "GWT 
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit/da160d91-e74c-4316-9ba7-a24cf9adf5can%40googlegroups.com.

Re: New Presentation about Modern GWT Webapp Development

2020-09-16 Thread Joker Joker 
Great job! These things help promote GWT.

среда, 13 мая 2020 г. в 14:33:58 UTC+4, lofid...@gmail.com: 

> I added a slide for: 
>
> *Why not server-side Java UI frameworks like Vaadin, Wicket, JSF, …?*
>
> IMHO, this is an important point too.
>
> Thanks, 
> Lofi
>

-- 
You received this message because you are subscribed to the Google Groups "GWT 
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit/d5f3cc43-0aab-4814-ad51-f29c8c4c58fbn%40googlegroups.com.

Re: New Presentation about Modern GWT Webapp Development

2020-05-13 Thread Dr. Lofi Dewanto 
I added a slide for: 

*Why not server-side Java UI frameworks like Vaadin, Wicket, JSF, …?*

IMHO, this is an important point too.

Thanks, 
Lofi

-- 
You received this message because you are subscribed to the Google Groups "GWT 
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit/3b836141-258c-4845-87be-7776962aa12b%40googlegroups.com.

Re: New Presentation about Modern GWT Webapp Development

2020-05-13 Thread Dr. Lofi Dewanto 
Update again with  and 

Because I think modern GWT == Elemental2 and Java Annotation Processor (no 
GWT generators) and I still put the "included" GWT UIs as both. Because in 
2.8.x you still use GWT generators and older Widget stuffs.

Thanks,
Lofi

-- 
You received this message because you are subscribed to the Google Groups "GWT 
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit/175b17af-cf2e-4c81-96a2-c7e29cb4fcb2%40googlegroups.com.

Re: New Presentation about Modern GWT Webapp Development

2020-05-13 Thread Dr. Lofi Dewanto 
Hi Jens,

thanks a lot for your comment. Yes, a good example is actually 
GWTBootstrap3:

   - Old one based on old stuffs GWT: 
   https://gwtbootstrap3.github.io/gwtbootstrap3-demo
   - And the new one based on Elemental2: 
   https://github.com/treblereel/gwtbootstrap3

So as an application developer I don't really need to change my code, 
because it still use the same APIs.

I changed the "deprecated" to two types: "NeedUpdateElemental2" and 
"NoFancyL" 

Thanks,
Lofi

-- 
You received this message because you are subscribed to the Google Groups "GWT 
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit/bcc596fe-8745-41f8-8fb1-a304326a4cd8%40googlegroups.com.

Re: New Presentation about Modern GWT Webapp Development

2020-05-13 Thread Jens 
Personally I would not say that GWT widgets are deprecated. They are ported 
to be compatible with J2CL, they just look a bit dated because nobody has 
done a new fancy CSS for them. So it is generally fine to use them, but you 
should not expect that any new components will be added to the currently 
available ones anytime soon. But if someone is really interested in it I 
could see that widget internals could be modernized even more, a more 
modern CSS theme could be written and then gradually enhance these widgets.

I would more see them as "not recommend if you expect an evolving UI 
framework with components for all kinds of use cases, even use cases you 
don't have.".

-- J.

-- 
You received this message because you are subscribed to the Google Groups "GWT 
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit/82ef2172-7834-4d19-ae57-7b4bf4279bcf%40googlegroups.com.

Re: New Presentation about Modern GWT Webapp Development

2020-05-12 Thread Dr. Lofi Dewanto 
Hi Thomas,

thanks a lot for the review. I updated following:

(1) Slide 18: updated with your content

(2) Slide 20: I let the slide 20 the same but I inserted a slide 23, which 
said "... more than two connections..."

(2.1) I also add a slide 24 about

Re: New Presentation about Modern GWT Webapp Development

2020-05-12 Thread Thomas Broyer 
Great deck, there are a few inaccuracies though:

   - Slide 18:  “Most browsers will allow a maximum of two simultaneous 
   connections for fetching resources.” This has been wrong for some time; 
   limit has been bumped to 6 since IE8, Firefox 3.6 (
   
https://developer.mozilla.org/en-US/docs/Web/HTTP/Connection_management_in_HTTP_1.x#Domain_sharding
   , https://hpbn.co/http1x/#using-multiple-tcp-connections, 
   https://en.wikipedia.org/wiki/HTTP_persistent_connection#Use_in_web_browsers
   , http://www.stevesouders.com/blog/2008/03/10/ie8-speeds-things-up/, 
   
http://kb.mozillazine.org/Network.http.max-persistent-connections-per-server), 
   I've even found a resource stating that IE11 used up to 13 connections (
   
https://docs.pushtechnology.com/cloud/latest/manual/html/designguide/solution/support/connection_limitations.html
   )
   - Slide 20: I'm pretty sure modern browsers will start to fetch 
   bigImageOne and reallyBigImageTwo in parallel to externalScriptZero (see 
   https://developer.mozilla.org/en-US/docs/Glossary/speculative_parsing), 
   and of course the example is tailored for a 2-connection-per-server limit, 
   which is no longer the case. As we're at it, you might also want to talk 
   about