Page display method, electronic equipment, storage medium and computer program product

Abstract

The invention provides a page display method, electronic equipment, a storage medium and a computer program product. The method comprises the steps that a first list is displayed on a first page, the first list comprises information of one or more function modules which are not selected to be displayed in all the function modules displayed on the first page, and one or more function modules which are selected to be displayed in all the function modules are further displayed on the first page; detecting a first operation, wherein the first operation is a selection operation for information of one or more function modules which are not displayed; and in response to the first operation, displaying the updated first list on the first page, the updated first list not containing the information of the selected one or more functional modules, and restoring the display of the selected one or more functional modules on the first page. According to the scheme provided by the invention, a plurality of function modules can be checked at the same time, the complexity of interactive operation is simplified, and the development investment of customizing management pages for all the function modules is reduced.

Description

Page display methods, electronic devices, storage media and computer program products Technical Field

[0001] This application relates to the field of computer technology, and in particular to a page display method, electronic device, storage medium, and computer program product. Background Technology

[0002] With the rapid development of computer technology, the content displayed on the pages of various applications is becoming increasingly rich. However, these applications usually provide users with fixed-layout page functional modules. These functional modules cannot be adjusted according to the user's personal preferences, and cannot meet the needs of users who may not be interested in certain functional modules or wish to remove certain functional modules, thus limiting the user experience. Summary of the Invention

[0003] To address the related technical issues, embodiments of this application provide a page display method, an electronic device, a storage medium, and a computer program product.

[0004] The technical solution of this application embodiment is implemented as follows: This application embodiment provides a page display method applied to an electronic device. The method includes: displaying a first list on a first page, the first list containing information on one or more functional modules that are not selected for display among all functional modules that can be displayed on the first page, and also displaying one or more functional modules that are selected for display among all functional modules on the first page; detecting a first operation, the first operation being a selection operation on the information of one or more functional modules that are not displayed; responding to the first operation, displaying an updated first list on the first page, the updated first list not containing information on the selected one or more functional modules, and restoring the display of the selected one or more functional modules on the first page.

[0005] In the above scheme, the method further includes: sending first information to the server, the first information being used to obtain information on all functional modules that are not selected for display in response to the first operation request; receiving a second list sent by the server, the second list containing information on one or more functional modules that are not selected for display; and restoring the display of the selected one or more functional modules on the first page, which includes: using the second list to restore the display of the selected one or more functional modules on the first page.

[0006] In the above scheme, the method further includes: detecting a second operation, the second operation being a deletion operation performed on the first page for the selected display of one or more functional modules; in response to the second operation, not displaying the deleted one or more functional modules on the first page, and displaying an updated first list on the first page, the updated first list containing information about the deleted one or more functional modules.

[0007] In the above scheme, the method further includes: sending second information to the server, the second information being used to obtain information on all functional modules that are not selected for display in response to the second operation request; receiving a third list sent by the server, the third list containing information on one or more functional modules that are not selected for display; and not displaying one or more deleted functional modules on the first page, including: using the third list to not display one or more deleted functional modules on the first page.

[0008] In the above scheme, each functional module that can be displayed on the first page corresponds to a component, and the components of all functional modules are encapsulated in the first component.

[0009] In the above scheme, displaying the first list on the first page includes: displaying the first list on the first page through a second component.

[0010] In the above scheme, displaying the first list on the first page via the second component includes: displaying a floating button on the first page via the second component; detecting a third operation, the third operation being a click operation on the button; and responding to the third operation by displaying the floating first list on the first page via the second component.

[0011] This application also provides an electronic device, including a processor and a memory for storing a computer program that can run on the processor, wherein when the processor runs the computer program, it executes the steps of any of the above-described page display methods.

[0012] This application embodiment also provides a storage medium storing a computer program thereon, which, when executed by a processor, implements the steps of any of the above-described page display methods.

[0013] This application provides a computer program product, including a computer program or computer executable instructions, which, when executed by a processor, implements the steps of any of the above-described page display methods.

[0014] The page display method, electronic device, storage medium, and computer program product provided in this application embodiment display a first list on a first page. The first list contains information about one or more functional modules that are not selected for display among all functional modules that can be displayed on the first page. The first page also displays one or more functional modules that are selected for display among all functional modules. A first operation is detected, which is a selection operation for information about one or more functional modules that are not displayed. In response to the first operation, an updated first list is displayed on the first page, which does not contain information about the selected one or more functional modules, and the selected one or more functional modules are restored to be displayed on the first page. In the above solution, multiple functional modules that the user wants to see can be displayed simultaneously on the first page. Compared to the solution of switching tabs to display different functional modules on the page, the above solution avoids only being able to display one functional module at a time, and can achieve the simultaneous display of multiple functional modules (i.e., multiple functional modules on one page). This makes it easier for users to view (viewing can be understood as the user being able to see the functional module and use the functions provided by the functional module) multiple functional modules at the same time, that is, the user can view all the functional modules they want to view at the same time, thus improving the user experience. At the same time, the first list can display information about one or more functional modules that are not selected for display. Detecting and responding to the first operation can restore the display of one or more selected functional modules on the same page (i.e., the first page). In this way, compared to using two pages, namely a dedicated management page for managing all functional module settings and a display page for displaying functional modules, where users need to perform multiple operations between the two pages when they want to view multiple functional modules or change the functional modules they want to view, the above solution simplifies the complexity of interactive operations, further improves the user experience, and reduces the development investment for customizing management pages for all functional modules. Attached Figure Description

[0015] Figure 1 is a schematic flowchart of a page display method according to an embodiment of this application; Figure 2 is a schematic diagram of a first page according to a first embodiment of this application; Figure 3 is a schematic diagram of a first page according to a second embodiment of this application; Figure 4 is a schematic diagram of a first page according to a third embodiment of this application; Figure 5 is a schematic diagram of a first page according to a fourth embodiment of this application; Figure 6 is a schematic diagram of a first page according to a fifth embodiment of this application; Figure 7 is a schematic diagram of a first page according to a sixth embodiment of this application; Figure 8 is a schematic flowchart of another page display method according to an embodiment of this application; Figure 9 is a schematic diagram of a first page according to a seventh embodiment of this application; Figure 10 is a schematic diagram of the structure of a page display device according to an embodiment of this application; Figure 11 is a schematic diagram of the structure of an electronic device according to an embodiment of this application. Detailed Implementation

[0016] To make the objectives, technical solutions, and advantages of this application clearer, the application will be further described in detail below with reference to the accompanying drawings. The described embodiments should not be regarded as limitations on this application. All other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0017] To allow users to select which functional modules they are interested in to display on the page, or to remove some functional modules they are not interested in or do not need, the relevant technologies provide the following solutions: Solution 1: Place each functional module in a tab, and display different functional modules by switching tabs; by providing a configuration of optional tab items, users can select one or more functional modules they need, as well as one or more functional modules they do not need.

