KR102061363B1 - Docking and undocking dynamic navigation bar for expanded communication service - Google Patents

Abstract

Navigation bars are provided to switch between modules within an extended communication service such as email, calendar, contacts, tasks, etc. and to provide a user with a preview peek associated with each module. . A temporary preview of the module may be provided upon hover action on a predefined navigation bar location, such as an icon and / or text identifier, without actually switching to the module. One or more preview windows may be docked or docked at a dynamically selected or user defined location on the main user interface such that it is permanently displayed within the main user interface. The user can cause the user interface controls to undock one or more of the docked preview windows. New actions or actions of interest within each module may be highlighted, for example, by displaying an information badge next to the module name.

Description

DOCKING AND UNDOCKING DYNAMIC NAVIGATION BAR FOR EXPANDED COMMUNICATION SERVICE}

With the proliferation of computing and networking technologies, the functionality and features of software applications have increased both quantitatively and qualitatively. Locally installed applications that provide a single tool are increasingly replaced with hosted services that combine multiple related functions. Microsoft® Outlook®, based in Redmond, Washington, is an example of such a tool. The program is locally installed or available for hosted service versions, allowing users to interact via email or text messaging, schedule appointments and meetings, manage tasks and / or contacts, and perform similar actions. To do it. The services provided by such programs are correlated in many ways. For example, email and text messaging (and meeting scheduling) services may be associated with a user's contacts, and scheduling meetings may be delivered to other users via email.

A software program (or service), such as Outlook®, provides a number of features and functions for each of the services it contains. These features and functions are combined when the number of tools provided by the program increases. As a result of this compounding, the complexity of the user interface increases, which makes the user more difficult to navigate. Menus and different user interfaces may allow a user to navigate individual features of the program, but the combined user interface has room for improvement of the user experience.

This Summary is provided to introduce a selection of concepts in a simplified form that are further described below in the Detailed Description. This Summary is not intended to represent essential or essential features of the claimed subject matter, nor is it intended to be used to limit the scope of the claimed subject matter.

Embodiments switch between modules within an extended communication service such as email, calendar, contacts, tasks, etc. and a navigation bar to provide the user with a preview peek associated with each module. It is about. According to some embodiments, a temporary preview of a module may be provided without actually switching to the module upon hover action over predefined navigation bar locations such as icons and / or text identifiers. One or more preview windows may be docked or docked at a dynamically selected or user defined location on the main user interface such that it is permanently displayed within the main user interface. The user can cause the user interface controls to undock one or more of the docked preview windows. New actions or actions of interest within each module may be highlighted, for example, by displaying an information badge next to the module name.

These and other features and advantages will become apparent upon review of the following detailed description and the associated drawings. It is to be understood that both the foregoing general description and the following detailed description are exemplary and are not limiting of the subject matter.

1 illustrates some exemplary devices in which a dynamic navigation bar for an extended communication service may be employed.
FIG. 2 illustrates a screenshot of a main user interface for an exemplary scalable communication service with a dynamic navigation bar in accordance with embodiments. FIG.
3 illustrates a calendar preview presented from the exemplary main user interface and navigation bar of FIG. 2 with a navigation bar in a minimized state.
4 illustrates the exemplary main user interface of FIG. 2 with two preview windows docked on the right side of the user interface.
5 illustrates an example preview type for a different module associated with a navigation bar in accordance with embodiments.
6 illustrates two exemplary preview windows docked together.
7 illustrates two other exemplary preview windows docked together.
8 illustrates three exemplary preview windows docked together.
9 illustrates a configuration menu for an exemplary navigation bar in accordance with embodiments.
10 illustrates a networked environment in which a system in accordance with embodiments may be implemented.
11 is a block diagram of an example computing operating environment in which embodiments may be implemented.
12 is a logic flow diagram for a process for providing a dynamic navigation bar when a preview window is docked and undocked in accordance with embodiments.

As briefly described above, the dynamic navigation bar may be provided with scalable communication services for email, text messaging, scheduling, task management, contact management, and similar services. The preview window is temporarily displayed in response to a hover action on the navigation bar item, which may be docked at a dynamically selected or user defined location on the user interface for permanent display or undocked if desired by the user.

