I'd support this. I came away from JavaOne convinced that either GWT or
Wicket would be a great choice. GWT may eventually have some nice REST
stuff eventually, and integrates nicely with Ext.js right now, which
we're looking at a lot on the OpenLayers side.
But Wicket seems to be nicer for web designers, plays better with CSS,
and we have access to some designers. And the big thing is wicket is
entirely pluggable, which would be really nice for our module system.
But I think our UI choice doesn't have to be what others will use in
their modules, people could do a cool app on gwt, it'll just be the
reference.
So I'd be in favor of just trying for a GSIP proposal with Wicket, and
bypassing another big formal evaluation, and using the time to work on
rest api, 1.7.0, ect.
Chris
Justin Deoliveira wrote:
Hi all,
I have been wanting to send my thoughts about the UI evaluation for a couple of days now and finally got a chance to sit down and do so.
Basically I think we might be going overboard with doing an exhaustive evaluation. I think the reason why is because we are worried that a bad technology choice will lead to something that is hard to maintain like the current UI is today. But I dont really see this happening, I think we have learned enough from the current UI to figure out what mistakes we should avoid.
Wicket solves all of our problems and at the same time is a lively project that does not appear to be going anywhere anytime soon. These two factors make me confident enough it as a technology choice.
So... bottom line is my vote is to go with wicket, and forgo any more evaluation. I think we have done enough at this point to make an intelligent choice.
My 2c,
-Justin