JP2017537373A - Contextual tab in the mobile ribbon - Google Patents

Abstract

Disclosed herein are systems, methods, and software that enhance the content display experience on computing devices. In one embodiment, the application presents a user interface that includes a canvas and navigation elements. When selected, this navigation element surfaces a navigation menu that includes various menu elements that can be selected to navigate to the corresponding mechanism menu. The application monitors for activity in the user interface that affects the presence of the context menu element for navigating to the context mechanism menu within the menu element. When that activity occurs, the application modifies the appearance of the navigation element to indicate the presence of the context menu element. [Selection] Figure 1

Description

 [0001] One feature found in some document productivity applications is the ribbon tool bar. The ribbon toolbar provides the user with access to many features and functions of the application. In some cases, this ribbon is contextual in that the mechanism found under a given tab in the ribbon may change based on context.

[0002] In the desktop computing space, most if not all tabs in the ribbon are immediately visible to the user. In mobile spaces where smaller form factors dominate, sometimes the tabs on the ribbon can be immediately displayed due to the limited visual space available on smaller form factor screens. is not.

[0003] Although systems, methods, and software are provided herein that enhance the user interface experience on computing devices that have a small form factor compared to larger devices, such enhancements are Applicable to any form factor device. In one embodiment, the application surfaces a bump animation to indicate the presence of a contextual tab in the ribbon. The ribbon represents a navigation menu, while the bump animation represents a modification to the appearance of the navigation element.

[0004] In addition, when any tab that is contextual is selected, the application surfaces other bump animations to indicate that the tab is contextual. Thus, the end user may be aware that a contextual tab exists in the ribbon, and once one is selected, the user will remember that it is contextual.

[0005] In at least one other embodiment, an application presents a user interface that includes a canvas and navigation elements. When selected, the navigation element surfaces a navigation menu that includes various menu elements that can be selected to navigate to the corresponding feature menu. The application monitors for activities in the user interface that affect the presence of contextual menu elements for navigating to the context mechanism menu within the menu element. As activity occurs, the application modifies the appearance of the navigation element to indicate the presence of the context menu element.

[0006] This summary is provided to introduce a selection of concepts in a simplified format that are further described below in the technical disclosure. It should be understood that this summary is not intended to identify key or essential features of the claimed subject matter, nor is it intended to be used to limit the scope of the claimed subject matter. I will.

[0007] Many aspects of the invention can be better understood with reference to the following drawings. Although some embodiments have been described with reference to these drawings, the invention is not limited to the embodiments disclosed herein. Rather, the intent is to cover all alternatives, modifications, and equivalents.

[0008] FIG. 2 illustrates an enhanced user interface technology used in one embodiment to provide various displays of a user interface. [0009] FIG. 3 illustrates a user interface process in one embodiment. [0010] FIG. 4 illustrates various user interface progressions in one embodiment of enhanced user interface technology. [0010] FIG. 6 illustrates various user interface progress in one embodiment of enhanced user interface technology. [0010] FIG. 6 illustrates various user interface progress in one embodiment of enhanced user interface technology. [0011] FIG. 6 illustrates user interface progress in one embodiment of enhanced user interface technology. [0012] FIG. 5 illustrates various user interface progress in one embodiment of enhanced user interface technology. [0012] FIG. 5 illustrates various user interface progress in one embodiment of enhanced user interface technology. [0012] FIG. 5 illustrates various user interface progress in one embodiment of enhanced user interface technology. [0013] FIG. 6 illustrates user interface progress in one embodiment. [0014] Figure 5 illustrates a user interface process in one embodiment. [0015] A computing system suitable for implementing any of the applications, architectures, services, processes, and operational scenarios disclosed herein with respect to FIGS. 1-8 and described below in the technical disclosure. Is shown.

[0016] The embodiments disclosed herein illustrate various user interfaces in which a user is warned about the presence of a context menu item that is outside the screen by changing the appearance of elements on the screen. The appearance of the elements is a way to alert the user, but can be changed in a sufficiently clever way to avoid diversion.

[0017] In one example, a home button is displayed in the user interface that, when selected, leads to a home menu from which the user can navigate to other submenus. If an activity is performed in the user interface that affects the presence of a contextual tab in the home menu, the home button will notify you of this change, even if the home menu may still not be visible in the user interface. The appearance of is corrected. The bump animation informs the user that a context menu is available and can be reached via the home button.

[0018] The context menu element is an element whose presence in the menu depends on the operating context when the user navigates to the menu. A non-context menu is an element whose presence in the menu does not depend on the surrounding context.

[0019] The table tab in the ribbon toolbar that leads to the control for formatting the table is a context menu item because its presence in the menu depends on whether the table is selected in the user interface. It is an example. The home tab in the ribbon toolbar is an example of a non-context menu item because its presence does not depend on the surrounding context. Other types or styles of toolbars in addition to or other than ribbon toolbars, such as classic style toolbars, can be considered within the scope of the present invention.

[0020] FIG. 1 illustrates one embodiment 100 of an enhanced user interface technology. Embodiment 100 includes a computing system 101. Application 103 resides on computing system 101 and is executed to provide user interface 105.

[0021] Computing system 101 represents any physical or virtual computing system, device, or collection thereof that can act as a host for application 103 and implement user interface process 200. Examples of the computing system 101 include a smartphone, a laptop computer, a tablet computer, a desktop computer, a hybrid computer, a gaming machine, a smart television, a virtual computer, and a wearable device represented by the computing system 801 in FIG. Including, but not limited to, any modification or combination.

[0022] Application 103 represents any software application that presents user interface 105 and can use user interface process 200. The application 103 may be a stand-alone application or may be realized in a distributed manner as a plurality of applications. In addition, the application 103 can be a natively installed application, a browser-based application that runs in connection with a browser, a streaming application, or any other type of application, including any combination or variation thereof. can do. Examples include, but are not limited to, productivity applications such as games, media players, app store applications, browsers, and word processing, spreadsheets, document editing, and presentation applications.

[0023] User interface process 200 represents any component, module, or other logic used to cause various visual progress within user interface 105. FIG. 2 illustrates functional steps that may be performed by the application 103 (or any application) when executing the user interface process 200.

[0024] Referring episodicly to the steps shown in FIG. 2, an application using the user interface process 200 will present a user interface that includes a canvas and navigation elements (step 201). The application will also monitor user activity performed within the user interface for any activity that may affect the presence (or lack thereof) of context menu elements in off-screen navigation menus (steps). 203).

[0025] When such activity is detected (step 205), the application will modify the appearance of the navigation element in the user interface to indicate the presence of the context menu element in the navigation menu (step 205). 207). If no such activity is detected, the application will continue its monitoring.

[0026] In some embodiments, the detected activity may be followed by other activities that reverse the state of the context menu element. In other words, some activities result in the presence of a context menu element in the navigation menu, and other activities that follow that activity remove the context menu element from the navigation menu. If such other activities occur, the navigation element may be modified again to indicate that the context menu element is no longer included in the navigation menu. For example, the appearance of the navigation element can be restored to its previous state.

[0027] Referring back to FIG. 1, various progress in the user interface 105 is shown to demonstrate an instance of the user interface process 200 used by the application 103 when providing the user interface 105. In its initial state 120, the user interface 105 includes a canvas 107 and a navigation element 109. The user interface 105 also includes content 111 provided on the canvas 107, which in this case is an image. Application 103 monitors user activity in user interface 105 to trigger the activity as described above.

[0028] The state of the user interface 105 proceeds from the initial state 120 to the state 121 when the user activity 113 is performed. User activity 113 in this progress is the selection of navigation element 109 such as a mouse click, touch, voice command, or some other user input. User activity 113 causes another state change in user interface 105 to state 123. However, the user activity in this progress is not an activity that results in the presence of a context menu element in the navigation menu, so the appearance of the navigation element 109 is not modified. Rather, in state 123, the navigation menu 112 that includes various menu elements represented by menu element 115 and menu element 117 is surfaced. Menu element 115 and menu element 117 can each be selected to navigate to a corresponding mechanism menu (not shown) that includes various mechanism controls.

[0029] Although different progress situations may occur, the progress situation also begins with the user interface 105 in its initial state 120. However, instead of performing user activity 113, user interface 105 proceeds to a state 125 where user activity 114 representing an activity that changes the presence of a context menu element in navigation menu 112 is performed. In this example, user activity 114 is the selection of content 111 that can be achieved by touch, mouse clicks, verbal commands, and the like. Selection of content 111 represents an activity that results in the presence of a context menu element in navigation menu 112.

[0030] Accordingly, the user interface 105 proceeds to another state 127 where the appearance of the navigation element 109 is modified compared to its appearance in state 125. Changes in appearance are represented by changes in the fill pattern of the navigation element 109, but many types of modifications are possible. For example, the size, shape, or color of the navigation element 109 may change, an audible sound may be emitted, or the arrangement of the navigation element 109 in the user interface 105 may change. is there. In one example, the navigation element 109 is animated to draw the user's attention to the change, thereby notifying the user that a context menu element is available.

