Page display method, device, storage medium and electronic device

Abstract

The present disclosure provides a page display method, apparatus, storage medium and electronic device; relating to the field of computer technology. The method includes: when a query operation on target data in a parent page is received, sending a first request to a server to store page jump parameters of the parent page, and jumping from the parent page to a sub-page corresponding to the target data; sending a second request to the server to obtain the page jump parameters of the parent page, and jumping back from the sub-page to the parent page according to the page jump parameters. When entering the sub-page from the parent page in the present disclosure, the server can store the page jump parameters, and when returning from the sub-page, the page jump parameters can be obtained from the server, and the previous parent page can be restored according to the page jump parameters, avoiding page refresh caused by page jump, thereby improving the user experience.

Description

Technical Field

[0001] The present disclosure relates to the field of computer technologies, and in particular, to a page display method, a page display device, a computer-readable storage medium, and an electronic device. Background Art

[0002] With the continuous update of front-end technologies and frameworks, the complexity of page functions and interactions has also increased. In front-end development, Vue is a progressive framework for building user interfaces. Based on the Vue framework, front-end pages can be developed quickly, such as developing single-page applications.

[0003] When using the Vue framework to develop a single-page application, page jumps will cause page refreshes. Taking the jump between a list page and a detail page as an example, after selecting a piece of data from the filtered list page and jumping to the detail page of the data, when returning from the detail page to the list page, the list page will return to its initial state, and the query result after the last filter is not saved. If the user needs to view this query result, they need to perform the filtering operation again, which reduces the user experience.

[0004] It should be noted that the information disclosed in the above background art section is only used to enhance the understanding of the background of the present disclosure, and therefore may include information that does not constitute the prior art known to those of ordinary skill in the art. Summary of the Invention

[0005] The purpose of the present disclosure is to provide a page display method, a page display device, a computer-readable storage medium, and an electronic device, so as to at least to some extent overcome the problem of low user experience caused by page refreshes during page jumps due to related technologies.

[0006] According to a first aspect of the present disclosure, a page display method is provided, including:

[0007] When a query operation on target data in a parent page is received, a first request is sent to a server to store the page jump parameters of the parent page, and the parent page is jumped to a sub-page corresponding to the target data;

[0008] A second request is sent to the server to obtain the page jump parameters of the parent page, and the sub-page is jumped back to the parent page according to the page jump parameters.

[0009] In an exemplary embodiment of the present disclosure, before jumping from the parent page to the sub-page corresponding to the target data, the method further includes:

[0010] Configuring a target file, which is used to store the parent-child relationship between the parent page and the sub-page.

[0011] In an exemplary embodiment of the present disclosure, before jumping from the parent page to the sub-page corresponding to the target data, the method further includes:

[0012] Define a first parameter memory variable, which is used to mark whether to remember the page jump parameters of the parent page;

[0013] Define a first navigation guard, which is used to assign values to the path attributes of the parent page and the sub-page in the first object, and when it is determined that the first object exists in the target file by traversing the target file, assign a value to the first parameter memory variable corresponding to the parent page in the first object.

[0014] In an exemplary embodiment of the present disclosure, when receiving a query operation on the target data in the parent page, sending a first request to the server to store the page jump parameters of the parent page, and jumping from the parent page to the sub-page corresponding to the target data, includes:

[0015] When receiving a query operation on the target data in the parent page, obtain the page jump parameters of the parent page and the first parameter memory variable;

[0016] When it is determined that the first parameter memory variable meets the preset conditions by using the page jump function, convert the page jump parameters into a target parameter string;

[0017] Send a first request carrying the target parameter string to the server to store the target parameter string in the server, and jump from the parent page to the sub-page corresponding to the target data.

[0018] In an exemplary embodiment of the present disclosure, the step of converting the page jump parameters into a target parameter string when it is determined that the first parameter memory variable meets the preset conditions by using the page jump function includes:

[0019] When it is determined that the value of the first parameter memory variable is the target value by using the page jump function, convert the page jump parameters into an initial parameter string;

[0020] Encode the initial parameter string to obtain a first parameter string;

[0021] Encrypt the first parameter string to obtain the target parameter string.

[0022] In an exemplary embodiment of the present disclosure, before jumping back from the sub-page to the parent page, the method further includes:

[0023] Define a second parameter memory variable, which is used to mark whether there is a page jump parameter of the parent page in the target file;

[0024] Define a second navigation guard, which is used to assign values to the path attributes of the parent page and the path attributes of the child page in the second object, and, when it is determined that the second object exists in the target file by traversing the target file, assign a value to the second parameter memory variable corresponding to the parent page in the second object.

[0025] In an exemplary embodiment of the present disclosure, the sending a second request to the server to obtain the page jump parameter of the parent page and jumping back to the parent page from the child page according to the page jump parameter includes:

[0026] When it is determined by using a parameter parsing function that the value of the second parameter memory variable is a target value, send a second request to the server to obtain the target parameter string from the server;

[0027] Decrypt the target parameter string to obtain the first parameter string;

[0028] Decode the first parameter string to obtain the initial parameter string, and convert the initial parameter string into the page jump parameter of the parent page;

[0029] Jump back to the parent page from the child page according to the page jump parameter.

[0030] In an exemplary embodiment of the present disclosure, the jumping back to the parent page from the child page according to the page jump parameter includes:

[0031] Assign the current value of the page jump parameter to an option variable, where the option variable is used to save the default value of the page jump parameter;

[0032] Jump back to the parent page from the child page according to the assigned option variable.

[0033] According to a second aspect of the present disclosure, there is provided a page display device, including:

[0034] A first page display module, configured to, when receiving a query operation on target data in a parent page, send a first request to a server to store the page jump parameter of the parent page, and jump from the parent page to the child page corresponding to the target data;

[0035] A second page display module, configured to send a second request to the server to obtain the page jump parameter of the parent page, and jump back to the parent page from the child page according to the page jump parameter.

[0036] According to a third aspect of the present disclosure, there is provided a computer-readable storage medium having stored thereon a computer program, which when executed by a processor implements the method described in any one of the above.

[0037] According to a fourth aspect of the present disclosure, there is provided an electronic device, including: a processor; and a memory for storing executable instructions of the processor; wherein the processor is configured to execute the method described in any one of the above by executing the executable instructions.

[0038] The exemplary embodiments of the present disclosure may have some or all of the following beneficial effects:

[0039] In the page display method provided by the exemplary embodiment of the present disclosure, when a query operation on target data in a parent page is received, a first request is sent to the server to store the page jump parameters of the parent page, and the parent page jumps to the sub-page corresponding to the target data; a second request is sent to the server to obtain the page jump parameters of the parent page, and the parent page is jumped back from the sub-page according to the page jump parameters. On the one hand, when entering the sub-page from the parent page in the present disclosure, the server can store the page jump parameters, and when returning from the sub-page, the page jump parameters can be obtained from the server, and the previous parent page can be restored according to the page jump parameters, avoiding page refresh caused by page jump, and the user can obtain the previous query result without further operation, thereby improving the user experience; on the other hand, the storage and acquisition of page jump parameters can be realized through interaction with the server, without using memory to store data, reducing memory consumption, and thus improving the display performance of the page.

[0040] It should be understood that the above general description and the following detailed description are only exemplary and explanatory, and cannot limit the present disclosure. BRIEF DESCRIPTION OF THE DRAWINGS

[0041] The accompanying drawings herein are incorporated into the specification and form a part of the specification, showing embodiments consistent with the present disclosure, and are used together with the specification to explain the principles of the present disclosure. Obviously, the accompanying drawings in the following description are only some embodiments of the present disclosure, and those of ordinary skill in the art can obtain other drawings without creative efforts based on these drawings.

