Page switching method and device, equipment and storage medium

Abstract

The embodiment of the invention provides a page switching method and device, equipment and a storage medium. The method comprises the following steps: displaying a first function page in an application window through a page stack container corresponding to a first resident service function under a main page container; in response to a trigger operation, detected through the first function page, of entering a second function page corresponding to the first non-resident service function, creating a page stack container corresponding to the first non-resident service function through the main page container, and creating and displaying a temporary function entry corresponding to the first non-resident service function in the function navigation bar; and adjusting a page stack container corresponding to the first non-resident service function to a display state through the main page container, and switching a first function page displayed in the application window to a second function page through the page stack container corresponding to the first non-resident service function. According to the method and the device, high efficiency and quickness of page switching in the target application can be ensured, and the operation complexity of page switching in the target application is greatly reduced.

Description

Technical Field

[0001] This application relates to the field of data processing technology, specifically to a method, apparatus, device, and storage medium for page switching. Background Technology

[0002] With the rapid development of internet technology, various applications are constantly releasing more and more service functions to users, resulting in a continuous addition of functional pages within these applications to support diverse user interactions. Therefore, achieving efficient and smooth page switching across various applications has become a critical issue that urgently needs to be addressed in this field.

[0003] Currently, various applications typically include functional controls on their main page to allow users to navigate to different functional pages. However, switching between pages within different services within these applications requires frequent returns to the main page, significantly increasing the tediousness of page navigation. Summary of the Invention

[0004] This application provides a method, apparatus, device, and storage medium for page switching, ensuring efficient and fast page switching within a target application, reducing the complexity of page switching operations, and improving the smoothness and effectiveness of page switching within the target application.

[0005] In a first aspect, embodiments of this application provide a method for page switching, wherein the application window of the target application includes a function navigation bar, the function navigation bar including multiple persistent function entries corresponding to persistent service functions, and the method includes: The first function page is displayed in the application window through the page stack container corresponding to the first persistent service function under the main page container; wherein, the first function page is the function page of the first persistent service function. In response to the trigger operation of entering the second function page corresponding to the first non-permanent service function detected by the first function page, a page stack container corresponding to the first non-permanent service function is created through the main page container, and a temporary function entry corresponding to the first non-permanent service function is created and displayed in the function navigation bar. The main page container adjusts the page stack container corresponding to the first non-permanent service function to the display state, and the page stack container corresponding to the first non-permanent service function switches the first function page displayed in the application window to the second function page.

[0006] Secondly, embodiments of this application provide a page switching device. The application window of the target application includes a function navigation bar, which includes multiple persistent function entries corresponding to persistent service functions. The device includes: The persistent function display module is used to display the first function page in the application window through the page stack container corresponding to the first persistent service function under the main page container; wherein, the first function page is the function page of the first persistent service function; The temporary function creation module is used to respond to the trigger operation of entering the second function page corresponding to the first non-permanent service function detected by the first function page, create a page stack container corresponding to the first non-permanent service function through the main page container, and create and display the temporary function entry corresponding to the first non-permanent service function in the function navigation bar. The page switching module is used to adjust the page stack container corresponding to the first non-permanent service function to the display state through the main page container, and to switch the first function page displayed in the application window to the second function page through the page stack container corresponding to the first non-permanent service function.

[0007] Thirdly, embodiments of this application provide an electronic device, which includes: A processor and a memory, the memory being used to store a computer program, and the processor being used to invoke and run the computer program stored in the memory to perform the page switching method provided in the first aspect of this application.

[0008] Fourthly, embodiments of this application provide a computer-readable storage medium for storing a computer program that causes a computer to perform the page switching method provided in the first aspect of this application.

[0009] Fifthly, embodiments of this application provide a computer program product, including a computer program / instructions that, when executed by a processor, implement the page switching method provided in the first aspect of this application.

[0010] The technical solution provided in this application embodiment sets a function navigation bar within the application window of the target application. This function navigation bar can include persistent function entries corresponding to multiple persistent service functions. Upon entering the target application, a first function page can be displayed in the application window via a page stack container corresponding to the first persistent service function under the main page container. This first function page can be the function page of the first persistent service function. When a trigger operation to enter a second function page corresponding to a first non-persistent service function is detected through the first function page, a page stack container corresponding to the first non-persistent service function is created through the main page container, and a temporary function entry corresponding to the first non-persistent service function is created and displayed in the function navigation bar. Then, the page stack container corresponding to the first non-persistent service function is adjusted to a display state through the main page container, and the first function page displayed in the application window is switched to the second function page through the page stack container corresponding to the first non-persistent service function, thereby achieving accurate page switching within the target application. Therefore, by displaying persistent and temporary function entries in the function navigation bar of the target application's application window, this application can ensure the efficiency and speed of page switching within the target application, eliminating the need to frequently return to the application's main page to perform page switching operations. This greatly reduces the cumbersomeness of page switching operations within the target application, improves the smoothness and effectiveness of page switching within the target application, and further optimizes the page switching performance within the target application. Attached Figure Description

[0011] To more clearly illustrate the technical solutions in the embodiments of this application, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the accompanying drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0012] Figure 1a A flowchart illustrating a page switching method provided in an embodiment of this application; Figure 1b An exemplary schematic diagram of the application window architecture of the target application provided in the embodiments of this application; Figure 1c Another exemplary schematic diagram of the application window architecture of the target application provided in the embodiments of this application; Figure 1d This is an exemplary schematic diagram illustrating the page switching process between persistent and non-persistent service functions provided in the embodiments of this application. Figure 2a An exemplary schematic diagram of a functional navigation bar provided in an embodiment of this application; Figure 2b Another exemplary schematic diagram of the functional navigation bar provided in the embodiments of this application; Figure 3 A flowchart illustrating the method for switching the function page of another non-permanent service function when a temporary function entry corresponding to a first non-permanent service function is created and displayed in the function navigation bar, as provided in this application embodiment; Figure 4a This is an exemplary control diagram of a temporary function entry corresponding to a non-permanent service function in the function navigation bar provided in the embodiments of this application; Figure 4b This is another exemplary control diagram of the temporary function entry corresponding to the non-permanent service function in the function navigation bar provided in the embodiments of this application; Figure 5a A flowchart illustrating the method for full-screen switching of function pages for any service function displayed in an application window provided in this embodiment of the application. Figure 5b A full-screen display diagram of any service function page displayed in the application window of the target application provided in this embodiment of the application; Figure 6 A schematic block diagram of a page switching device provided in an embodiment of this application; Figure 7 A schematic block diagram of an electronic device provided in an embodiment of this application. Detailed Implementation

[0013] The technical solutions of the embodiments of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those of ordinary skill in the art without creative effort are within the scope of protection of this application.

[0014] It should be noted that the terms "first," "second," etc., in the specification, claims, and accompanying drawings of this application are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that the embodiments of this application described herein can be implemented in orders other than those illustrated or described herein. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion; for example, a process, method, system, product, or server that comprises a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or devices.

[0015] In this application, the terms "exemplary" or "for example" are used to indicate that something is an example, illustration, or description. Any embodiment or solution described as "exemplary" or "for example" in this application should not be construed as being better or more advantageous than other embodiments or solutions. Specifically, the use of terms such as "exemplary" or "for example" is intended to present the relevant concepts in a specific manner.

[0016] In the description of the embodiments in this application, unless otherwise stated, "multiple" means two or more, that is, at least two. "At least one" means one or more. "Any" means any one or any several.