In this progress situation, the navigation element 109 is selected by a user activity 116 that causes a state change in the user interface 105 to the state 129. In state 129, navigation menu 112 is surfaced with context menu element 119 present therein. In addition, the context menu element 119 is surfaced within the navigation menu 112 in such a way that it is distinguishable from the menu element 115 and the menu element 117. For example, context menu element 119 may be surfaced with a different color, shape, size, or fill pattern than that of menu element 115 or menu element 117.

[0032] FIG. 3A illustrates another user interface progress status 300A in one embodiment. In the user interface 300A, the user interface 301 includes a canvas 303, a mechanism menu 307, and a navigation element 309. The canvas 303 includes content 305 that has already been created.

[0033] In operation, a user activity 311 is performed that qualifies as an activity that triggers the presence of a context menu element in the navigation menu. The appearance of the navigation element 309 is modified in response to the activity in a manner that draws attention to the element. In this progress example, a shift 313 of the navigation element 309 is achieved in the horizontal direction, followed by a reverse shift 315 in the opposite direction. The combination of shift 313 and reverse shift 315 can give a visual impression that the navigation element 309 pops out of the user interface 301 if performed quickly enough.

[0034] In addition to this bump-out animation, a static modification represented by a solid dot provided when the navigation element 309 is shifted horizontally in one direction or vice versa is a navigation element. 309 may be performed. This dot provides the user with an additional visual clue that there is a context menu element in the navigation menu accessible via the navigation element 309.

FIG. 3B shows another user interface progress status 300B. The user interface progress 300B may be a continuation of the user interface progress 300A, but in some scenarios arise from other progresses that result in the presence of a context menu element in the navigation menu. there is a possibility.

[0036] In operation, a selection 317 regarding the navigation element 309 is made. Selection of the navigation element 309 results in the navigation menu 319 appearing with various menu elements included therein, as well as at least one context menu element. This menu element is represented by a menu element 321, a menu element 323, a menu element 325, and a menu element 327. The context menu element is represented by a context menu element 329. In some, but not all, context menu elements 329 may be provided with an appearance that distinguishes it from other menu elements.

FIG. 3C shows a user interface progress status 300C. The user interface progress 300C may also be a continuation of the user interface progress 300B, but in some scenarios it may continue from other progress.

[0038] In operation, the navigation menu 319 is provided as a result of the user selecting the navigation element 309 when a context menu element is present in the navigation menu 319. A selection 331 regarding the context menu element 329 is made. In response, the user interface 301 transitions to a state that includes a mechanism menu 333 corresponding to the context menu element 329. If a different one of the elements in the navigation menu 319 is selected, the user interface 301 will transition to the mechanism menu corresponding to that element.

[0039] The mechanism menu 333 includes various control elements that allow a user to apply application mechanisms and controls, at least one of which may be a context mechanism element. Control element 337 and control element 339 represent such elements. A context mechanism element is an element that is not present in the other state in the mechanism menu, is not usable, or is not considered usable in other states, depending on the context or state of the application. The mechanism menu also includes a navigation element 335. When the navigation element 335 is selected, the navigation menu 319 is surfaced.

FIG. 4 illustrates yet another user interface progress status 400 in one embodiment. In operation, the user interface 301 is in a state that represents a state that may occur after an activity has been performed that causes a context menu element to be present in the navigation menu. Such a state is represented by italic font content 305 as well as the presence of visual dots in the navigation element 309. In other words, the user interface is in a state similar to the initial state of the user interface 301 of FIG. 3B.

[0041] User activities 341 are performed in the user interface 301 that do not affect the presence (or lack thereof) of context menu elements in the navigation menu. In practice, user activity 341 may occur following the triggering of the activity, so that the context menu element is no longer usable from the state that the context menu element is available off the screen. There is a possibility of changing the state of the user interface 301 to the state.

[0042] To indicate a change in state, the content 305 is changed from italic to non-italic. As an example, a selection 343 regarding the navigation element 309 is made in the user interface progress 400. Selection 343 advances user interface 301 to a new state where navigation menu 319 is surfaced again. However, in this state, no context menu element exists in the navigation menu 319. This is due to the state or context of the user interface 301 when the selection 343 is made.

FIG. 5A shows a user interface progress status 500 A regarding the user interface 501. A user interface 501 represents a user interface that may be generated by an application such as a productivity application or an email application. The user interface 501 includes a canvas 503 on which content is displayed. This content includes a table 505 and text. The user interface 501 also includes a mechanism menu 507.

