No announcement yet.
  • Filter
  • Time
Clear All
new posts

    Best practice SmartGWT -> SmartClient migration

    Hi Isomorphic,

    as you might know GWT seems not to be in really active development anymore (see their git log).
    My partners now ask me "What happens if GWT development is stopped". I assume that your answer is "Bad for people using GWT Widgets, no problem for SmartGWT, which just needs the Java-to-JavaScript compiler".
    But that's just my assumption. Do you see any possible problems for current SmartGWT projects if GWT development would be stopped?

    Also, related, did you ever migrate a SmartGWT project to SmartClient? Is there a best practice?
    I could think of these options:
    • Migrate by hand, SmartGWT class -> SmartClient isc.ClassFactory.defineClass("myClass", "theJavaExtends")
      • If doing so, do you see an advantage in using XML Components if there are no separate design / development persons in a company, where design could modify the Components XML?
    • Compile with GWT as pretty as possible, use, format and adjust result a looong time
    Is there a demo project one should start SmartClient development with? Do you have any recommendations w.r.t "source control in many files -> 1 application JS file"?

    Best regards

    We've already covered this on the blog. GWT development changed a while ago, but the technology still has a positive future:

    If someone wanted to convert from SmartGWT to SmartClient for some other reason, like a sudden desire to use JavaScript instead of Java, or a project that requires a lot of reflection usage where GWT is weak/complicated, then we would recommend first rebuilding a couple of screens without reference to the existing SmartGWT codebase, to get the hang of how things differ in SmartClient and to find a personal/team style of file organization, and then manual conversion.

    There would be no reason to start using Component XML specific to SmartClient. You either wanted to use it with SmartGWT and keep using it, or you didn't and don't.


      Hi Isomorphic,

      do you know about J2CL? It's still alpha, but seems to be the perfect GWT replacement for you (see here) (IFF there ever is a problem with GWT), as it focuses on the Java to JavaScript Compiler, and leaves away the Widgets etc, you are not using anyway.
      Also it seems that there is way more development taking place there right now compared to GWT.

      I assume debugging will also involve source maps and some kind of SuperDevMode, but I did not find details on this, yet.
      I know that we don't need this now, but it's good to know that there is going to be some Java-to-Javascript compiler even if GWT development slows down.

      Best regards


        GWT development is not dead, there are current and numerous conversations about GWT3 using J2CL.
        You can participate here:

        Reactive GWT looks very interesting and promising, it turns the whole reasoning upside-down by seeing user interaction as a stream of events:

        Finally j2cl is out in the wild if you want to give it a spin, they also have an explanation on how it is different from GWT

        If you need any other input feel free to reach out:


          Hi lpolvani,

          yes, I also found the link in the meantime.
          Good to see that there is still active GWT development talking place.

          Thank you & Best regards