[0018] Option 2: Use two pages. One page provides an indicator of available functional modules for the user; this page can be understood as the management page for all functional modules. The other page displays the functional module selected by the user. If the user wants to view multiple functional modules or change the viewed functional module, they need to perform multiple operations between the two pages to ultimately display the multiple functional modules they want on the page. Viewing a functional module can be understood as the user looking at the functional modules displayed on the page, and changing the viewed functional module can be understood as the user changing the functional modules displayed on the page.

[0019] However, the above two solutions have the following drawbacks: 1. Solution 1 can only display one functional module at a time, which makes it unsuitable for scenarios where multiple functional modules can be viewed simultaneously; 2. Different functional modules are displayed in the same area on the page, which greatly limits the overall layout of the page. Furthermore, since the actual area occupied by each functional module is different, switching may cause the page layout to be readjusted, affecting the user experience.

[0020] 2. Option 2 uses two pages. If multiple functional modules need to be viewed or the viewed functional module needs to be changed, multiple operations are required between the two pages, making the interaction relatively complex. In addition, the page providing the indicator module is equivalent to a management page for all functional modules in the page displaying functional modules. The configurable indicator modules in the management page have a strong correspondence with the functional modules in the page displaying functional modules. It can be said that the management page is customized based on all the functional modules that can be displayed in the page displaying functional modules, and cannot be applied to the functional modules of other pages. That is, this option requires the redevelopment of a corresponding display page for each configurable functional module's management page, which requires a significant investment in program development.

[0021] Based on this, in various embodiments of this application, multiple functional modules that the user wants to display can be displayed simultaneously on the first page. Compared with the solution of switching tabs to display different functional modules on the page, this avoids the situation where only one page functional module can be displayed at the same time, and enables the display of multiple functional modules at the same time (i.e., multiple functional modules are displayed on one page). This makes it convenient for users to view (viewing can be understood as the user being able to see the functional module and use the functions provided by the functional module) multiple functional modules at the same time, that is, the user can view all the functional modules they want to view at the same time, thus improving the user experience. At the same time, the first list can display information of one or more functional modules that are not selected for display. Detecting and responding to the first operation can restore the display of one or more selected functional modules on the same page (i.e., the first page). In this way, compared with using two pages, namely a dedicated management page for managing all functional module settings and a display page for displaying functional modules, where users need to perform multiple operations between the two pages when they want to view multiple functional modules or change the functional modules they want to view, the solution provided by the embodiments of this application can simplify the complexity of interactive operations, further improve the user experience, and reduce the development investment for customizing management pages for all functional modules.

[0022] This application provides a page display method applied to electronic devices, including but not limited to mobile phones, tablets, and desktop computers. As shown in Figure 1, the method includes: Step 101: Displaying a first list on a first page, wherein the first page also displays one or more (one or more can be understood as at least one) functional modules selected for display from all functional modules, and the first list contains information on one or more functional modules that are not selected for display from all functional modules that can be displayed on the first page.

[0023] Step 102: A first operation is detected, which is a selection operation for information of one or more functional modules that are not displayed.

[0024] Step 103: In response to the first operation, an updated first list is displayed on the first page, and the selected one or more functional modules are restored to be displayed on the first page. The updated first list does not contain information about the selected one or more functional modules.

[0025] Here, an application (APP) is installed on the electronic device, so the electronic device can be called a client; correspondingly, the first page refers to the APP page. For example, the APP may include, but is not limited to, a browser, and correspondingly, the first page refers to the World Wide Web page.

[0026] In practical applications, when a user wants to access the first page, a triggering operation is performed, causing the client to send an access request for the first page to the server. The triggering operation varies depending on the type of client. For example, when the client is a browser, the triggering operation may include: the user opening the browser and entering the URL corresponding to the first page, or the user opening the webpage link corresponding to the first page in the browser. When the client is a non-browser app, the triggering operation may include: the user clicking the app icon to request access to the first page (in this case, the first page can be understood as the app's homepage), or clicking a function icon within the app to request access to the first page (in this case, the first page can be understood as the app's function page).

[0027] After detecting the user's triggered action, the client sends an access request to the server for the first page. Specifically, it can obtain the page file of the first page by calling the first application programming interface (API), and obtain relevant information of all functional modules that are not displayed on the first page by calling the second API, such as the identifier (ID) and name of all functional modules. When calling the second API, the user ID and the ID of the first page can be used as parameters of the second API.

[0028] After receiving an access request for the first page, the server returns the page file corresponding to the first page to the client, as well as the IDs and names of all functional modules that are not displayed on the first page.

[0029] In practical applications, the server can be understood as a service program deployed on a server to receive and process client requests. Page files can include, but are not limited to, HyperText Markup Language (HTML) files, Cascading Style Sheets (CSS) files, JavaScript (JS) files, or Extensible Markup Language (XML) files, etc. Page files can contain all functional modules configured on the first page, along with the IDs and names of all functional modules.

[0030] After receiving information about all functional modules not displayed on the first page, the client generates a first list based on this information and displays it on the first page. This first list can include the names of all functional modules not displayed on the first page. Having the server store the information about all functional modules not displayed on the first page ensures that the client receives an accurate first list.

[0031] Of course, in practical applications, the client can also save information about all functional modules that are not displayed on the first page, i.e., save the first list. This can reduce the number of interactions between the client and the server and reduce network overhead.

[0032] The first list may contain information about one or more functional modules that the current user has selected not to display from all the functional modules configured on the first page. The information of the displayed functional modules should allow the user to identify which functional modules are not displayed. For example, the information of the displayed functional modules may include the name of the functional module.

[0033] The client can display the first list on the first page; it is understood that the first list can be displayed on the left or right side of the first page. In actual application, the display position of the first list on the first page can be determined according to actual needs.

[0034] After the client obtains the page file corresponding to the first page returned by the server, it loads only the front-end code corresponding to the functional modules that are not in the first list based on the IDs of all functional modules that are not displayed on the first page, and displays these front-end codes according to the layout format in the page file, thereby displaying one or more functional modules selected from all functional modules on the first page.

[0035] Understandably, when a user visits the first page for the first time, the IDs of all functional modules not displayed on the first page returned by the server can include one or more functional module IDs. These IDs can be obtained by the server counting the IDs of functional modules that other users have collectively chosen not to display. Alternatively, these IDs can be pre-set by the server based on user roles. The server can query the database for the user ID to find the corresponding user role, and then determine the pre-set IDs of the functional modules not to be displayed based on the user role. User roles can be understood as the user's department, job level, etc. In practical applications, the method for determining these functional module IDs can be chosen according to the actual situation.

[0036] Of course, when a user visits the first page for the first time, the IDs of all functional modules that are not displayed on the first page, returned by the server or saved by the client, can be empty. This can be understood as all functional modules being displayed on the first page by default when a user visits the first page for the first time.

[0037] If this is not the user's first visit to the first page, the IDs of all functional modules not displayed on the first page returned by the server or saved by the client are the IDs of one or more functional modules that were not selected for display during the user's last visit to the first page.

[0038] In practical applications, the type of the first page varies depending on the client type. For example, when the client is a browser, the type of the first page includes web pages; when the client is a non-browser app, the type of the first page includes pages provided within the app, such as the app homepage, user center page, and function pages. Function modules can be understood as an independent, clearly defined visual area on the first page, such as a navigation bar module, login / registration module, data display module, and search module.

[0039] In practical applications, when a user wants to restore the display of one or more functional modules on the first page, a first action will occur. This first action can include: the user clicking on information about one or more functional modules in the first list displayed on the first page, or the user long-pressing on information about one or more functional modules in the first list displayed on the first page. In practice, the first action can be set according to the actual situation and is not limited here.

[0040] For example, the functional modules configured on the first page include: functional module 1, functional module 2, and functional module 3. Assuming that functional module 1 is not displayed, functional modules 2 and 3 are displayed. Assuming that the name of functional module 1 is functional module 1, the name of functional module 2 is functional module 2, and the name of functional module 3 is functional module 3, as shown in Figure 2, the functional modules displayed on the first page 201 include: functional module 2 205 and functional module 3 207, and the functional modules not displayed on the first page 201 include: functional module 1; wherein, the first list 209 contains the name of functional module 1; the user is performing a first operation 211 by clicking the name of functional module 1.

[0041] The client detects in real time whether the user has performed a first action. If the first action is detected, the client can respond by updating the first list and restoring the display of one or more functional modules selected by the user through the first action on the first page.

[0042] In practical applications, the first list can be maintained by the client itself. In this case, updating the first list can be understood as the client deleting information about one or more functional modules selected in the first operation from the first list and saving the updated first list on the client. Correspondingly, after detecting the first operation, the client can load the front-end code corresponding to the one or more functional modules selected in the first operation from the page file and display this front-end code according to the layout format in the page file, thereby restoring the display of the one or more functional modules selected by the user through the first operation on the first page.

[0043] The first list can also be maintained by the server. In this case, updating the first list can be understood as the client deleting information about one or more functional modules selected in the first operation from the first list, and sending the information (such as IDs) of the selected functional modules to the server. The server then records (or saves) the information of the selected functional modules. This way, when the user revisits the first page or accesses the first page from a different client, the updated first list can be obtained based on the information of all functional modules that are not displayed, as returned by the server. The updated first list will not be lost because the client stores it in temporary memory, which is then cleared by the system when the user closes the first page, or because the client reinstalls the client on a different electronic device. Accordingly, the client requests the server to obtain updated information (such as IDs) of all functional modules not displayed on the first page, and receives updated information of all functional modules not displayed on the first page from the server; based on the updated information of all functional modules not displayed on the first page, the client only loads the front-end code corresponding to the functional modules not in the updated first list, and displays these front-end codes according to the layout format in the page file, thereby restoring the display of one or more functional modules selected by the user through the first operation on the first page.

[0044] It is understandable that when the client restores the display of one or more functional modules selected by the user through the first operation on the first page, it will not affect the functional modules that were displayed on the first page before the first operation. That is, the functional modules that were displayed on the first page before the first operation will still be displayed on the first page.

[0045] For example, based on the example shown in FIG2, as shown in FIG3, in response to the first operation 211, the client displays the updated first list 210 on the first page 201 and restores the display of functional module 1 203 on the first page 201; functional modules 2 205 and functional module 3 207 that were displayed on the first page 201 before the first operation 211 are still displayed normally.

[0046] In this embodiment of the application, a first list is displayed on a first page. The first list contains information about one or more functional modules that are not selected for display among all functional modules that can be displayed on the first page. The first page also displays one or more functional modules that are selected for display among all functional modules. A first operation is detected. The first operation is a selection operation for the information of one or more functional modules that are not displayed. In response to the first operation, an updated first list is displayed on the first page. The updated first list does not contain the information of the selected one or more functional modules. The selected one or more functional modules are then displayed again on the first page. In the above solution, multiple functional modules that the user wants to see can be displayed simultaneously on the first page. Compared to the solution of switching tabs to display different functional modules on the page, the above solution avoids only being able to display one functional module at a time, and can achieve the simultaneous display of multiple functional modules (i.e., multiple functional modules on one page). This makes it easier for users to view (viewing can be understood as the user being able to see the functional module and use the functions provided by the functional module) multiple functional modules at the same time, that is, the user can view all the functional modules they want to view at the same time, thus improving the user experience. At the same time, the first list can display information about one or more functional modules that are not selected for display. Detecting and responding to the first operation can restore the display of one or more selected functional modules on the same page (i.e., the first page). Thus, compared to using two pages, namely a dedicated management page for managing all functional module settings and a display page for displaying functional modules, where users need to perform multiple operations between the two pages to view multiple functional modules or change the functional modules they want to view, the above solution simplifies the complexity of interactive operations, further improves the user experience, and reduces the development investment for customizing management pages for all functional modules.

[0047] When the first list is maintained by the server, in order to restore the display of all the functional modules selected in the first operation on the first page, the client can request the second list from the server. In this way, when the user revisits the first page or accesses the first page from a different client, the latest information on one or more functional modules that were not selected for display can be obtained. The updated first list will not be lost because the client saves it in temporary memory and the temporary memory is cleared by the system when the user closes the first page, or because the client reinstalls the client on a different electronic device.

[0048] Based on this, in an optional embodiment, the method may further include: sending first information to a server, the first information being used to obtain information on all functional modules that are not selected for display in response to the first operation request; receiving a second list sent by the server, the second list containing information on one or more functional modules that are not selected for display; and restoring the display of the selected one or more functional modules on the first page, which includes: using the second list to restore the display of the selected one or more functional modules on the first page.

[0049] Here, in response to the first operation, the client can send first information to the server to obtain the second list; the first information may include the IDs of one or more functional modules, page IDs, and user IDs selected in the first operation.

[0050] The server can record information about all functional modules selected by each user that are not displayed on the first page. When the server receives the IDs of one or more functional modules, page IDs, and user IDs selected by the client in the first operation, it can delete the IDs of the functional modules under that user and the corresponding information of the functional modules based on the IDs of the functional modules, page IDs, and user IDs, to obtain a second list, and send the second list to the client. For example, the second list may include the IDs and names of all functional modules that are not displayed on the first page after being updated for the first operation.

[0051] In practical applications, the client can call the third API to send the IDs of one or more functional modules selected in the first operation, the page ID, and the user ID to the server. The server then uses these IDs to delete the IDs of the functional modules under that user and their corresponding information, resulting in a second list. Simultaneously, the client calls the second API to send the page ID and user ID to the server, which then returns the second list based on these IDs.

