Why does this interface builder approach differ from conventional layout based tools?
Generally the development of appropriate forms is split up into the design of the layout of the form and the programming of logical aspects e.g. by implementing the data type. With conventional tools user interface designers are able to edit the layout of the form visually whereas the logical part is done by programming. Unfortunately both tasks are not coupled with each other and the tool cannot assist the designer in important aspects e.g. in deciding whether all data is visually presented.
On the other hand our model based visual interface builder will be equipped with all relevant information about the logical structure of the application domain and would already provide the developer with a good suggestion for the layout. Most importantly the layout only would have to be adjusted and wouldn't need to be created from scratch. This should reduce development time drastically and can eliminate a whole set of common errors that cannot be checked by conventional layout based interface builders.
M. Frank and P. Szekely( 1998). Adaptive Forms: An interaction paradigm for entering structured data. In: Proceedings of the International Conference on Intelligent User Interfaces( San Francisco, USA, January 6-8), 153-160.
A. B. Girgensohn Zimmermann, A. Lee, B. Burns, and M. E. Atwood( 1995). Dynamic forms: An enhanced interaction abstraction based on forms. In: Proceedings of Interact'95, Fifth IFIP Conference on Human-Computer Interaction( London, England), 362-367.
G. Klein( 1997). Die objekt-orientierte Bedienoberflächenbibliothek EasyGUI. Fortgeschrittenenpraktikum, Technische Universitat München.
S. Schreiber( 1994). Specification and Generation of User Interfaces with the BOSS-System. In Human computer Interaction, Selected Papers EWHCI'94 Conference, Springer LNCS 876.
S.Schreiber( 1997). Spezifikationstechniken und Generierungstechniken für graphische Ben utzungsoberflächen. Dissertation, Technische Universität München.