Spring 3 and JS client to ease developer burden?

Interesting post on architecture choices - after we upgrade to Spring
3.0 our Mapping/GIS module will be along the lines proposed - perhaps
easing development for some as suggested?

···

---------- Forwarded message ----------
From: John DeRiggi <j_deriggi@yahoo.com>
Date: Fri, Apr 16, 2010 at 8:33 AM
Subject: Re: [OPENMRS-DEV] User Interface Frameworks, again
To: openmrs-devel-l@listserv.iupui.edu

I'm going to throw my vote in for spring 3.0 or some other REST
provider and a js client.
Reasons:
1) JSP and JSF are too much Java at the web tier. Developing the view
should not necessitate having an in depth knowledge/understanding of
the data model.
2) Writing some modules would be easier. Imagine if OpenMRS's
documentation looked like this:
http://developer.nytimes.com/docs/congress_api
Then, perhaps some module writers would be alleviated from the
requirement of knowing Java, eclipse,dependcy injection, AOP, and
JSTL in order to write a simple module. Those more familiar with
OpenMRS and its core could write the fine grained services to which
web developers would be the client of.
Thats all.
PS side note - we're using spring jdbctemplates at work which is a
nice break from hibernate.

________________________________
From: Jaime Hablutzel Egoavil <hablutzel1@GMAIL.COM>
To: openmrs-devel-l@LISTSERV.IUPUI.EDU
Sent: Mon, April 12, 2010 11:03:05 PM
Subject: Re: [OPENMRS-DEV] User Interface Frameworks, again

+1 to JSF + Icefaces + Facelets

On Mon, Apr 12, 2010 at 9:55 PM, shazin sadakath <s2_zat@yahoo.com> wrote:

Hi Darius,
Yeah sure. There is this Tutorial link provided by ICEFaces itself.
http://www.icefaces.org/main/resources/tutorials.iface
You must be registered but it is worth it. It even has a tutorial for
porting your JSP App to JSF App.
Regards,
Shazin

________________________________
From: Darius Jazayeri <djazayeri+pih@GMAIL.COM>
To: openmrs-devel-l@LISTSERV.IUPUI.EDU
Sent: Tue, April 13, 2010 12:55:17 AM
Subject: Re: [OPENMRS-DEV] User Interface Frameworks, again

Hi Shazin,
Do you know of a good introductory tutorial to JSF and/or to ICEfaces? I'd like to read through them myself and get up to speed.
-Darius

On Thu, Apr 8, 2010 at 8:27 PM, shazin sadakath <s2_zat@yahoo.com> wrote:

I am in for JSF + ICEFaces. I have a fair bit of experience in ICEFaces.
Happy to volunteer :slight_smile:
Shazin

________________________________
From: Darius Jazayeri <djazayeri@GMAIL.COM>
To: openmrs-devel-l@LISTSERV.IUPUI.EDU
Sent: Fri, April 9, 2010 5:14:19 AM
Subject: [OPENMRS-DEV] User Interface Frameworks, again

Hi All,
April has arrived, I'm now working full-time on OpenMRS, and I want to pick up the UI Redesign thread again. If you want a refresher see the original thread and a followup. And see an email I just sent to some non-OpenMRS people that describes what we're looking for.
I've created a wiki page called OpenMRS 2.0 UI Framework to start tracking this project going forwards. (It currently includes no more than is in this email.)
The issue at hand is that we have a one-time-only chance to pick a new UI framework, and we want to pick the right one for our needs. It needs to let us produce good user interfaces, quickly, and without a steep learning curve. It needs to let us create reusable components. And it needs to do so in the context of our modular architecture.
We're going to do a "bake-off", where different people prototype one particular example in ~5 different frameworks. Once that's done, everyone who's interested can check out what the code looks like, and how easy it is to modify.
Here's the current list of frameworks we're considering. (This isn't set in stone, but we're also not going to be able to prototype every option out there.)

Spring MVC 3.0 + RIA framework (Ext JS, ...)
Spring MVC 3.0 + javascript UI framework (jquery-ui, YUI, ...)
Grails + RIA framework
Grails + javascript UI framework
JSF + ICEfaces
GXT
JSR-168 Portals

OpenMRS becomes a portal container. People can write portlets in any technology they want.
We still have to choose a technology to create our core portlets.

I suspect these won't make the cut, but they're cool, so I'd like to hear arguments for including them:

Wicket
ZK

So, at this point, we need volunteers, for what promises to be quite a fun project. Want to play around with a new framework you haven't used before? Or show off your skills with one you're familiar with? Want to play a big role in driving the OpenMRS application's future? Then step up and volunteer to build an example app in one of these frameworks. You will not be judged on how pretty your UI looks, so if you're graphically-challenged, don't let that deter you. (You, and the framework, will be judged on how concise and understandable your code looks, and how easy it is to extend.) The specific requirements for what you have to do are here.
Who's in?
-Darius
PS- If you're impatiently waiting to discuss the content of the UI, an email about that is coming in a few days.
________________________________
Click here to unsubscribe from OpenMRS Developers' mailing list
________________________________
Click here to unsubscribe from OpenMRS Developers' mailing list

________________________________
Click here to unsubscribe from OpenMRS Developers' mailing list
________________________________
Click here to unsubscribe from OpenMRS Developers' mailing list

--
Jaime Hablutzel

(tildes omitidas intencionalmente)
________________________________
Click here to unsubscribe from OpenMRS Developers' mailing list
________________________________
Click here to unsubscribe from OpenMRS Developers' mailing list

--
Cheers,
Knut Staring