Re: [ANN] (Unofficial) Elemental2 2.24 release

On Wed, Jun 12, 2019 at 8:29 AM Peter Donald <pe...@realityforge.org> wrote:

On Wed, Jun 12, 2019 at 7:31 AM John Huss <john...@gmail.com> wrote:

Out of curiosity, how did you get this project to build successfully? 

When I try to build it I see this:

$ ./bazel_build_test.sh 

ERROR: /Users/john/repos/elemental2/third_party/BUILD:21:1: no such target '@com_google_javascript_closure_compiler//:externs': target 'externs' not declared in package '' defined by /private/var/tmp/_bazel_john/b729f51825638d22c4a92cfea6e4556d/external/com_google_javascript_closure_compiler/BUILD and referenced by '//third_party:es6_collections'

My guess is that you need to do something like this

bazel clean --expunge

 

This will remove all downloaded repositories (i.e. the closure-compiler source code as well as the other remote dependencies) and rebuild them. I believe after that it should build cleanly.

That said I just ran this and it seems to be running against the last binary release of closure compiler ... not the current git repository ... which will not produce the same jar as I generated as the closure externs are outdated. I will need to poke around to figure out how to work arouns this.

That worked, thanks! 

--
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+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/5b43869e-8228-4649-a98b-8adab3bbe074%40googlegroups.com.

Re: [ANN] (Unofficial) Elemental2 2.24 release

On Wed, Jun 12, 2019 at 8:29 AM Peter Donald <peter@realityforge.org> wrote:

On Wed, Jun 12, 2019 at 7:31 AM John Huss <johnthuss@gmail.com> wrote:

Out of curiosity, how did you get this project to build successfully? 

When I try to build it I see this:

$ ./bazel_build_test.sh 

ERROR: /Users/john/repos/elemental2/third_party/BUILD:21:1: no such target '@com_google_javascript_closure_compiler//:externs': target 'externs' not declared in package '' defined by /private/var/tmp/_bazel_john/b729f51825638d22c4a92cfea6e4556d/external/com_google_javascript_closure_compiler/BUILD and referenced by '//third_party:es6_collections'

My guess is that you need to do something like this

bazel clean --expunge

 

This will remove all downloaded repositories (i.e. the closure-compiler source code as well as the other remote dependencies) and rebuild them. I believe after that it should build cleanly.

That said I just ran this and it seems to be running against the last binary release of closure compiler ... not the current git repository ... which will not produce the same jar as I generated as the closure externs are outdated. I will need to poke around to figure out how to work arouns this.

--

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+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/CACiKNc5xTgA7L7%3Dmz0-WNrjw0UUvM6aQLqiqPUhtquFj%2BC%2BRag%40mail.gmail.com.

Re: [ANN] (Unofficial) Elemental2 2.24 release

On Wed, Jun 12, 2019 at 7:31 AM John Huss <johnthuss@gmail.com> wrote:

Out of curiosity, how did you get this project to build successfully? 

When I try to build it I see this:

$ ./bazel_build_test.sh 

ERROR: /Users/john/repos/elemental2/third_party/BUILD:21:1: no such target '@com_google_javascript_closure_compiler//:externs': target 'externs' not declared in package '' defined by /private/var/tmp/_bazel_john/b729f51825638d22c4a92cfea6e4556d/external/com_google_javascript_closure_compiler/BUILD and referenced by '//third_party:es6_collections'

My guess is that you need to do something like this

bazel clean --expunge

 

This will remove all downloaded repositories (i.e. the closure-compiler source code as well as the other remote dependencies) and rebuild them. I believe after that it should build cleanly.

HTH

On Sunday, June 2, 2019 at 8:56:47 PM UTC-5, Peter Donald wrote:

Elemental2 provides type checked access to browser APIs for Java
code. This is done by using closure extern files and generating
JsTypes, which are part of the new JsInterop specification that
is implemented in both GWT and J2CL.

https://github.com/google/elemental2

This is an unofficial release to Maven Central under a different groupId.
Please don't bug the original authors. Versions are released on demand.

API Changes relative to Elemental2 version 2.23

elemental2-core:
  API Differences: https://jsinterop.github.io/api-diff/?key=elemental2-core&old=2.23&new=2.24
  - 39 non breaking changes.
  - 19 potentially breaking changes.
  - 49 breaking changes.
elemental2-dom:
  API Differences: https://jsinterop.github.io/api-diff/?key=elemental2-dom&old=2.23&new=2.24
  - 85 non breaking changes.
  - 68 potentially breaking changes.
  - 165 breaking changes.