[0052] Understandably, in practical applications, the functions of the second and third APIs can be merged to create a new API. In this way, the client can call the new API and send the IDs, page IDs, and user IDs of one or more functional modules selected in the first operation to the server. The server then deletes the IDs of the functional modules under that user and the corresponding functional module information based on the functional module IDs, page IDs, and user IDs, obtains the second list, and returns the second list to the client.

[0053] After receiving the second list sent by the server, the client uses the second list to load only the front-end code corresponding to the functional modules whose functional module IDs are not in the second list, and displays these front-end codes according to the layout format in the page file, thereby restoring the display of one or more functional modules selected by the user through the first operation on the first page.

[0054] It is understandable that the second list sent by the server does not contain information (such as IDs) of one or more functional modules selected through the first operation. Thus, the first page can restore the display of one or more functional modules selected through the first operation.

[0055] In this embodiment, a first piece of information is sent to the server, which is used to obtain information on all functional modules that are not selected for display in response to the first operation request; a second list sent by the server is received, which contains information on one or more functional modules that are not selected for display; using the second list, the selected one or more functional modules are restored to be displayed on the first page. This allows for the restoration of the display of the functional modules needed by the user on demand. Since the first page can display all functional modules at the same time, restoring the display of the functional modules needed by the user does not affect the overall page layout, resulting in a good user interaction experience.

[0056] To allow users to hide (or delete) specific functional modules according to their needs and preferences, the client can set one or more functional modules currently displayed on the first page to be hidden as needed. Based on this, in some optional embodiments, the method further includes: detecting a second operation, the second operation being a deletion operation performed on the first page targeting the selected one or more functional modules; in response to the second operation, not displaying the deleted one or more functional modules on the first page, and displaying an updated first list on the first page, the updated first list containing information about the deleted one or more functional modules.

[0057] Here, when a user wants to hide one or more functional modules currently displayed on the first page, a second operation will be performed. This second operation can include: the user clicking the delete button corresponding to one or more functional modules currently displayed on the first page, or the user long-pressing one or more functional modules currently displayed on the first page. In practical applications, the second operation can be set according to the actual situation and is not limited here.

[0058] The client detects in real time whether the user has performed a second action. If the user performs a second action, the client can respond by not displaying one or more deleted functional modules on the first page and displaying an updated first list on the first page.

[0059] In this context, one or more deleted functional modules can be understood as one or more functional modules selected through the second operation.

[0060] When the client maintains the initial list itself, displaying the updated initial list on the first page can be understood as the client adding information about one or more functional modules selected by the second operation to the initial list, obtaining the updated initial list, displaying the updated initial list on the first page, and saving the updated initial list on the client. Correspondingly, after detecting the second operation, the client can, based on the front-end code corresponding to the one or more functional modules selected by the second operation in the page file, set the display style of the corresponding functional modules to transparent and hidden, so that these functional modules are not displayed on the first page, thus achieving the goal of not displaying one or more deleted functional modules on the first page.

[0061] When the server maintains the initial list, displaying the updated initial list on the first page can be understood as the client adding information about one or more functional modules selected in the second operation to the initial list, obtaining the updated initial list, displaying the updated initial list on the first page, and sending relevant information (such as IDs) of the one or more functional modules selected in the second operation to the server, which then records this information. By recording (or saving) the relevant information of the one or more functional modules selected in the second operation on the server, it can be ensured that each second operation by the user is recorded by the server. This way, when the user revisits the initial page or accesses the initial page from a different client, the latest initial list can be obtained based on the information of all functional modules not currently displayed, as returned by the server. The updated initial list will not be lost due to the client storing it in temporary memory, which is then cleared by the system when the user closes the initial page, or due to changing electronic devices and reinstalling the client. Accordingly, upon detecting the second operation, the client can request updated information from the server regarding all functional modules not displayed on the first page, and receive updated information from the server regarding all functional modules not displayed on the first page. Based on the updated information (such as IDs) of all functional modules not displayed on the first page, the client only loads the front-end code corresponding to the functional modules not in the updated first list, and displays this front-end code according to the layout format in the page file, thereby restoring the display of one or more functional modules selected by the user through the first operation on the first page. It is understood that the updated first list sent by the server contains information about one or more functional modules selected through the second operation; thus, one or more deleted functional modules may not be displayed on the first page.

[0062] It is understandable that when the client sets one or more functional modules selected by the user through the second operation to not be displayed, it will not affect other functional modules of one or more functional modules that are currently displayed on the first page. That is, functional modules that are not selected by the second operation will still be displayed on the first page.

[0063] In this embodiment, a second operation is detected, which is a deletion operation performed on the first page for one or more selected functional modules. In response to the second operation, the deleted one or more functional modules are not displayed on the first page, and an updated first list containing information about the deleted one or more functional modules is displayed on the first page. In this way, by responding to the second operation, users can easily hide specific functional modules according to their needs and preferences, realizing dynamic customization of the first page for different users. In addition, compared with using two pages and setting up a dedicated management page for managing all functional modules, users need to perform multiple operations between the two pages when they want to view multiple functional modules or change the functional modules they want to view, ultimately completing the solution of displaying multiple functional modules on the page. The above solution can simplify the complexity of interactive operations and reduce the development investment of customizing a management page for all functional modules.

[0064] When the first list is maintained by the server, in order to prevent all the functional modules selected by the second operation from being displayed on the first page, the client can request a third list from the server. In this way, when the user revisits the first page or accesses the first page from a different client, the client can obtain the latest information on one or more functional modules that are not selected for display. This prevents the client from losing the updated first list because the temporary memory is cleared by the system when the user closes the first page, or because the client reinstalls the client on a different electronic device.

[0065] Based on this, in an optional embodiment, the method may further include: sending second information to a server, the second information being used to obtain information on all functional modules that are not selected for display in response to the second operation request; receiving a third list sent by the server, the third list containing information on one or more functional modules that are not selected for display; and the step of not displaying one or more deleted functional modules on the first page includes: using the third list to not display one or more deleted functional modules on the first page.

[0066] Here, the client can send a second piece of information to the server to obtain a third list; the second piece of information may include: the ID of one or more functional modules selected in the second operation, the page ID, and the user ID.

[0067] The server can record information about all functional modules selected by each user that are not displayed on the first page. When the server receives the IDs of one or more functional modules, page IDs, and user IDs selected by the client in the second operation, it can add and save the IDs of the functional modules under that user and the corresponding information of the functional modules based on the IDs of the functional modules, page IDs, and user IDs, and obtain a third list. The third list may include the IDs and names of all functional modules that are not displayed on the first page after the second operation.