[0017] It should be noted that all information (including but not limited to user identity information when logging into the target application, various application function definition information, and other related personal information), data (including but not limited to data used for analysis, stored data, and displayed data), and signals involved in this application have been authorized by the user or fully authorized by all parties, and the collection, use, and processing of related data must comply with the relevant laws, regulations, and standards of the relevant countries and regions. For example, the user identity data when logging into the target application, the persistent definition information of various application functions within the target application, and various user switching operation data during page switching processes involved in this application were all obtained with full authorization.

[0018] In related technologies, switching between different service functions within various applications requires frequently returning to the application's main page to perform the corresponding page switching operation, which greatly increases the cumbersomeness of page switching.

[0019] To address the aforementioned technical issues, this application proposes a novel page switching scheme. A function navigation bar is set within the application window of the target application. This navigation bar can include persistent function entries corresponding to multiple persistent service functions. Upon entering the target application, a first function page (the page for the first persistent service function) is displayed in the application window via a page stack container corresponding to the first persistent service function under the main page container. When a trigger operation to enter a second function page corresponding to a first non-persistent service function is detected through the first function page, a page stack container corresponding to the first non-persistent service function is created through the main page container, and a temporary function entry corresponding to the first non-persistent service function is created and displayed in the function navigation bar. Then, the page stack container corresponding to the first non-persistent service function is brought to the display state through the main page container, and the first function page displayed in the application window is switched to the second function page through the page stack container corresponding to the first non-persistent service function, thereby achieving accurate page switching within the target application. Therefore, by displaying persistent and temporary function entry points in the function navigation bar of the target application's application window, this application can ensure the efficiency and speed of page switching within the target application, greatly reduce the cumbersomeness of page switching operations within the target application, and improve the smoothness and effectiveness of page switching within the target application.

[0020] Figure 1a This is a flowchart illustrating a page switching method provided in an embodiment of this application. This method can be executed by the page switching device provided in this application. The page switching device can be implemented in any software and / or hardware manner. Exemplarily, the page switching device can be applied to any electronic device, including but not limited to tablet computers, mobile phones (such as foldable phones, large-screen phones, etc.), wearable devices, in-vehicle devices, laptops, ultra-mobile personal computers (UMPCs), netbooks, personal digital assistants (PDAs), smart TVs, smart screens, high-definition TVs, 4K TVs, smart speakers, smart projectors, service terminals, cloud servers, server clusters, and other computing devices. This application does not impose any restrictions on the specific type of electronic device.

[0021] Specifically, such as Figure 1a As shown, the method may include the following steps: S110, the first function page is displayed in the application window through the page stack container corresponding to the first persistent service function under the main page container; wherein, the first function page is the function page of the first persistent service function.

[0022] The target application can be any application developed based on users' diverse interaction needs in various scenarios. The target application will continuously release various service functions, and each service function will have various functional pages to provide users with diverse interactive services. Therefore, by continuously switching between the functional pages under different service functions within the target application, users can perform diverse interactive operations on different functional pages under different service functions.

[0023] Therefore, in order to achieve efficient and accurate switching between various pages within the target application, this application sets a function navigation bar within the application window of the target application. It can be understood that the function navigation bar can be displayed within a preset area of ​​the main page of the target application; wherein, the preset area can refer to the bottom of the main page of the target application, that is, the function navigation bar can be a bottom navigation bar; the preset area can refer to the left or right side of the main page of the target application, that is, the function navigation bar can be a side navigation bar; the preset area can also refer to the top of the main page of the target application, that is, the function navigation bar can be a top navigation bar, etc., and this application does not limit it in this way.

[0024] The function navigation bar may include at least one function entry corresponding to a service function. By triggering the function entry corresponding to the service function, the function page corresponding to the service function can be quickly opened in the target application, so that users can quickly and effectively access and operate the service function within the function navigation bar.

[0025] Specifically, the service functions may include persistent service functions, which can refer to service functions that users use frequently. To ensure accurate integration of frequently used functions within the aforementioned function navigation bar, this application, in addition to the aforementioned function navigation bar, can also configure a custom persistent service function for the target application. This allows any user, upon entering the target application, to trigger the pre-defined custom persistent service function control to pre-define frequently used service functions from all the target application's service functions, which will then be used as persistent service functions in this application. Furthermore, the function navigation bar can directly display the persistent function entry points corresponding to each persistent service function, enabling users to quickly and effectively access and operate each persistent service function within the navigation bar.

[0026] In one embodiment, the aforementioned functional navigation bar can be managed through a main page container. The main page container corresponds to the application window of the target application and is used to manage the content displayed in the application window. Specifically, by integrating the aforementioned functional navigation bar in the application window into the main page container, the main page container can manage the functional navigation bar. Specifically, the main page container can manage the display status of the functional navigation bar in the application window, the number of persistent functional services in the functional navigation bar, and the display status of the corresponding functional entries for the persistent functional services in the functional navigation bar.

[0027] Furthermore, in one embodiment, the main page container may also be configured with page stack containers, with different page stack containers corresponding to different service functions; the main page container can be used to manage the creation, closing, displaying or hiding of page stack containers for different service functions, so as to display or close the corresponding service function's function page in the application page.

[0028] Specifically, for each persistent function service in the function navigation bar, a page stack container corresponding to each persistent function service can be pre-created through the main page container, and the function pages of the corresponding persistent function services can be stored and displayed through the page stack container. Understandably, for each service function within the target application, in order to ensure diverse functional interactions for users within the target application, each service function will be configured with multiple functional pages, including a main functional page and multiple sub-functional pages. The page stack container corresponding to the service function can continuously store the relevant functional pages that the user has most recently viewed in that persistent service function, according to the page browsing order under that service function. When the number of stored pages exceeds the total storage capacity set by the page stack container, the earliest relevant functional page that the user has viewed in that persistent service function can be removed, so that the top page in the page stack container corresponding to each persistent service function can always be a specific functional page that the user has most recently viewed in that persistent service function.

[0029] Therefore, for the target application, the main page container corresponding to the application window can specifically include a main page container with a function navigation bar and a page stack container corresponding to multiple persistent service functions. Furthermore, the main page container is used to adjust the specific state of the page stack containers corresponding to each persistent service function to display the function pages of the relevant persistent service functions within the target application window.

[0030] For example, the number of persistent functional services in the function navigation bar is 4, such as... Figure 1bAs shown, the main page container corresponding to the application window of the target application can include a main page container with a function navigation bar and page stack containers corresponding to four persistent service functions. The function navigation bar contains persistent function entries for the four persistent service functions. Furthermore, each page stack container corresponding to a persistent service function can contain a sub-function navigation bar located in a different area from the main function navigation bar, to avoid confusion with the main function navigation bar.

[0031] As can be seen from the above, the first persistent service function in this application can be any persistent service function already defined in the target application, and the persistent function entry corresponding to the first persistent service function will be set in the function navigation bar of the application window. The page stack container corresponding to the first persistent service function can be created through the main page container.

[0032] The first persistent service function can be a persistent service function that is displayed by default when entering the target application, or a persistent service function that the user is currently browsing and using; there is no limitation here. For example... Figure 1d As shown, the main page container of the target application can adjust the page stack container corresponding to the first persistent service function to a visible state, while adjusting the page stack containers corresponding to other persistent service functions to a hidden state, so that the application window of the target application displays the function page corresponding to the first persistent service function. At the same time, the main page container of the target application can also set the function entry of the first persistent service function in the function navigation bar to a selected state.

