Augmented I/O for limited form factor user-interfaces

The claimed subject matter relates to an architecture that can enhance and/or simplify tactile-based I/O transactions in connection with a user-interface (UI) of limited form factor. In particular, the architecture can monitor a position of a selector object such as an operator's finger relative to a UI display as the selector object hovers or moves above the UI display. Based upon this position, an analogous coordinate in the UI display can be determined, and a portion of the UI display substantially centered at the coordinate can be modified. As one example, the UI display can be modified to increase the magnification scale (e.g., a virtual magnifying glass) of the portion of the display indicated by the selector object.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is related to co-pending U.S. patent application Ser. No. 12/256,818 filed on Oct. 23, 2008, entitled, “TRACKING APPROACHING OR HOVERING OBJECTS FOR USER-INTERFACES.” The entirety of this application is incorporated herein by reference.

TECHNICAL FIELD

The present application relates generally to enhancing features associated with a user-interface (UI) of limited form factor, and more specifically to coupling UI updates to a position of a selector object hovering or tracking over the UI.

BACKGROUND

The consumer and commercial markets for mobile devices (or other devices of limited size or form factor) such as cellular phones, digital media players, Personal Digital Assistants (PDAs) and similar devices is rapidly growing and has been gaining momentum for some time. Advances in chip technology, ergonomics, user interface (UI) technology, software applications, and the like often spur additional growth potential for many of these devices. Accordingly, many mobile devices are becoming more powerful, capable of delivering increasing functionality, while at the same time becoming less expensive, more compact, and more convenient to operate and carry.

As a result, mobile devices or other devices of limited form factor have the potential to deliver a great deal of computational power. However, such devices also often underscore some of the fundamental challenges associated with the various limitations of these devices, such as small screen size, limited keyboard, short battery life, complex operation and/or high prices due to the need to embed UI components in such a small form factor. These and other limitations can substantially hinder the utility and proliferation of some mobile devices.

In accordance therewith, the consumer and commercial markets for these mobile devices are faced with difficulties in which current trends in the area do not appear adequate to solve. In particular, users of most mobile devices desire simpler, smaller, less expensive hardware, but on the other hand users also desire mobile devices that can provide a richer set of functionality, yet remain simple to use. Miniaturization of electronic devices has reached the point where significant computing power can be delivered in devices smaller than a matchbook. Hence, miniaturization is no longer the primary technological bottleneck for meeting the demands of consumers. Rather, the challenges are increasingly leaning toward the user interface of such devices. For example, technology exists for building a full-featured cellular phone (or other device) that is no larger than a given user's thumb, yet packing a display, keyboard, and other UI features in such a small area is all but impossible. Even devices that have opted to forego keyboards in favor of touch-screen I/O present numerous challenges for the implementation of a successful UI.

SUMMARY

The following presents a simplified summary of the claimed subject matter in order to provide a basic understanding of some aspects of the claimed subject matter. This summary is not an extensive overview of the claimed subject matter. It is intended to neither identify key or critical elements of the claimed subject matter nor delineate the scope of the claimed subject matter. Its sole purpose is to present some concepts of the claimed subject matter in a simplified form as a prelude to the more detailed description that is presented later.

The subject matter disclosed and claimed herein, in one aspect thereof, comprises an architecture that can simplify or enhance tactile-related input/output (I/O) in connection with a user-interface (UI) of limited form factor. In accordance therewith and to other related ends, the architecture can monitor a position of a selector object relative to a UI display as the selector object hovers above and/or tracks across the UI display. Typically, the selector object will be a device operator's finger, a stylus, or another suitable object. Based upon the position of the selector object, the architecture can update an output of the UI display.