[0042] Figure 1 A schematic diagram showing an exemplary system architecture to which the page display method and apparatus according to the embodiments of the present disclosure can be applied;

[0043] Figure 2 A flowchart schematically showing a page display method according to an embodiment of the present disclosure;

[0044] Figure 3 Schematically shows a flowchart of storing page jump parameters during page jump according to an embodiment of the present disclosure;

[0045] Figure 4 Schematically shows a flowchart of processing page jump parameters during page jump according to an embodiment of the present disclosure;

[0046] Figure 5 Schematically shows a flowchart of storing page jump parameters during page jump according to another embodiment of the present disclosure;

[0047] Figure 6 Schematically shows a flowchart of obtaining page jump parameters when returning to a page according to an embodiment of the present disclosure;

[0048] Figure 7 Schematically shows a flowchart of obtaining page jump parameters when returning to a page according to another embodiment of the present disclosure;

[0049] Figure 8 Schematically shows a complete flowchart of a page display method according to an embodiment of the present disclosure;

[0050] Figure 9A Schematically shows a schematic diagram of an original list page according to an embodiment of the present disclosure;

[0051] Figure 9B Schematically shows a schematic diagram of an intermediate list page according to an embodiment of the present disclosure;

[0052] Figure 9C Schematically shows a schematic diagram of a work order details page according to an embodiment of the present disclosure;

[0053] Figure 10 Schematically shows a block diagram of a page display device according to an embodiment of the present disclosure;

[0054] Figure 11 Schematically shows a schematic diagram of the structure of a computer system of an electronic device suitable for implementing the embodiments of the present disclosure. Detailed implementation manners

[0055] Example embodiments will now be described more fully with reference to the accompanying drawings. However, the example embodiments can be implemented in various forms and should not be construed as limited to the examples set forth herein; rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the concept of the example embodiments to those skilled in the art. The features, structures, or characteristics described may be combined in any suitable manner in one or more embodiments. In the following description, numerous specific details are provided to give a thorough understanding of the embodiments of the present disclosure. However, those skilled in the art will realize that the technical solutions of the present disclosure may be practiced without one or more of the specific details, or may be implemented using other methods, components, devices, steps, etc. In other cases, well-known technical solutions are not shown or described in detail to avoid obscuring various aspects of the present disclosure.

[0056] In addition, the accompanying drawings are only schematic illustrations of the present disclosure and are not necessarily drawn to scale. The same reference numerals in the drawings denote the same or similar parts, and thus repeated descriptions thereof will be omitted. Some of the block diagrams shown in the drawings are functional entities and do not necessarily correspond to physically or logically independent entities. These functional entities may be implemented in software, or in one or more hardware modules or integrated circuits, or in different networks and / or processor devices and / or microcontroller devices.

[0057] Figure 1 A schematic diagram of a system architecture of an exemplary application environment in which a page display method and apparatus according to an embodiment of the present disclosure can be applied is shown.

[0058] As Figure 1 shown, the system architecture 100 may include one or more of the terminal devices 101, 102, 103, a network 104, and a server 105. The network 104 is a medium for providing a communication link between the terminal devices 101, 102, 103 and the server 105. The network 104 may include various connection types, such as wired, wireless communication links, or fiber optic cables, etc. The terminal devices 101, 102, 103 may be various electronic devices, including but not limited to desktop computers, portable computers, smart phones, and tablet computers, etc., for providing a user interface for page display. For example, a client (such as a browser) is installed on the terminal device, and a page can be browsed through the browser client. Specifically, the browser on the terminal device can be used to perform: when a query operation for target data in the parent page is received, sending a first request to the server to store the page jump parameter of the parent page, and jumping from the parent page to the sub-page corresponding to the target data; sending a second request to the server to obtain the page jump parameter of the parent page, and jumping back from the sub-page to the parent page according to the page jump parameter. It should be understood thatFigure 1 The numbers of the terminal devices, networks, and servers in [description] are merely illustrative. According to the implementation requirements, there can be any number of terminal devices, networks, and servers. For example, the server 105 can be a single server, a server cluster composed of multiple servers, a cloud computing platform, or a virtualization center. Additionally, the server 105 can be used to provide background services for view components that support page display, etc.

[0059] The page display method provided by the embodiments of the present disclosure is generally executed by one or more of the terminal devices 101, 102, and 103. Correspondingly, the page display device is generally disposed in the terminal devices 101, 102, and 103. For example, after being executed by the terminal device, the previous query result can be directly displayed on the display screen of the terminal device. No special limitation is made in this exemplary embodiment. However, it is easily understood by those skilled in the art that the page display method provided by the embodiments of the present disclosure can also be executed by the server 105. Correspondingly, the page display device can also be disposed in the server 105. The server can store the query conditions selected by the user so that when performing page jumps, the previous query result can be returned according to the query conditions and presented to the user by the terminal device.

[0060] The technical solutions of the embodiments of the present disclosure are elaborated in detail below:

[0061] With the continuous update of front-end technologies and frameworks, the complexity of page functions and interactions has also increased. In front-end development, Vue is a progressive framework for building user interfaces. Based on the Vue framework, front-end pages can be quickly developed, such as developing single-page applications.

[0062] When using the Vue-Cli framework (a scaffolding tool in the Vue framework) to develop single-page applications, page jumps will cause page refreshes. Taking the jump between a list page and a detail page as an example, after selecting a piece of data from the filtered list page and jumping to the detail page of that data, when returning from the detail page to the list page, it will return to the initial state of the list page without saving the previous filtered query result. If the user needs to view the query result, they need to perform the filtering operation again, which reduces the user experience.

[0063] Based on the above one or more problems, this exemplary embodiment provides a page display method. This method can be applied to one or more of the above terminal devices 101, 102, and 103, and can also be applied to the above server 105. No special limitation is made in this exemplary embodiment.

[0064] Refer to Figure 2 As shown, the page display method can include step S210 and step S220:

[0065] Step S210. When a query operation on target data in the parent page is received, send a first request to the server to store the page jump parameters of the parent page, and jump from the parent page to the sub-page corresponding to the target data;

[0066] Step S220. Send a second request to the server to obtain the page jump parameters of the parent page, and jump back from the sub-page to the parent page according to the page jump parameters.

[0067] In the page display method provided by the exemplary embodiment of the present disclosure, when a query operation on target data in the parent page is received, a first request is sent to the server to store the page jump parameters of the parent page, and jump from the parent page to the sub-page corresponding to the target data; a second request is sent to the server to obtain the page jump parameters of the parent page, and jump back from the sub-page to the parent page according to the page jump parameters. On the one hand, when entering the sub-page from the parent page in the present disclosure, the server can store the page jump parameters, and when returning from the sub-page, the page jump parameters can be obtained from the server, and the previous parent page can be restored according to the page jump parameters, avoiding page refresh caused by page jump, and the user can obtain the previous query result without re-operation, thereby improving the user experience; on the other hand, the storage and acquisition of page jump parameters can be realized through interaction with the server, without using memory to store data, reducing memory consumption, and thus improving the display performance of the page.

[0068] Next, the above steps of this exemplary embodiment will be described in more detail.

[0069] In step S210, when a query operation on target data in the parent page is received, send a first request to the server to store the page jump parameters of the parent page, and jump from the parent page to the sub-page corresponding to the target data.