DETAILED DESCRIPTION The following detailed description refers to the accompanying drawings, in which specific embodiments or examples are shown by way of example. These features may be combined, other features may be utilized, and structural changes may be made without departing from the spirit or scope of the disclosure. The following detailed description, therefore, is not to be taken in a limiting sense, and the scope of the present invention is defined by the appended claims and their equivalents. While embodiments will be described in the general context of a program module executing with an application program running on an operating system on a personal computer, those skilled in the art will understand that features may be implemented with other program modules.

Generally, program modules include those that perform particular tasks or implement particular abstract data types, such as routines, programs, components, data structures, and the like. In addition, those skilled in the art will appreciate that embodiments may be practiced in other computing system configurations, including handheld devices, multiprocessor systems, microprocessor-based or programmable consumer electronics, minicomputers, mainframe computers, and equivalent computing devices. There will be. Embodiments may also be practiced in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network. In a distributed computing environment, program modules may be located in both local and memory storage devices.

Embodiments may be implemented as a computer-implemented process (method), computing system, or as a product such as a computer program product or a computer readable medium. The computer program product may be a computer storage medium that is readable by a computer system and that encodes a computer program that includes instructions that cause a computer or computing system to perform the exemplary process. The computer readable storage medium is a computer readable memory device. The computer readable storage medium may be embodied by one or more of, for example, volatile computer memory, nonvolatile memory, hard drive, flash drive, floppy disk, compact disk, and the like.

As used herein, scalable communications services refer to hosted services, enterprise services, or locally installed applications, which include services such as email communications, text message exchange, calendar functions, task management, contact management, and similar functions. to provide. Such a service may include a number of integrated modules for personal services or some modules may provide a plurality of services. The main user interface may allow the user to interact with the service to receive notifications, view different items, or provide input for various functions. As described below, various devices may be used to perform these services, including touch input, gesture input, voice input, gyroscope input via a finger, pen, mouse, or similar device, and predefined keyboard input. Other interaction mechanisms such as combinations may be used.

1 illustrates some example devices in which a dynamic navigation bar for an extended communication service may be used. The scalable communication service according to the embodiments may be provided to the server-client architecture as a cloud-based service or as the locally installed application described above. Thus, various devices can be used to present the user interface to the user. In addition to other computing devices, consumer electronics (eg, TV consoles), personal digital assistants (PDAs), mobile phones, digital media and music players, handheld game consoles, calculators, and computer peripherals may be used.

Portable devices, many of which employ touch or gesture based input, tend to have smaller screen sizes, which means that the available space for the user interface is smaller. For example, in addition to the presented portion of the document, a virtual keyboard must be displayed, which further defines the available space (“real estate”). Thus, for such a scenario, it may be impractical or inconvenient for a user to provide a multi-faceted communication service to the entire user interface.

With reference to FIG. 1, some exemplary devices are shown wherein dynamic navigation bars can be provided according to embodiments that save valuable screen real estate while enabling efficient display of information associated with different embodiments. Embodiments may be implemented in different devices having various form factors and functions.

1 illustrates a computer monitor 116, a touch enabled 120 laptop computer 118, a handheld computer 124, a smartphone 126, a tablet computer (or slate) 128, and a mobile computing device 132. And some exemplary devices that can be used for calculation, communication, control, measurement, and many other purposes. Some of the example devices of FIG. 1 are shown having a touch active function 120. However, any of these and other exemplary devices may utilize the activation by gesture function. Also, a tool such as pen 130 may be used to provide touch input. The dynamic navigation bar and associated preview can also be controlled through conventional methods such as mouse input or input via keyboard 122.

2 depicts a screenshot of a main user interface for an exemplary scalable communication service with a dynamic navigation bar in accordance with embodiments. An example user interface in screenshot 200 displays information associated with an email module of an extended communication service. This information includes a folder list 202 and an email list 204 in the selected folder. The third viewing pane on the user interface displays the selected email 206.