In particular, the architecture can update a portion of the UI display that is local to (and moves or tracks with) the selector objector. For instance, the position can be mapped to a coordinate for the UI display, with the portion to be updated substantially centered at the coordinate. The update can relate to a change in the magnification scale for the portion of the UI display that is updated, in effect providing a virtual magnifying glass. Thus, certain elements in the UI display (e.g., determined by the position of the selector object) can be easier to recognize and/or select, yet the “big picture” can still be apparent. Given that the virtual magnifying glass can require that the selected portion of the UI display be redrawn at a larger scale, the virtual magnifying glass can be implemented to occlude neighboring elements of the UI display. Additionally or alternatively, these neighboring elements can be presented in a semi-transparent manner, or crowded together to fit in the remaining areas of the UI display. Moreover, the architecture can facilitate other updates beyond magnification, such as highlighting or other appropriate changes to RGB features of portions of the UI display.

The monitoring of the selector object and/or the updating of the UI display can be intelligently activated and deactivated in order to conserve power and maximize or tailor effective use. For example, one or both of the monitoring or the updating can be activated when a keyboard application is instantiated, and then deactivated when the keyboard application is closed. In some cases, the monitoring can be active, while the updating is inactive to allow gestures associated with the selector object to represent input, such as a gesture command to activate the virtual magnifying glass or another update.

The following description and the annexed drawings set forth in detail certain illustrative aspects of the claimed subject matter. These aspects are indicative, however, of but a few of the various ways in which the principles of the claimed subject matter may be employed and the claimed subject matter is intended to include all such aspects and their equivalents. Other advantages and distinguishing features of the claimed subject matter will become apparent from the following detailed description of the claimed subject matter when considered in conjunction with the drawings.

DETAILED DESCRIPTION

Referring now to the drawing, with reference initially toFIG. 1, system100that can enhance or simplify tactile-related input/output (I/O) in connection with a user-interface (UI) of limited form factor is depicted. In particular, tactile-related I/O can include, e.g., inputs provided by means of touch or gestures. Generally, system100can include tracking component102that can monitor position104of selector object106relative to UI display108. Position104is typically a salient point or feature of selector object106, or the nearest portion of selector object106to UI display108.

As depicted, selector object106can be a finger or thumb of an operator or user of a device (not shown) associated with UI display108. In addition, selector object106can also be a stylus or another physical object suitable for tactile-based I/O. Appreciably, selector object106can include a transmitter or other signaling hardware or special purpose material to aid in position tracking, however, such need not necessarily be the case. Rather, tracking component102can rely upon one or more camera that can detect objects proximal to UI display108. For example, UI display108, in addition to displaying content can also include one or an array of cameras. In other cases, tracking component102can monitor position104based upon techniques described herein and incorporated by reference.

Regardless of the type or range of sensors employed to determine position104, position104can include x-y values for a coordinate plane that is substantially parallel to a surface of UI display108. In addition, position104can also include a distance between selector object106and UI display108, which is here represented by a length of dashed line110. Line110can be substantially perpendicular to the surface of UI display108, intersecting UI display108at coordinate112, which can be additionally or alternatively described as the point or pixel over which selector object106is hovering as determined by a suitable sensing means. Appreciably, as selector object106moves, tracking component102can update position104commensurately, and therefore, if necessary, also update coordinate112. It should be understood that Cartesian coordinates are employed for the sake of ready understanding; however, it should be appreciated that polar coordinates or another coordinate system can be employed to map and/or track position104or coordinate112.

Additionally, system100can further include augmentation component114that can update (e.g. update116) an output of UI display108based upon position104of selector object106. More particularly, augmentation component114can update the output of UI display108at, or for an area centered at, coordinate112. In an aspect of the claimed subject matter, update116can relate to changing a display or magnification scale of a portion (e.g., a portion centered at coordinate112) of UI display108. These and other features will become more apparent with referenceFIGS. 2-4, which can be examined along sideFIG. 1for additional context and understanding.

