Have Geek Brain

Rich Internet Applications

I am evaluating rich internet applications for use in the next project. I have heard of the following solutions -

  • Adobe flex
  • ExtJS
  • Jboss richfaces
  • ICEfaces
  • Oracle ADF
  • JavaFX
  • Silverlight
  • GWT

I want to know if there are more solutions available.

I would appreciate it if you could provide any valuable feedback on the above solutions.

+1


a source to share


3 answers


After evaluating and reading various RIA solutions, I finally chose GWT and GWT-Ext. I see these benefits for me and my team -



  • We're used to Eclipse, so this is an advantage.
  • The ability to use Java Debugger in Eclipse is extremely useful.
  • GWT Hosted mode in eclipse so no compilation and deployment is required on every change.
  • Large developer community
  • Many ready-to-use components
  • Java knowledge priority
  • Similar to a swing, and the team worked on Swing on an earlier project.
  • The look is also good.
  • Maven support is also available.
  • Junit test cases can be written.
  • Java does not require knowledge of other languages.
  • Simple RPC configuration based on annotations.
+1


a source


The IT Mill Toolkit is a "server-side" framework built on top of GWT.

Commentary: Coming from a heavy PHP and Java hostile background, I found the Toolkit very enjoyable to use quite quickly. Being able to write anything other than (strongly typed, well OO oriented) Java is good, given the fact that what you change in your code reflects pretty instantly on what you see in the browser.

A bit tricky to set up, but IT Mill has an Eclipse plugin that supposedly helps with this. The only thing is that the plugin itself is unintuitive to use :)

0,02 €



Reply to comment: The biggest difference between GWT and IMT is that GWT runs entirely in the browser (hostile / exploited environment like FireBug), whereas IMT only uses GWT to display server-side state. So while you can edit whatever values ​​you want in the browser with both GWT and IMT, GWT will happily accept user-modified variable values, IMT keeps track of the values ​​on the server side and doesn't allow for discrepancies between client and server.

Another big difference is that GWT widgets need to be compiled every time you make any changes to them with the relatively time-consuming GWT cross-compiler (compiles Java to JavaScript). IMT, on the other hand, only needs to be redistributed into the servlet container, and the changes are there, because the GWT widgets inside IMT do not need to be recompiled. With Tomcat, this is almost instantaneous (i.e., as soon as Tomcat notices that Eclipse has recompiled the classes on the fly).

@the_drow: not familiar with Dijit, here's the answer: Dojo is javascript only, which means only client side. Vaadin (née IT Mill Toolkit) lives partly on the server side (calls itself a "managed server"), so you can't hack the client side just by changing the values ​​of JavaScript variables. There's a chart that compares Vaadin to other comparable products. Dojo is not included, but JQuery, which is vaguely similar to Dojo

+6


a source


I've had experience with Spring Webflow + Rich Faces with mixed results - the time to get results on screen is really short, but it hurts to tweak part of the presentation.

those. if you are building some tech / backend / standard GUI oriented - this is ok, if you are going to build the interface used by millions of web2.0-ers you end up getting into the css / javascript presentation part.

+1


a source






More articles:


All Articles