Developing with GWT is pretty damn sweet (especially, because they have finally figured out how to do layout properly [2]).
I wonder how they do that. One project I worked on did all the layout on the server side. If your connection is low latency it is reasonably fast. Other than doing things impossible with CSS, this approach is also immune to browser-specific layout bugs. There's no reason doing your own layout calculations can't be done on the browser.
But CL as a language is so much better suited than Java for the kind of service-oriented APIs that one implements with GWT. Thus, a combination of ABCL and Parenscript would be a perfect replacement for GWT.
Parenscript, your proposed object sharing system, and a nice way to interface that with ExtJS (best JS UI library IMO, but a pain to do anything dynamic with) would do everything that GWT does, in a much better way.
Vladimir
[1] https://bespin.mozillalabs.com/ [2] http://2ality.blogspot.com/2010/02/next-generation-of-web-application-ui.htm...
On Feb 28, 2010, at 23:46 , Vladimir Sedach wrote:
I think it's a good idea for a library. Maybe as an extensions to Red Daly's PSOS? In any case, that would be one more idea to steal from HOP (http://hop.inria.fr/), which I think was doing object sharing before, and in a better way, than GWT.
As far as freedom and democracy, if someone requests a feature and it seems like a good idea, I will implement it.
-- Axel.Rauschmayer@ifi.lmu.de http://www.pst.ifi.lmu.de/~rauschma/
parenscript-devel mailing list parenscript-devel@common-lisp.net http://common-lisp.net/cgi-bin/mailman/listinfo/parenscript-devel