elemental2-indexeddb:
  API Differences: https://jsinterop.github.io/api-diff/?key=elemental2-indexeddb&old=2.23&new=2.24
  - 1 non breaking changes.
elemental2-svg:
  API Differences: https://jsinterop.github.io/api-diff/?key=elemental2-svg&old=2.23&new=2.24
  - 1 breaking changes.
elemental2-webassembly:
  API Differences: https://jsinterop.github.io/api-diff/?key=elemental2-webassembly&old=2.23&new=2.24
  - 1 potentially breaking changes.

The complete set of Elemental2 API differences is available at

  https://jsinterop.github.io/api-diff/?key=elemental2&old=2.23&new=2.24

The Maven dependencies can be added to your pom.xml via

    <dependency>
      <groupId>org.realityforge.com.google.elemental2</groupId>
      <artifactId>${artifact-id}</artifactId>
      <version>2.24</version>
    </dependency>

where artifact-id is one of

* elemental2-core
* elemental2-dom
* elemental2-promise
* elemental2-indexeddb
* elemental2-svg
* elemental2-webgl
* elemental2-media
* elemental2-webstorage
* elemental2-webassembly

Hope this helps,

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+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/a7ddd14d-d72d-4f45-ab43-cecb13c267a0%40googlegroups.com.

--

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+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/CACiKNc6gDFQHANZ63-gq6vidL6oxyeSuWo%3DbcD4ErTke7h%3Dz3Q%40mail.gmail.com.

Re: [ANN] (Unofficial) Elemental2 2.24 release

Out of curiosity, how did you get this project to build successfully? 

When I try to build it I see this:

$ ./bazel_build_test.sh 

ERROR: /Users/john/repos/elemental2/third_party/BUILD:21:1: no such target '@com_google_javascript_closure_compiler//:externs': target 'externs' not declared in package '' defined by /private/var/tmp/_bazel_john/b729f51825638d22c4a92cfea6e4556d/external/com_google_javascript_closure_compiler/BUILD and referenced by '//third_party:es6_collections'

On Sunday, June 2, 2019 at 8:56:47 PM UTC-5, Peter Donald wrote:

Elemental2 provides type checked access to browser APIs for Java
code. This is done by using closure extern files and generating
JsTypes, which are part of the new JsInterop specification that
is implemented in both GWT and J2CL.

https://github.com/google/elemental2

This is an unofficial release to Maven Central under a different groupId.
Please don't bug the original authors. Versions are released on demand.

API Changes relative to Elemental2 version 2.23

elemental2-core:
  API Differences: https://jsinterop.github.io/api-diff/?key=elemental2-core&old=2.23&new=2.24
  - 39 non breaking changes.
  - 19 potentially breaking changes.
  - 49 breaking changes.
elemental2-dom:
  API Differences: https://jsinterop.github.io/api-diff/?key=elemental2-dom&old=2.23&new=2.24
  - 85 non breaking changes.
  - 68 potentially breaking changes.
  - 165 breaking changes.
elemental2-indexeddb:
  API Differences: https://jsinterop.github.io/api-diff/?key=elemental2-indexeddb&old=2.23&new=2.24
  - 1 non breaking changes.
elemental2-svg:
  API Differences: https://jsinterop.github.io/api-diff/?key=elemental2-svg&old=2.23&new=2.24
  - 1 breaking changes.
elemental2-webassembly:
  API Differences: https://jsinterop.github.io/api-diff/?key=elemental2-webassembly&old=2.23&new=2.24
  - 1 potentially breaking changes.

The complete set of Elemental2 API differences is available at

  https://jsinterop.github.io/api-diff/?key=elemental2&old=2.23&new=2.24

The Maven dependencies can be added to your pom.xml via

    <dependency>
      <groupId>org.realityforge.com.google.elemental2</groupId>
      <artifactId>${artifact-id}</artifactId>
      <version>2.24</version>
    </dependency>

where artifact-id is one of

* elemental2-core
* elemental2-dom
* elemental2-promise
* elemental2-indexeddb
* elemental2-svg
* elemental2-webgl
* elemental2-media
* elemental2-webstorage
* elemental2-webassembly

Hope this helps,

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+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/a7ddd14d-d72d-4f45-ab43-cecb13c267a0%40googlegroups.com.

Re: A Short GWT JsInterop Article for Beginners

On Tuesday, June 4, 2019 at 6:38:44 PM UTC+2, Jamal Romero wrote:

Thanks for sharing this!I would love to see also pointer or a reference available somewhere about the workings of Super Dev Mode in conjunction with the GWT compiler. Just a high level schematic or flowchart showing the flow and connections between these tools. What the codeserver does? So far if I follow the documented steps and nothing goes wrong during the compile and build all is good. But things start to get complicated when something goes wrong with the build tools.

7 years old next week, but still accurate afaik: http://blog.ltgt.net/how-does-gwts-super-dev-mode-work/

"Modern" SDM doesn't need anything specific in the gwt.xml files, and (major difference) no longer requires bookmarklets if you run CodeServer with -launcherDir (or use the DevMode launcher instead); it then generates a nocache.js file that does the same thing as the bookmarklet+compile button automatically on page load; but the overall architecture hasn't changed.

--
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+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/04fc61c1-c980-4639-8447-f1f59dad8b12%40googlegroups.com.

A Short GWT JsInterop Article for Beginners

Thanks for sharing this!I would love to see also pointer or a reference available somewhere about the workings of Super Dev Mode in conjunction with the GWT compiler. Just a high level schematic or flowchart showing the flow and connections between these tools. What the codeserver does? So far if I follow the documented steps and nothing goes wrong during the compile and build all is good. But things start to get complicated when something goes wrong with the build tools.

--
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+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/80c2c634-92e8-4167-83b2-eed4cb6dde4c%40googlegroups.com.

Re: GWT - Still Active ?

I can see why you would be frustrated ... and the GWT documentation is not particularly good. For us superdev+browser debugging mode "just works" as long as you do not change the linker. We don't have a massive app (~700K lines of client-side java source code across 37 directory trees + lots different jars) and generally we don't embed assets in javascript (which can degrade performance and increase js size).

These days we tend to debug in the browser rather than the IDE as historically IntelliJ struggled debugging large browser apps (although I believe this is no longer true) but we now find the browser debugger nicer to work with as it has all the other browser goodies.

I would recommend starting with a very simple app and seeing if you can get source maps and debugging working with that and then work from there. https://gitter.im/gwtproject/gwt is usually helpful and someone else was helped with this recently...

On Mon, Jun 3, 2019 at 11:13 PM Edson Richter <brviking@gmail.com> wrote:

Well, let's name few problems here:

1) Source maps: I don't know why, but Chrome can't find them. I've tried everything (I swear, I followed step by step every tutorial in earth - it just wont work. It may be because our folder structure that is bit more complex than those simple examples).

2) So, I'll forget and leave Java sources, and try to debug Javascript code. I've configured GWT compiler to produce "pretty", "non-obfuscated code". The generated javascript files are so big that chrome can't open it in developer mode. I just open an "empty" window. Nothing else.

Just to let you know, I'm using NetBeans - but this has nothing to do with the IDE I use - I'm just talking about debug javascript code.

I do consider myself a experienced engineer, having worked with several languages and systems - but I can't manage to get superdevmode working at all. May be just my system is currently too large.

Regards,

Edson

Em domingo, 2 de junho de 2019 15:01:04 UTC-3, Andrew Buck escreveu:

Debugging of both the server and client code works great. I'm not sure why it doesn't work for you. Client side debugging is done in the browser console using source maps that are automatically generated by the GWT compiler.

On Saturday, June 1, 2019 at 3:22:09 PM UTC-7, Edson Richter wrote:

This is my opinion (from a person with more than 30 years of experience in software enginnering), and I respect every other persons opinion - I'll just not put my eggs on this basket for another 8 years "just to see if it will get better".

Last year I had big issue with dates, because GWT has outdated DST tables (backend had correct dates, front end show everything one hour earlier!!!). This is just one little big problem for enterprise apps. I've asked support for this issue here, without any result (if someone had pointed me how to fix, I'll contribute code back to the project!). Finally, I had to write my own DST table and use "creativity" to overcome this "bug".

Not having support is also a big issue.

Not being able to debug the code anymore is another one.

More and more, GWT will get those "pieces" failing... and finally, it won't be usable anymore.

Regards,

Edson

Em sexta-feira, 31 de maio de 2019 11:41:27 UTC-3, Jamal Romero escreveu:

Out of curiosity, what would prevent someone still build projects based on current GWT 2.8.2 and keep using all the goodies? I think as of 2.8.2 it is future proof especially with a shift to jsinteop included in current release version? People even with current version took their own path and modernized part of GWT like the excellent gwt material & domino ui kit.

--
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+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/6f3dfaf6-ab6e-400a-a154-35b3c386422d%40googlegroups.com.

--

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+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit/CACiKNc7Oyn33n_MfPsQwTzAW31UP9fkyZ4CNbRTrZwS%2Bo%3DP9yw%40mail.gmail.com.