Interaction method and apparatus, device, and storage medium
By dividing regions in the application navigation bar, flexible switching between components and pages is solved, the problem of poor user experience in existing applications is solved, and the convenience and interactivity of the application are improved.
Patent Information
- Application Number
- PCT/CN2024/096862
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2023-06-02
- Filing Date
- 2024-05-31
- Publication Date
- 2024-12-05
AI Technical Summary
Existing applications do not support flexible switching when switching components or pages between users, resulting in poor user experience, especially in suite applications, where users need to start over from the component's homepage or switch outside the application, reducing convenience .
By dividing two sub-regions in the application's navigation bar, the first sub-regions present the entry control of the preset component, and the second sub-regions present the relevant access portal in response to the component's opening operation, allowing users to easily switch different components and page.
Improves user convenience in switching between different components and pages, improves user experience, supports flexible application interaction, and reduces the need to restart or switch to outside the application.
Smart Images

Figure CN2024096862_05122024_PF_FP_ABST
Abstract
Description
Interaction method, device, equipment and storage medium
[0001] This application claims priority to the Chinese invention patent application entitled “Interactive Method, Apparatus, Device and Storage Medium” filed on June 2, 2023, with application number 202310651348.6, the entire contents of which are incorporated by reference into this application. Technical Field
[0002] Example embodiments of the present disclosure generally relate to the field of computers, and more particularly, to interactive methods, apparatuses, devices, and computer-readable storage media. Background Art
[0003] With the development of information technology, various terminal devices can provide various services to people in work and life. For example, terminal devices can be deployed with applications that provide services. Terminal devices or their applications can provide users with various types of functions, such as social communication, calendar, weather query, etc., to assist users.
[0004] Some apps offer a single, specialized function, such as instant messaging apps providing social communication and instant messaging, calendar apps providing calendar services, and cloud document apps providing document collaboration services. Other apps offer multiple functions, such as office suites offering one or more of instant messaging, calendaring, tasks, audio and video conferencing, and cloud documents. Providing users with interactive methods within apps to better serve them is a technical challenge currently under exploration.
[0005] Summary of the Invention
[0006] In a first aspect of the present disclosure, an interaction method is provided. The method comprises: presenting, in a first sub-area of a navigation bar of an application, one or more entry controls corresponding to one or more preset components in the application; and in response to a preset open operation on the first component in the application, presenting, in a second sub-area of the navigation bar, a first access entry associated with the first component, the second sub-area being different from the first sub-area; wherein the first access entry comprises an entry to the first component or an entry to a first page in the first component.
[0007] In a second aspect of the present disclosure, an interactive device is provided. The device includes: a first presentation module configured to present, in a first sub-area of a navigation bar of an application, one or more entry controls corresponding to one or more preset components in the application; a second presentation module configured to present, in response to a preset open operation on the first component in the application, a first access entry associated with the first component in a second sub-area of the navigation bar, the second sub-area being different from the first sub-area; wherein the first access entry includes an entry to the first component or an entry to a first page in the first component.
[0008] In a third aspect of the present disclosure, an electronic device is provided. The device includes at least one processing unit; and at least one memory coupled to the at least one processing unit and storing instructions for execution by the at least one processing unit. When executed by the at least one processing unit, the instructions cause the device to perform the method of the first aspect.
[0009] In a fourth aspect of the present disclosure, a computer-readable storage medium is provided, wherein a computer program is stored on the computer-readable storage medium, and the computer program can be executed by a processor to implement the method of the first aspect.
[0010] It should be understood that the content described in this summary section is not intended to limit the key features or important features of the embodiments of the present disclosure, nor is it intended to limit the scope of the present disclosure. Other features of the present disclosure will become easily understood through the following description. BRIEF DESCRIPTION OF THE DRAWINGS
[0011] The above and other features, advantages and aspects of the embodiments of the present disclosure will become more apparent with reference to the following detailed description in conjunction with the accompanying drawings. In the accompanying drawings, the same or similar reference numerals represent the same or similar elements, wherein:
[0012] FIG1 shows a schematic diagram of an example environment in which embodiments of the present disclosure can be implemented;
[0013] 2A to 2G respectively illustrate schematic diagrams of example navigation bars in applications according to some embodiments of the present disclosure;
[0014] 3A and 3B are schematic diagrams respectively illustrating example sliding of a navigation bar according to some embodiments of the present disclosure;
[0015] 4A and 4B are schematic diagrams respectively illustrating example menus for components according to some embodiments of the present disclosure;
[0016] FIG5 shows a schematic diagram of an interface including a clear control according to some embodiments of the present disclosure;
[0017] 6A to 6C are schematic diagrams respectively illustrating sliding of the second sub-area according to some embodiments of the present disclosure;
[0018] 7A and 7B respectively illustrate schematic diagrams of example floating windows according to some embodiments of the present disclosure;
[0019] FIG7C shows a schematic diagram of an updated first sub-region according to some embodiments of the present disclosure;
[0020] FIG8 is a schematic diagram illustrating an example interface of a management component in an application according to some embodiments of the present disclosure;
[0021] FIG9 shows a flow chart of an interaction process according to some embodiments of the present disclosure;
[0022] FIG10 shows a block diagram of an interaction device according to some embodiments of the present disclosure; and
[0023] FIG11 shows a block diagram of a device capable of implementing various embodiments of the present disclosure. DETAILED DESCRIPTION
[0024] The following describes embodiments of the present disclosure in more detail with reference to the accompanying drawings. Although certain embodiments of the present disclosure are shown in the accompanying drawings, it should be understood that the present disclosure can be implemented in various forms and should not be construed as limited to the embodiments described herein. Rather, these embodiments are provided to provide a more thorough and complete understanding of the present disclosure. It should be understood that the drawings and embodiments of the present disclosure are for illustrative purposes only and are not intended to limit the scope of protection of the present disclosure.
[0025] In the description of the embodiments of the present disclosure, the term "including" and similar terms should be understood as open inclusion, i.e., "including but not limited to". The term "based on" should be understood as "based at least in part on". The term "one embodiment" or "the embodiment" should be understood as "at least one embodiment". The term "some embodiments" should be understood as "at least some embodiments". Other explicit and implicit definitions may be included below.
[0026] Herein, unless explicitly stated otherwise, executing a step “in response to A” does not mean executing the step immediately after “A” but may include one or more intermediate steps.
[0027] It is understandable that the data involved in this technical solution (including but not limited to the data itself, the acquisition, use, storage or deletion of the data) shall comply with the requirements of relevant laws, regulations and relevant provisions.
[0028] It is understandable that before using the technical solutions disclosed in the various embodiments of the present disclosure, the type, scope of use, usage scenarios, etc. of the information involved in the present disclosure should be informed to relevant users and authorization should be obtained from relevant users in an appropriate manner in accordance with relevant laws and regulations. The relevant users may include any type of right holders, such as individuals, enterprises, and groups.
[0029] For example, in response to receiving an active request from a user, a prompt message is sent to the relevant user to clearly prompt the relevant user that the operation requested to be performed will require obtaining and using the information of the relevant user, so that the relevant user can independently choose whether to provide information to the software or hardware such as the electronic device, application, server or storage medium that executes the operation of the technical solution of the present disclosure based on the prompt message.
[0030] As an optional but non-limiting implementation, in response to receiving an active request from a user, a prompt message may be sent to the user, for example, in the form of a pop-up window, in which the prompt message may be presented in text form. Furthermore, the pop-up window may also include a selection control for the user to select "agree" or "disagree" to provide information to the electronic device.
[0031] It is understandable that the above notification and the process of obtaining user authorization are merely illustrative and do not constitute a limitation on the implementation of the present disclosure. Other methods that comply with relevant laws and regulations may also be applied to the implementation of the present disclosure.
[0032] Some applications may be applications that provide a main function, such as instant messaging applications. Such applications may include multiple components related to the main function, such as a message component for chatting, an address book component, a favorites component, a search component, and so on. In contrast, other applications may be suite applications (sometimes also referred to as collaborative office platforms) that integrate multiple applications. Users can obtain and use multiple applications through suite applications. For example, suite applications may include instant messaging applications, calendar applications, document applications, and so on. These applications integrated by the suite application may also be referred to as components of the suite application.
[0033] As briefly mentioned above, how to provide users with interactive methods in applications to better serve users is a technical issue currently being explored. Whether it is an application that provides a single main function or a suite application that provides multiple functions, during use, users may need to switch between different components or between different pages. However, current solutions do not support flexible switching. Taking a suite application as an example, when a user wants to switch back to a previously opened page, the user needs to start again from the homepage of the component corresponding to the page, or the page is opened outside the suite application, and the user needs to switch outside the suite application. This reduces the convenience of users using the application.
[0034] To this end, an embodiment of the present disclosure proposes an interaction solution. According to various embodiments of the present disclosure, the navigation bar of the application can be divided into at least two different sub-areas, namely a first sub-area and a second sub-area. In the first sub-area, one or more entry controls corresponding to one or more preset components in the application are presented. If a preset opening operation for a component in the application is detected, an access entry related to the component is presented in the second sub-area. The access entry includes an entry to the component or an entry to a page in the component. Thus, the access entry to the preset component and the access entry to the component or page opened by the user can be provided in the navigation bar at the same time. In this way, it is convenient for users to switch between different components and different pages, thereby improving the user experience.
[0035] Figure 1 shows a schematic diagram of an example environment 100 in which embodiments of the present disclosure can be implemented. In this example environment 100, an application 120 is installed on a terminal device 110. A user 140 can interact with the application 120 via the terminal device 110 and / or a device attached to the terminal device 110. In some embodiments, the application 120 may be an application that provides a single primary function, also known as a single-function application. In some embodiments, the application 120 may also be an integrated suite application that provides multiple functions to the user 140. To this end, the suite application may include multiple components for implementing these functions, in which case each component can be considered to correspond to a sub-application. Suite applications in the office field are sometimes also referred to as "office applications," "collaborative office platforms," etc. As examples, the components integrated into a suite application may include, but are not limited to, one or more of the following: a chat component (also known as an instant messaging (IM) component), a document component, an audio and video conferencing component, an email component, a calendar component, a schedule component, a task component, an Objectives and Key Results (OKR) component, etc. In some embodiments, the suite application can also be downloaded and installed as a single application on the terminal device 110.
[0036] In the environment 100 of FIG1 , if the application 120 is started, the terminal device 110 may present an interface 150 of the application 120 to the user 140. The interface 150 is sometimes also referred to as the client interface 150. The interface 150 may include entry controls and access portals for various components provided by the application 120, as well as interactive interfaces associated with the components, such as a conversation interface presenting chat content, a video conferencing interface, a file sharing interface, and the like.
[0037] In some embodiments, the terminal device 110 communicates with the server 130 to enable the supply of services to the application 120. The terminal device 110 can be any type of mobile terminal, fixed terminal or portable terminal, including a mobile phone, a desktop computer, a laptop computer, a notebook computer, a netbook computer, a tablet computer, a media computer, a multimedia tablet, a personal communication system (PCS) device, a personal navigation device, a personal digital assistant (PDA), an audio / video player, a digital camera / camcorder, a television receiver, a radio broadcast receiver, an e-book device, a gaming device or any combination thereof, including accessories and peripherals of these devices or any combination thereof. In some embodiments, the terminal device 110 can also support any type of interface for the user (such as a "wearable" circuit, etc.). The server 130 can be various types of computing systems / servers that can provide computing power, including but not limited to mainframes, edge computing nodes, computing devices in cloud environments, and the like.
[0038] It should be understood that the structure and function of the various elements in the environment 100 are described for illustrative purposes only and do not imply any limitation on the scope of the present disclosure.
[0039] The following will continue to describe some example embodiments of the present disclosure with reference to the accompanying drawings. For ease of explanation, these example embodiments will be described in conjunction with FIG1 . For example, the interactive process provided by the embodiments of the present disclosure can be implemented by the terminal device 110. It should be understood that each interface exemplified in the present disclosure can be presented to the user 140 by the terminal device 110 as a presentation interface of the application 120. In addition, in the subsequent description, the suite application is used as an example, but it should be understood that the content described with respect to the suite application can also be applied to other types of applications.
[0040] In an embodiment of the present disclosure, in order to facilitate the user 140 in using the application 120, a navigation bar may be provided in the application 120, and the navigation bar may include controls, portals, etc. associated with the components. The user 140 may use the corresponding components based on the interaction with these controls, portals, etc. For example, for component A, the user 140 may interact (e.g., click) through the entry controls and access portals associated with component A presented in the navigation bar (e.g., access portals presented based on the icon of component A) to select and use component A (e.g., activate component A, interact with the interface of component A, etc.). The "activation" described herein may refer to any form of access to a page, such as browsing, editing, etc.
[0041] The navigation bar can be divided into at least two presentation areas, for example, a first sub-area and a second sub-area. In the first sub-area of the navigation bar of application 120, one or more entry controls corresponding to one or more preset components in application 120 are presented. In some embodiments, such one or more preset components can be pre-configured by the manager of application 120 (for example, the operator or provider of application 120). In this document, for exemplary purposes only, the preset one or more components whose entry controls are presented in the first sub-area may also be referred to as "fixed components" in application 120. As an example, these fixed components may be associated with some basic functions of application 120 or commonly used functions of users. For example, fixed components may include a message component, a calendar component, a weather component, and the like. Using the first sub-area of the navigation bar to present one or more entry controls corresponding to these fixed components can facilitate users to use these default, basic, or commonly used functions. In some embodiments, the entry control of the fixed component displayed in the first sub-area may point to a page of the fixed component, such as a default page (for example, the homepage of the sub-application) or an opened page. In the following, for the convenience of discussion and without any limitation, the page pointed to by the entry control is referred to as a fixed page.
[0042] In addition to fixed components, application 120 also integrates other components whose entry controls are not displayed in the first sub-area, which are also referred to as non-fixed components. In addition, in addition to fixed pages, fixed components also include other pages that users may visit, also referred to as non-fixed pages. To facilitate user access to non-fixed components or non-fixed pages, the navigation bar also includes a second sub-area that is different from the first sub-area. In response to a preset open operation for a component (also referred to as a target component for ease of discussion), an access entry associated with the target component is presented in the second sub-area. The preset open operation can include various suitable types of operations to activate the target component. The access entry presented may include an entry to the target component or an entry to a page associated with the target component (also referred to as a target page for ease of discussion). In some embodiments, the target component may be different from the fixed component, for example, it may be a non-fixed component. In some embodiments, the target component may be the same as or different from the fixed component, and the address of the target page (e.g., a uniform resource locator URL) is different from the address pointed to by the entry control in the first sub-area. In this embodiment, whether the access entry to the target page is presented in the second sub-area depends on the address of the target page.
[0043] In some embodiments, if the target component is a non-fixed component, the access entry presented may be the entry to the default page of the non-fixed component (e.g., the homepage of the application) or the entry to the opened page of the non-fixed component. Accordingly, the preset opening operation may be the opening of the non-fixed component. For example, user 140 may open component B and access the page in component B via application 120. However, such component B is not provided as a fixed component by application 120. For such a non-fixed component, the terminal device 110 may utilize the second sub-area in the navigation bar to present an entry for accessing the non-fixed component or its page. In this way, user 140 may obtain an access entry for accessing a non-fixed component.
[0044] In some embodiments, if the sub-application is a fixed component, the access entry presented may be the entry to a non-fixed page in the fixed component. Accordingly, the preset opening operation may be the opening of the non-fixed page. For example, after opening the fixed component, the user 140 browses or creates another page that is different from the fixed page. In response to this, the terminal device 110 may display the access entry to the page in the second sub-area so that the user can quickly access it. At this point, although the component that provides the page is still a fixed component, the entry control of the fixed component in the first sub-area does not point to the page. By displaying the access entry to the page in the second sub-area, it is convenient to quickly jump to the non-fixed page in the fixed component.
[0045] In some embodiments, if multiple pages of a component are open, access portals for each of these pages can be presented in the second sub-area. These access portals can be displayed in an aggregated or distributed manner. In this way, users can conveniently access different pages of the same component. An example embodiment of the aggregated approach will be described in detail below with reference to FIG2D .
[0046] In some embodiments, the component targeted by the access entry presented in the second sub-area may be a component in application 120. Alternatively or additionally, the page targeted by the access entry presented in the second sub-area may be a page of the component in application 120 (e.g., a page of a sub-application corresponding to the component). In embodiments of the present disclosure, the component in application 120 may be any suitable component, such as a native component of application 120 or a non-native component developed by a third party.
[0047] Hereinafter, for ease of description, the access portals to non-fixed components or non-fixed pages presented in the second sub-area are also referred to as non-fixed access portals. For example, reference may be made to interface 200A in FIG. 2A . It should be understood that FIG. 2A and the other figures described below use a suite application as an example of application 120 , but this is merely exemplary and not intended to be limiting. The embodiments described with reference to these figures are equally applicable to other applications.
[0048] Interface 200A can be considered as an example interface of a suite application. In some embodiments, the suite application can be associated with different tenants. Accordingly, interface 200A may also include area 210, which provides tenant entrances 211 and 212 for different tenants. User 140 can select a tenant by interacting with the tenant entrance (for example, left-clicking the mouse, or simply left-clicking). Alternatively or additionally, in order to indicate the tenant currently selected and used by user 140, after the tenant entrance is selected, the current tenant entrance may also be highlighted in interface 200A, for example, an indicator box 213 may be added in association with the tenant entrance to intuitively show the user 140 the tenant identity currently being used. For the same user, the same or different fixed components may be preset for different tenants.
[0049] In the example of Figure 2A, the navigation bar 220 includes a first sub-area 230 and a second sub-area 240. In the first sub-area 230, entry controls 221-223 of preset fixed components are presented. In the second sub-area 240, access entries 226-227 associated with the target component are presented. In this example, the access entry 226 is the entry of a non-fixed component (whose displayed name is "Application AB"), such as the homepage of the non-fixed component or any open page. The access entry 227 includes the entry of a page (for example, an opened document) in a fixed component (for example, a "Document" component).
[0050] The entry controls and access portals presented in the navigation bar can have any suitable presentation style, for example, they can include icon elements and / or text description elements to facilitate the user's understanding of the component being pointed to. In the example of Figure 2A, the entry control 221 can include an icon element and a text description "message". However, this is merely exemplary and is not intended to be limiting. The presentation style of the entry controls and access portals is also related to the overall layout of the interface of the suite application, and such an example will be described below with reference to Figures 2B and 2C.
[0051] In some embodiments, a separation line 225 may be further presented for distinguishing the first sub-region 230 from the second sub-region 240 , so that the user 140 can intuitively understand the first sub-region 230 and the second sub-region 240 based on the separation line 225 .
[0052] In addition, a page presentation area may be displayed, which is displayed in the same interface as the navigation bar and is used to present the currently activated page or a page within an activated component. In some embodiments, the page presentation area and the navigation bar may not overlap. Continuing with the example of FIG. 2A , interface 200A also includes a page presentation area 260. In embodiments of the present disclosure, the page presentation area and the navigation bar are presented in the same interface. In the example of FIG. 2A , the entry control 221 of the "Message" component is selected. Accordingly, the information stream 261 and chat window 262 of the "Message" component are displayed in page presentation area 260. User 140 can select other users with whom to chat in information stream 261 and engage in a conversation with the selected users in chat window 262. Alternatively or additionally, a separator 263 may be used to distinguish between information stream 261 and chat window 262. In some embodiments, separator 263 may be toggleable, allowing user 140 to adjust the ratio between information stream 261 and chat window 262 using separator 263.
[0053] Alternatively or additionally, a trigger control 224 for managing fixed components may also be presented in the first sub-area 230. The user 140 may use the trigger control 224 to call up a floating window to manage the fixed components in the first sub-area 230 (e.g., add a fixed component, delete the currently displayed fixed component, etc.). This will be described in detail below.
[0054] In some embodiments, in response to user operations or automatically, the terminal device 110 can adjust the layout of the client interface of the application 120. Accordingly, the proportion or area occupied by the navigation bar in the client interface changes. To this end, the presentation style of the entry controls and access portals may also change. For example, for navigation bars of different sizes, a word count constraint can be set for the text description. If the text description exceeds the word count constraint, only a portion of the text description is presented or the text description is not presented.
[0055] For example, reference can be made to interface 200B in FIG2B . Compared to interface 200A, the width of the navigation bar 220 in the horizontal direction is reduced, and area 210 is adjusted from the side of the navigation bar 220 to area 270 below the navigation bar 220. Furthermore, the terminal device 110 can also adjust the presentation position of the text description associated with the component, or adjust the visual style of the entry control and access entrance to further save space. For example, the text description of the entry control and access entrance is adjusted from the horizontal right side of the icon element to the vertical bottom of the icon element.
[0056] In the example of interface 200C, the horizontal width of navigation bar 220 is further reduced. Accordingly, the entry controls and the text descriptions of the access entries are hidden. As a result, the display area of page presentation area 260 can be further increased in the adjusted layout of interface 200B to facilitate user 140's use.
[0057] In some embodiments, in response to a preset operation (e.g., a hover operation) associated with an access entry presented in the second sub-area, a detailed text description of the component or page corresponding to the access entry, such as the full name of the document, may be presented. For example, reference may be made to interface 200D in FIG. 2D . In response to detecting a hover operation directed to access entry 227, terminal device 110 may provide description information 283 associated with access entry 227, thereby providing user 140 with a detailed text description of the non-fixed component or page associated with access entry 227 using description information 283.
[0058] In some embodiments, in order to present the access entrance in the second sub-area, the terminal device 110 can increase the area of the navigation bar, and present at least a portion of the text description and the preset icon in the second sub-area of the navigation bar with the increased area. For example, when a preset open operation for a target component is detected, the size of the navigation bar may not be sufficient to display the text description of the target component or page, such as in the state shown in Figure 2C. In this case, the area of the navigation bar can be increased to the area of the navigation bar 230 illustrated in the interface 200A, and at least a portion of the page name and the preset icon of the component can be presented in the second sub-area 240 of the navigation bar with the increased area. Thus, more information can be provided to the user when a non-fixed component or non-fixed page is opened. Thereafter, the user can be allowed to manually retract the navigation bar, for example, to restore the size of the navigation bar to its previous size.
[0059] In some embodiments, terminal device 110 may provide prompt information to indicate the function of second sub-area 240. For example, interface 200C may display indication information 281 and a control 282 for confirming receipt of indication information 281. After control 282 is triggered, it can be determined that user 140 has received indication information 281, and accordingly, indication information 281 is no longer presented. Indication information 281 allows the user to clearly understand that they can quickly and conveniently access non-fixed components or non-fixed pages, as well as information such as the duration of the non-fixed access portal.
[0060] In some embodiments, the portal controls for multiple linked open pages can be displayed in an aggregated manner in the second sub-area. Linked opening refers to opening one page based on another page, for example, based on a control or displayed content on another page. Linked open pages can be pages of the same type, such as multiple documents, or pages of different types, such as documents or chat windows. Presenting the portal controls for these pages in an aggregated manner allows users to intuitively perceive the relevance of these pages.
[0061] Any suitable aggregation method can be used to display the entry controls of each of these pages. In some embodiments, the entry controls of each of these pages can be displayed in a stacked manner in the second sub-area. Refer to Figure 2D for example. The access portal 227 includes entry controls for three pages displayed in a stacked manner. The stacking order of these entry controls can be related to the sorting of the corresponding pages. As an example, the pages can be sorted according to the time when the pages are opened, for example, the entry control of the most recently opened page is displayed at the top. As another example, the pages can be sorted according to the time of last activation, for example, the entry control of the page most recently visited by the user is displayed at the top.
[0062] In some embodiments, the associated open pages can be displayed in the page presentation area in a paginated manner. That is, at least some of the associated open pages can be displayed simultaneously in the page presentation area. Depending on the upper limit of the number of pages that can be displayed in the page presentation area, pages with a lower ranking can be displayed according to the page ranking, and pages with a higher ranking will not be displayed. The pages can be sorted according to the most recent activation time, and the later the most recent activation time, the lower the ranking of the page.
[0063] In some embodiments, a navigation bar update prompt may be provided to user 140. For example, if the navigation bar configuration is updated to allow for presentation of non-fixed access portals in the second sub-area, a navigation bar update prompt may be presented in first sub-area 230. For example, reference may be made to interface 200E in FIG. 2E . In interface 200E, terminal device 110 may present prompt information 228 at the bottom of first sub-area 230. User 140 may understand that the navigation bar has been updated based on prompt information 228.
[0064] In some embodiments, the presentation positions of different access portals in the second sub-area are related to the order or time in which the associated target components are opened. For ease of understanding, the component that is opened first can be referred to as the first component, and the component that is opened later can be referred to as the second component. Accordingly, the access portal associated with the first component can be referred to as the first access portal, and the access portal associated with the second component can be referred to as the second access portal. The presented second access portal can be located at the first position of the first access portal. The first position indicates that the opening time of the second access portal is later than the opening time of the first access portal. For example, the time sequence in which the access portal, the corresponding component or page is opened can be indicated by the distance between the non-fixed access portal and the first sub-area. For example, the access portal associated with the most recently opened component is closest to the first sub-area. As a result, the user 140 can understand the order in which the non-fixed components or pages are opened based on the arrangement order of the access portals.
[0065] For example, see Figure 2A . In this example, access entry 226 is closer to first sub-area 230 than access entry 227 . This means that the non-fixed component corresponding to access entry 226 is opened later than the non-fixed page corresponding to access entry 227 .
[0066] In some embodiments, when a non-fixed access portal (also referred to as a first access portal) is to be presented, the area of the second sub-area may not be sufficient to display multiple non-fixed access portals including the non-fixed access portal. For example, if the number of fixed components is large, resulting in the first sub-area occupying most of the navigation area, or the client interface of the application 120 occupies a small area on the screen of the terminal device 110, the second sub-area may not be sufficient to display these non-fixed access portals. In this case, at least a portion of these non-fixed access portals can be displayed to the user 140 by sliding the navigation bar or by sliding the second sub-area. For example, at least the first access portal can be displayed by sliding.
[0067] For example, reference may be made to Figures 3A to 3B. In the interface 300A, the navigation bar 220 may only present the first sub-area in the current state, or in other words, the elements in the first sub-area 230 occupy all the positions for presenting entry controls and access entries. In this regard, in order to present the non-fixed access entry when a non-fixed component or a non-fixed page is opened, the entire navigation bar or the second sub-area may be slid. Referring to Figures 3A and 3B at the same time, in the interface 300A, the non-fixed access entry is not displayed in the navigation bar 220. The terminal device 110 can adjust the displayed entry controls and non-fixed access entries in a scrolling manner (for example, scrolling vertically up or down in the navigation bar 220 or the second sub-area 240). For example, in the case shown in Figure 3A, the navigation bar 220 can be scrolled up so that the entry control 311 is no longer presented in the navigation bar 220, that is, the first entry control presented in the navigation bar 220 is no longer the entry control 311, but the entry control 312. Accordingly, a non-fixed access entry 226 may be displayed in the navigation bar 220, as shown in Figure 3B. In this embodiment, when the first access entry is to be displayed, the first access entry is displayed by autonomously sliding the navigation bar or the second sub-area.
[0068] In some embodiments, if the same non-fixed component or non-fixed page is opened repeatedly, deduplication can be performed based on the address (e.g., URL) and the opened page can be located. That is, in this embodiment, the addresses pointed to by the various non-fixed access portals presented in the second sub-area are different from each other. For example, if it is determined that the target page is to be opened again, the non-fixed access portal of the target page can be highlighted and the target page can be presented in the page presentation area. In this embodiment, deduplication can be used to avoid the same page having multiple non-fixed access portals.
[0069] In some embodiments, if a preset operation on an access entry in the second sub-area is detected, the access entry can be fixedly displayed at a preset position in the second sub-area. The preset operation can be any suitable operation, for example, the preset operation can be to drag the access entry to a preset position. As another example, a control for fixing the access entry at a preset position can be provided in a menu (such as menu 400A described below), and the preset operation can be a triggering operation on the control. The preset position can be any suitable position in the second sub-area. For example, the preset position can be a position in the second sub-area close to the first sub-area, such as the top of the second sub-area. In this embodiment, if the user wants to frequently access a certain page or application, the user can fix its access entry (for example, pin it to the top). In this way, the user can easily find the access entry without being affected by other pages or applications that are subsequently opened.
[0070] The above describes some example embodiments of presenting a non-fixed access portal when a non-fixed component or a non-fixed page is opened. The following describes some example embodiments related to closing a non-fixed access portal.
[0071] In some embodiments, when the non-fixed access entry is the entry to a component, if a closing operation on the component is detected, the presentation of the non-fixed access entry in the second sub-area is correspondingly stopped. In some embodiments, when the non-fixed access entry is the entry to a page, if a closing operation on the page is detected, the presentation of the non-fixed access entry in the second sub-area is correspondingly stopped.
[0072] In some embodiments, if a closing operation is detected for a non-fixed access portal, the non-fixed access portal is no longer presented in the second sub-area. For example, the terminal device 110 may be configured with a close control associated with the non-fixed access portal, so that the user 140 can access the close control through a preset operation (e.g., right-clicking the access portal or hovering over the access portal) and use the close control to close the corresponding access portal. If the non-fixed access portal is closed, the corresponding non-fixed component or page may be closed, for example, by clearing it from the cache.
[0073] When the non-fixed access portal is closed, the terminal device 110 may present different interfaces depending on the page being presented in the page presentation area. In some embodiments, when the non-fixed access portal is closed, the user 140 may be browsing or using a page related to the non-fixed access portal (for ease of understanding, the page presented in the page presentation area 260 at this time may be referred to as the third page), that is, the page presentation area is presenting the third page. The third page may be a target page or any page in a target component. In this case, in response to the closing operation on the non-fixed access portal, the terminal device 110 may stop presenting the non-fixed access portal in the second sub-area, highlight the default portal control in one or more portal controls, and present the page in the component corresponding to the default portal control in the page presentation area. The default portal control may be a fixed component configured to be displayed by default among multiple fixed components, for example, the fixed component ranked first in the first sub-area.
[0074] As an example, the default component can be the "Message" component in Figure 2A, and a chat window can be presented in the page rendering area accordingly. For example, refer to Figure 2F. User 140 is browsing the page corresponding to access entry 229, which in this example is the document "About the Usable Ways of F in G Scenario". Accordingly, the document is displayed in the page rendering area 260. In this case, user 140 closes access entry 229. The presented interface changes to interface 200G in Figure 2G. Access entry 229 is no longer presented in the second sub-area. The entry control 221 of the "Message" component, which is the default entry control, is highlighted, and the information flow and chat window are presented in the page rendering area 260. In this embodiment, if the non-fixed access entry is closed when the relevant page is activated, the default entry control and the page in the corresponding component can be highlighted. In this way, uncontrollable rendering errors caused by the deletion of the non-fixed access entry can be avoided, thereby improving the interaction stability.
[0075] In some embodiments, when the user 140 closes the non-fixed access portal, the current page presented by the page rendering area may be different from the third page, that is, the current page is neither the target page nor the page in the target component. In this case, in response to the closing operation of the non-fixed access portal, the terminal device 110 can stop presenting the non-fixed access portal in the second sub-area 240, highlight the entry control or access portal associated with the current page in the navigation bar, and continue to present the current page in the page rendering area. In this embodiment, when the user browses and uses other pages (which are not the pages pointed to by the non-fixed access portal or the pages in the pointed component), the user can close the non-fixed access portal and continue to present the current page. Thus, closing the non-fixed access portal will not affect the user's browsing and use of the current page.
[0076] In some embodiments, management functions may be provided for non-fixed access portals, and the entrances to these functions may be integrated using a menu for use by user 140. For example, in response to a preset operation on a non-fixed access portal (e.g., right-clicking the access portal), the terminal device 110 may present a menu for the non-fixed access portal. One or more controls may be displayed in the menu, such as a control for moving the non-fixed access portal to the first sub-area, a control for stopping the presentation of the non-fixed access portal, a control for displaying the name of a component, or a control for changing the area of the navigation bar. Thus, user 140 can manage the non-fixed access portal based on the menu.
[0077] For example, Figure 4A shows a menu 400A for a non-fixed access portal. User 140 can call up menu 400A through a pre-set interaction method (e.g., right-clicking a non-fixed access portal in the second sub-area). In this example, control 411 is used to move the non-fixed access portal to the first sub-area, control 412 is used to display the name of the component corresponding to the non-fixed access portal, control 413 is used to change the size of the navigation bar (in this example, to collapse the navigation bar), and control 414 is used to close the non-fixed access portal.
[0078] In some embodiments, to further facilitate the use of the user 140, the user 140 may be allowed to "upgrade" the non-fixed component or page to a fixed component or page based on the usage of the non-fixed component or page, usage requirements, etc. For example, one or more preset operations may be pre-configured. The terminal device 110 may respond to the preset operation made by the user 140 for the non-fixed access portal and present the non-fixed access portal in the first sub-area 230. Accordingly, the presentation of the non-fixed access portal in the second sub-area may be stopped. Thus, the non-fixed access portal can be "upgraded" according to the needs of the user 140 to facilitate subsequent use by the user 140.
[0079] It should be understood that the "upgrade" mentioned above and the "downgrade" to be described below are merely exemplary expressions for the convenience of explanation and are not intended to impose any limitations on the present disclosure. For example, there is no restriction on the "level" relationship between "fixed components" and "non-fixed components".
[0080] The preset operation may include any suitable type of operation. In some embodiments, the preset operation may include a drag operation to move the non-fixed access portal from the second sub-area to the first sub-area. Alternatively or additionally, terminal device 110 may also configure a menu for the non-fixed access portal. For example, user 140 may invoke the menu by, for example, right-clicking the access portal. The menu may display a movement control for moving the access portal to the first sub-area, such as control 411 in menu 400A. If user 140 triggers the movement control, the non-fixed access portal is moved to the first sub-area.
[0081] In some embodiments, this "upgraded" non-fixed access entry can be displayed after the entry control of the previously configured fixed component, for example, after the access entry 223 shown in the interface 200A). In some embodiments, for the above-mentioned situation where the trigger control 224 exists, this "upgraded" access entry can be presented between the entry control and the trigger control of the fixed component. For example, for the interface 200A, the "upgraded" access entry can be presented between the entry control 223 and the trigger control 224. In this way, the original layout in the first sub-area is avoided from being disrupted, and interference with the user 140 is avoided. In addition, this method is also beneficial to the position of the fixed trigger control, making it convenient for the user 140 to use the trigger control.
[0082] In some embodiments, in order to better utilize the second sub-area 240, the terminal device 110 may maintain a non-fixed access entrance in the second sub-area 240. Some example embodiments of maintaining a non-fixed access entrance are described below.
[0083] In some embodiments, the terminal device 110 may retain the non-fixed access entries that were present in the second sub-area when the application 120 was last exited. In this case, when the application 120 is restarted, these retained non-fixed access entries may be presented in the second sub-area. This further facilitates user access to non-fixed components or non-fixed pages.
[0084] Maintenance of non-fixed access portals may include a clearing mechanism for non-fixed access portals. In some embodiments, the duration of automatic clearing may be set. When the activation of the target component or target page is not detected after a predetermined period of time, the terminal device 110 may automatically stop presenting the corresponding non-fixed access portal in the second sub-area. That is, the non-fixed access portals of pages or components that have not been accessed for a long time may be cleared to avoid pages or components that the user currently does not need occupying the second sub-area and consuming background resources. Alternatively or additionally, the predetermined duration may be notified to the user 140 using, for example, the indication information 281 in the interface 200C. In some embodiments, the preset duration may be configured differently based on the different components. For example, the predetermined duration corresponding to a part of the components may be 5 minutes, while another part of the components may correspond to 1 hour, 1 week, 1 month, and so on. It should be understood that the specific values of the durations listed here are merely exemplary and are not intended to be limiting.
[0085] In some embodiments, user 140 can be supported to clear the content in the second sub-area in batches. For example, if a preset operation for the second sub-area is detected, the content presented in the second sub-area can be cleared. The preset operation can be any suitable type of operation. For example, user 140 can right-click in the second sub-area to call out a clear control.
[0086] In some embodiments, clearing logic can be configured in association with the dividing line between the first sub-area and the second sub-area 240 (e.g., dividing line 225 illustrated in interface 200A). For example, if a hover event is detected over the dividing line between the first sub-area and the second sub-area 240, a second sub-area clear control can be presented. Furthermore, if the user 140 triggers the second sub-area clear control, the terminal device 110 can clear all access entries presented in the second sub-area 240.
[0087] For example, see interface 500 shown in FIG5 . In response to detecting a hover event on separator line 225, a second sub-area clear control 510 may be presented. If user 140 clicks second sub-area clear control 510, terminal device 110 may clear all access entries in second sub-area 240. In this embodiment, quick clearing logic is provided to user 140, allowing user 140 to quickly and batch-clear non-fixed access entries by triggering the quick clearing logic.
[0088] In some embodiments, if the size of the navigation bar is insufficient to display the entire first sub-area and the second sub-area, user 140 may be allowed to slide the navigation bar to display a different portion of the navigation bar. For example, when a hover is detected on the navigation bar, a scroll bar may be presented. User 140 may slide the scroll bar to display a different portion of the navigation bar.
[0089] In some embodiments, the user 140 may be allowed to slide the second sub-area to display different non-fixed access entrances. In this regard, reference may be made to interfaces 600A-600C shown in Figures 6A to 6C. The user 140 may slide the second sub-area 240 (e.g., scroll it down) to update the interface 600A to the interface 600B, i.e., adjust the displayed access entrances 226 and 227 to access entrances 227 and 611. Similarly, the user 140 may continue to slide the second sub-area 240 to update the interface 600B to the interface 600C, i.e., adjust the displayed access entrances 227 and 611 to access entrances 611 and 612.
[0090] Some exemplary embodiments of the second sub-area are described above, and some exemplary embodiments of the first sub-area and the fixing component are described below.
[0091] As briefly mentioned above, a trigger control for a floating window may be presented in the first sub-area, such as trigger control 224 shown in FIG2A . This floating window is used to display "more" components to the user in addition to fixed components. A floating window can serve as a quick launch pad for components and can be used to display portals for commonly used components that are not fixed to the navigation bar. If the trigger control is triggered, the terminal device 110 may present a floating window displaying portal controls for a group of components in the application 120 other than fixed components (e.g., portal controls for non-fixed components). For an example, see FIG7A . In interface 700A, after user 140 clicks trigger control 224, the terminal device 110 may present a floating window 710. Floating window 710 displays portal controls 711-713 for non-fixed components. User 140 can open the corresponding non-fixed component by triggering the portal control in the floating window. If user 140 opens a non-fixed component in this manner, the non-fixed access portal associated with that component will be presented in the second sub-area accordingly. For example, if the entry control 713 is triggered, an access entry associated with the “Photo Album” component is presented in the second sub-area.
[0092] For the non-fixed components in the floating window 710, a menu for management and operation can also be configured for them for use by user 140. In some embodiments, in response to a preset operation (e.g., right-click or hover) on the entry control of the non-fixed component in the floating window, a menu for the non-fixed component can be presented. The menu can display a control for moving the entry control of the non-fixed component to the first sub-area. That is, through this control, the non-fixed component can be upgraded to a fixed component. For example, the newly moved entry control can be presented above the trigger control for the floating window. Alternatively or additionally, the menu can display a control for removing the non-fixed component from the floating window. This makes it easier for user 140 to manage the non-fixed components through the floating window. If all the entry controls in the floating window are removed, the trigger control for the floating window will stop being presented in the navigation bar, for example, the trigger control 224 will stop being presented. Correspondingly, if there is an entry control in the floating window again, the trigger control will be presented again in the navigation bar.
[0093] For example, please refer to Figure 7B. Comparing interface 100A and interface 700B, after user 140 right-clicks entry control 711, terminal device 110 can present menu 720. Control 721 in menu 720 is used to move the entry control of the "map" component to the first sub-area. Control 722 is used to remove the entry control of the "map" component from the floating window. Based on needs, user 140 can choose to trigger control 721 or control 722 to achieve fixation or deletion of non-fixed components. Further, please refer to Figure 7C. Comparing interface 700B and interface 700C, if user 140 triggers (for example, left-clicks) control 721, entry control 711 for the "map" component can be added in the first sub-area.
[0094] In some embodiments, the user 140 may be allowed to move the entry control of the fixed component in the first sub-area to a floating window, for example by dragging, to cancel the fixation of the component. In other words, the fixed component is "downgraded" to a non-fixed component. In some embodiments, if the entry control of the component is moved into the floating window when a page in the fixed component (also referred to as the fourth page) is being presented in the page rendering area, the entry control of the downgraded fixed component may be stopped from being presented in the first sub-area. Further, an access entry associated with the component may be presented in the second sub-area 240, which may be the entry of the page being presented or the entry of the component. In this embodiment, if the fixed component is "downgraded" to a non-fixed component while being opened, the access entry associated with the component is presented in the second sub-area.
[0095] In some embodiments, the user 140 may be supported to adjust the order of components by dragging in the floating window. In some embodiments, a control for viewing all components in the application 120 may be provided in the floating window. If the user clicks the control, the user may be redirected to or presented with a suitable display of a list of components in the application 120. The list of components may include components that the user 140 can use, obtain, or discover.
[0096] In some embodiments, the non-fixed component with its entry control presented in the floating window can be determined based on at least one of the following: configuration information for configuring the display content in the floating window, identification information of whether the component in the application 120 is a commonly used component, or a fixed component. The configuration information, for example, indicates which component or components the administrator configures in the floating window. The identification information, for example, indicates which component or components in the application 120 are commonly used components. Fixed components are considered for deduplication. As an example, the range of components displayed in the floating window can be the sum of the components configured by the administrator to the floating window and the commonly used components of the workbench, minus the fixed components that have been fixed in the first sub-area. In this embodiment, as many non-fixed components as possible can be displayed to the user.
[0097] In some embodiments, for fixed components, the terminal device 110 can similarly provide the user 140 with management functions for fixed components by presenting a menu. The menu for the fixed component can be presented in response to a preset operation (e.g., hovering or right-clicking) on the entry control of the fixed component. For example, reference can be made to menu 400B in Figure 4B. In menu 400B, control 421 is used to move the entry control of the fixed component from the first sub-area to the floating window, control 422 is used to remove the entry control of the fixed component, control 423 is used to hide the name of the fixed component, and control 424 is used to adjust the navigation bar area (e.g., increase the area of the navigation bar in the horizontal direction). If the user 140 selects the remove control (e.g., control 422) in the menu, the entry control of the fixed component is stopped from being presented in the first sub-area. This makes it easy for the user to set the fixed component according to their own needs. If the page of the component is open when the entry control is removed, the page can be closed directly, and the entry control of the default component in the fixed component is highlighted. For example, the entry control of the "Message" component is selected by default.
[0098] Furthermore, to facilitate component configuration and selection by administrators, a management component can be provided. This management component can be used by the administrator of application 120 or a tenant's administrator to configure components within application 120. This allows for dynamic configuration of components based on their functionality, usage, and other factors, improving the quality and usability of components within the component folder. Such a management component can also be considered a component within application 120, and thus the embodiments described above with reference to components within application 120 can also be applied to management components.
[0099] For example, referring to FIG8 , the interface 800 shown in FIG8 may be provided to an administrator for managing "applications." It should be understood that the access portal to such a management component (e.g., access portal 830 ) may also be presented in the navigation bar, for example, in the second sub-area. Similar to interface 200C , instruction information 881 may also be presented.
[0100] The above descriptions of example interfaces for implementing interactions are described with reference to the accompanying drawings. It should be understood that the various interfaces described above and the interface elements, text, etc. therein are exemplary and are not intended to limit the scope of this disclosure. Furthermore, it should be understood that the various embodiments described above can be implemented individually or in combination.
[0101] In an embodiment of the present disclosure, by presenting a non-fixed access entry in the navigation bar, it is convenient for users to re-access used components or pages. In addition, in some embodiments, users are allowed to customize fixed components or pages, thereby making it easier for users to create a navigation bar that is more convenient for them.
[0102] FIG9 shows a flow chart of an interaction process 900 according to some embodiments of the present disclosure. The process 900 may be implemented at the terminal device 110. The process 900 is described below with reference to FIG1.
[0103] In block 910 , the terminal device 110 presents one or more entry controls corresponding to one or more preset components in the application in a first sub-area of a navigation bar of the application.
[0104] At block 920, in response to a preset open operation on a first component in the application, the terminal device 110 presents a first access entry related to the first component in a second sub-area 240 of the navigation bar, where the second sub-area 240 is different from the first sub-area. In an embodiment of the present disclosure, the first access entry includes an entry to the first component or an entry to the first page in the first component.
[0105] In some embodiments, process 900 also includes: in response to a preset opening operation on a second component in the application, presenting a second access entrance related to the second component in the second sub-area 240, the second access entrance including an entrance to the second component or an entrance to a second page in the second component, the second access entrance being located at the first position of the first access entrance, the first position indicating that the opening time of the second access entrance is later than the opening time of the first access entrance.
[0106] In some embodiments, process 900 also includes: in a case where the first access entrance includes an entrance to the first component, in response to a closing operation on at least one of the first component or the first access entrance, stopping presenting the first access entrance in the second sub-area 240; in a case where the first access entrance includes an entrance to the first page in the first component, in response to a closing operation on at least one of the first page or the first access entrance, stopping presenting the first access entrance in the second sub-area.
[0107] In some embodiments, the first component is different from the one or more components; or, the first component is different from or the same as the one or more components, and the address of the first page is different from the address pointed to by the one or more entry controls.
[0108] In some embodiments, presenting the first access entrance includes: in response to the area of the second sub-area being insufficient to display multiple access entrances including the first access entrance, sliding the navigation bar or sliding the second sub-area to display multiple access entrances including the first access entrance to the user.
[0109] In some embodiments, the process 900 further includes: presenting the first access entry in the first sub-area in response to a preset operation on the first access entry.
[0110] In some embodiments, a trigger control for a floating window is also presented in the first sub-area, and the floating window is used to display entry controls of components other than one or more components in the application, and the first access entry is presented between the trigger control and the one or more entry controls.
[0111] In some embodiments, the preset operation includes at least one of the following: a drag operation of moving the first access entrance to the first sub-area, or a selection operation of a mobile control in a menu for the first access entrance.
[0112] In some embodiments, process 900 also includes at least one of the following: in response to detecting a closing operation on the first access portal while presenting a third page in the page rendering area, stopping presenting the first access portal in the second sub-area, highlighting a default portal control among one or more portal controls, and presenting a page in the component corresponding to the default portal control in the page rendering area, or, in response to detecting a closing operation on the first access portal while presenting a current page different from the third page in the page rendering area, stopping presenting the first access portal in the second sub-area, highlighting the portal control or access portal associated with the current page in the navigation bar, and continuing to present the current page in the page rendering area, wherein the third page includes the first page or a page in the first component.
[0113] In some embodiments, the component targeted by the access entry presented in the second sub-area is a component in the application, and / or the page targeted by the access entry presented in the second sub-area is a page of the component in the application.
[0114] In some embodiments, process 900 also includes: in response to a preset operation for the first access entry, presenting a menu for the first access entry, displaying at least one of the following items in the menu: a control for moving the first access entry to the first sub-area, a control for stopping presenting the first access entry, a control for displaying the name of the first component, or a control for changing the area of the navigation bar.
[0115] In some embodiments, presenting the first access portal includes: increasing the area of the navigation bar; and presenting at least a portion of the name associated with the first page and a preset icon corresponding to the first component in a second sub-area of the navigation bar with the increased area.
[0116] In some embodiments, process 900 further includes: in response to determining that the first page is to be opened again, highlighting the first access entry; and presenting the first page in the page presentation area.
[0117] In some embodiments, process 900 further includes: in response to the application being restarted, presenting in the second sub-area one or more access entries that existed in the second sub-area when the application was last exited.
[0118] In some embodiments, process 900 also includes: in a case where the first access entry includes an entry to a first component, in response to not detecting activation of the first component after a predetermined period of time, stopping presenting the first access entry in the second sub-area; or, in a case where the first access entry includes an entry to a first page in the first component, in response to not detecting activation of the first page after a predetermined period of time, stopping presenting the first access entry in the second sub-area.
[0119] In some embodiments, the process 900 further includes: in response to a preset operation on the second sub-area, clearing the content presented in the second sub-area.
[0120] In some embodiments, process 900 further includes: presenting a second sub-area clear control in response to a hover event on a dividing line between the first sub-area and the second sub-area, and wherein the preset operation includes triggering an operation on the second sub-area clear control.
[0121] In some embodiments, a trigger control for a floating window is also presented in the first sub-area, and process 900 also includes: in response to a trigger operation on the trigger control, presenting a floating window, displaying entry controls of a group of components in the application other than one or more components in the floating window, and one of the group of components includes the first component, and the preset opening operation includes a trigger operation on the entry control of the first component.
[0122] In some embodiments, process 900 also includes: in response to a preset operation for the entry control of the first component, presenting a menu for the first component, displaying at least one of the following items in the menu: a control for moving the entry control of the first component to the first sub-area, or a control for removing the entry control of the first component from the floating window.
[0123] In some embodiments, a group of components is determined based on at least one of the following: configuration information for configuring display content in a floating window, identification information of whether a component in an application is a commonly used component, or one or more components.
[0124] In some embodiments, process 900 also includes: in response to the entry control of the third component being moved from the first sub-area to a floating window while the fourth page of the third component in one or more components is presented, stopping presenting the entry control of the third component in the first sub-area; and presenting a third access entry related to the third component in the second sub-area, wherein the third access entry is an entry to the third component or an entry to the fourth page.
[0125] In some embodiments, process 900 also includes: in response to a preset operation on the entry control of a fourth component among the one or more components, presenting a menu for the fourth component; and in response to a selection of a remove control in the menu, stopping presenting the entry control of the fourth component in the first sub-area.
[0126] In some embodiments, process 900 further includes: displaying, in the second sub-area, portal controls of respective associated opened pages in an aggregated manner.
[0127] In some embodiments, displaying the respective entry controls of the plurality of associated opened pages in an aggregated manner in the second sub-region includes: displaying the respective entry controls of the plurality of associated opened pages in a stacked manner in the second sub-region.
[0128] In some embodiments, the process 900 further includes: in response to a second preset operation on the fourth access entrance in the second sub-area, fixedly displaying the fourth access entrance at a preset position in the second sub-area.
[0129] 10 shows a schematic structural block diagram of an interactive apparatus 1000 according to some embodiments of the present disclosure. Apparatus 1000 may be implemented as or included in a terminal device 110. Each module in apparatus 1000 may be implemented by hardware, software, firmware, or any combination thereof.
[0130] As shown, the apparatus 1000 includes a first presentation module 1010 configured to present, in a first sub-area of a navigation bar of an application, one or more entry controls corresponding to one or more preset components in the application. The apparatus 1000 also includes a second presentation module 1020 configured to present, in response to a preset open operation on the first component in the application, a first access entry associated with the first component in a second sub-area of the navigation bar, the second sub-area being different from the first sub-area; wherein the first access entry includes an entry to the first component or an entry to the first page in the first component.
[0131] In some embodiments, the device 1000 also includes a third presentation module, which is configured to present a second access entrance related to the second component in a second sub-area in response to a preset opening operation on the second component in the application, the second access entrance including an entrance to the second component or an entrance to the second page in the second component, and the second access entrance is located at the first position of the first access entrance, and the first position indicates that the opening time of the second access entrance is later than the opening time of the first access entrance.
[0132] In some embodiments, the device 1000 also includes a first stop module, which is configured to stop presenting the first access entrance in the second sub-area in response to a closing operation on at least one of the first component or the first access entrance when the first access entrance includes an entrance to the first component; and to stop presenting the first access entrance in the second sub-area in response to a closing operation on at least one of the first page or the first access entrance when the first access entrance includes an entrance to the first page in the first component.
[0133] In some embodiments, the first component is different from the one or more components; or, the first component is different from or the same as the one or more components, and the address of the first page is different from the address pointed to by the one or more entry controls.
[0134] In some embodiments, the second presentation module 1020 is further configured to: in response to the area of the second sub-area being insufficient to display multiple access entrances including the first access entrance, display multiple access entrances including the first access entrance to the user by sliding the navigation bar or by sliding the second sub-area.
[0135] In some embodiments, the apparatus 1000 further includes an entry adding module configured to present the first access entry in the first sub-area in response to a preset operation on the first access entry.
[0136] In some embodiments, the second presentation module 1020 is further configured to present a trigger control for a floating window in the first sub-area, the floating window being used to display entry controls of components other than one or more components in the application, and the first access entry being presented between the trigger control and the one or more entry controls.
[0137] In some embodiments, the preset operation includes at least one of the following: a drag operation of moving the first access entrance to the first sub-area, or a selection operation of a mobile control in a menu for the first access entrance.
[0138] In some embodiments, the second presentation module 1020 can also be configured to perform at least one of the following: in response to detecting a closing operation on the first access portal while presenting a third page in the page presentation area, stop presenting the first access portal in the second sub-area, highlight the default portal control among one or more portal controls, and present the page in the component corresponding to the default portal control in the page presentation area, or, in response to detecting a closing operation on the first access portal while presenting a current page different from the third page in the page presentation area, stop presenting the first access portal in the second sub-area, highlight the portal control or access portal associated with the current page in the navigation bar, and continue to present the current page in the page presentation area, wherein the third page includes the first page or a page in the first component.
[0139] In some embodiments, the component targeted by the access entry presented in the second sub-area is a component in the application, and / or the page targeted by the access entry presented in the second sub-area is a page of the component in the application.
[0140] In some embodiments, the device 1000 also includes a first menu presentation module, which is configured to present a menu for the first access entry in response to a preset operation for the first access entry, and at least one of the following items is displayed in the menu: a control for moving the first access entry to the first sub-area, a control for stopping presenting the first access entry, a control for displaying the name of the first component, or a control for changing the area of the navigation bar.
[0141] In some embodiments, the second presentation module 1020 is further configured to increase the area of the navigation bar; and present at least a portion of the name associated with the first page and a preset icon corresponding to the first component in a second sub-area of the navigation bar with an increased area.
[0142] In some embodiments, the second presentation module 1020 is further configured to, in response to determining that the first page is to be opened again, highlight the first access entry; and present the first page in the page presentation area.
[0143] In some embodiments, the second presentation module 1020 is further configured to present, in response to the application being restarted, one or more access entries that existed in the second sub-area when the application was last exited, in the second sub-area.
[0144] In some embodiments, the device 1000 also includes a second stopping module, which is configured to stop presenting the first access entry in the second sub-area in response to not detecting activation of the first component or the first page after a predetermined period of time when the first access entry includes an entry to the first component, or to stop presenting the first access entry in the second sub-area in response to not detecting activation of the first page after a predetermined period of time when the first access entry includes an entry to the first page in the first component.
[0145] In some embodiments, the apparatus 1000 further includes a clearing module configured to clear the content presented in the second sub-area in response to a preset operation on the second sub-area.
[0146] In some embodiments, the device 1000 also includes a clear control presentation module, which is configured to present a second sub-area clear control in response to a hover event on a dividing line between the first sub-area and the second sub-area, and wherein the preset operation includes a triggering operation on the second sub-area clear control.
[0147] In some embodiments, a trigger control for a floating window is also presented in the first sub-area, and the device 1000 also includes: a floating window presentation module, configured to present a floating window in response to a trigger operation on the trigger control, displaying entry controls of a group of components in the application other than one or more components in the floating window, and one of the group of components includes the first component, and the preset opening operation includes a trigger operation on the entry control of the first component.
[0148] In some embodiments, the device 1000 also includes a second menu presentation module, which is configured to present a menu for the first component in response to a preset operation on the entry control of the first component, and display at least one of the following items in the menu: a control for moving the entry control of the first component to the first sub-area, or a control for removing the entry control of the first component from the floating window.
[0149] In some embodiments, a group of components is determined based on at least one of the following: configuration information for configuring display content in a floating window, identification information of whether a component in an application is a commonly used component, or one or more components.
[0150] In some embodiments, the device 1000 also includes an entry movement module, which is configured to stop presenting the entry control of the third component in the first sub-area in response to the entry control of the third component being moved from the first sub-area to the floating window while the fourth page of the third component in one or more components is presented; and present a third access entry related to the third component in the second sub-area, wherein the third access entry is the entry of the third component or the entry of the fourth page.
[0151] In some embodiments, the device 1000 also includes a third stop module, which is configured to present a menu for the fourth component in response to a preset operation on the entry control of the fourth component among the one or more components; and to stop presenting the entry control of the fourth component in the first sub-area in response to a selection of the remove control in the menu.
[0152] In some embodiments, the second presentation module 1020 is further configured to display the respective portal controls of the multiple associated opened pages in an aggregated manner in the second sub-area.
[0153] In some embodiments, the second presentation module 1020 is further configured to display the respective portal controls of the associated opened pages in a stacked manner in the second sub-area.
[0154] In some embodiments, the second presentation module 1020 is further configured to, in response to a second preset operation on the fourth access entrance in the second sub-area, fixedly display the fourth access entrance at a preset position in the second sub-area.
[0155] FIG11 is a block diagram illustrating an electronic device 1100 in which one or more embodiments of the present disclosure may be implemented. It should be understood that the electronic device 1100 shown in FIG11 is merely exemplary and should not be construed as limiting the functionality and scope of the embodiments described herein. The electronic device 1100 shown in FIG11 may be used to implement the electronic device 110 of FIG1 .
[0156] As shown in FIG11 , electronic device 1100 is a general-purpose electronic device. Components of electronic device 1100 may include, but are not limited to, one or more processors or processing units 1110, memory 1120, storage device 1130, one or more communication units 1140, one or more input devices 1150, and one or more output devices 1160. Processing unit 1110 may be a real or virtual processor and is capable of performing various processes according to programs stored in memory 1120. In a multi-processor system, multiple processing units execute computer-executable instructions in parallel to enhance the parallel processing capabilities of electronic device 1100.
[0157] The electronic device 1100 typically includes a plurality of computer storage media. Such media can be any accessible media that can be obtained by the electronic device 1100, including but not limited to volatile and non-volatile media, removable and non-removable media. The memory 1120 can be a volatile memory (e.g., registers, cache, random access memory (RAM)), a non-volatile memory (e.g., read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory), or some combination thereof. The storage device 1130 can be a removable or non-removable medium and can include a machine-readable medium, such as a flash drive, a disk, or any other medium that can be used to store information and / or data and can be accessed within the electronic device 1100.
[0158] The electronic device 1100 may further include additional removable / non-removable, volatile / non-volatile storage media. Although not shown in FIG. 11 , a disk drive for reading from or writing to a removable, non-volatile disk (e.g., a "floppy disk") and an optical drive for reading from or writing to a removable, non-volatile optical disk may be provided. In these cases, each drive may be connected to a bus (not shown) by one or more data media interfaces. The memory 1120 may include a computer program product 1125 having one or more program modules configured to perform various methods or actions of various embodiments of the present disclosure.
[0159] The communication unit 1140 enables communication with other electronic devices via a communication medium. Additionally, the functions of the components of the electronic device 1100 can be implemented as a single computing cluster or multiple computing machines that can communicate via a communication connection. Thus, the electronic device 1100 can operate in a networked environment using logical connections to one or more other servers, network personal computers (PCs), or other network nodes.
[0160] Input device 1150 may be one or more input devices, such as a mouse, keyboard, or trackball. Output device 1160 may be one or more output devices, such as a display, a speaker, or a printer. Electronic device 1100 may also communicate with one or more external devices (not shown) via communication unit 1140 as needed, such as storage devices, display devices, or the like, with one or more devices that allow a user to interact with electronic device 1100, or with any device that allows electronic device 1100 to communicate with one or more other electronic devices (e.g., a network card, a modem, etc.). Such communication may be performed via an input / output (I / O) interface (not shown).
[0161] According to an exemplary implementation of the present disclosure, a computer-readable storage medium is provided, on which computer-executable instructions are stored, wherein the computer-executable instructions are executed by a processor to implement the method described above. According to an exemplary implementation of the present disclosure, a computer program product is also provided, which is tangibly stored on a non-transitory computer-readable medium and includes computer-executable instructions, and the computer-executable instructions are executed by a processor to implement the method described above.
[0162] Various aspects of the present disclosure are described herein with reference to flowcharts and / or block diagrams of methods, apparatuses, devices, and computer program products implemented according to the present disclosure. It should be understood that each block of the flowcharts and / or block diagrams, and combinations of blocks in the flowcharts and / or block diagrams, can be implemented by computer-readable program instructions.
[0163] These computer-readable program instructions can be provided to a processing unit of a general-purpose computer, a special-purpose computer, or other programmable data processing device, thereby producing a machine, such that when these instructions are executed by the processing unit of the computer or other programmable data processing device, a device is generated that implements the functions / actions specified in one or more blocks in the flowchart and / or block diagram. These computer-readable program instructions can also be stored in a computer-readable storage medium, where these instructions cause the computer, programmable data processing device, and / or other device to operate in a specific manner. Thus, the computer-readable medium storing the instructions comprises an article of manufacture that includes instructions for implementing various aspects of the functions / actions specified in one or more blocks in the flowchart and / or block diagram.
[0164] Computer-readable program instructions can be loaded onto a computer, other programmable data processing apparatus, or other device so that a series of operational steps are performed on the computer, other programmable data processing apparatus, or other device to produce a computer-implemented process, thereby causing the instructions executed on the computer, other programmable data processing apparatus, or other device to implement the functions / actions specified in one or more boxes in the flowchart and / or block diagram.
[0165] The flow charts and block diagrams in the accompanying drawings show the possible architecture, functions and operations of the systems, methods and computer program products according to multiple implementations of the present disclosure. In this regard, each box in the flow chart or block diagram can represent a part for a module, program segment or instruction, and a part for a module, program segment or instruction comprises one or more executable instructions for realizing the logical function of the specification. In some alternative implementations, the functions marked in the box can also occur in a sequence different from that marked in the accompanying drawings. For example, two continuous boxes can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each box in the block diagram and / or flow chart, and the combination of the boxes in the block diagram and / or flow chart can be realized by a special hardware-based system that performs the function or action of the specification, or can be realized by a combination of special hardware and computer instructions.
[0166] While various implementations of the present disclosure have been described above, the foregoing description is intended to be illustrative, not exhaustive, and not limited to the disclosed implementations. Many modifications and variations will be apparent to those skilled in the art without departing from the scope and spirit of the described implementations. The terminology used herein is selected to best explain the principles of the implementations, their practical applications, or improvements to existing technologies, or to enable others skilled in the art to understand the various implementations disclosed herein.
Claims
1. An interactive method, comprising: In a first sub-area of a navigation bar of an application, presenting one or more entry controls corresponding to one or more preset components in the application respectively; as well as In response to a preset opening operation on a first component in the application, presenting a first access entry related to the first component in a second sub-area of the navigation bar, the second sub-area being different from the first sub-area; The first access entrance includes an entrance to the first component or an entrance to the first page in the first component.
2. The method according to claim 1, further comprising: In response to a preset opening operation on a second component in the application, a second access entrance related to the second component is presented in the second sub-area, the second access entrance including an entrance to the second component or an entrance to a second page in the second component, the second access entrance being located at a first position of the first access entrance, the first position indicating that an opening time of the second access entrance is later than an opening time of the first access entrance.
3. The method according to claim 1, further comprising: In a case where the first access entrance includes an entrance of the first component, in response to a closing operation on at least one of the first component or the first access entrance, stopping presenting the first access entrance in the second sub-area; or, In a case where the first access entrance includes an entrance to a first page in the first component, in response to a closing operation on at least one of the first page or the first access entrance, the first access entrance stops being presented in the second sub-area.
4. The method according to claim 1, wherein the first component is different from the one or more components; or, The first component is different from or the same as the one or more components, and the address of the first page is different from the addresses pointed to by the one or more entry controls.
5. The method according to claim 1, wherein presenting the first access portal comprises: In response to the area of the second sub-region being insufficient to display multiple access entrances including the first access entrance, the multiple access entrances including the first access entrance are displayed to the user by sliding the navigation bar or by sliding the second sub-region.
6. The method according to claim 1, further comprising: In response to a preset operation on the first access entrance, the first access entrance is presented in the first sub-area.
7. The method according to claim 6, wherein a trigger control for a floating window is also presented in the first sub-area, the floating window is used to display entry controls of components in the application other than the one or more components, and the first access entry is presented between the trigger control and the one or more entry controls.
8. The method according to claim 6, wherein the preset operation comprises at least one of the following: A drag operation of moving the first access entry to the first sub-area, or A selection operation on a mobile control in a menu for the first access portal.
9. The method according to claim 1, further comprising at least one of the following: In response to detecting a closing operation on the first access portal while presenting a third page in the page presentation area, stopping presenting the first access portal in the second sub-area, highlighting a default portal control among the one or more portal controls, and presenting a page in a component corresponding to the default portal control in the page presentation area, or, In response to detecting a closing operation on the first access entry while presenting a current page different from the third page in the page presentation area, stopping presenting the first access entry in the second sub-area, highlighting an entry control or access entry associated with the current page in the navigation bar, and continuing to present the current page in the page presentation area, The third page includes the first page or a page in the first component.
10. The method according to claim 1, wherein the component for which the access entry presented in the second sub-area is directed is a component in the application, and / or The page targeted by the access entry presented in the second sub-area is a page of a component in the application.
11. The method according to claim 1, further comprising: In response to a preset operation for the first access entry, a menu for the first access entry is presented, wherein at least one of the following items is displayed in the menu: A control for moving the first access entry to the first sub-area, a control for stopping presentation of the first access entry, a control for displaying the name of the first component, or A control used to change the area of the navigation bar.
12. The method according to claim 1, wherein presenting the first access portal comprises: Increasing the area of the navigation bar; as well as At least a portion of the name associated with the first page and a preset icon corresponding to the first component are presented in a second sub-region of the navigation bar with an increased area.
13. The method according to claim 1, further comprising: In response to determining that the first page is to be opened again, highlighting the first access entry; as well as The first page is presented in a page presentation area.
14. The method according to claim 1, further comprising: In response to the application being restarted, one or more access entries that existed in the second sub-area when the application was last exited are presented in the second sub-area.
15. The method according to claim 1, further comprising: In a case where the first access entrance includes an entrance of the first component, in response to not detecting activation of the first component after a predetermined period of time, stopping presenting the first access entrance in the second sub-area or, In a case where the first access entry includes an entry to a first page in the first component, in response to not detecting activation of the first page for a predetermined period of time, the first access entry is stopped from being presented in the second sub-area.
16. The method according to claim 1, further comprising: In response to a preset operation on the second sub-area, the content presented in the second sub-area is cleared.
17. The method according to claim 16, further comprising: In response to a hover event on a dividing line between the first sub-area and the second sub-area, presenting a second sub-area clearing control, and The preset operation includes a triggering operation of clearing controls in the second sub-area.
18. The method according to claim 1, wherein a trigger control for a floating window is also presented in the first sub-area, and the method further comprises: In response to a trigger operation on the trigger control, presenting the floating window, displaying entry controls of a group of components in the application other than the one or more components in the floating window, and The group of components includes the first component, and the preset opening operation includes a triggering operation of an entry control of the first component.
19. The method according to claim 18, further comprising: In response to a preset operation on the entry control of the first component, a menu for the first component is presented, in which at least one of the following items is displayed: Move the entry control of the first component to the control of the first sub-area, or A control for removing the entry control of the first component from the floating window.
20. The method of claim 18, wherein the set of components is determined based on at least one of: Configuration information for configuring the display content in the floating window, Identification information of whether the component in the application is a common component, or The one or more components.
21. The method of claim 18, further comprising: In response to the entry control of the third component being moved from the first sub-region to the floating window while the fourth page of the third component among the one or more components is presented, stopping presenting the entry control of the third component in the first sub-region; as well as A third access entry related to the third component is presented in the second sub-area, wherein the third access entry is an entry to the third component or an entry to the fourth page.
22. The method of claim 1, further comprising: In response to a preset operation on an entry control of a fourth component among the one or more components, presenting a menu for the fourth component; as well as In response to a selection of a remove control in the menu, presentation of an entry control of the fourth component in the first sub-area is stopped.
23. The method of claim 1, further comprising: In the second sub-area, respective entry controls of the multiple pages associated and opened are displayed in an aggregated manner.
24. The method according to claim 23, wherein: The displaying of the respective entry controls of the multiple pages opened in association in the second sub-area in an aggregated manner comprises: In the second sub-area, respective entry controls of the associated opened pages are displayed in a stacked manner.
25. The method of claim 1, further comprising: In response to a second preset operation on a fourth access entrance in the second sub-area, the fourth access entrance is fixedly displayed at a preset position in the second sub-area.
26. An interactive device, comprising: A first presentation module is configured to present, in a first sub-area of a navigation bar of an application, one or more entry controls corresponding to one or more preset components in the application; A second presentation module is configured to present, in response to a preset opening operation on a first component in the application, a first access entry related to the first component in a second sub-area of the navigation bar, the second sub-area being different from the first sub-area; The first access entrance includes an entrance to the first component or an entrance to the first page in the first component.
27. An electronic device comprising: at least one processing unit; as well as at least one memory, the at least one memory being coupled to the at least one processing unit and storing instructions for execution by the at least one processing unit, the instructions causing the electronic device to execute according to The method of any one of claims 1 to 25.
28. A computer-readable storage medium having a computer program stored thereon, the computer program being executable by a processor to implement the method according to any one of claims 1 to 25.
Citation Information
Patent Citations
Desktop management method of terminal equipment and terminal equipment
CN113325985A
Application interface switching method and device based on navigation, equipment and storage medium
CN113835585A
Small component processing method and device, equipment and medium
CN114741017A
Taskbar with start menu
US5757371A