Furthermore system100can also include or be operatively connected to data store118. Data store118is intended to be a repository of all or portions of data, data sets, or information described herein or otherwise suitable for use with the claimed subject matter. Data store118can be centralized, either remotely or locally cached, or distributed, potentially across multiple devices and/or schemas. Furthermore, data store118can be embodied as substantially any type of memory, including but not limited to volatile or non-volatile, sequential access, structured access, or random access and so on. It should be understood that all or portions of data store118can be included in system100, or can reside in part or entirely remotely from system100.

Turning now toFIG. 2, illustration200that exemplifies various features associated with preparing to update a display based a position of a selector object is provided. Example device202can be substantially any device that includes UI display108, an example of which is also illustrated here. Typically, device202is a mobile device contemplated to include a limited UI form factor such as a cellular or smart phone (or other device), media player, or Personal Digital Assistant (PDA). UI display108can be a “touch screen,” e.g. a touch-sensitive display that accepts an input based upon contact between UI display108and selector object106.

Implementing a touch screen can help mitigate the conflict between miniaturization and providing rich feature sets/easily navigable UIs. For example, rather than attaching a physical keypad/keyboard, the touch screen can provide virtual keys, thus removing the need to devote non-screen real estate to buttons or keys. However, when many elements are simultaneously displayed within UI108such as keys of a keyboard, photos in a photo album, folders or files in a directory, or other icons or graphical elements, certain difficulties can arise. One such example is the well-known “fat finger” difficulty, wherein due to the limited size of UI display108and a given number of elements displayed (e.g. the entire keyboard), each element can be smaller than an operator's finger, commonly resulting in multiple selection events when only one is intended or a selection of the incorrect element (e.g. pressing the wrong key). Unfortunately, changing the scale of each element or key implies that only a portion of the whole (e.g., only half of the keyboard) will be displayed at any given time, which can lead to other difficulties or inefficiencies and can further be less intuitive.

In order to mitigate these and other difficulties, augmentation component114can selectively update a certain portion of UI display108without necessarily affecting other portions of UI display108or changing the total number of elements displayed. In accordance therewith, example UI display108of illustration200includes numerous elements depicted as squares or blocks. As indicated supra, each of these blocks can represent a distinct key of a keyboard, a photo in an electronic album, a folder or file in a directory, an icon or the like.

Coordinate112, representing, e.g. the point or pixel over which selector object106is hovering is also depicted in illustration200. Thus, augmentation component114that can update an output of UI display108based upon position104of selector object106, can also map position104to coordinate112. The update can take to form of magnification or increasing the magnification scale of UI display108, but usually only within a certain area of effect. Accordingly, the magnification scale of certain portions of UI display108can be increased to simplify input or selection of an element, yet without compromising the operator's orientation or view of the whole (e.g., all the other elements, their respective relationships or relative locations).

In other words, augmentation component114can provide a virtual magnifying glass that increases a magnification scale of a portion of UI display108such that the portion is displayed at a different scale within an area of effect of the virtual magnifying glass. In this case, the portion of UI display108that can be magnified is represented by circle204, whereas circle206represents the area of effect of the virtual magnifying glass. Thus, visual data included in portion204, after magnification, will occupy the larger area206, and hence be capable of display at a greater magnification scale. Hence, because circle206has a radius that is approximately twice as large as circle204, graphical elements included in portion204can be updated to appear twice a large as would otherwise occur.

Appreciably, portion204and area206need not necessarily be circles, but can be other suitable shapes as well, but are illustrated here as circles merely to simplify explanation. Likewise, a 2-1 ratio between area206and portion204is selected to provide a convenient example; however, one can readily appreciate that other ratios can be employed. In fact, the sizes (as well as shapes) of portion204and area206can be determined independently from one another, yet, the size ratio between the two will typically represent the level of magnification (e.g., the change in magnification scale).