[0033] Furthermore, the top page in the page stack container corresponding to the first resident service function can be obtained and displayed in the application window of the target application as the first function page.

[0034] It is understandable that, since the page stack container corresponding to the first persistent service function is used to manage multiple functional pages, including the main functional page and multiple sub-functional pages under that first persistent service function, the aforementioned first functional page can be any one of the main functional page and multiple sub-functional pages under the first persistent service function.

[0035] S120, in response to the trigger operation of entering the second function page corresponding to the first non-permanent service function detected by the first function page, a page stack container corresponding to the first non-permanent service function is created through the main page container, and a temporary function entry corresponding to the first non-permanent service function is created and displayed in the function navigation bar.

[0036] In addition to the persistent services in the navigation bar, the target application will also contain several less frequently used services, which can be considered non-persistent services. It's understood that the function pages of each service often contain trigger controls or links to other services. Upon detecting a trigger operation on these controls or links, users can be redirected from the original page of the primary service to the page of the corresponding non-persistent service. Therefore, the relevant function pages of the persistent services can contain trigger controls or links for non-persistent services. Upon detecting a trigger operation on these controls or links, users can be redirected from the original page of the persistent service to the page of the non-persistent service indicated by the trigger control or link, allowing users to effectively access and operate multiple function pages of various non-persistent services.

[0037] After displaying the first functional page in the target application's application window, this first functional page may contain function trigger controls or access links for related non-permanent service functions. Therefore, this application can use the first functional page to detect whether the user has performed a trigger operation on a function trigger control or access link for a specific non-permanent service function within that first functional page, thereby determining whether the user has an access requirement for the relevant functional page of that non-permanent service function.

[0038] When the system detects that a user has triggered an operation on a function trigger control or access link within a non-resident service function on the first function page, this application can designate that non-resident service function as the first non-resident service function in this application, and determine a specific function page that the user specified to access for the first non-resident service function as the second function page in this application, to instruct the user to enter the second function page. The second function page can be the main function page displayed by default when the first non-resident service function is enabled, or it can be a sub-page of the first non-resident service function represented by the access link triggered by the user.

[0039] Then, in response to the triggering operation of entering the second functional page corresponding to the first non-permanent service function detected by the first functional page, this application can create a page stack container for the first non-permanent service function through the main page container, so as to manage the relevant functional pages browsed by the user under the first non-permanent service function through the page stack container.

[0040] At the same time, such as Figure 1dAs shown, the main page container also creates and displays a temporary function entry for the first non-permanent service function in the function navigation bar, allowing users to quickly and effectively access and operate the first non-permanent service function within this function navigation bar. Specifically, the function navigation bar can display the temporary function entry for the first non-permanent service function in a designated area.

[0041] Furthermore, the main page container of the target application can also set the function entry of the first permanent service function in the function navigation bar to an unselected state, and set the temporary function entry corresponding to the first non-permanent service function in the function navigation bar to a selected state.

[0042] Understandably, for the target application, if a non-persistent service function is enabled within the target application, the main page container of the target application window can include a main page container with a function navigation bar, multiple persistent service functions, and a page stack container corresponding to the enabled non-persistent service function. Furthermore, by adjusting the specific state of the page stack containers corresponding to each persistent service function and the enabled non-persistent service function through the main page container, the function pages of the relevant service functions among the persistent and enabled non-persistent service functions are displayed in the target application window.

[0043] For example, if the number of persistent service functions in the function navigation bar is 4, and 1 non-persistent service function is already enabled, then... Figure 1c As shown, the main page container of the target application's application window can include a function navigation bar, four page stack containers corresponding to persistent service functions, and one page stack container corresponding to a non-persistent service function. The function navigation bar includes persistent function entries for the four persistent service functions and a temporary function entry for the one non-persistent service function. Furthermore, both the page stack containers corresponding to persistent and non-persistent service functions can contain sub-function navigation bars located in different areas from the main function navigation bar, avoiding confusion with the main function navigation bar.

[0044] S130, the page stack container corresponding to the first non-permanent service function is adjusted to the display state through the main page container, and the first function page displayed in the application window is switched to the second function page through the page stack container corresponding to the first non-permanent service function.

[0045] After creating the page stack container corresponding to the first non-permanent service function through the main page container, and creating and displaying the temporary function entry corresponding to the first non-permanent service function in the function navigation bar, this application can adjust the page stack container corresponding to the first permanent service function to a hidden state through the main page container, and adjust the page stack container corresponding to the first non-permanent service function to a visible state. Furthermore, as... Figure 1d As shown, this application can store the second functional page corresponding to the first non-resident service function indicated by the triggering operation detected through the first functional page into the page stack container corresponding to the first non-resident service function. The second functional page, as the top page in the page stack container corresponding to the first non-resident service function, can be displayed in the application window of the target application, thereby switching the first functional page displayed in the application window to the second functional page, and realizing accurate page switching within the target application.

[0046] It is understandable that, for the permanent service entry points corresponding to multiple permanent service functions and the temporary function entry points corresponding to the first non-permanent service function in the function navigation bar, when this application displays the function page of any of the aforementioned permanent service functions and the first non-permanent service functions in the application window of the target application, this application can adjust the function entry point of the specific service function of any page currently displayed in the application window to the selected state in the function navigation bar, so as to distinguish the function entry point of the specific service function of any page currently displayed in the application window from the function entry points of other service functions in the function navigation bar, ensuring that the user intuitively understands which service function's function page the user is currently browsing in the application window.

[0047] The technical solution provided in this application embodiment sets a function navigation bar within the application window of the target application. This function navigation bar can include persistent function entries corresponding to multiple persistent service functions. Upon entering the target application, a first function page can be displayed in the application window via a page stack container corresponding to the first persistent service function under the main page container. This first function page can be the function page of the first persistent service function. When a trigger operation to enter a second function page corresponding to a first non-persistent service function is detected through the first function page, a page stack container corresponding to the first non-persistent service function is created through the main page container, and a temporary function entry corresponding to the first non-persistent service function is created and displayed in the function navigation bar. Then, the page stack container corresponding to the first non-persistent service function is adjusted to a display state through the main page container, and the first function page displayed in the application window is switched to the second function page through the page stack container corresponding to the first non-persistent service function, thereby achieving accurate page switching within the target application. Therefore, by displaying persistent and temporary function entries in the function navigation bar of the target application's application window, this application can ensure the efficiency and speed of page switching within the target application, eliminating the need to frequently return to the application's main page to perform page switching operations. This greatly reduces the cumbersomeness of page switching operations within the target application, improves the smoothness and effectiveness of page switching within the target application, and further optimizes the page switching performance within the target application.

[0048] As an optional implementation scheme in this application embodiment, in order to accurately distinguish between persistent and non-persistent service functions in the function navigation bar, the function navigation bar in this application can be divided into a persistent section and a temporary section. The persistent section can include the persistent function entry points corresponding to each persistent service function, while the temporary section can include the temporary function entry points corresponding to enabled non-persistent service functions, thereby achieving partitioned display of persistent and temporary function entry points in the function navigation bar.

[0049] Furthermore, since the persistent service functions defined within the target application are the most frequently used services by users, it indicates that users may frequently switch between the relevant function pages of each persistent service function within the target application, causing the target application to continuously switch between different persistent service functions. Therefore, to ensure efficient and convenient switching between the corresponding function pages of each persistent service function within the target application, the persistent function entry points corresponding to each persistent service function in this application can be arranged sequentially in the persistent section of the function navigation bar.

