Re: GWT compiler keeps complaining about missing source files

[Peter Donald]

It looks like you put the source in the resources tree rather than in the
source tree. If you fix that then it may help

On Tue, Jul 26, 2022 at 6:21 PM mmo  wrote:

> In the code that I inherited my predecessors had decided to use a couple
> of Spring classes even in GWT client code.
> While I am not exactly enthused by this decision the referenced classes
> are - at least from my point of view - OK to use in GWT client code, since
> they are mostly interfaces or simple classes that don't pull too much of
> "Spring" into the client. So my aim is to leave the code as such unchanged
> as much as possible (trying to follow the "never change running
> code"-principle...).
>
> What I don't like, however, is that so far they had simply ignored the
> resulting GWT compile errors. I am thus now trying to correct the GWT
> settings such that this at least compiles without errors (i.e. that I can
> use the "strict" compiler setting).
>
> The initial error was that the Spring sources for GrantedAuthority,
> CredentialsContainer and a few more classes could not be found during GWT
> compilation.
> When I then added the Spring sources jar to the dependencies the GWT
> compiler ran havock and apparently tried to compile the ENTIRE Spring
> library. That was definitely NOT what I wanted.
> Next I tried to provide ONLY (copies of) those sources that are actually
> referenced in our GWT code, i.e. I added copies of those spring source
> files to our resources folder and try to direct the GWT compiler to use
> only those. Besides the mentioned java files I thus also added a
> GwtSpring.gwt.xml file which I reference from our application's
> ZHStRegisterJPWeb.gwt.xml like so:
>
>
> * 
> |
> +-* src
> | +-* main
> | | +-* java
> | | | +-* ch
> | | | | +-* zh
> | | | | | +-* registerjp
> | | | | | | +-* client
> | | | | | | | +-- ...
> | | | | | | +-* shared
> | | | | | | | +-* security
> | | | | | | | | +-- ZHStRegisterJPUser.java
> | | | | | | | | +-- ...
> | | | | | | | +-- ...
> | | | | | | +-* server
> | | | | | | | +-- ...
> | | |
> | | +-* resource
> | | | +-* ch
> | | | | +-* zh
> | | | | | +-* registerjp
> | | | | | | +-- ZHStRegisterJPWeb.gwt.xml   << our application's gwt-file
> | | | | | ...
> | | | |
> | | | +-* org
> | | | | +-* springframework
> | | | | | +-- GwtSpring.gwt.xml   << the added Spring gwt-file
> | | | | | +-* security   << copies of the referenced Spring source files
> below this folder
> | | | | | | +-* core
> | | | | | | | +-- GrantedAuthority.java
> | | | | | | | +-- CredentialsContainer.java
> | | | | | | | +-- ...
> | | | | | | | +-* userdetails
> | | | | | | | | +-- User.java
> | | | | | | | | +-- UserDetails.java
> | | | ...
>
> [Note: '*' are directories]
>
>
> The ZHStRegisterJPWeb.gwt.xml reads:
> ---
> 
> 
> 
> 
>
> 
> 
>
> ... further details omitted here ...
> ---
>
>
> The GwtSpring.gwt.xml reads:
> ---
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
>
> ... further details omitted here ...
> 
> ---
>
> However, the GWT compiler STILL complains that it can not locate the
> sources of GrantedAuthority and other Spring classes:
> ...
> [INFO]Tracing compile failure path for type
> 'ch.zh.ksta.zhstregisterjp.shared.security.ZHStRegisterJPUser'
> [INFO]   [ERROR] Errors in
> 'ch/zh/ksta/zhstregisterjp/shared/security/ZHStRegisterJPUser.java'
> [INFO]  [ERROR] Line 40: No source code is available for type
> org.springframework.security.core.userdetails.User; did you forget to
> inherit a required module?
> [INFO]  [ERROR] Line 94: No source code is available for type
> org.springframework.security.core.GrantedAuthority; did you forget to
> inherit a required module?
> ...
>
> Any idea why it doesn't find these files even though I now provide them
> explicitly?  What am I missing here?
>
> --
> 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/cffab879-e6ac-4aac-9fe1-cabcaac72d0an%40googlegroups.com
> <https://groups.google.com/d/msgid/google-web-toolkit/cffab879-e6ac-4aac-9fe1-cabcaac72d0an%40googlegroups.com?utm_medium=email_source=footer>
> .
>


-- 
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/CACiKNc4Gke1G1r%2B6F9qd0fZO%2BYkJXnpFZu2pEwMNf5-k%2BA1fog%40mail.gmail.com.

Re: [ANN] Akasha: Typed Browser API version 0.24 released

[Peter Donald]

Hi,

On Wed, Sep 15, 2021 at 6:27 PM Jens  wrote:

> really interesting work, but don't you think something like feature
> detection should be handled by a dedicated library like Modernizr for
> example? You likely want to check for vendor prefixed support when you do
> feature detection.
>

It depends upon the actual feature detection that is taking place. All the
akasha stuff does is check whether a property/function is present on an
object. So mostly it allows you to replace something like:

if (Js.global().has("indexedDB")) { /* perform logic requiring indexDB */ }

with:

if (WindowGlobal.isIndexedDBSupported()) { /* perform logic requiring
indexDB */ }

Largely Akasha assumes that browsers conform with the HTML Living document
(or whatever it is called) or the underlying spec and only presents the
prefixes that are declared as part of the living document. If you want to
perform more complex feature detection and polyfills (i.e. assigning
prefixed version to unprefixed property or adding polyfills or detecting
non-code related features such as css properties) then going with a
dedicated library is a better option.

Mostly we have found that our needs are served with pretty simple feature
detection but YMMV

-- 
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/CACiKNc6Yrhv1E_oMKiP8TBzMHOhHkj%2BULXNnh98Sup8NmG5rMw%40mail.gmail.com.

[ANN] Akasha: Typed Browser API version 0.24 released

[Peter Donald]

Akasha is a typed browser API layer that is always up to date with the
latest web specifications.

Several significant changes have been made since the 0.17 announced to this
group. The major changes include:


   - The ability to test for features before using the feature
   using methods such as WindowGlobal.isIndexedDBSupported(). The feature
   tests can be done dynamically at runtime or statically at compile-time. If
   done at compile time then the code can be compiled assuming that the
   feature is present or absent.
   - Global execution contexts other than "window" are natively supported.
   From a practical perspective this means it is relatively easy to use Akasha
   to write service workers and access the globals via ServiceWorkerGlobal.
   Similarly  there exists AudioWorkletGlobal and DedicatedWorkerGlobal
   etc. Within a GWT application, these global execution contexts may still
   require custom linkers but are much easier to write.

Other changes since the 0.17 release:

   - Update the WebGPU spec to the W3C Working Draft, 10 September
2021 version.
   This update resulted in a few minor name changes (i.e. the
   GPURequestAdapterOptions.forceSoftware member was renamed to
   GPURequestAdapterOptions.forceFallbackAdapter, GPUAdapter.isSoftware was
   renamed to GPUAdapter.isFallbackAdapter) as well as improved modelling
   of the types that contain constants (i.e. GPUMapMode no longer extends
   JsObject and is a final class in the java binding).
   - Update the Permissions spec to the W3C Working Draft 07 September
2021 version.
   This update resulted in a few minor changes to the PermissionsName
enumeration,
   the addition of the name attribute to the PermissionStatus type and the
   removal of the (unused) PermissionSetParameters.
   - Update the WebCodecs spec to the W3C Working Draft, 8 September
2021 version.
   This update resulted in many changes across several types. See the API diff
   for further details.
   - Migrate artifacts generated from the WebCodecs spec to the package
   codecs in the java binding.
   - Update the Visual Viewport API spec to the Draft Community Group
   Report 10 September 2021 version. This update resulted in the
   VisualViewport.segments attribute being made optional (or Nullable in
   the java binding).
   - Update the Web Share API spec to the W3C Working Draft 03 September
   2021 version. This update resulted in the addition of the
   Navigator.canShare(...) operation.
   - Update the WebXR Device API spec to the W3C Working Draft, 24 August
   2021 version. This update resulted in several changes, check the API
   diff for further details.
   - Update the HTML Living Standard spec to the 11 September 2021 version.
   This update resulted in several changes, check the API diff for further
   details. The most significant changes were the addition of oncontextlost
and oncontextrestored message handlers to several types and the
   addition of isContextLost() to contexts as appropriate.
   - Updates across several specifications resulted in PostMessageOptions being
   renamed to StructuredSerializeOptions.
   - Re-fetch the entire set of specifications ensuring that the required
   members in dictionaries appear in declaration order as initiated in version
   v0.15. This has resulted in the reordering of parameters in create() methods
   in the java binding to represent members in declaration order. This
   impacted the following types at a minimum: StaticRangeInit,
   XRInputSourcesChangeEventInit, RTCRtpCodecCapability,
   RTCRtpCodecParameters, RTCRtpContributingSource,
   RTCRtpHeaderExtensionParameters, RTCRtpParameters, RTCRtpSendParameters,
   RTCStats, RTCTrackEventInit, HkdfParams, Pbkdf2Params,
   AllowedBluetoothDevice, AudioProcessingEventInit, IIRFilterOptions,
   OfflineAudioContextOptions (as well as several other less used
   dictionaries)
   - Rename several union types to reflect intent, migrate the unions to
   the java package where they are used and convert unions to marker
   interfaces where appropriate. i.e. The union type
   IDBObjectStoreOrIDBIndexUnion was renamed to IDBCursorSource, converted
   to a marker interface and migrated to the akasha.idb java package. See
   the API diff for a full list of unions migrated.
   - Type the AudioTrack.kind attribute as an enumeration containing the
   set of valid values.
   - Add the Resize Observer spec at W3C First Public Working Draft, 11
   February 2020 version to the set of specs that are used to generate the
   browser API. This added the ResizeObserver type and related
   infrastructure.
   - Generate static types for global execution contexts of a service
   worker (i.e. SharedWorkerGlobal), a worker (i.e. DedicatedWorkerGlobal),
   a shared worker (i.e. SharedWorkerGlobal) and audio worklets (i.e.
   AudioWorkletGlobal).
   - Change the way the java binding generates unions so that methods of
   the form as[X]() and is[X]() exist for every component type X that 

[ANN] Akasha: Typed Browser API version 0.17 released

[Peter Donald]

Akasha is a typed browser API layer that is always up to date with the
latest web specifications.

Changes since the 0.14 release include:

   - Convert the following types into const enum representation to improve
   usability in the java binding. The types modified include:
   GPUBufferUsageFlags, GPUShaderStageFlags, GPUMapModeFlags,
   GPUColorWriteFlags and GPUTextureUsageFlags.
   - Fix the typing of the RegExpResult type so that it is typed as an Array in
   the akasha:gwt artifact but continues to be typed as RegExpResult for
   the akasha:j2cl artifact. A change introduced in version v0.11
    made it impossible to cast
   instances of this type in a GWT application without an unchecked cast
   because GWT was expecting a native javascript type of RegExpResult which
   is actually a closure type and not a javascript type.
   - Improve the typing of HTMLSelectElement.selectedOptions so accessing
   an element from the collection does not require casts.


   - Change JsObject.create(...), JsObject.getPrototypeOf(...) and
   JsObject.assign(...) operations so that they return an instance of type
   JsObject rather than an instance of type Object.
   - Explicitly override the HTMLOptionsCollection.item(...) and
   HTMLOptionsCollection.namedItem(...) operations inherited from
   HTMLCollection as the HTMLOptionsCollection interface guarantees that
   the return type is HTMLOptionElement and thus the usability of the
   generated classes and externs can be improved by encoding this constraint.
   - Correct the javadocs for the JsObject.valueOf_() operation.
   - Define the JsObject.toString_() operation.
   - Define the JsObject.hasOwnProperty() operation.
   - Define the JsObject.propertyIsEnumerable() operation.
   - Define the JsObject.isPrototypeOf() operation.
   - Update the way that the Dictionary factory methods are generated so
   that the parameters in the factory method are in the same order as they
   appear in the specification. For some specifications (i.e. WebGPU) the
   order of members has some semantic connotations (i.e. The r, g, b
and a members
   of the GPUColorDict should appear in that order in the generated code to
   respect the way the users of the API expect to arrange the data.)


To learn more about Akasha and get started:

https://github.com/akasha/akasha

Thanks!

The Akasha Team

-- 
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/CACiKNc42%2BatasoFKXHK%2BtNS7cey1za5sVOizuWLHpTieweiVOQ%40mail.gmail.com.

[ANN] Akasha: Typed Browser API version 0.14 released

[Peter Donald]

Akasha is a typed browser API layer that is always up to date with the
latest web specifications.

The release includes 75 non breaking API changes and 285 breaking API changes.

Changes in this release:

* Update the `Permissions` spec to the `W3C Working Draft, 13 July
2021` version. This updated the set of valid values for the
`PermissionName` enum.
* Update the `Resource Timing Level 2` spec to the `W3C Editor's Draft
15 July 2021` version. This corrected the type of the
`PerformanceResourceTiming.nextHopProtocol` attribute to match the
browser implementations but should have no visible impact on the
generated API.
* Update the `WebCodecs` spec to the `W3C Working Draft, 17 June 2021`
version. This updated the structure of the `EncodedVideoChunkMetadata`
dictionary that is used when defining an optional callback when
constructing an instance of `VideoEncoder`.
* Update the `Content Security Policy Level 3` spec to the `W3C
Working Draft, 29 June 2021` version. This refined the parameters
passed to the constructor of the `SecurityPolicyViolationEvent` type.
* Update the `CSS Object Model` spec to the `Editor’s Draft, 7 July
2021` version. This defined a constructor that can be used to create
instances of the `CSSStyleSheet` type.
* Update the `HTML Living Standard` spec to the `14 July 2021`
version. This added back valid definitions for the deprecated `Plugin`
and `MimeType` types as well as adding several minor updates to align
with features implemented in  modern browsers.
* Update the `WebGPU` spec to the `W3C Working Draft, 15 July 2021`
version. This change included renaming the context type (again!) from
`GPUPresentationContext` to `GPUCanvasContext` and ensuring it is
typed as an `OffscreenRenderingContext` and a `RenderingContext`.
Several other smaller changes were made to the spec and the chrome
canary browser version now aligns with this version of the spec.
* Annotate several union types with the `[MarkerType]` extended
attribute. This changed the way these types are implemented in the
java binding by converting them into marker interfaces. The union
types modified:
  - `CanvasImageSource`
  - `GPUBindingResource`
  - `GPUError`
  - `HTMLOrSVGImageElement`
  - `HTMLOrSVGScriptElement`
  - `ImageBitmapSource`
  - `ImageBufferSource`
  - `MessageEventSource`
  - `PasswordCredentialInit`
  - `ReadableStreamReader`
  - `ReadableStreamController`
  - `OffscreenRenderingContext`
  - `XRWebGLRenderingContext`
 This change also resulted in the `WindowProxy` typedef being
converted into a marker interface.

To learn more about Akasha and get started:

https://github.com/akasha/akasha

Thanks!

The Akasha Team

-- 
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/CACiKNc5RNVJqhGi9dqieiYafgtV-TLBteno3WEjwiaciM%3DmcVQ%40mail.gmail.com.

[ANN] Akasha: Typed Browser API version 0.13 released

[Peter Donald]

Akasha is a typed browser API layer that is always up to date with the
latest web specifications.

Changes in this release:

* Add the WebGPU spec with version W3C Working Draft, 12 July 2021 to the
set of specifications which the API is generated from. This specification
and the corresponding generated elements are marked as "Experimental" as
the specification is experimental and in developer trial mode and thus not
enabled by default in the major browsers.

To learn more about Akasha and get started:

https://github.com/akasha/akasha

Thanks!

The Akasha Team

-- 
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/CACiKNc600rDx2zRRd7X7VPoWJiovQHzd3s%2B7gaVqoP9Zu29qBQ%40mail.gmail.com.

Re: [ANN] Akasha: Typed Browser API

[Peter Donald]

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/CACiKNc7b4Bnc7hMb9W1zHnH5eOLqaQz-X_7yG%3DsHV0MnUrL8mw%40mail.gmail.com.

[ANN] Akasha: Typed Browser API 0.12 released

[Peter Donald]

Akasha is a typed browser API layer that is always up to date with the
latest web specifications.

Changes in this release:

* Add the `WebCodecs` spec with version `W3C Working Draft, 11 June 2021`
to the set of specifications which the API is generated from.
* Update the `Geolocation API` spec to the `W3C Working Draft 10 June 2021`
version. This improved typing and aligned with how browsers are
implementing the underlying javascript objects.
* Update the `Gamepad` spec to the `W3C Working Draft 08 April 2021`
version. This added event events for when gamepads are connected and
disconnected. This version also supports XR mappings.
* Update the `Web Bluetooth` spec to the `Draft Community Group Report, 17
May 2021` version. This improved the typing of several attributes and
exposed `manufacturerData` via the API.
* Update to the latest version of the `webgl` specifications. This
primarily resulted in supporting `VideoFrame` as a `TexImageSource`.
* Upgrade to the latest version of the `Web Authentication: Level 2
Recommendation` or `webauthn` specification finalized on `8 April 2021`.
* Update several web specifications with various fixes, clarifications and
API changes to more closely align with actual browser implementations.
These specifications included: `whatwg_html`, `whatwg_dom`,
`visual_viewport`, `screen_capture` and `cssom_view`.

To learn more about Akasha and get started:

https://github.com/akasha/akasha

Thanks!

The Akasha Team

-- 
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/CACiKNc4X8jpU8-1613F7hRtktLTkSin730PG%3DqX-tjoAcz4YOw%40mail.gmail.com.

Re: [ANN] Akasha: Typed Browser API

[Peter Donald]

On Thu, May 27, 2021 at 11:10 PM lofid...@gmail.com 
wrote:

> Great work Peter!
>
> I like the APIs from Akasha (former WebTack).
>
> If someone wants to compare the APIs from *Elemental2* and *Akasha*
> checkout this example:
>
>- Elemental2 in IndexDB:
>
> https://github.com/lofidewanto/jsinterop-simple-jsframework-example/tree/master/indexeddb-elemental2-example
>
>
>- Akasha in IndexDB:
>
> https://github.com/lofidewanto/jsinterop-simple-jsframework-example/tree/master/indexeddb-elemental3-example
>
> Oops - that was an super alpha version of the library and one of the APIs
has changed since then. I will send a PR to fix that up ;)