For example, portion204can be defined by operator preferences or defaults, yet can be intelligently adjusted to comport with the sizes of the elements of UI display108(e.g., the illustrated blocks). Accordingly, the magnified portions can be comparable to the size of elements of interest to an operator. Based upon such adjustments area206can, but need not, be adjusted as well. Similarly, area206can also be defined by operator preferences or defaults, but can be adjusted, potentially independently of the size of portion204, by, e.g. modifying the hover distance (e.g., distance110) of selector object106. For instance, decreasing the hover distance of an operator's finger over the surface of UI display108can increase the size of area206, while increasing the hover distance can decrease the size of area206. For instance, when selector object106hovers at the limits of detectable range, then the magnification scale can be set to 2 times normal or even no magnification. However, as selector object106crosses tiered thresholds relating to hover distance110(e.g., the z-axis of the coordinate plane), then the magnification scale can be increased by discrete amounts, such as 4×, 8×, and so on until the maximum magnification scale, say 16× is reached at actual contact (or within a few millimeters of actual contact) with UI display108. It should be appreciated that the magnification scale need not necessarily be multiples of 2, and further need not be integers. Hence, magnification can be 2.5× or similar.

Moreover, it should also be understood that while coordinate112is substantially based upon position104of selector object106, coordinate112can be further based upon or biased toward a central location of an element included in UI display108. Hence, while position104of the operator's finger might actually be mapped to a coordinate that is near the outer edge of the indicated element, or perhaps even beyond the edges of the element, coordinate112can be intelligently biased toward the center of the element since it can be inferred in many cases that the operator is not interested in selecting a portion of the screen that is not occupied by a selectable element or in magnifying portions of the background exiting between elements.

For the sake of thoroughness, it should be noted that providing a virtual magnifying glass is not necessarily limited to instances in which there are many discreet elements presented by UI display108. Rather, for example, UI display108can present a single element such as map or high-resolution photograph such that this single element occupies substantially all of UI display108. In this case, as selector object106traverses over the map or photograph, associated portions of UI display108can be resolved into clearer or more detailed depictions. Similarly, a element can be a thumbnail that, when magnified presents a larger scale view.

In addition, augmentation component114is not necessarily limited to application of a virtual magnifying glass, but can also provide other types of updates to UI display108. For example, augmentation component114can update the output of UI display108by affecting a change in a color, a contrast, a brightness level, or some other Red-Green-Blue (RGB) attribute of one or a set of pixels included in UI display108, typically pixels of one or more element associated with coordinate112and therefore, by proxy, associated with position104. As one example, consider again the situation in which example UI display108presents a virtual keyboard. As the operator's finger hovers over the surface, the key that is substantially beneath the finger can change color or be highlighted to provide a visual cue to aid in selecting the desired element in spite of other difficulties described herein or otherwise extant.

FIG. 3depicts illustration300that exemplifies a virtual magnifying glass that occludes neighboring elements. As withFIG. 2, example device202includes UI display108. In this case, with coordinate112again mapped approximately to the center of the element, portion204can now be redrawn and can be equal to area206in terms of size. Accordingly, when update116is applied, portion204is displayed at a different scale, the display of which can occlude neighboring elements in UI display108. For example, the elements occluded can be those within area of effect206, as depicted.

It should be appreciated that although not expressly depicted, according to an aspect of the claimed subject matter, the elements in UI display108excluded from portion204but within area of effect206of the virtual magnifying glass (e.g., those elements described above as occluded), can instead be updated to become semi-transparent in order to avoid total occlusion. Moreover, yet another implementation of the virtual magnifying glass is provided in connection withFIG. 4.

Referring now toFIG. 4, illustration400that exemplifies a virtual magnifying glass that facilitates crowding rather than occlusion is depicted. Once more, example device202with UI display108is provided. In this case, update116provided by, e.g. augmentation component114can (in addition to updating area of effect206) also modify UI display108in secondary area of effect402. In particular, augmentation component114can decrease the magnification scale for otherwise occluded neighboring elements, and can display such elements within secondary area of effect402in a crowded fashion. In other words, so as not to occlude the neighboring elements, those elements as well as elements slightly beyond area of effect206can be effectively reduced in size and/or crowded together to fit, whereas the remainder of UI display108can remain unaffected.