[0044] The mechanism menu 507 includes various controls with which the user can interact to format the text in the canvas 503. A home button 509 is also included in the mechanism menu 507, which represents a navigation element for navigation to the navigation menu.

In operation, the application providing the user interface 501 monitors user activity for any activity that may affect the presence of a context menu item in the navigation menu accessed by the home button 509. An example of such a trigger activity is a selection 511 made with respect to table 505. Selection 511 in table 505 changes the visual appearance of table 505 so that the user knows that it has been selected.

[0046] The appearance of home button 509 also changes to alert the user about the presence of a context menu item. The context menu item exists in the navigation menu outside the screen because the table 505 has been selected. Selecting a context menu from the navigation screen will lead the user to a mechanism menu specific to the table. The change in appearance with respect to the home button 509 is represented by dots positioned between the vertical arrows in the home button 509. This dot is a visual clue to the user that the navigation menu accessed via the home button 509 includes a context menu element.

[0047] FIG. 5B illustrates a user interface progress 500B that may be encountered after a context menu element is available in the navigation element. In operation, the home button 509 is displayed in its changed state. A selection 513 regarding the home button 509 is made, and as a result, the user interface 301 advances to a state where the ribbon toolbar 515 is surfaced.

[0048] Ribbon toolbar 515 includes various menu elements and a context menu element represented by a button labeled "Table". The front button is displayed with an appearance that distinguishes it from the other buttons in the ribbon toolbar 515. In this example, the presence of the pattern fill and dot alerts the user about the presence of the context menu item. It also notifies the user that selecting a table button will lead to controls and other tools specific to the table selected on the canvas. It can be appreciated that the ribbon toolbar 515 is just one example of a navigation menu.

FIG. 5C shows a user interface progress status 500C that may be performed following the user interface progress status 500B. In the user interface progress status 500 </ b> C, the user selects a table button 521 in the ribbon toolbar 515. Selection 521 causes a change in state of user interface 501, thereby replacing mechanism menu 507 with mechanism menu 527 corresponding to the table button. Mechanism menu 527 includes various controls and other mechanisms for controlling the features of table 505. Note also that the front button in feature menu 527 also includes a dot between vertical arrows to mean that a context feature is available in this menu.

[0050] The user interface progress 600 shown in FIG. 6 represents a progress that may occur when user activity does not trigger the presence of a context menu item in the navigation menu. In the user interface progress status 600, the table 505 is not selected. Rather, a selection 541 regarding the home button 509 is made. Selection of the home button 509 brings up the ribbon toolbar 515. In this state, the ribbon toolbar includes various buttons corresponding to the mechanism menu, but does not include a context menu element.

[0051] FIG. 7 illustrates a user interface process 700 in one embodiment. User interface process 700 can be used by a productivity application when providing a display for a document.

[0052] In operation, the application monitors for when the contextual tab is visible in the ribbon (step 701). When the contextual tab is visible, the application surfaces or provides a bump or animation visually associated with the contextual tab (step 703). When that context tab or other context tab is selected, other bumps or other such identifiers are surfaced in a sub-menu for that tab that is visually related to the name of the tab (step 705).

[0053] A technical effect that can be recognized from the above description is an improved user experience when interacting with ribbon and tab menus on small form factor devices compared to desktop and laptop computers. For example, a user engaged in a productivity application on a mobile phone, tablet, or fablet is warned about the presence of a contextual tab in the toolbar menu, even if the menu is not yet visible to the user. The user recalls its presence when displaying the toolbar menu. This can increase the speed at which the user navigates within the user interface and can reduce navigation errors or other obstacles that the user encounters.

[0054] FIG. 8 illustrates a computing system 801 that represents any system or collection of systems capable of implementing the various operational architectures, scenarios, and processes disclosed herein. Examples of computing system 801 include smartphones, laptop computers, tablet computers, desktop computers, hybrid computers, gaming machines, virtual machines, smart televisions, smart watches, and other wearable devices, and any variations thereof. Or, including, but not limited to, combinations. Other examples include server computers, rack servers, web servers, cloud computing platforms, and data center equipment, any other type of physical or virtual server machines, and any variations or combinations thereof, A type of computer may be involved in the process.

[0055] The computing system 801 may be implemented as a single device, system, or device, or may be implemented in a distributed fashion as multiple devices, systems, or devices. The computing system 801 includes, but is not limited to, a processing system 802, a storage system 803, software 805, a communication interface system 807, and a user interface system 809. Processing system 802 is operatively coupled to storage system 803, communication interface system 807, and user interface system 809.