-- 
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/CACiKNc73aWm8pdYsFkN_7BX%2B8xFnQRHM7rb6qdsXdwpE6-X22w%40mail.gmail.com.

Re: [ANN] Akasha: Typed Browser API

[Peter Donald]

On Thu, May 27, 2021 at 5:52 PM Vassilis Virvilis  wrote:

> That supersedes elemental2. And the API is not the same (AFAICT) so we are
> going to have some inevitable churn in our code base.
>

The APIs are different but not substantially so - it took us a couple of
hours to convert our code bases which are mid-sized.


> Will this be endorsed by GWT as elemental2 replacement?
>

No idea - I also dont know who GWT is ;) Google has a large internal
closure code base so it is unlikely that they will adopt as the externs
differ. The akasha externs are more strongly typed to try and get slightly
better optimizability by CC and if you don't have an existing closure
codebase this is an easy win but not so if you have a large existing js
codebase.


> I tried to find the gitnub page for the project (found it:
> https://github.com/akasha/akasha) but https://github.com/AKASHAorg pops
> up.
>

I should have popped that in the email ;)

-- 
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/CACiKNc5X6EnxcqUyEgSY07YrJWxcggnnV1qC3dEAir1Y%3DDJGbw%40mail.gmail.com.

Re: GWT Front-end on different server than Back-end

[Peter Donald]

Hi,

On Thu, May 27, 2021 at 3:56 PM Bruno Borges  wrote:

> I've been reading the GWT documentation and trying to understand the
> deployment model of the front-end, especially for PWA apps (but not
> exlucisvely!) to find a scenario where GWT front-end could be deployed to
> Azure Static Web App service (to serve the static content), and then the
> back-end APIs deployed as an Azure Function.
>
>  I wonder if anyone has played with the general idea of deploying
> front-end on a different server (Nginx/Apache) only to serve the static
> content, and the actual API back-end to another.
>

This is the way we deploy most of our applications and it is not really any
different from how you have to do it for any other javascript context and
the standard security concerns. The only tricky part really is working with
your transport layer. If you are using GWT-RPC (which I recommend against)
then you are stuck updating the server and the client at the same time if
you ever change the API in a backward incompatible manner and you have to
do some ugly configuration of base url of services. Assuming the Azure
Function can be accessed as http calls then you should be fine.

If you are using the "builtin" support for separating our resources
(i.e. GWT.getHostPageBaseURL(), GWT.getModuleBaseForStaticFiles(),
GWT.getModuleBaseURL())
for accessing assets then you may find some things break for local
development when GWT.getModuleBaseForStaticFiles() !=
GWT.getModuleBaseURL() as GWT.getModuleBaseForStaticFiles() does not take
into account the debug hooks but this is pretty rare scenario.

Is there a specific problem that you are having?

-- 
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/CACiKNc5K_0QrVz-RoMiEH7FYYBjdx7XAsBsz_u1%3DH2So3etOyA%40mail.gmail.com.

[ANN] Akasha: Typed Browser API

[Peter Donald]

with new Web APIs as they
come out with minimal fuss compared to past approaches such as the
handwritten DOM adapters, elemental or elemental2 libraries and we think
Akasha is nearing a time where it is suitable for adoption in a broader
context.
-- 
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/CACiKNc4sfFH-JWYnU2OLpEYtC%3Djp4z2k3w80rLDjJRUBhNScBQ%40mail.gmail.com.

Re: [gwt-contrib] Asking for decision on DevMode embedded Jetty support

[Peter Donald]

On Wed, Apr 14, 2021 at 5:23 AM eliasbala...@gmail.com <
eliasbala...@gmail.com> wrote:

> This is something I have been pushing my teams to do.
>
> We keep out GWT apps very simple, just "CRUD" so that they can run in
> DevMode but also de-couple from business logic and background tasks as much
> as possible, a microservices approach.
>
> If that is not enough we equip the GWT app strictly with front-end code,
> we keep the back-end services in a separate application and bridge the two
> with a remote API (e.g. REST+JSON).
>
> I believe this is what is implied by "pure GWT frontend"
>
> On Tuesday, 13 April 2021 at 20:14:16 UTC+1 t.br...@gmail.com wrote:
>
>> What do you mean by "pure GWT frontend" ? Do you need servlets ? Or
>> serving only static files would be OK?
>> Because the problem is with server side code.
>>
>
One thing you may want to consider is actually publishing all resources as
"" assets in your gwt modules. That way you can sneakily use the
codeserver to host your launcher page and everything else and only need the
codeserver. As long as you don't not have massive numbers of local assets
or large size it works quite well. In short we put the launcher html inside
public and use the "/recompile-requester/mygwtmodule" as the url for the js
code.

So in a typical GWT only microservice frontend we end up with 3 GWT modules
(1 common, 1 for local development and 1 for production) that declare 1
public dir each. In each public dir is the appropriate assets (common
assets in common public dir, dev launcher in development public dir,
production launcher in production public dir). Then you can just start
local code server and run the app from in it ;)

For example:

* Common GWT module:
https://github.com/react4j/react4j-heart-rate-monitor/blob/master/src/main/java/react4j/hrm/HeartRateMonitor.gwt.xml
* Development GWT module:
https://github.com/react4j/react4j-heart-rate-monitor/blob/master/src/main/java/react4j/hrm/HeartRateMonitorDev.gwt.xml
* Production GWT module:
https://github.com/react4j/react4j-heart-rate-monitor/blob/master/src/main/java/react4j/hrm/HeartRateMonitorProd.gwt.xml

* Common public assets:
https://github.com/react4j/react4j-heart-rate-monitor/tree/master/src/main/java/react4j/hrm/public/common
* Development GWT Asset (just a launch page):
https://github.com/react4j/react4j-heart-rate-monitor/tree/master/src/main/java/react4j/hrm/public/dev
* Production GWT Asset (just a launch page):
https://github.com/react4j/react4j-heart-rate-monitor/tree/master/src/main/java/react4j/hrm/public/prod

Often we can just use these as is but sometimes we do put a proxy in it
(when they use host relative services/links/whatnot, SSL or other
capabilities). Seems to work fine for us ;)

-- 
Cheers,

Peter Donald

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

Re: Superdevmode and ReferenceErrors

[Peter Donald]

Hi,

On Thu, Feb 25, 2021 at 6:51 AM Stik  wrote:

> Occasionally when running under SDM in Eclipse I will get a
> "ReferenceError: _g$ is not defined" from the browser.   The usual
> "fix" is to rename the symbol in question, reload, and the issue is gone.
>  If i then rename it back to what it used to be called, so nothing has
> actually changed, it remains fixed.


If it is a symbol that is a method-reference or containing in a lambda then
it is a known problem. I believe there was some guidance from google at one
stage how to diagnose/fix the problem but no one ever followed it up. I
usually just do what you do ;)

-- 
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/CACiKNc6opoXa2SNChOCuhzqcetSAk69U-AcAr2wSnYBkk%2Bpfiw%40mail.gmail.com.

Re: Our 10+ year journey with GWT (+ job opening)

[Peter Donald]

On Tue, Jan 26, 2021 at 5:08 AM Vassilis Virvilis  wrote:

> Thanks for the insightful reply. You seem to focus on optimization which I
> agree is a worthy target.
>

It is the limiting factor when building at large scale.


> I was focusing on development practices and reuse. For example I have
> created bindings for jQuery. I would love to just use somebody else's
> bindings. But here is the thing. I didn't need jQuery for me or my
> application. I needed it for DataTables.net. I created bindings for them
> too and jQuery was a requirement.
>
> Having done the exercise I believe that it is impossible to reuse jQuery
> from another source and DataTables.net from another. They have to be
> developed in sync or at least first the jQuery and then the DataTables.net
> bindings. It looks like a huge waste of effort to me and not very scalable
> regarding ecosystem growth if every gwt developer develops his own bindings
> every time.
>
> But what would be a proper solution here? Create a mega project to
> coordinate smaller bindings only projects? Provisions have to be taken for
> packaging and namespaces in order to avoid collisions and a ton of other
> things that are massive headaches.
>

It could work ... and if you have the time it is worth trying. Seeing if
you can gather support on the chat channel seems like the best way forward.
Good luck!

I guess my concern is that if the binding is not generated automatically
from the types in the source js project then the binding will be an
opinionated mapping of a subset of the js API that made sense to the author
or their use-case. If that mapping makes sense for enough other people then
I can imagine that it is worth collaborating with other people to develop
and maintain it over time. We maintain a fairly opinionated binding of
react and (several) bindings for keycloak.js but other than those two
libraries, any binding we have tends to be project specific because the
mapping focuses on small subsets of the relevant libraries.

-- 
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/CACiKNc6kuakQ9epWFAW82x8hnzJHoZQ2JoSmx8PeWLBqBYSTGQ%40mail.gmail.com.

Re: Our 10+ year journey with GWT (+ job opening)

[Peter Donald]

On Sun, Jan 24, 2021 at 8:17 PM Vassilis Virvilis  wrote:

> I asked here one or two times but IIRC the answer was there should be an
> automatic way to import js libraries. Maybe through DefinitelyTyped
> typescript https://github.com/DefinitelyTyped/DefinitelyTyped
> definitions? not sure if it is even possible.
>

There are a few problems that we became aware of quickly. To get dead code
elimination / minimization / optimization you really need to have a
consistent type model for all code within an output target. When we
experimented with this approach we used the same model that I believe is
used inside google. i.e. closure typed javascript is the definitive
representation, java is compiled to closure compiler annotated js via j2cl,
typescript is compiled is compiled to closure annotated js via tsickle,
jsinterop-generator converted closure annotated code into jsinterop
annotated java and then closure compiler was responsible for
optimization/assembly.

However you could rarely take an off-the-shelf typescript library and
import it into the mix as tsickle was usually on an older version of
typescript or the library was not completely typed or it used some
typescript features not supported by tsickle. This usually meant that the
library had to be patched and/or was not stripped of unused code and/or was
not optimized etc. We often ended up writing our own library event when
there was an equivalent available in the js ecosystem. (Which is no
different to what we have to do with java-to-js solutions but generally the
tooling available for long term maintenance is less good for js than for
java). Even when all the stars aligned we often found that closure could
not detect some code was unused due to the way js works and so we had to
patch code so we could eliminate unused code by changing how we used a
library. This is probably one of the reasons we ended back writing code in
java. We could not use the existing ecosystem and had to work with a
limited ecosystem if we wanted high-quality, minimized code .

So while it may be possible to use existing libraries from typescript
and/or DefinitelyTyped, unless the typing is 100% then bugs will creep in
and you won't be able to eliminate unused code. Where we are using js
libraries we tend to write our own bindings or we just rewrite the
functionality we need in java and get all the benefits provided by the
compiler.

I am not aware of such a way or at least a roadmap. Do you think that with
> the WASM target the jsinterop binidings will be more automatic / easier /
> less manual?
>

WASM is still a moving target and I haven't tracked it of late ... but
there were specs that defined the inter module API which would be trivial
to automatically generate bindings for. There was also primitive tooling
that did dead code elimination and optimization between modules (by
essentially removing the unused API ingress and re-running intra module
optimizer to strip dead code) but I don't know how good it is. I don't know
if it will ever be possible to do whole application optimization and
combining into a single module but I am not sure that will be much of a
problem in practice. At least not for languages that do not have much
overhead during compilation.

Anyhoo - it will be an interesting time regardless.

-- 
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/CACiKNc7Z%3DC3F0cXTggkPhPFeh8%3D5M%3DYpE45%3DWfnCWJzSaBFGgw%40mail.gmail.com.

Re: Our 10+ year journey with GWT (+ job opening)

[Peter Donald]

;>> GWT 2.6.1 + Eclipse 4.8.  Tomcat8 + MySQL5.7  + Java8 + JasperReport
>>>>>> my next 10 years plan is  move to TypeScript + VueJS.
>>>>>> On Monday, 4 January 2021 at 23:37:53 UTC+7 Alexander Bertram wrote:
>>>>>>
>>>>>>> Nice to hear from everyone!
>>>>>>>
>>>>>>> Here's to the next ten years :-)
>>>>>>>
>>>>>>> Best wishes for 2021,
>>>>>>> Alex
>>>>>>>
>>>>>>> On Tuesday, December 22, 2020 at 10:22:08 AM UTC+1 Segun Razaq
>>>>>>> Sobulo wrote:
>>>>>>>
>>>>>>>>
>>>>>>>> I've been using GWT for 7+ years (with appengine java backends) and
>>>>>>>> actively looking for a job. I'll push my resume.
>>>>>>>>
>>>>>>>> Thanks
>>>>>>>> On Monday, 21 December 2020 at 15:24:19 UTC+1 aka...@gmail.com
>>>>>>>> wrote:
>>>>>>>>
>>>>>>>>> We are in times where working remotly id actually a good option.
>>>>>>>>>
>>>>>>>>> On Monday, December 21, 2020 at 4:19:13 PM UTC+2 David Nouls wrote:
>>>>>>>>>
>>>>>>>>>> Hi Alex,
>>>>>>>>>>
>>>>>>>>>> Same story here. I have been working with GWT since it first came
>>>>>>>>>> out. For our current project we again opted for GWT because we share 
>>>>>>>>>> a lot
>>>>>>>>>> of code between client and server and productivity is high.
>>>>>>>>>>
>>>>>>>>>> I’m not available at the moment (maybe end of next year)… but
>>>>>>>>>> living in Belgium/Leuven I don’t think that is doable. Relocation is 
>>>>>>>>>> not an
>>>>>>>>>> option. Good luck finding people, there are not a lot on the market.
>>>>>>>>>>
>>>>>>>>>> Groeten,
>>>>>>>>>> David
>>>>>>>>>> On 20 Dec 2020, 16:16 +0100, 'Alexander Bertram' via GWT Users <
>>>>>>>>>> google-we...@googlegroups.com>, wrote:
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> Dear all,
>>>>>>>>>>
>>>>>>>>>> I hope this email isn't too off-topic, but I wanted to share an
>>>>>>>>>> opening for a job on our team with a large GWT component.
>>>>>>>>>>
>>>>>>>>>> https://jobs.bedatadriven.com/software-engineer
>>>>>>>>>>
>>>>>>>>>> The first version of our product, ActivityInfo, a data collection
>>>>>>>>>> and analysis platform for humanitarian relief, was built with GWT, 
>>>>>>>>>> GXT and
>>>>>>>>>> Google Gears in 2009 and seriously would not have been possible 
>>>>>>>>>> without
>>>>>>>>>> GWT.
>>>>>>>>>>
>>>>>>>>>> In 2018, nearly 10 years later, we looked at the amazing js
>>>>>>>>>> ecosystem and considered moving to Typescript or Elm.
>>>>>>>>>>
>>>>>>>>>> Instead, we decided to keep the bits that we loved about GWT: the
>>>>>>>>>> typesafety, code-reuse with the server, i18n, code splitting, 
>>>>>>>>>> linkers, and
>>>>>>>>>> the amazing compiler, and add SCSS for styles and our own port of 
>>>>>>>>>> Preact +
>>>>>>>>>> rxJava-like reactivity for dom manipulation using Elemental2.
>>>>>>>>>>
>>>>>>>>>> Three years after the start of ActivityInfo 4.0 we couldn't be
>>>>>>>>>> happier with the choice, and are more productive than ever.
>>>>>>>>>>
>>>>>>>>>> If you're an experienced GWT developer that would enjoy the
>>>>>>>>>> challenge of a working on a modern GWT codebase, I hope you'll 
>>>>>>>>>> consider
>>>>>>>>>> joining our team!
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> Best,
>>>>>>>>>> Alex
>>>>>>>>>>
>>>>>>>>>> --
>>>>>>>>>> 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/46240bd9-f716-4448-a481-acfc87229f8fn%40googlegroups.com
>>>>>>>>>> <https://groups.google.com/d/msgid/google-web-toolkit/46240bd9-f716-4448-a481-acfc87229f8fn%40googlegroups.com?utm_medium=email_source=footer>
>>>>>>>>>> .
>>>>>>>>>>
>>>>>>>>>> --
> 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/2c7b6eec-67cd-4361-8777-18490db3dba7n%40googlegroups.com
> <https://groups.google.com/d/msgid/google-web-toolkit/2c7b6eec-67cd-4361-8777-18490db3dba7n%40googlegroups.com?utm_medium=email_source=footer>
> .
>
> --
> 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/25324b20-e0d8-4a7b-a292-9782066fdf1b%40Spark
> <https://groups.google.com/d/msgid/google-web-toolkit/25324b20-e0d8-4a7b-a292-9782066fdf1b%40Spark?utm_medium=email_source=footer>
> .
>


-- 
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/CACiKNc4QQnbo4cJARmYT_fPWEAJ_iK6o8oXiJi0Z%3DT7cVgn%3D5g%40mail.gmail.com.

Re: app not reload from android chrome

[Peter Donald]

There's a library that manages this for you at
https://github.com/realityforge/gwt-cache-filter which will set the caching
parameters as required.

On Mon, Jan 11, 2021 at 9:35 PM pierre...@gmail.com 
wrote:

> Hi,
> I have a gwt app developed with gwt-material but I assume it's not
> relevant for this problem.
> The app is served by Tomcat.
> Everything is fine with PC/iphone/iPad but with android after deploying a
> new app, the old one is still showned. The nocache mecanism doesnot work in
> android chrome.
> Removing the cache works, but I cannot asks that to my users.
>
> Any hint how can I force the browser  to reload the app from server for
> theses mobiles ?
> Thanks in advance
> Pierre
>
> --
> 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/cf24a086-3c9e-4488-9ab8-200402a38b4bn%40googlegroups.com
> <https://groups.google.com/d/msgid/google-web-toolkit/cf24a086-3c9e-4488-9ab8-200402a38b4bn%40googlegroups.com?utm_medium=email_source=footer>
> .
>


