I released a GUI related project called Wi.Ser (Widget Server) which is a Java/XML server-side GUI-framework that enables an application to run as either a monolithic Swing app, a client/server Swing app, or as a Web app without any change.
It includes a mixed deployment mode, which supports one server to serve Swing clients and Web clients at the same time. The framework uses XML to define an application's GUI. It provides a common widget-based, object-oriented programming interface for Web and Swing GUIs, which prevents the developer from struggling with HTML and HTTP or with the internals of Swing. For Swing client/server applications the client/server split as well as the client/server communication is handled transparently by the framework.
The project includes a GUI builder that is based on the framework's functionality.
I need feedback on my work for further development. Please tell me what you think about the approach and the software.
I do not know AUIML very well but by reading the corresponding articles and looking at the AUIML examples I think I learned the following:
Compared to AUIML my approach is similar in rendering one XML GUI definition either into HTML or into Swing. But that's all. As far as I know AUIML does not handle the client/server split in case of using a thin Swing client. I think it does not extend the abilities of the target channels to a common set of features (e.g. window system with moveable and resizeable windows for Web/HTML or tables which are able by default to render every other widget in their cells or drag&drop support in Web/HTML, ...). For me the most interesting thing (and advantage) in AUIML is the eclipse plugin for building the GUIs. This is something which I do not support at the moment. If you look deeper you will find more diffs I think.