The processing system 802 loads and executes software 805 from the storage system 803. The software 805 includes an application 811 and an operating system 813. Application 811 includes a user interface process 815. Application 811 represents the application described with respect to FIGS. User interface process 815 includes processes implemented in user interface process 200, user interface process 700, and user interface progress 300A, 300B, 300C, 400, 500A, 500B, 500C, and 600. Represents the process described with respect to When executed by processing system 802 to enhance user interface technology, software 805 may at least as described herein for various processes, operating scenarios, and sequences described in the above embodiments. Instructs processing system 802 to operate. The computing system 801 may optionally include additional devices, features, or functions that are not mentioned for brevity.

[0057] In at least one embodiment, the application 811 provides a bump animation for the navigation element by repeatedly changing the parameters of the navigation element. This may be done, for example, by making repeated calls to the operating system 813 to change the horizontal position of the navigation element. The operating system 813 receives the parameter change and shifts the horizontal position of the navigation element back and forth to give a visual bumpout effect. Other mechanisms that affect bump animation are possible and can be considered within the scope of the present invention.

Still referring to FIG. 8, the processing system 802 can include a microprocessor and other circuitry that retrieves and executes software 805 from the storage system 803. The processing system 802 can be implemented within a single processing device, but can also be distributed among multiple processing devices or subsystems that cooperate in executing program instructions. Examples of processing system 802 include general purpose central processing units, application specific processors, logic elements, any other type of processing unit, and combinations or variations thereof.

[0059] The storage system 803 may include any computer-readable storage medium readable by the processing system 802 and capable of storing software 805. Storage system 803 implements volatile and non-volatile removable and non-removable media implemented in any method or technique for storage of information such as computer readable instructions, data structures, program modules, or other data. Can be included. Examples of storage media include random access memory, read-only memory, magnetic disk, optical disk, flash memory, virtual memory and non-virtual memory, magnetic cassette, magnetic tape, magnetic disk storage device or other magnetic storage device, or any Including other suitable storage media. In either case, the computer readable storage medium is not a propagated signal.

[0060] In addition to computer-readable storage media, in some embodiments, storage system 803 may also include computer-readable communication media with which at least a portion of software 805 can be communicated internally or externally. it can. Storage system 803 can be implemented as a single storage device, but can also be implemented between multiple storage devices or subsystems that are co-located or distributed with respect to each other. The storage system 803 may include additional elements such as a controller that can communicate with the processing system 802 or possibly other systems.

[0061] The software 805 can be implemented with program instructions, and in terms of various functions scenarios, sequences, and processes shown herein when executed by the processing system 802, among other functions. Processing system 802 can be instructed to operate as described. For example, software 805 can include program instructions for implementing enhanced ribbon animation and related functions.

[0062] In particular, program instructions may include various components or modules that cooperate or otherwise interact to perform the various processes and operational scenarios described herein. . Various components or modules may be implemented with compiled or interpreted instructions or with some other variation or combination of instructions. The various components or modules can execute in a synchronous or asynchronous manner, serially or in parallel, in a single thread environment or multithread, or according to any other suitable execution paradigm or variation or combination thereof. . Software 805 can include additional processes, programs, or components in addition to or including user interface process 815. The software 805 can also include firmware executable by the processing system 802 or some other form of machine-readable processing instructions.

[0063] In general, software 805, when loaded and executed within processing system 802, removes the appropriate apparatus, system, or device (represented by computing system 801) generally from a general purpose computing system. , Can be converted to a dedicated computing system customized to facilitate enhanced user interface technologies such as enhanced ribbon animation. In fact, when the software 805 on the storage system 803 is encoded, the physical structure of the storage system 803 can be converted. The specific transformation of the physical structure may depend on various factors in the various embodiments herein. Examples of such factors include the technology used to implement the storage medium of storage system 803, whether the computer storage medium is characterized as primary storage or secondary storage, and other factors. It is possible to include, but is not limited to these.

[0064] For example, if the computer-readable storage medium is realized as a semiconductor-based memory, the software 805 may change the program instructions by converting the states of transistors, capacitors, or other discrete circuit elements that constitute the semiconductor memory. Can be transformed into the physical state of the semiconductor memory. Similar conversions can be made for magnetic or optical media. Other transformations of the physical medium are possible without departing from the scope of the present specification, and the above examples are provided only to facilitate this discussion.

[0065] Computing system 801 typically has one or more computing systems on which software 805 can be deployed and executed to implement enhanced user interface technologies, such as enhanced ribbon animation. Can be understood to represent However, the computing system 801 can stage software 805 thereon from which software can be distributed, transported, downloaded from there for further deployment and execution, or for further distribution. Or any other computing system that can be provided in other ways.