-- 
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/CACiKNc4bZXnCsF8mU-FRzrQxcWh0aAWcDBmuJQyDXzbJMAd%2BvA%40mail.gmail.com.

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

[Peter Donald]

On Mon, Oct 19, 2020 at 1:56 AM lofid...@gmail.com 
wrote:

> Thanks Craig for the info...
>
> I'm not familiar with React (only Hello World )
>
> Can you integrate React with these GWT React frameworks? So write your
> components in Java and integrate them back into React JavaScript?
>
>- https://github.com/GWTReact/gwt-react
>- https://github.com/react4j/react4j.github.io
>
> I don't know whether it is possible?
>

It may be possible in react4j to publish a java component as a react
component but not without significant overhead/boilerplate. It is also
possible to consume a js react component from within react4j with a little
overhead and we built some of our early apps like this. However, react4j's
sweet spot is when the majority of the application is written in java.

With gwt-react it is much easier to both consume js components and publish
java components ... except for the normal constraints of publishing java to
js. My guess is that the sweet spot for gwt-react is for applications that
combine js components into a java app but I have never used it in anger.


-- 
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/CACiKNc6x9_3VoLj7ikUs8M5Fppq3f%2Bwed1sgb1OHtdR3e_J6fw%40mail.gmail.com.

Re: GWT SDM hanging on recompiles?

[Peter Donald]

Are you on GWT 2.9.x? I have seen this intermittently after upgrading
to GWT 2.9.x. Unfortunately I always forget to get a thread dump to
see where it has got stuck.

FWIW We run under JDK8, with no server component from IntelliJ IDE.

On Fri, Aug 7, 2020 at 6:18 AM Michael Conrad  wrote:
>
> Greetings everyone.
>
> Hopefully someone can tell me what I need to change.
>
> When running SDM via Gradle, after so many recompiles, it will stop with 
> something similar to:
>
>  GET /recompile/gwt
>Job com.newsrx.ButterAdmin_1_7
>   starting job: com.newsrx.ButterAdmin_1_7
>
> and never actually do the compile.
>
> A non-hung recompile looks like:
>
> GET /recompile/gwt
>Job com.newsrx.ButterAdmin_1_6
>   starting job: com.newsrx.ButterAdmin_1_6
>   binding: locale=default
>   binding: user.agent=safari
>   Compiling module com.newsrx.ButterAdmin
>  Unification traversed 876 fields and methods and 394 types. 17 are 
> considered part of the current module and 26 had all of their fields and 
> methods traversed.
>  Compiling 1 permutation
> Compiling permutation 0...
> Linking per-type JS with 17 new/changed types.
> Source Maps Enabled
>  Compile of permutations succeeded
>  Compilation succeeded -- 2.086s
>   Linking into 
> /home/michael/git/ButterAdmin/ButterAdmin-client/build/gwt/work/com.newsrx.ButterAdmin/compile-8/war/gwt;
>  Writing extras to 
> /home/michael/git/ButterAdmin/ButterAdmin-client/build/gwt/work/com.newsrx.ButterAdmin/compile-8/extras/gwt
>  Link succeeded
>  Linking succeeded -- 0.186s
>   2.475s total -- Compile completed
>
>
> To fix the issue I have to kill it and start it over.
>
> Pointers as to what might be causing this?
>
> AdoptOpenJDK11 -> with -release 8.
>
> --
> 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/b4f358f7-3783-db02-e31b-be305b5e9119%40newsrx.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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit/CACiKNc6c%2Bpp0VdqOujvPN4vcAkYSxusEuBwkOgUDtrOsBxWAaQ%40mail.gmail.com.

Re: [gwt-contrib] Elemental2-1.1.0 released

[Peter Donald]

Great work - thanks!

On Fri, Jun 19, 2020 at 10:47 AM Julien Dramaix
 wrote:
>
> Hi,
>
> We released and pushed to maven central a new version of Elemental2 today: 
> Elemental2-1.1.0.
>
> Please refer to the github page for an explanation on how to use it.
>
> Summary of fixes/improvements included in this release:
> - Elemental2 have been generated from the last version of closure extern 
> files. Please refer to this page for the list of improvements/fixes on those 
> extern files.
> - Fix elemental2-webassembly maven pom file to correctly depend on 
> elemental2-dom
> - Update jsinterop-annotations dependency to jsinterop-annotations 2.0.0.
> - Fix uncheckedCast overlay call when parameter is a varargs.
>
> Please report any issues to https://github.com/google/elemental2/issues
>
> -Julien
>
> --
> You received this message because you are subscribed to the Google Groups 
> "GWT Contributors" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/google-web-toolkit-contributors/a41bdcc6-48de-4b84-9ea7-5dc453fb4bb2o%40googlegroups.com.



-- 
Cheers,

Peter Donald

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

Re: [gwt-contrib] Re: Ant, ZipScanner, and GWT

[Peter Donald]

On Sat, Jun 13, 2020 at 11:11 AM Colin Alworth  wrote:
> If I understand you, that is what I'm doing - I only the required 18 classes 
> (with some members removed so that I don't need more than that), and am just 
> seeking an opinion other than my own as to whether it is better to checked 
> them straight into gwt as com.google.gwt.thirdparty.ant... classes, or into a 
> standalone jar (to be clearer that this is external work+license, and have a 
> pointer to where that work originated).

If it was me, I would just pull the source in and place it in
com.google.gwt.util.tools.zipscanner and flatten all the files into
that package. No need to mark it as vendored as you never intend to
pull from upstream again as they have moved in an incompatible
direction. They are license compatible as both Apache-2.0 and as long
as the GWT project does not have a policy against including code that
is copyright to another organization in source tree then that seems
like the easiest option going forward.

-- 
Cheers,

Peter Donald

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

Re: [gwt-contrib] Re: Ant, ZipScanner, and GWT

[Peter Donald]

ject umbrella.
>
> Finally, is there any objection to staying with 1.6.5, or should I see if we 
> can use a later version, or update GWT's internals to use the new behavior 
> around leading slashes, etc?
>
>
> --
> You received this message because you are subscribed to the Google Groups 
> "GWT Contributors" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/google-web-toolkit-contributors/7e0c1856-2835-4254-a8ed-b73a03de1ea7o%40googlegroups.com.
>
>
> --
> You received this message because you are subscribed to the Google Groups 
> "GWT Contributors" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/google-web-toolkit-contributors/fd913f25-f6a0-4820-ad96-ff95a064cdb0%40www.fastmail.com.



-- 
Cheers,

Peter Donald

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

Re: [ANN] JRS gwt-time 1.4.6 release

[Peter Donald]

Great work!

On Mon, May 4, 2020 at 3:41 PM foal  wrote:
>
> Hi,
>
> JRS gwt-time 1.4.6 was released - details 
> https://github.com/foal/gwt-time/releases/tag/1.4.6
>
> Check readme.md, I added a new section "Unimplemented or partial implemented 
> features" 
> (https://github.com/foal/gwt-time#unimplementet-or-partial-implemented-features)
>
> Best,
> Stas
>
> --
> 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/c18f7bb0-8878-43ec-a017-0ccedf43692b%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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit/CACiKNc58%3DBV5pQFm1qty1BWN1G8S2GkR5gPF5AVwvPqkaRkzhg%40mail.gmail.com.

Re: GWT - Angular/React Migration & Integration

[Peter Donald]

FWIW A couple of years ago we decided to move away from GWT and move
to react+mobx+typescript under the assumption we could produce apps
faster. After several months in that world, we came back to the GWT
world. Mostly this was due to productivity.

Except for some legacy applications we don't use classes from the GWT
runtime and instead use react and arez (a mobx alternative) - which is
much more productive. We still have somewhat slow refresh times for
large apps but our prototyping with J2CL seemed to indicate even that
would go away and in fact, be faster than the equivalent in JS land
(!). JS still has the advantage of a larger set of libraries and
framework-specific speed Improvements (i.e. hot reloading in react) we
certainly have no interest in going back ;)

On Tue, Apr 28, 2020 at 10:33 AM Thomas  wrote:
>
> Thanks Howard.
>
> Definitely not planning a deep integration...
>
> Interesting insight about GWT vs JS in terms of productivity. GWT always felt 
> 'enterprise' to me with large apps in mind.
>
> --
> 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/78d169e4-7b2a-4b4a-840f-7626faed24e2%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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit/CACiKNc63bbN6msth6jjfBOTq16XVXuUJtK-qMFg-XwZDme7sFA%40mail.gmail.com.

Re: (Unofficial) Elemental2 2.27 question

[Peter Donald]

On Fri, Apr 24, 2020 at 11:15 PM Vassilis Virvilis  wrote:
> I updated to Elemental 2.27 from 2.25 and
> a) Element has no children property

I haven't got an IDE handy but that is what I would expect. IIRC
Element extends Node and Node has a read only attribute childNodes ...
at least according to the spec WebIDL AFAIK. I would have to
investigate the closure externs to figure out why it used to have a
children property.

> b) it depends on jsinterop-annotations-1.0.2.jar but 
> jsinterop-annotations-2.8.2-v20191108.jar exists. Is 
> jsinterop-annotations-2.8.2-v20191108.jar a J2CL thing?

1.0.2 is released by google so I just preferred the use of that as I
expect other libraries would depend on this jar and having a shared
coordinate reduces the likelihood of ending up with two copies of it
in the project class path

-- 
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/CACiKNc6famF88h-Vsjqdta%2BQ4GgtvqUJm1kLBPtxUkyeGhLyLA%40mail.gmail.com.

Re: [ANN] Sting v0.13 (Beta) release

[Peter Donald]

On Sun, Apr 5, 2020 at 7:55 PM foal  wrote:
> Does Sting support the GWT "Code Splitting"? 
> (http://www.gwtproject.org/doc/latest/DevGuideCodeSplitting.html), I tried to 
> migrate from GIN to the Dagger, but it was the main issue why I still use the 
> GIN.

Sting does not do it much differently than Dagger. It has been a while
since we used code-splitting but I believe all you would need to do is
use an interface to define the service and instantiate the service
implementation behind a split point from a provider method in a
@Fragment annotated type. (A similar approach should be achievable in
dagger but putting the split point in a @Provides annotated method in
a @Module but I have not checked daggers generated code to make sure
it would still work)

So, in theory, it should be fine but I have yet to try it myself ;)

-- 
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/CACiKNc6Sy8yW28wXt%2BV4mEG%2B4E6it7Gif7RVeqhZBH-oavByOQ%40mail.gmail.com.

[ANN] Sting v0.13 (Beta) release

[Peter Donald]

Sting is a fast, easy to use, compile-time dependency injection toolkit.
If you are familiar with Dagger, it is a replacement for Dagger that is
more optimized for the web context and GWT/J2CL.

We have been developing Sting for a while as we were not satisfied with
existing solutions but we have recently reached a point where we have
replaced all of our existing dependency injection solutions (GIN,
Dagger2 and some home-grown variants) with Sting and we think it is
ready for other people to give it a try. So we are looking for feedback
from anyone who is interested in giving it a try.

We have set up a documentation site at

  https://sting-ioc.github.io/docs/overview.html

But to get a feel for what the code looks like. A component is
defined by adding the @Injectable annotation to the class such as:

  @Injectable
  class MyFancyService { ... }

However, we also support a @Named annotation and @Typed annotation
that is similar in practice to the same-named annotations in CDI
applications that add a qualifier to a component or control the types
with which a component is published. We also support an @Eager
annotation to ensure a component is instantiated when the injector is
constructed.

We also have the equivalent of daggers modules in the form of
fragments where you can programmatically create components by writing
code such as GWT.create(MyBackendServiceAsync.class)

So why choose Sting over something like Dagger? We did write up a
comparison at

  https://sting-ioc.github.io/docs/dagger.html

However, it is a little blunt and I will probably soften the points in
it a little (it was written for an internal audience initially).
The main reason to adopt Sting is that it is easier to use and it
produces smaller, faster and easier to optimize code.

Anyhoo, if anyone is looking for a dependency injection framework,
here is another to try and we would really appreciate the feedback.

Thanks,

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/CACiKNc5PTU7vEhLJvLdUx67xtJaHVQkQrpW3d2vwOKaYpbu3gA%40mail.gmail.com.

gwt-serviceworker-linker

[Peter Donald]

Hi,

With the pending removal of Appcache from the major browsers, I have
deprecated the Appcache libraries I maintained and put together an
extremely minimal service-worker linker for GWT that did something roughly
similar to Appcache if anyone needs it.

It is available at:

https://github.com/realityforge/gwt-serviceworker-linker

-- 
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/CACiKNc41vcRwZVG8AZKZx46znR26UVYV8mvRy9CNBB4hguTvzQ%40mail.gmail.com.

Re: Is GWT 3.0 /GWT 2.9 dead?

[Peter Donald]

On Thu, Feb 20, 2020 at 8:58 AM Jens  wrote:

>
> I hope GWT 2.9 is out "soon", because we're planning to switch to Java 11
>> in the coming months, and it would be a burden to maintain a separated Java
>> version only for the frontend part (been there, done that with Java 8).
>>
>
> Java 11 syntax additions are available in GWT snapshot releases:
> https://gwt-review.googlesource.com/c/gwt/+/21540
>

And in an unofficial release in Maven central ;)

https://groups.google.com/forum/#!topic/google-web-toolkit/qmwiMVofhR8/discussion

-- 
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/CACiKNc56TbpZfpGTfdF%2BWyn5Pf41d-WZB2nDkkMeZBNRke2baw%40mail.gmail.com.

Re: [ANN] (Unofficial) GWT 2.8.2-v20191108 release

[Peter Donald]

On Tue, Jan 14, 2020 at 8:29 PM Alexandre Schmit 
wrote:

> This version is unofficial, why?


Because I am not on the GWT team and did not go through the release process
(which mostly involves making sure all examples work)


> And what is the code source base?
>

It is just the last successful build on the master branch of the official
GWT repository on the date that the release occurred.

-- 
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/CACiKNc6Vz3Fif2nx7zfCdPCaqzwmUKzVXC%3DBtZTe9Azg%3D6Q%2BLg%40mail.gmail.com.

Re: [ANN] (Unofficial) GWT 2.8.2-v20191108 release

[Peter Donald]

On Sat, Jan 11, 2020 at 5:45 PM David Nouls  wrote:

> Has it only been 3 years ? I also don’t understand why dwt devs are so out
> of touch with their user base. Nobody will take gwt 3 as a serious option.
> All old GWT apps will have been migrated to other toolkits by the time it
> gets released.
>
> Why are these incremental changes not officially released ? Is there no
> trust in the quality of these changes ? Are the unit tests not good enough
> to  ensure stability ?
>

I think it is largely because there is no one volunteering to do the
work. There are enough organizations that use master of GWT (including
google) so it is plenty stable. Google uses GWT master and has no need to
package a release. This is largely why I ended up packaging a release.

-- 
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/CACiKNc4aXtNr25F0XQt9SEVkEAKWhNvm3UJjNNA3d-WPJJ1iVA%40mail.gmail.com.

Re: [ANN] (Unofficial) GWT 2.8.2-v20191108 release

[Peter Donald]

On Wed, Jan 8, 2020 at 12:38 PM Hristo Stoyanov 
wrote:

> Hi Peter,
> I tried to use your GWT distro, and although I see that I get the right
> artifacts on my classpath:
>

Sorry, I missed this email...

I still use Java8, not Java9+ and don't use Errai. So I am not sure how
much help I can be ;)

That said we use elemental2 version 2.27 when using the GWT version
2.8.2-v20191108

This will transitively depend upon the most recently released version
of jsinterop-base (with coordinate com.google.jsinterop:base:jar:1.0.0)

So the deps look roughly like

com.google.jsinterop:base:jar:1.0.0

org.realityforge.com.google.jsinterop:jsinterop-annotations:jar:2.8.2-v20191108

com.google.elemental2:elemental2-core:2.27

org.realityforge.com.google.gwt:gwt-user:jar:2.8.2-v20191108


HTH

-- 
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/CACiKNc59gmHp2NAGGtE%3Dth%2BP7GAj3eUQ1iBUPjiagoHToyxhkg%40mail.gmail.com.

Re: [ANN] (Unofficial) GWT 2.8.2-v20191108 release

[Peter Donald]

We use a different build tool but it works with this version of GWT. I
don't use Maven so not sure how it is normally integrated. However, to
configure it manually you can go to "Project Structure" dialog then
"Project Settings / Facets / Default" section and set "Path to GWT
installation directory" to something like
"/Users/peter/.m2/repository/org/realityforge/com/google/gwt/gwt-dev/2.8.2-v20191108"
and this will be picked up by any GWT facets and thus work in IDE.

HTH

On Tue, Dec 3, 2019 at 6:00 AM Nick Stolwijk 
wrote:

> Thanks.
>
> I was able to use them in my Maven build. Only my IDE, IntelliJ doesn't
> pick them up. Do you if it is possible to use these as the compiler in
> IntelliJ?
>
> With regards,
>
> Nick S.
>
> On Monday, 11 November 2019 04:20:20 UTC+1, Peter Donald wrote:
>>
>> GWT is a development toolkit for building and optimizing complex
>> browser-based applications. Its goal is to enable productive
>> development of high-performance web applications without the
>> developer having to be an expert in browser quirks,
>> XMLHttpRequest, and JavaScript. It’s open-source, completely
>> free, and used by thousands of developers around the world.
>>
>> https://github.com/gwtproject/gwt
>>
>> This is an unofficial release to Maven Central with the groupId
>> prefixed with "org.realityforge.". The intent is to get the current
>> version of GWT into more people's hands earlier. Please don't bug
>> the GWT project. Versions are released on demand.
>>
>> The one significant difference in the way that it has been packaged
>> is to release the jsinterop-annotations artifact with the coordinate
>>
>> org.realityforge.com.google.jsinterop:jsinterop-annotations:jar:2.8.2-v20191108
>>
>>
>> For most Maven users, it should be sufficient to update your
>> dependency declarations to something like:
>>
>> 
>>   org.realityforge.com.google.gwt
>>   gwt-user
>>   2.8.2-v20191108
>> 
>> 
>>   org.realityforge.com.google.gwt
>>   gwt-dev
>>   2.8.2-v20191108
>> 
>>
>> 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+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/google-web-toolkit/313e9b2b-886f-4848-80ee-2c5deff39815%40googlegroups.com
> <https://groups.google.com/d/msgid/google-web-toolkit/313e9b2b-886f-4848-80ee-2c5deff39815%40googlegroups.com?utm_medium=email_source=footer>
> .
>


