Link Details

GWT 2.5 version is out. The aim of this post is to share my experience, opinion, my critics about GWT

Posted by kmahdi  |   Nov 21 2012 / 09:17

Add your comment


Html tags not supported. Reply is editable for 5 minutes. Use [code lang="java|ruby|sql|css|xml"][/code] to post code snippets.

Comments

User 411746 avatar

nikolas.lotz replied ago:

>>> It isn't the ideal technology choice to do prototyping

 >>> making even sample application working take time and effort [code class="java"] Did you try utilizing one of the (gwt-)maven archetypes available? That should enable anyone to create a "GWT development best practices" application from scratch within a few minutes ( e.g. http://mojo.codehaus.org/gwt-maven-plugin/user-guide/archetype.html ). 
[code class="java"][/code> >>> (using embedded Jetty), testing a small change of the source code take long time That sounds odd. Small changes in client code should always recompile pretty much instantly while in development mode. What kind of hardware are you using and how much memory do you allocate for the JVM ( -Xmx... )? >>> In the reality the generated java script is not really cross browser compatible (as promised) Could you please elaborate or give a simple example? >>> Documentation isn't the biggest advantage of GWT Agreed, again.

Reply 0 votes
User 411746 avatar

nikolas.lotz replied ago:

How does formatting work in these comments!? [[---quote---]] It isn't the ideal technology choice to do prototyping [[---comment---]] Agreed. [[---quote---]] making even sample application working take time and effort [[---comment---]] Did you try utilizing one of the (gwt-)maven archetypes available? That should enable anyone to create a "GWT development best practices" application from scratch within a few minutes ( e.g. http://mojo.codehaus.org/gwt-maven-plugin/user-guide/archetype.html ). [[---quote---]] (using embedded Jetty), testing a small change of the source code take long time [[---comment---]] That sounds odd. Small changes in client code should always recompile pretty much instantly while in development mode. What kind of hardware are you using and how much memory do you allocate for the JVM ( -Xmx... )? [[---quote---]] In the reality the generated java script is not really cross browser compatible (as promised) [[---comment---]] Could you please elaborate or give a simple example? [[---quote---]] Documentation isn't the biggest advantage of GWT [[---comment---]] Agreed, again.

Reply 0 votes
User 331442 avatar

kmahdi replied ago:

Thank you for sharing your knowledgeable with us. <<>> In the reality the generated java script is not really cross browser compatible (as promised) <<>> Could you please elaborate or give a simple example? <<>> I'll check in our bug trucking tool, I'm sure that we fixed some bugs concerning the compatibility between IE and firefox. <<>> http://mojo.codehaus.org/gwt-maven-plugin/user-guide/archetype.html >> We are already using this archetype but it's only create a sample application. But I don't agree that the generated application contains the "best practices''.Just to create 2 screens, you need to create: 2 places, 2 activities, , DTO, View, ViewImpl class, UIBinder file, some events, some event handlers, place mappers, module inject...lot of plumbing.

Reply 1 votes
User 388907 avatar

MCII replied ago:

GWT probably isn't future-proof. I'd stick to JSF2.

Reply 0 votes
User 983885 avatar

infovation_Softwares replied ago:

i had started learning GWT , but as Goog started pulling the rugs off its feet , i gave up. now i a happy with my decision i made a year ago. :-)

Reply 0 votes

Recommended Links

Scala
Written by: Ryan Knight
Featured Refcardz: Top Refcardz:
  1. Apache Hadoop
  2. Play
  3. Akka
  4. Debugging JavaScript
  5. Design Patterns
  1. Apache Hadoop
  2. REST
  3. Java
  4. Git
  5. Java Performance
Connect with DZone