With reference now toFIG. 5, system500that can selectively trigger the monitoring or the updating is illustrated. Generally, system500can include tracking component102that can monitor position104relative to UI display108; and augmentation component114that can update UI display108according to position104, both as substantially described supra. In addition, system500can also include activation component502that can initiate at least one of the monitoring associated with tracking component102or the updating of UI display108associated with augmentation component114.

For example, activation component502can generate and transmit initiation message504to one or both tracking component102or augmentation component114. Initiation message504can thus trigger one or both the monitoring of position104or the updating of UI display104that is based upon position104. Similarly, in an aspect of the disclosed subject matter, activation component502can also send termination message506that can terminate operation of the monitoring and/or updating. Accordingly, while various features have been described herein relating to modifying portions of the display based upon position104of selector object106, it should be appreciated that such features can be selectively activated and/or deactivated when not needed or desired.

In an aspect, activation component502can initiate (or terminate) the monitoring by tracking component102or the updating by augmentation component114based upon various criteria or parameters, some or all of which can be provided by input508. For example, initiation message504(or termination message506) can be provided based upon a state of a device associated with UI display108. An illustration of this can be entering into (or exiting) a keyboard mode for the device. Thus, activation component502can obtain data relating to this state by way of input502. As another example, messages504or506can be provided based upon an application instantiated by a device associate with UI display108. For instance, calling/closing a photo album application can activate/terminate the monitoring and/or updating, when, e.g., input502indicating the particular application was instantiated or closed is received.

Of course, numerous other examples can exist. Activation component502can provide the suitable message based upon a number of graphical elements included in UI display108such as when UI display108is displaying a large list or a large number of files, folders, or icons. As another example, messages504,506can be provided based upon a magnification scale of the graphical elements included in UI display108. For example, when elements are displayed at relatively small scales, such can be a criteria (received or otherwise determined or obtained as input502) for activating the claimed features; or, likewise when the elements are displayed at a more normal scale or one that is determined or inferred to be easily distinguishable, then the updating can be terminated as magnification or other features can be less useful in those cases.

As yet another example, activation component502can initiate the monitoring or the updating based upon a complexity of one or more graphical elements. For instance, display of a highly complex element such as an image of a map or a photograph can prompt message504. In other cases, message504can be intelligently generated when a relatively large number of correction-based or undo-based device inputs (e.g., backspace, delete . . . ) are detected. It should be further appreciated that settings related to triggering the monitoring or updating can be defined by operator preferences. Moreover, it should be further understood that monitoring position104of selector object106(e.g., by tracking component102) can be active, even while updates that would otherwise be performed by augmentation component114is not active. Hence, tracking component106can detect the presence and trajectory of an operator's finger when it is suitably proximal to UI display108, even though no augmentations to the output are provided. Accordingly, a predefined gesture by selector object106(e.g., moving one's finger in a particular pattern), can instantiate the updating aspects, while another gesture or pattern can be utilized to turn the UI updating off.

Turning now toFIG. 6, system600that can provide a pseudo-touch screen is depicted. Typically, system600can include tracking component102, augmentation component114, and activation component502as substantially described supra. However, in addition to what has been described, tracking component102can further utilize a distance parameter to effectuate pseudo-surface602at distance604from a surface of UI display108. For example, pseudo-surface602can represent a plane that is substantially parallel to and bounded to some degree in shape and size to that of UI display108, but some distance604away from UI display108. When selector object106breaks a plane associated with pseudo-surface602, such activity can simulate contact with UI display108. In other words, actual physical contact with UI display108can be simulated without touching or otherwise making contact with UI display108.