-- 
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/CACiKNc4cXHgmYkRmBvVsJKEn5KZ7S2b2o5Y1RdXWw3fy6i-MDA%40mail.gmail.com.

[ANN] (Unofficial) Elemental2 2.27 release

[Peter Donald]

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.

It should be noted that this version DOES NOT work with GWT 2.8.2 and requires
either a SNAPSHOT version or the unofficial GWT 2.8.2-v20191108 release.

API Changes relative to Elemental2 version 2.26

elemental2-core:
  API Differences:
https://jsinterop.github.io/api-diff/?key=elemental2-core=2.26=2.27
  - 79 non breaking changes.
  - 198 potentially breaking changes.
  - 62 breaking changes.
elemental2-dom:
  API Differences:
https://jsinterop.github.io/api-diff/?key=elemental2-dom=2.26=2.27
  - 61 non breaking changes.
  - 84 potentially breaking changes.
  - 108 breaking changes.
elemental2-indexeddb:
  API Differences:
https://jsinterop.github.io/api-diff/?key=elemental2-indexeddb=2.26=2.27
  - 61 non breaking changes.
  - 86 potentially breaking changes.
  - 60 breaking changes.
elemental2-media:
  API Differences:
https://jsinterop.github.io/api-diff/?key=elemental2-media=2.26=2.27
  - 5 non breaking changes.
  - 13 potentially breaking changes.
  - 7 breaking changes.
elemental2-svg:
  API Differences:
https://jsinterop.github.io/api-diff/?key=elemental2-svg=2.26=2.27
  - 3 non breaking changes.
  - 2 breaking changes.
elemental2-webgl:
  API Differences:
https://jsinterop.github.io/api-diff/?key=elemental2-webgl=2.26=2.27
  - 31 non breaking changes.
  - 18 potentially breaking changes.
  - 30 breaking changes.
elemental2-webassembly:
  API Differences:
https://jsinterop.github.io/api-diff/?key=elemental2-webassembly=2.26=2.27
  - 3 potentially breaking changes.

The complete set of Elemental2 API differences is available at

  https://jsinterop.github.io/api-diff/?key=elemental2=2.26=2.27

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


  org.realityforge.com.google.elemental2
  ${artifact-id}
  2.27


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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit/CACiKNc52POh5zvCXX767TcnCkRXh_b2n6vKnRYq-6UWdSyU0ng%40mail.gmail.com.

[ANN] (Unofficial) GWT 2.8.2-v20191108 release

[Peter Donald]

GWT is a development toolkit for building and optimizing complex
browser-based applications. Its goal is to enable productive
development of high-performance web applications without the
developer having to be an expert in browser quirks,
XMLHttpRequest, and JavaScript. It’s open-source, completely
free, and used by thousands of developers around the world.

https://github.com/gwtproject/gwt

This is an unofficial release to Maven Central with the groupId
prefixed with "org.realityforge.". The intent is to get the current
version of GWT into more people's hands earlier. Please don't bug
the GWT project. Versions are released on demand.

The one significant difference in the way that it has been packaged
is to release the jsinterop-annotations artifact with the coordinate

org.realityforge.com.google.jsinterop:jsinterop-annotations:jar:2.8.2-v20191108


For most Maven users, it should be sufficient to update your
dependency declarations to something like:


  org.realityforge.com.google.gwt
  gwt-user
  2.8.2-v20191108


  org.realityforge.com.google.gwt
  gwt-dev
  2.8.2-v20191108


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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit/CACiKNc69sWBoc%3DsbNjRfNU9jwhMGcD7uRhe4THpXE%3DfBUMypDw%40mail.gmail.com.

Re: [ANN] (Unofficial) Elemental2 2.26 release

[Peter Donald]

Not at this stage. I had planned on doing so and may in the near future ...
but I was hoping an official GWT 2.9 release would become available
soonish. If not I will figure out a way of releasing unofficial versions
based off master.

On Sun, Oct 27, 2019 at 2:17 AM foal  wrote:

> Hi,
>
> Do you have a rebranded release on GWT 2.9 too?
>
> Best,
> Stas
>
> On Thursday, October 17, 2019 at 4:02:53 AM UTC+2, Peter Donald wrote:
>>
>> Unfortunately, 2.26 is not compatible with GWT 2.8.2 - we were testing
>> with a later version of GWT and I did not pick this up before I sent the
>> mail. Sorry about that!
>>
>> 2.26 will be compatible with GWT 2.9 when/if that gets out.
>>
>> On Thu, Oct 17, 2019 at 12:08 PM Hristo Stoyanov 
>> wrote:
>>
>>> Peter,
>>> Getting this error with Elemental 2.26 and GWT 2.8.2:
>>>
>>> elemental2_version=2.26
>>> jsinterop_base_version=1.0.0-b2-e6d791f
>>> jsinterop_version=1.0.2-p1
>>>
>>> ...
>>>
>>> Compiling module com.recres.web.MainDev
>>>Tracing compile failure path for type 'elemental2.core.JsArray'
>>>   [ERROR] Errors in 
>>> 'jar:file:/C:/g/caches/modules-2/files-2.1/org.realityforge.com.google.elemental2/elemental2-core/2.26/1c407ef9a7e45ecc39be56283e9fe8d677060257/elemental2-core-2.26.jar!/elemental2/core/JsArray.java'
>>>  [ERROR] Line 3: The type javaemul.internal.ArrayStamper is not 
>>> visible
>>>  [ERROR] Line 258: ArrayStamper cannot be resolved
>>>[ERROR] Aborting compile due to errors in some input files
>>>
>>>
>>> Downgrading to 2.25 fixes the issue. Any clue?
>>>
>>> On Sunday, August 25, 2019 at 5:25:29 PM UTC-7, 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.25
>>>>
>>>> elemental2-core:
>>>>   API Differences:
>>>> https://jsinterop.github.io/api-diff/?key=elemental2-core=2.25=2.26
>>>>   - 1 non breaking changes.
>>>>   - 3 potentially breaking changes.
>>>>   - 1 breaking changes.
>>>> elemental2-dom:
>>>>   API Differences:
>>>> https://jsinterop.github.io/api-diff/?key=elemental2-dom=2.25=2.26
>>>>   - 33 non breaking changes.
>>>>   - 65 potentially breaking changes.
>>>>   - 30 breaking changes.
>>>>
>>>> The complete set of Elemental2 API differences is available at
>>>>
>>>>
>>>> https://jsinterop.github.io/api-diff/?key=elemental2=2.25=2.26
>>>>
>>>> The Maven dependencies can be added to your pom.xml via
>>>>
>>>> 
>>>>   org.realityforge.com.google.elemental2
>>>>   ${artifact-id}
>>>>   2.26
>>>> 
>>>>
>>>> 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+unsubscr...@googlegroups.com.
>>> To view this discussion on the web visit
>>> https://groups.google.com/d/msgid/google-web-toolkit/88772e13-7233-4257-9cd7-2aa15c7b959f%40googlegroups.com
>>> <https://groups.google.com/d/msgid/google-web-toolkit/88772e13-7233-4257-9cd7-2aa15c7b959f%40googlegroups.com?utm_medium=email_source=footer>
>>> .
>>>
>>
>>
>> --
>> 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/13c6b848-207a-4735-915c-b0477393a667%40googlegroups.com
> <https://groups.google.com/d/msgid/google-web-toolkit/13c6b848-207a-4735-915c-b0477393a667%40googlegroups.com?utm_medium=email_source=footer>
> .
>


-- 
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/CACiKNc4auhWM27NuaQQPsunOwzBKZ-vJDH-yLAzY1D377bJh1w%40mail.gmail.com.

Re: [ANN] (Unofficial) Elemental2 2.26 release

[Peter Donald]

Unfortunately, 2.26 is not compatible with GWT 2.8.2 - we were testing with
a later version of GWT and I did not pick this up before I sent the mail.
Sorry about that!

2.26 will be compatible with GWT 2.9 when/if that gets out.

On Thu, Oct 17, 2019 at 12:08 PM Hristo Stoyanov 
wrote:

> Peter,
> Getting this error with Elemental 2.26 and GWT 2.8.2:
>
> elemental2_version=2.26
> jsinterop_base_version=1.0.0-b2-e6d791f
> jsinterop_version=1.0.2-p1
>
> ...
>
> Compiling module com.recres.web.MainDev
>Tracing compile failure path for type 'elemental2.core.JsArray'
>   [ERROR] Errors in 
> 'jar:file:/C:/g/caches/modules-2/files-2.1/org.realityforge.com.google.elemental2/elemental2-core/2.26/1c407ef9a7e45ecc39be56283e9fe8d677060257/elemental2-core-2.26.jar!/elemental2/core/JsArray.java'
>  [ERROR] Line 3: The type javaemul.internal.ArrayStamper is not 
> visible
>  [ERROR] Line 258: ArrayStamper cannot be resolved
>[ERROR] Aborting compile due to errors in some input files
>
>
> Downgrading to 2.25 fixes the issue. Any clue?
>
> On Sunday, August 25, 2019 at 5:25:29 PM UTC-7, 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.25
>>
>> elemental2-core:
>>   API Differences:
>> https://jsinterop.github.io/api-diff/?key=elemental2-core=2.25=2.26
>>   - 1 non breaking changes.
>>   - 3 potentially breaking changes.
>>   - 1 breaking changes.
>> elemental2-dom:
>>   API Differences:
>> https://jsinterop.github.io/api-diff/?key=elemental2-dom=2.25=2.26
>>   - 33 non breaking changes.
>>   - 65 potentially breaking changes.
>>   - 30 breaking changes.
>>
>> The complete set of Elemental2 API differences is available at
>>
>>   https://jsinterop.github.io/api-diff/?key=elemental2=2.25=2.26
>>
>> The Maven dependencies can be added to your pom.xml via
>>
>> 
>>   org.realityforge.com.google.elemental2
>>   ${artifact-id}
>>   2.26
>> 
>>
>> 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+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/google-web-toolkit/88772e13-7233-4257-9cd7-2aa15c7b959f%40googlegroups.com
> <https://groups.google.com/d/msgid/google-web-toolkit/88772e13-7233-4257-9cd7-2aa15c7b959f%40googlegroups.com?utm_medium=email_source=footer>
> .
>


-- 
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/CACiKNc5d7VbNLvqHnhsPEqPR8FDvOs9EiscaNR9KYr60%3DDq4rQ%40mail.gmail.com.

Re: RealTime communication

[Peter Donald]

Elemental2 is just the browsers API so pretty much any javascript example
will work. As a matter of fact, I always used to annoy/delight some of my
colleagues by taking an ES6 example and search replacing "const" with
"var", "let" with "var" and "=>" with "->" and you would be amazed how
often this produced workable code after a few autoimport fixes.

Anyhoo ... something like the following will work although I have not
compiled or tested this ... it is just a translation of a javascript
example ;).

final WebSocket socket = new WebSocket( "wss://echo.websocket.org/" );

