Thank you. The event model is probably the aspect of jSeamless I'm most proud of.
I am actually working on version 2.0 of jSeamless to deal with a lot of the "lessons learned" from 1.0. It is slowly taking shape and probably will not have a lot happening with it for some time yet, but one of the major issues with 1.0 is new implementations. I've realized that there is much greater complexity in creating a new implementation of jSeamless than there need be and 2.0 is being designed with simplicity in mind for a core that can be extended. I have done some initial testing with Swing as I'm planning to write a Swing implementation and an ICEFaces implementation simultaneous as I'm developing it.
All this is to say that though it is very possible to develop new implementations using jSeamless 1.0 if you are willing to assist in the process of developing version 2.0 I would welcome the help and at the same time you would be able to build an implementation with WingS much more simplistically. Realize that 2.0 is not at all complete even in framework concept yet, but at this time I'm considering only supporting the Flex implementation in 1.0 and focus on 2.0 to fully realize the intent of jSeamless.
If you'd like to see what I've put in place thus far you can see it here:
http://jseamless.googlecode.com/svn/framework/branches/2.0/There are some drastic ideological changes from 1.0 that though I don't think any other UI framework has ever done before, I think they make for the next generation of UI development. If you (and anyone else for that matter) are interested in collaborating on ideas for for 2.0 let me know and I'd be happy to discuss each aspect I'm considering in the forums as it's being molded. There are others I'm also working with to develop the ideas, but much of it has come from using other frameworks since I've been developing jSeamless and limitations I've found in 1.0 or just standard limitations of UIs in general that could be resolved by changing structure.