[0066] The communication interface system 807 can include communication connections and devices that allow communication with other computing systems (not shown) over a communication network (not shown). Examples of connections and devices that together enable inter-system communication can include network interface cards, antennas, power amplifiers, RF circuits, transceivers, and other communication circuits. The connections and devices can communicate via a communication medium for exchanging communication with other computing systems or system networks, such as metal, glass, air, or any other suitable communication medium. The above media, connections, and devices are well known and need not be discussed at length here.

[0067] A user interface system 809 includes a keyboard, a mouse, a voice input device, a touch input device for receiving touch gestures from a user, a motion input device for detecting non-touch gestures and other motion by a user, and from a user. Other comparable input devices and associated processing elements that can receive user input can be included. Output devices such as displays, speakers, haptic devices, and other types of output devices can also be included in the user interface system 809. In some cases, an input device and an output device can be combined into a single device such as a display that can display images and receive touch gestures. The above user input and output devices are well known in the art and need not be discussed at length here.

[0068] The user interface system 809 may also include associated user interface software that can be executed by the processing system 802 in support of the various user input and output devices described above. User interface software and user interface devices present user interface progress as described herein with respect to user interface 105, user interface 301, and user interface 501 separately or together with each other and other hardware and software elements. Can support a graphical user interface, a natural user interface, or any other type of user interface.

[0069] Communication between computing system 801 and other computing systems (not shown) may be performed by one or more communication networks according to various communication protocols, combinations of protocols, or variations thereof. . Examples include intranet, internetwork network, internet, local area network, wide area network, wireless network, wired network, virtual network, software defined network, data center bus, computing backplane, or any other type Includes networks, combinations of networks, or variations thereof. The above communication networks and protocols are well known and need not be discussed in detail here. However, some communication protocols that can be used include Internet protocols (IP, IPv4, IPv6, etc.), Transfer Control Protocol (TCP), and User Datagram Protocol (UDP), as well as any other suitable communication protocol, such as Including, but not limited to, variations or combinations.

[0070] In any of the above examples where data, content, or any other type of information is exchanged, the exchange of information can be FTP (File Transfer Protocol), HTTP (Hypertext Transfer Protocol), REST (Representation State). Transfer), web socket, DOM (document object model), HTML (hypertext markup language), CSS (chained style sheet), HTML5, XML (extensible markup language), JavaScript, JSON (JavaScript object notation), And AJAX (asynchronous JavaScript and XML), and any other suitable protocol, variations or combinations thereof, can be performed according to any of a variety of protocols.

[0071] Although FIGS. 1-8 generally depict relatively few users and relatively few instances of service platforms, application platforms, applications, and services, the concepts disclosed herein are of a certain scale. It can be recognized that this is applicable. For example, the ribbon process disclosed herein can be deployed in support of any number of devices, users, data, applications, and instances thereof.

[0072] Certain aspects of the invention can be appreciated from the above disclosure, and various examples thereof are as follows.

[0073] Example 1. One or more computer-readable storage media and program instructions stored on the one or more computer-readable storage media, when executed by a processing system, at least a canvas; Presenting a user interface to the application that includes a navigation element that surfaces a navigation menu that includes a plurality of menu elements that are selectable to navigate to a plurality of mechanism menus when selected; and the plurality of menu elements Monitoring for activities that affect the presence of a context menu element for navigating to a context mechanism menu within the appearance of the navigation element to indicate the presence of the context menu element when the activity is performed Fix Device including program instructions to instruct the Rukoto, to the processing system, the.

[0074] Example 2. The program instructions presenting the navigation menu in the user interface in response to selection of the navigation element when the context menu element is in the navigation menu; and the context menu element and the plurality of The apparatus of embodiment 1, further instructing the processing system to modify the appearance of the context menu element to visually distinguish it from other menu elements within the menu element.

[0075] Example 3. The program instruction presents the context mechanism menu in response to the selection of the context menu element and the appearance of other navigation elements in the context mechanism menu to visually represent the presence of the context controller The apparatus of Embodiments 1 and 2 instructing the processing system to correct the data.

[0076] Example 4. Further including the processing system for executing the program instructions, the navigation menu including a ribbon toolbar, wherein each of the plurality of menu elements navigates to a corresponding one of the plurality of mechanism menus. The apparatus of Examples 1-3, including selectable graphical tabs.