[0050] The non-resident service functions already enabled within the target application are those that users use infrequently. This indicates that users typically only use a particular non-resident service function once in a relatively long period, thus the target application does not frequently switch between the related function pages of various non-resident services. Therefore, for non-resident service functions, this application can pre-set the specific number of temporary function entries corresponding to non-resident service functions displayed in the function navigation bar, and support different display formats for these temporary function entries under different display numbers. That is, the function navigation bar in this application can support displaying one or more temporary function entries corresponding to non-resident service functions. Therefore, the specific display format used for these temporary function entries in the function navigation bar will differ depending on the number of times it supports displaying them.

[0051] Therefore, if the function navigation bar supports displaying temporary function entries corresponding to non-resident service functions, the temporary function entries corresponding to non-resident service functions can be placed in the temporary section of the function navigation bar by enabling time-series replacement; while if the function navigation bar supports displaying temporary function entries corresponding to multiple non-resident service functions, the temporary function entries corresponding to non-resident service functions can be placed in the temporary section of the function navigation bar by stacking the entries.

[0052] In other words, if the function navigation bar can only display a temporary function entry corresponding to a non-resident service function at a time, this application can place the temporary function entry corresponding to the most recently enabled non-resident service function in the target application within the temporary section of the function navigation bar. Each time a new non-resident service function is enabled within the target application, the temporary section of the function navigation bar can directly replace the currently displayed temporary function entry corresponding to the non-resident service function with the newly enabled temporary function entry, ensuring that the temporary section of the function navigation bar can only display the temporary function entry corresponding to the most recently enabled non-resident service function at a time. Figure 2a As shown, this application can place the temporary function entry corresponding to the most recently enabled non-resident service function in the target application within the temporary section of the function navigation bar.

[0053] If the function navigation bar can support displaying temporary function entries corresponding to multiple non-resident service functions, then this application can stack the temporary function entries corresponding to multiple enabled non-resident service functions within the target application together and place them in a temporary section of the function navigation bar. When the function navigation bar supports displaying a fixed number of temporary function entries corresponding to multiple non-resident service functions, the number of enabled non-resident service functions within the target application may exceed this fixed number. Therefore, this application can filter out the most recently enabled fixed number of non-resident service functions in the target application in real time, and continuously replace the earliest enabled temporary function entries with the temporary function entries corresponding to the most recently enabled non-resident service functions, thereby stacking the temporary function entries corresponding to the most recently enabled fixed number of non-resident service functions together and placing them in a temporary section of the function navigation bar. Figure 2b As shown, this application can stack the temporary function entries corresponding to multiple non-resident service functions that have been enabled in the target application together and place them in the temporary partition of the function navigation bar.

[0054] In some exemplary implementations, for both the permanent function entry corresponding to the permanent service function and the temporary function entry corresponding to the non-permanent service function, this application can set both the permanent function entry corresponding to the permanent service function and the temporary function entry corresponding to the non-permanent service function as specific function icons that can support users to perform various triggering interactive operations (such as click operations, long press operations, etc.).

[0055] According to one or more embodiments of this application, for the target application, each service function is configured with multiple function pages, such as a main function page and various sub-function pages. Therefore, to ensure seamless page switching within the target application, this application can also support users switching between different function pages under the same service function. Thus, after displaying the first function page in the application window through the page stack container corresponding to the first persistent service function under the main page container, the first function page contains switching trigger controls for other function pages, such as a next page control. Therefore, when the user performs a page switching operation on the switching trigger controls of other function pages, the first function page displayed in the application window can be switched to another function page under the first persistent service function.

[0056] Therefore, in order to ensure a complete page switching for the target application, this application can also respond to the trigger operation of entering the third functional page corresponding to the first resident service function detected by the first functional page, and switch the first functional page displayed in the application window to the third functional page through the page stack container corresponding to the first resident service function.

[0057] In other words, after displaying the first function page under the first persistent service function in the application window of the target application, this application can detect in real time whether the user has executed a trigger operation on the switching trigger control set for the third function page of the first persistent service function within the first function page, in order to determine whether it is necessary to switch from the first function page to the third function page of the first persistent service function. Therefore, when a trigger operation to enter the third function page of the first persistent service function is detected through the first function page, this application will also keep the page stack container corresponding to the first persistent service function in the display state, and adjust the stack positions of the first and third function pages through the page stack container corresponding to the first persistent service function, thereby switching the first function page displayed in the application window of the target application to the third function page.

[0058] In some embodiments, in order to achieve accurate switching from the first functional page to the third functional page in the application window of the target application, this application generates a third functional page when a trigger operation to enter the third functional page of the first persistent service function is detected through the first functional page; stores the third functional page in the page stack container corresponding to the first persistent service function; and displays the top page of the stack container corresponding to the first persistent service function in the application window through the page stack container corresponding to the first persistent service function, so that the first functional page displayed in the application window is switched to the third functional page.

[0059] Specifically, when a trigger operation to enter the third functional page of the first persistent service function is detected through the first functional page, this application first obtains various page content information related to the third functional page to generate the third functional page. Then, the third functional page can be stored sequentially in the stack container corresponding to the first persistent service function, thus storing the third functional page as the top page in the stack container. Therefore, while the stack container corresponding to the first persistent service function remains in the display state, the top page in the stack container can be displayed in the application window, thereby switching the first functional page displayed in the application window to the third functional page, thus achieving accurate page switching within the same service function of the target application.

[0060] The technical solution provided in this application embodiment, when a trigger operation to enter the third functional page of the first persistent service function is detected through the first functional page, switches the first functional page displayed in the application window to the third functional page through the page stack container corresponding to the first persistent service function, so as to realize accurate page switching under the same service function in the target application and ensure comprehensive page switching in the target application.

[0061] According to one or more embodiments of this application, the function navigation bar in the application window of the target application can include multiple persistent function entries corresponding to persistent service functions. Therefore, to ensure quick page switching within the target application, this application allows users to quickly switch between browsing related function pages of different persistent service functions by triggering the persistent function entries corresponding to different persistent service functions in the function navigation bar. Thus, after displaying the first function page in the application window through the page stack container corresponding to the first persistent service function under the main page container, multiple persistent function entries corresponding to persistent service functions will exist in the function navigation bar. These persistent function entries can serve as page switching trigger controls for each persistent service function. Therefore, when a user performs a trigger operation on a persistent function entry corresponding to a persistent service function other than the first persistent service function in the function navigation bar, the first function page displayed in the application window can be switched to a related function page under another persistent service function.

[0062] Therefore, in order to ensure quick page switching in the target application, this application can respond to the trigger operation of the persistent function entry corresponding to the second persistent service function in the function navigation bar, adjust the page stack container corresponding to the second persistent service function to the display state through the main page container, and display the top page of the stack container corresponding to the second persistent service function in the application window through the page stack container corresponding to the second persistent service function. The top page is the function page of the second persistent service function.

[0063] The second persistent service function can be any other persistent service function in the function navigation bar besides the first persistent service function. The function navigation bar will contain multiple persistent function entry points corresponding to different persistent service functions.

[0064] Therefore, regardless of whether the first function page of the first persistent service function or the second function page of the first non-persistent service function is displayed in the application window of the target application, this application can detect in real time whether the user has performed a trigger operation on the persistent function entry corresponding to the second persistent service function in the function navigation bar, so as to determine whether the target application needs to display the relevant function page of the second persistent service function in the application window.

