Re: DominoKit has a new home

[Andrea Stocchero]

well done guys!

Il giorno mercoledì 1 novembre 2023 alle 18:31:31 UTC+1 lofid...@gmail.com 
ha scritto:

> Great work! Congrats!
>
> Vegegoku schrieb am Dienstag, 31. Oktober 2023 um 09:41:19 UTC+1:
>
>> Exciting news — https://dominokit.com is live! Our new platform stands 
>> as a beacon of inclusion, unifying detailed documentation in one 
>> centralized location to empower and educate. We invite you to explore this 
>> collective reservoir of knowledge, designed to support and inspire. Please 
>> help us spread the word by sharing this resource with your network and 
>> beyond. Together, we can create a vast community of shared wisdom and 
>> resources.
>>
>

-- 
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/74c23d48-1d9b-47f9-b77d-d4e313ba9a96n%40googlegroups.com.

Re: JavaFX for GWT

[Andrea Stocchero]

Really interesting

Il giorno martedì 8 novembre 2022 alle 15:37:50 UTC+1 Bruno Salmon ha 
scritto:

> Hi,
>
> I'm working on a JavaFX transpiler powered by GWT.
> It lets you use JavaFX as a UI toolkit in your GWT apps.
> The JavaFX API is far from completely covered, but you can already see 
> some interesting results.
>
> The project is on GitHub for those who are interested.
> https://github.com/webfx-project/webfx
>
> If you have any questions, please let me know.
>

-- 
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/30a8e75f-bf0c-412c-88c6-345b7610701dn%40googlegroups.com.

Re: Wrapping Javascript library (chart.js) using JSInterop

[Andrea Stocchero]

Why don't you use Charba? https://github.com/pepstock-org/Charba

Charba is providing the wrapper of Chart.js for GWT and J2CL.

Il giorno domenica 11 settembre 2022 alle 14:53:25 UTC+2 
manassriv...@gmail.com ha scritto:

> I have added a pom.xml file in the project attached below while running 
> the command - mvn clean install I got an error - Compiling module 
> com.jsinteropdemo.JSInteropDemo
> [INFO][ERROR] Module has no entry points defined
> Also attaching the screenshot of my project folder and default .XML file
> On Sunday, September 11, 2022 at 5:59:36 PM UTC+5:30 m.conr...@gmail.com 
> wrote:
>
>> Check your dependencies. That is an add-on library which must be included 
>> explicitly.
>>
>> On Sun, Sep 11, 2022 at 5:10 AM Manas  wrote:
>>
>>> Hi All,
>>>
>>> Good Day!
>>>
>>> I'm new in GWT and I'm going through documentation and JSInterop. I'm 
>>> facing issues with implementing chart.js using JSInterop. Can anyone guide 
>>> me on how to resolve and keep things working? I am facing an error - "The 
>>> import elemental2 cannot be resolved"
>>>
>>> code is - 
>>> package chartjs;
>>>
>>> import elemental2.dom.HTMLCanvasElement; => facing error on this line
>>> import jsinterop.annotations.JsPackage;
>>> import jsinterop.annotations.JsType;
>>>
>>> @JsType(isNative = true, namespace = JsPackage.GLOBAL)
>>> public class Chart {
>>>
>>> public Chart(HTMLCanvasElement canvasElement, ChartConfiguration 
>>> configuration) {
>>> }
>>> }
>>>
>>> -- 
>>> 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-tool...@googlegroups.com.
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/google-web-toolkit/d85e1313-7a55-482f-b712-022cf6fef5acn%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/0b0ae3fa-2622-4762-b1e5-ec49bceca637n%40googlegroups.com.

Re: GWT 2.10.0 release

[Andrea Stocchero]

Great!
Thank you Colin and everyone. 

Il giorno venerdì 15 luglio 2022 alle 10:30:30 UTC+2 abhiy...@gmail.com ha 
scritto:

> Hi Priya,
>
> GWT 2.10 has dropped support for  IE 8, 9, and 10. So it will not work 
> unless you modify the Sencha GXT 2.3.1.a.jar
>
> On Thursday, July 14, 2022 at 5:24:08 PM UTC+5:30 priyako...@gmail.com 
> wrote:
>
>> Hello All,
>> Good to see that new version of GWT coming with new features!!!
>> Is the new 2.10.0 GWT version compatible with Sencha GXT 2.3.1.a ? 
>> Will appreciate an early reply! 
>>
>> On Sat, Jul 2, 2022 at 1:40 AM Mihail Krastev  wrote:
>>
>>> Really good job, thanks to everyone involved!
>>>
>>> On Thursday, June 23, 2022 at 7:16:50 PM UTC+3 nilo...@gmail.com wrote:
>>>
 I'm very happy to announce the release of GWT 2.10.0. This is the first 
 release using our new groupId, org.gwtproject, and the final release using 
 com.google.gwt. If you resolve dependencies from Maven Central, please be 
 certain that your project is using com.google.gwt:gwt (or 
 org.gwtproject:gwt) as a BOM, so that you are certain to have consistent 
 versions of gwt-user and gwt-dev, even across groupIds.

 For this release, either groupId will work, but future releases will 
 only be made on the org.gwtproject groupId.

 The zip download of the GWT SDK is available at 
 https://github.com/gwtproject/gwt/releases/download/2.10.0/gwt-2.10.0.zip

 --

 Release notes for GWT 2.10.0, taken from 
 https://www.gwtproject.org/release-notes.html#Release_Notes_2_10_0

 Highlights 

- 

Updated to HtmlUnit 2.55.0 and Jetty 9.4.44. With this newer 
HtmlUnit build comes support for Promise in unit tests, and the browser 
strings that can be specified when running tests are “FF”, “Chrome”, 
 “IE” 
(for IE11), “Edge”, and “Safari”.
- 

Tested support for running on Java 17, dropped remaining support 
for running on Java 7.
- 

Maven groupId is formally changed to org.gwtproject, projects 
should take care to make sure they are using either the old 
com.google.gwt:gwt BOM or the new org.gwtproject:gwt BOM to sure 
that Maven or Gradle correctly handle this change. This will be the 
 last 
published version using the com.google.gwt groupId.
- 

Dropped support for IE 8, 9, and 10.

 Bug fixes 

- Correct Long.hashCode semantics
- Support CLASSPATH environment variable when creating child 
processes, fixing a bug where Windows could fail with a long list of 
arguments.
- Use Function.name instead of displayName to support visible 
method names in Chrome 93+.
- Allow stack traces to be available in Chrome when loading scripts 
from a remote origin.

 JRE Emulation 

- Added OutputStreamWriter emulation.
- Support StringReader mark() and reset() methods.
- Added StrictMath emulation.
- Added BufferedWriter emulation.
- Added incomplete PrintStream emulation.
- Add Charset.defaultCharset() emulation.
- Improve BigInteger emulated performance.
- System.nanoTime() emulation with performance.now().
- Added Optional.isEmpty emulation.
- JRE Emulation improvements/simplifications to facilitate J2CL’s 
WASM support. Note that these do not always offer specific improvements 
 to 
GWT itself, but helps to keep the codebases consistent.

 Miscellaneous 

- Add support to compile GWT itself in Java 9+.
- Improve compiled code size for applications that never use 
streams, by avoiding referencing streams from Throwable.

 For more detail, see the commit log 
 .

>>> -- 
>>> 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-tool...@googlegroups.com.
>>> To view this discussion on the web visit 
>>> https://groups.google.com/d/msgid/google-web-toolkit/af5e74c8-4f62-46d2-a29a-f28203555e32n%40googlegroups.com
>>>  
>>> 
>>> .
>>>
>>
>>
>> -- 
>> Life is Beautiful..
>> Keep Smiling
>> Priya..
>>
>

-- 
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/855c4916-ec45-4077-b739-e46c95

Re: [ANN] Akasha: Typed Browser API

[Andrea Stocchero]

For INTL Number and Date format, there is an implementation here: 
https://github.com/pepstock-org/Charba/tree/master/src/org/pepstock/charba/client/intl
If you are not using that chart lib, it could be a starting point.


Il giorno martedì 15 giugno 2021 alle 00:54:56 UTC+2 peter.j...@gmail.com 
ha scritto:

> On Tue, Jun 15, 2021 at 6:59 AM foal  wrote:
>
>> Hi, do you have support for Intl API? 
>
>
> Not as yet. It is a javascript specification rather than a browser 
> interface specification which means there is no WebIDL to use to generate 
> the API. This would mean I would need to write the WebIDL or manually 
> construct the jsinterop types ... which looks easy enough ... but I have 
> yet to get to it ;)
>
> -- 
> Cheers,
>
> Peter Donald
>

-- 
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/83683660-af71-4b41-bf9b-e377131cdd66n%40googlegroups.com.

Re: Can I create GWT Widget in javascript code?

[Andrea Stocchero]

Charba is a library which is wrapping CHART.JS to provide charts in GWt and 
J2Cl appliation and for GWT a chat can be a widget. Almost everything by 
JSINTEROP.