[0070] In the exemplary embodiments of the present disclosure, the page display in a single-page application can be taken as an example for illustration. Correspondingly, the parent page can be a list page, and the sub-page can be a detail page. Among them, a single-page application refers to an application program with only one main page. When this application program runs in a browser, the system only needs to load resources once, and subsequent operation interactions and data interactions are implemented through Router (routing) and AJAX (Asynchronous Javascript And XML, a web development technology for creating interactive web applications). The list page and the detail page can be user interfaces developed by the Vue-Cli framework. Specifically, the list page can be a user interface in the application program for displaying interface elements with high repetition, and the order, position, and data source of each interface element can be controlled by the Vue-Cli framework. The detail page can be a user interface in the application program for displaying the detailed content of a certain interface element.

[0071] When a user queries the details of a certain piece of data in the list page, the user needs to enter query conditions related to this data in the list page. In the exemplary embodiments of the present disclosure, the query conditions can include filtering conditions and paging conditions. The filtering conditions can be information such as name and type, and the paging conditions can be information such as page number and the number of data items per page. For example, if the user searches according to the type in the list page, and the filtering condition carried by the list page is "alarmType:1", it can mean to find the data with the alarm type of type 1 in the list page. If the user searches according to the page number in the list page, and the paging condition carried by the list page is "pageNum:2", it can mean to select a certain piece of data on the second page to view the details of this data. It should be noted that the list page can include an original list page and an intermediate list page. Among them, the original list page can be the initial state of the list page, and the intermediate list page can be the list page with both filtering conditions and paging conditions. Exemplarily, after filtering the original list page using the filtering condition (such as alarmType:1), the original list page can be switched to the intermediate list page, that is, the second page, according to the paging condition (such as pageNum:2). After selecting a certain piece of data on the second page, it can be jumped to the detail page of this data. At this time, the corresponding query condition is: "alarmType:1,pageNum:2". It can be understood that the original list page can be defaulted to the data on the first page without filtering conditions, and the corresponding query condition is "alarmType:'',pageNum:1".

[0072] In an example implementation, the parent page can be the original list page or the intermediate list page. That is, it is possible to query the details of the data in the original list page or the intermediate list page. Taking the query of the details of the data in the intermediate list page as an example, when a query operation for the target data in the intermediate list page is received, a request can be sent to the server to store the page jump parameters of the intermediate list page. For example, the page jump parameters can be stored in a database, and then jump from the intermediate list page to the details page corresponding to the target data. Among them, the page jump parameters can be the query conditions carried by the intermediate list page, the target data can be any list data in the intermediate list page associated with the details page, the details page can be the first page displayed when querying the details of the target data, and the request sent to the server can be an http (hypertext transfer protocol) request. For example, the page jump parameters of the intermediate list page can be sent to the server through a first request such as a post request, so that the server stores the received page jump parameters of the intermediate list page in the database.

[0073] It should be noted that before jumping from the parent page to the child page corresponding to the target data, a target file can be pre-configured. This target file can be used to store all the parent-child relationships between the parent pages and the child pages. When developing an application using the Vue-Cli framework, correspondingly, the target file can be a JS (JavaScript) file configured in the Vue-store (storage folder). For example, when applied to the page jump function in the application, a pageJumpMemory.js file can be configured in the Vue-store. This file is used to describe all the pages with parent-child relationships in the application. The data in this file can form a configuration item array, and this array can be used as a global variable, which only needs to be loaded once when the project starts to pull all the configuration information in the file and store all the configuration information in the store state management for subsequent global calls.

[0074] Exemplarily, in a web application, the parent-child relationships of all pages in the pageJumpMemory.js file can be configured and stored in the form of a table. When the parent-child relationships in the original maintained table change, the table can be updated accordingly. For example, if new parent-child relationship pages are added during the iteration of the web application, the new parent and child pages can be added to the table to achieve the timely update of the web application. As shown in Table 1, a table for storing the parent-child relationships of pages in the configured pageJumpMemory.js file is schematically given. Among them, there are two groups of pages with parent-child relationships, namely parent page 1 (path attribute value: / fatherPage1 / index) and child page 1 (path attribute value: / fatherPage1 / son1), parent page 2 (path attribute value: / fatherPage2 / index) and child page 2 (path attribute value: / fatherPage2 / son1). When jumping from parent page 1 to child page 1, it is necessary to remember the query conditions carried by parent page 1. When jumping from parent page 2 to child page 2, it is not necessary to remember the query conditions carried by parent page 2.

[0075] Table 1

[0076] Parent Page Sub Page Do you need to remember (Y / N) / fatherPage1 / index / fatherPage1 / son1 Y / fatherPage2 / index / fatherPage2 / son1 N

[0077] To implement the function of retaining the query conditions carried by the parent page, before jumping from the parent page to the child page corresponding to the target data, a first parameter memory variable, that is, requireMemory, can also be defined. This first parameter memory variable can be used to mark whether to remember the page jump parameters of the parent page. For example, if requireMemory = false, it means that there is no need to remember the page jump parameters of the parent page. If requireMemory = true, it means that it is necessary to remember the page jump parameters of the parent page, that is, it is necessary to remember the query conditions carried by the parent page. At the same time, a first navigation guard, that is, the beforeRouteLeave hook function, can also be defined. This guard can be used to assign values to the path attributes of the parent page and the path attributes of the child page in the first object, and when it is determined that the first object exists in the target file by traversing the target file, the first parameter memory variable corresponding to the parent page in the first object can be assigned a value. Specifically, when registering the beforeRouteLeave hook function on the parent page, three parameters need to be passed in, namely to, from, and next. Among them, the parameter to (Route, routing attribute) represents the target route object that is about to be entered, the parameter from (Route, routing attribute) represents the route object that the navigation is about to leave. The route jump is executed by calling the next function, and the execution effect depends on the call parameters of the next function.

[0078] For example, a temporary object temp = {fatherPage: '', sonPage: ''} can be defined as the first object. Through the beforeRouteLeave hook function, the path property value of the parameter to can be assigned to temp.son, and the path property value of the parameter from can be assigned to temp.father. According to the assigned path property value, it is possible to jump from the parent page to the child page, that is, from the current page to the target page. Then, the configured pageJumpMemory.js file can be traversed to determine whether the temp object exists in the file. If the temp object exists in the pageJumpMemory.js file, the first parameter memory variable requireMemory will be assigned the value true; if the temp object does not exist in the pageJumpMemory.js file, the first parameter memory variable requireMemory will be assigned the value false.

[0079] In an exemplary embodiment, referring to Figure 3 as shown, it is possible to implement the jump from the parent page to the child page corresponding to the target data according to steps S310 to S330.

[0080] Step S310. When a query operation on the target data in the parent page is received, obtain the page jump parameter of the parent page and the first parameter memory variable.

[0081] Exemplarily, still taking the parent page as the middle list page and the child page as the details page as an example for illustration. For a middle list page with both filtering conditions and pagination conditions, when a query operation on the target data in the middle list page is received, the beforeRouteLeave hook function can be triggered to call the page jump function, and the page jump function can be used to jump from the middle list page to the details page corresponding to the target data. Among them, the query operation can be a click / short press operation by the user on the "Details" control on the middle list interface, and the present disclosure does not make specific limitations thereon. In the exemplary embodiment of the present disclosure, the page jump function can be the toDetails function. When using the toDetails function to jump from the middle list page to the details page, the page jump parameter carried by the middle list page, that is, the query condition, can be stored on the server side, so that when returning from the details page, the query condition can be obtained from the server side, and the previous query result can be restored according to the obtained query condition, without the user having to perform a filtering operation on the original list page again, which can improve the user experience.

[0082] Specifically, when calling the toDetails function, the first parameter memory variable requireMemory and the page jump parameters options carried in the intermediate list page need to be passed in. options are the parameter names and parameter values to be remembered during page jump, and are of the type of an array of objects. For example, when the query condition is to filter the original list page according to the filter condition "alarmType is 1", and then switch from the original list page to the intermediate list page according to the paging condition "the second page, with 10 data items per page" to query the target data in the intermediate list page, the options passed in corresponding to this query condition can be {pageNum: 2, pageSize: 10, alarmType: 1}.

