Object-oriented user interface: Difference between revisions

Revision as of 19:00, 6 November 2007

Revision as of 11:19, 9 November 2007

Line 31:

The [[IBM Common User Access | CUA]] guidelines stated that 'In an object-oriented user interface, the objects that a user works with do not necessarily correspond to the objects, or modules of code, that a programmer used to create the product.'<ref name = "cua">IBM, Common User Access - Guide to User Interface Design. 1991, IBM: Cary, North Carolina.</ref>

Mark Vanvan Harmelen states that 'Object-oriented user interface design does not require designers to take an object-oriented view of the problem from the beginning of the project. . .Furthermore, even if designers take an object-oriented perspective throughout, they will benefit from focusing separately on the object model and the object-oriented user interface design.'<ref name="harmelen">Vanvan Harmelen, M., ed. Object Modelling and User Interface Design. 2001, Addison-Wesley: Reading, MA.</ref>

By contrast, the [[naked objects]] pattern is an approach to the design of applications that enforces a direct correspondence between the objects represented in the OOUI and the underlying ___domain objects, auto-generating fhe former from the latter.<ref name="pawson">Pawson, R., Naked Objects, Ph.D Thesis, 2004, Trinity College, Dublin, Ireland</ref>