socket.onopen = e -> {
  DomGlobal.console.log( "[open] Connection established" );
  socket.send( Global.JSON.stringify( JsPropertyMap.of( "message","Hi
ho Silver!" ) ) );
};
socket.onerror = e -> DomGlobal.console.log( "[error]", e );
socket.onmessage = e -> DomGlobal.console.log( "[message] Data
received from server: ", e.data );
socket.onclose = e -> {
  if ( e.wasClean )
  {
DomGlobal.console.log( "[close] Connection closed cleanly, code="
+ e.code + " reason=" + e.reason + "" );
  }
  else
  {
// e.g. server process killed or network down
// event.code is usually 1006 in this case
DomGlobal.console.log( "[close] Connection died" );
  }
};


On Mon, Oct 7, 2019 at 7:46 PM Frank  wrote:

> Do you know where I can find any documentation about how to use websockets
> with Elemental 2 ?
>
> --
> 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/0ec9d2a0-90df-4653-8cbc-8256d98b0948%40googlegroups.com
> <https://groups.google.com/d/msgid/google-web-toolkit/0ec9d2a0-90df-4653-8cbc-8256d98b0948%40googlegroups.com?utm_medium=email_source=footer>
> .
>


-- 
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/CACiKNc5P7mz9K1%2B%2BVYaaX78a%2BgY_-wNiWutr1s1sNY%3DSncmqjw%40mail.gmail.com.

Re: ClassCastException in some browser, but not others (

[Peter Donald]

On Sun, 6 Oct 2019 at 22:56, Jens  wrote:

>
> Actually I believe it is a bug in closures externs from which elemental2
>> is generated. Without checking my guess is that IDBDatabase is annotated
>> with a @constructor tag rather than a @interface which is incorrect as
>> the spec defines it as an interface [1]. Unfortunately, this is a common
>> problem with some of the closure compiler externs. It does not impact
>> people using closure compiler. Unfortunately, the jsinterop-generator will
>> generate incorrect code if the extern is incorrectly annotated.
>>
>
> But they do accept fixes for these kind of things?
>

I believe that they would. My limited experience is that they will almost
always accept changes that improve the correctness unless it requires
massive reworks of internal apps. Even then I have got through some
compromise changes to externs that achieve the same thing. Sometimes the
occasional ping is required to get the ball rolling but other than that a
relatively smooth experience to get changes in.

-- 
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/CACiKNc6F-OJ8auT_CHtpMxw5gmud556oWbyWTZBwbdm-%3D_bU6g%40mail.gmail.com.

Re: ClassCastException in some browser, but not others (

[Peter Donald]

On Sun, Oct 6, 2019 at 8:30 PM Thomas Broyer  wrote:

> Wrt the cast error, it might be that the object in 'result' is not
> "instanceof $wnd.IDBDatabase". This would be a bug in Safari; and
> uncheckedCast is indeed the workaround.
>

Actually I believe it is a bug in closures externs from which elemental2 is
generated. Without checking my guess is that IDBDatabase is annotated with
a @constructor tag rather than a @interface which is incorrect as the spec
defines it as an interface [1]. Unfortunately, this is a common problem
with some of the closure compiler externs. It does not impact people using
closure compiler. Unfortunately, the jsinterop-generator will generate
incorrect code if the extern is incorrectly annotated.

[1] https://www.w3.org/TR/IndexedDB-2/#database-interface

-- 
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/CACiKNc4je86w4xxRJ76P__d18s1DYN6Dq5JMd5%2Brc45x5Y5Dwg%40mail.gmail.com.

Re: RealTime communication

[Peter Donald]

On Fri, 4 Oct 2019 at 23:35, Frank  wrote:

> I was thinking about just bare bones websockets. Since this is most the
> metal and you best now what is going around...
> Any hints where to look on how to work with WebSockets in GWT ? Which
> library to use ?
>

We use web sockets for this use case and it works great. We already had our
own reconnect-on-drop logic and a serialization layer so found there’s no
real value in higher level abstractions

We have dropped all custom websocket libraries and use a recent elemental2
version and find that fine. (The original elemental2 version was not mapped
correctly)

-- 
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/CACiKNc69tdyLpwiwGSP8ULzRdAO2WPjifsB%3D63rH%3DU0hGoT35A%40mail.gmail.com.

Re: Replacement sites for Google Plus for GWT

[Peter Donald]

Hi,

I don't know of any websites that publish GWT specific news items but for
chat around progress for GWT3 and other random help I recommend

https://gitter.im/gwtproject/gwt
https://gitter.im/vertispan/j2cl

which are reasonably active and reasonably helpful.

On Mon, Aug 26, 2019 at 12:00 PM David  wrote:

> I am trying to find out more news about GWT. I knew I could find out them
> in Google Plus. Now do you know where is the replacement site for GWT in
> Google Plus?
>
> Thanks,
>
> David
>
> --
> 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/49d64b2c-b6bb-45d4-94a9-3fd19916a43b%40googlegroups.com
> <https://groups.google.com/d/msgid/google-web-toolkit/49d64b2c-b6bb-45d4-94a9-3fd19916a43b%40googlegroups.com?utm_medium=email_source=footer>
> .
>


-- 
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/CACiKNc6%2BR5Le4w1N3EqySpgiCPWXQOdYqkLp%3DyvMYGtZ2wBRxQ%40mail.gmail.com.

[ANN] (Unofficial) Elemental2 2.26 release

[Peter Donald]

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.25

elemental2-core:
  API Differences:
https://jsinterop.github.io/api-diff/?key=elemental2-core=2.25=2.26
  - 1 non breaking changes.
  - 3 potentially breaking changes.
  - 1 breaking changes.
elemental2-dom:
  API Differences:
https://jsinterop.github.io/api-diff/?key=elemental2-dom=2.25=2.26
  - 33 non breaking changes.
  - 65 potentially breaking changes.
  - 30 breaking changes.

The complete set of Elemental2 API differences is available at

  https://jsinterop.github.io/api-diff/?key=elemental2=2.25=2.26

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


  org.realityforge.com.google.elemental2
  ${artifact-id}
  2.26


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

Re: elemental2: Native maps with primitive types?

[Peter Donald]

On Thu, Aug 15, 2019 at 4:28 PM Vassilis Virvilis  wrote:

> I have seen the @DoNotAutoBox and I tried with Integer, Number, JsNumber.
>
> Note: I can put int in the JsPropertyMap but I cannot read it back. So
> I cast it to (double) and the then to (int). I believe that is because
> JavaScript does not have int type.
>

That is certainly an option but in some circumstances can lead to type
issues when casting. I tend to prefer using Any to do these sorts of
conversions. It is a little more verbose but it avoids any unexpected
casting problems. I don't have the code in front of me but I believe there
is a method like getAsAny("myprop") that works in this scenario


>
> --
> Vassilis Virvilis
>
> --
> 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/CAKbOjEzHuG5ZC7igRyvzrkLt26qBWkxNUeuWL%2BZNbKCo%2BcShgA%40mail.gmail.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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit/CACiKNc6CpmL2naFFydC%2BYS%3Dmtj3yQFsQ2KojGQCRAXXSRCYhLg%40mail.gmail.com.

Re: elemental2: Document.createEvent ?

[Peter Donald]

execCommand is not yet part of elemental2. There is no reason why it should
not be other than the externs need cleaning up. It is on my list of things
to do some time but we don't use it so I haven't got off my kaboose to do
the work. The issue that is tracking this (among other things) is
https://github.com/google/elemental2/issues/86

Until that is completed you will have to use jsinterop to do it yourself.

On Sat, Aug 10, 2019 at 12:54 AM Vassilis Virvilis 
wrote:

> What about Document.execCommand() ?
>
>
> On Fri, Aug 9, 2019 at 5:20 PM Vassilis Virvilis 
> wrote:
> >
> > Hi,
> >
> > I am looking for  Document.createEvent and I can see that createEvent
> > is defined in DocumentEvent which is an interface but Document itself
> > does not inherit/implement this interface.
> >
> > I suppose I can cast Document it to DocumentEvent with Js.cast() but
> > that's ugly.
> >
> > So what's going on?
> >
> > I am using elemental2 2.25 as published by Peter Donald.
> >
> > --
> > Vassilis Virvilis
>
>
>
> --
> Vassilis Virvilis
>
> --
> 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/CAKbOjEx4%2B3TZuMJf2%3DBiCW6d57o-OLoMiBjqjSi%3DMjPny%2B%2B_ug%40mail.gmail.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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit/CACiKNc4frwwFenqaAGPN3nBxgsYHJ_gO_86QbOPQpBT02eySsg%40mail.gmail.com.

[ANN] (Unofficial) Elemental2 2.25 release

[Peter Donald]

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.24

elemental2-dom:
  API Differences:
https://jsinterop.github.io/api-diff/?key=elemental2-dom=2.24=2.25
  - 34 non breaking changes.
  - 16 potentially breaking changes.
  - 26 breaking changes.
elemental2-indexeddb:
  API Differences:
https://jsinterop.github.io/api-diff/?key=elemental2-indexeddb=2.24=2.25
  - 6 breaking changes.
elemental2-media:
  API Differences:
https://jsinterop.github.io/api-diff/?key=elemental2-media=2.24=2.25
  - 5 breaking changes.
elemental2-svg:
  API Differences:
https://jsinterop.github.io/api-diff/?key=elemental2-svg=2.24=2.25
  - 1 non breaking changes.

The complete set of Elemental2 API differences is available at

  https://jsinterop.github.io/api-diff/?key=elemental2=2.24=2.25

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


  org.realityforge.com.google.elemental2
  ${artifact-id}
  2.25


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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit/CACiKNc4pH%2BDS-hJHSKXKwyk85%3DWMKrZwMxMsrNXaE7SqEVTDhg%40mail.gmail.com.

Re: "socket.io.js" + JSInterop

[Peter Donald]

On Wed, Jun 19, 2019 at 8:24 PM Rinaldo Arden 
wrote:

> The problem is not that it cannot be done (everything can be done with a C
> compiler and a text editor), but that this is the year 2019, and we are
> still talking about this matter. GWT never provided an underlying
> up-to-date transport mechanism (there was RPC earlier of course); I recall
> having to hack up something to get websockets working, some time ago. OK it
> worked but it was no proper library. Another chap has pointed me kindly to
> a JSNI wrapper for socketio, which is itself some years old. And some years
> after JSInterop has been released there still appears to be no up-to-date
> library for socketio; which confirms my original suspicion that there is no
> interest in GWT for real-time applications, or really even in underlying
> network transport. Which cannot be said of Angular, or React, or of other
> frameworks. What exactly is GWT 3 is going to be all about?
>

We have been doing "real time applications" in GWT since ~2011 and we have
historically used our own libraries that with a combination of long
polling, eventsource and websocket tech. However browsers have got good
enough these days that we have stripped most of it away and are just
sending json packets and json-like packets on websockets. And you can use
elemental2 for that - see
https://groups.google.com/d/msg/google-web-toolkit/qkgexZ4C0n0/kp9bqw-MAQAJ
for latest elemental2.

GWT may not have have bindings for some library but most of those libraries
no longer offer the value they once did. I do miss having decent
serialization library ... but you can't have everything ;)
-- 
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/CACiKNc5mxa%3DdrJHEsJ95-mk01M%2BUayjmemeFPAvhPjmmgtZkGQ%40mail.gmail.com.

Re: [ANN] (Unofficial) Elemental2 2.24 release

[Peter Donald]

On Wed, Jun 12, 2019 at 8:29 AM Peter Donald  wrote:

> On Wed, Jun 12, 2019 at 7:31 AM John Huss  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+unsubscr...@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

[Peter Donald]

On Wed, Jun 12, 2019 at 7:31 AM John Huss  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=2.23=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=2.23=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=2.23=2.24
>>   - 1 non breaking changes.
>> elemental2-svg:
>>   API Differences:
>> https://jsinterop.github.io/api-diff/?key=elemental2-svg=2.23=2.24
>>   - 1 breaking changes.
>> elemental2-webassembly:
>>   API Differences:
>> https://jsinterop.github.io/api-diff/?key=elemental2-webassembly=2.23=2.24
>>   - 1 potentially breaking changes.
>>
>> The complete set of Elemental2 API differences is available at
>>
>>   https://jsinterop.github.io/api-diff/?key=elemental2=2.23=2.24
>>
>> The Maven dependencies can be added to your pom.xml via
>>
>> 
>>   org.realityforge.com.google.elemental2
>>   ${artifact-id}
>>   2.24
>> 
>>
>> 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+unsubscr...@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
> <https://groups.google.com/d/msgid/google-web-toolkit/a7ddd14d-d72d-4f45-ab43-cecb13c267a0%40googlegroups.com?utm_medium=email_source=footer>
> .
>


-- 
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/CACiKNc6gDFQHANZ63-gq6vidL6oxyeSuWo%3DbcD4ErTke7h%3Dz3Q%40mail.gmail.com.

Re: GWT - Still Active ?

[Peter Donald]

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  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+unsubscr...@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
> <https://groups.google.com/d/msgid/google-web-toolkit/6f3dfaf6-ab6e-400a-a154-35b3c386422d%40googlegroups.com?utm_medium=email_source=footer>
> .
>


-- 
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/CACiKNc7Oyn33n_MfPsQwTzAW31UP9fkyZ4CNbRTrZwS%2Bo%3DP9yw%40mail.gmail.com.

[ANN] (Unofficial) Elemental2 2.24 release

[Peter Donald]

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=2.23=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=2.23=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=2.23=2.24
  - 1 non breaking changes.
elemental2-svg:
  API Differences:
https://jsinterop.github.io/api-diff/?key=elemental2-svg=2.23=2.24
  - 1 breaking changes.
elemental2-webassembly:
  API Differences:
https://jsinterop.github.io/api-diff/?key=elemental2-webassembly=2.23=2.24
  - 1 potentially breaking changes.

The complete set of Elemental2 API differences is available at

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

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


  org.realityforge.com.google.elemental2
  ${artifact-id}
  2.24


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

Re: What is the advantage of GWT 3.0?

[Peter Donald]

On Sun, Jun 2, 2019 at 12:59 PM Andrew Buck  wrote:

> I love GWT 2.8 and I appreciate all the work that the community has put
> into it as well as the work towards GWT 3.0. I'm trying to understand what
> the advantage of GWT 3.0 is though. It seems like GWT 3.0 is a subset of
> GWT 2.8 with a different compiler under the covers. How is the closure
> compiler better than the GWT 2 compiler and is it really worth trying to
> switch when GWT 2.8 is mature and works well?
>

The reason we are moving that way is:

* <1s refresh times in dev mode regardless of the size of the project. The
promise is that the compile time is proportional to the size of the change,
not the size of the app.
* Integration with modern javascript so can use modern browser facilities
without backflips. i.e. Simple creation of ES6 class instances so can do
things like WebComponents without ugly hacks and/or loss of
optimize-ability.
* Potential for much better code optimization and writing custom compiler
passes.
* Emitting modules as non-web apps without writing custom linkers. i.e.
Currently if you are building a browser extension or a web worker or an app
to run in node you need to write a custom linker
* potential for hot-reload in candidate modules without loosing any
application state (i.e reload just a single ui component in our react/gwt
app without loosing the rest of the state in our application)
* Integration/optimization with native javascript. i.e. Bringing in native
js modules will be possible and they will all be compiled and optimized
together
* Exporting java libraries to native Typescript/javascript without any
ugliness and full optimization still available

To be honest the first two are the main reasons ... the rest is icing on
the cake ;)

-- 
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/CACiKNc7NUQ1b-AD6ZOrobxH3okOq57_dNjuiDMp3Mr8nCJOprA%40mail.gmail.com.

Re: GWT - Still Active ?

[Peter Donald]

On Fri, May 31, 2019 at 10:44 AM Craig Mitchell 
wrote:

> Off topic:  I do wonder how web assembly (WASM) is going to impact GWT,
> especially if it gets garbage collection, and therefore makes Java to WASM
> compilation possible.
>

That is the biggest risk IMO. When we did our analysis to decide on whether
to commit to J2CL/GWT3.x for the next 10 years or not this was the only
real risk that we found (or that Typescript gets a lot better backend).

WebAssembly is still a way off but projects like
https://github.com/i-net-software/JWebAssembly do seem to be something to
watch


-- 
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/CACiKNc6AcJeBXAoqKWgBTrSgQsmwG57r-onZUKtbjU%3D%3D4jY%3D_w%40mail.gmail.com.

Re: Is this project active?

[Peter Donald]

On Fri, May 31, 2019 at 10:55 AM Rob Newton  wrote:

> A contributor may develop something new or port something, and then
> announce it to the community that it is available for use, but there is no
> central site listing/promoting these wares.
>

A central place would be nice and has been tried before but it takes a lot
of effort to establish it and keep it going.

> Perhaps things are in too much flux to attract new developers to using
> GWT.  Perhaps the goal should be to retain existing GWT users?  The more
> users there are, the more contributors there will be, and the better GWT
> will be for all of us.  Conversely, the fewer users there are, ... .
>

I think that is the point porting the GWT2.x modules to jsinterop. To help
retain existing users.

There is also a lot of companies that have abandoned all of those framework
libraries and just use jsinterop and java to js compiler. Vue-GWT seems
successful. We use react+GWT and find it invaluable. I think all of googles
stuff probably does this.


> (It's easy for me (a non-contributor) to list some shortcomings, but am I
> going to volunteer my personal time to improve things?  Or do I expect
> Google to do everything, and I just use it and give nothing back?)
>

I don't think Google is really responsible. I expect that in time that the
jre layer + jsinterop library will probably move out of GWT and into their
own repositories so they can be more easily used by J2CL (googles
replacement java-to-js compiler) at which point I am not sure how much work
will go on in the current GWT repo. However I expect work in the
elemental2, j2cl and other repos to continue.

-- 
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/CACiKNc6fLjV3%3D5iq-g18qvEPsfAzGA8Zf81tmoGqcfert4b7HA%40mail.gmail.com.

[ANN] (Unofficial) Elemental2 2.23 release

[Peter Donald]

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 both implemented in 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.

Unfortunately 2.22 was released with a patch incorrectly applied that led
to DomGlobal.location and Window.location being incorrectly typed. This
subsequent release just removes the incorrect patch to fix the types.

API Changes relative to Elemental2 version 2.22

elemental2-dom:
  API Differences:
https://jsinterop.github.io/api-diff/?key=elemental2-dom=Elemental2=2.22=2.23
  - 1 non breaking changes.
  - 2 breaking changes.

The complete set of Elemental2 API differences is available at


https://jsinterop.github.io/api-diff/?key=elemental2=Elemental2=2.22=2.23

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


  org.realityforge.com.google.elemental2
  ${artifact-id}
  2.23


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+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

[ANN] (Unofficial) Elemental2 2.22 release

[Peter Donald]

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 both implemented in 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.

This release uses a different version schema which is essentially
2.[BuildNumber] at the request of a few who found the old schema
distasteful.

The API diff reports are also generated statically and stored on a GitHub
pages site so that they are always available.

API Changes relative to Elemental2 version 1.0.0-b21-6a027d2

elemental2-dom:
  API Differences:
https://jsinterop.github.io/api-diff/?key=elemental2-dom=Elemental2=1.0.0-b21-6a027d2=2.22
  - 52 non breaking changes.
  - 53 potentially breaking changes.
  - 23 breaking changes.
elemental2-webgl:
  API Differences:
https://jsinterop.github.io/api-diff/?key=elemental2-webgl=Elemental2=1.0.0-b21-6a027d2=2.22
  - 297 potentially breaking changes.

The complete set of Elemental2 API differences is available at


https://jsinterop.github.io/api-diff/?key=elemental2=Elemental2=1.0.0-b21-6a027d2=2.22

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


  org.realityforge.com.google.elemental2
  ${artifact-id}
  2.22


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+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: Is this project active?

[Peter Donald]

On Fri, Apr 12, 2019 at 1:04 PM Craig Mitchell 
wrote:

> You can use both of them together ;) We use react+GWT and absolutely love
>> it. We use a state management library Arez (https://arez.github.io/)
>> which is very similar conceptually to Mobx done in Java style. You can see
>> a sample application @
>> https://github.com/react4j/react4j-todomvc/tree/arez_maven/src/main/java/react4j/todomvc
>>
>
> That is very cool!  I couldn't get Super Dev Mode working due to:
>
> [ERROR] linkers other than CrossSiteIFrameLinker aren't supported. Found:
> com.google.gwt.core.linker.SingleScriptLinker
>
>
This may be true running the TodomvcProd.gwt.xml but if you run
TodomvcDev.gwt.xml it should be fine. We don't use Maven at work so I may
have misconfigured the tooling :/


> However, the GWT compile worked fine, and it ran on my Tomcat server.
> Going to dive into the code to see how easy/hard it would be to use
> existing React components.
>

We *used* to use existing react components but due to differences between
the different environments it always felt a bit clunky and I am not sure
how easy it would be to do at this stage. You would probably need to use
jsinterop to get the react component type and write a custom builder to
create the component and it should be possible but we don't do this
anymore. We found it is easier to just port the component and keep in java
land.

-- 
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 post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: Is this project active?

[Peter Donald]

On Mon, Apr 8, 2019 at 2:34 PM Craig Mitchell 
wrote:

> I took a break from GWT to develop in React for 2 years.  While the React
> structure is okay, writing in JS is just painful.  TypeScript looked a
> little better, but never got the chance to dive into it.  Now I'm back
> using GWT and loving it!
>

You can use both of them together ;) We use react+GWT and absolutely love
it. We use a state management library Arez (https://arez.github.io/) which
is very similar conceptually to Mobx done in Java style. You can see a
sample application @
https://github.com/react4j/react4j-todomvc/tree/arez_maven/src/main/java/react4j/todomvc

We are still on Java8/GWT2.X but hopefully by mid year our apps will be cut
across to Java11/J2CL+closure compiler. So far everything is looking good ;)

-- 
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 post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

[ANN] (Unofficial) Elemental2 1.0.0-b21-6a027d2 release

[Peter Donald]

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 both implemented in 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 1.0.0-b20-bfe6e22

elemental2-core: Full details at
https://diff.revapi.org/?groupId=org.realityforge.com.google.elemental2=elemental2-core=1.0.0-b20-bfe6e22=1.0.0-b21-6a027d2
  4 non breaking changes.
  4 potentially breaking changes.
elemental2-dom: Full details at
https://diff.revapi.org/?groupId=org.realityforge.com.google.elemental2=elemental2-dom=1.0.0-b20-bfe6e22=1.0.0-b21-6a027d2
  38 non breaking changes.
  149 potentially breaking changes.
  49 breaking changes.
elemental2-media: Full details at
https://diff.revapi.org/?groupId=org.realityforge.com.google.elemental2=elemental2-media=1.0.0-b20-bfe6e22=1.0.0-b21-6a027d2
  3 non breaking changes.
  3 potentially breaking changes.
  8 breaking changes.
elemental2-promise: Full details at
https://diff.revapi.org/?groupId=org.realityforge.com.google.elemental2=elemental2-promise=1.0.0-b20-bfe6e22=1.0.0-b21-6a027d2
  1 non breaking changes.
  2 breaking changes.
elemental2-svg: Full details at
https://diff.revapi.org/?groupId=org.realityforge.com.google.elemental2=elemental2-svg=1.0.0-b20-bfe6e22=1.0.0-b21-6a027d2
  137 breaking changes.
elemental2-webgl: Full details at
https://diff.revapi.org/?groupId=org.realityforge.com.google.elemental2=elemental2-webgl=1.0.0-b20-bfe6e22=1.0.0-b21-6a027d2
  8 non breaking changes.
  4 potentially breaking changes.
  8 breaking changes.

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


  org.realityforge.com.google.elemental2
  ${artifact-id}
  1.0.0-b21-6a027d2


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+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Extracting jsinterop-annotations?

[Peter Donald]

I was just hoping to release a copy to Maven Central and thought it may be
useful to do the extraction at the same time ... and just general cleaning
up ;)

No rush.

On Fri, Apr 5, 2019 at 9:45 AM 'Goktug Gokdogan' via GWT Contributors <
google-web-toolkit-contributors@googlegroups.com> wrote:

> Sorry for the late response. The work of creating the repo is tiny but
> wiring everything especially internally is plenty of work. The current
> annotations in opensource is also missing J2CL specific ones that we need
> to export as well so I don't see much value of you trying to extract a
> repository.
>
> Is there a particular reason that you would like to get this one sooner
> than later other than generally cleaning things up and reducing deps?
>
>
> On Fri, Mar 29, 2019 at 7:54 PM Peter Donald 
> wrote:
>
>> On Sat, Mar 30, 2019 at 6:57 AM 'Goktug Gokdogan' via GWT Contributors <
>> google-web-toolkit-contributors@googlegroups.com> wrote:
>>
>>> Yes, google/jsinterop-annotations was the plan all along however
>>> unfortunately most of the work is on our side and we couldn't get back to
>>> it.
>>>
>>
>> Is there any value in me trying to extract a repository for this or would
>> that cause more work for you?
>>
>> --
>> Cheers,
>>
>> Peter Donald
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "GWT Contributors" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/google-web-toolkit-contributors/CACiKNc761i8unTuxQWB3fsRJ1kGm_Y2oybwygACMYkXsYUg-Pw%40mail.gmail.com
>> <https://groups.google.com/d/msgid/google-web-toolkit-contributors/CACiKNc761i8unTuxQWB3fsRJ1kGm_Y2oybwygACMYkXsYUg-Pw%40mail.gmail.com?utm_medium=email_source=footer>
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
> --
> You received this message because you are subscribed to the Google Groups
> "GWT Contributors" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAN%3DyUA32%3DF%2BWbqWEZtk8VhAoszH7dioJfP0-nv5wQD3BUOZHpQ%40mail.gmail.com
> <https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAN%3DyUA32%3DF%2BWbqWEZtk8VhAoszH7dioJfP0-nv5wQD3BUOZHpQ%40mail.gmail.com?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>


-- 
Cheers,

Peter Donald

-- 
You received this message because you are subscribed to the Google Groups "GWT 
Contributors" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CACiKNc612gonFp9YxeNVP2nKQcffd1oc%3DU9kHoB3U%2B%3D7LU3RyA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Extracting jsinterop-annotations?

[Peter Donald]

On Sat, Mar 30, 2019 at 6:57 AM 'Goktug Gokdogan' via GWT Contributors <
google-web-toolkit-contributors@googlegroups.com> wrote:

> Yes, google/jsinterop-annotations was the plan all along however
> unfortunately most of the work is on our side and we couldn't get back to
> it.
>

Is there any value in me trying to extract a repository for this or would
that cause more work for you?

-- 
Cheers,

Peter Donald

-- 
You received this message because you are subscribed to the Google Groups "GWT 
Contributors" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CACiKNc761i8unTuxQWB3fsRJ1kGm_Y2oybwygACMYkXsYUg-Pw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[gwt-contrib] Extracting jsinterop-annotations?

[Peter Donald]

Hi,

The jsinterop annotation jar is shipped as an independent artifact and
along with jsinterop-base and elemental2 seems to be among the artifacts
that will be shared between GWT2.x and J2CL. I would like to see it moved
to a separate top level project and am happy to do the work to make it so.

My feeling is that it is basically maintained by the J2CL team so it seems
like a good idea to formalise this.  "git log" seems to indicate that most
of the changes were done by google engineers with the exception of one
commit by Thomas Broyer.

So I think a reasonable approach would be to basically extract it as
'google/jsinterop-annotations' project on github using Bazel modelled after
jsinterop-base and friends. If that makes people uncomfortable I also went
and nabbed the "jsinterop" github organization so it could be added as a
project such as https://github.com/jsinterop/annotations or
https://github.com/jsinterop/jsinterop-annotations

The jsinterop annotations currently live in
the user/src/jsinterop/annotations directory within GWT. It would be
relatively easy to extract the code from their, preserving history of
changes and put it in a new repository with a new build system.

Thoughts?,

Peter Donald

-- 
You received this message because you are subscribed to the Google Groups "GWT 
Contributors" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CACiKNc6ukcq_Bqic%2BpAmoUR6RpJqvAcDPM8YonbO9ZWBc5LGVA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Is this project active?

[Peter Donald]

I think the project is more active now than it has been in a long time. It
is just that the work is spread out over a few different places. Most work
atm seems to be towards getting to GWT3.x The java-to-js compiler is under
active development at https://github.com/google/j2cl - the browser apis at
https://github.com/google/elemental2. There is also people working on
porting the GWT2.x apis to be forward compatible. There also seems to be a
few people working on various other frameworks and toolkits.

Chat seems to be best place to keep up and occurs at
https://gitter.im/gwtproject/gwt or on other gitter channels.

HTH

On Thu, Mar 28, 2019 at 7:12 PM Jens  wrote:

> Java 11 language/syntax support has just been committed:
> https://gwt.googlesource.com/gwt/+/205b88a4d88cc0c23b2cd0df681a18d114443a7c
>
> Currently in the GWT 2.x versions only minimal work will be done.
> Contributors focus their work on splitting GWT SDK into smaller pieces and
> make them J2CL compatible (new Java -> JS compiler from Google). This work
> is happening on Github and CI builds for most of these projects can be
> found at ci.vertispan.com.
>
> GWT depends on contributors these days, so amount of commits can vary
> greatly, depending on the free time contributors 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 post to this group, send email to google-web-toolkit@googlegroups.com.
> Visit this group at https://groups.google.com/group/google-web-toolkit.
> For more options, visit https://groups.google.com/d/optout.
>


-- 
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 post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

[ANN] (Unofficial) Elemental2 1.0.0-b20-bfe6e22 release

[Peter Donald]

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 both implemented in 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.

The changes primarily involved
* Renaming some parameters to event callbacks
* Addition of some more modern javascript methods (i.e String.trimStart())
* A cleanup of the WebSocket API to align add all the features present
standard WebIDL.

API Changes relative to Elemental2 version 1.0.0-b19-fb227e3

elemental2-core: Full details at
https://diff.revapi.org/?groupId=org.realityforge.com.google.elemental2=elemental2-core=1.0.0-b19-fb227e3=1.0.0-b20-bfe6e22
  3 non breaking changes.

elemental2-dom: Full details at
https://diff.revapi.org/?groupId=org.realityforge.com.google.elemental2=elemental2-dom=1.0.0-b19-fb227e3=1.0.0-b20-bfe6e22
  10 non breaking changes.
  12 potentially breaking changes.
  4 breaking changes.

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


  org.realityforge.com.google.elemental2
  ${artifact-id}
  1.0.0-b20-bfe6e22


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+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: [ANN] (Unofficial) JsInterop-Base 1.0.0-b2-e6d791f release

[Peter Donald]

Hi,

I have also released the J2CL compatible variant of this library with the
artifactId set to "base-j2cl". This should be available in Maven central in
5 minutes or so via:



org.realityforge.org.realityforge.com.google.jsinterop
  base-j2cl
  1.0.0-b2-e6d791f


Enjoy!


On Sun, Feb 24, 2019 at 10:10 AM Peter Donald 
wrote:

> The jsInterop-base library contains a set of utilities to implement
> functionality that
> cannot be expressed with Jsinterop alone.
>
> https://github.com/google/jsinterop-base
>
> This is an unofficial release to Maven Central under a different groupId.
> Please don't bug the original authors. Versions are released on demand.
>
> The only change relative to 1.0.0-b1-e6d791f is that the java source is
> included in the main jar rather than only being available in the
> `-sources` jar.
> This was to align with behaviour of the original 1.0.0-RC1 release.
>
> The Maven dependency can be added to your pom.xml via
>
> 
>
> org.realityforge.org.realityforge.com.google.jsinterop
>   base
>   1.0.0-b2-e6d791f
> 
>
> Hope this helps,
>
> Peter Donald
>
>

-- 
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 post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

[ANN] (Unofficial) Elemental2 1.0.0-b19-fb227e3 release

[Peter Donald]

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 both implemented in 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 1.0.0-b18-f3472e7

* All of the poms that are part of the release have been updated to
reference
  a more recent version of the jsinterop-base dependency

elemental2-dom:
Full details at
https://diff.revapi.org/?groupId=org.realityforge.com.google.elemental2=elemental2-dom=1.0.0-b18-f3472e7=1.0.0-b19-fb227e3
  11 non breaking changes.
* Added field elemental2.dom.CanvasRenderingContext2D.imageSmoothingEnabled
* Several improvements around fetch API

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


  org.realityforge.com.google.elemental2
  ${artifact-id}
  1.0.0-b19-fb227e3


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+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

[ANN] (Unofficial) JsInterop-Base 1.0.0-b2-e6d791f release

[Peter Donald]

The jsInterop-base library contains a set of utilities to implement
functionality that
cannot be expressed with Jsinterop alone.

https://github.com/google/jsinterop-base

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

The only change relative to 1.0.0-b1-e6d791f is that the java source is
included in the main jar rather than only being available in the `-sources`
jar.
This was to align with behaviour of the original 1.0.0-RC1 release.

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



org.realityforge.org.realityforge.com.google.jsinterop
  base
  1.0.0-b2-e6d791f


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+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

[ANN] (Unofficial) JsInterop-Base 1.0.0-b1-e6d791f release

[Peter Donald]

The jsInterop-base library contains a set of utilities to implement
functionality that
cannot be expressed with Jsinterop alone.

https://github.com/google/jsinterop-base

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

This release contains 2 breaking changes. The removal of the methods:

* JsArrayLike::getAnyAt(int)
* JsPropertyMap::getAny(java.lang.String)

And 6 non breaking changes.

It should be noted that this is the GWT2.x variant and is not j2cl
compatible. In the future there may be a j2cl compatible artifact released
if there is demand.

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



org.realityforge.org.realityforge.com.google.jsinterop
  base
  1.0.0-b1-e6d791f


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+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

[ANN] (Unofficial) elemental2-webassembly release

[Peter Donald]

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 both implemented in GWT and J2CL.

https://github.com/google/elemental2

This is an unofficial release to Maven Central under a different groupId
and is completely unofficial so please don't bug the original authors. A
new version is released on demand.

This release includes the first release of elemental2-webassembly. Huzzah!
Please take it for a test drive and report any bugs.

API Changes relative to Elemental2 version 1.0.0-b17-6897368

elemental2-core: Full details at
https://diff.revapi.org/?groupId=org.realityforge.com.google.elemental2=elemental2-core=1.0.0-b17-6897368=1.0.0-b18-f3472e7
  7 non breaking changes.
  4 potentially breaking changes.
  2 breaking changes.

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


  org.realityforge.com.google.elemental2
  ${artifact-id}
  1.0.0-b18-f3472e7


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+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

[ANNOUNCE] (Unofficial) Elemental2 1.0.0-b17-6897368 packages published to Maven Central

[Peter Donald]

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 both implemented in GWT and J2CL.

The official Elemental2 project is available via

https://github.com/google/elemental2

The Elemental2 project does not yet provide regular releases but
is evolving as the underlying Closure compiler externs evolve and
this can make it difficult to adopt Elemental2 in more traditional
build systems.

Until regular Elemental2 releases start occurring, I have decided
to periodically publish versions of Elemental2 artifacts to maven
central. To avoid conflicts with the official releases the groupId
of the artifacts are prefixed with "org.realityforge." and artifacts
use different versions.

This is completely unofficial so please don't bug the original
Elemental2 authors. A new version will be released when I need a
feature present in newer externs or when I am explicitly asked.

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


  org.realityforge.com.google.elemental2
  ${artifact-id}
  1.0.0-b17-6897368


where artifact-id is one of

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

API Changes relative to version 1.0.0-b16-6897368

elemental2-dom: 10 changes. See
https://diff.revapi.org/?groupId=org.realityforge.com.google.elemental2=elemental2-dom=1.0.0-b16-6897368=1.0.0-b17-6897368


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+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

[ANNOUNCE] (Unofficial) Elemental2 1.0.0-b16-6897368 packages published to Maven Central

[Peter Donald]

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 both implemented in GWT and J2CL.

The official Elemental2 project is available via

https://github.com/google/elemental2

The Elemental2 project does not yet provide regular releases but
is evolving as the underlying Closure compiler externs evolve and
this can make it difficult to adopt Elemental2 in more traditional
build systems.

Until regular Elemental2 releases start occurring, I have decided
to periodically publish versions of Elemental2 artifacts to maven
central. To avoid conflicts with the official releases the groupId
of the artifacts are prefixed with "org.realityforge." and artifacts
use different versions.

This is completely unofficial so please don't bug the original
Elemental2 authors. A new version will be released when I need a
feature present in newer externs or when I am explicitly asked.

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


  org.realityforge.com.google.elemental2
  ${artifact-id}
  1.0.0-b16-6897368


where artifact-id is one of

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

API Changes relative to version 1.0.0-b15-7a28038

* elemental2-dom: 2 changes. See
https://diff.revapi.org/?groupId=org.realityforge.com.google.elemental2=elemental2-dom=1.0.0-b15-7a28038=1.0.0-b16-6897368

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+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: [ANNOUNCE] (Unofficial) Elemental2 1.0.0-b14-2f97dbe packages published to Maven Central

[Peter Donald]

Version 1.0.0-b15-7a28038 has been published to Maven Central (but it may
take an hour or so to be replicated out). A problem was identified - namely
ClientRect disappeared from the API due to a change in closure ~12 days
ago. See https://github.com/google/elemental2/pull/80 for the fix.

It was suggested that one way to help identify changes and problems ahead
of time is to generate one of the API diffs via something like japicmp (See
http://siom79.github.io/japicmp/Examples.html for some examples). I was
thinking about producing this against the baseline build (i.e. last
official elemental2 publish) and the previous build.

Before I did this - would anyone find this useful? And/or has anyone got
any better ideas on how to trace API evolution over time?





On Sun, Feb 3, 2019 at 11:47 PM 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 both implemented in GWT and J2CL.
>
> The official Elemental2 project is available via
>
> https://github.com/google/elemental2
>
> The Elemental2 project does not yet provide regular releases but
> is evolving as the underlying Closure compiler externs evolve and
> this can make it difficult to adopt Elemental2 in more traditional
> build systems.
>
> Until regular Elemental2 releases start occurring, I have decided
> to periodically publish versions of Elemental2 artifacts to maven
> central. To avoid conflicts with the official releases the groupId
> of the artifacts are prefixed with "org.realityforge." and artifacts
> use different versions.
>
> This is completely unofficial so please don't bug the original
> Elemental2 authors. A new version will be released when I need a
> feature present in newer externs or when I am explicitly asked.
>
> The Maven dependencies published can be added to your pom.xml via
>
> 
>   org.realityforge.com.google.elemental2
>   ${artifact-id}
>   1.0.0-b14-2f97dbe
> 
>
> where artifact-id is one of
>
> * elemental2-core
> * elemental2-dom
> * elemental2-promise
> * elemental2-indexeddb
> * elemental2-svg
> * elemental2-webgl
> * elemental2-media
> * elemental2-webstorage
>
> To see how these artifacts are published see:
> https://github.com/realityforge/repackr
>
> Hope it helps someone,
>
> Peter Donald
>
>

-- 
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 post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

[ANNOUNCE] (Unofficial) Elemental2 1.0.0-b14-2f97dbe packages published to Maven Central

[Peter Donald]

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 both implemented in GWT and J2CL.

The official Elemental2 project is available via

https://github.com/google/elemental2

The Elemental2 project does not yet provide regular releases but
is evolving as the underlying Closure compiler externs evolve and
this can make it difficult to adopt Elemental2 in more traditional
build systems.

Until regular Elemental2 releases start occurring, I have decided
to periodically publish versions of Elemental2 artifacts to maven
central. To avoid conflicts with the official releases the groupId
of the artifacts are prefixed with "org.realityforge." and artifacts
use different versions.

This is completely unofficial so please don't bug the original
Elemental2 authors. A new version will be released when I need a
feature present in newer externs or when I am explicitly asked.

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


  org.realityforge.com.google.elemental2
  ${artifact-id}
  1.0.0-b14-2f97dbe


where artifact-id is one of

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

To see how these artifacts are published see:
https://github.com/realityforge/repackr

Hope it helps someone,

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 post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Update on J2CL

[Peter Donald]

t not very soon" worries me. Is J2CL a 100% Java or you use 
>>>>>>>>> other stuff that can not be released?
>>>>>>>>>
>>>>>>>>> 5. I still don't quite understand why not dump everything J2CL on 
>>>>>>>>> Gihub "AS IS" and let us sort it out?
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Also, It would be helpful if some of the developers who already 
>>>>>>>>> received the J2CL code drop comment and clarify what needs to be 
>>>>>>>>> finished from their point of view.
>>>>>>>>>
>>>>>>>>> As far as GWT3, I don't understand what is the value of it at all, 
>>>>>>>>> maybe valuable time/resources can be spent on J2CL instead, once it 
>>>>>>>>> is placed on Github
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Thanks.
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>> You received this message because you are subscribed to the Google 
>>>>>>>>> Groups "GWT Contributors" group.
>>>>>>>>> To unsubscribe from this group and stop receiving emails from it, 
>>>>>>>>> send an email to 
>>>>>>>>> google-web-toolkit-contributors+unsubscr...@googlegroups.com.
>>>>>>>>> To view this discussion on the web visit 
>>>>>>>>> https://groups.google.com/d/msgid/google-web-toolkit-contributors/807613cc-5945-49c1-8f5e-205dd53f5dea%40googlegroups.com.
>>>>>>>>> For more options, visit https://groups.google.com/d/optout.
>>>>>>>
>>>>>>> --
>>>>>>> You received this message because you are subscribed to the Google 
>>>>>>> Groups "GWT Contributors" group.
>>>>>>> To unsubscribe from this group and stop receiving emails from it, send 
>>>>>>> an email to 
>>>>>>> google-web-toolkit-contributors+unsubscr...@googlegroups.com.
>>>>>>> To view this discussion on the web visit 
>>>>>>> https://groups.google.com/d/msgid/google-web-toolkit-contributors/d4af467b-ae98-4ab6-a665-d465c5145527%40googlegroups.com.
>>>>>>> For more options, visit https://groups.google.com/d/optout.
>>>>>>
>>>>>> --
>>>>>> You received this message because you are subscribed to the Google 
>>>>>> Groups "GWT Contributors" group.
>>>>>> To unsubscribe from this group and stop receiving emails from it, send 
>>>>>> an email to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
>>>>>> To view this discussion on the web visit 
>>>>>> https://groups.google.com/d/msgid/google-web-toolkit-contributors/CAN%3DyUA260YR-MCguZadyrsQB3_vxhDCCsB7tW10OVmwn6%2BWi7g%40mail.gmail.com.
>>>>>> For more options, visit https://groups.google.com/d/optout.
>>>>
>>>> --
>>>> You received this message because you are subscribed to the Google Groups 
>>>> "GWT Contributors" group.
>>>> To unsubscribe from this group and stop receiving emails from it, send an 
>>>> email to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
>>>> To view this discussion on the web visit 
>>>> https://groups.google.com/d/msgid/google-web-toolkit-contributors/fa0348e5-a4f9-4ea1-846e-b9784b26e3e1%40googlegroups.com.
>>>> For more options, visit https://groups.google.com/d/optout.
>
> --
> You received this message because you are subscribed to the Google Groups 
> "GWT Contributors" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
> To view this discussion on the web visit 
> https://groups.google.com/d/msgid/google-web-toolkit-contributors/ed1958fb-5094-4c5f-864c-2c2e21d283d8%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.



-- 
Cheers,

Peter Donald

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

gRPC-Web for GWT and/or J2CL?

[Peter Donald]

Hi,

It seems like gRPC has gone GA.

https://www.cncf.io/blog/2018/10/24/grpc-web-is-going-ga/

It seems it can emit closure annotated classes and I guess it would be
not too hard to output the equivalent jsinterop annotated classes.
This would make it very easy to get excellent integration into J2CL
and event GWT2.x.

Eyeballing it makes it seem like a very attractive target. Has anyone
used it or done any work with it before? Or know of any equivalent
GWTish generator for 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 post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Re: "GWT RPC" and its role in the future of GWT

[Peter Donald]

Hi,

IMNSHO I think that the best idea would be to host the new "gwt-rpc"
project outside the project have a completely separate moniker -
something that offers easy iconography (Mmmm ... TigerRPC?). Once it
is stabilised and offers a credible alternative to current gwt-rpc, at
that point I think it would be good to start documenting it as the
spiritual successor of gwt-rpc.

The advantage of this approach is that you get to iterate much faster
with a lot less overhead. You also potentially get developers involved
that have the time/interest to work on that specific project.

--
Cheers,

Peter Donald

-- 
You received this message because you are subscribed to the Google Groups "GWT 
Contributors" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CACiKNc5G0KHqZpY_tTKxojP36gwyQDHh1XVPY%2BsH4Wk59ntkew%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Run your web application and its web workers alongside in Super Dev Mode!

[Peter Donald]

Nice - thanks for sharing!

On Thu, Jun 14, 2018 at 8:20 AM Paul Sitarz  wrote:

> Hi guys,
>
> If like me you got headaches when trying to use web workers with GWT in
> Super Dev Mode, I am glad to tell you it can be done.
>
> And in Super Dev Mode!
>
> I just posted a video on YouTube on the subject:
> https://youtu.be/1x8SCZ90hwg
>
> You will find my blog article and the files needed here:
> https://www.xalys.com/2018/06/13/web-workers-in-super-dev-mode/
>
> Best,
> Paul
>
> PS: I also  posted a video yesterday about layout trashing/reflows:
> https://youtu.be/AZWNxstL4dA
>
> --
> 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 post to this group, send email to google-web-toolkit@googlegroups.com.
> Visit this group at https://groups.google.com/group/google-web-toolkit.
> For more options, visit https://groups.google.com/d/optout.
>


-- 
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 post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

GWT QR Code Generation LIbrary

[Peter Donald]

Hi,

Recently I had to generate QR Codes as part of a GWT app so I ended up
porting an existing java library that did the same. For anyone who is
interested the GWT port is available at:

https://github.com/realityforge/gwt-qr-code

and in Maven central.

-- 
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 post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Which API for a future, modern JSON library?

[Peter Donald]

Hi,

Have you considered the javax.json API? There are some parts that may
not be able to be directly translated but from memory it should mostly
work. The "advantage" is that it is a standard that is starting to
gain traction and will likely be present in lots more APIs as more of
the EE stack adopts it. The "disadvantage" is that the api is a bit
more primitive and it evolves slowly. It could probably be done with
just @JsOverlay methods and a few adapter classes. Another
disadvantage is that it is an immutable/read-only API.

As for json writing - We tend to use @JsType annotated classes and
have yet to come up with a use case where we would need to drop down
to JsPropertyMap.

-- 
Cheers,

Peter Donald

-- 
You received this message because you are subscribed to the Google Groups "GWT 
Contributors" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CACiKNc6_RvyT7RaQ8r87bXcexVvGB%2BmtFCiATZrY-aNcB%2BYKEg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: Strange elemental 2 behavior and weird workaround

[Peter Donald]

We have experienced this a bit and have a custom script to clean out
the cache although it seems we could have just used the SDM UI.

However the most frequent place we find this is on inline lambdas.
i.e. Something like "doAction( () -> myfunction() );". The lambda will
often end up null after a recompile. Weirdly extracting this out into
a separate variable ala "final Runnable action = () -> myfunction();
doAction(action);" seems to "fix" this or at least reduce the
frequency of this bug so much that we don't notice. We have never
invested the time to track down the exact cause of this.

HTH

On Tue, Dec 5, 2017 at 9:37 PM, Jens <jens.nehlme...@gmail.com> wrote:
> GWT SuperDevMode only compiles changes (and its dependencies) but sometimes
> it might miss a change which can result in broken code. As you said the only
> workaround is to force a change to the affected method or clean SDM cache
> and rebuild the whole app (click the small clean button on the SDM UI at
> localhost:9876).
>
> Of course it is a bug but without being able to reproduce it, I guess it is
> tough to find and fix.
>
> -- 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 post to this group, send email to google-web-toolkit@googlegroups.com.
> Visit this group at https://groups.google.com/group/google-web-toolkit.
> For more options, visit https://groups.google.com/d/optout.



-- 
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 post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] jsinterop-base github repository and new beta release

[Peter Donald]

Fantastic!

On Sat, Nov 11, 2017 at 6:59 PM, 'Julien Dramaix' via GWT Contributors <
google-web-toolkit-contributors@googlegroups.com> wrote:

> I'll create a new release of elemental2 next week. Stay tuned.
>
>
> On Friday, November 10, 2017 at 6:13:31 PM UTC-8, Peter Donald wrote:
>>
>> Great work - thanks!
>>
>> Is this compatible with the last release of elemental2? (IIRC it
>> was 1.0.0-beta-1)
>>
>> On Sat, Nov 11, 2017 at 12:22 PM, 'Julien Dramaix' via GWT Contributors <
>> google-web-toolkit-contributors@googlegroups.com> wrote:
>>
>>> Dear contributors,
>>>
>>> We've just created a new github repository containing the source code of
>>> jsinterop-base: https://github.com/google/jsinterop-base
>>>
>>> We've also released a new beta version of the library:
>>> jsinterop-base:1.0.0-beta-3
>>> <https://oss.sonatype.org/content/repositories/releases/com/google/jsinterop/base/1.0.0-beta-3/>
>>>
>>> You can try it by downloading the jar file
>>> <https://oss.sonatype.org/content/repositories/releases/com/google/jsinterop/base/1.0.0-beta-3/base-1.0.0-beta-3.jar>
>>> or use the following Maven dependency:
>>>
>>>
>>> 
>>>   com.google.jsinterop
>>>   base
>>>   1.0.0-beta-3
>>> 
>>>
>>>
>>> Don’t hesitate to report any bugs, issues, concerns you have on the github
>>> issue tracker <https://github.com/google/jsinterop-base/issues>.
>>>
>>> -Julien
>>>
>>> --
>>> You received this message because you are subscribed to the Google
>>> Groups "GWT Contributors" group.
>>> To unsubscribe from this group and stop receiving emails from it, send
>>> an email to google-web-toolkit-contributors+unsubscr...@googlegroups.com
>>> .
>>> To view this discussion on the web visit https://groups.google.com/d/ms
>>> gid/google-web-toolkit-contributors/CABXeq2TrKCNg0i0R%2BUB%2
>>> BPBDGEPL2r--jQFA5ZQOyywdOGvsdsg%40mail.gmail.com
>>> <https://groups.google.com/d/msgid/google-web-toolkit-contributors/CABXeq2TrKCNg0i0R%2BUB%2BPBDGEPL2r--jQFA5ZQOyywdOGvsdsg%40mail.gmail.com?utm_medium=email_source=footer>
>>> .
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>>
>>
>> --
>> Cheers,
>>
>> Peter Donald
>>
> --
> You received this message because you are subscribed to the Google Groups
> "GWT Contributors" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/google-web-toolkit-contributors/ff40c05b-5f30-
> 418e-9caa-6a53a96dfa84%40googlegroups.com
> <https://groups.google.com/d/msgid/google-web-toolkit-contributors/ff40c05b-5f30-418e-9caa-6a53a96dfa84%40googlegroups.com?utm_medium=email_source=footer>
> .
>
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Cheers,

Peter Donald

-- 
You received this message because you are subscribed to the Google Groups "GWT 
Contributors" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CACiKNc6_Er8psaFZYwdgoFO0GvW_ncgOa8pRzTz5if6bdWm%2BpA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] jsinterop-base github repository and new beta release

[Peter Donald]

Great work - thanks!

Is this compatible with the last release of elemental2? (IIRC it
was 1.0.0-beta-1)

On Sat, Nov 11, 2017 at 12:22 PM, 'Julien Dramaix' via GWT Contributors <
google-web-toolkit-contributors@googlegroups.com> wrote:

> Dear contributors,
>
> We've just created a new github repository containing the source code of
> jsinterop-base: https://github.com/google/jsinterop-base
>
> We've also released a new beta version of the library:
> jsinterop-base:1.0.0-beta-3
> <https://oss.sonatype.org/content/repositories/releases/com/google/jsinterop/base/1.0.0-beta-3/>
>
> You can try it by downloading the jar file
> <https://oss.sonatype.org/content/repositories/releases/com/google/jsinterop/base/1.0.0-beta-3/base-1.0.0-beta-3.jar>
> or use the following Maven dependency:
>
>
> 
>   com.google.jsinterop
>   base
>   1.0.0-beta-3
> 
>
>
> Don’t hesitate to report any bugs, issues, concerns you have on the github
> issue tracker <https://github.com/google/jsinterop-base/issues>.
>
> -Julien
>
> --
> You received this message because you are subscribed to the Google Groups
> "GWT Contributors" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/google-web-toolkit-contributors/CABXeq2TrKCNg0i0R%2BUB%2BPBDGEPL2r--
> jQFA5ZQOyywdOGvsdsg%40mail.gmail.com
> <https://groups.google.com/d/msgid/google-web-toolkit-contributors/CABXeq2TrKCNg0i0R%2BUB%2BPBDGEPL2r--jQFA5ZQOyywdOGvsdsg%40mail.gmail.com?utm_medium=email_source=footer>
> .
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Cheers,

Peter Donald

-- 
You received this message because you are subscribed to the Google Groups "GWT 
Contributors" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CACiKNc7%2B8HtnC32JpBsw7a5%3DbmvgDndwAwHKnAMTwHUtp-wFTA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: New project best practice

[Peter Donald]

who are not front end specialists). However the
javascript ecosystems is rich enough that you will find something that
works in your context. (It should be noted that I have also hear rumours
that there are people who are looking at bringing significant portions of
gwt2 framework in j2cl age so staying with what you know and adopting GMD
or a similar modern widget toolkit may also work)

There are some things that are missing in GWT2.x world that I hope will be
fixed by j2cl/GWT (optimising native javascript, webpack equivalent, better
asset pipeline control) but it has not stopped us moving everything else
forward and development is great again.

--
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 post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: Controlling Inling in GWT compiler

[Peter Donald]

>
> I still suspect (having not experimented with it) that the "return this"
> aliasing will still confuse matters, at least without deliberate code in
> closure to handle it. At least with strings, it isn't smart enough:
> https://closure-compiler.appspot.com/home#code%3D%252F%252F%2520%253D%
> 253DClosureCompiler%253D%253D%250A%252F%252F%2520%2540compilation_level%
> 2520ADVANCED_OPTIMIZATIONS%250A%252F%252F%2520%2540output_file_name%
> 2520default.js%250A%252F%252F%2520%253D%253D%
> 252FClosureCompiler%253D%253D%250A%250A%252F%252F%2520ADD%
> 2520YOUR%2520CODE%2520HERE%250Afunction%2520A()%257Bthis.
> str%253D%27%27%257D%253B%250AA.prototype.b%2520%253D%
> 2520function(string)%2520%257Bthis.str%252B%253Dstring%
> 253B%2520return%2520this%253B%257D%253B%250AA.prototype.c%
> 2520%253D%2520function()%2520%257Breturn%2520this.str%257D%
> 253B%250A%250Aconsole.log(new%2520A().b(%2522a%2522).b(
> window.prompt()).b(%2522b%2522).c())%253B
> I'm having a hard time modeling this in plain JS to get it to treat the
> constructor like an object, so as to correctly handle the "return this".
> Might be better as a @JsOverlay...
>

I should note I tried lots of different ways to try and get this working
and came up with nothing. If you do figure it out - I would love to see
what it looks like ;)

-- 
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 post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: Controlling Inling in GWT compiler

[Peter Donald]

On Wed, Oct 18, 2017 at 1:14 PM, Colin Alworth <niloc...@gmail.com> wrote:

> For the first one, chaining methods has the unfortunate detail that each
> method has a return value, which the next object is called on. To my
> knowledge, there is no optimization in the compiler which currently can
> undo the presence of the return value, and recognize that the method
> returns "this" (or a param, some other easily aliased value) as a special
> case.
>

Ok. I think I have been spoilt by working on the JVM for so long. I just
assumed that GWT and/or Closure could do escape analysis and inline
non-escaping objects into the current scope. I assume this is not the case
then? It would explain the resulting code.

Lets assume that "str" was only one char, since we are compiling after all,
> 40 chars for the "idiomatic" js version, 37 chars for staticified version,
> 50 for the "inlined" version.
>

Hmm ... I guess I was too down in the trenches to think high level enough.
I like this idea. In my context the following is the lay of the land

*Current Java Input: *
new InputBuilder().type( "checkbox" ).className( "foo" ).child( "Hello"
).build()

*Naive Javascript output (71 chars)*
React.createElement('input',{type:'checkbox',className:'foo'},'Hello')

*Current GWT output: (lots)*
function up(a){var b,c;c=a.b;b=a.a;return
$wnd.React.createElement.apply(null,[hw,c].concat(b))}
function vp(a,b){a.a.concat(b);return a}
function wp(a){a.b['className']='foo';return a}
function xp(a){a.b['type']='checkbox';return a}
a=up(vp(wp(xp(new yp)),'Hello'))

*Non-reusable GWT output: (82 chars)*
function wp(a){a.b['className']='foo';return a}
a=up(vp(wp(xp(new yp)),'Hello'))

*Hypothetical Less Naive ES3 Javascript output (45 chars)*
ab(dc,{'type':xs,'className':'foo'},'Hello')

*Hypothetical Less Naive ES6 Javascript output (36 chars)*
ab(dc,{[eg]:xs,[gg]:'foo'},'Hello')

So even if you strip the potentially reusable code out of the current GWT
output the non reusable chunk is still 82 characters which is 9 characters
more than the most naive javascript implementation. However a more
optimized javascript implementation that aliases the methods and constants
comes in at 36 chars. However I think that uses some ES6 features ([gg] as
key).

I still suspect (having not experimented with it) that the "return this"
> aliasing will still confuse matters, at least without deliberate code in
> closure to handle it. At least with strings, it isn't smart enough:
>

Right.


> I played with a similar optimization in GWT a few years ago, but ended up
> not finishing it. It mostly dealt with trying to deal with compile-time
> strings and avoiding runtime regular expressions on them, but I abandoned
> it. If there is enough interest in this, I think I at least have the
> working knowledge to give it a shot... but lets be sure that we get
> something out of it.
>

To be perfectly honest I have no idea on the state of either the GWT or
closure optimizer so could not rightly say but I suspect that without an
escape analysis this may be a very difficult optimization to get right and
probably a lot of work ;) I remember spending weeks  (months?) trying to
get some similar optimizations working in a past life and I mostly failed !
But if you want to try don't let me stop you.