[0065] Therefore, upon detecting a trigger operation targeting the persistent function entry corresponding to the second persistent service function in the function navigation bar, this application can adjust the page stack container corresponding to the specific service function (e.g., the first persistent service function or the first non-persistent service function) of any page currently displayed in the application window to a hidden state via the main page container, while adjusting the page stack container corresponding to the second persistent service function to a visible state. Furthermore, by analyzing the specific page information stored in the page stack container corresponding to the second persistent service function, the top page in the stack container can be determined. This top page can be the main page of the second persistent service function or the sub-page of the function most recently viewed by the user under the second persistent service function. Thus, by using the page stack container corresponding to the second persistent service function, the top page in the stack container can be displayed in the application window of the target application, thereby switching any function page displayed in the application window to the relevant function page of the second persistent service function, achieving accurate page switching within the target application.

[0066] It is understandable that, to ensure a seamless page transition within the target application, the relevant function pages of the second persistent service function will also contain function trigger controls or access links for various non-persistent service functions. This allows users to effectively access and operate multiple function pages of various non-persistent service functions within the relevant function pages of the second persistent service function. Therefore, after displaying the relevant function pages of the second persistent service function in the target application's application window, these pages may also contain function trigger controls or access links for related non-persistent service functions. Thus, if a temporary function entry corresponding to the first non-persistent service function is created and displayed in the function navigation bar, this application can also support users initiating access to and browsing of another non-persistent service function's function page within the relevant function page of the second persistent service function. The following is in conjunction with... Figure 3This application can provide a detailed explanation of the function page switching process for another non-permanent service function when a temporary function entry corresponding to the first non-permanent service function is created and displayed in the function navigation bar.

[0067] Figure 3 The flowchart illustrates a method for switching between function pages of another non-permanent service function when a temporary function entry corresponding to a first non-permanent service function is created and displayed in the function navigation bar, as provided in this application embodiment. This method may specifically include the following steps: S310, in response to the trigger operation of entering the fourth function page corresponding to the second non-resident service function detected by the function page of the second resident service function, a page stack container corresponding to the second non-resident service function is created through the main page container.

[0068] After displaying the function page of the second persistent service function in the application window of the target application, this function page may also contain function trigger controls or access links for related non-persistent service functions. Therefore, this application can use the function page of the second persistent service function to detect whether the user has triggered an operation on the function trigger control or access link of another non-persistent service function (other than the first non-persistent service function) within that function page, thereby determining whether the user has an access request for the related function page of that other non-persistent service function.

[0069] When the system detects that a user has triggered an operation on a function trigger control or access link for another non-resident service function (other than the first non-resident service function) within the function page of the second persistent service function, this application can designate that other non-resident service function as the second non-resident service function in this application, and determine a specific function page that the user specified to access for that second non-resident service function as the fourth function page in this application, thus instructing the user to enter the fourth function page. This fourth function page can be the main function page displayed by default when the second non-resident service function is enabled, or it can be a sub-page of the second non-resident service function represented by the access link triggered by the user.

[0070] Then, in response to the triggering operation of entering the fourth function page corresponding to the second non-permanent service function detected by the function page of the second permanent service function, this application can create a page stack container for the second non-permanent service function through the main page container, so as to manage the relevant function pages browsed by the user under the second non-permanent service function through the page stack container.

[0071] S320: Delete the temporary function entry corresponding to the first non-permanent service function in the function navigation bar, and create and display the temporary function entry corresponding to the second non-permanent service function.

[0072] If the function navigation bar only supports displaying a temporary function entry corresponding to a non-resident service function at a time, in order to ensure the accurate display of the non-resident service function page, this application can delete the temporary function entry corresponding to the first non-resident service function that has been created in the function navigation bar through the main page container, and recreate and display the temporary function entry corresponding to the second non-resident service function in the function navigation bar, so that users can also quickly and effectively access and operate the second non-resident service function in the function navigation bar.

[0073] S330 adjusts the page stack container corresponding to the second non-permanent service function to the display state through the main page container, and switches the function page of the second permanent service function displayed in the application window to the fourth function page through the page stack container corresponding to the second non-permanent service function.

[0074] After creating the page stack container corresponding to the second non-permanent service function through the main page container, and creating and displaying the temporary function entry corresponding to the second non-permanent service function in the function navigation bar, this application can adjust the page stack container corresponding to the second permanent service function to a hidden state through the main page container, and adjust the page stack container corresponding to the second non-permanent service function to a visible state. Furthermore, this application can store the fourth function page corresponding to the second non-permanent service function, indicated by the aforementioned trigger operation detected through the function page of the second permanent service function, into the page stack container corresponding to the second non-permanent service function. This fourth function page is then displayed as the top page in the page stack container corresponding to the second non-permanent service function in the application window of the target application, thereby switching the function page of the second permanent service function displayed in the application window to the fourth function page, achieving accurate page switching within the target application.

[0075] For example, the function navigation bar contains permanent function entries for each permanent service function, and also contains a temporary function entry for a first non-permanent service function A. When a second non-permanent service function B is enabled and accessed through the function page of a second permanent service function, for the second non-permanent service function B, the page stack container corresponding to the first non-permanent service function A is first deleted from the main page container, and a new page stack container is created for the second non-permanent service function B. This page stack container is then made visible. Furthermore, the temporary function entry for the first non-permanent service function A can be deleted from the function navigation bar through the main page container, while a temporary function entry for the second non-permanent service function B is created and displayed in the function navigation bar, thus replacing the temporary function entry for the first non-permanent service function A in the function navigation bar. Additionally, the page stack container corresponding to the second non-permanent service function B is managed by the main page container, allowing the fourth function page corresponding to the second non-permanent service function B to be stored in this page stack container as the top page, displayed in the target application's application window.

[0076] If the function navigation bar can support displaying temporary function entries corresponding to multiple non-permanent service functions, then when a trigger operation to enter the fourth function page corresponding to the second non-permanent service function is detected through the function page of the second permanent service function, this application can create a page stack container corresponding to the second non-permanent service function through the main page container, and create and display the temporary function entry corresponding to the second non-permanent service function in the function navigation bar, stacking it together with the temporary function entry corresponding to the first non-permanent service function, and placing it in the temporary partition of the function navigation bar. Furthermore, the main page container adjusts the page stack container corresponding to the second non-permanent service function to a display state, and through the page stack container corresponding to the second non-permanent service function, the function page of the second permanent service function displayed in the application window is switched to the fourth function page.

[0077] The technical solution provided in this application, when a trigger operation to enter the fourth function page corresponding to the second non-resident service function is detected through the function page of the second permanent service function, creates a page stack container corresponding to the second non-resident service function through the main page container, deletes the temporary function entry corresponding to the first non-resident service function in the function navigation bar, and creates and displays the temporary function entry corresponding to the second non-resident service function. Then, the page stack container corresponding to the second non-resident service function is adjusted to the display state through the main page container, and the function page of the second permanent service function displayed in the application window can be switched to the fourth function page through the page stack container corresponding to the second non-resident service function. This achieves accurate switching and display of pages of different non-resident service functions within the target application, ensuring efficient and fast page switching within the target application.

[0078] According to one or more embodiments of this application, for the function navigation bar in the application window of the target application, the function navigation bar may include a permanent function entry corresponding to multiple permanent service functions and a temporary function entry corresponding to a first non-permanent service function. Therefore, within the target application, in order to ensure diverse user interactions with non-permanent service functions, this application may also support users in managing the temporary function entry of the first non-permanent service function in the function navigation bar.