[0068] In practical applications, in response to the second operation, the client can call the fourth API to send the IDs of one or more functional modules selected in the second operation, the page ID, and the user ID to the server. Based on the functional module IDs, page IDs, and user IDs, the server adds and saves the IDs of the functional modules under that user and the corresponding functional module information, obtaining the third list. Simultaneously, the client calls the second API to send the page ID and user ID to the server, and the server returns the third list based on the page ID and user ID.

[0069] Understandably, in practical applications, the functions of the second and fourth APIs can be merged to create a new API. In this way, the client can call the new API to send the IDs, page IDs, and user IDs of one or more functional modules selected in the second operation to the server. The server, based on the functional module IDs, page IDs, and user IDs, adds and saves the IDs of the functional modules under that user and the corresponding functional module information, obtains the third list, and returns the third list to the client.

[0070] In practical applications, the first API, second API, third API, and fourth API are different APIs. As can be seen from the description above, the client and server interact through APIs.

[0071] After receiving the third list from the server, the client uses this list to load only the front-end code corresponding to the functional modules whose IDs are not in the third list, and displays this front-end code according to the layout format in the page file. This prevents one or more deleted functional modules from being displayed on the first page. Essentially, the third list sent by the server contains the IDs of one or more functional modules selected through the second operation; therefore, the first page can avoid displaying the one or more functional modules selected through the second operation.

[0072] In this embodiment, a second piece of information is sent to the server. This second piece of information is used to obtain information on all functional modules that are not selected for display in response to the second operation request. A third list sent by the server is received. This third list contains information on one or more functional modules that are not selected for display. Using this third list, one or more deleted functional modules are not displayed on the first page. This allows specific functional modules to be hidden according to the user's needs and preferences. Since the first page can display all functional modules at the same time, not displaying functional modules that the user does not need does not affect the overall page layout and provides a good user experience. In addition, by requesting the third list from the server, the latest information on one or more functional modules that are not selected for display can be obtained when the user revisits the first page or accesses the first page from different clients.

[0073] In order to achieve on-demand display of functional modules, it is necessary to implement componentization of functional modules. Based on this, in an optional embodiment, each functional module corresponds to a component among all functional modules that can be displayed on the first page, and the components of all functional modules are encapsulated in the first component.

[0074] In practical applications, to delete one or more functional modules according to user needs and to prevent the deleted functional modules from being displayed in subsequent implementations, each functional module can be encapsulated into a component, a corresponding delete button component can be added to the component corresponding to each functional module, and the component of each functional module and the corresponding delete button component can be encapsulated into the first component.

[0075] The components corresponding to the functional modules can be understood as containers that carry the specific content of the functional modules. The first component can be understood as a container that carries the functional module components and the corresponding delete button components. In this way, the display status of all functional modules can be managed uniformly through the first component, without having to traverse the components of each functional module to obtain or change the display status of the functional modules one by one.

[0076] For example, based on the example shown in Figure 2, the first component is located on the first page. The first component includes: a component of functional module 1, a component of functional module 2, and a component of functional module 3. The components of functional module 1, functional module 2, and functional module 3 respectively have corresponding first delete button components, second delete button components, and third delete button components. Assuming that all functional modules are displayed on the first page through the first component, as shown in Figure 4, the first page 201 displays functional module 1 403, functional module 2 405, and functional module 3 407. Functional module 1 403, functional module 2 405, and functional module 3 407 respectively have corresponding first delete buttons 404, second delete buttons 406, and third delete buttons 408. The first page 201 also includes a first list 210. The first list 210 is empty, which can be understood as displaying all configured functional modules on the first page 201.

[0077] For example, based on the example shown in FIG4, the client detects a second operation 409, wherein the second operation 409 includes the user clicking a third delete button 408; as shown in FIG5, in response to the second operation 409, the deleted functional module 3 407 is not displayed on the first page 201, and an updated first list 501 is displayed on the first page 201, the updated first list 501 containing information about the deleted functional module 3.

[0078] In practical applications, the client's detection and response to the second operation 409 can be achieved through the event operations bound to the third delete button component. The event operations include listening events and handling events. Listening events can be understood as the client detecting the second operation 409 in real time, and handling events can be understood as the client responding to the second operation 409 by not displaying the deleted functional module 3 407 on the first page 201, and displaying the updated first list 501 on the first page 201.

[0079] In this embodiment of the application, each functional module that can be displayed on the first page corresponds to a component, and the components of all functional modules are encapsulated in the first component. In this way, by encapsulating the components of all functional modules in the first component, it is not necessary to pay attention to the specific content of the functional modules, so as to adapt to any functional module and be applicable to most pages and application scenarios.

[0080] To enable the restoration and display of one or more selected functional modules on the first page, the functional modules corresponding to the first list can be encapsulated in a second component. Based on this, in an optional embodiment, displaying the first list on the first page includes: displaying the first list on the first page via the second component.

[0081] Here, the first list is displayed on the first page through the second component. The second component can be understood as a container that holds the specific content of the first list. Through the second component, the specific content can be displayed, and responses to the first operation can be achieved.

[0082] For example, the second component may include a list component and a list item component. The list component controls the pagination and sorting logic of the first list, while the list item component handles the display of each list item in the first list and responds to the user's first action on each list item. When a user wants to restore one or more functional modules to the first page, they long-press on a list item displayed on the first page. The client detects this long-press action and sends the ID of the corresponding functional module, page ID, and user ID to the server. The server can then use these information to delete the IDs and corresponding information of the functional modules under that user, obtaining the second list, which is then sent to the client. Based on the second list sent by the server, the client restores the functional modules that the user wanted to restore to the first page.

[0083] For example, the second component may include a list component, list item components, checkbox components, and confirmation button components. The list component controls the pagination and sorting logic of the first list. The list item component handles the display of each list item in the first list. The checkbox component and confirmation button component respond to the user's first action on each list item. This first action may include checking the checkbox corresponding to the list item and clicking the confirmation button. When a user wants to restore the display of one or more functional modules on the first page, they will check the checkbox corresponding to the list item and click the confirmation button. The client detects this action and sends the ID of the functional module, the page ID, and the user ID corresponding to that list item to the server. The server can then delete the information of the functional module corresponding to the ID of the user's functional module, obtaining the second list, and sends the second list to the client. The client receives the second list from the server and restores the display of the functional modules the user wanted to restore on the first page.

[0084] In this embodiment of the application, a first list is displayed on the first page through a second component. In this way, the specific content of the first list can be displayed through the second component, and the detection and response to the first operation can be realized, thereby realizing the display of the updated first list on the first page, and the restoration of the display of one or more selected functional modules on the first page.

[0085] To reduce the page space occupied by the first list and to allow users to flexibly control its display method and position, a floating button component and a floating list component can be used. Based on this, in an optional embodiment, displaying the first list on the first page via the second component includes: displaying a floating button on the first page via the second component; detecting a third operation, the third operation being a click operation on the button; and responding to the third operation by displaying the floating first list on the first page via the second component.