[0077] Example 5. In order to modify the appearance of the navigation element, the program instructions include shifting the navigation element horizontally from an initial position in the user interface and returning the navigation element to the initial position. The apparatus of Examples 1-4 which directs the system.

[0078] Example 6. In order for the program instructions to include the application, shift the navigation element horizontally from the initial position in the user interface, and return the navigation element to the initial position, the application An example in which a plurality of calls are made to instruct the processing system to shift the horizontal display parameter of the navigation element from the initial value to the next value and to return the horizontal display parameter to the initial value. 1-5 devices.

[0079] Example 7. The apparatus of Examples 1-6, wherein the program instructions further direct the processing system to surface an instance of a symbol in the navigation element to modify the appearance of the navigation element.

[0080] Example 8. In order to modify the appearance of the context menu to visually distinguish the context menu element from other menu elements in the plurality of menu elements, the program instructions The apparatus of Examples 1-7, instructing the processing system to surface another instance.

[0081] Example 9. One or more computer-readable storage media and program instructions stored on the one or more computer-readable storage media, when executed by a processing system, at least within the ribbon Surface a bump animation to indicate the presence of a contextual tab, and when a tab that is contextual is selected, surface another bump animation to indicate that the tab is contextual And a program instruction including an application for instructing the processing system.

[0082] Example 10. The apparatus of example 9, further comprising the processing system operably coupled to the one or more computer-readable storage media for reading and executing the program instructions, wherein the application includes a document productivity application.

[0083] Example 11. Embodiments 9-10 further instruct the processing system to surface the context tab in the ribbon in a manner that distinguishes the context tab from other non-context tabs in the ribbon. apparatus.

[0084] Example 12. Example 9 wherein the program instructions further instruct the processing system to monitor for activities performed in the user interface for the application that trigger the presence of the contextual tab in the ribbon. ~ 11 devices.

[0085] Example 13. A method for enhancing a user interface for an application, comprising: a canvas and a navigation element that surfaces a navigation menu that includes a plurality of menu elements that can be selected to navigate to multiple mechanism menus when selected. Presenting a user interface to the application, monitoring for activities that affect the presence of a context menu element for navigating to a context mechanism menu within the plurality of menu elements, and performing the activity Modifying the appearance of the navigation element to indicate the presence of the context menu element.

[0086] Example 14. The program instructions presenting the navigation menu in the user interface in response to selection of the navigation element when the context menu element is in the navigation menu; and the context menu element and the plurality of The method of example 13, further instructing the processing system to modify the appearance of the context menu element to visually distinguish it from other menu elements in the menu element.

[0087] Example 15. Example 13 presenting the context mechanism menu in response to selection of the context menu element and modifying the appearance of other navigation elements in the context mechanism menu to visually represent the presence of the context controller ~ 14 methods.

[0088] Example 16. Examples 13-15 wherein the navigation menu includes a ribbon toolbar, and each of the plurality of menu elements includes a graphical tab that is selectable to navigate to a corresponding one of the plurality of mechanism menus. the method of.

[0089] Example 17. Examples 13-16, wherein modifying the appearance of the navigation element includes shifting the navigation element horizontally from an initial position in the user interface and returning the navigation element to the initial position. the method of.

[0090] Example 18. Shifting the navigation element horizontally from the initial position in the user interface and returning the navigation element to the initial position causes the application to make a call to an operating system component to The method of Examples 13-17, including shifting the display parameter from the initial value to the next value and returning the horizontal display parameter to the initial value.

[0091] Example 19. The method of embodiments 13-18, wherein modifying the appearance of the navigation element further comprises surfacing an instance of a symbol in the navigation element.

[0092] Example 20. Modifying the appearance of the context menu to visually distinguish the context menu element from other menu elements in the menu elements surface other instances of the symbol in the context menu element The method of Examples 13-19, comprising:

[0093] The functional block diagrams, operating scenarios and sequences, and flow diagrams provided in the drawings represent exemplary systems, environments, and methods for carrying out the novel aspects of the present invention. For simplicity of explanation, the methods included herein can be in the form of functional diagrams, operational scenarios or sequences, or flow diagrams, and can be described as a series of actions, It is understood that this method is not limited by the order of actions, since actions may be performed in a different order and / or concurrently with other actions accordingly than shown and described herein. Should be recognized. For example, those skilled in the art will understand and appreciate that a methodology could alternatively be represented as a series of interrelated states or events, such as in a state diagram. Moreover, not all acts illustrated in one method may be required in one novel embodiment.

