Objects also have properties or attributes. Properties are the unique characteristics ofan object. Properties help to describe an object and can be changed by users. Examples of properties are text styles (such as normal or italics), font sizes (such as 10 or 12points), or window background colors (such as black or blue). Actions In addition to objects, there are actions. People take actions on objects. They manipulate objects in specific ways (commands) or modify the properties of objects (propertyor attribute specification). Commands are actions that manipulate objects. They may be performed in a varietyof ways, including direct manipulation or a command button. They are executed immediately when selected. Once executed, they cease to be relevant. Examples of commands include opening a document, printing a document, closing a window, and quitting an application. Property/attribute specification actions establish or modify the attributes or properties of objects. When selected, they remain in effect until deselected. Examples include selecting cascaded windows to be displayed, a particular font style, or a particular color. The following is a typical property/attribute specification sequence: 1. The user selects an object such as several words of text. 2. The user then selects an action to apply to that object, such as the action Bold. 3. The selected words are made bold and will remain bold until selected andchanged again. A series of actions may be performed on a selected object. Performing a series of actions on an object also permits and encourages system learning through exploration. Application versus Object or Data Orientation Earlier graphical systems were usually application-oriented, a continuation of the philosophy that enveloped text-based systems. When a text-based system was developed, it was called an application. As graphical systems evolved, developers usually thought in terms of applications as well. When a real picture of the user began to emerge, it finally became evident that people think in terms of tasks, not applications.They choose objects and then act upon them. An application-oriented approach takes an action:object approach, like the following: Action> 1. The user opens an application such as word processing. Object> 2. The user then selects a file or other object such as a memo. An object-oriented object:action approach does the following: Object> 1. The user chooses an object such as a memo. Action> 2. The user then selects an application such as word processing. The object:action approach permits people to focus more easily on their task and minimizes the visibility of the operating system and separate applications. Many experienced users may have difficulty switching from one approach to another because an old interaction behavior must be unlearned and a new one learned. New users should not experience these problems because it more accurately reflects a person’s thinking. In any one interface, it is critical that a consistent orientation be maintained, either an object:action or an action:object approach. Atin Dasgupta is director and founder of Leveljam. Web Development Company Mumbai Leveljam is an internet services agency from Mumbai, India focussed on providing cutting edge design and business solutions to the services & manufacturing sector with innovative approaches and advanced methodologies. Our Services include Web Design & Branding, Logo Design, Flash Animation, Application Development, Website Development, E-commerce Development, Content Management Solutions, Mobile Applications Development, Search Engine Optimization, Internet Marketing Solutions, Social Media Visibility & Management, Technical Support and Customer Service. For more information please visit our website www.leveljam.com
Related Articles -
Web Design Company Mumbai, Affordable Website Design Company Mumbai, best web design company Mumbai, Website Design Company in Mumbai,
|