[0086] Here, the second component may include a floating button component and a floating list component. The floating button component can be dragged and displayed in different positions on the first page. Similarly, the floating list can also be dragged and displayed in different positions on the first page.

[0087] The client can display the default display form of the second component (i.e., the floating button) and detect the third action; if the third action is detected, the second component switches to the display form of the floating list component and displays the floating first list on the first page.

[0088] For example, based on the above example, the second component is located on the first page. The second component includes a floating button component and a floating list component. Assuming that functional module 1 and functional module 2 are displayed on the first page, as shown in Figure 6, the first page 201 may contain a floating button 601. If the user wants to view the contents of the first list, a third operation 602 is performed. The third operation 602 may include: the user clicks the floating button 601 on the first page 201, the client detects the third operation 602, and in response to the third operation 602, as shown in Figure 7, the floating button 601 is not displayed on the first page 201, and the floating first list 701 is switched to be displayed.

[0089] In this embodiment, a floating button component is displayed on the first page via the second component; a third operation is detected, which is a click operation on the button component; in response to the third operation, a floating first list is displayed on the first page via the second component. In this way, by using the floating button component, the page space occupied by the first list can be reduced, and by floating, the user can easily and flexibly control the display position of the button and the first list.

[0090] The following section provides a more detailed description of this application with reference to application examples.

[0091] In this application example, the server maintains information about all functional modules that are not displayed on the page.

[0092] As shown in Figure 8, the method for displaying the example page of this application includes the following steps: Step 801: Send an access request for the first page.

[0093] Step 802: Call the second API to retrieve the IDs and names of all functional modules not displayed on the first page from the server.

[0094] Here, when a user wants to access the first page, a triggering operation is performed, causing the client to send an access request for the first page to the server. The triggering operation varies depending on the type of client. For example, when the client is a browser, the triggering operation may include: the user opening the browser and entering the URL corresponding to the first page, or the user opening the webpage link corresponding to the first page in the browser. When the client is a non-browser app, the triggering operation may include: the user clicking the app icon to request access to the first page (in this case, the first page can be understood as the app's homepage), or clicking a function icon within the app to request access to the first page (in this case, the first page can be understood as the app's function page).

[0095] After detecting the user's triggered action, the client sends an access request to the server for the first page. Specifically, it can obtain the page file of the first page by calling the first API, and obtain the IDs and names of all functional modules that are not displayed on the first page by calling the second API (which can also be understood as obtaining a list of deleted functional modules on the page, containing the IDs and corresponding names of all deleted functional modules on the page). When calling the second API, the user ID and the ID of the first page can be used as parameters of the second API.

[0096] After receiving an access request for the first page, the server returns the page file corresponding to the first page to the client, as well as the IDs and names of all functional modules not displayed on the first page. In practical applications, the server can be understood as a service program deployed on a server to receive and process client requests. The page file can be, but is not limited to, HTML, CSS, JS, or XML files, and can contain all functional modules configured on the first page, along with their IDs and names.

[0097] Correspondingly, the client receives the IDs and names of all functional modules not displayed on the first page, and uses the names of all functional modules as the first list. The server stores the relevant information of all functional modules not displayed on the first page, enabling the client to obtain an accurate first list.

[0098] Step 803: Dynamically load one or more functional modules selected for display from all functional modules on the first page.

[0099] Here, dynamically loading one or more functional modules selected for display from all functional modules on the first page can be understood as the client loading only the front-end code corresponding to functional modules not in the first list based on the IDs of all functional modules not displayed on the first page, thus achieving dynamic loading of one or more functional modules selected for display from all functional modules on the first page.

[0100] Step 804: Render the first page, then proceed to step 805, or proceed to step 807.

[0101] Here, the client can display the aforementioned front-end code according to the layout format in the page file, thereby displaying one or more functional modules selected from all functional modules on the first page, completing the rendering of the first page. At the same time, the first page also displays content associated with the first list, such as floating buttons.

[0102] Step 805: Second operation detected.

[0103] Step 806: In response to the second operation, call the fourth API to send the IDs, page IDs, and user IDs of one or more functional modules selected in the second operation to the server.

[0104] Here, when a user wants to hide (or delete) one or more functional modules currently displayed on the first page, a second operation will be performed. The second operation may include clicking the delete button corresponding to one or more functional modules currently displayed on the first page. Each functional module corresponds to a component, and all components of the functional modules (each component of a functional module can be understood as a sub-component) are encapsulated in the first component. At the same time, the delete button component (which can be a sub-component) is also encapsulated in the first component so that the user can delete one or more functional modules on the first page through the first component, i.e., perform the second operation.

[0105] The client detects the second operation and responds by calling the fourth API to send the IDs of one or more functional modules, page IDs, and user IDs selected by the second operation to the server.

[0106] After receiving the IDs of one or more functional modules, page IDs, and user IDs selected by the client in the second operation, the server adds and saves the IDs of the functional modules under that user and the corresponding functional module information based on the functional module IDs, page IDs, and user IDs, thus obtaining a third list. The third list includes the IDs and names of all functional modules that are not displayed on the first page after being updated in response to the second operation.

[0107] Accordingly, the client also calls the second API to obtain the IDs and names of all functional modules not displayed on the first page from the server, i.e., execute step 802. It can be understood that the IDs and names of all functional modules not displayed on the first page obtained from the server at this time include the IDs and names of all functional modules not displayed on the first page after the second operation.

[0108] In addition, the client continues to execute steps 803 and 804 in order to display the content on the first page, including: all the updated functional modules displayed on the first page, and the content associated with the updated first list.

[0109] Step 807: Third operation detected.

[0110] Step 808: In response to the third operation, display a list of all deleted functional modules on the first page.

[0111] Here, when a user wants to view the contents of the list of all deleted functional modules on the first page (i.e., the floating first list), a third operation is performed. The third operation may include: the user clicks the floating button on the first page, the client detects the third operation, and responds to the third operation by displaying the list of all deleted functional modules on the first page.

[0112] Step 809: Detect the first operation, respond to the first operation, call the third API, and send the ID of one or more functional modules selected by the first operation, the page ID, and the user ID to the server.

[0113] Here, for example, the functional modules configured on the first page include: functional module 1, functional module 2, and functional module 3. The first component is located on the first page and includes: components of functional module 1, components of functional module 2, and components of functional module 3. The components of functional module 1, functional module 2, and functional module 3 respectively have corresponding first delete button components, second delete button components, and third delete button components. Assuming that the components of functional module 1, functional module 2, first delete button components, and second delete button components are displayed on the first page, the second component is located on the first page and includes: a floating list component, a checkbox component, and a confirmation button component, as shown in Figure 9. If the user wants to restore the display of functional module 3 on the first page 201, they perform a first operation 901. The first operation 901 includes: checking the checkboxes 902 corresponding to the list items of the floating first list 701 and clicking the confirmation button 903.