[0094] The description and drawings contained herein depict specific embodiments to teach those skilled in the art how to make and use the best choice. For the purpose of teaching inventive principles, some conventional aspects have been simplified or omitted. Those skilled in the art will appreciate variations from these embodiments that fall within the scope of the invention. Those skilled in the art will also recognize that the features described above can be combined in various ways to form multiple embodiments. As a result, the invention is not limited to the specific embodiments described above, but only by the claims and their equivalents.

Claims (15)

One or more computer-readable storage media;
Program instructions stored on the one or more computer-readable storage media when executed by a processing system, at least
Presenting a user interface to the application that includes a canvas and a navigation element that, when selected, surfaces a navigation menu that includes a plurality of menu elements that can be selected to navigate to a plurality of mechanism menus;
Monitoring for activities that affect the presence of a context menu element for navigating to a context mechanism menu within the plurality of menu elements;
Modifying the appearance of the navigation element to indicate the presence of the context menu element when the activity is performed;
A program instruction for instructing the processing system
Including the device. The program instructions are
Presenting the navigation menu in the user interface in response to selection of the navigation element when the context menu element is present in the navigation menu;
Modifying the appearance of the context menu element to visually distinguish the context menu element from other menu elements in the plurality of menu elements;
The apparatus of claim 1 further instructing the processing system. The program instructions are
Presenting the context mechanism menu in response to the selection of the context menu element;
Modifying the appearance of other navigation elements in the context mechanism menu to visually represent the presence of a context controller;
3. The apparatus of claim 2, wherein the apparatus is directed to the processing system. Further comprising the processing system for executing the program instructions;
The navigation menu includes a ribbon toolbar;
The apparatus of claim 2, wherein each of the plurality of menu elements includes a graphical tab selectable for navigating to a corresponding one of the plurality of mechanism menus. In order to modify the appearance of the navigation element, the program instructions
Shifting the navigation element horizontally from an initial position in the user interface;
Returning the navigation element to the initial position;
5. The apparatus of claim 4, wherein the apparatus is directed to the processing system. The program instructions include the application;
In order to shift the navigation element horizontally from the initial position in the user interface and return the navigation element to the initial position, the application makes multiple calls to an operating system component to Shifting the horizontal display parameter from the initial value to the next value,
Returning the horizontal display parameter to the initial value;
6. The apparatus of claim 5, wherein the apparatus is directed to the processing system. In order to modify the appearance of the navigation element, the program instructions
The apparatus of claim 5, further instructing the processing system to surface an instance of a symbol in the navigation element. In order to modify the appearance of the context menu to visually distinguish the context menu element from other menu elements in the plurality of menu elements, the program instructions include:
8. The apparatus of claim 7, instructing the processing system to surface another instance of the symbol in the context menu element. One or more computer-readable storage media;
Program instructions stored on the one or more computer-readable storage media when executed by a processing system, at least
Surface the bump animation to indicate the presence of a contextual tab in the ribbon,
Surface another bump animation to indicate that the tab is contextual when a contextual tab is selected;
Program instructions including an application for instructing the processing system
Including the device. Further comprising the processing system operably coupled to the one or more computer-readable storage media for reading and executing the program instructions;
The apparatus of claim 9, wherein the application comprises a document productivity application. The program instructions are
The apparatus of claim 9, further instructing the processing system to surface the contextual tab in the ribbon in a manner that distinguishes the contextual tab from other non-contextual tabs in the ribbon. The program instructions are
The apparatus of claim 9, further instructing the processing system to monitor for activities performed in a user interface for the application that trigger the presence of the contextual tab in the ribbon. A method for enhancing the user interface to an application,
Presenting a user interface to the application that includes a canvas and a navigation element that, when selected, surfaces a navigation menu that includes a plurality of menu elements that can be selected to navigate to a plurality of mechanism menus;
Monitoring for activities that affect the presence of a context menu element for navigating to a context mechanism menu within the plurality of menu elements;
Modifying the appearance of the navigation element to indicate the presence of the context menu element when the activity is performed;
Including a method. The program instructions are
Presenting the navigation menu in the user interface in response to selection of the navigation element when the context menu element is present in the navigation menu;
Modifying the appearance of the context menu element to visually distinguish the context menu element from other menu elements in the plurality of menu elements;
14. The method of claim 13, further instructing the processing system. Responsive to the selection of the context menu element, presenting the context mechanism menu and modifying the appearance of other navigation elements in the context mechanism menu to visually represent the presence of a context controller;
The navigation menu includes a ribbon toolbar;
The method of claim 14, wherein each of the plurality of menu elements includes a graphical tab selectable for navigating to a corresponding one of the plurality of mechanism menus.