[0079] Specifically, after displaying the relevant function page of any service function (such as a persistent service function or an enabled first non-persistent service function) in the application window of the target application, this application can detect in real time whether the user performs a corresponding control trigger operation on the temporary function entry in the function navigation bar, so as to determine whether the display style of the temporary function entry in the function navigation bar needs to be adjusted. Therefore, based on the above solution, this application can also respond to the trigger operation of deleting the temporary function entry in the function navigation bar by deleting the temporary function entry corresponding to the first non-persistent service function in the function navigation bar, and delete the page stack container corresponding to the first non-persistent service function through the main page container.

[0080] In other words, for temporary function entries in the function navigation bar, it not only supports users to perform corresponding page switching operations when the temporary function entry corresponding to the first non-permanent service function is triggered, but also supports users to perform corresponding deletion control operations when the temporary function entry corresponding to the first non-permanent service function is triggered.

[0081] Therefore, to ensure diverse user interactions with the first non-permanent service function in the function navigation bar, this application can set a first type of trigger operation and a second type of trigger operation for the first non-permanent service function in the function navigation bar according to the user's specific interaction needs. The first type of trigger operation can be a click operation, used to indicate a need to switch between related function pages for temporary functions; while the second type of trigger operation can be a long press operation, used to indicate a need to delete or manage the first non-permanent service function.

[0082] Therefore, for the temporary function entry corresponding to the first non-permanent service function displayed in the function navigation bar, this application can detect in real time whether the user has performed a second type of trigger operation on the temporary function entry in the function navigation bar, in order to determine whether the temporary function entry needs to be deleted from the function navigation bar. Thus, when it is detected that the user has performed a second type of trigger operation on the temporary function entry in the function navigation bar, it can be determined that a trigger operation to delete the temporary function entry in the function navigation bar has been detected. In this way, the temporary function entry corresponding to the first non-permanent service function can be directly deleted from the function navigation bar through the main page container, and the page stack container corresponding to the first non-permanent service function can be deleted through the main page container, so that the first non-permanent service function can be successfully reactivated subsequently.

[0083] In some embodiments, if the function navigation bar only supports displaying a temporary function entry corresponding to a non-resident service function at a time, then after detecting a triggering operation to delete the temporary function entry in the function navigation bar, as follows: Figure 4a As shown, this application can determine that the specific deletion control operation supported by the first non-resident service function can be a temporary function deletion operation. Based on this, a deletion confirmation control (such as a deletion confirmation bubble) is generated for the first non-resident service function to serve as the deletion response page of the first non-resident service function. The deletion confirmation control is displayed in the application window of the target application at the associated position of the temporary function entry in the function navigation bar, so that the user can delete the temporary function entry corresponding to the first non-resident service function in the function navigation bar in a timely and effective manner, and complete the accurate deletion response of the display style of the temporary function entry in the function navigation bar.

[0084] If the function navigation bar supports displaying temporary function entries corresponding to multiple non-permanent service functions, then in response to the user's temporary function management operation triggered by the overall entry of the stacked temporary function entries of multiple non-permanent service functions in the function navigation bar, such as... Figure 4bAs shown, this application can determine that the specific control operations supported by each non-resident service function in the function navigation bar can include temporary function deletion, temporary function sorting, and temporary function dragging operations, etc., thereby generating a control operation window (e.g., a list of non-resident service functions that supports deletion, sorting, and dragging of each non-resident service function) for multiple non-resident service functions, which serves as the corresponding control response page. This control response page is then displayed in the application window of the target application in the associated area after the stacking of multiple temporary function entries in the function navigation bar, so that users can promptly and effectively perform corresponding control adjustments on the specific display style of each non-resident service function within this control response page, thereby completing the accurate control response for each non-resident service function in the function navigation bar.

[0085] The technical solution provided in this application, when a triggering operation to delete a temporary function entry in the function navigation bar is detected, deletes the temporary function entry corresponding to the first non-permanent service function in the function navigation bar, and deletes the page stack container corresponding to the first non-permanent service function through the main page container, thereby enabling users to perform diversified control and interaction on the first non-permanent service function in the function navigation bar, and enhancing the functional interaction effect when switching pages within the target application.

[0086] As an optional implementation in this application, for any service function's function page displayed in the application window of the target application, the function page can be the main function page of that service function or any sub-page of that service function after one or more page switches are performed through the main function page. Since the main function page of any service function is usually the first page displayed when the service function is accessed, it is mainly used to display some overall functional information of the service function; while the sub-pages of any service function, as specific pages under the main function page, are mainly used to display more detailed information or provide specific detailed services under that service function.

[0087] Therefore, it can be seen that the content of functional subpages is usually designed to support the core details within the main functional page, or to provide users with more in-depth functional information, making users pay more attention to the content of the functional subpages. Therefore, to ensure a smooth visual experience during page transitions, this application can also provide a choice between full-screen and non-full-screen display for any service function's functional page displayed in the application window of the target application, whether it is a main functional page or a subpage. Furthermore, this application can provide a detailed explanation of the process of displaying any service function's functional page in full-screen or non-full-screen mode within the application window of the target application.

[0088] Figure 5aA flowchart illustrating a method for full-screen switching of function pages for any service function displayed in an application window provided in this embodiment of the application. This method may specifically include the following steps: S510 generates a corresponding full-screen browsing control within the function page of any service function displayed in the application window.

[0089] For any service function page displayed in the application window of the target application, in order to ensure that the user can focus more on browsing the content of the function page, this application will further generate a corresponding full-screen browsing control within the function page when displaying the function page in the application window through the page stack container corresponding to the specific service function, so as to support the user to realize the full-screen display of the function page by triggering the full-screen browsing control.

[0090] So, when displaying this function page in the application window through the page stack container corresponding to the specific service function it belongs to, such as... Figure 5b As shown, the full-screen browsing control on the function page will also be displayed simultaneously.

[0091] S520, in response to a trigger operation on the full-screen browsing control, sets the function navigation bar to a hidden state through the main page container and displays a visually optimized full-screen browsing page of the function page in the application window, the full-screen browsing page including a full-screen exit control.

[0092] To ensure accurate display of pages within the target application, for any service function page displayed in the application window of the target application, when the page stack container corresponding to the specific service function displays the function page in the application window, this application can also detect in real time whether the user executes the corresponding trigger operation on the full-screen browsing control within the function page to determine whether the function page has a full-screen display requirement.

[0093] Therefore, when a user executes a trigger operation on the full-screen browsing control within the function page, it indicates that the function page requires full-screen display. Thus, to achieve full-screen display of the function navigation bar, this application can directly set the function navigation bar to a hidden state through the main page container, and perform visual optimization processing on the page specifications of the function page to support full-screen display based on the application window specifications of the target application, thereby obtaining the corresponding full-screen browsing page. This full-screen browsing page has the same page content as the function page and supports full-screen display within the application window of the target application.

[0094] Furthermore, in order to enable normal page switching subsequently, such as Figure 5bAs shown, this application can also generate a corresponding full-screen exit control within the aforementioned full-screen browsing page and display the full-screen browsing page in the application window of the target application. This allows users to trigger the full-screen exit control within the full-screen browsing page to return to the original function page for default display, facilitating subsequent page switching operations.

[0095] It should be noted that since the page stack container corresponding to the specific service function containing this function page may also have a corresponding sub-function navigation bar to guide the user to switch pages under the corresponding service function, when the user is detected to have performed a corresponding trigger operation on the full-screen browsing control within this function page, this application, through the main page container, will not only hide the function navigation bar, but also hide the sub-function navigation bar in the page stack container corresponding to the specific service function containing this function page, ensuring the full-screen display of this function page.