Appreciably, the features detailed supra can incorporate various gestures. For instance an abrupt downward motion by selector object106can indicate a keystroke or selection for a touch screen, even without actually touching the screen. Such can be beneficial in a number of ways. For example, the surface of a touch-screen as well as associated sensors can be protected from damage or wear. Additionally, the surface of a touch-screen need not be exposed to fingerprints or other soiling that commonly results from use. As another advantage, it is also possible to simulate a touch-screen display, even when the requisite hardware is not entirely available. Hence, a common display can be made to emulate a touch-screen display in some cases by monitoring the behavior of selector object106.

It is understood that one potentially important aspect of any given UI can be operator feedback, which can often indicate or reinforce the occurrence of certain I/O transactions. For example, in the case of a conventional keyboard, an operator receives both tactile and audio feedback when keys are pressed. While an operator might not be consciously aware of such feedback during use, operators tend to notice when that same feedback is lacking. Similarly, for touch-screen inputs, the operator receives tactile feedback when contact with the touch-screen is made, which verifies to the operator that the intended transaction (e.g., touching the screen at the intended location) has occurred. However, given that pseudo-surface602typically will not include a physical surface capable of imparting tactile feedback, other forms or types of feedback can be provided instead. In accordance therewith, tracking component102can facilitate feedback when selector object106breaks the plane associated with pseudo-surface602by way of a signal606. For instance, when the plane is broken or a command gesture is detected, feedback signal606can be transmitted to a suitable I/O component of a UI to provide, e.g., an auditory “click” to denote a key-press, or some other suitable feedback. As another example, visual feedback can be provided as well, such as a visual “click,” a flash, highlighting features and so forth.

In addition, system600can also include intelligence component608that can provide for or aid in various inferences or determinations. It is to be appreciated that intelligence component608can be operatively coupled to all or some of the aforementioned components, e.g.102,114, and502. Additionally or alternatively, all or portions of intelligence component608can be included in one or more components described herein. Moreover, intelligence component608will typically have access to all or portions of data sets described herein, such as access to data store118, and can furthermore utilize previously determined or inferred data.

For example, intelligence component608can aid tracking component102by intelligently determining or inferring distance602. As an example, machine learning techniques can be employed to analyze aspects of position104to establish a normal or comfortable hover distance for a particular operator during I/O transactions. Based upon this operator-specific hover distance, distance604can be set, generally slightly less than the hover distance to register “clicks” when the pseudo-surface plane is broken. Likewise, intelligence component608can aid augmentation component114in intelligently determining or inferring what type of update to be employed. For instance, suppose a virtual keyboard application is instantiated. Initially, the update can relate to highlighting the keys based upon position104in order to provide a visual aid in key selection. However, if a number of errors are made or that the size of the keys are below a certain threshold, then augmentation component114can employ or switch to the virtual magnifying glass. Additionally, the activation or termination of the updates to UI display108described herein in connection with activation component502can be facilitated or assisted by intelligence component608.

Accordingly, in order to provide for or aid in the numerous inferences described herein, intelligence component608can examine the entirety or a subset of the data available and can provide for reasoning about or infer states of the system, environment, and/or user from a set of observations as captured via events and/or data. Inference can be employed to identify a specific context or action, or can generate a probability distribution over states, for example. The inference can be probabilistic—that is, the computation of a probability distribution over states of interest based on a consideration of data and events. Inference can also refer to techniques employed for composing higher-level events from a set of events and/or data.

Such inference can result in the construction of new events or actions from a set of observed events and/or stored event data, whether or not the events are correlated in close temporal proximity, and whether the events and data come from one or several event and data sources. Various classification (explicitly and/or implicitly trained) schemes and/or systems (e.g. support vector machines, neural networks, expert systems, Bayesian belief networks, fuzzy logic, data fusion engines . . . ) can be employed in connection with performing automatic and/or inferred action in connection with the claimed subject matter.