[0083] Step S320. When it is determined by the page jump function that the first parameter memory variable meets the preset condition, convert the page jump parameters into a target parameter string.

[0084] After the parameter passing is completed, refer to Figure 4 As shown, the page jump parameters can be processed according to steps S410 to S430 to store the processing results.

[0085] Step S410. When it is determined by the page jump function that the value of the first parameter memory variable is the target value, convert the page jump parameters into an initial parameter string.

[0086] It can be judged by the page jump function whether the first parameter memory variable requireMemory meets the preset condition. For example, the preset condition can be that the value of the first parameter memory variable is the target value true to perform page jump according to the value of requireMemory. When it is determined that requireMemory = true, the page jump parameters can be converted into an initial parameter string. Among them, the page jump parameters can be the query condition options carried in the intermediate list page, and the initial parameter string can be the params string. It should be noted that the purpose of converting the page jump parameters into parameter strings is to convert the page jump parameters into content that can be uniformly recognized by the page jump function, which is convenient for unified integrated management and operation.

[0087] Exemplarily, the toDetails function can be used to convert the options object into a params string. If options is {pageNum: 2, pageSize: 10, alarmType: 1}, the converted params string can be {"pageNum": 2, "pageSize": 10, "alarmType": 1}, as shown in Table 2.

[0088] Table 2

[0089] options object pageNum:2,pageSize:10,alarmType:1 params string ”pageNum”:2,”pageSize”:10,”alarmType”:1

[0090] Step S420. Encode the initial parameter string to obtain a first parameter string.

[0091] To increase the security of the page jump parameter, after converting the page jump parameter into an initial string, the initial string can be encoded to obtain a first parameter string. Exemplarily, the options object can be converted into a params string using the toDetails function, and this params string is the initial parameter string. Then, the encodeURI function can be used to perform UTF-8 (8-bit Unicode Transformation Format, variable-length character encoding) encoding on this params string, and the encoded params string is the first parameter string. Among them, the encodeURI function can encode the string as a URI component. Exemplarily, the encoded params string can be: “%7BpageNum%3Apagesize%22…”, as shown in Table 3.

[0092] Table 3

[0093] options object pageNum:2,pageSize:10,alarmType:1 params string ”pageNum”:2,”pageSize”:10,”alarmType”:1 Encoded params string %7BpageNum%3Apagesize%22…

[0094] It can be seen that the parameter names in the query condition such as pageNum, pagesize, etc. can be seen from the encoded params string, but the parameter values of each parameter cannot be obtained, which can improve the security of the page jump parameter.

[0095] Step S430. Encrypt the first parameter string to obtain the target parameter string.

[0096] On the basis of increasing the security of the page jump parameter, further, to increase the aesthetics of the page jump parameter, the first parameter string obtained by encoding can also be encrypted to obtain the target parameter string.

[0097] Exemplarily, first, the toDetails function can be used to convert the options object into a params string, which is the initial parameter string. Then, the encodeURI function can be used to encode the params string, and the encoded result of the params string is encrypted. Among them, the encoded result of the params string can be Base64 encoded to encrypt the encoded result of the params string. It can be understood that the encryption method can also be MD5 (message-digest algorithm 5), SHA1 (Secure Hash Algorithm 1), Crypto-JS (a JavaScript encryption algorithm), etc., and the present disclosure does not make specific limitations thereto. The encoded params string is the first parameter string, and the encrypted params string is the target parameter string. Exemplarily, the encrypted params string can be "cGFnZU51bTo1LCBw…", as shown in Table 4.

[0098] Table 4

[0099] options object pageNum:2,pageSize:10,alarmType:1 params string ”pageNum”:2,”pageSize”:10,”alarmType”:1 Encoded params string %7BpageNum%3Apagesize%22… Encrypted params string cGFnZU51bTo1LCBw…

[0100] It can be seen that the parameter information related to the query condition cannot be read from the encrypted params string, which further improves the security of the page jump parameters and can also increase the aesthetics of the page jump parameters.

[0101] In other examples, after using the toDetails function to convert the options object into a params string, the obtained params string can also be used as the target parameter string. It is also possible to directly encrypt the converted params string and use the encrypted result as the target parameter string. During the encryption process, the params string can also be encrypted in multiple layers. For example, the encoded result of the params string can be successively Base64 encoded, MD5 encrypted, and SHA1 encrypted, etc., to further improve the security of the page jump parameters. Or it is also possible to encode the converted params string and directly use the encoded result as the target parameter string, and the present disclosure does not make specific limitations thereto.

[0102] Step S330. Send a first request carrying the target parameter string to the server to store the target parameter string in the server, and jump from the parent page to the sub-page corresponding to the target data.

[0103] After obtaining the target parameter string, a first request such as a POST request can be sent to the server. The target parameter string can be carried in the POST request to send the target parameter string to the server, and the server stores the target parameter string, realizing the storage function of the query conditions on the intermediate list page. Then, the next function can be called through the beforeRouteLeave hook function to perform page jumping according to the path attribute value of the intermediate list page and the path attribute value of the details page, so as to jump from the intermediate list page to the details page corresponding to the target data.

[0104] In an exemplary embodiment, referring to Figure 5 as shown, page jumping can also be implemented according to steps S501 to S506.

[0105] Step S501. Determine whether requireMemory is true. The value of requireMemory is determined through the page jump function toDetails. If requireMemory === true, step S502 is executed; otherwise, step S506 is directly executed.

[0106] Step S502. Convert options to a params string.

[0107] Step S503. Encrypt the params string.

[0108] Step S504. Encode the encrypted params string.

[0109] Step S505. Send the encoded params string to the server for storage through a POST request.

[0110] Step S506. Jump to the target page.

[0111] In the exemplary embodiment of the present disclosure, when developing a single-page application using the vue-cli framework, only a page jump function needs to be added to the source code of the parent page to realize jumping from the parent page to the child page. Using the page jump parameters, the query conditions of the parent page can be stored when jumping pages, so that the query conditions can be obtained when returning from the child page, and the previous query results can be restored according to the obtained query conditions without modifying the source code of the child page, reducing the workload of users and improving the page operation efficiency of users. Moreover, by sending a request to the server, the query conditions of the parent page can be stored in the database without using memory to store data, reducing memory consumption, thereby improving the display performance of the page.

[0112] In step S220, a second request is sent to the server to obtain the page jump parameters of the parent page, and the subpage jumps back to the parent page according to the page jump parameters.

[0113] In the exemplary embodiment of the present disclosure, an option variable defaultParams can be defined, and this option variable can be used to save the default values of the page jump parameters. For example, it can be used to save the initial query conditions of the list page. If the initial query conditions are {pageNum: 1, pageSize: 10}, it means that ten data are included per page by default, and the data on the first page is retrieved for display. When entering the list page, defaultParams is used as the query condition by default to obtain the corresponding list data. It can be understood that when the query condition of the list page is the initial query condition, the initial state of the list page is displayed, that is, the original list page. When the user queries the details of a certain piece of data on the first page, the user can jump from the original list page to the details page of this data. When returning from this details page, defaultParams is used as the query condition. At this time, defaultParams is the initial query condition, and the list data on the first page is obtained according to the initial query condition, that is, the user can directly jump back to the original list page from this details page.

