Abstract:
Methods, systems, and computer program products are described comprising a device configured to: present a first window of the first application in a first application region of a presentation space of the display; detect first user input in connection with the first window of the first application; in response to the detection of the first user input in connection with the first window of the first application, present a representation of a second window of the second application in a menu, in a first particular region of the presentation space of the display, for displaying the second window of the second application, in a second application region in the presentation space of the display, the first particular region: located in a first location adjacent to a second location of the first application region, operable for being at least one of re-sized or moved in response to the first application region being at least one of re-sized or moved, and operable for being hidden in response to the first application region being maximized, and re-presented in response to the first application region being returned to a non-maximized state; detect second user input in connection with the representation of the second window of the second application in the menu; and in response to the detection of the second user input in connection with the representation of the second window of the second application in the menu, present the second window of the second application.

Description:
RELATED APPLICATIONS 
     The present application is continuation of, and claims priority to U.S. patent application Ser. No. 14/173,806, titled “METHODS, SYSTEMS, AND COMPUTER PROGRAM PRODUCTS FOR NAVIGATING BETWEEN VISUAL COMPONENTS,” filed Feb. 5, 2014; which, in turn, is a continuation-in-part of, and claims priority to U.S. patent application Ser. No. 12/868,767, titled “METHODS, SYSTEMS, AND COMPUTER PROGRAM PRODUCTS FOR NAVIGATING BETWEEN VISUAL COMPONENTS,” filed on Aug. 26, 2010, now issued as U.S. Pat. No. 8,661,361; U.S. patent application Ser. No. 12/956,008, titled “METHODS, SYSTEMS, AND COMPUTER PROGRAM PRODUCTS FOR BINDING ATTRIBUTES BETWEEN VISUAL COMPONENTS,” filed on Nov. 30, 2010, now issued as U.S. Pat. No. 8,780,130; and U.S. patent application Ser. No. 12/955,993, titled “METHODS, SYSTEMS, AND COMPUTER PROGRAM PRODUCTS FOR AUTOMATICALLY SCROLLING ITEMS IN A SELECTION CONTROL,” filed on Nov. 30, 2010, all of which are incorporated herein by reference in their entirety for all purposes. 
    
    
     BACKGROUND 
     Cluttered desktops on desktop, notebook, and handheld devices are common. Navigating among visual components of various applications requires locating a desired visual component in the clutter and/or interoperating with a standard user interface element such as a task bar and/or application menu of a desktop that remains in a single location and requires the same types of inputs and user movements for each application and/or visual component to be located. This may require a user to repeat a similar and/or same set of movements over and over. Further, a task bar or other standard application navigation user interface may be located in a location that is convenient for some applications but inconvenient for others for a user. This creates a lot of input overhead in cases where switching between applications is frequent. Input to bring an application into focus is essentially non-productive input, as it is not related to any of the tasks performed by the applications a user is interacting with. 
     Accordingly, there exists a need for methods, systems, and computer program products for navigating between visual components. 
     SUMMARY 
     The following presents a simplified summary of the disclosure in order to provide a basic understanding to the reader. This summary is not an extensive overview of the disclosure and it does not identify key/critical elements of the invention or delineate the scope of the invention. Its sole purpose is to present some concepts disclosed herein in a simplified form as a prelude to the more detailed description that is presented later. 
     Methods and systems are described for navigating between visual components. A first visual component, of a first application in a plurality of applications, is detected in a first application region of a presentation space of a display device. A first navigation control is presented, in a first navigation region determined based on the first application region, for navigating to a second visual component, of a second application in the plurality, in a second application region in the presentation space. A user input corresponding to the first navigation control is detected. In response to the detected user input, navigation information is sent to navigate to the second visual component. 
    
    
     
       BRIEF DESCRIPTION OF THE DRAWINGS 
       Objects and advantages of the present invention will become apparent to those skilled in the art upon reading this description in conjunction with the accompanying drawings, in which like reference numerals have been used to designate like or analogous elements, and in which: 
         FIG. 1  is a block diagram illustrating an exemplary hardware device included in and/or otherwise providing an execution environment in which the subject matter may be implemented; 
         FIG. 2  is a flow diagram illustrating a method for navigating between visual components according to an aspect of the subject matter described herein; 
         FIG. 3  is a block diagram illustrating an arrangement of components for navigating between visual components according to another aspect of the subject matter described herein; 
         FIG. 4 a    is a block diagram illustrating an arrangement of components for navigating between visual components according to another aspect of the subject matter described herein; 
         FIG. 4 b    is a block diagram illustrating an arrangement of components for navigating between visual components according to another aspect of the subject matter described herein; 
         FIG. 4 c    is a block diagram illustrating an arrangement of components for navigating between visual components according to another aspect of the subject matter described herein; 
         FIG. 4 d    is a block diagram illustrating an arrangement of components for navigating between visual components according to another aspect of the subject matter described herein; 
         FIG. 5  is a network diagram illustrating an exemplary system for navigating between visual components according to another aspect of the subject matter described herein; 
         FIG. 6 a    is a diagram illustrating a user interface presented via a display according to another aspect of the subject matter described herein; 
         FIG. 6 b    is a diagram illustrating a user interface presented via a display according to another aspect of the subject matter described herein; 
         FIG. 6 c    is a diagram illustrating a user interface presented via a display according to another aspect of the subject matter described herein; 
         FIG. 6 d    is a diagram illustrating a user interface presented via a display according to another aspect of the subject matter described herein; and 
         FIG. 6 e    is a diagram illustrating a user interface presented via a display according to another aspect of the subject matter described herein. 
     
    
    
     DETAILED DESCRIPTION 
     One or more aspects of the disclosure are described with reference to the drawings, wherein like reference numerals are generally utilized to refer to like elements throughout, and wherein the various structures are not necessarily drawn to scale. In the following description, for purposes of explanation, numerous specific details are set forth in order to provide a thorough understanding of one or more aspects of the disclosure. It may be evident, however, to one skilled in the art that one or more aspects of the disclosure may be practiced with a lesser degree of these specific details. In other instances, well-known structures and devices are shown in block diagram form in order to facilitate describing one or more aspects of the disclosure. 
     An exemplary device included in an execution environment that may be configured according to the subject matter is illustrated in  FIG. 1 . An execution environment includes an arrangement of hardware and, optionally, software that may be further configured to include an arrangement of components for performing a method of the subject matter described herein. An execution environment includes and/or is otherwise provided by one or more devices. An execution environment may include a virtual execution environment including software components operating in a host execution environment. Exemplary devices included in or otherwise providing suitable execution environments for configuring according to the subject matter include personal computers, notebook computers, tablet computers, servers, handheld and other mobile devices, multiprocessor devices, distributed devices, consumer electronic devices, routers, communication servers, and/or other network-enabled devices. Those skilled in the art will understand that the components illustrated in  FIG. 1  are exemplary and may vary by particular execution environment. 
       FIG. 1  illustrates hardware device  100  included in execution environment  102 .  FIG. 1  illustrates that execution environment  102  includes instruction-processing unit (IPU)  104 , such as one or more microprocessors; physical processor memory  106  including storage locations identified by addresses in a physical memory address space of IPU  104 ; persistent secondary storage  108 , such as one or more hard drives and/or flash storage media; input device adapter  110 , such as a key or keypad hardware, a keyboard adapter, and/or a mouse adapter; output device adapter  112 , such as a display or audio adapter for presenting information to a user; a network interface component, illustrated by network interface adapter  114 , for communicating via a network such as a LAN and/or WAN; and a communication mechanism that couples elements  104 - 114 , illustrated as bus  116 . Elements  104 - 114  may be operatively coupled by various means. Bus  116  may comprise any type of bus architecture, including a memory bus, a peripheral bus, a local bus, and/or a switching fabric. 
     IPU  104  is an instruction execution machine, apparatus, or device. Exemplary IPUs include one or more microprocessors, digital signal processors (DSPs), graphics processing units, application-specific integrated circuits (ASICs), and/or field programmable gate arrays (FPGAs). In the description of the subject matter herein, the terms “IPU” and “processor” are used interchangeably. IPU  104  may access machine code instructions and data via one or more memory address spaces in addition to the physical memory address space. A memory address space includes addresses identifying locations in a processor memory. The addresses in a memory address space are included in defining a processor memory. IPU  104  may have more than one processor memory. Thus, IPU  104  may have more than one memory address space. IPU  104  may access a location in a processor memory by processing an address identifying the location. The processed address may be in an operand of a machine code instruction and/or may be identified in a register or other portion of IPU  104 . 
       FIG. 1  illustrates virtual processor memory  118  spanning at least part of physical processor memory  106  and at least part of persistent secondary storage  108 . Virtual memory addresses in a memory address space may be mapped to physical memory addresses identifying locations in physical processor memory  106 . An address space for identifying locations in a virtual processor memory is referred to as a virtual memory address space; its addresses are referred to as virtual memory addresses; and its processor memory is known as a virtual processor memory or virtual memory. The term “processor memory” may refer to physical processor memory  106  and/or virtual processor memory  118  depending on the context in which the term is used. 
     Physical processor memory  106  may include various types of memory technologies. Exemplary memory technologies include static random access memory (SRAM) and/or dynamic RAM (DRAM) including variants such as dual data rate synchronous DRAM (DDR SDRAM), error correcting code synchronous DRAM (ECC SDRAM), and/or RAMBUS DRAM (RDRAM). Physical processor memory  106  may include volatile memory as illustrated in the previous sentence and/or may include nonvolatile memory such as nonvolatile flash RAM (NVRAM) and/or ROM. 
     Persistent secondary storage  108  may include one or more flash memory storage devices, one or more hard disk drives, one or more magnetic disk drives, and/or one or more optical disk drives. Persistent secondary storage may include removable media. The drives and their associated computer-readable storage media provide volatile and/or nonvolatile storage for computer-readable instructions, data structures, program components, and other data for execution environment  102 . 
     Execution environment  102  may include software components stored in persistent secondary storage  108 , in remote storage accessible via a network, and/or in a processor memory.  FIG. 1  illustrates execution environment  102  including operating system  120 , one or more applications  122 , and other program code and/or data components illustrated by other libraries and subsystems  124 . In an aspect, some or all software components may be stored in locations accessible to IPU  104  in a shared memory address space shared by the software components. The software components accessed via the shared memory address space are stored in a shared processor memory defined by the shared memory address space. In another aspect, a first software component may be stored in one or more locations accessed by IPU  104  in a first address space and a second software component may be stored in one or more locations accessed by IPU  104  in a second address space. The first software component is stored in a first processor memory defined by the first address space and the second software component is stored in a second processor memory defined by the second address space. 
     Software components typically include instructions executed by IPU  104  in a computing context referred to as a “process”. A process may include one or more “threads”. A “thread” includes a sequence of instructions executed by IPU  104  in a computing sub-context of a process. The terms “thread” and “process” may be used interchangeably herein when a process includes only one thread. 
     Execution environment  102  may receive user-provided information via one or more input devices illustrated by input device  128 . Input device  128  provides input information to other components in execution environment  102  via input device adapter  110 . Execution environment  102  may include an input device adapter for a keyboard, a touch screen, a microphone, a joystick, a television receiver, a video camera, a still camera, a document scanner, a fax, a phone, a modem, a network interface adapter, and/or a pointing device, to name a few exemplary input devices. 
     Input device  128  included in execution environment  102  may be included in device  100  as  FIG. 1  illustrates or may be external (not shown) to device  100 . Execution environment  102  may include one or more internal and/or external input devices. External input devices may be connected to device  100  via corresponding communication interfaces such as a serial port, a parallel port, and/or a universal serial bus (USB) port. Input device adapter  110  receives input and provides a representation to bus  116  to be received by IPU  104 , physical processor memory  106 , and/or other components included in execution environment  102 . 
     Output device  130 , in  FIG. 1 , exemplifies one or more output devices that may be included in and/or may be external to and operatively coupled to device  100 . For example, output device  130  is illustrated connected to bus  116  via output device adapter  112 . Output device  130  may be a display device. Exemplary display devices include liquid crystal displays (LCDs), light emitting diode (LED) displays, and projectors. Output device  130  presents output of execution environment  102  to one or more users. In some embodiments, an input device may also include an output device. Examples include a phone, a joystick, and/or a touch screen. In addition to various types of display devices, exemplary output devices include printers, speakers, tactile output devices such as motion-producing devices, and other output devices producing sensory information detectable by a user. 
     A device included in or otherwise providing an execution environment may operate in a networked environment communicating with one or more devices via one or more network interface components. The terms “communication interface component” and “network interface component” are used interchangeably.  FIG. 1  illustrates network interface adapter (NIA)  114  as a network interface component included in execution environment  102  to operatively couple device  100  to a network. A network interface component includes a network interface hardware (NIH) component and optionally a software component. 
     Exemplary network interface components include network interface controller components, network interface cards, network interface adapters, and line cards. A node may include one or more network interface components to interoperate with a wired network and/or a wireless network. Exemplary wireless networks include a BLUETOOTH network, a wireless 802.11 network, and/or a wireless telephony network (e.g., a cellular, PCS, CDMA, and/or GSM network). Exemplary network interface components for wired networks include Ethernet adapters, Token-ring adapters, FDDI adapters, asynchronous transfer mode (ATM) adapters, and modems of various types. Exemplary wired and/or wireless networks include various types of LANs, WANs, and/or personal area networks (PANs). Exemplary networks also include intranets and internets such as the Internet. 
     The terms “network node” and “node” in this document both refer to a device having a network interface component for operatively coupling the device to a network. The terms “device” and “node” as used herein further refer to one or more devices and nodes, respectively, providing and/or otherwise included in an execution environment unless clearly indicated otherwise. 
     The block diagram in  FIG. 3  illustrates an exemplary system for navigating between visual components according to the method illustrated in  FIG. 2 .  FIG. 3  illustrates a system, adapted for operation in an execution environment, such as execution environment  102  in  FIG. 1 , for performing the method illustrated in  FIG. 2 . The system illustrated includes a presentation space (PS) monitor component  302 , an application navigator component  304 , a navigation element handler component  306 , and a navigation director component  308 . The execution environment includes an instruction-processing unit, such as IPU  104 , for processing an instruction in at least one of the presentation space monitor component  302 , the application navigator component  304 , the navigation element handler component  306 , and the navigation director component  308 . Some or all of the exemplary components illustrated in  FIG. 3  may be adapted for performing the method illustrated in  FIG. 2  in a number of execution environments.  FIGS. 4 a - d    include block diagrams illustrating the components of  FIG. 3  and/or analogs of the components of  FIG. 3  adapted for operation in various execution environments  401  including and/or otherwise provided by one or more nodes. 
       FIG. 1  illustrates components of an exemplary device that may at least partially provide and/or otherwise be included in an execution environment. The components illustrated in  FIGS. 4 a - d    may be included in or otherwise combined with the components of  FIG. 1  to create a variety of arrangements of components according to the subject matter described herein. 
       FIG. 5  illustrates user node  502  as an exemplary device that in various aspects may be included in and/or otherwise adapted for providing any of execution environments  401  illustrated in  FIGS. 4 a - c   , each illustrating a different adaptation of the arrangement of components in  FIG. 3 .  FIG. 5  illustrates that user node  502  is operatively coupled to network  504  via a network interface component, such as NIA  114 . Alternatively or additionally, an adaptation of an execution environment  401  may include and/or may otherwise be provided by a device that is not operatively coupled to a network. Application provider node  506  may be included in and/or otherwise adapted for providing execution environment  401   d  illustrated in  FIG. 4 d   . As illustrated in  FIG. 5 , application provider node  506  is operatively coupled to network  504  via a network interface component included in execution environment  401   d.    
       FIG. 4 a    illustrates execution environment  401   a  hosting application  403   a  including an adaptation of the arrangement of components in  FIG. 3 .  FIG. 4 b    illustrates execution environment  401   b  hosting browser  403   b  including an adaptation of the arrangement of components in  FIG. 3  that may operate at least partially in a network application agent  405   b  received from a remote application provider, such as network application  403   d  in  FIG. 4 d   . Browser  403   b  and execution environment  401   b  may provide at least part of an execution environment for network application agent  405   b  that may be received via a network from a network application operating in a remote execution environment.  FIG. 4 c    illustrates an arrangement of the components in  FIG. 3  adapted to operate in GUI subsystem  437   c  of execution environment  401   c . The arrangement in  FIG. 4 c    may mediate communication between applications in execution environment  401   c  and one or more output devices, such as output device  130  in  FIG. 1 . 
       FIG. 4 d    illustrates execution environment  401   d  configured to host one or more network applications, such as a Web service, illustrated by network application  403   d .  FIG. 4 d    also illustrates network application platform  409   d  that may provide services to one or more network applications. Network application  403   d  includes yet another adaptation of the arrangement of components in  FIG. 3 . 
     The various adaptations of the arrangement in  FIG. 3  are not exhaustive. For example, those skilled in the art will see based on the description herein that arrangements of components for performing the method illustrated in  FIG. 2  may be at least partially included in an application and at least partially external to the application. Further, arrangements for performing the method illustrated in  FIG. 2  may be distributed across more than one node and/or execution environment. For example, such an arrangement may operate at least partially in browser  403   b  in  FIG. 4 b    and at least partially in execution environment  401   d  in and/or external to network application  403   d  in  FIG. 4   d.    
       FIGS. 4 a - d    illustrate adaptations of network stacks  411  configured for sending and receiving messages over a network, such as network  504 , via a network interface component. Network application platform  409   d  in  FIG. 4 d    provides services to one or more network applications. In various aspects, network application platform  409   d  may include and/or interoperate with a web server.  FIG. 4 d    also illustrates network application platform  409   d  configured for interoperating with network stack  411   d  directly and/or indirectly. 
     Network stacks  411  may support the same protocol suite, such as TCP/IP, or may communicate via a network gateway or other protocol translation device and/or service. For example, browser  403   b  in  FIG. 4 b    and network application platform  409   d  in  FIG. 4 d    may interoperate via their respective network stacks: network stack  411   b  and network stack  411   d.    
       FIGS. 4 a - d    illustrate applications  403 , respectively, which may communicate via one or more application layer protocols.  FIGS. 4 a - d    respectively illustrate application protocol components  413  for communicating via one or more application layer protocols. Exemplary application protocols include hypertext transfer protocol (HTTP) and instant messaging and presence (XMPP-IM) protocol. Matching protocols enabling applications  403  to communicate via network  504  in  FIG. 5  are not required, if communication is via a protocol gateway or other translator. 
     In  FIG. 4 b   , browser  403   b  may receive some or all of network application agent  405   b  in one more messages sent from a network application, such as network application  403   d  via network application platform  409   d , a network stack  411 , a network interface component, and optionally an application protocol component  413 . In  FIG. 4 b   , browser  403   b  includes content manager component  415   b . Content manager component  415   b  may interoperate with one or more of application protocol components  413   b  and/or network stack  411   b  to receive the message or messages including some or all of network application agent  405   b.    
     Network application agent  405   b  may include a web page for presenting a user interface for network application  403   d . The web page may include and/or reference data represented in one or more formats including hypertext markup language (HTML) and/or other markup language, ECMAScript and/or other scripting language, byte code, image data, audio data, and/or machine code. 
     In an example, in response to a request received from browser  403   b  in  FIG. 4 b    operating in user node  502  in  FIG. 5 , controller component  417   d , in  FIG. 4 d   , operating in application provider node  506  may invoke model subsystem  419   d  to perform request-specific processing. Model subsystem  419   d  may include any number of request handlers (not shown) for dynamically generating data and/or retrieving data from model database  421   d  based on the request. Controller component  417   d  may further invoke template engine component  423   d  to identify one or more templates and/or static data elements for generating a user interface for representing a response to the received request.  FIG. 4 d    illustrates template database  425   d  including exemplary template  427   d .  FIG. 4 d    illustrates template engine  423   d  as a component in view subsystem  429   d  configured to return responses to processed requests in a presentation format suitable for a client, such as browser  403   b . View subsystem  429   d  may provide the presentation data to controller component  417   d  to send to browser  403   b  in response to the request received from browser  403   b . Some or all of network application agent  405   b  may be sent to browser  403   b  via network application platform  409   d  as described above. 
     While the example above describes sending some or all of network application agent  405   b  in response to a request, network application  403   d  additionally or alternatively may send some or all of a network application agent to browser  403   b  via one or more asynchronous messages. An asynchronous message may be sent in response to a change detected by network application  403   d . Publish-subscribe protocols, such as the presence protocol specified by XMPP-IM, are exemplary protocols for sending messages asynchronously. 
     The one or more messages including information representing some or all of network application agent  405   b  in  FIG. 4 b    may be received by content manager component  415   b  via one or more of application protocol component(s)  413   b  and network stack  411   b  as described above. In  FIG. 4 b   , browser  403   b  includes one or more content handler components  431   b  to process received data according to its data type, typically identified by a MIME-type identifier. Exemplary content handler components  431   b  include a text/html content handler component for processing HTML documents; an application/xmpp-xml content handler component for processing XMPP streams including presence tuples, instant messages, and publish-subscribe data as defined by various XMPP specifications; one or more video content handler components for processing video streams of various types; and still image data content handler components for processing various images types. Content handler components  431   b  process received data and may provide a representation of the processed data to one or more user interface (UI) element handler components  433   b.    
     UI element handler components  433  are illustrated in presentation controller components  435  in  FIG. 4 a   ,  FIG. 4 b   , and  FIG. 4 c   . A presentation controller component  435  may manage visual, audio, and/or other types of output of its including application  403  as well as receive and route detected user and other inputs to components and extensions of its including application  403 . With respect to  FIG. 4 b   , a UI element handler component  433   b  in various aspects may be adapted to operate at least partially in a content handler component  431   b  such as a text/html content handler component and/or a script content handler component. Additionally or alternatively, a UI element handler component  433  in an execution environments  401  may operate in and/or as an extension of its including application  403 , such as a plug-in providing a virtual machine for script and/or byte code, and/or may operate external to an interoperating application  403 . 
       FIGS. 6 a - e    illustrate respective display presentation spaces  602  of a display in and/or operatively coupled to a device.  FIGS. 6 a - e    illustrate first app  604 - 1  visual components and second app  604 - 2  visual components in respective presentation spaces  602 . The various app  604  visual components illustrated in  FIGS. 6 a - e    are described as user interfaces of various applications  403  and other components illustrated in  FIGS. 4 a - d    as required in describing the subject matter herein. An application  604  visual component may be provided as a user interface of multiple applications interoperating. For example, an application  604  visual component and/or a visual component included in an application  604  visual component may be presented via interoperation of browser  403   b , network application agent  405   b , and network application  403   d  illustrated in  FIG. 4 b    and  FIG. 4 d   . Browser  403   b  may operate in user node  502  and network application  403   d  may operate in application provider node  506 . Network application agent  405   b  may be provided to user node  502  by application provider node  506  via network  504 , as described above. 
     Various UI elements of applications  403  described above may be presented by one or more UI element handler components  433  in  FIGS. 4 a - c    and/or by one or more template engines  423   d  in  FIG. 4 d   . In an aspect, illustrated in  FIGS. 4 a - c   , UI element handler component(s)  433  of one or more applications  403  is/are configured to send representation information representing a visual interface element, such as an operation bar  606  in  FIG. 6 a    and in  FIG. 6 d   , to a GUI subsystem  437 . A GUI subsystem  437  may instruct a graphics subsystem  439  to draw the visual interface element in a region of a respective display presentation space  602 , based on representation information received from a corresponding UI element handler component  433 . 
     Input may be received corresponding to a UI element via an input driver  441  illustrated in  FIGS. 4 a - c   , in various adaptations. For example, a user may move a mouse to move a pointer presented in a display presentation space  602  over an operation user interface element presented in an operation bar  606 . A user may provide an input detected by the mouse. The detected input may be received by a GUI subsystem  437  via an input driver  441  as an operation or command indicator based on the association of the shared location of the pointer and the operation user interface element in display presentation space  602 . 
     The components of a user interface are generically referred to herein as user interface elements. More specifically, visual components of a user interface are referred to herein as visual interface elements. A visual interface element may be a visual component of a graphical user interface (GUI). Exemplary visual interface elements include windows, textboxes, sliders, list boxes, drop-down lists, spinners, various types of menus, toolbars, ribbons, combo boxes, tree views, grid views, navigation tabs, scrollbars, labels, tooltips, text in various fonts, balloons, dialog boxes, and various types of button controls including check boxes and radio buttons. An application interface may include one or more of the elements listed. Those skilled in the art will understand that this list is not exhaustive. The terms “visual representation”, “visual component”, and “visual interface element” are used interchangeably in this document. Other types of user interface elements include audio output components referred to as audio interface elements, tactile output components referred to as tactile interface elements, and the like. 
     A “user interface (UI) element handler” component, as the term is used in this document, includes a component configured to send information representing a program entity for presenting a user-detectable representation of the program entity by an output device, such as a display. A “program entity” is an object included in and/or otherwise processed by an application or executable program component. The user-detectable representation is presented based on the sent information. The sent information is referred to herein as “presentation information”. Presentation information may include data in one or more formats. Exemplary formats include image formats such as JPEG, video formats such as MP4, markup language data such as HTML and other XML-based markup, and/or instructions such as those defined by various script languages, byte code, and/or machine code. For example, a web page received by a browser from a remote application provider may include HTML, ECMAScript, and/or byte code for presenting one or more user interface elements included in a user interface of the remote application. Components configured to send information representing one or more program entities for presenting particular types of output by particular types of output devices include visual interface element handler components, audio interface element handler components, tactile interface element handler components, and the like. 
     A representation of a program entity may be stored and/or otherwise maintained in a presentation space. As used in this document, the term “presentation space” refers to a storage region allocated and/or otherwise provided for storing presentation information, which may include audio, visual, tactile, and/or other sensory data for presentation by and/or on an output device. For example, a buffer for storing an image and/or text string may be a presentation space. A presentation space may be physically and/or logically contiguous or non-contiguous. A presentation space may have a virtual as well as a physical representation. A presentation space may include a storage location in a processor memory, secondary storage, a memory of an output adapter device, and/or a storage medium of an output device. A screen of a display, for example, is a presentation space. 
     As used herein, the term “program” or “executable” refer to any data representation that may be translated into a set of machine code instructions and optionally associated program data. Thus, a program component or executable component may include an application, a shared or non-shared library, and a system command. Program representations other than machine code include object code, byte code, and source code. Object code includes a set of instructions and/or data elements that either are prepared for linking prior to loading or are loaded into an execution environment. When in an execution environment, object code may include references resolved by a linker and/or may include one or more unresolved references. The context in which this term is used will make clear that state of the object code when it is relevant. This definition can include machine code and virtual machine code, such as Java™ byte code. 
     As used herein, an “addressable entity” is a portion of a program, specifiable in programming language in source code. An addressable entity is addressable in a program component translated from the source code in a compatible execution environment. Examples of addressable entities include variables, constants, functions, subroutines, procedures, modules, methods, classes, objects, code blocks, and labeled instructions. A code block includes one or more instructions in a given scope specified in a programming language. An addressable entity may include a value. In some places in this document “addressable entity” refers to a value of an addressable entity. In these cases, the context will clearly indicate that the value is being referenced. 
     Addressable entities may be written in and/or translated to a number of different programming languages and/or representation languages, respectively. An addressable entity may be specified in and/or translated into source code, object code, machine code, byte code, and/or any intermediate languages for processing by an interpreter, compiler, linker, loader, or analogous tool. 
     Returning to  FIGS. 6 a - e   , first app  604 - 1  visual components and second app  604 - 2  visual components are collectively and generically are referred to as app(s)  604  visual components. App  604  visual components in  FIGS. 6 a - e    illustrate a number of visual user interface elements commonly found in application user interfaces. Menu bars  608  are illustrated in first app  604 - 1  visual components in  FIGS. 6 a - e   . Menu bars  608  are illustrated including menu controls for receiving user input to identify commands to perform. Location bars  609  are illustrated including universal resource locators (URLs) identifying sources of presented data. App  604  visual components also illustrate user interface elements providing respective application presentation spaces  610  for presenting content including other visual components illustrated by resource user interface elements  612 - 1   d  through  612 - nd  in  FIG. 6 d    representing respective resources. 
     With reference to  FIG. 2 , block  202  illustrates that the method includes detecting, in a first application region of a presentation space of a display device, a first visual component of a first operating application in a plurality of operating applications. Accordingly, a system for navigating between visual components includes means for detecting, in a first application region of a presentation space of a display device, a first visual component of a first operating application in a plurality of operating applications. For example, as illustrated in  FIG. 3 , presentation space monitor component  302  is configured for detecting, in a first application region of a presentation space of a display device, a first visual component of a first operating application in a plurality of operating applications.  FIGS. 4 a - d    illustrate presentation space monitor components  402  as adaptations and/or analogs of presentation space monitor component  302  in  FIG. 3 . One or more presentation space monitor components  402  operate in execution environments  401 . 
     In  FIG. 4 a   , PS monitor component  402   a  is illustrated as a component of application  403   a . In  FIG. 4 b   , PS monitor component  402   b  is illustrated as a component of network application agent  405   b . In  FIG. 4 c   , PS monitor component  402   c  is illustrated operating external to one or more applications  403   c . Execution environment  401   c  includes PS monitor component  402   c  in GUI subsystem  437   c . In  FIG. 4 d   , PS monitor component  402   d  is illustrated operating in network application  403   d  remote from a display device for presenting and/or updating a visual component. For example, PS monitor component  402  may operate in application provider node  506  while a visual component is presented via a display device of user node  502  based on presentation information sent via network  504  from application provider node  506 . 
     A visual component may be detected by one or more of receiving a request to present the visual component, receiving a request for a resource for presenting the visual component, detecting a change in at least a portion of a presentation space, intercepting a communication identifying the visual component, receiving an input corresponding to the visual component, receiving a notification identifying the visual component, and sending presentation information to present at least a portion of the visual component. 
     In  FIG. 4 a   , PS monitor  402   a  may receive a request to present a visual component, such as app  604  visual component in any of  FIGS. 6 a - e   . PS monitor component  402   a  may be configured to intercept and/or otherwise mediate access to one or more UI element handler components  433   a  for presenting the app  604  visual component and/or other visual components of application  403   a . PS monitor component  402   a  may send presentation information and/or information for generating presentation information to a UI element handler component  433   a  for presenting some or all of a visual component via a display device. 
     In  FIG. 4 b   , PS monitor component  402   b  may receive, intercept, and/or otherwise mediate processing of a request for a resource for presenting a visual component such as a browser tab, a browser window of browser  403   b , and/or content received from network application  403   d  in  FIG. 4 d    operating in application provider node  506 . Content from network application  403   d  may include network application agent  405   b  and/or content retrieved by network application agent  405   b . PS monitor component  402   b  may be a component of browser  403   b . Alternatively or additionally, a PS monitor component  402  may operate as a component of network application agent  405   b  and/or a component of network application  403   d  as illustrated by PS monitor component  402   d.    
     PS monitor component  402   c  in  FIG. 4 c    may track and/or otherwise monitor at least some changes to a presentation space accessible to GUI subsystem  437   c .  FIGS. 6 a - e    illustrate various display presentation spaces  602  and application presentation spaces  610  as exemplary presentation spaces. A change to a presentation space may include presenting a visual component via the presentation space, updating a visual component in the presentation space, and/or removing a visual component from the presentation space. A change may be in response to a user input. PS monitor component  402   c  may receive and/or otherwise monitor user input received for a visual component. In an aspect, PS monitor component  402   c  may receive change information by accessing a log maintained by GUI subsystem  437   c  and/or graphics subsystem  439   c . The log may be accessed via receiving notifications of log entries. 
     As described above, a visual component may be detected by an application presenting some or all of the visual component, by a remote node, and/or by a component operating external to an application that presents some or all of the visual component. 
     In detecting and/or otherwise monitoring a visual component, a PS monitor component  402  may identify a region in a presentation space that includes the visual component. The region is referred to herein as an “application region”. As illustrated in  FIGS. 6 a - e    a visual component may be included in a plurality of visual components in a presentation space. The visual components may be included in user interfaces of a plurality of operating applications. 
     Returning to  FIG. 2 , block  204  illustrates that the method further includes presenting a first navigation control, in a first navigation region determined based on the first application region, for navigating to a second visual component, of a second application in the plurality, in a second application region in the presentation space. Accordingly, a system for navigating between visual components includes means for presenting a first navigation control, in a first navigation region determined based on the first application region, for navigating to a second visual component, of a second application in the plurality, in a second application region in the presentation space. For example, as illustrated in  FIG. 3 , application navigator component  304  is configured for presenting a first navigation control, in a first navigation region determined based on the first application region, for navigating to a second visual component, of a second application in the plurality, in a second application region in the presentation space.  FIGS. 4 a - d    illustrate application navigator components  404  as adaptations and/or analogs of application navigator component  304  in  FIG. 3 . One or more application navigator components  404  operate in execution environments  401 . 
     A navigation control is a user interface element for navigating between and/or among user interface elements of respective operating applications. The user interface elements may be visual components. A navigation control may include and/or have an application control representing a particular application. An application control may include and/or have a visual component control representing a particular visual component in the application represented by the application control. An input received corresponding to a particular application control may identify a user instruction to navigate to a visual component of the particular application. A user input corresponding to a particular visual component control may identify a user instruction to navigate to a particular visual component in a particular application corresponding to an application control that includes and/or otherwise has the visual component control. 
       FIGS. 6 a - e    illustrate various navigation control  614  visual components. Second navigation control  614 - 2   a  illustrates a user interface element that is a parent of second app  604 - 2   a  visual component. Navigation control  614 - 2   a  includes and illustrates first application control  616 - 1   a , second application control  616 - 2   a , and third application control  616 - 3   a . First app  604 - 1   a  visual component may be included in a user interface for a first application, second app  604 - 2   a  visual component may be included in a user interface for a second application, and a third app visual component (not shown) may be included in a user interface for a third application. 
     A navigation control may be automatically presented in response to presenting of a corresponding visual component in a user interface of an operating application. For example, as described, second navigation control  614 - 2   a  includes second app  604 - 2   a  visual component of a second application. In  FIG. 4 c   , GUI subsystem  437   c  may receive presentation information for presenting second app  604 - 2   a  visual component. GUI subsystem  437   c  may invoke application navigator component  404   c . Application navigator component  404   c  may provide a presentation space for presenting second app  604 - 2   a  visual component in second navigation control  614 - 2   a  by instructing navigation element handler component  406   c  to present second navigation control  614 - 2   a  in display presentation space  602   a.    
     In another aspect, a navigation control may be presented in response to a navigation-activate input received from a user via an input device. For example, first app  604 - 1   b  visual component in  FIG. 6 b    may be presented by browser  403   b  in  FIG. 4 b   . First navigation control  614 - 1   b  may be non-existent and/or hidden until a navigation-activate input is received by application navigator component  404   b  via a UI element handler component  433   b . The input may be a hotkey, a touch in a designated location of a touch screen, and/or a mouse gesture defined as a navigation-activate input. Alternatively or additionally, a pointer user interface element presented within a specified distance of, for example, the top, right corner of first app  604 - 1   b  visual component may be detected as a navigation-activate input. A navigation-activate input may be defined by a particular application such as application  403   a  in  FIG. 4 a    and/or browser  403   b  in  FIG. 4 b   . In another aspect, a navigation-activate input may be defined for an execution environment. For example GUI subsystem  437   c  may include and/or otherwise access configuration information defining a navigation-activate input for applications operating in execution environment  401   c . Further, a navigation-activate input may be defined and/or detected by a node remote from a node detecting the input. Application navigator component  404   d  and navigation element handler component  406   d  operating in application provider node  506  may define and/or may detect a navigation-activate input via browser  403   b  and/or network application agent  405   b  operating in user node  502 . 
     An application navigator component  404  may determine and/or otherwise identify a region, in a presentation space, to present a navigation control  614 . The navigation region may be determined based on an application region as described above. A region including a navigation control is referred to herein as a “navigation region”. As illustrated in  FIGS. 6 a - e   , a navigation region may be determined based on an application region in various ways.  FIG. 6 a    illustrates navigation control  614 - 2   a  in a navigation region that includes the application region of second app  604 - 2   a  visual component.  FIG. 6 b    illustrates navigation control  614 - 1   b  in a navigation region determined based on the top, right corner of the application region for first app  604 - 1   b  visual component.  FIG. 6 c    illustrates navigation control  614 - 1   c  in a navigation region based on a portion of a left border of the application region that includes first app  604 - 1   c  visual component.  FIG. 6 d    illustrates navigation control  614 - 2   d  in a navigation region as a pop-up or context pane where the navigation region may be determined based on a location corresponding to an input detected in the application region including second app  604 - 2   d  visual component.  FIG. 6 e    illustrates navigation control  614 - 1   e  in a navigation region bound to menu bar  608 - 1   e  in the application region that includes first app  604 - 1   e  visual component. 
     Returning to  FIG. 2 , block  206  illustrates that the method yet further includes detecting a user input corresponding to the first navigation control. Accordingly, a system for navigating between visual components includes means for detecting a user input corresponding to the first navigation control. For example, as illustrated in  FIG. 3 , navigation element handler component  306  is configured for detecting a user input corresponding to the first navigation control.  FIGS. 4 a - d    illustrate navigation element handler component  406  as adaptations and/or analogs of navigation element handler component  306  in  FIG. 3 . One or more navigation element handler components  406  operate in execution environments  401 . 
     In an aspect, an input may be detected by a navigation element handler component  406  in  FIGS. 4 a - d   . The navigation element handler component  406  may determine a second visual component based on an ordering of applications and/or their respective visual components maintained by a corresponding application navigation component  404 . For example, an ordering may be based on a z-level of visual components, a priority assigned to an application process providing a context for an operating application, a priority and/or other attribute of a thread in an application process, and/or a user-specified ordering. In an aspect, a navigation element handler component  406  and/or an application navigation component  404   b  may identify an application and/or a visual component of an application randomly. For example, applications and/or visual components may be assigned numbers and a random number generator may be invoked to identify an application and/or visual component identified by a number generated by the random number generator. 
     Detecting a user input corresponding to a navigation control may include detecting the user input corresponding to an application control included in and/or otherwise associated with the navigation control. A navigation control may include one or more application controls corresponding to one or more respective applications. In another aspect, an application control corresponding to a particular application may be included in a navigation control. A user input may be detected corresponding to a particular application control in a navigation control. The application control identifies an application. A navigation element handler component  406  may interoperate with an application navigation component  404  to identify a visual component of the application  403 , such as the application&#39;s main window, a visual component most recently updated, and/or a visual component assigned input focus for an input device. 
     Detecting a user input corresponding to a navigation control may include detecting the user input corresponding to a visual component control included in and/or otherwise associated with the navigation control. A visual component control may be included in and/or otherwise associated with an application control corresponding to an application of a visual component corresponding to the visual component control. A navigation control and/or an application control may include one or more visual component controls corresponding to one or more respective visual components. A visual component control may be included in an application control, corresponding to a particular application, included in a navigation control. A user input may be detected corresponding to a particular visual component control in a navigation control. The visual component control identifies a particular visual component in a particular application. A navigation element handler component  406  may interoperate with an application navigation component  404  to identify the visual component of the application. 
     A navigation element handler component  406  may determine and/or otherwise detect an input corresponding to a navigation control  614 . As illustrated in  FIGS. 6 a - e   , a navigation control may be presented in various ways. A navigation control as illustrated in  FIGS. 6 a - e    may include an application control  616  and/or a visual component control  618 . 
       FIG. 6 a    illustrates first application control  616 - 1   a , second application control  616 - 2   a , and third application control  616 - 3   a  in second application control  614 - 2   a .  FIG. 6 b    illustrates first application control  616 - 1   b , second application control  616 - 2   b , and third application control  616 - 3   b  as menu items and/or submenus in navigation control  614 - 1   b  presented as a menu.  FIG. 6 c    illustrates first application control  616 - 1   c , second application control  616 - 2   c , and third application control  616 - 3   c  as first level nodes in navigation control  614 - 1   c  presented as a tree view user interface control.  FIG. 6 c    also illustrates three visual component controls  618 - 1   c ,  618 - 2   c ,  618 - 3   c  as child nodes of second application control  616 - 2   c .  FIG. 6 d    illustrates first application control  616 - 1   d , second application control  616 - 2   d , and third application control  616 - 3   d  as first level nodes in navigation control  614 - 2   d  presented as a tree view context user interface control.  FIG. 6 d    also illustrates three visual component controls  618 - 1   d ,  618 - 2   d ,  618 - 3   d  as child nodes of second application control  616 - 2   d .  FIG. 6 e    illustrates no application control for first app  604 - le  visual component.  FIG. 6 e    illustrates second application control  616 - 2   e  and third application control  616 - 3   e  as menu items and/or submenus in navigation control  614 - 1   e .  FIG. 6 e    also illustrates three visual component controls  618 - 1   e ,  618 - 2   e ,  618 - 3   e  as a child menu items of third application control  616 - 3   e.    
     An application navigation component  404  may invoke one or more navigation element handler components  406  to present and/or detect input for respective application controls and/or visual component controls. 
     Returning to  FIG. 2 , block  208  illustrates that the method yet further includes sending, in response to detecting the user input, navigation information to navigate to the second visual component. Accordingly, a system for navigating between visual components includes means for sending, in response to detecting the user input, navigation information to navigate to the second visual component. For example, as illustrated in  FIG. 3 , navigation director component  308  is configured for sending, in response to detecting the user input, navigation information to navigate to the second visual component.  FIGS. 4 a - d    illustrate navigation director components  408  as adaptations and/or analogs of navigation director component  308  in  FIG. 3 . One or more navigation director components  408  operate in execution environments  401 . 
     Sending the navigation information may include sending the navigation information by invoking a function, a method, and/or a subroutine. Sending the navigation information may include sending the navigation information by sending a message via a network. The message may be sent asynchronously. The message, in another aspect, may be included in a request/response exchange. Sending the navigation information may include sending the navigation information by sending data via an inter-process communication (IPC) including, for example, a message queue, a pipe, an interrupt, a semaphore, and/or a lock. Sending the navigation information may include sending the navigation information via a shared data area. 
     Navigation information may include information for changing an attribute of a visual component. For example, a z-order attribute, an input focus attribute, a size attribute, a location attribute, a font, a color, and/or a transparency level may be changed based on navigation information for a visual component being navigated to and/or a visual component being navigated from. 
     In  FIG. 4 a   , navigation director component  408   a  may send navigation information to a specified message queue in execution environment  401   a . Applications operating in execution environment  401   a  may subscribe to and/or poll the message queue to receive a navigation instruction. Navigation information may identify a visual component and/or an application to navigate to. An identified application may determine a visual component to navigate to if a visual component of the application is not identified by the navigation information. 
     In  FIG. 6 a   , first app  604 - 1   a  visual component may be included in a user interface for application  403   a  in execution environment  401   a . An input corresponding to second application control  616 - 2   a  may be detected by navigation element handler component  406   a . Navigation element handler component  406   a , application navigation component  404   a , and/or navigation director component  408   a  may generate navigation information based on second application control  616 - 2   a . Navigation director component  408   a  may post the navigation information to a message queue, write the navigation information to a pipe configured for exchanging navigation information between and/or among applications, and/or store the navigation information in a shared data area accessible to other applications in execution environment  401   a . A second application may receive the navigation information and determine that the navigation information identifies the second application. The second application may update second app  604 - 2   a  visual component, for example, so that it is presented on top of first app  604 - 1   a  visual component as shown in  FIG. 6 a   . The second application may determine a visual component of a user interface of second application to which to navigate. The determination may be user configurable and/or determined by execution environment  401   a.    
     In  FIG. 4 b   , navigation director component  408   b  may operate as described above. Alternatively or additionally, navigation director component  408   b  operating in user node  502  may send a message via network  504  to a remote node, such as application provider node  506 . Network application  403   d  may provide a subscription service. Navigation director component  408   b  may send navigation information to a specified publish-subscribe tuple and/or service. Applications operating in execution environment  401   a  may subscribe to and/or poll the tuple and/or service to receive navigation information. Navigation information may identify a visual component and/or an application to navigate to. An identified application may determine a visual component to navigate to if a visual component of the application is not identified by the navigation information. In  FIG. 6 b   , first app  604 - 1   b  visual component may be included in a user interface for browser  403   b  in execution environment  401   b . An input corresponding to first visual component control  618 - 1   b  associated with third application control  616 - 3   b  as illustrated may be detected by navigation element handler component  406   b . Navigation element handler component  406   b , application navigation component  404   b , and/or navigation director component  408   b  may generate navigation information based on first visual component control  618 - 1   b . Navigation director component  408   b  may post the navigation information via an asynchronous message to the specified tuple and/or service. The tuple and/or service may be accessible to other applications in execution environment  401   b  via a subscription and/or via polling for navigation information. 
     A second application may receive the navigation information and determine that the navigation information identifies a third application. The second application may ignore the navigation information or may change an attribute of a visual component in a user interface of the second application in accordance with the instruction to navigate to the identified visual component of the third application. The third application may update a third app visual component. The third app visual component may be minimized prior to processing the navigation instruction, may be hidden behind another visual component, and/or may otherwise not be visible to a user. The third application may present the visual component identified by visual component control  618 - 1   b  according to the navigation instruction represented in and/or by the navigation information. 
     In an aspect, an input detected corresponding to a navigation control may be communicated by user node  502  to network application  403   d  operating in application provider node  506 . The input information may be received by navigation element handler component  406   d . The navigation control presented by user node  502  may be presented based on presented information provided by application navigation component  404   d  based on visual components detected by PS monitor component  402   d  interoperating with user node  502 . Navigation director component  408   d  may send the navigation information to any number of requesting and/or otherwise identified client nodes, such as user node  502 . In another aspect, navigation director component  408   d  may determine a node to receive the navigation information. Navigation director component  408   d  may send the navigation information to the node identified by the determination. Navigation director component  408   d  may send the navigation information in an unsolicited message via an asynchronous message and/or may send the navigation information in response to a request from the identified node. 
     In  FIG. 4 c   , navigation director component  408   c  may send navigation information by invoking a function, method, subroutine, and/or other addressable instruction in an application identified based on the detected input corresponding to a navigation control. Applications operating in execution environment  401   c  may register an invocation point with GUI subsystem  437   c . Registration may be explicit and/or implicit in an interoperation between an application  403   c  and GUI subsystem  437   c . Navigation information may identify a visual component and/or an application to navigate to. An identified application may determine a visual component to navigate to if a visual component of the application is not identified by the navigation information. In  FIG. 6 c   , first app  604 - 1   c  visual component may be included in a user interface for an application  403 - 1   c  in execution environment  401   c . An input corresponding to second application control  616 - 2   c  may be detected by navigation element handler component  406   c . Navigation element handler component  406   c , application navigation component  404   c , and/or navigation director component  408   c  may generate navigation information based on second application control  616 - 2   c . Navigation director component  408   c  may invoke second application  403 - 2   c  providing access to the navigation information via the invocation. Second application  403 - 2   c  may receive the navigation information and determine a visual component to navigate to if one is not identified in the navigation information. The second application may update second app  604 - 2   c  visual component by moving it from behind first app  604 - 1   c  visual component. 
     In another aspect, navigation director component  408   c  may invoke first application  403 - 1   c , instructing first application  403 - 1   c  to change a transparency level of first app  604 - 1   c  visual component allowing second app  604 - 2   c  visual component to be visible to a user. Navigation director component  408   c  may assign input focus for one or more input devices to the visual component of second application  403 - 2   c  so that input from the one or more input devices is routed to second application  403 - 2   c  and corresponds to the visual component according to the navigation instruction of the navigation information. In various aspects, one or both of first application  403 - 1   c  and second application  403 - 2   c  may be sent navigation information. In another aspect, neither first application  403 - 1   c  nor second application  403 - 2   c  may be sent navigation information. Rather, navigation information may be sent to a component of GUI subsystem  437   c . For example, GUI subsystem  437   c  may change the transparency level of first app  604 - 1   c  visual component and assign input focus to second app  604 - 2   c  visual component in navigating to second app  604 - 2   c  visual component. 
     As described above, in response to navigating to a visual component, a navigation control, in a navigation region determined based on the application region of the visual component, may be presented for navigating from the visual component to another visual component. Thus some or all visual components of some or all operating applications in an execution environment may be presented with a navigation control for navigating to another visual component of the same and/or of a different application. 
     The method illustrated in  FIG. 2  may include additional aspects supported by various adaptations and/or analogs of the arrangement of components in  FIG. 3 . In various aspects, a visual component may be included in and/or may include window, a dialog box, a textbox, a check box, a radio button, a slider, a list box, a drop-down list, a spinner, a menu, a menu item, a toolbar, a ribbon, a combo box, a tree view, a grid view, a navigation tab, a scrollbar, a label, a tooltip, a balloon, a slide-out control, a pop-up, a pop-over, a pop-under, and a sidebar, to name a few examples. 
     A first application presenting a first visual component may operate in a first process in an execution environment and a second application presenting a second visual component may operate in a second process in the execution environment. Further, the first and second application may be generated from different source code. The first application may be represented in a processor memory by at least a portion of a first program generated from first source code and the second application may be represented in a processor memory by at least a portion of a second program generated from second source code 
     Detecting a visual component may include detecting a measure of visibility of the first visual component to a user. A measure of visibility may be based on at least one of a z-order, an attribute of a font, a size, a location in the presentation space, a transparency attribute, and/or a size of a visible portion of a visual component. For example, in  FIG. 4 c    PS monitor component  402   c  may receive information identifying a measure of visibility for any visual component processed by GUI subsystem  437   c.    
     A navigation control for a visual component may be presented in response to a change detected in a visually detectable attribute of the visual component. For example, an application navigator component  404  in  FIGS. 4 a - d    may be configured to hide a navigation control  614  in response to maximizing a corresponding app  604  visual component in a user interface of an application  403 . When the app  604  visual component is restored to its non-maximized state, the application navigation component  404  may present a navigation control  614  for the app  604  visual component. The navigation control  614  may be presented automatically in response to an input and/or other instruction to present the app  604  visual component in its normal state, neither minimized nor maximized. 
     A navigation region may be determined based on a location of a visual component, a parent visual component of the visual component, and a child visual component of the visual component. For example, in  FIG. 6 a    an application navigation component  404  in  FIGS. 4 a - d    may determine a navigation region for second navigation control  614 - 2   a  where second navigation control  614 - 2   a  is a parent of second app  604 - 2   a  visual component and includes an application region of the visual component, second app  604 - 2   a .  FIG. 6 b    illustrates that an application navigation component  404  may determine a navigation region including navigation control  614 - 1   b  where the navigation region is adjacent to the application region of first app  604 - 1   b  visual component.  FIG. 6 e    illustrates that an application navigation component  404  may determine a navigation region based on menu bar  608 - 1   e  included as a child visual component in first app  604 - 1   e  visual component. 
     A navigation region may be determined based on a border of a visual component, a parent visual component of the visual component, and a child visual component of the visual component.  FIG. 6 b    and  FIG. 6 c    illustrate navigation regions for navigation control  614 - 1   b  and navigation control  614 - 1   c  respectively determined based on a border of first app  604 - 1   b  visual component and first app  604 - 1   c  visual component.  FIG. 6 b    and  FIG. 6 c    further illustrate that a navigation region may share a border with an associated application region, may be at least partially included in the application region, and may be outside the application region. 
     In an aspect, a navigation control and/or an associated visual component may be at least partially transparent. A transparency attribute of the navigation control and/or the visual component may be responsive to a change in a position of a visual representation of an input pointer, a change in an input focus attribute associated with at least one of the navigation control and the visual component, and/or a transparency attribute of the respective visual component and/or the navigation control. A navigation element handler component  406  in  FIGS. 4 a - d    may be configured to manage the transparency of a navigation control and may further interoperate with a UI element handler component  433  and/or a graphics subsystem  439  to manage transparency of a corresponding visual component. 
     Presenting a navigation control may include detecting the navigation control presented in a previous navigation region determined based on a corresponding application region. Presenting may further include detecting a move indication (in response to a detected user input), and determining the navigation region based on at least one of a current application region and the previous navigation region. A navigation region may be determined based on the move indication. Further, presenting the navigation control may include determining that a corresponding application region differs from a previous application region in the presentation space, which includes a visual component that corresponded to the navigation region prior to the presenting. Presenting may further include presenting the navigation control in the navigation region from a previous navigation region determined based on the previous application region. 
     For example, an application navigation component  404  and/or a navigation element handler component  406  may be configured to minimize movement of a navigation control  614  and present the navigation control  614  along a border of a corresponding visual component. When the visual component is moved and/or resized, the application navigation component  404  and/or a navigation element handler component  406  determine a navigation region to include the moved and/or resized navigation control  614  based on the previous navigation region and based on the new application region. Alternatively or additionally, a first input may indicate that a navigation control is to be presented adjacent to a first border of a visual component and a second input may indicate that the navigation control is to be presented as a child visual component of the visual component. 
     As described above, an application control and/or a visual component control may be included in and/or activated for receiving input based on a state of a corresponding application and/or a state of a visual component of the corresponding application. A state may indicate that an application and/or a visual component is minimized, hidden, partially hidden, suspended, blocked, and/or that access is not authorized. 
     An application control and/or a visual component control may be presented in a plurality including at least one of a plurality of application controls and a plurality of visual component controls based on a specified order of at least one of a plurality of applications corresponding to the plurality of application controls and a plurality of visual components corresponding to the plurality of visual component controls. A specified order may be based on a time attribute, an application identifier, a z-order attribute, a size attribute, a color attribute, a font, a state of a process context for an application, a state of a thread context in the process context, and/or a user-assigned order. 
     To the accomplishment of the foregoing and related ends, the descriptions and annexed drawings set forth certain illustrative aspects and implementations of the disclosure. These are indicative of but a few of the various ways in which one or more aspects of the disclosure may be employed. The other aspects, advantages, and novel features of the disclosure will become apparent from the detailed description included herein when considered in conjunction with the annexed drawings. 
     It should be understood that the various components illustrated in the various block diagrams represent logical components that are configured to perform the functionality described herein and may be implemented in software, hardware, or a combination of the two. Moreover, some or all of these logical components may be combined, some may be omitted altogether, and additional components may be added while still achieving the functionality described herein. Thus, the subject matter described herein may be embodied in many different variations, and all such variations are contemplated to be within the scope of what is claimed. 
     To facilitate an understanding of the subject matter described above, many aspects are described in terms of sequences of actions that may be performed by elements of a computer system. For example, it will be recognized that the various actions may be performed by specialized circuits or circuitry (e.g., discrete logic gates interconnected to perform a specialized function), by program instructions being executed by one or more instruction-processing units, or by a combination of both. The description herein of any sequence of actions is not intended to imply that the specific order described for performing that sequence must be followed. 
     Moreover, the methods described herein may be embodied in executable instructions stored in a computer-readable medium for use by or in connection with an instruction execution machine, system, apparatus, or device, such as a computer-based or processor-containing machine, system, apparatus, or device. As used here, a “computer-readable medium” may include one or more of any suitable media for storing the executable instructions of a computer program in one or more of an electronic, magnetic, optical, electromagnetic, and infrared form, such that the instruction execution machine, system, apparatus, or device may read (or fetch) the instructions from the computer-readable medium and execute the instructions for carrying out the described methods. A non-exhaustive list of conventional exemplary computer-readable media includes a portable computer diskette; a random access memory (RAM); a read only memory (ROM); an erasable programmable read only memory (EPROM or Flash memory); optical storage devices, including a portable compact disc (CD), a portable digital video disc (DVD), a high definition DVD (HD-DVD™), and a Blu-ray™ disc; and the like. 
     Thus, the subject matter described herein may be embodied in many different forms, and all such forms are contemplated to be within the scope of what is claimed. It will be understood that various details may be changed without departing from the scope of the claimed subject matter. Furthermore, the foregoing description is for the purpose of illustration only, and not for the purpose of limitation, as the scope of protection sought is defined by the claims as set forth hereinafter together with any equivalents thereof. 
     All methods described herein may be performed in any order unless otherwise indicated herein explicitly or by context. The use of the terms “a” and “an” and “the” and similar referents in the context of the foregoing description and in the context of the following claims are to be construed to include the singular and the plural, unless otherwise indicated herein explicitly or clearly contradicted by context. The foregoing description is not to be interpreted as indicating that any non-claimed element is essential to the practice of the subject matter as claimed.