In addition to email, scalable communication services may provide text messaging, scheduling, task management, contact management, and similar functionality. In a conventional user interface, the user can switch between modules providing different functions by selecting menu items or corresponding control elements. However, switching between modules results in disrupting the user experience. For example, if a user changes a view from an email to a calendar, the information associated with the email is no longer available and vice versa. Thus, the user does not have the ability to review one module while continuing to look at one module without interference. Some applications may allow a user to view multiple modules on the same user interface, but due to display space limitations, the displayed view may be limited or the user interface may contain too much information to confuse the user's navigation. It may be.

According to some embodiments, a text, graphic, or combination navigation bar 208 is provided on the user interface that allows a user to switch between different modules and to view a preview of another module without leaving the current view of the user interface. Can be provided. To maintain valuable display space, the navigation bar 208 does not occupy space from other displayed items, such as the bottom side, both sides, top side, or equivalent position (as shown in the figure). Can be dynamically placed in a location on the user interface without having to.

Keyboards, mice, touches, gestures, pen inputs, voice commands are exemplary input mechanisms that can be used with the navigation bar (and user interface). Other exemplary input mechanisms include, but are not limited to, accelerometer or direction sensor based inputs, optically captured gestures, time based inputs, proximity to other devices / persons / places, and the like. In some embodiments, the navigation bar includes a user's left or right handedness, the size of a finger (in a touch-based device), the size of a tap gesture pointer associated with a pointing device, the user credentials, the ergonomic characteristics of the computing device, and The left, right, top or top of the user interface based on one or more of the location attributes, including one or more of a language selection, geographic location information, time zone information, and / or country information for the user interface. It can be presented and / or moved along the bottom. If the size of the user interface changes (eg, changes in the display or opens another user interface on the screen, etc.), the navigation bar 208 is moved and / or resized.

In some embodiments, the layout of the items displayed on the navigation bar 208 may be automatically sorted and rearranged based on the elements or other elements listed above. Multiple configurations may be used to improve the efficiency of the navigation bar 208, such as color schemes, graphical schemes, shading schemes, and similar schemes. For example, items may be displayed in a dark format and / or in a bright format, which may be used interchangeably depending on the background color.

FIG. 3 illustrates a calendar preview presented from the exemplary main user interface and navigation bar of FIG. 2 with a minimized navigation bar. As mentioned above, the items on the navigation can be text, graphics (eg, icons), or a combination of both. Icon-based navigation bars can be displayed in smaller sizes, thus saving display space.

The screenshot 300 of FIG. 3 displays the user interface of FIG. 2, where the text-based navigation bar at the bottom of the user interface has been replaced with an icon-based minimized state navigation bar 320. The minimized state navigation bar 320 may include only icons or a combination of icons and text. In some embodiments, a textual tip may be displayed adjacent to the icon upon user selection (or hover operation). Alternatively, some icons may include text tips and other icons may not include text tips (eg, if generally known).

Another feature of the navigation bar according to the embodiments is the preview feature. To allow the user to get a preview of the module without leaving the currently displayed module, the preview window 324 may be temporarily displayed in response to a hover action on one of the items in the navigation bar. In screenshot 300, a calendar preview window 324 is displayed in response to user hovering on calendar item 322 in minimized state navigation bar 320. The calendar preview window lists a summary 328 of a user's calendar 326 (eg, month, week, day, etc.) and some of the items on the calendar (eg, appointments). It may include.

Preview window 324 may enable limited interaction with the user. For example, a user can select one of the displayed summary items and view details about that item. The information displayed in the preview window can be determined automatically based on default parameters, learned from user actions, manually configurable by the user, or obtained from other applications associated with the user. In addition, display and removal of the preview window may be done in an animated manner. The scope of the interaction may be predefined.

In some embodiments, the design of the preview window may be chosen to be consistent across different devices / applications. For example, the preview window for the desktop user interface may be the same as or similar to the module user interface on a handheld device user interface (eg, a smartphone), thereby allowing the user to have a consistent view and feel across devices. Can be.