[0096] S530, in response to a trigger operation on the fullscreen exit control, sets the function navigation bar to the display state through the main page container and redisplays the function page in the application window.

[0097] After displaying a visually optimized full-screen browsing page of any functional page in the application window of the target application, this application can also detect in real time whether the user executes the corresponding trigger operation for the full-screen exit control in the full-screen browsing page, so as to determine whether the full-screen browsing page needs to exit full-screen and return to the original functional page for display.

[0098] Therefore, when a user executes a trigger operation on the full-screen exit control within the full-screen browsing page, it indicates that the full-screen browsing page needs to exit full-screen display. Thus, for the function navigation bar, in order to achieve the normal default display of the function page, this application can use the main page container to reset the function navigation bar from a hidden state to a visible state, and as follows... Figure 5b As shown, the original function page is re-displayed in the application window of the target application through the page stack container corresponding to the specific service function where the function page is located.

[0099] It should be noted that when any functional page is displayed in full-screen mode, if the main page container not only hides the functional navigation bar but also hides the sub-functional navigation bar within the page stack container corresponding to the specific service function, then when the functional page exits full-screen mode, this application will, through the main page container, not only restore the functional navigation bar from hidden to displayed but also restore the sub-functional navigation bar within the page stack container corresponding to the specific service function from hidden to displayed.

[0100] The technical solution provided in this application embodiment enables the full-screen display of any service function's functional page in the application window of the target application, based on the full-screen browsing control within the functional page and the full-screen exit control within the visually optimized full-screen browsing page, thereby enhancing the user's focus on the content of any service function's functional page.

[0101] Figure 6 This is a schematic block diagram of a page switching device provided in an embodiment of this application. Figure 6 As shown, the application window of the target application includes a function navigation bar, which includes persistent function entries corresponding to multiple persistent service functions. The device 600 may include: The persistent function display module 610 is used to display the first function page in the application window through the page stack container corresponding to the first persistent service function under the main page container; wherein, the first function page is the function page of the first persistent service function. The temporary function creation module 620 is used to respond to the trigger operation of entering the second function page corresponding to the first non-permanent service function detected by the first function page, create a page stack container corresponding to the first non-permanent service function through the main page container, and create and display the temporary function entry corresponding to the first non-permanent service function in the function navigation bar. The page switching module 630 is used to adjust the page stack container corresponding to the first non-permanent service function to the display state through the main page container, and to switch the first function page displayed in the application window to the second function page through the page stack container corresponding to the first non-permanent service function.

[0102] In some implementations, the page switching module 630 can also be used for: In response to the triggering operation of entering the third function page corresponding to the first permanent service function detected by the first function page, the first function page displayed in the application window is switched to the third function page through the page stack container corresponding to the first permanent service function.

[0103] In some implementations, the page switching module 630 is specifically used for: Generate a third-function page; Store the third function page into the page stack container corresponding to the first persistent service function; By using the page stack container corresponding to the first persistent service function, the top page of the stack container corresponding to the first persistent service function is displayed in the application window, so that the first function page displayed in the application window is switched to the third function page.

[0104] In some implementations, the page switching module 630 can also be used for: In response to a trigger operation targeting the persistent function entry corresponding to the second persistent service function in the function navigation bar, the page stack container corresponding to the second persistent service function is adjusted to a display state through the main page container, and the top page of the stack container corresponding to the second persistent service function is displayed in the application window through the page stack container corresponding to the second persistent service function. The top page is the function page of the second persistent service function.

[0105] In some implementations, the page switching device 600 may further include a temporary function entry deletion response module. This temporary function entry deletion response module can be used for: In response to the trigger operation of deleting the temporary function entry in the function navigation bar, the temporary function entry corresponding to the first non-permanent service function is deleted from the function navigation bar, and the page stack container corresponding to the first non-permanent service function is deleted through the main page container.

[0106] In some implementations, the page switching module 630 can also be used for: In response to the trigger operation of entering the fourth function page corresponding to the second non-permanent service function detected through the function page of the second permanent service function, a page stack container corresponding to the second non-permanent service function is created through the main page container; Delete the temporary function entry corresponding to the first non-permanent service function in the function navigation bar, and create and display the temporary function entry corresponding to the second non-permanent service function. The main page container is used to adjust the page stack container corresponding to the second non-permanent service function to the display state, and the function page of the second permanent service function displayed in the application window is switched to the fourth function page through the page stack container corresponding to the second non-permanent service function.

[0107] In some implementations, the page switching device 600 may also include a full-screen browsing module. This full-screen browsing module can be used for: For any service function page displayed in the application window, generate a corresponding full-screen browsing control within the function page; In response to a trigger operation on the full-screen browsing control, the function navigation bar is set to a hidden state through the main page container, and a visually optimized full-screen browsing page of the function page is displayed in the application window, the full-screen browsing page including a full-screen exit control; In response to the triggering operation of the fullscreen exit control, the function navigation bar is set to the display state through the main page container, and the function page is redisplayed in the application window.

[0108] In this embodiment, a function navigation bar is set within the application window of the target application. This function navigation bar can include persistent function entries corresponding to multiple persistent service functions. Upon entering the target application, a first function page can be displayed in the application window via a page stack container corresponding to the first persistent service function under the main page container. This first function page can be the function page of the first persistent service function. When a trigger operation to enter a second function page corresponding to a first non-persistent service function is detected through the first function page, a page stack container corresponding to the first non-persistent service function is created through the main page container, and a temporary function entry corresponding to the first non-persistent service function is created and displayed in the function navigation bar. Then, the page stack container corresponding to the first non-persistent service function is adjusted to a display state through the main page container, and the first function page displayed in the application window is switched to the second function page through the page stack container corresponding to the first non-persistent service function, thereby achieving accurate page switching within the target application. Therefore, by displaying persistent and temporary function entries in the function navigation bar of the target application's application window, this application can ensure the efficiency and speed of page switching within the target application, eliminating the need to frequently return to the application's main page to perform page switching operations. This greatly reduces the cumbersomeness of page switching operations within the target application, improves the smoothness and effectiveness of page switching within the target application, and further optimizes the page switching performance within the target application.

[0109] It should be understood that the device embodiments and method embodiments can correspond to each other, and similar descriptions can be referred to the method embodiments. To avoid repetition, further details will not be provided here. Specifically, Figure 6 The apparatus 600 shown can execute any of the method embodiments provided in this application, and the foregoing and other operations and / or functions of each module in the apparatus 600 are respectively for implementing the corresponding processes in the various methods of the embodiments of this application. For the sake of brevity, they will not be described in detail here.

[0110] The apparatus 600 of this application embodiment has been described above from the perspective of functional modules in conjunction with the accompanying drawings. It should be understood that this functional module can be implemented in hardware, in software instructions, or in a combination of hardware and software modules. Specifically, the steps of the method embodiments in this application can be completed by integrated logic circuits in the processor's hardware and / or by software instructions. The steps of the method applied in this application embodiment can be directly manifested as execution by a hardware decoding processor, or by a combination of hardware and software modules in the decoding processor. Optionally, the software module can be located in a mature storage medium in the art, such as random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, etc. This storage medium is located in memory, and the processor reads information from the memory and, in conjunction with its hardware, completes the steps in the above method embodiments.

[0111] Figure 7 A schematic block diagram of an electronic device provided in an embodiment of this application.

[0112] like Figure 7 As shown, the electronic device 700 may include: The system includes a memory 710 and a processor 720. The memory 710 stores computer programs and transfers the program code to the processor 720. In other words, the processor 720 can retrieve and run the computer program from the memory 710 to implement the methods described in the embodiments of this application.