[0114] In the exemplary embodiment of the present disclosure, the Vue framework is used to implement the page display of a single-page application. Therefore, before jumping back from the subpage to the parent page, that is, before returning from the details page to the intermediate list page, a second parameter memory variable, namely hasMemory, can also be defined. This second parameter memory variable can be used to mark whether there are page jump parameters of the parent page in the target file. For example, if hasMemory = false, it means that there are no page jump parameters of the parent page in the target file; if hasMemory = true, it means that there are page jump parameters of the parent page in the target file, that is, the query conditions carried by the parent page exist in the pageJumpMemory.js file. At the same time, a second navigation guard, namely the beforeRouteEnter hook function, can also be defined. This guard can be used to assign values to the path attributes of the parent page and the subpage in the second object, and when it is determined that the second object exists in the target file by traversing the target file, assign values to the second parameter memory variable corresponding to the parent page in the second object. Specifically, when defining the beforeRouteEnter hook function in the parent page, three parameters, namely to, from, and next, also need to be passed in. Among them, the parameter to represents the current page, the parameter from represents the previous page, and the page jump is executed by calling the next function, and the execution effect depends on the calling parameters of the next function.

[0115] For example, a temporary object temp2 = {fatherPage: '', sonPage: ''} can be defined as the second object. Through the beforeRouteEnter hook function, the path property value of the parameter to can be assigned to temp2.son, and the path property value of the parameter from can be assigned to temp2.father. Based on the assigned path property value, it is possible to jump back from the sub-page to the parent page, that is, jump from the current page to the previous page. Then, the configured pageJumpMemory.js file can be traversed to determine whether the temp2 object exists in the file. If the temp2 object exists in the pageJumpMemory.js file, the second parameter memory variable hasMemory will be assigned the value true; if the temp2 object does not exist in the pageJumpMemory.js file, the second parameter memory variable hasMemory will be assigned the value false.

[0116] When a user queries the details of a certain piece of data in the middle list page, they can jump from the middle list page to the details page of that data. When returning from the details page, defaultParams will be used as the query condition, and the list data of the original list page will be obtained based on the initial query condition, that is, it is possible to jump back from the details page to the original list page. When the user views the detailed content of the target data on the details page and returns from the details page, to avoid losing the previous query result due to page refresh when returning from the details page to the original list page, the parameter parsing function can be called, and the parameter parsing function can be used to return from the details page to the list page that retains the previous query result, that is, return to the middle list page. In the exemplary implementation manner of the present disclosure, the parameter parsing function can be the getMemoryParams function. Exemplarily, when receiving a trigger operation by the user on the page back button in the browser interface, the beforeRouteEnter hook function can be triggered to call the getMemoryParams function, and the getMemoryParams function can be used to complete the acquisition and parsing of the previous query condition before entering the list page, so as to facilitate modifying the value of defaultParams according to the parsing result, and then restoring the previous query result, without the user having to perform operations such as filtering on the list page again, improving the user experience.

[0117] Exemplarily, when returning from the detail page to the middle list page, the getMemoryParams function can be called before entering the middle list page using the beforeRouteEnter hook function. A request is sent to the server through the getMemoryParams function to obtain the page jump parameters for the middle list page, and the middle list page is returned from the detail page based on the page jump parameters. Among them, the request sent to the server can be an HTTP request. For example, a second request such as a GET request can be sent to the server to enable the server to return the page jump parameters for the middle list page.

[0118] In an exemplary implementation manner, referring to Figure 6 as shown, it is possible to jump back from the sub-page to the parent page that retains the previous query result according to steps S610 to S630. For example, it is possible to jump back from the detail page to the middle list page.

[0119] Step S610. When it is determined by the parameter parsing function that the value of the second parameter memory variable is the target value, a second request is sent to the server to obtain the target parameter string from the server.

[0120] Specifically, when calling the getMemoryParams function, parameters for extracting the previous query conditions can be passed in, including the parameters reg, to, from, and next. Among them, reg is a regular expression, and reg can be used to match the URL of the detail page corresponding to the current list page. to and from can be obtained from the beforeRouteEnter hook function. Both to and from are object-type data. Information about the list page can be obtained through to, and information about the page where the list page was entered from can be obtained through from. next is a jump function. The beforeRouteEnter hook function requires the business code to call the next function after execution is complete, which is used to mark the completion of the function and enter the page loading process.

[0121] After passing the parameters, the getMemoryParams function can be used to obtain the target parameter string. Exemplarily, when returning from the details page, the getMemoryParams function can be used to check whether the query conditions for the intermediate list page are stored in the database. Exemplarily, when the value of the second parameter memory variable hasMemory is the target value true, it indicates that there are page jump parameters for the intermediate list page in the database. Then, a second request such as a get request can be sent to the server to obtain the target parameter string from the server. It can be understood that if the intermediate list page and the details page do not exist in the pageJumpMemory.js file, that is, when hasMemory = false, it can indicate that this page jump is not from the specified details page back to the intermediate list page, or there are no page jump parameters for the intermediate list page in the database. At this time, next() can be directly executed to enter the list page, that is, return to the initial state of the list page.

[0122] Step S620. Decrypt the target parameter string to obtain the first parameter string.

[0123] After obtaining the target parameter string from the server, the target parameter string can be parsed to obtain the page jump parameters. Exemplarily, when jumping from the intermediate list page to the details page, the options object is first converted into a params string, then the params string is encoded using the encodeURI function, and the encoded result of the params string is Base64 encoded. The encoded result of the encrypted params string is used to obtain the params string "cGFnZU51bTo1LCBw…". Correspondingly, when parsing the params string "cGFnZU51bTo1LCBw…", the params string "cGFnZU51bTo1LCBw…" can be first Base64 decrypted to obtain the decrypted params string "%7BpageNum%3Apagesize%22…", which is the first parameter string, facilitating subsequent decoding of the first parameter string to obtain the initial parameter string and converting the initial parameter string into the page jump parameters.

[0124] Step S630. Decode the first parameter string to obtain the initial parameter string, and convert the initial parameter string into the page jump parameters of the parent page.

[0125] After obtaining the first parameter string, the first parameter string can be decoded to obtain the initial parameter string, and the initial parameter string can be converted into the page jump parameter of the intermediate list page. Exemplarily, the decodeURI function can be used to decode the decrypted params string “%7BpageNum%3Apagesize%22…” to obtain the decoded params string {”pageNum”:2,”pageSize”:10,”alarmType”:1}, which is the initial parameter string. Then, the params string can be restored to the object type data options{pageNum:2,pageSize:10,alarmType:1}.

[0126] In other examples, if the target parameter string is the params string “%7BpageNum%3Apagesize%22…”, the decodeURI function can be used to decode the params string “%7BpageNum%3Apagesize%22…” to obtain the decoded params string {”pageNum”:2,”pageSize”:10,”alarmType”:1}. Then, the decoded params string can be restored to the object type data options{pageNum:2,pageSize:10,alarmType:1}. If the target parameter string is the params string {”pageNum”:2,”pageSize”:10,”name”:”name1”,”type”:”type1”}, the params string can be directly restored to the object type data options{pageNum:2,pageSize:10,name:'name1',type:'type1'}, and the present disclosure makes a limitation on this.

[0127] Step S640. Jump back from the subpage to the parent page according to the page jump parameter.

[0128] After extracting the page jump parameter, the current value of the page jump parameter can be assigned to the option variable defaultParams, so as to jump back from the detail page to the intermediate list page according to the assigned option variable. Exemplarily, after the assignment, the option variable defaultParams changes from the initial query condition {pageNum:1,pageSize:10} to options{pageNum:2,pageSize:10,alarmType:1}, and by calling next() to enter the intermediate list page, that is, it realizes jumping back from the detail page to the list page that retains the previous query result.

