Interpreted remote user interface for medical applications

Medical applications often need to be extended or new functionality need to be added. This is usually done by plugins. These plugins usually provide extensions both for data processing and user-interface part and this idea is encouraged by the fact that GUI might be just remote access to data processing core. Unless we want introduce double-plugin architecture, we need to provide a way to data processing extension to define its own user-interface needs. The best way to this is to use some kind of user-interface description language and by interpreting constitute the user-interface.
The interpreter should be platform independent and should provide both local and remote access functionality (e.g. client/server architecture). On client side, the interpreter will interpret the user-interface definitions, display the results in respective way and report user response. On server side, it will provide a connection to code (C++).

The interpreter must manage UI-Request and UI-Action objetcs.

In a client/server application the client sends a UI-Request and receives an
UI-Action asociated to the UI-Request.

• Create a platform independent (at least for Windows/Linux) client/server system.
• The system should take care of local/remote connection, the client should constitute user-interface from received description, should display results in respective way and report user action.
  
• The server should be responsible for communication of client with respective plugins.

Eduard Gröller  <groeller@cg.tuwien.ac.at>
Tel.: 58801 18682

Alexandra La Cruz  <alacruz@cg.tuwien.ac.at>
Tel.: 58801 18670