[0114] The client detects the first operation and responds by calling the third API to send the IDs of one or more functional modules, the page ID, and the user ID selected in the first operation to the server.

[0115] The server deletes the IDs of functional modules and their corresponding information under the user based on the ID of the functional module, the page ID, and the user ID, thus obtaining a second list. The second list may include the IDs and names of all functional modules that are not displayed on the first page after the update for the first operation.

[0116] Accordingly, the client also calls the second API to obtain the IDs and names of all functional modules not displayed on the first page from the server, i.e., execute step 802. It can be understood that the IDs and names of all functional modules not displayed on the first page obtained from the server at this time include the IDs and names of all functional modules not displayed on the first page after the update for the first operation.

[0117] In addition, the client continues to execute steps 803 and 804 in order to display the content on the first page, including: all the updated functional modules displayed on the first page, and the content associated with the updated first list.

[0118] For example, the solution of this application embodiment can be applied to the following scenario: The first page displays various monitoring data of a region: Since there are many monitoring indicators, and most of them are presented in the form of charts, if all of them are displayed, the page will load slowly. Moreover, the indicators that people in different positions or departments care about are different. They can simply display the indicators they care about and remove irrelevant indicators. In this way, the page will load quickly and they can quickly see the indicators they care about without having to search.

[0119] As can be seen from the above description, the solution of this application embodiment has the following advantages: 1) The solution provided by this application embodiment has a wide range of applications and is applicable to page display in most scenarios. Different application scenarios correspond to different pages. For example, if the scenario is that the user is viewing personal information, the corresponding page is the personal center page. If the scenario is shopping, the corresponding page is the mall page.

[0120] 2) In this embodiment of the application, the operation is simple and the user interaction experience is good.

[0121] 3) In this embodiment of the application, components are dynamically loaded, and components that are not displayed will not be loaded.

[0122] 4) In this embodiment of the application, the display of functional modules is not mutually exclusive and they can all be displayed simultaneously.

[0123] 5) In this embodiment of the application, there are no special requirements for the overall page layout, and it does not affect the overall page layout.

[0124] 6) The method provided in this application embodiment can be quickly applied to new pages with minimal development investment.

[0125] To implement the page display method of this application embodiment, this application embodiment also provides a page display device, disposed on an electronic device, as shown in FIG10. The device includes: a display unit 1001, configured to display a first list on a first page, the first list containing information on one or more functional modules that are not selected for display among all functional modules that can be displayed on the first page, and the first page also displays one or more functional modules that are selected for display among all functional modules; a processing unit 1002, configured to detect a first operation, the first operation being a selection operation for information on one or more functional modules that are not displayed; and in response to the first operation, to display an updated first list on the first page, the updated first list not containing information on the selected one or more functional modules, and to restore the display of the selected one or more functional modules on the first page.

[0126] In an optional embodiment, the apparatus may further include: a sending unit, configured to send first information to a server, the first information being used to obtain information on all functional modules that are not selected for display in response to the first operation request; a receiving unit, configured to receive a second list sent by the server, the second list containing information on one or more functional modules that are not selected for display; and the processing unit 1002, further configured to use the second list to restore the display of the one or more selected functional modules on the first page.

[0127] In an optional embodiment, the processing unit 1002 is further configured to: detect a second operation, the second operation being a deletion operation performed on the first page for the selected display of one or more functional modules; in response to the second operation, not display the deleted one or more functional modules on the first page, and display an updated first list on the first page, the updated first list containing information about the deleted one or more functional modules.

[0128] In an optional embodiment, the sending unit is further configured to send second information to the server, the second information being used to obtain information on all functional modules that are not selected for display in response to the second operation request; the receiving unit is further configured to receive a third list sent by the server, the third list containing information on one or more functional modules that are not selected for display; the processing unit 1002 is further configured to use the third list to prevent the display of one or more deleted functional modules on the first page.

[0129] In an optional embodiment, each functional module that can be displayed on the first page corresponds to a component, and the components of all functional modules are encapsulated in the first component.

[0130] In an optional embodiment, the processing unit 1002 is further configured to: display a first list on a first page via a second component.

[0131] In an optional embodiment, the processing unit 1002 is further configured to: display a floating button on the first page via the second component; detect a third operation, the third operation being a click operation on the button; and in response to the third operation, display a floating first list on the first page via the second component.

[0132] In practical applications, the display unit 1001 and the processing unit 1002 can be implemented by the processor in the page display device, and the sending unit and the receiving unit can be implemented by the processor in the page display device in combination with the communication interface.

[0133] It should be noted that the page display device provided in the above embodiments is only illustrated by the division of the above program modules. In actual applications, the above processing can be assigned to different program modules as needed, that is, the internal structure of the device can be divided into different program modules to complete all or part of the processing described above. In addition, the page display device and the page display method embodiments provided in the above embodiments belong to the same concept, and the specific implementation process can be found in the method embodiments, which will not be repeated here.

[0134] Based on the hardware implementation of the above-mentioned program modules, and in order to implement the method of the embodiments of this application, the embodiments of this application also provide an electronic device, as shown in FIG11. The electronic device 1100 includes: a communication interface 1101, which is capable of information interaction with a server; a processor 1102, which is connected to the communication interface 1101 to realize information interaction with the server and is used to execute the method provided by one or more technical solutions on the electronic device side when running a computer program; and a memory 1103, on which the computer program is stored.

[0135] Specifically, the processor 1102 is configured to: display a first list on a first page, the first list containing information on one or more functional modules that are not selected for display among all functional modules that can be displayed on the first page, and also displaying one or more functional modules that are selected for display among all functional modules on the first page; detect a first operation, the first operation being a selection operation for information on one or more functional modules that are not displayed; and in response to the first operation, display an updated first list on the first page, the updated first list not containing information on the selected one or more functional modules, and restore the display of the selected one or more functional modules on the first page.

[0136] In an optional embodiment, the communication interface 1101 is configured to send first information to the server, the first information being used to obtain information on all functional modules that are not selected for display in response to the first operation request; receive a second list sent by the server, the second list containing information on one or more functional modules that are not selected for display; the processor 1102 is further configured to use the second list to restore the display of one or more selected functional modules on the first page.

[0137] In an optional embodiment, the processor 1102 is further configured to: detect a second operation, the second operation being a deletion operation performed on the first page for the selected display of one or more functional modules; in response to the second operation, not display the deleted one or more functional modules on the first page, and display an updated first list on the first page, the updated first list containing information about the deleted one or more functional modules.

[0138] In an optional embodiment, the communication interface 1101 is further configured to send second information to the server, the second information being used to obtain information on all functional modules that are not selected for display in response to the second operation request; the communication interface 1101 is further configured to receive a third list sent by the server, the third list containing information on one or more functional modules that are not selected for display; the processor 1102 is further configured to use the third list to prevent the display of one or more deleted functional modules on the first page.