https://github.com/pepstock-org/Charba/tree/master/src/org/pepstock/charba/client/gwt/widgets

https://github.com/pepstock-org/Charba

Il giorno martedì 2 marzo 2021 alle 15:48:08 UTC+1 Boris Brudnoy ha scritto:

> Would vue-gwt (https://github.com/VueGWT/vue-gwt) help your scenario?
>
> *Boris Brudnoy*
> Web Software Engineer | LinkedIn  
> | StackOverflow 
> I created RecipeLot.com, a companion for culinary enthusiasts. Check it 
> out.
>
>
> On Tue, Mar 2, 2021 at 5:43 AM Zhang Alex  wrote:
>
>> since now not yet!
>> I have a large application build with gwt 2.8 + Gxt
>> recently, other company need integration  some UI  into it's web 
>> application, eg:  div
>> Does JsInterop suitable my Scene
>> Thank for your example case
>> 在2021年3月2日星期二 UTC+8 下午4:58:00 写道：
>>
>>> Never wrap a Widget with JsInterop before... but just like in this 
>>> article I wrapped a Calculator with JsInterop so that afterwards I could 
>>> use it from JavaScript. 
>>>
>>> https://bit.ly/WebJavaStory
>>>
>>> Did you try to wrap your Widget with JsInterop?
>>>
>>> alex...@gmail.com schrieb am Dienstag, 2. März 2021 um 05:09:24 UTC+1:
>>>
 For example:
  I have a vue app and classic gwt application,  The gwt application 
 have lot of module .
 but I only want to one module (eg: A query UI) integration  to my vue 
 app using js
 How can I done this?
 Tks.


 -- 
>> 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-tool...@googlegroups.com.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msgid/google-web-toolkit/29710f11-149d-4eae-8915-54010c0586e7n%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/a455a304-3aa3-4cc1-852b-23eb2bc89e3dn%40googlegroups.com.

Re: Why Don’t You Use Java for Programming the Client-Side Web Apps on Web Browser?

[Andrea Stocchero]

Sorry Lofi, I misunderstood you.

Fully agree with you!

Il giorno martedì 29 settembre 2020 alle 10:56:26 UTC+2 lofid...@gmail.com 
ha scritto:

> Ahh, I mean not only "Maven" just a *build tool* like Maven, Gradle, 
> Buildr, Bazel, Ivy or whatever... 😉👍
>
> The main thing we need to *manage the dependencies and versions*.
>
> Just putting those Jar files in your project and only depends on IDE 
> dependent plugins won't help in mid term, IMHO.
>
> stock...@gmail.com schrieb am Dienstag, 29. September 2020 um 09:57:24 
> UTC+2:
>
>>
>> Lofi, 
>>
>> https://github.com/pepstock-org/Charba is not using Maven and it's using 
>> Ivy.
>>
>> Also I'm not using it for my applications. I had to use it for the Charba 
>> J2CL showcase where I'm leveraging on J2CL maven plugin. 
>>
>> Il giorno martedì 29 settembre 2020 alle 09:40:22 UTC+2 
>> lofid...@gmail.com ha scritto:
>>
>>> Actually I don't see any Java apps should work without Maven:
>>>
>>>- Why won't you use Maven? At the end everyone has to *manage 
>>>dependencies* / *versions* and today you need such a tool like Maven.
>>>
>>> Yes, design patterns are language independent.
>>>
>>> Did you use pdf.js? And this is actually a very important part of GWT / 
>>> J2CL development. In such a case we should always offer an Open Source lib 
>>> for *JsInterop*, just like *DefinitelyTyped* in TypeScript... I found a 
>>> GWT project for pdf.js but it still using JSNI: 
>>> https://github.com/pandurangpatil/gwt-pdfjs
>>>
>>> I think, I'll open a GitHub project for the list of libraries for GWT, 
>>> similar to *DefinitelyTyped but only a link list...*
>>>
>>> As you said, if everyone support implementing *JsInterop files for 
>>> JavaScript libs* it will be very easy for Java developers to use them 
>>> and they don't need to write the JsInterop files for x times...
>>>
>>> Thanks,
>>> Lofi
>>> rmr...@gmail.com schrieb am Dienstag, 29. September 2020 um 01:06:29 
>>> UTC+2:
>>>
 Hello Lofi,

 Some loose comments:

 - Another great advantage I enjoy is that I don't need Maven. Can you 
 rewrite your example _without_ depending on Maven? And without using a 
 library that relies on annotations?

 - VisualStudio code is great for Java and JavaScript. You can also use 
 Eclipse with Java and JavaScript, but it is not as fast.

 - Design patterns are language independent. You can use them with Java, 
 TypeScript, C++ or whatever you like.

 - Although there tons of libraries you can use on the server side, Java 
 has limited options as a client in a browser. For example, in one of my 
 projects I need to display a PDF in the browser and manipulate its text 
 content depending on certain user actions; there aren't Java libraries 
 that 
 can work in the browser and are good enough for the task.

 Regards,
 Rodolfo


 On Mon, Sep 28, 2020 at 7:09 PM lofid...@gmail.com  
 wrote:

> OK, now I understand you 😉
>
> Yes, we always have to separate the Client and the Server part. This 
> is also GWT best practice.
>
> But if you are using JavaScript on browser you lose the advantages 
> like:
>
>1. We use *Java* as the language
>2. We have the best *ecosystem* like libraries, frameworks, build 
>system and IDEs.
>3. We know best design patterns to make our apps maintainable like 
>Dependency Injection, Mock Testing and many other just take a look at: 
>http://bit.ly/DesignPatternsJava
>4. … and if you use Java on the server-side with *Spring Framework*
> or *JavaEE* you have *one language* through the whole stack. So, 
>you could reuse Validation APIs, Business Rules, Business Model, etc. 
> from 
>server to client.
>
> I've built this sample project: 
> https://github.com/gwtboot/domino-rest-enum-date to show some reuse 
> for Client and Server and I plan to write more articles on this topic: 
> Dependency Injection, Mocking Test, Validation API, Business Rules - all 
> from Server to Client.
>
> This type of reuse cannot be done if you are using JavaScript / 
> TypeScript on the web browser...
>
> Thanks,
> Lofi
> rmr...@gmail.com schrieb am Montag, 28. September 2020 um 23:20:23 
> UTC+2:
>
>> If the server part is a Java servlet that handles REST calls, there 
>> is no need for GWT at all. No need to deal with JSInterop and no need to 
>> deal with annotations, that's cleaner code!
>>
>> If you have a server that exposes a REST API, you can write the 
>> client in anything. JavaScript is great in the browser and TypeScript 
>> improves the coding experience while sharing direct use of JavaScript 
>> libraries.
>>
>> Running a Java client in the browser implies extra steps and 
>> complications. First and foremost, you can't mix Java and Ja

Re: Why Don’t You Use Java for Programming the Client-Side Web Apps on Web Browser?

[Andrea Stocchero]

Sorry Lofi,



Il giorno mar 29 set 2020 alle ore 10:57 lofid...@gmail.com <
lofidewa...@gmail.com> ha scritto:

> Ahh, I mean not only "Maven" just a *build tool* like Maven, Gradle,
> Buildr, Bazel, Ivy or whatever... 😉👍
>
> The main thing we need to *manage the dependencies and versions*.
>
> Just putting those Jar files in your project and only depends on IDE
> dependent plugins won't help in mid term, IMHO.
>
> stock...@gmail.com schrieb am Dienstag, 29. September 2020 um 09:57:24
> UTC+2:
>
>>
>> Lofi,
>>
>> https://github.com/pepstock-org/Charba is not using Maven and it's using
>> Ivy.
>>
>> Also I'm not using it for my applications. I had to use it for the Charba
>> J2CL showcase where I'm leveraging on J2CL maven plugin.
>>
>> Il giorno martedì 29 settembre 2020 alle 09:40:22 UTC+2
>> lofid...@gmail.com ha scritto:
>>
>>> Actually I don't see any Java apps should work without Maven:
>>>
>>>- Why won't you use Maven? At the end everyone has to *manage
>>>dependencies* / *versions* and today you need such a tool like Maven.
>>>
>>> Yes, design patterns are language independent.
>>>
>>> Did you use pdf.js? And this is actually a very important part of GWT /
>>> J2CL development. In such a case we should always offer an Open Source lib
>>> for *JsInterop*, just like *DefinitelyTyped* in TypeScript... I found a
>>> GWT project for pdf.js but it still using JSNI:
>>> https://github.com/pandurangpatil/gwt-pdfjs
>>>
>>> I think, I'll open a GitHub project for the list of libraries for GWT,
>>> similar to *DefinitelyTyped but only a link list...*
>>>
>>> As you said, if everyone support implementing *JsInterop files for
>>> JavaScript libs* it will be very easy for Java developers to use them
>>> and they don't need to write the JsInterop files for x times...
>>>
>>> Thanks,
>>> Lofi
>>> rmr...@gmail.com schrieb am Dienstag, 29. September 2020 um 01:06:29
>>> UTC+2:
>>>
 Hello Lofi,

 Some loose comments:

 - Another great advantage I enjoy is that I don't need Maven. Can you
 rewrite your example _without_ depending on Maven? And without using a
 library that relies on annotations?

 - VisualStudio code is great for Java and JavaScript. You can also use
 Eclipse with Java and JavaScript, but it is not as fast.

 - Design patterns are language independent. You can use them with Java,
 TypeScript, C++ or whatever you like.

 - Although there tons of libraries you can use on the server side, Java
 has limited options as a client in a browser. For example, in one of my
 projects I need to display a PDF in the browser and manipulate its text
 content depending on certain user actions; there aren't Java libraries that
 can work in the browser and are good enough for the task.

 Regards,
 Rodolfo


 On Mon, Sep 28, 2020 at 7:09 PM lofid...@gmail.com 
 wrote:

> OK, now I understand you 😉
>
> Yes, we always have to separate the Client and the Server part. This
> is also GWT best practice.
>
> But if you are using JavaScript on browser you lose the advantages
> like:
>
>1. We use *Java* as the language
>2. We have the best *ecosystem* like libraries, frameworks, build
>system and IDEs.
>3. We know best design patterns to make our apps maintainable like
>Dependency Injection, Mock Testing and many other just take a look at:
>http://bit.ly/DesignPatternsJava
>4. … and if you use Java on the server-side with *Spring Framework*
> or *JavaEE* you have *one language* through the whole stack. So,
>you could reuse Validation APIs, Business Rules, Business Model, etc. 
> from
>server to client.
>
> I've built this sample project:
> https://github.com/gwtboot/domino-rest-enum-date to show some reuse
> for Client and Server and I plan to write more articles on this topic:
> Dependency Injection, Mocking Test, Validation API, Business Rules - all
> from Server to Client.
>
> This type of reuse cannot be done if you are using JavaScript /
> TypeScript on the web browser...
>
> Thanks,
> Lofi
> rmr...@gmail.com schrieb am Montag, 28. September 2020 um 23:20:23
> UTC+2:
>
>> If the server part is a Java servlet that handles REST calls, there
>> is no need for GWT at all. No need to deal with JSInterop and no need to
>> deal with annotations, that's cleaner code!
>>
>> If you have a server that exposes a REST API, you can write the
>> client in anything. JavaScript is great in the browser and TypeScript
>> improves the coding experience while sharing direct use of JavaScript
>> libraries.
>>
>> Running a Java client in the browser implies extra steps and
>> complications. First and foremost, you can't mix Java and JavaScript
>> libraries without wasting a lot of time with compatibility layers. T

Re: Why Don’t You Use Java for Programming the Client-Side Web Apps on Web Browser?

[Andrea Stocchero]

First of all, let me say I'm a Java developer and I'm using GWT since years.

Having started developing java since 1996 (with java 1.0.2), I have seen 
many technologies and frameworks to help a java developer can use to build 
a UI on web browser (like applets, servlets, jsp, jsf, webstart).
I have met GWT many years ago and it was for me the right answer to my 
questions to develop by a single programming language both client and 
server sides.
And I'm still using.

Nevertheless there are some pain points that it's important do not 
under-estimate.

1. Java developer has to have some skills HTML, CSS and Javascript as well. 
2. Usage of JSinterop to map a javascript code is not trivial even if it's 
complex. It's time consuming (time that you don't have to spend using 
Javascript).
3. GWT widgets should be modernized (even if there are other frameworks 
like Domino and GWT Materials but adding complexity).
4. Java code must be well designed in order to be efficient. Javascript 
(for its nature) allows you to develop very fast (time means cost).

In my opinion there are other reasons why Java developers during last years 
preferred to learn javascript for UI, like the unclear GWT future and 
roadmap, but maybe less important.

Il giorno giovedì 24 settembre 2020 alle 21:02:18 UTC+2 lofid...@gmail.com 
ha scritto:

> I would like to know, what are the *obstacles* for you as *Java 
> developers* not using *Java as programming language for writing Web 
> browser apps*. Web browser apps are client-side and *not server-side* Web 
> apps. 
>
>- Open discussion at https://bit.ly/HackerNewsTypeScriptJavaGWT
>- Article at https://bit.ly/TypeScriptVsJavaGWT
>
> I would like to know from you... Java developers...
>
> 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/04bf418b-ec46-44b5-9556-c54bb95caf9dn%40googlegroups.com.