[0129] It should be noted that after jumping back from the detail page to the list page that retains the previous query result according to the page jump parameter, the page jump parameter stored in the database can be deleted, so that there are only 0 or 1 records in the database table, greatly reducing the storage pressure on the database. For example, the deletion of the page jump parameter can be achieved through a delete request, and the specific implementation method of deleting the page jump parameter can be changed according to the specific implementation scenario, and the present disclosure does not make specific limitations thereon.

[0130] In this example, when developing a single-page application using the Vue-cli framework, only a parameter parsing function needs to be added to the source code of the parent page to achieve jumping back from the child page to the parent page that retains the previous query result. When returning from the child page, the query result of the parent page is restored by reading the previously recorded query conditions, without modifying the source code of the child page, reducing the workload of users and improving the page operation efficiency of users.

[0131] In an exemplary implementation manner, referring to Figure 7 as shown, it is possible to implement jumping back from the detail page to the list page according to steps S701 to S708.

[0132] Step S701. Check whether the list page and the detail page exist in the pageJumpMemory.js file. If so, execute step S702; if not, and this page jump is not from the specified detail page to the intermediate list page, or the page jump parameter of the intermediate list page does not exist in the database, then execute step S707;

[0133] Step S702. Send a get request to the server to obtain the params string;

[0134] Step S703. Decode the params string;

[0135] Step S704. Decrypt the decoded params string;

[0136] Step S705. Convert the decrypted params string into an options object;

[0137] Step S706. Assign options to defaultParams;

[0138] Step S707. Enter the list page, for example, next() can be executed to enter the list page;

[0139] Step S708. Use defaultParams to request list data, render the list data and display it to the user through the terminal device.

[0140] In the exemplary embodiments of the present disclosure, two steps are required to retain the previous query result when returning from the details page to the list page: First, before leaving the list page, in the beforeRouterLeave hook function of the list page, call the page jump function (such as the toDetails function) to determine whether the query conditions of the current page need to be remembered. If they need to be remembered, send a post request to the server to store the query conditions. Before sending the post request to the server, the query conditions have been base64 encoded, which can ensure the security of the request. Second, before entering the list page, in the beforeRouteEnter hook function of the list page, call the parameter parsing function (such as the getMemoryParams function) to determine whether there are query conditions for the list page. If there are, send a get request to the server to obtain the query conditions, read and parse the obtained query conditions to get the previous query conditions options, and modify the page default query conditions, that is, the option variable defaultParams, to the previous query conditions options, then the restoration of the previous query result on the list page can be completed. This method only needs to add a page jump function and a parameter parsing function to the source code of the list page, without modifying the source code of the details page, reducing the workload required for the user to complete this function and improving the user's operation efficiency. In addition, based on the http request, the storage and acquisition of the page jump parameters are realized, and then the function of retaining and obtaining the previous query conditions is realized. There is no need to use memory to store data, reducing memory consumption, thereby improving the display performance of the page.

[0141] In one exemplary embodiment, with reference to Figure 8 as shown, the page display can be performed according to steps S801 to S807.

[0142] Step S801. Configure the parent-child page relationship. Configure the pageJumpMemory.js file in the Vue-store of the browser to store and maintain the parent-child relationship pages and whether the page jump parameters of the parent page need to be remembered;

[0143] Step S802. Before page jump, assign a value to the first parameter memory variable. Determine whether the current page and the target page exist in the pageJumpMemory.js file. If they exist, assign the value true to the first parameter memory variable; otherwise, assign the value false to the first parameter memory variable;

[0144] Step S803. When page jumping, send a post request to the server according to the first parameter memory variable to store the page jump parameters. When the value of the first parameter memory variable is true, the encoded page jump parameters can be sent to the server through a post request, so that the server stores the page jump parameters in the database;

[0145] Step S804. The server receives the post request sent by the browser and stores the page jump parameters in the database;

[0146] Step S805. When the page returns, send a get request to the server to obtain the page jump parameters;

[0147] Step S806. The server receives the get request sent by the browser, obtains the page jump parameters from the database, returns the page jump parameters to the browser, and clears the page jump parameters stored in the database in a timely manner;

[0148] Step S807. Decode the obtained page jump parameters, and request the corresponding data according to the decoding result to re-render the browser page.

[0149] In this example, on the one hand, when entering the sub-page from the parent page, the server can store the page jump parameters. When returning from the sub-page, the page jump parameters can be obtained from the server, and the previous parent page can be restored according to the page jump parameters, avoiding page refresh caused by page jumping. Users can obtain the previous query results without having to operate again, thereby improving the user experience. On the other hand, the storage and acquisition of page jump parameters can be achieved through interaction with the server, without using memory to store data, reducing memory consumption, and thus improving the display performance of the page.

[0150] Reference Figure 9A As shown, a schematic list page displayed when an application program for operation and maintenance services is running is given. It can be seen that Figure 9AIt shows the initial state of the list page, that is, the original list page. The corresponding query conditions are "name:", "pageNum:1", which means the data on the first page without filtering conditions. There are 6 list data in this list page. Each list data includes a work order number, a work order name, and a work order status. For example, the first list data is a test work order with the work order number 202101, and the current status of this work order is resolved. It can be understood that each list data in the list page can be used as target data. When the user selects a certain list data, that is, when selecting a certain work order, the user can perform the "View Details" operation corresponding to the work order to enter the details page of the work order from the current list page. For example, when clicking "View Details", the beforeRouteLeave hook function can be triggered, and the toDetails function can be called through the beforeRouteLeave hook function to use the toDetails function to jump from the current list page to the details page of the work order while storing the query conditions of the current list page on the server side. Among them, "work order number", "work order name", and "work order status" can all be used as filtering conditions, and the page number and 6 data per page can be used as paging conditions. In addition, the user can also directly select the target page number to go to the corresponding intermediate list page.

[0151] Exemplarily, when the user enters the work order name "Prohibit Invasion" and then clicks the search button, 100 list data can be filtered. After the filtering is completed, the list page where the "Prohibit Invasion" work order is located can be shown to the user. Refer to Figure 9B As shown, a schematic list page with filtering conditions and paging conditions is given, that is, the intermediate list page. It can be seen that the corresponding query conditions for this list page are "name: Prohibit Invasion, pageNum: 6", Figure 9B and the 6 list data in it are all Prohibit Invasion work orders. Each list data can be used as target data. When the user performs the view details operation on a certain list data, the user can Figure 9B jump from the list page shown as follows to the details page corresponding to the list data. For example, when the user selects the Prohibit Invasion work order with the work order number 202131 and performs the view details operation, the user can enter the details page of this work order from the current list page, such as Figure 9C the details page shown as follows. There are 6 details data in this details page, which are work order name, work order number, work order status, creator, creator contact information, creation time, and relevant pictures.

[0152] When returning from Figure 9C the details page shown as follows, it can return to Figure 9B the list page shown as follows, directly showing the 6th page list data with the filtering condition of "Prohibit Invasion" to the user, instead of returning to Figure 9AThe list page shown. For example, when the "Back" operation is clicked, the beforeRouteEnter hook function can be triggered, and the getMemoryParams function can be called through the beforeRouteEnter hook function to use the getMemoryParams function to obtain the page jump parameters of the list page shown in Figure 9B from the server, and re-request the list data and render the page according to the page jump parameters. When returning from the detail page to the list page, the last query result can be retained for the user to view, improving the user experience.

[0153] It can be understood that when the user performs Figure 9A the operation of viewing the details of a certain list data in Figure 9A the list page shown, it can jump from Figure 9A the list page shown to the detail page corresponding to the list data. When returning from the detail page, it can jump back to

[0154] the list page shown, that is, return to the initial state of the list page, and similarly, the function of retaining the last query result when returning from the detail page to the list page is also realized.