4 illustrates the example main user interface of FIG. 2 with two preview windows docked on the right side of the user interface. Upon detecting a hover or similar operation on the navigation bar 408, the application under the user interface on the screenshot 400 may display a temporary preview window associated with the item of interest as described above. Text or graphic control elements 426 and 428 on the temporarily displayed preview window may allow the user to dock or dock the preview window 422 at a predefined or dynamically selected location on the user interface.

The location of the preview window docking may be determined based on the user interface context, available display space, content of the user interface, application type, device type, user credentials, and / or similar factors. The user may also select a location for docking the preview window. The user may also pin the plurality of preview windows 422, 424. The position, size, and content of the fixed preview window can be adjusted automatically when additional preview windows are docked or undocked. The function of the control element to enable docking of the preview window may change to undocking when the preview window is docked. Alternatively, other control elements for the docked preview window may be provided.

5 illustrates an example preview type for a different module associated with a navigation bar according to embodiments. The content of the preview window may be determined automatically (eg, via machine learning, user history, retrieval of information from another application, etc.) and may be user configurable.

The preview windows shown in diagram 500 are example preview windows for illustrative purposes. As noted above, the navigation bar in accordance with embodiments may be extensible and may include items representing multiple default or additional modules. Thus, a preview window associated with each of the items on the navigation bar can be provided. For example, a productivity or customer relationship management (CRM) function module can be added to the scalable communication service along with the associated navigation bar items and the preview window.

Each preview window may provide summary information related to related modules having limited interaction with the user. For example, the email preview window 530 can list a number of emails (eg, top few, newest few, etc.) and allow the user to open, delete, mark, or list new items. To initiate. Which items to list may be determined automatically or may be configurable by the user. The contact preview window 532 may display summary contact information for favorite contacts, most recent contacts, and the like. The task list preview window 534 may display a summary list of some of the tasks in chronological order and allow the user to mark tasks as completed, important, and the like. The calendar preview window 536 may display a summary calendar (month, week, day, etc.) and calendar items (appointments, meetings, etc.) such as most important items, newest items, current items, and the like.

Although the list of items (emails, calendar items, tasks, contacts, etc.) may be limited to the space available on the preview window, additional items may be displayed through the use of scroll bars or similar mechanisms. In some embodiments, the preview type may be active or inactive based on the context of the user interface. For example, if the user interface is displaying information related to an email module, it may be unnecessary to display a preview for the email and the preview may be deactivated as long as the email is the main displayed module. Similarly, the displayed item on the navigation bar may change based on the context of the user interface. Thus, if an email is the main displayed module on the user interface, the email item on the navigation bar may be replaced by another item.

The preview window configuration described above is exemplary only and does not limit the embodiments. The minimized or full status preview window associated with the dynamic navigation bar in accordance with embodiments may have a configuration and combination of any of the text, graphics, and other items utilizing the principles described herein. Similar configurations and presentations can also be used for other modules such as email, contacts, tasks, and the like.

6 shows three example previews docked together. Various preview windows associated with different modules supported by the communication service / application may be displayed and docked on the user interface. Diagram 600 shows two example preview windows, a calendar preview window 642 and an email preview window 648.

The calendar preview window 642 includes a monthly calendar view 644 and a list 646 of upcoming calendar items. Email preview window 648 includes a view of the user's inbox 659 that includes a subject line and an email list 652 identified by the sender. Additional information may be provided in the form of an icon indicating whether the email was replied to, whether it was sent, whether it contains an attachment or the like. Upon detection of a hover action on one of the listed emails, the email may be highlighted (654) and a delete option (or an option to perform another action) may be presented to the user.

As mentioned above, the preview window provides limited interaction to the user. When the preview window is docked, the functionality it provides may be modified in accordance with some embodiments. For example, additional interaction functionality may be provided. In addition, when a new preview window is added or an existing preview window is undocked, the size, content, and order of the docked preview window may be adjusted. In addition, the docked preview window may be automatically undocked in response to changes in the user interface. For example, if the user interface changes to displaying an email module in the main view, the preview window for the email may no longer be needed and thus may be removed.