Turning now toFIG. 7, exemplary method700for enhancing or simplifying tactile-related I/O for a UI with a limited form factor is illustrated. Generally, at reference numeral702, a position of a selector object hovering over a UI display can be tracked. The position can be defined as a salient portion of the selector object and/or the nearest portion of the selector object to the UI display. In addition, the position can be sampled over time in order to determine motion or a trajectory of the selector object. Hence, gestures or other motions can be identified. It should be understood that the selector object can be an appendage of an operator interacting with the UI display, such as a finger or thumb, and can also be a stylus or pointer.

Next to be described, at reference numeral704, the position can be associated with a coordinate of the UI display. Typically, the coordinate will represent a point or pixel on the UI display that is substantially below the selector object. In other words, the coordinate can be substantially along a line adjoining a surface of the UI display to the selector object, wherein the line is perpendicular to the surface of the UI display. At reference numeral706, an augmented output for the UI display can be provided in an area of effect that is substantially centered at the coordinate. Thus, the UI display can be modified or updated locally based upon the position of an operator's finger (e.g. selector object) hovering over the UI display.

With reference nowFIG. 8, exemplary method800for implementing a virtual magnifying glass is provided. In accordance therewith, at reference numeral802, a virtual magnifying glass that increases the magnification scale of a magnified area of the UI display can be implemented for the augmented output detailed at reference numeral706. Thus, the magnified area around the coordinate can be expanded to fit the area of effect in order to effectuate the magnification.

At reference numeral804, a size of the area of effect can be adjusted based upon a hover distance representing a distance between the surface and the selector object. Thus, by modifying the distance between the selector object and the UI display, the level of magnification as well as the size of the magnified area can be adjusted. It should be appreciated that the virtual magnifying glass can be effectuated according to a variety of distinct schemes. For example, at reference numeral806, elements of the UI display that are included within the area of effect but not included within the magnified area can be occluded. In other words, the magnified area occludes nearby features of the UI display to allow the magnified area to be displayed at a greater magnification scale.

At reference numeral808, these nearby features can avoid total occlusion. For instance, elements of the UI display that are included within the area of effect but not included within the magnified area can be displayed in a semi-transparent manner. Thus, rather than total occlusion for neighboring elements, these elements can be visible by adjusting the transparency. As a third example, at reference numeral810, a crowding effect can be utilized for displaying elements of the UI display that are included within a second, larger area of effect but not included within the magnified area. Accordingly, these elements can be distorted to a degree in either size or shape to allow for the updated magnification scale for one portion of the UI display, while still depicting all elements without strict occlusion.

Turning now toFIG. 9, exemplary method900for providing additional features associated with enhancing or simplifying I/O for a limited form factor UI is depicted. At reference numeral902, a change can be affected in at least one of a color, a contrast, a brightness, or a RGB attribute of one or more pixels included in the area of effect. In particular, updates to the UI display are not necessarily limited to adjusting the magnification scale of a portion of the display, but other updates can be facilitated, such as highlighting a particular pixel of group of pixels for instance.

At reference numeral904, an activation message can be employed for initiating or terminating activity associated with providing the augmented output. For example, as described at reference numeral706, an augmented output for the UI display can be facilitated in a particular area of effect. However, when these augmented outputs occur can be selectively determined, essentially allowing the augmented output to be switched on or off. For instance, the virtual magnifying glass can be activated when a keyboard application is instantiated, and terminated when the keyboard application is closed.

At reference numeral906, the activation message can be generated based upon a state of, or application instantiated by, a device associated with the UI display. In an aspect, the activation message can also be generated based upon a number of, a graphical complexity of, or a magnification scale for, graphical elements included in the UI display. Likewise, the activation message can be generated based upon a number of correction-based or undo-based inputs. The activation message can also be generated based upon preferences or settings associated with the UI display, or, in some cases, based upon a predefined gesture executed by the selector object.

