> For the emulation changes I can live with what is available now and get > some more in a later release. But how does the gwt team decide which are > crucial and which ones can be done in a separate library ? The java.time > API should really be considered, the Date object has been deprecated for > ages. Right now I use moment.js with a JsInterop mapping to handle dates > and times. >
It is generally preferred to have JRE emulation within GWT itself instead of having separate libraries. Basically a single source of trust, which is well reviewed, tested and optimized. Also J2CL uses the same emulation and it might be beneficial to have J2CL experts take a look at the emulation code as well. There was someone who did java.time emulation but he never contributed it. It was based on the threeten repository on Github. Personally I think java.time should really be tackled by GWT because working with Date in Client code is a pain. Using momentjs works, however it is still a pain for code you want to share between client and server. (There is also a java.time emulation on Github somewhere which uses momentjs under the hood I believe) -- J. -- 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/google-web-toolkit-contributors/5fcf5659-b317-42bf-9ed9-61b3ca42b061%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