7 shows two other exemplary previews docked together. Diagram 700 shows a task preview window 756 and a contact preview window 762. The task preview window 756 lists the different tasks 760 in chronological order, grouped by TODAY and TOMORROW. Limited functionality, such as task flagging or changing a property of a task (eg, in progress, completed) may be provided along with the ability to create a new task 758.

The contact preview window 762 displays the user's favorite contacts 766 with a contact search function 764. The type of item (task or person) to list, the classification of the item, and the functionality provided to the user can be configurable or automatically determined.

8 illustrates three exemplary previews docked together in conjunction with a navigation bar in accordance with embodiments. The preview window according to embodiments may be temporarily displayed in response to the hover action on the navigation menu. According to some embodiments, one or more preview windows may be docked or fixed at a fixed location on the user interface for permanent display. Diagram 800 shows a combination of three preview windows docked together.

In the example of diagram 800, the calendar preview window 868, the contact preview window 872, and the task preview window 874 are docked together. Docking icon 870 indicates that the preview window is currently docked and can be used to undock (or hide) the preview window. The location for docking the preview window may be dynamically selectable by a program based on user-selectable or displayed information on the user interface and available display area. Similarly, the size and content of the docked preview window can be selectable and modified based on the context and display space of the user interface.

According to some embodiments, the preview window may be docked or undocked, depending on the animation configuration. In addition, color schemes, graphical schemes, and / or shading schemes can be used to enhance the visual effect of the preview window in docked or undocked form.

9 illustrates a configuration menu for an exemplary navigation bar in accordance with embodiments. The navigation bar and associated preview window may be configured automatically as described above, but a configuration menu may be provided for customization.

According to some embodiments, a higher level menu 976 may be provided for the user to select and customize the navigation bar itself, individual items on the navigation bar, and / or preview window settings. The configuration menu 900 for customizing the preview window settings may include an option to activate or deactivate some or all of the preview windows. The configuration menu 900 may further include separate sections for various preview window types, such as calendar preview options 980, mail preview options 982, contact preview options 984, and task preview options 986. .

Configurable options for an individual preview window type may be determined based on application functionality, context of the user interface, device functionality, user credentials (eg, privilege level), and the like. Configurable options may be dynamically modified in response to an application, computing device, display device, language or region selection, or similar changes.

The example configurations, navigation bars, items, and interactions shown in FIGS. 1-9 are provided for illustrative purposes. Embodiments are not limited to the shapes, shapes, and contents shown in the example diagrams, but may be implemented using other text, graphics, and similar arrangements using the principles described herein.

10 illustrates an example networked environment in which embodiments may be implemented. In addition to locally installed applications, such as the communications application 1022 described below, the navigation bar may be used with hosted applications and services that may be implemented through software running on one or more servers 1006 or individual servers 1008. have. The hosted service or application may be a web-based service or application, a cloud-based service or application, and the like, and may include a handheld computer 1001, a desktop computer 1002, a laptop computer 1003 via a network 1010. ), It can communicate with client applications on a personal computer device, such as smart phone 1004, tablet computer (or slate) 1005 (client device), and control the user interface presented to the user. An example of a Web-based service is Microsoft® Outlook®, Redmond, Washington, which provides clients with email, text messaging, calendar, task management, and contact management services through a browser interface on a client device. Such a service may enable a user to interact with the displayed content through a dynamic navigation bar and various input mechanisms as discussed herein.

Client devices 1001-1005 are used to access functionality provided by a hosted service or application. One or more of server 1006 or server 1008 may be used to provide the various services described above. Related data may be stored in one or more data stores (eg, data store 1014), which may be managed by either one of the servers 1006 or the database server 1012.

Network 1010 may include any topology of servers, clients, Internet service providers, and communication media. The system according to embodiments may have a static or dynamic topology. The network 1010 may include a secure network, such as an enterprise network, an insecure network, such as a wireless open network, or the Internet. The network 1010 may coordinate communications over another network, such as a PSTN or a cellular network. Network 1010 provides communication between the nodes described herein. For example, network 1010 may include, but is not limited to, wireless media such as acoustic, RF, infrared, and other wireless media.