[0155] It should be noted that the parent and child pages in the exemplary embodiments of the present disclosure include, but are not limited to, a list page and a detail page. That is to say, the parent and child pages can be any two pages in the page display scenario by storing and obtaining page jump parameters. The present disclosure does not make specific limitations on this.

[0156] In the page display method provided by the exemplary embodiments of the present disclosure, when a query operation on target data in the parent page is received, a first request is sent to the server to store the page jump parameter of the parent page, and the page jumps from the parent page to the child page corresponding to the target data; a second request is sent to the server to obtain the page jump parameter of the parent page, and the page jumps back from the child page to the parent page according to the page jump parameter. On the one hand, when entering the child page from the parent page in the present disclosure, the server can store the page jump parameter, and when returning from the child page, the page jump parameter can be obtained from the server, and the previous parent page can be restored according to the page jump parameter, avoiding page refresh caused by page jump, and the user can obtain the previous query result without re-operation, thereby improving the user experience; on the other hand, the storage and acquisition of page jump parameters can be achieved through interaction with the server, without using memory to store data, reducing memory consumption, and thus improving the display performance of the page.

[0157] It should be noted that although the steps of the method in the present disclosure are described in a specific order in the drawings, this does not require or imply that these steps must be executed in this specific order, or that all the steps shown must be executed to achieve the desired result. Additionally or alternatively, some steps may be omitted, multiple steps may be combined into one step for execution, and / or one step may be decomposed into multiple steps for execution, etc.

[0158] Furthermore, in the exemplary embodiments of the present disclosure, a page display device is further provided. This device can be applied to a terminal device or a server. Refer to Figure 10 As shown, the page display device 1000 may include a first page display module 1010 and a second page display module 1020, where:

[0159] The first page display module 1010 is configured to, when a query operation on target data in the parent page is received, send a first request to the server to store the page jump parameter of the parent page, and jump from the parent page to the child page corresponding to the target data;

[0160] The second page display module 1020 is configured to send a second request to the server to obtain the page jump parameter of the parent page, and jump back from the child page to the parent page according to the page jump parameter.

[0161] In an optional embodiment, the page display device 1000 further includes:

[0162] A file configuration module for configuring a target file, where the target file is used to store the parent - child relationship between the parent page and the child page.

[0163] In an optional implementation, the page display device 1000 further includes:

[0164] A first variable definition module for defining a first parameter memory variable, where the first parameter memory variable is used to mark whether to remember the page jump parameter of the parent page;

[0165] A first guard definition module for defining a first navigation guard, where the first navigation guard is used to assign values to the path attributes of the parent page and the child page in the first object, and when it is determined that the first object exists in the target file by traversing the target file, assign a value to the first parameter memory variable corresponding to the parent page in the first object.

[0166] In an optional implementation, the first page display module 1010 includes:

[0167] A parameter acquisition unit for acquiring the page jump parameter of the parent page and the first parameter memory variable when a query operation on the target data in the parent page is received;

[0168] A parameter conversion unit for converting the page jump parameter into a target parameter string when it is determined that the first parameter memory variable meets a preset condition by using a page jump function;

[0169] A parameter storage unit for sending a first request carrying the target parameter string to the server to store the target parameter string in the server and jumping from the parent page to the child page corresponding to the target data.

[0170] In an optional implementation, the parameter conversion unit includes:

[0171] A parameter conversion sub - unit for converting the page jump parameter into an initial parameter string when it is determined that the value of the first parameter memory variable is a target value by using a page jump function;

[0172] A string encoding sub - unit for encoding the initial parameter string to obtain a first parameter string;

[0173] A string encryption sub - unit for encrypting the first parameter string to obtain the target parameter string.

[0174] In an optional implementation, the page display device 1000 further includes:

[0175] A second variable definition module for defining a second parameter memory variable, which is used to mark whether there is a page jump parameter of the parent page in the target file;

[0176] A second guard definition module for defining a second navigation guard, which is used to assign values to the path attributes of the parent page and the path attributes of the child page in a second object, and, when it is determined that the second object exists in the target file by traversing the target file, assign a value to the second parameter memory variable corresponding to the parent page in the second object.

[0177] In an alternative embodiment, the second page display module 1020 includes:

[0178] A string acquisition unit for sending a second request to the server to obtain the target parameter string from the server when it is determined by a parameter parsing function that the value of the second parameter memory variable is a target value;

[0179] A string decryption unit for decrypting the target parameter string to obtain the first parameter string;

[0180] A string decoding unit for decoding the first parameter string to obtain the initial parameter string and converting the initial parameter string into the page jump parameter of the parent page;

[0181] A page jump unit for jumping back from the child page to the parent page according to the page jump parameter.

[0182] In an alternative embodiment, the page jump unit includes:

[0183] A parameter assignment sub-unit for assigning the current value of the page jump parameter to an option variable, which is used to save the default value of the page jump parameter;

[0184] A page jump sub-unit for jumping back from the child page to the parent page according to the assigned option variable.

[0185] The specific details of each module in the above page display device have been described in detail in the corresponding page display method, so they will not be elaborated here.

[0186] Each module in the above device may be a general-purpose processor, including: a central processing unit, a network processor, etc.; it may also be a digital signal processor, an application-specific integrated circuit, a field programmable gate array or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components. Each module may also be implemented in the form of software, firmware, etc. Each processor in the above device may be an independent processor or integrated together.

[0187] Exemplary embodiments of the present disclosure also provide a computer-readable storage medium having a program product stored thereon that can implement the methods described above in this specification. In some possible embodiments, various aspects of the present disclosure may also be implemented in the form of a program product, which includes program code that, when the program product runs on an electronic device, causes the electronic device to execute the steps according to various exemplary embodiments of the present disclosure described in the "Exemplary Methods" section above in this specification. The program product may be a portable compact disc read-only memory (CD-ROM) and includes program code, and may run on an electronic device, such as a personal computer. However, the program product of the present disclosure is not limited thereto. In this document, the readable storage medium may be any tangible medium that contains or stores a program that can be used by or in conjunction with an instruction execution system, apparatus, or device.

[0188] The program product may employ any combination of one or more readable media. The readable media may be a readable signal medium or a readable storage medium. The readable storage medium may, for example, but not be limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the above. More specific examples (a non-exhaustive list) of the readable storage medium include: an electrical connection having one or more wires, a portable disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above.

[0189] The computer-readable signal medium may include a data signal propagated in a baseband or as part of a carrier wave, which carries the readable program code. Such a propagated data signal may take various forms, including but not limited to an electromagnetic signal, an optical signal, or any suitable combination of the above. The readable signal medium may also be any readable medium other than the readable storage medium, which can send, propagate, or transmit a program for use by or in conjunction with an instruction execution system, apparatus, or device.

[0190] The program code contained on the readable medium may be transmitted using any appropriate medium, including but not limited to wireless, wired, optical fiber cable, RF, etc., or any suitable combination of the above.

[0191] Program code for performing the operations of the present disclosure can be written in any combination of one or more programming languages, including object-oriented programming languages such as Java, C++, etc., and also including conventional procedural programming languages such as the "C" language or similar programming languages. The program code can be executed entirely on the user's computing device, partially on the user's device, executed as a stand-alone software package, partially on the user's computing device and partially on a remote computing device, or entirely on a remote computing device or server. In cases involving a remote computing device, the remote computing device can be connected to the user's computing device through any type of network, including a local area network (LAN) or a wide area network (WAN), or, it can be connected to an external computing device (e.g., by connecting through the Internet using an Internet service provider).

[0192] Exemplary embodiments of the present disclosure also provide an electronic device capable of implementing the above method. The following will refer to Figure 11 to describe the electronic device 1100 according to such an exemplary embodiment of the present disclosure. Figure 11 The illustrated electronic device 1100 is merely an example and should not impose any limitations on the functions and scope of use of the embodiments of the present disclosure.