[0139] In an optional embodiment, each functional module that can be displayed on the first page corresponds to a component, and the components of all functional modules are encapsulated in the first component.

[0140] In an optional embodiment, the processor 1102 is further configured to: display a first list on a first page via a second component.

[0141] In an optional embodiment, the processor 1102 is further configured to: display a floating button on the first page via the second component; detect a third operation, the third operation being a click operation on the button; and, in response to the third operation, display a floating first list on the first page via the second component.

[0142] Of course, in practical applications, the various components in electronic device 1100 are coupled together through bus system 1104. It can be understood that bus system 1104 is used to realize the connection and communication between these components. In addition to the data bus, bus system 1104 also includes a power bus, a control bus, and a status signal bus. However, for clarity, all buses are labeled as bus system 1104 in Figure 11.

[0143] The memory 1103 in this embodiment is used to store various types of data to support the operation of the electronic device 1100. Examples of such data include any computer program used to operate on the electronic device 1100.

[0144] The methods disclosed in the embodiments of this application can be applied to, or implemented by, the processor 1102. The processor 1102 may be an integrated circuit chip with signal processing capabilities. During implementation, each step of the above method can be completed by the integrated logic circuitry of the hardware in the processor 1102 or by instructions in software form. The processor 1102 may be a general-purpose processor, a digital signal processor (DSP), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The processor 1102 can implement or execute the methods, steps, and logic block diagrams disclosed in the embodiments of this application. A general-purpose processor may be a microprocessor or any conventional processor, etc. The steps of the methods disclosed in the embodiments of this application can be directly manifested as execution by a hardware decoding processor, or execution by a combination of hardware and software modules in the decoding processor. The software modules may be located in a storage medium, specifically memory 1103. The processor 1102 reads information from memory 1103 and, in conjunction with its hardware, completes the steps of the aforementioned method.

[0145] In an exemplary embodiment, the electronic device 1100 may be implemented by one or more application-specific integrated circuits (ASICs), DSPs, programmable logic devices (PLDs), complex programmable logic devices (CPLDs), field-programmable gate arrays (FPGAs), general-purpose processors, controllers, microcontrollers (MCUs), microprocessors, or other electronic components to perform the aforementioned method.

[0146] It is understood that the memory 1103 in this embodiment can be volatile memory or non-volatile memory, or both. 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), ferromagnetic random access memory (FRAM), flash memory, magnetic surface memory, optical disc, or compact disc read-only memory (CD-ROM); magnetic surface memory can be disk storage or magnetic tape storage. Volatile memory can be random access memory (RAM), which is used as an external cache. By way of example, but not limitation, many forms of RAM are available, such as Static Random Access Memory (SRAM), Synchronous Static Random Access Memory (SSRAM), Dynamic Random Access Memory (DRAM), Synchronous Dynamic Random Access Memory (SDRAM), Double Data Rate Synchronous Dynamic Random Access Memory (DDRSDRAM), Enhanced Synchronous Dynamic Random Access Memory (ESDRAM), SyncLink Dynamic Random Access Memory (SLDRAM), and Direct Rambus Random Access Memory (DRRAM).The memories described in the embodiments of this application are intended to include, but are not limited to, these and any other suitable types of memories.

[0147] In an exemplary embodiment, this application also provides a storage medium, namely a computer storage medium, specifically a computer-readable storage medium, such as a memory 1103 storing a computer program, which can be executed by the processor 1102 of the electronic device 1100 to complete the steps described in the aforementioned method. The computer-readable storage medium may be a memory such as FRAM, ROM, PROM, EPROM, EEPROM, Flash Memory, magnetic surface memory, optical disc, or CD-ROM.

[0148] For example, this application also provides a computer program product, including a computer program that can be executed by the processor 1102 of the electronic device 1100 to perform the steps described in the foregoing method.

[0149] It should be noted that terms such as "first" and "second" are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence.

[0150] Furthermore, the technical solutions described in the embodiments of this application can be combined arbitrarily without conflict.

[0151] The above description is merely an embodiment of this application and is not intended to limit the scope of protection of this application. Any modifications, equivalent substitutions, and improvements made within the spirit and scope of this application are included within the scope of protection of this application.

Claims

1. A page display method, characterized in that, The method, applied to an electronic device, includes: displaying a first list on a first page, the first list containing information on one or more functional modules that are not selected for display among all functional modules that can be displayed on the first page, and also displaying one or more functional modules that are selected for display among all functional modules on the first page; detecting a first operation, the first operation being a selection operation for information on the one or more functional modules that are not displayed; and responding to the first operation, displaying an updated first list on the first page, the updated first list not containing information on the selected one or more functional modules, and restoring the display of the selected one or more functional modules on the first page.

2. The method according to claim 1, characterized in that, The method further includes: sending first information to a server, the first information being used to obtain information on all functional modules that are not selected for display in response to the first operation request; receiving a second list sent by the server, the second list containing information on one or more functional modules that are not selected for display; and restoring the display of the selected one or more functional modules on the first page, comprising: using the second list to restore the display of the selected one or more functional modules on the first page.

3. The method according to claim 1, characterized in that, The method further includes: detecting a second operation, the second operation being a deletion operation performed on the first page for the selected display of one or more functional modules; in response to the second operation, not displaying the deleted one or more functional modules on the first page, and displaying an updated first list on the first page, the updated first list containing information about the deleted one or more functional modules.

4. The method according to claim 3, characterized in that, The method further includes: sending second information to the server, the second information being used to obtain information on all functional modules that are not selected for display in response to the second operation request; receiving a third list sent by the server, the third list containing information on one or more functional modules that are not selected for display; and the step of not displaying one or more deleted functional modules on the first page includes: using the third list to not display one or more deleted functional modules on the first page.

5. The method according to claim 3, characterized in that, Each functional module that can be displayed on the first page corresponds to a component, and the components of all functional modules are encapsulated in the first component.

6. The method according to any one of claims 1 to 5, characterized in that, The step of displaying the first list on the first page includes: displaying the first list on the first page through a second component.

7. The method according to claim 6, characterized in that, The step of displaying the first list on the first page via the second component includes: displaying a floating button on the first page via the second component; detecting a third operation, the third operation being a click operation on the button; and responding to the third operation by displaying the floating first list on the first page via the second component.

8. An electronic device, characterized in that, It includes a processor and a memory for storing a computer program capable of running on the processor, wherein, when the processor is used to run the computer program, it performs the steps of the method according to any one of claims 1 to 7.

9. A storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by a processor, it implements the steps of the method according to any one of claims 1 to 7.

10. A computer program product comprising a computer program or computer-executable instructions, characterized in that, When the computer program or computer-executable instructions are executed by a processor, they implement the steps of the method according to any one of claims 1 to 7.

Images