Many other configurations of computing devices, applications, data sources, and data distribution systems may be used to provide dynamic navigation bars with scalable communication services. In addition, the networked environment discussed in FIG. 10 is for illustrative purposes only. Embodiments are not limited to these example applications, modules, or processes.

11 and related discussion are intended to provide a brief, general description of a suitable computing operating environment in which embodiments may be implemented. Referring to FIG. 11, shown is a block diagram of an exemplary computing operating environment for an application according to embodiments, such as computing device 1100. In a basic configuration, computing device 1100 may be any computing device, such as a stationary, mobile, or other type, such as the example device discussed with FIG. 1, with at least one processing unit 1102 and system memory 1104. ) May be included. The computing device 1100 may also include a plurality of processing units that cooperate in an executable program. Depending on the exact configuration and type of computing device, system memory 1104 may be volatile (eg, RAM), nonvolatile (eg, ROM, flash memory, etc.), or some combination of the two. System memory 1104 typically includes an operating system 1105 suitable for controlling the operation of the platform, such as Microsoft's WINDOWS®, WINDOWS MOBILE®, or WINDOWS PHONE® operating system located in Redmond, Washington. System memory 1104 may also include one or more software applications, such as program module 1106, communication application 1122, user interface module 1124, and preview module 1126.

The user interface module 1124 can work with the communication application 1122 and provide a user interface that allows the user to interact with various modules of the communication application such as email, text messaging, calendars, task lists, and contacts. Can be. In addition to providing separate viewing windows for modules, menus, and text / graphic controls, the user interface module 1124 provides a dynamic navigation bar that allows the user to switch between viewing modules of different modules while preserving valuable display space. You may. In addition, the preview module 1126 may enable the display of a preview window for each module highlighting a new action and an action of interest associated with each module. The preview window can be docked or undocked as described herein. The basic configuration is shown in FIG. 10 as components within dashed line 1108.

Computing device 1100 may have additional features and functionality. For example, computing device 1100 may include additional data storage devices (removable and / or non-removable) such as, for example, magnetic disks, optical disks, or tapes. Such additional storage is shown in FIG. 11 as removable storage 1109 and non-removable storage 1010. Computer-readable storage media may include volatile and nonvolatile, removable and non-removable media implemented in any method or technology for storage of information such as computer readable instructions, data structures, program modules, or other data. . System memory 1104, removable storage 1109 and non-removable storage 1110 are all examples of computer readable storage media. Computer-readable storage media may include RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disk (DVD) or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices. Or any other medium that can be used to store desired information and can be accessed by the computing device 1100. Any such computer readable storage media may be part of computing device 1100. The computing device 1100 may have input devices 1112 such as a keyboard, mouse, pen, voice input device, touch input device, optical capture device for detecting gestures, and an equivalent input device. Output devices 1114 may be included, such as displays, speakers, printers, and other types of output devices. These devices are well known in the art and need not be discussed here for a long time.

Computing device 1100 may also include a communications connection 1116 that enables the device to communicate with other devices 1118, such as through a wireless network, satellite link, cellular link, and similar mechanism in a distributed computing environment. . Other devices 1118 may include computer devices running communication applications, other directory or policy servers, and similar devices. Computer connection 1116 is an example of a communication medium. Communication media may include computer readable instructions, data structures, program modules, or other data in a modulated data signal such as a carrier or other transmission mechanism, and includes any information delivery media. The term "modulated data signal" means a signal that has one or more of its characteristics set or changed in such a manner as to encode information in the signal. For example, communication media include wired media such as a wired network or direct wired connection, and wireless media such as acoustic, RF, infrared and other wireless media.

Example embodiments also include methods. These methods can be implemented in a variety of ways, including the configurations described herein. One such method is implemented by machine operation of an apparatus of the type described herein.

Another optional method is for one or more of the individual operations of the method to be performed in conjunction with some operations performed by one or more operators performing some operations. These operators do not need to collaborate with each other, each just needs to have a machine that runs part of the program.

12 illustrates a logic flow diagram for a process for providing a dynamic navigation bar when a preview window is docked and undocked in accordance with embodiments. Process 1200 may be implemented as part of an extended communication service or application.