[0193] As Figure 11 shown, the electronic device 1100 can be presented in the form of a general-purpose computing device. The components of the electronic device 1100 may include, but are not limited to: at least one processing unit 1110, at least one storage unit 1120, a bus 1130 connecting different system components (including the storage unit 1120 and the processing unit 1110), and a display unit 1140.

[0194] The storage unit 1120 stores program code, and the program code can be executed by the processing unit 1110, so that the processing unit 1110 executes the steps according to various exemplary embodiments of the present disclosure described in the above "Exemplary Method" section of this specification. For example, the processing unit 1110 can execute Figures 2 to 8 any one or more of the method steps.

[0195] The storage unit 1120 may include a readable medium in the form of a volatile storage unit, such as a random access storage unit (RAM) 1121 and / or a cache storage unit 1122, and may further include a read-only storage unit (ROM) 1123.

[0196] The storage unit 1120 may also include a program / utility 1124 having a set (at least one) of program modules 1125. Such program modules 1125 include, but are not limited to, an operating system, one or more application programs, other program modules, and program data. Each or some combination of these examples may include the implementation of a network environment.

[0197] The bus 1130 may represent one or more of several types of bus structures, including a memory bus or memory controller, a peripheral bus, an accelerated graphics port, a processing unit, or a local bus using any of a variety of bus structures.

[0198] The electronic device 1100 may also communicate with one or more external devices 1200 (such as a keyboard, a pointing device, a Bluetooth device, etc.), and may also communicate with one or more devices that enable a user to interact with the electronic device 1100, and / or communicate with any device that enables the electronic device 1100 to communicate with one or more other computing devices (such as a router, a modem, etc.). Such communication may be through the input / output (I / O) interface 1150. Moreover, the electronic device 1100 may also communicate with one or more networks (such as a local area network (LAN), a wide area network (WAN), and / or a public network, such as the Internet) through the network adapter 1160. As shown in the figure, the network adapter 1160 communicates with other modules of the electronic device 1100 through the bus 1130. It should be understood that, although not shown in the figure, other hardware and / or software modules may be used in conjunction with the electronic device 1100, including but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, and data backup storage systems, etc.

[0199] Through the description of the above embodiments, those skilled in the art can easily understand that the exemplary embodiments described herein can be implemented by software, or by a combination of software and necessary hardware. Therefore, the technical solutions according to the embodiments of the present disclosure can be embodied in the form of a software product, which can be stored in a non-volatile storage medium (which can be a CD-ROM, a USB flash drive, a mobile hard disk, etc.) or on a network, including several instructions to enable a computing device (which can be a personal computer, a server, a terminal device, or a network device, etc.) to execute the method according to the exemplary embodiments of the present disclosure.

[0200] In addition, the above drawings are only schematic illustrations of the processes included in the method according to the exemplary embodiments of the present disclosure, rather than for limiting purposes. It is easy to understand that the processes shown in the above drawings do not indicate or limit the time sequence of these processes. Additionally, it is also easy to understand that these processes may be executed, for example, synchronously or asynchronously in multiple modules.

[0201] It should be noted that although several modules or units of the device for action execution are mentioned in the above detailed description, such a division is not mandatory. In fact, according to the embodiments of the present disclosure, the features and functions of the two or more modules or units described above can be embodied in one module or unit. Conversely, the features and functions of one module or unit described above can be further divided and embodied by multiple modules or units.

[0202] It should be understood that the present disclosure is not limited to the exact structures already described and shown in the drawings, and various modifications and changes can be made without departing from its scope. The scope of the present disclosure is only limited by the appended claims.

Claims

1. A page display method, characterized in that, Including: When receiving a query operation for target data in the parent page, send a first request to the server to store the page jump parameters of the parent page, and jump from the parent page to the sub-page corresponding to the target data; Send a second request to the server to obtain the page jump parameters of the parent page, and jump back from the sub-page to the parent page according to the page jump parameters; Before jumping from the parent page to the sub-page corresponding to the target data, the method further includes: Configure a target file, which is used to store the parent-child relationship between the parent page and the sub-page; Define a first parameter memory variable, which is used to mark whether to remember the page jump parameters of the parent page; Define a first navigation guard, which is used to assign values to the path attributes of the parent page and the sub-page in the first object, and when it is determined that the first object exists in the target file by traversing the target file, assign a value to the first parameter memory variable corresponding to the parent page in the first object.

2. The page display method according to claim 1, wherein When receiving a query operation for target data in the parent page, send a first request to the server to store the page jump parameters of the parent page, and jump from the parent page to the sub-page corresponding to the target data, including: When receiving a query operation for target data in the parent page, obtain the page jump parameters of the parent page and the first parameter memory variable; When it is determined that the first parameter memory variable meets the preset conditions by using the page jump function, convert the page jump parameters into a target parameter string; Send a first request carrying the target parameter string to the server to store the target parameter string in the server, and jump from the parent page to the sub-page corresponding to the target data.

3. The page display method according to claim 2, wherein When it is determined that the first parameter memory variable meets the preset conditions by using the page jump function, convert the page jump parameters into a target parameter string, including: When it is determined that the value of the first parameter memory variable is the target value by using the page jump function, convert the page jump parameters into an initial parameter string; Encode the initial parameter string to obtain a first parameter string; Encrypt the first parameter string to obtain the target parameter string.

4. The page display method according to claim 1, wherein Before jumping back from the sub-page to the parent page, the method further includes: Define a second parameter memory variable, which is used to mark whether the page jump parameters of the parent page exist in the target file; Define a second navigation guard, which is used to assign values to the path attributes of the parent page and the sub-page in the second object, and when it is determined that the second object exists in the target file by traversing the target file, assign a value to the second parameter memory variable corresponding to the parent page in the second object.

5. The page display method according to claim 4, wherein Send a second request to the server to obtain the page jump parameters of the parent page, and jump back from the sub-page to the parent page according to the page jump parameters, including: When it is determined that the value of the second parameter memory variable is the target value by using the parameter parsing function, a second request is sent to the server to obtain the target parameter string from the server; Decrypt the target parameter string to obtain the first parameter string; Decode the first parameter string to obtain the initial parameter string, and convert the initial parameter string into the page jump parameter of the parent page; Jump back to the parent page from the child page according to the page jump parameter.

6. The page display method according to claim 5, wherein The jumping back to the parent page from the child page according to the page jump parameter includes: Assign the current value of the page jump parameter to an option variable, and the option variable is used to save the default value of the page jump parameter; Jump back to the parent page from the child page according to the assigned option variable.

7. A page display device, characterized in that, Includes: A first page display module, which is used to send a first request to the server to store the page jump parameter of the parent page when a query operation on the target data in the parent page is received, and jump from the parent page to the child page corresponding to the target data; A second page display module, which is used to send a second request to the server to obtain the page jump parameter of the parent page, and jump back to the parent page from the child page according to the page jump parameter; A file configuration module, which is used to configure a target file for storing the parent-child relationship between the parent page and the child page; A first variable definition module, which is used to define a first parameter memory variable for marking whether to remember the page jump parameter of the parent page; A first guard definition module, which is used to define a first navigation guard for assigning values to the path attributes of the parent page and the path attributes of the child page in a first object, and when it is determined that the first object exists in the target file by traversing the target file, assign a value to the first parameter memory variable corresponding to the parent page in the first object.

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

9. An electronic device, characterized in that, Includes: A processor; And A memory for storing executable instructions of the processor; Wherein, the processor is configured to execute the method according to any one of claims 1-6 by executing the executable instructions.

Images