In addition, at reference numeral908, a pseudo-surface can be created at a specified distance from the surface. The pseudo-surface can be employed for simulating a touch-sensitive UI display in a non-contact manner. For example, a touch-screen can be utilized in a contactless manner to reduce wear, maintenance, and/or fingerprints or other soiling to the touch-screen. Moreover, it is also possible to simulate a touch-screen in this manner even though the underlying UI display does not include touch or tactile-based components. At reference numeral910, feedback such as auditory feedback can be provided for signaling a tactile (e.g., touch) or tactile-based input (e.g., including gestures) in connection with the pseudo-surface.

Referring now toFIG. 10, there is illustrated a block diagram of an exemplary computer system operable to execute the disclosed architecture. In order to provide additional context for various aspects of the claimed subject matter,FIG. 10and the following discussion are intended to provide a brief, general description of a suitable computing environment1000in which the various aspects of the claimed subject matter can be implemented. Additionally, while the claimed subject matter described above may be suitable for application in the general context of computer-executable instructions that may run on one or more computers, those skilled in the art will recognize that the claimed subject matter also can be implemented in combination with other program modules and/or as a combination of hardware and software.

Continuing to referenceFIG. 10, the exemplary environment1000for implementing various aspects of the claimed subject matter includes a computer1002, the computer1002including a processing unit1004, a system memory1006and a system bus1008. The system bus1008couples to system components including, but not limited to, the system memory1006to the processing unit1004. The processing unit1004can be any of various commercially available processors. Dual microprocessors and other multi-processor architectures may also be employed as the processing unit1004.

A monitor1044or other type of display device is also connected to the system bus1008via an interface, such as a video adapter1046. In addition to the monitor1044, a computer typically includes other peripheral output devices (not shown), such as speakers, printers, etc.

When used in a LAN networking environment, the computer1002is connected to the local network1052through a wired and/or wireless communication network interface or adapter1056. The adapter1056may facilitate wired or wireless communication to the LAN1052, which may also include a wireless access point disposed thereon for communicating with the wireless adapter1056.

When used in a WAN networking environment, the computer1002can include a modem1058, or is connected to a communications server on the WAN1054, or has other means for establishing communications over the WAN1054, such as by way of the Internet. The modem1058, which can be internal or external and a wired or wireless device, is connected to the system bus1008via the serial port interface1042. In a networked environment, program modules depicted relative to the computer1002, or portions thereof, can be stored in the remote memory/storage device1050. It will be appreciated that the network connections shown are exemplary and other means of establishing a communications link between the computers can be used.

Referring now toFIG. 11, there is illustrated a schematic block diagram of an exemplary computer compilation system operable to execute the disclosed architecture. The system1100includes one or more client(s)1102. The client(s)1102can be hardware and/or software (e.g., threads, processes, computing devices). The client(s)1102can house cookie(s) and/or associated contextual information by employing the claimed subject matter, for example.

The system1100also includes one or more server(s)1104. The server(s)1104can also be hardware and/or software (e.g., threads, processes, computing devices). The servers1104can house threads to perform transformations by employing the claimed subject matter, for example. One possible communication between a client1102and a server1104can be in the form of a data packet adapted to be transmitted between two or more computer processes. The data packet may include a cookie and/or associated contextual information, for example. The system1100includes a communication framework1106(e.g., a global communication network such as the Internet) that can be employed to facilitate communications between the client(s)1102and the server(s)1104.

Communications can be facilitated via a wired (including optical fiber) and/or wireless technology. The client(s)1102are operatively connected to one or more client data store(s)1108that can be employed to store information local to the client(s)1102(e.g., cookie(s) and/or associated contextual information). Similarly, the server(s)1104are operatively connected to one or more server data store(s)1110that can be employed to store information local to the servers1104.

What has been described above includes examples of the various embodiments. It is, of course, not possible to describe every conceivable combination of components or methodologies for purposes of describing the embodiments, but one of ordinary skill in the art may recognize that many further combinations and permutations are possible. Accordingly, the detailed description is intended to embrace all such alterations, modifications, and variations that fall within the spirit and scope of the appended claims.