Process 1200 begins at operation 1210, where a dynamic navigation bar is displayed on the user interface of the scalable communication service or application. The navigation bar may include items presented in the form of text, graphics, or a combination. The navigation bar can be displayed at an appropriate location on the user interface so that the display space is used efficiently. At operation 1220, a hover action or similar indication of interest by the user on one of the items in the navigation bar may be detected, and then an associated preview may be temporarily displayed at operation 1230.

At operation 1240, a docking request for the displayed preview window, such as activation of a control element for docking, may be received. In operation 1250, the displayed preview window may be docked at a user-defined or dynamically selected location on the user interface. The temporary display of the preview window according to the hover operation and docking of the displayed preview window may be repeated to dock the plurality of preview windows.

At operation 1260, an undocking request may be received via the same control element or other control element that is activated on the docked preview window. In operation 1270, the docked preview window that receives the undocking request is undocked and hidden. Operations 1260 and 1270 can be repeated, where the user can undock one or more (or all) docked preview windows.

The operations included in process 1200 are for illustration. Providing the dynamic navigation bar in a different state, including a minimized state for the scalable communication service according to embodiments, is different by similar processes with fewer or additional steps, and also using the principles described herein. It may be implemented in the order of operation.

The above description, examples, and data provide a complete description of the manufacture and use of the composition of the embodiments. Although the subject matter is described in language specific to structural features and / or methodological acts, it is to be understood that the subject matter defined in the appended claims is not necessarily limited to the specific features and acts described above. Rather, the specific features and acts described above are disclosed as example forms of implementing the claims and embodiments.

Claims (19)

