Patent Application
20060195794
The present invention relates to computer user interfaces.
User interfaces are the primary means by which computer users interact with computers. A user interface generally includes a display of one or more controls that provide information to a user, generally in visual form, and receive information from the user to instruct a computing device. One of the primary goals of user interface design is to provide a host of functions to a user in a simple, intuitive form.
As computer software and hardware provide more and more complex functionality, it becomes increasingly important to provide user interfaces that allow users to navigate such complex functionality in a relatively simple and intuitive manner. One area where more and more complex functionality is being provided is in automated business applications. Such software is generally used by a business to automate, or electronically facilitate some or all of the business's functions. For example, computers are now used to track inventory, manage a human relations department, perform accounting functions, as well as a host of other functions. Since virtually ever company's demands for a business application vary, it would be inefficient to write a complete business solution for each such company from scratch. Instead, such applications are generally created in two parts. First, a software company, such as Microsoft Corporation of Redmond, Wash., will create a development framework to provide significant tools and software classes related to businesses. Then, a developer, such as an Independent Software Vendor (ISV), will build a tailored or customized business application specific to a company using the framework application. This regime is highly successful in that it provides extremely powerful and adaptable tools in such a manner that they can be significantly tailored and customized in order to match a company's needs.
One potential drawback of the manner in which such software is developed, is that if the company or ISV wishes to alter the manner in which the user interface is displayed, or any parameter therein, it is necessary for the source code of the application to be modified. When the source code is modified, it is also then necessary to recompile the source code in order to provide a working altered application. This process is cumbersome because it requires significant work from the ISV. Thus, users of such software and/or ISVs have been discouraged from making changes to user interface elements in these types of situations.
It would be a significant benefit to the art if the user interfaces could be more easily changed or customized, without having to recompile the source code.
User interface element property customization is provided. An application requiring a user interface attempts to load a user interface modification resource. If the resource fails to load, a default user interface is provided. However, if the resource successfully loads, modifications set forth in the resource are applied to appropriate user interface elements. The modification resource can be in the form of Extensible Markup Language (XML), a database, or any other suitable data storage format. As each customization is applied to each user interface element, information about the user interface code itself is used to adjust the customization information prior to application of the customization information to the user interface element. Finally, if the layout of the user interface will be impacted by the customization, the layout is preferably accommodated by adjusting the layout of one or more other user interface elements.
The invention is operational with numerous other general purpose or special purpose computing system environments or configurations. Examples of well-known computing systems, environments, and/or configurations that may be suitable for use with the invention include, but are not limited to, personal computers, server computers, hand-held or laptop devices, multiprocessor systems, microprocessor-based systems, set top boxes, programmable consumer electronics, network PCs, minicomputers, mainframe computers, telephony systems, distributed computing environments that include any of the above systems or devices, and the like.
The invention may be described in the general context of computer-executable instructions, such as program modules, being executed by a computer. Generally, program modules include routines, programs, objects, components, data structures, etc. that perform particular tasks or implement particular abstract data types. The invention is designed to be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, program modules are located in both local and remote computer storage media including memory storage devices.
With reference to
Computer 110 typically includes a variety of computer readable media. Computer readable media can be any available media that can be accessed by computer 110 and includes both volatile and nonvolatile media, removable and non-removable media. By way of example, and not limitation, computer readable media may comprise computer storage media and communication media. Computer storage media includes both volatile and nonvolatile, removable and non-removable media implemented in any method or technology for storage of information such as computer readable instructions, data structures, program modules or other data. Computer storage media includes, but is not limited to, RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disks (DVD) or other optical disk storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to store the desired information and which can be accessed by computer 110. Communication media typically embodies computer readable instructions, data structures, program modules or other data in a modulated data signal such as a carrier wave or other transport mechanism and includes any information delivery media. The term “modulated data signal” means a signal that has one or more of its characteristics set or changed in such a manner as to encode information in the signal. By way of example, and not limitation, communication media includes wired media such as a wired network or direct-wired connection, and wireless media such as acoustic, RF, infrared and other wireless media. Combinations of any of the above should also be included within the scope of computer readable media.
The system memory 130 includes computer storage media in the form of volatile and/or nonvolatile memory such as read only memory (ROM) 131 and random access memory (RAM) 132. A basic input/output system 133 (BIOS), containing the basic routines that help to transfer information between elements within computer 110, such as during start-up, is typically stored in ROM 131. RAM 132 typically contains data and/or program modules that are immediately accessible to and/or presently being operated on by processing unit 120. By way of example, and not limitation,
The computer 110 may also include other removable/non-removable volatile/nonvolatile computer storage media. By way of example only,
The drives and their associated computer storage media discussed above and illustrated in
A user may enter commands and information into the computer 110 through input devices such as a keyboard 162, a microphone 163, and a pointing device 161, such as a mouse, trackball or touch pad. Other input devices (not shown) may include a joystick, game pad, satellite dish, scanner, or the like. These and other input devices are often connected to the processing unit 120 through a user input interface 160 that is coupled to the system bus, but may be connected by other interface and bus structures, such as a parallel port, game port or a universal serial bus (USB). A monitor 191 or other type of display device is also connected to the system bus 121 via an interface, such as a video interface 190. In addition to the monitor, computers may also include other peripheral output devices such as speakers 197 and printer 196, which may be connected through an output peripheral interface 195.
The computer 110 is operated in a networked environment using logical connections to one or more remote computers, such as a remote computer 180. The remote computer 180 may be a personal computer, a hand-held device, a server, a router, a network PC, a peer device or other common network node, and typically includes many or all of the elements described above relative to the computer 110. The logical connections depicted in
When used in a LAN networking environment, the computer 110 is connected to the LAN 171 through a network interface or adapter 170. When used in a WAN networking environment, the computer 110 typically includes a modem 172 or other means for establishing communications over the WAN 173, such as the Internet. The modem 172, which may be internal or external, may be connected to the system bus 121 via the user input interface 160, or other appropriate mechanism. In a networked environment, program modules depicted relative to the computer 110, or portions thereof, may be stored in the remote memory storage device. By way of example, and not limitation,
Memory 204 is implemented as non-volatile electronic memory such as random access memory (RAM) with a battery back-up module (not shown) such that information stored in memory 204 is not lost when the general power to mobile device 200 is shut down. A portion of memory 204 is preferably allocated as addressable memory for program execution, while another portion of memory 204 is preferably used for storage, such as to simulate storage on a disk drive.
Memory 204 includes an operating system 212, application programs 214 as well as an object store 216. During operation, operating system 212 is preferably executed by processor 202 from memory 204. Operating system 212, in one preferred embodiment, is a WINDOWS® CE brand operating system commercially available from Microsoft Corporation. Operating system 212 is preferably designed for mobile devices, and implements database features that can be utilized by applications 214 through a set of exposed application programming interfaces and methods. The objects in object store 216 are maintained by applications 214 and operating system 212, at least partially in response to calls to the exposed application programming interfaces and methods.
Communication interface 208 represents numerous devices and technologies that allow mobile device 200 to send and receive information. The devices include wired and wireless modems, satellite receivers and broadcast tuners to name a few. Mobile device 200 can also be directly connected to a computer to exchange data therewith. In such cases, communication interface 208 can be an infrared transceiver or a serial or parallel communication connection, all of which are capable of transmitting streaming information.
Input/output components 206 include a variety of input devices such as a touch-sensitive screen, buttons, rollers, and a microphone as well as a variety of output devices including an audio generator, a vibrating device, and a display. The devices listed above are by way of example and need not all be present on mobile device 200. In addition, other input/output devices may be attached to or found with mobile device 200 within the scope of the present invention.
As illustrated, custom application 400 preferably employs operating system 134, 212 to generate user interface 404 via one or more application programming interfaces 304. In accordance with one embodiment of the present application, custom application 400 accesses user interface modification resource 406. Resource 406 may take any suitable form including an Extensible Markup Language (XML) file, or a database, or any other suitable data structures. Resource 406 includes information relative to one or more modifications to be made to the default user interface specification 402 at run-time. When application 400 is initialized, it attempts to access external resource 406. If resource 406 is not found, application 400 simply loads as normal using default user interface specification 402. However, if custom application 400 does successfully load resource 406, it will parse the contents of resource 406. Resource 406 preferably includes specific information relative to individual user interface elements and their associated properties and the values of those properties. Only user interface elements that are to be changed are generally specified in resource 406. Accordingly, application 400 will apply the property changes to specific user interface elements specified in resource 406 and then load user interface 404. For example, while default user interface specification 402 may specify user interface 404 identically to user interface 306 (illustrated in
In block 506, the loaded modification resource 406 is parsed to generate a hash table that allows lookup of a user interface element and its associated meta-data. An exemplary element of this hash table is illustrated at block 512 with element 514 having meta-data 516 that includes such things as the name of the user interface element; the property to be customized; the values of those properties; and any nested user interface elements contained within element 514. Once the hash table has been generated at block 506, control passes to block 518 by moving to the first or top element in resource 406. Preferably, resource 406 lists the user interface modifications in a hierarchical manner such that the first element within resource 406 is also the parent of all elements therein. However, this is merely a preference, and many other variations of storage formats within resource 406, and processing regimes can be used. At block 519, the hash table is consulted to lookup any meta-data in the hash table for the element at the top of the chain. Preferably a data structure, such as that illustrated at 514, provides relevant information for that particular user interface element. Once the information has been obtained from the lookup table, control passes to block 520 where the customization is applied to the appropriate user interface element. A more detailed description of the application of a customization is described below with respect to
At block 606, the adjusted customization information is applied to the user interface code. In some embodiments, the customization of a user interface element may change the layout or size of that particular user interface element. This layout change may then interfere with one or more other elements in the user interface.
In accordance with embodiments of the present invention, once the adjusted customization information is applied as described with respect to block 606, the effect of the customization is actually measured, or otherwise obtained, as illustrated in optional block 608. For example, if the text of a control is changed from “button” to “customized_button” the actual length of the text will likely require the physical control, such as a button, to become larger as well. The larger button may then not align properly with other controls, or it may even overlap other controls.
If the customized element will not impact user element layout, control passes along line 610 and method 600 ends. However, if the layout will be impacted, control passes along 612 to block 614 where the actual layout of the user interface is adjusted to accommodate the re-sized customized UI element. This accommodation can take the form of simply moving one or more elements that may otherwise interfere with the adjusted UI element. However, adjusting the layout to accommodate the re-sized user interface element can also include adjusting other elements to align them with the re-sized element. For example, if the re-sized button becomes wider than all other buttons, it may be used to generate a button width for all other buttons that are aligned vertically with the re-sized button. Additionally, another aspect of user interface element modification includes the ability to allow resource 406 to specify a completely new location on the user interface for a modified element.
In conclusion, embodiments of the present invention generally allow high quality user interface customization to be done without re-compiling applications. Moreover, if the customization should fail, for one reason or another, applications, in accordance with embodiments of the present invention, simply load a default user interface.
Although the present invention has been described with reference to particular embodiments, workers skilled in the art will recognize that changes may be made in form and detail without departing from the spirit and scope of the invention.