[0113] For example, the processor 720 can be used to execute the above-described method embodiments according to instructions in the computer program.

[0114] In some embodiments of this application, the processor 720 may include, but is not limited to: General-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc.

[0115] In some embodiments of this application, the memory 710 includes, but is not limited to: Volatile memory and / or non-volatile memory. Non-volatile memory can be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. Volatile memory can be random access memory (RAM), used as an external cache. By way of example, but not limitation, many forms of RAM are available, such as Static RAM (SRAM), Dynamic RAM (DRAM), Synchronous DRAM (SDRAM), Double Data Rate SDRAM (DDR SDRAM), Enhanced SDRAM (ESDRAM), Synchronous Link DRAM (SLDRAM), and Direct Rambus RAM (DR RAM).

[0116] In some embodiments of this application, the computer program may be divided into one or more modules, which are stored in the memory 710 and executed by the processor 720 to perform the method provided in this application. The one or more modules may be a series of computer program instruction segments capable of performing a specific function, which describe the execution process of the computer program in the electronic device.

[0117] like Figure 7 As shown, the electronic device may further include: Transceiver 730, which can be connected to processor 720 or memory 710.

[0118] The processor 720 can control the transceiver 730 to communicate with other devices; specifically, it can send information or data to other devices or receive information or data sent by other devices. The transceiver 730 may include a transmitter and a receiver. The transceiver 730 may further include antennas, and the number of antennas may be one or more.

[0119] It should be understood that the various components in the electronic device are connected through a bus system, which includes a data bus, a power bus, a control bus, and a status signal bus.

[0120] This application also provides a computer storage medium storing a computer program thereon, which, when executed by a computer, enables the computer to perform the methods of the above-described method embodiments. Alternatively, this application also provides a computer program product containing instructions that, when executed by a computer, cause the computer to perform the methods of the above-described method embodiments.

[0121] When implemented using software, it can be implemented entirely or partially as a computer program product. This computer program product includes one or more computer instructions. When these computer program instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of this application are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another via wired (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium accessible to a computer or a data storage device such as a server or data center that integrates one or more available media. The available medium can be a magnetic medium (e.g., floppy disk, hard disk, magnetic tape), an optical medium (e.g., digital video disc (DVD)), or a semiconductor medium (e.g., solid-state disk (SSD)).

[0122] Those skilled in the art will recognize that the modules and algorithm steps of the various examples described in conjunction with the embodiments claimed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0123] In the several embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of modules is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple modules or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between apparatuses or modules may be electrical, mechanical, or other forms.

[0124] The modules described as separate components may or may not be physically separate. The components shown as modules may or may not be physical modules; that is, they may be located in one place or distributed across multiple network units. Some or all of the modules can be selected to achieve the purpose of this embodiment according to actual needs. For example, the functional modules in the various embodiments of this application may be integrated into one processing module, or each module may exist physically separately, or two or more modules may be integrated into one module.

[0125] The above are merely specific embodiments of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the technical scope disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A method for page switching, characterized in that, The target application's application window includes a function navigation bar, which includes persistent function entries corresponding to multiple persistent service functions. The method includes: The first function page is displayed in the application window through the page stack container corresponding to the first persistent service function under the main page container; wherein, the first function page is the function page of the first persistent service function. In response to the trigger operation of entering the second function page corresponding to the first non-permanent service function detected by the first function page, a page stack container corresponding to the first non-permanent service function is created through the main page container, and a temporary function entry corresponding to the first non-permanent service function is created and displayed in the function navigation bar. The main page container adjusts the page stack container corresponding to the first non-permanent service function to the display state, and the page stack container corresponding to the first non-permanent service function switches the first function page displayed in the application window to the second function page.

2. The method according to claim 1, characterized in that, The method further includes: In response to the trigger operation of entering the third function page corresponding to the first persistent service function detected by the first function page, the first function page displayed in the application window is switched to the third function page through the page stack container corresponding to the first persistent service function.

3. The method according to claim 2, characterized in that, The step of switching the first functional page displayed in the application window to the third functional page through the page stack container corresponding to the first resident service function includes: Generate a third-function page; Store the third function page into the page stack container corresponding to the first persistent service function; By using the page stack container corresponding to the first persistent service function, the top page of the stack container corresponding to the first persistent service function is displayed in the application window, so that the first function page displayed in the application window is switched to the third function page.

4. The method according to claim 1, characterized in that, The method further includes: In response to a trigger operation targeting the persistent function entry corresponding to the second persistent service function in the function navigation bar, the page stack container corresponding to the second persistent service function is adjusted to a display state through the main page container, and the top page of the stack container corresponding to the second persistent service function is displayed in the application window through the page stack container corresponding to the second persistent service function. The top page is the function page of the second persistent service function.

5. The method according to claim 1, characterized in that, The method further includes: In response to the trigger operation of deleting the temporary function entry in the function navigation bar, the temporary function entry corresponding to the first non-permanent service function is deleted from the function navigation bar, and the page stack container corresponding to the first non-permanent service function is deleted through the main page container.

6. The method according to claim 4, characterized in that, The method further includes: In response to the trigger operation of entering the fourth function page corresponding to the second non-permanent service function detected through the function page of the second permanent service function, a page stack container corresponding to the second non-permanent service function is created through the main page container; Delete the temporary function entry corresponding to the first non-permanent service function in the function navigation bar, and create and display the temporary function entry corresponding to the second non-permanent service function. The main page container is used to adjust the page stack container corresponding to the second non-permanent service function to the display state, and the function page of the second permanent service function displayed in the application window is switched to the fourth function page through the page stack container corresponding to the second non-permanent service function.

7. The method according to claim 1, characterized in that, For any service function page displayed in the application window, the method further includes: Generate the corresponding full-screen browsing control within the function page; In response to a trigger operation on the full-screen browsing control, the function navigation bar is set to a hidden state through the main page container, and a visually optimized full-screen browsing page of the function page is displayed in the application window, the full-screen browsing page including a full-screen exit control; In response to the triggering operation of the fullscreen exit control, the function navigation bar is set to the display state through the main page container, and the function page is redisplayed in the application window.

8. A page switching device, characterized in that, The application window of the target application includes a function navigation bar, which includes persistent function entries corresponding to multiple persistent service functions. The device includes: The persistent function display module is used to display the first function page in the application window through the page stack container corresponding to the first persistent service function under the main page container; wherein, the first function page is the function page of the first persistent service function. The temporary function creation module is used to respond to the trigger operation of entering the second function page corresponding to the first non-permanent service function detected by the first function page, create a page stack container corresponding to the first non-permanent service function through the main page container, and create and display the temporary function entry corresponding to the first non-permanent service function in the function navigation bar. The page switching module is used to adjust the page stack container corresponding to the first non-permanent service function to the display state through the main page container, and to switch the first function page displayed in the application window to the second function page through the page stack container corresponding to the first non-permanent service function.

9. An electronic device, characterized in that, include: A processor and a memory, the memory for storing a computer program, the processor for calling and running the computer program stored in the memory to perform the page switching method according to any one of claims 1-7.

10. A computer-readable storage medium, characterized in that, Used to store a computer program that causes a computer to perform a page switching method as described in any one of claims 1-7.

11. A computer program product, comprising a computer program / instructions, characterized in that, When the computer program / instruction is executed by the processor, it implements the page switching method as described in any one of claims 1-7.

Images