A method of providing a dynamic navigation bar having preview docking and undocking functionality within an expanded communication application, executed at least in part on a computing device, the method comprising:
Displaying the navigation bar in the user interface of the communication application, the navigation bar including a plurality of items representing individual modules of the communication application;
In response to detecting a hover action on a navigation bar item,
Determine whether a preview pane associated with the module represented by the navigation bar item is active based on the context of the current view of the user interface, wherein the preview window is selected by another module represented by another navigation bar item. Activated when displayed in the current view of the user interface,
In response to determining that the preview window is active, temporarily display the preview window presenting content associated with the module concurrently with the current view of the user interface presenting content associated with the other module-the preview window and The format of the current view is different-,
Allow interaction with the presented content associated with the module via the temporarily displayed preview window, wherein the presented content associated with the module includes one or more items, wherein the interaction opens, marks the one or more items. Doing and deleting, and creating a new item-
In response to receiving the docking request, docking the preview window at one of a predefined location and a dynamically determined location on the user interface for permanent display;
In response to detecting that the module is displayed in a current view of the user interface, automatically undocking the preview window from the user interface.
How to provide a dynamic navigation bar comprising a.
The method of claim 1,
At least one of the set of the scope of the interaction, the presented content, the layout of the presented content, and the format of the presented content is configurable by the user
How to provide a dynamic navigation bar.
The method of claim 2,
At least one of the set of the range of interactions, the presented content, the layout of the presented content, and the format of the presented content is based on one or more of a machine learning process that analyzes user behavior and information received from other applications. Automatically determined
How to provide a dynamic navigation bar.
The method of claim 1,
Further comprising disabling one or more preview windows associated with one or more navigation bar items.
How to provide a dynamic navigation bar.
The method of claim 1,
Automatically deactivating a preview window associated with the module displayed in the current view on the user interface.
How to provide a dynamic navigation bar.
The method of claim 1,
Dynamically locate a location for docking the preview window based on at least one of a set of currently displayed modules, an available display area, displayed content on the user interface, an application type, a device type, and a user credential; Further comprising the step of determining
How to provide a dynamic navigation bar.
The method of claim 1,
Further comprising allowing docking of the plurality of preview windows.
How to provide a dynamic navigation bar.
The method of claim 7, wherein
Adjusting at least one of the set of size, layout, position, and content of the docked preview window in response to one of docking a new preview window and undocking an existing preview window.
How to provide a dynamic navigation bar.
The method of claim 1,
Further comprising at least one of a set of displaying, hiding, docking, and undocking the preview window in an animated manner.
How to provide a dynamic navigation bar.
The method of claim 1,
Allowing a display of additional content in the preview window via a scroll function;
How to provide a dynamic navigation bar.
The method of claim 1,
At least one of the set of size, layout, position, and content of the preview window is dynamically adjustable, fixed, or user configurable
How to provide a dynamic navigation bar.
A computing device that provides a dynamic navigation bar for docking and undocking preview windows in scalable communications applications.
Input device,
With memory,
At least one processor coupled to the memory and the input device, the at least one processor executing the communication application and causing a user interface associated with the communication application to be displayed on a screen;
The at least one processor
Within the user interface of the communication application a plurality of items representing a respective module of the communication application, the module associated with at least one of a set consisting of email exchange, scheduling, text messaging, contact management, and task management. Displaying the navigation bar,
In response to detecting a hover action on a navigation bar item,
Determine whether a preview window associated with the module represented by the navigation bar item is active based on the context of the current view of the user interface, wherein the preview window is configured to indicate that another module represented by another navigation bar item Activated when displayed in the current view,
In response to determining that the preview window is active, temporarily display the preview window presenting content associated with the module concurrently with a current view of the user interface presenting content associated with the other module,
In response to receiving the docking request, dock the preview window at one of a predefined location and a dynamically determined location on the user interface for permanent display,
In response to detecting that the module is displayed in the current view of the user interface, automatically undocking the preview window from the user interface.
Computing device configured.
The method of claim 12,
The at least one processor is further configured to adjust at least one of the set of size, layout, position, and content of the preview window in response to docking of the preview window.
Computing device.
The method of claim 12,
The at least one processor is further configured to allow manual adjustment of the position of the docked preview window.
Computing device.
The method of claim 12,
The at least one processor is further configured to allow docking of the preview window via activation of a first control element presented in the temporarily displayed preview window.
Computing device.
The method of claim 15,
Undocking of the docked preview window is permitted through activation of one of the first and second control elements presented in the docked preview window.
Computing device.
The method of claim 12,
The communication application is provided as one of a web-based application in a server-client architecture, a cloud-based hosted application, and a locally installed application,
The computing device is one of a fixed computer, a laptop computer, a vehicle-mounted computer, a handheld computer, a consumer electronic device, a PDA, a smartphone, a handheld game console, and a computer peripheral
Computing device.
A computer readable memory device having instructions stored therein for performing a method for providing a dynamic navigation bar having preview docking and undocking functionality in an extended communications application.
The method,
Displaying the navigation bar including a plurality of items representing individual modules of the communication application in a user interface of the communication application, wherein the items in the navigation bar are one or more of text, graphics, images, and combinations of text and graphics. Contains-W,
In response to detecting a hover action on a navigation bar item,
Determine whether a preview window associated with the module represented by the navigation bar item is active based on the context of a current view of the user interface, wherein the preview window is further configured to indicate that another module represented by another navigation bar item is selected from the user interface; Is active when displayed in the current view,
In response to determining that the preview window is active, temporarily displaying the preview window presenting content associated with the module concurrently with the current view of the user interface presenting content associated with the other module-the preview window and the The format of the current view is different-
Allow interaction with the presented content associated with the module via the temporarily displayed preview window, wherein the presented content associated with the module includes one or more items, wherein the interaction opens, marks the one or more items. Doing and deleting, and creating a new item-
In response to receiving the docking request, docking the preview window at one of a predefined location and a dynamically determined location on the user interface for permanent display;
In response to detecting that the module is displayed in the current view of the user interface, automatically undocking the preview window from the user interface;
In response to detecting the selection of the navigation bar item, modifying the user interface to display the module represented by the navigation bar item in a current view of the user interface.
Computer-readable memory device comprising a.
The method of claim 18,
The method includes layout, color, and shading in relation to displaying and docking the preview window such that a consistent look and feel is provided across different applications and devices associated with a user. further using one or more of a scheme, a textual scheme, a graphical scheme, and an animation scheme.
Computer-readable memory device.

Images