create({a:'asdf',b:1,c:false});
> create(c(b(a({},'asdf'),1),false);
> Literal is 31 bytes, chained is 35, so two bytes per setter (plus the cost
> of the setter method, which can then be reused). Might not be worth more
> than a few hours of time, but then again, the work could lead to other
> unexpected benefits...
>


I think the optimization would offer a fairly significant improvement but I
also think it is a massive amount of work. Maybe time would be better spent
elsewhere.

Anyhoo interesting idea - thanks for your reply.

-- 
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 post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Controlling Inling in GWT compiler

[Peter Donald]

Hi,

So I am trying to figure out a way to control inlining in GWT compiler and
potentially if it will be compatible with J2CL. My motivation is that I
want to build type-safe builders that are compiled away at runtime. The
idea is to compile something like

new InputBuilder().type( InputType.checkbox ).className( "foo"
).child( "Hello" ).build()

to

React.createElement('input', { className: 'foo' }, 'Hello')

And browsing the code I thought I could make use of @ForceInline and
@HasNoSideEffects in appropriate places to control the inlining. The goal
would essentially be to move most of the building code into caller which
allow the data flow analyzer to zap it into a nice compact form. But I can
not seem to get it to work.

It is unclear whether I am using it wrong or it just won't work and reading
through the compiler source code is proving to be slow way to understand
the problem.

@ForceInline does not seem to force inlining but instead raises an error if
code is not inlined? Am I understanding this correctly? Certainly adding
the annotation to all the places that I wanted that occur causes a error
like "Function X is marked as @ForceInline but it could not be inlined".
Reading through the JsInliner source code has not enlightened me why.

So more code less talk. Here is the example I have been working with

https://gist.github.com/realityforge/5c9c04cd86dc6ada80f05558d609a3ae

Next question is around optimisation of the new jsinterop code. It seems
that GWT compiler does not work particularly well and something like

final JsPropertyMapOfAny prop = JsPropertyMap.of();
prop.set( "a", 1 );
prop.set( "b", 2 );
prop.set( "c", 3 );

will not produce an object literal.

So do you think this is an achievable goal with GWT2, what about in
J2CL? Any suggestions on how I could achieve this?

BTW I know using things like @ForceInline and @HasNoSideEffects is
"dangerous" and unsupported but I am comfortable with the impact I would
have on compile size/time. (Once worked on JikesRVM which is a JVM written
in Java which has similar annotations and similar tradeoffs - see
http://www.jikesrvm.org/JavaDoc/org/vmmagic/pragma/package-summary.html)

-- 
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 post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: Looking for a List of all GWT Modules.

[Peter Donald]

oups
> "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 post to this group, send email to google-web-toolkit@googlegroups.com.
> Visit this group at https://groups.google.com/group/google-web-toolkit.
> For more options, visit https://groups.google.com/d/optout.
>



-- 
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 post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: Test Strategies for Modern GWT (i.e. Elemental2 etc)

[Peter Donald]

Excellent - I will look into it. I had always assumed as the modern code
did not use GWT.create() anymore that GwtMockito was no longer necessary
but I guess it must have other goodies in there ;)

Anyhoo - will dig in. This is one occasion where I do miss the javascript
ecosystem with it's ease of testing with a real browser.


On Tue, Sep 19, 2017 at 4:16 PM, Ignacio Baca Moreno-Torres <
igna...@bacamt.com> wrote:

> Elemento (so elemental2) uses it to test the builder, but as Erik said,
> not quite practical for anything else than non-browser-related logic
> testing.
> https://github.com/hal/elemento/blob/develop/core/
> src/test/java/org/jboss/gwt/elemento/core/ElementsBuilderTest.java#L50
>
> On Tue, Sep 19, 2017 at 3:48 AM Erik Kuefler <ekuef...@gmail.com> wrote:
>
>> If you want to further explore the mock-based option you should check out
>> GwtMockito: https://github.com/google/gwtmockito. It handles natives and
>> finals and has a few other GWT-specific features. I haven't made any big
>> changes to it in the last couple of years, but if there are new things it
>> could do to help with Elemental2 or other modern GWT I'm definitely open to
>> suggestions.
>>
>> Mocking helps for certain types of logic tests, but for anything that
>> relies on logic that runs in the browser (e.g. calculating the size of
>> elements) it doesn't get you very far, so it's not great for testing
>> widgets. For that I don't think there's much way around WebDrive.
>>
>>
>> On Sunday, September 17, 2017 at 5:24:10 AM UTC-7, Peter Donald wrote:
>>>
>>> Hi,
>>>
>>> Has anyone got any good examples of how they are testing GWT code that
>>> is interacting with the browser APIs.
>>>
>>> Historically we just ignored that low level code as we either were using
>>> pre-existing Widgets that we implicitly trusted and for that limited amount
>>> of jsni or browser interaction that we wrote we just hand tested and
>>> limited change in that area. We then built abstractions ala MVP and tested
>>> the rest of the app (which was typically 95% of the code anyhoo).
>>>
>>> Now that we are moving to Elemental2 there are fewer abstractions and it
>>> would be nice to test the low level code. In particular small little
>>> elements.
>>>
>>> So how do we people do this? Options that we came up with:
>>>
>>> * Ignore. build abstractions and use manual testing where required.
>>> * GWTTestCase - although last time we tried it (maybe ~2010) it was
>>> nothing like a real browser and rather slow.
>>> * Compile code and tests to javascript and figure out a way to run them
>>> in a real browser and scrape the results.
>>> * Compile code to javascript and use webdriver/selenium to interact with
>>> browser.
>>> * Ignore for now and wait till J2CL and use js ecosystems solutions.
>>> * Use something like powermock to mock natives etc and run them in jre
>>>
>>> Anyone got any examples of this working or can offer any suggestions? In
>>> particular I am interested to see examples that use Elemental2 or other
>>> jsinterop code.
>>>
>>> --
>>> 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 post to this group, send email to google-web-toolkit@googlegroups.com.
>> Visit this group at https://groups.google.com/group/google-web-toolkit.
>> For more options, visit https://groups.google.com/d/optout.
>>
> --
> 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 post to this group, send email to google-web-toolkit@googlegroups.com.
> Visit this group at https://groups.google.com/group/google-web-toolkit.
> For more options, visit https://groups.google.com/d/optout.
>



-- 
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 post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Test Strategies for Modern GWT (i.e. Elemental2 etc)

[Peter Donald]

Hi,

Has anyone got any good examples of how they are testing GWT code that is
interacting with the browser APIs.

Historically we just ignored that low level code as we either were using
pre-existing Widgets that we implicitly trusted and for that limited amount
of jsni or browser interaction that we wrote we just hand tested and
limited change in that area. We then built abstractions ala MVP and tested
the rest of the app (which was typically 95% of the code anyhoo).

Now that we are moving to Elemental2 there are fewer abstractions and it
would be nice to test the low level code. In particular small little
elements.

So how do we people do this? Options that we came up with:

* Ignore. build abstractions and use manual testing where required.
* GWTTestCase - although last time we tried it (maybe ~2010) it was nothing
like a real browser and rather slow.
* Compile code and tests to javascript and figure out a way to run them in
a real browser and scrape the results.
* Compile code to javascript and use webdriver/selenium to interact with
browser.
* Ignore for now and wait till J2CL and use js ecosystems solutions.
* Use something like powermock to mock natives etc and run them in jre

Anyone got any examples of this working or can offer any suggestions? In
particular I am interested to see examples that use Elemental2 or other
jsinterop code.

-- 
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 post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: Emulating CompletableFuture with Promise

[Peter Donald]

That is pretty awesome. Thanks!

On Thu, Sep 7, 2017 at 6:55 AM, Benjamin DeLillo <b...@ekotrope.com> wrote:

> I decided to package this up in a standalone library so it can be used
> until such time that it makes it into a GWT release.
>
> https://github.com/OneGeek/GWT-CompletableFuture
>
> On Monday, September 5, 2016 at 4:47:10 AM UTC-4, Andrei Korzhevskii wrote:
>>
>> I guess you need to super-source this class so the gwt compiler could use
>> it.
>>
>> You can take a look at my initial CompletableFuture implementation here:
>>
>> https://github.com/nordligulv/gwt/tree/completable-future
>> https://github.com/nordligulv/gwt/commit/ea70c5358bac3c939cb
>> 0c1628a58ccc462cd7423
>>
>> Feel free to use it but note that I haven't tested it properly yet.
>>
>>
>>
>> On Monday, September 5, 2016 at 3:28:27 AM UTC+3, Ian Preston wrote:
>>>
>>> I'm trying to emulate CompletableFuture by backing directly onto
>>> Promise, but when compiling it gives this error:
>>> "No source code is available for type java.util.concurrent.Completab
>>> leFuture"
>>> (it finds other JRE classes I've replaced fine)
>>>
>>> My source I'm including is below. Am I doing anything illegal?
>>> 
>>> package java.util.concurrent;
>>>
>>> import com.google.gwt.user.client.*;
>>> import jsinterop.annotations.*;
>>>
>>> import java.util.function.*;
>>>
>>> @JsType(isNative=true, name = "Promise", namespace = JsPackage.GLOBAL)
>>> public class CompletableFuture implements CompletionStage {
>>>
>>> @JsMethod(name = "then")
>>> public native  CompletableFuture thenApply(Function>> T,? extends U> fn);
>>>
>>> @JsMethod(name = "then")
>>> public native CompletableFuture thenAccept(Consumer
>>> action);
>>>
>>> @JsMethod(name = "then")
>>> public native  CompletableFuture thenCompose(Function>> T, ? extends CompletionStage> fn);
>>>
>>> @JsMethod(name = "reject")
>>> public native boolean completeExceptionally(Throwable ex);
>>>
>>> @JsMethod(name = "resolve")
>>> public native boolean complete(T value);
>>>
>>> @JsMethod(name = "resolve")
>>> public static native  CompletableFuture completedFuture(U
>>> value);
>>>
>>> @JsOverlay
>>> public T get() throws InterruptedException, ExecutionException {
>>> Window.alert("Calling synchronous get() on CompletableFuture is
>>> not possible in Javascript!");
>>> throw new IllegalStateException("Unimplemented!");
>>> }
>>> }
>>>
>> --
> 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 post to this group, send email to google-web-toolkit@googlegroups.com.
> Visit this group at https://groups.google.com/group/google-web-toolkit.
> For more options, visit https://groups.google.com/d/optout.
>



-- 
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 post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Re: Business proposition of GWT 3.0 - what is it good for vs. other solutions out there?

[Peter Donald]

On Sat, May 20, 2017 at 10:05 AM, Learner Evermore
<learner.everm...@gmail.com> wrote:
> So, simple questions that truly need to be answerable before GWT 3 can have
> any future for us with complex products... and I think for any future users
> too:

As context: We have several largish code bases probably totalling just
over a million lines of client code in total although some of that is
generated. However our single largest codebase is only 338K LOC but it
does support a bunch of complex scenarios.

And from what we have heard so far GWT 3 will make our lives a lot
easier. On the basis of this we are looking at building the next
version of our suite in GWT3 which is likely to have at least a 15
year lifespan.

I do not disagree that there will be some period of adjustment and
some growing pain but the future looks brighter now than it has in a
while for the GWT project. I also will be first to admit the GWT
projects communication is not always the greatest ;)

> How to reasonably accomplish compatibility with existing code dependent on
> widgets (for example Sencha GXT - most should be aware of that)

We looked at this and it seems reasonably simple to get the Widgets
working under a pure jsinterop+System.getProperty world. Simple but
labour intensive. You could do it now if you wanted to prepare for
GWT3.

We use UIBinder extensively and that is probably easy enough to get
95% converted to APT. However I do recall there being a bunch of
scenarios where it becomes harder - although what they were slips my
mind atm. In that case we are likely to just implement the subset and
generate errors if there is any of those scenarios in our code.

I have no idea what shape the client bundles would end up in but I
suspect  we would move to using wrappers for whatever tool bundled the
javascript be it webpack or closure (does it have a bundling tool?) or
whatever. I love some of the css-in-js stuff happening in javascript
land - (See 
https://markdalgleish.github.io/presentation-a-unified-styling-language
for an overview). I certainly see some significant advantages about
changing the way we do stuff here.

> How to reasonably accomplish GWT RPC serialization (all of it)?

It is unfortunate that you have used this feature but I can't see it
ever being implemented by google or the community at large. It is
likely that this is something you will need to do and it will be hard,
particularly arbitrary exceptions which we have found difficult to
whitelist.

Most frameworks based on language/framework specific serialization
strategies tend to fail, often due to the difficulty of interacting
from other platforms or difficult evolving code on the same platform.
Java RMI is largely unused these days. Maybe now is the time to move
to something different*.

Failing that you can stick with GWT 2.X if it fits your current needs.

* A few years ago "grpc" (another google project IIRC? based on
protocol buffers?) came about which looked like it may be a good rpc
solution but it never had a javascript client.

-- 
Cheers,

Peter Donald

-- 
You received this message because you are subscribed to the Google Groups "GWT 
Contributors" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-web-toolkit-contributors/CACiKNc6ES5V%2BSt378Lnz032%2BFzb%2BVK7QoUhB5%3DJWZFHB%3DeDvHg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: java.util.Lists in Gwt super dev mode debugger

[Peter Donald]

On Thu, May 4, 2017 at 4:27 AM, bclark <bclarkfair...@gmail.com> wrote:

> The connection between Intellij and Chrome is definitely squirrelly
> though.  I often have to execute the code server bookmarklet twice to
> finally get Intellij to stop at a breakpoint and sometimes Intellij won't
> reconnect to Chrome until I close and restart it.
>
Rather than restarting chrome you can just disable the intellij extension
then re-enable it and after that IDEA is usually able to reconnect with no
problems.

-- 
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 post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: GWTReact Release and Roadmap

[Peter Donald]

Great work.

We are just starting down the path of React+GWT and glad to see the project
moving forward

On Sun, Apr 30, 2017 at 10:27 PM, Paul Stockley <pstockl...@gmail.com>
wrote:

> I have just released a new version of the GWTReact
> <https://github.com/GWTReact> projects to support GWT 2.8.1
>
> As of this release, I will no longer be maintaining the MobX and Redux
> projects. Our company is not using them currently and I don't have the time
> to keep them updated. In the future, we may update MobX if we start using
> it in production. If you would like take over maintenance of either of
> these projects please let me know.
>
> *Road Map*
>
> With the current release, I feel pretty good about the quality of the
> projects. We are starting to use both gwt-interop-utils and gwt-react in
> our production code with excellent results. However, I think to get to a
> 1.0 release I need to make the following changes:
>
>
>1. Migrate gwt-interop-utils to use the new GWT base project
>2. Migrate gwt-react to use elemental 2
>
> I will start working on these objectives in a month or two. The main
> determining factor on how quick this happens will be how fast elemental 2
> matures.
>
> --
> 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 post to this group, send email to google-web-toolkit@googlegroups.com.
> Visit this group at https://groups.google.com/group/google-web-toolkit.
> For more options, visit https://groups.google.com/d/optout.
>



-- 
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 post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: [gwt-contrib] Re: GWT 2.8.1 release

[Peter Donald]

Indeed - great work!

On Wed, Apr 26, 2017 at 6:44 AM, Predrag Remark <codelessoluti...@gmail.com>
wrote:

> Great news!
>
> --
> You received this message because you are subscribed to the Google Groups
> "GWT Contributors" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to google-web-toolkit-contributors+unsubscr...@googlegroups.com.
> To view this discussion on the web visit https://groups.google.com/d/
> msgid/google-web-toolkit-contributors/cebc800a-92b6-
> 4a0d-87ce-e759f645be2e%40googlegroups.com
> <https://groups.google.com/d/msgid/google-web-toolkit-contributors/cebc800a-92b6-4a0d-87ce-e759f645be2e%40googlegroups.com?utm_medium=email_source=footer>
> .
>
> For more options, visit https://groups.google.com/d/optout.
>



-- 
Cheers,

Peter Donald

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

Re: Caching of Static Files in GWT

[Peter Donald]

GWT uses perfect hashing for javascript files and thus some of the files
can be cached forever (because if the content changes the filename
changes). Some files can never be cached (i.e. the *.nocache.* files).

To make sure the appropriate cchine headers are set you can use the
following library (it deploys fine under payara)

https://github.com/realityforge/gwt-cache-filter

HTH



On Tue, Mar 28, 2017 at 8:23 PM, abdul <mohammedsameen@gmail.com> wrote:

> Hi,
>  Developed application using GWT which contains lot of static
> files(`javascript,css,images`) which i want to cache for `30` days. I read
> lot of blogs but didn't get any clue.
>
>  *- How to cache static files?
>  - What are the possible option to achieve caching (do i need to configure
> in server or GWT application, here i am using glassfish/payara server for
> deployment)*
>
> Any idea?
>
> --
> 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 post to this group, send email to google-web-toolkit@googlegroups.com.
> Visit this group at https://groups.google.com/group/google-web-toolkit.
> For more options, visit https://groups.google.com/d/optout.
>



-- 
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 post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: Call client method from server

[Peter Donald]

On Wed, Mar 16, 2016 at 7:26 AM, Greg <grz3gorz.no...@gmail.com> wrote:
> Don't forget about EventSource / Server Sent Events.
>
> Browser support: http://caniuse.com/#search=eventsource
> There are polyfills for IE/Edge: https://github.com/Yaffle/EventSource
> (there are other mentioned in README.md)
>
> The advantage over websockets is that it uses plain http connection, just
> long lived and managed by the browser itself (do not mistake it for long
> polling). That means it should not be affected by firewalls.

We ended up having to use a combination of technologies for all the
browsers we need to support. So we use

* Periodic & Long Polling: Just HTTP(S) so works in all browsers
across all intermediaries. See
https://github.com/realityforge/gwt-webpoller
* EventSource / Server Sent Events: Faster than polling, works in a
lot of browsers. See https://github.com/realityforge/gwt-eventsource
* Web Sockets: Fastest and easiest to use programatically but least
compatible. See https://github.com/realityforge/gwt-websockets

HTH,

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 post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: What is best IDE for developing GWT applications?

[Peter Donald]

Hi,

On Tue, Mar 1, 2016 at 12:26 PM, Slava Pankov <pank...@gmail.com> wrote:
> I don't know why many people are suggesting IntelliJ for GWT. For example
> code completion in ui.xml files is not working in IntelliJ, and I don't
> understand how to develop UI efficiently without it.

It works fine for me and has in every version I have ever used.

The current version I am using is either 14.1.5 or  14.1.6

-- 
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 post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: Getting rid of Dev mode for future GWT releases

[Peter Donald]

On Saturday, 12 December 2015, <geek.macb...@gmail.com> wrote:
>
> So - my opinion - reducing the functionality of the debugger (moving from
> DevMode to SDM, for example) is in fact a loss of useful features and a
> reduction in the power of the tools at my disposal. I can use SDM - but it
> only covers like 50% of the functionality I use in a JVM debugger.
>

I keep hearing that SDM is not as good as DevMode but our experience is
that it is better in almost every way. This may be because we IntelliJ idea.

In Both you can run the debugger from the ide, set break points, inspect
variables. DevMode has the advantage that variables are easier to decipher.
SDM has the  advantage of speed for both startup and refresh and during
debug. SDM also never has to deal with differences between different modes
and can debug regular JavaScript / other is languages

The one disadvantage will surely be fixed in time so I never really
understand why people lament the imminent demise of DevMode


-- 
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 post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

Re: Progress bar during GWT bootstrap process?

[Peter Donald]

The easiest way to do that is to just have the base page have a
loading indicator and have the last action in your EntryPoint remove
the loading indicator. If you want progress as loads occur then you
can just update the progress level from each step in your EntryPoint.
HTH

On Tue, Oct 27, 2015 at 10:54 AM, Ali Akhtar <ali.rac...@gmail.com> wrote:
> When GWT based sites are first loaded, the browser shows a loading indicator
> as nocache.js is downloaded. But then, when nocache.js inserts the actual
> scripts, there's no loading indicator, and the user is left staring at an
> idle screen. Not a very good experience.
>
> Is it possible to show a progress bar indicator as the other gwt assets
> loaded during the bootstrap process, are downloaded?
>
> --
> 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 post to this group, send email to google-web-toolkit@googlegroups.com.
> Visit this group at http://groups.google.com/group/google-web-toolkit.
> For more options, visit https://groups.google.com/d/optout.



-- 
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 post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.