There are some problems.
Local data storage Swing applications can use a disk to store data. Assuming that the local data store available in HTML 5 is working, it will still be difficult to automatically reassign file / disk access for local data store calls.
Multithreading and synchronization Swing applications typically create threads, and this is not possible with GWT. Itβs hard to get it right.
Network Access Swing applications can connect to arbitrary network locations that do not work with GWT.
Using Java functions that are not available in the browser Everything that is outside the java kernel is not available, so the automatic port will most likely fail.
Optimize memory and performance Garbage patterns are completely different. How do you optimize optimal download sizes? How can you map multiple rotation screens to use something like code splitting for better performance?
Look and feel Everything said and done, you have to get your hands infected in order to write CSS code in order to get the right look. An automatic port cannot do this.
Given all this, I think that this is not possible for anything other than trivial applications. And for trivial applications, you can also rewrite the code.
source share