Re: Struts vs. Something Else POC

Just curious if you've considered the Eclipse RCP for your client server app.  Here's an article I found interesting http://www.eclipse.org/articles/Article-RCP-1/tutorial1.html

What made me think of it regarding your particular application, is that with Eclipse 3.1, certain tasks have an option of running in the background. So, if you have a user ready to submit data to the server, the task can run in the background while the user continues work on another screen.

The above article describes the improvements in the RCP beginning with 3.0 and 3.1

  ----- Original Message ----- 
  From: Karen Collins 
  To: [email protected] 
  Sent: Monday, January 02, 2006 9:31 PM
  Subject: [Juglist] Struts vs. Something Else POC


  Thought this might be interesting to someone due to recent posts. My next work assignment is to research GUI frameworks for some upcoming green fields projects. Currently Struts is our standard, but we will be doing work requiring consistent keyboard response times for heads down data entry and question if a web framework is even the way to go. 

  We will be looking at JSF with AJAX and at Swing as possible new directions. I will then code a Struts and one other version of our next project as throw away prototypes to compare them. If anyone is interested I will post the results. We will be measuring the following: 

      a.. Application speed – i.e., must support heads down data entry 
      b.. Developer learning curve – i.e., amount of time needed for a developer to reach a productive skill level. 
      c.. Flexibility 
        a.. Medical Dictionary integration 
          a.. Effort needed and complexity required to integrate 
          b.. Response time to spell check an object 
        b.. Support approved screen design layouts 
          a.. Drop down boxes populated via properties files and / or reference tables 
          b.. Necessary graphics need to be functional
        c.. Compatibility with Mercury test tools 
      d.. Operations reliability 
      e.. Software configuration requirements and footprint on client and server 
      f.. Licensing and maintenance cost 
  If anyone has any past experience along these lines I'd appreciate your comments. If anyone is interested in the results of this research, I'd be glad to post them.



------------------------------------------------------------------------------


  _______________________________________________
  Juglist mailing list
  [email protected]
  http://trijug.org/mailman/listinfo/juglist_trijug.org

_______________________________________________
Juglist mailing list
[email protected]
http://trijug.org/mailman/listinfo/juglist_trijug.org