On Sat, May 20, 2017 at 10:05 AM, Learner Evermore <[email protected]> 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 [email protected]. 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.
