Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>We used SmartGWT in our last project (duration: 6 months). The following is my personal opinion:</p> <p>The widgets are really great! The documentation and API is verbose. We would use client-side again.</p> <p>The server-side integration works, but did not save any development time. Instead we had a lot of problems where we had to find workarounds. Also, because of the new API, no other developer can maintain the project within investing a lot of time to learn the SmartGWT API.</p> <p>Some Cons:</p> <ul> <li><p>You have to learn a totally new API instead of using Hibernate and GWT-RPC or REST.</p></li> <li><p>The data integration is done automatically, that is true. But if you need some (also little) changes, you have to write XML mapping files as with Hibernate or JDO. So the benefit is gone.</p></li> <li><p>The forum support is bad: You get an answer to almost every posted question. But that answer often does not help. They ask you things such as “why do you want to do that”. Or they say: “use our tool and do XYZ with it” three times, although again and again I told them this suggestion does not work. After a few answers to a question the final answer is: “you need training, buy our support”.</p></li> <li><p>The commercial support is way to expensive (costs approximately as much as the SmartGWT license).</p></li> </ul> <p>We will probably not use the server-side integration of SmartGWT again.</p> <p>You can read all my "lessons learned" with Pros and Cons at my blog:</p> <p><a href="http://www.kai-waehner.de/blog/2010/12/11/lessons-learned-smartgwt-2-3-component-library-for-google-web-toolkit-gwt/" rel="noreferrer">http://www.kai-waehner.de/blog/2010/12/11/lessons-learned-smartgwt-2-3-component-library-for-google-web-toolkit-gwt/</a></p> <p>Best regards, Kai Wähner</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. This table or related slice is empty.
    2. VO
      singulars
      1. This table or related slice is empty.
    3. VO
      singulars
      1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload