Interface display method, electronic device and storage medium

Abstract

The application discloses an interface display method, an electronic device and a storage medium. The method comprises the following steps: acquiring configuration data matched with a current object, wherein the configuration data defines interface display parameters of various interface components; in response to a query request, determining a query strategy, wherein the query strategy comprises a progressive query and a full-quantity query, the progressive query is used for querying query data of a second field after querying query data of a first field, the priority of the first field is higher than that of the second field, and the full-quantity query is used for querying query data of all fields matched with the query request; based on the query strategy, querying query data of a target field matched with the query request, and displaying a query result interface based on the configuration data and the query data. The page configuration of the newly-added object can be realized without programming, the development efficiency is relatively high, the progressive loading scheme can be adopted, the page loading speed can be improved, and the work efficiency is improved.

Description

Technical Field

[0001] This application relates to the field of interface display technology, specifically to an interface display method, electronic device, and storage medium. Background Technology

[0002] Currently, when adding a new page management role, the subsystem needs to be redeveloped to program the page layout, fields, buttons, etc. of the new role separately. This not only results in low page development efficiency, but also causes slow page loading if the amount of data loaded is too large, requiring users to wait for a long time, which greatly affects the overall work efficiency. Summary of the Invention

[0003] This application provides an interface display method, electronic device, and storage medium. By configuring objects in various interface components, page configuration of new objects can be achieved without programming, resulting in high development efficiency. It also features a sampling progressive loading scheme, prioritizing the timely display of high-priority first field data on the page, thereby improving page loading speed and work efficiency.

[0004] On one hand, embodiments of this application provide an interface display method, the method comprising: Get the configuration data that matches the current object. The configuration data defines the interface display parameters of each interface component. In response to a query request, a query strategy is determined. The query strategy includes progressive query and full query. The progressive query is used to retrieve query data for the second field after retrieving query data for the first field, with the first field having a higher priority than the second field. The full query is used to retrieve query data for all fields that match the query request. Based on the query strategy, query data matching the target field of the query request is retrieved, and the query results interface is displayed based on the configuration data and the query data.

[0005] On the other hand, embodiments of this application provide an electronic device, which includes a processor and a memory. The memory stores a computer program, and the processor executes the interface display method as described in any of the above embodiments by calling the computer program stored in the memory.

[0006] On the other hand, embodiments of this application provide a computer-readable storage medium storing a computer program adapted for loading by a processor to execute the interface display method as described in any of the above embodiments.

[0007] The interface display method, electronic device, and storage medium provided in this application embodiment can configure the page for newly added objects and configure the interface display parameters of each interface component of the newly added object. There is no need to supplement the page code in the system. The system can quickly display each UI component corresponding to the newly added object by reading the configuration data of the newly added object, thereby realizing the page display of the newly added object.

[0008] Furthermore, when users need to query data, a specific query strategy can be determined based on the query request. In scenarios where data needs to be displayed quickly, a progressive query strategy can be used to retrieve data, allowing the page to load data based on the highest priority first field obtained from the query, quickly displaying the first screen, improving page loading efficiency, and enabling users to quickly see the more important first field data, reducing user waiting time and improving user work efficiency. While the user is viewing the first field data, the system continues to query and load the second field data, achieving progressive data loading. This ensures both the efficiency of the first screen loading and the integrity of the data loading process. Attached Figure Description

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

[0010] Figure 1 This is a schematic diagram of an example interface display system provided in an embodiment of this application.

[0011] Figure 2 This is a first flowchart illustrating the interface display method provided in an embodiment of this application.

[0012] Figure 3 This is a schematic diagram of a scenario for the interface display method provided in the embodiments of this application.

[0013] Figure 4 This is a second flowchart illustrating the interface display method provided in an embodiment of this application.

[0014] Figure 5 A schematic diagram of the interface display device provided in the embodiments of this application.

[0015] Figure 6 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application. Detailed Implementation

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

[0017] This application provides an interface display method, apparatus, storage medium, device, and program product. Specifically, the interface display method of this application can be executed by an electronic device, which can be a terminal or server, etc.

[0018] The terminal can be a smartphone, tablet, laptop, smart TV, wearable smart device, smart vehicle terminal, etc. The terminal can also include a client, which can be a game client, browser client, instant messaging client, or mini-program, etc.

[0019] A server can be a standalone physical server, a server cluster or distributed system consisting of multiple physical servers, or a cloud server that provides basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communication, middleware services, domain name services, security services, content delivery networks (CDN), and big data and artificial intelligence platforms.

[0020] It should be noted that in this embodiment of the application, the execution subject of the interface display method can be a terminal device or a server, and this embodiment of the application does not limit the type of execution subject.

[0021] It is understood that in the specific implementation of this application, user object data, context data and other related data are involved. When the embodiments of this application are applied to specific products or technologies, user permission or consent is required, and the collection, use and processing of related data must comply with the relevant laws, regulations and standards of the relevant countries and regions.

[0022] For example, in conjunction with the above description, Figure 1 This application illustrates an interface display system 1000 for implementing an interface display method, as provided in an embodiment of this application. The interface display system 1000 may include at least one terminal 1001, at least one server 1002, at least one database 1003, and a network. The terminal 1001 can connect to different servers via the network. The terminal can be any device with computing hardware capable of supporting and executing software application tools corresponding to the game.

[0023] Furthermore, when the interface display system 1000 includes multiple terminals, multiple servers, and multiple networks, different terminals can connect to each other through different networks and servers. The network can be a wireless network or a wired network, such as a wireless local area network (WLAN), local area network (LAN), cellular network, 2G network, 3G network, 4G network, 5G network, etc. Additionally, different terminals can also connect to other terminals or to servers using their own Bluetooth networks or hotspot networks. Furthermore, the system 100 can include multiple databases, which are coupled to different servers, and can continuously store game-related information in the databases while different users are playing multiplayer games online.

[0024] It should be noted that, Figure 1 The schematic diagram of the interface display system shown is merely an example. The interface display system 1000 described in this application embodiment is intended to more clearly illustrate the technical solutions of this application embodiment and does not constitute a limitation on the technical solutions provided in this application embodiment. As those skilled in the art will know, with the evolution of interface display systems and the emergence of new business scenarios, the technical solutions provided in this application embodiment are also applicable to similar technical problems.

[0025] It should be noted that the triggering operations (such as editing configuration data) that appear in the subsequent detailed description of the interface display method provided in the embodiments of this application can all be regarded as triggering operations performed by the player through fingers or by controlling a medium such as a mouse, keyboard, or stylus. The specific medium used can be determined according to the type of electronic device. For example, when the electronic device is a touch screen device such as a mobile phone, tablet computer, or game console, the player can operate on the touch screen using any suitable object or accessory such as a finger or stylus. When the terminal device is a non-touch screen terminal device such as a desktop computer or laptop computer, the player can operate using external devices such as a mouse or keyboard.

[0026] The technical solution of this application will be described in detail below through specific embodiments. It should be noted that the following specific embodiments can be combined with each other, and the same or similar concepts or processes may not be described again in some embodiments.

[0027] Please see Figure 2 It should be noted that the steps shown may be executed in a logical order different from that shown in the flowchart of this method. The interface display method of this application may include the following steps: Step 011: Obtain the configuration data matching the current object. The configuration data defines the interface display parameters of each interface component.

[0028] Here, the current object refers to an object in the system that has access to specific data. Based on different permissions, different objects can generally access different data. For example, the system has multiple preset user groups, and the current object is an object of any preset user group. Different preset user groups have different permissions, and corresponding configuration data can be assigned and set for different preset user groups.

[0029] The configuration data is used to define the interface corresponding to the current object, such as the interface display parameters (style, size, parameters, etc.) of each interface component (i.e., UI component) in the interface, so that the system can quickly render each UI component based on the configuration data to display the interface corresponding to the current object.

[0030] In an optional embodiment, the configuration data may further include permission configuration data, used to configure the permissions of the current object (such as configuring the preset user group to which the current object belongs), and different preset user groups correspond to different sets of accessible data fields.

[0031] When querying data for the current object, the target field can be retrieved from the set of fields corresponding to its permissions.

[0032] After the current object logs in, the system can obtain the configuration identifier corresponding to the current object, and then read the configuration data corresponding to the configuration identifier from the database to obtain the configuration data matching the current object.

[0033] In this way, by obtaining the configuration data that matches the current object, the system can quickly render the various UI components of the interface based on the configuration data, and realize the display of the page framework.

[0034] Furthermore, compared to implementing page display through programming, implementing page display using configuration data allows for quick configuration of pages for newly added objects based on different business scenarios, and enables personalized configuration of pages for newly added objects, resulting in higher scalability and maintenance efficiency.

[0035] Step 012: In response to the query request, determine the query strategy. The query strategy includes progressive query and full query. Progressive query is used to retrieve query data for the second field after retrieving query data for the first field. The first field has a higher priority than the second field. Full query is used to retrieve query data for all fields that match the query request.

[0036] A query request is a request to retrieve data from the database and display it on the page.

[0037] In one alternative embodiment, the interface component includes a filtering component S1, which includes at least one filtering condition component S11, and generates a query request in response to an edit operation on each filtering condition component S11.

[0038] For example, the filter component S11 includes at least one drop-down box, a selection box, and a search box.

[0039] Please see Figure 3 By clicking the drop-down button in the drop-down menu, multiple preset filter conditions can be displayed. Selecting any one of these preset filter conditions will define the target filter. Users can also select or deselect the checkbox to confirm whether the target filter condition is selected. Alternatively, users can input the text to search for, thus defining the target filter condition based on the text.

[0040] In this way, by editing the various filter components, complex target filter conditions can be determined, thereby generating query requests to meet the personalized query needs of different users.

[0041] In an optional embodiment, step 012, in response to a query request, determines a query strategy, including: Step 0121: If the target field includes at least the first field, determine the query strategy as incremental query; Step 0122: If the target field only includes the second field, determine the query strategy as a full query.

[0042] When determining a query strategy, it can be based on the field types contained in the target fields matched by the query request. If the target fields include at least the first field, since the first field is of higher importance, it needs to be displayed on the page as quickly as possible. Therefore, in this case, a progressive query strategy can be determined, prioritizing the query data for the first field.

[0043] If the target field only includes the second field, the importance of the data is relatively low. Therefore, prioritizing the completeness of the data display allows us to determine a full query strategy.

[0044] Please combine Figure 3 In an optional embodiment, the interface component includes a table component S2, which is used to display query data. Step 012, in response to the query request, determines a query strategy, including: Step 0123: Determine the query strategy based on the data display volume configured in the table component.

[0045] It's understandable that the page includes a table component to display the query data. The number of rows and columns in the table component can be configured in advance; the more rows and columns, the more data the table component can display, and vice versa.

[0046] To avoid low query efficiency, data is typically loaded only based on the number of rows and columns of the table component. Therefore, the complete table component can be displayed simply by retrieving the query data corresponding to the number of rows and columns of the table component.

[0047] For example, if the target field has 100 rows and 10 columns of data, and the table component has 20 rows and 10 columns, then you only need to query the first 20 rows of data for the target field to display the data on the first screen of the table component.

[0048] In one alternative embodiment, the table component may include a pagination control for flipping through pages to load query data from the previous or next page. For example, after displaying the first page of query data (i.e., the first 20 rows), the second page of query data (i.e., rows 21 to 40) can be displayed in response to a page-turning operation.

[0049] Therefore, when determining the query strategy, the amount of data displayed in the table component can also be considered. When the amount of data displayed in the table component is small, even if the entire table component's query data is loaded, the query and loading time will be short. Therefore, the query strategy can be a full query to display as much of the query data as possible. However, when the amount of data displayed is high, the query and loading time will be longer. Therefore, the query strategy can be a progressive query to prioritize the first screen loading and load the data of the most important first field as quickly as possible.

[0050] Alternatively, if the target field includes at least the first field, but the amount of data displayed in the table component is small, the query strategy can still be determined as a full query; while if the target field only includes the second field, but the amount of data displayed in the table component is large, the query strategy can be determined as a progressive query.

[0051] The query strategies include incremental queries and full queries. Incremental queries prioritize important fields and postpone queries for less important fields. For example, if a database has a first field with higher priority and a second field with lower priority, an incremental query first sends a data request for the first field. After retrieving the data for the first field, it then sends a data request for the second field to retrieve the data for that field.

[0052] In an optional embodiment, the configuration data may further include priority information, allowing users to customize the priority of each field in the configuration database, defining each field as the first field or the second field.

[0053] Full query is a query strategy that queries all fields with the same priority. For example, it can simultaneously send data requests for all fields that match the query request to retrieve query data for all fields.

[0054] Step 013: Based on the query strategy, query the target field that matches the query request, and display the query results interface based on the configuration data and the query data.

[0055] The target field for matching the query request can be determined based on the various target filter conditions that generated the query request. For example, each target filter condition can correspond to at least one field, thus determining the target field for the query request.

[0056] Once the query strategy is determined, data can be queried based on that strategy. The query will retrieve the data matching the target fields of the query request.

[0057] Based on the configuration data, the page framework can be displayed first, enabling the rendering and display of the page and its various UI components. Based on the query data, the query data can then be displayed in the table component.

[0058] In one alternative embodiment, the query request and the query data of the target field that matches the current object are queried.

[0059] It's understandable that when selecting a target field, it's crucial to ensure that the target field is accessible to the current object. Therefore, we can first determine the set of fields corresponding to the current object based on the preset user group to which it belongs. Then, within this set of fields, we identify the target field that matches the query request, thus ensuring that the target field matches both the query request and the current object.

[0060] In this way, access control can be implemented when performing data queries based on query requests, thus ensuring data security.

[0061] In an optional embodiment, step 013 includes: Step 0131: When the query strategy is progressive query, the query data of the first field is obtained, and the query results interface is displayed based on the configuration data and the query data of the first field. Step 0132: After obtaining the query data for the first field, obtain the query data for the second field, and update the query results interface based on the query data for the second field.

[0062] When the query strategy is progressive query, the page loads progressively based on the query data obtained from the progressive query. For example, the page framework can be displayed based on the configuration data, and then after the query data for the first field is obtained, the query data for the first field can be displayed in a table component, thus displaying the query results interface.

[0063] After obtaining the query data for the first field, the query data for the second field is obtained, and the query results interface is updated based on the query data for the second field, thereby displaying the query data for all target fields.

[0064] In an optional embodiment, step 013 further includes: Step 0133: When the query strategy is full query, the query data of the second field is obtained, and the query results interface is displayed based on the configuration data and the query data of the second field.

[0065] When the query strategy is full query, the page is fully loaded based on the query data obtained from the full query. For example, the page framework can be displayed based on the configuration data, and then after the query data for the second field is obtained, the query data for the second field can be displayed in the table component, thus displaying the query results interface.

[0066] In an optional embodiment, step 013 includes: Step 0134: Determine the third field for cross-table joins between each target field; Step 0135: Batch query the query data of each target field and the associated third field.

[0067] It is understandable that when querying data for a target field, if the target field has a third field that is related across tables, a query request will be initiated again after the query data for each target field is obtained, in order to query the query data for the third field that is related across tables.

[0068] Therefore, to improve query efficiency and avoid multiple queries, query requests for the target field and the third field that is related to the target field across tables can be merged into a single query request, batch querying the data for each target field and the associated third field.

[0069] The interface display method of this application can configure the page for the newly added object and configure the interface display parameters of each interface component of the newly added object. There is no need to re-add page code in the system. The system can quickly display the various UI components corresponding to the newly added object by reading the configuration data of the newly added object, thus realizing the page display of the newly added object.

[0070] Furthermore, when users need to query data, a specific query strategy can be determined based on the query request. In scenarios where data needs to be displayed quickly, a progressive query strategy can be used to retrieve data, allowing the page to load data based on the highest priority first field obtained from the query, quickly displaying the first screen, improving page loading efficiency, and enabling users to quickly see the more important first field data, reducing user waiting time and improving user work efficiency. While the user is viewing the first field data, the system continues to query and load the second field data, achieving progressive data loading. This ensures both the efficiency of the first screen loading and the integrity of the data loading process.

[0071] Please see Figure 3 and Figure 4 In some embodiments, the interface component further includes a grouping component S3, and the method further includes: Step 014: Based on the pre-configured grouping function of the grouping component, group the query data of the target field to obtain grouping information; Step 015: Display the group component based on the page display parameters and group information of the group component.

[0072] The grouping component is a component that displays the grouping of query data based on preset grouping logic. The grouping function can be customized in advance based on the required grouping logic, such as grouping the query data by month or by task type, thereby obtaining different grouping information.

[0073] The grouping information includes the group name and the query data within each group.

[0074] When determining groupings, the preset grouping logic can be implemented based on pre-configured grouping functions. These functions process the query data for each target field matched by the query request, thereby obtaining the grouping information for each group. For example, when grouping by month, the timestamps of each query data are obtained, and then the timestamps in year-month-day format are converted into months to obtain the query data for each month, thus achieving grouping by month.

[0075] First, based on the page display parameters corresponding to the group component, display the group component on the page. Then, based on the group information of each group component, display the corresponding group controls for each group, thereby realizing the display of the group component.

[0076] Users can quickly view the query data corresponding to any group through the grouping component (e.g., by clicking on any group component, the query data of the selected group will be displayed in the table component), which makes it convenient for users to view and improves the efficiency of users' data query.

[0077] In one alternative embodiment, parent-child relationship analysis is performed on the fields within each group to adjust the hierarchical relationship of each group.

[0078] It's understandable that, besides grouping based on a preset grouping function, fields within the same group may also have hierarchical relationships. For example, some fields might be fields of a parent task, while others might be fields of a child task of that parent task, creating a hierarchical relationship between parent and child tasks. Therefore, by performing parent-child relationship analysis on the fields within a group—for example, grouping the fields by parent task to obtain the child tasks of each parent task—the hierarchical relationships of the grouping can be further optimized, making the grouping more accurate.

[0079] In one optional embodiment, the number of times the data processing function is called and the execution time of the object corresponding to each preset user group are obtained to generate a performance analysis report.

[0080] It's understandable that different preset user groups have different permissions and can access different amounts of query data. Therefore, different preset user groups require different data processing functions, which leads to varying degrees of complexity in the generated prompts.

[0081] To ensure system performance and prevent data processing functions from consuming excessive computing resources, the number of calls and execution time of data processing functions corresponding to objects in each preset user group can be monitored to generate a performance analysis report. The performance analysis report displays the number of calls and execution time of data processing functions corresponding to objects in each preset user group within a preset time period. By viewing the number of calls and execution time, users can optimize the performance of data processing functions with excessively high call counts and / or execution times (such as average execution time and total execution time) to improve system performance.

[0082] In one optional embodiment, a query index can be constructed for each group, which is used to locate the query data for each field in the group; upon receiving a data refresh request for the target group, the refresh data corresponding to the target group is queried based on the query index corresponding to the target group; and the query result interface is updated based on the refresh data.

[0083] Understandably, in order to ensure that the query data is always up-to-date and to improve the effectiveness of the query data, the system can refresh the query data periodically, and users can also refresh the query data manually.

[0084] The storage location of the target field data matched by the current query request is generally constant, but the content of the query data may change. Therefore, the storage location of each target field can be obtained during the first query to find the target field data matched by the current query request. After grouping, the storage location of the query data corresponding to each field within the group can be obtained (e.g., the query data is located in a row of a certain data table), thereby generating the query index corresponding to that group.

[0085] Upon receiving a data refresh request for any target group, the refresh data corresponding to that target group (i.e., the query data at the storage location corresponding to the query index) can be quickly located based on the query index. Finally, the query results interface can be updated based on the refresh data, thus refreshing the query data. In this way, by building query indexes for each group, the query efficiency for the query data corresponding to each group can be improved.

[0086] Please refer to it again. Figure 4 In some embodiments, the interface display method further includes: Step 016: Based on the pre-configured data processing function of the grouping component, process the query data of each group to generate prompt information corresponding to each group. The prompt information includes at least one of time prompt information, workflow prompt information and business logic prompt information. Step 017: Display the corresponding prompt information for each group in the area where each group is located in the group component.

[0087] It is understandable that, in order to help users quickly grasp the general information of each group, the query data of each group can be processed to obtain prompt information for each group.

[0088] For example, data processing functions for grouping components can be pre-configured, and then the query data for each group can be processed through these functions to generate corresponding prompts for each group.

[0089] The prompts include at least one of the following: time prompts, workflow prompts, and business logic prompts.

[0090] For example, the system pre-registers a series of data processing functions through decorators, such as time notification functions, workflow functions, and business logic functions.

[0091] The time-notification function processes the query data within a group to determine the deadline status of each task and obtain time-notification information, such as in progress, about to expire, or expired. Based on the deadline status of each task, the number of tasks under different deadline statuses can be determined, such as in progress (10), about to expire (12), or expired (2), thus realizing time-notification for each task within the group and helping users manage task deadlines.

[0092] In one alternative embodiment, different visual states can be used to display the query data corresponding to tasks with different deadlines within a group. For example, the background color of the row corresponding to the query data for tasks in progress, those about to expire, and those that have expired in the table component can be different.

[0093] For example, workflow functions can process the current workflow node in the query data within a group to determine the current workflow node of each task and provide workflow prompts. For instance, if the "Art Task" is found to be at the completion node, it should now proceed to the test node. At this point, the workflow status of the task can be determined as "pending workflow." Users can check if the number of tasks awaiting workflow is 0 to promptly advance the task, preventing it from getting stuck at a certain node and improving work efficiency.

[0094] Business logic functions can understand the business logic of each task, enabling each task to be executed normally, and promptly issue business logic prompts when it fails to execute normally.

[0095] If it discovers that "a task is important but the assigned personnel are not qualified enough", or "the task is already in progress before the scheduled deadline", it can identify operations that do not conform to business logic and issue business logic prompts to ensure that the task execution process conforms to business logic and that the task is executed correctly and effectively.

[0096] After receiving the prompts for each group, the prompts for each group can be displayed in the area where each group is located (i.e., the corresponding group control). Through the group component, users can quickly understand the overall situation of tasks or assets in each group without having to look at the specific query data in each group, thereby improving the user's work efficiency.

[0097] In one optional embodiment, a query index can be generated based on the query data associated with the prompt information. When a user wants to view the query data corresponding to the prompt information (e.g., to view the query data for "overdue" tasks, they can click the "overdue" prompt control), they can quickly retrieve the corresponding query data through the query index and display it in the table component, resulting in high query efficiency.

[0098] In one alternative embodiment, the prompt information corresponding to the current query request is cached, and the cache is cleared when the next query request is received.

[0099] It's understandable that the query data remains largely unchanged until a next query request is made. Therefore, the prompt information can be cached after receiving it, avoiding repeated data processing by the data processing function and reducing computational load. However, upon receiving the next query request, the query data will generally have changed, requiring further data processing by the data processing function to obtain the prompt information and ensure its accuracy.

[0100] In one optional embodiment, different prompts have different priorities. Since the display area for grouped information is limited, it may be impossible to display all prompts within a group. Therefore, when displaying prompts, higher-priority prompts can be prioritized to ensure that important prompts are shown to the user first.

[0101] In some embodiments, the data update frequency of each field in a preset database can be obtained; fields with a data update frequency lower than the preset frequency can be cached.

[0102] It is understandable that the update frequency of each field in the preset database can be statistically analyzed. For fields with low update frequency (i.e., data update frequency lower than the preset frequency), data can be cached. When performing data queries, the cached data can be quickly retrieved, which can improve query efficiency while ensuring data accuracy as much as possible.

[0103] In some embodiments, configuration data corresponding to the current object can be configured in response to a configuration operation. The interface components include a grouping component, a table component, and a filtering component. The interface display parameters include at least one of the following: the interface rendering parameters of each interface component, the grouping parameters of the grouping component, the data display volume of the table component, and the filtering conditions of the filtering component.

[0104] Users can customize the configuration data for the current object through configuration operations. Furthermore, for grouping components, table components, and filtering components, the interface rendering parameters of each UI component (such as the style and size of each UI component) can be configured separately.

[0105] In addition, the grouping parameters of the grouping component can be configured separately. The grouping parameters are used to characterize the grouping logic, such as grouping by month or by task type. Grouping functions can be generated through the grouping parameters. The data display volume of the table component (such as the number of rows and columns of the table component) can be configured separately. The filtering conditions of the filtering component can be configured separately (such as the filtering conditions corresponding to the filtering conditions of the drop-down filter component, such as the filtering conditions corresponding to the selection box filter component).

[0106] In some embodiments, the query data is converted into a preset format.

[0107] The preset format can be a pre-configured format for the data to be displayed in the table component, so as to ensure that each query data can be accurately displayed in the table component.

[0108] For example, after obtaining the query data, data validation can be performed to determine whether the query data conforms to the preset data output standard. This could involve forcibly checking whether all returned data includes dates formatted as "YYYY-MM-DD", whether empty values ​​are filled with their corresponding default values, and whether the values ​​are within the range of the corresponding fields.

[0109] To facilitate better implementation of the interface display method in the embodiments of this application, the embodiments of this application also provide an interface display method. Please refer to... Figure 5 , Figure 5 This is a schematic diagram of the interface display method provided in an embodiment of this application. The interface display method 200 can provide a graphical user interface through a terminal device. The graphical user interface includes at least a partial virtual scene and at least one virtual character. The interface display method 200 may include: The acquisition module 201 is used to acquire the configuration data matched by the current object. The configuration data defines the interface display parameters of each interface component. Module 202, in response to the query request, determines the query strategy, which includes progressive query and full query. Progressive query is used to retrieve query data for the second field after retrieving query data for the first field, with the first field having higher priority than the second field. Full query is used to retrieve query data for all fields that match the query request. The query module 203, based on the query strategy, queries the target field that matches the query request and displays the query results interface based on the configuration data and the query data.

[0110] Each module or unit in the above-described interface display method can be implemented entirely or partially through software, hardware, or a combination thereof. Each of these units can be embedded in or independent of the processor in the electronic device in hardware form, or stored in the memory of the electronic device in software form, so that the processor can call and execute the operations corresponding to each of these units.

[0111] The interface display method 200 can be integrated into a terminal or server that has storage and a processor and thus computing power, or the interface display method 200 can be the terminal or server.

[0112] Optionally, this application also provides an electronic device, including a memory and a processor, wherein the memory stores a computer program, and the processor executes the computer program to implement the steps in the above-described method embodiments.

[0113] Figure 6 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application. The electronic device may be a terminal or a server. Figure 6 As shown, the electronic device 300 includes a processor 301 with one or more processing cores, a memory 302 with one or more computer-readable storage media, and a computer program stored in the memory 302 and executable on the processor. The processor 301 and the memory 302 are electrically connected. Those skilled in the art will understand that the electronic device structure shown in the figures does not constitute a limitation on the electronic device, and may include more or fewer components than shown, or combine certain components, or have different component arrangements.

[0114] The processor 301 is the control center of the electronic device 300. It connects various parts of the electronic device 300 through various interfaces and lines. By running or loading software programs and / or modules stored in the memory 302, and calling data stored in the memory 302, it executes various functions of the electronic device 300 and processes data, thereby performing overall processing of the electronic device 300.

[0115] Optional, such as Figure 6 As shown, the electronic device 300 also includes: a display screen 303, a radio frequency circuit 304, an audio circuit 305, an input unit 306, and a power supply 307. The processor 301 is electrically connected to the display screen 303, the radio frequency circuit 304, the audio circuit 305, the input unit 306, and the power supply 307. Those skilled in the art will understand that... Figure 6 The electronic device structure shown does not constitute a limitation on the electronic device and may include more or fewer components than shown, or combine certain components, or have different component arrangements.

[0116] The display screen 303 can be used to display a graphical user interface (GUI) and receive operation commands generated by the user interacting with the GUI. The display screen 303 may include a display panel and a touch panel. The display panel can be used to display information input by the user or information provided to the user, as well as various graphical user interfaces of the electronic device. These graphical user interfaces can be composed of graphics, text, icons, video, and any combination thereof. The touch panel can be used to collect touch operations performed by the user on or near it (such as operations performed by the user using a finger, stylus, or any suitable object or accessory on or near the touch panel), generate corresponding operation commands, and execute the corresponding program. Optionally, the touch panel may include a touch detection device and a touch controller. The touch detection device detects the user's touch location and the signal generated by the touch operation, and transmits the signal to the touch controller. The touch controller receives touch information from the touch detection device, converts it into touch point coordinates, sends it to the processor 301, and can receive and execute commands from the processor 301. The touch panel can cover the display panel. When the touch panel detects a touch operation on or near it, it transmits the information to the processor 301 to determine the type of touch event. Subsequently, the processor 301 provides corresponding visual output on the display panel according to the type of touch event. In this embodiment, the touch panel and the display panel can be integrated into the display screen 303 to achieve input and output functions. However, in some embodiments, the touch panel and the display screen 303 can be implemented as two independent components to achieve input and output functions. That is, the display screen 303 can also be used as part of the input unit 306 to achieve input functions.

[0117] The radio frequency circuit 304 can be used to transmit and receive radio frequency signals to establish wireless communication with network devices or other electronic devices, and to transmit and receive signals with network devices or other electronic devices.

[0118] Audio circuitry 305 can be used to provide an audio interface between a user and an electronic device via a speaker and a microphone. Audio circuitry 305 converts received audio data into electrical signals, transmits them to the speaker, and the speaker converts them into sound signals for output. Conversely, the microphone converts collected sound signals into electrical signals, which are then received by audio circuitry 305, converted back into audio data, and then processed by processor 301 before being transmitted via radio frequency circuitry 304 to, for example, another electronic device, or output to memory 302 for further processing. Audio circuitry 305 may also include an earphone jack to facilitate communication between peripheral headphones and electronic devices.

[0119] The input unit 306 can be used to receive input numbers, characters, or object feature information (such as fingerprints, irises, facial information, etc.), and to generate keyboard, mouse, joystick, optical, or trackball signal inputs related to user settings and function control.

[0120] Power supply 307 is used to supply power to various components of electronic device 300. Optionally, power supply 307 can be logically connected to processor 301 through a power management system, thereby enabling functions such as charging, discharging, and power consumption management through the power management system. Power supply 307 may also include one or more DC or AC power supplies, recharging systems, power fault detection circuits, power converters or inverters, power status indicators, and other arbitrary components.

[0121] although Figure 6 As not shown in the diagram, the electronic device 300 may also include a camera, sensor, wireless fidelity module, Bluetooth module, etc., which will not be described in detail here.

[0122] This application also provides a computer-readable storage medium for storing a computer program. This computer-readable storage medium can be applied to an electronic device, and the computer program causes the electronic device to execute the corresponding processes in the interface display method described in the embodiments of this application; for the sake of brevity, further details are omitted here.

[0123] This application also provides a computer program product including computer instructions stored in a computer-readable storage medium. The processor of an electronic device reads the computer instructions from the computer-readable storage medium and executes the computer instructions, causing the electronic device to perform the corresponding flow in the interface display method of the embodiments of this application. For simplicity, further details are omitted here.

[0124] It should be understood that the processor in this application may be an integrated circuit chip with signal processing capabilities. In implementation, the steps of the above method embodiments can be completed by integrated logic circuits in the processor's hardware or by instructions in software form. The processor described above can be a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, or discrete hardware components. It can implement or execute the methods, steps, and logic block diagrams disclosed in the embodiments of this application. The general-purpose processor can be a microprocessor or any conventional processor. The steps of the methods disclosed in the embodiments of this application can be directly embodied in the execution of a hardware decoding processor, or executed by a combination of hardware and software modules in the decoding processor. The software modules can be located in random access memory, flash memory, read-only memory, programmable read-only memory, electrically erasable programmable memory, registers, or other mature storage media in the art. This storage medium is located in memory, and the processor reads information from the memory and, in conjunction with its hardware, completes the steps of the above method.

[0125] It is understood that the memory in the embodiments of this application can be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory. The non-volatile memory can be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. The 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), Dynamic Random Access Memory (DRAM), Synchronous DRAM (SDRAM), Double Data Rate SDRAM (DDR SDRAM), Enhanced Synchronous DRAM (ESDRAM), Synchlink DRAM (SLDRAM), and Direct Rambus RAM (DR RAM). It should be noted that the memory used in the systems and methods described herein is intended to include, but is not limited to, these and any other suitable types of memory.

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

[0127] Those skilled in the art will understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.

[0128] In the embodiments of this application, the terms "module" or "unit" refer to a computer program or part of a computer program that has a predetermined function and works with other related parts to achieve a predetermined goal, and can be implemented wholly or partially using software, hardware (such as processing circuitry or memory), or a combination thereof. Similarly, a processor (or multiple processors or memory) can be used to implement one or more modules or units. Furthermore, each module or unit can be part of an overall module or unit that includes the functionality of that module or unit.

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

[0130] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0131] In addition, the functional units in this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.

[0132] If a function is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or a portion of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause an electronic device (which may be a personal computer or a server) to execute all or part of the steps of the methods in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, ROM, RAM, magnetic disks, or optical disks.

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

Claims

1. A method for displaying an interface, characterized in that, include: Get the configuration data that matches the current object. The configuration data defines the interface display parameters of each interface component. In response to a query request, a query strategy is determined. The query strategy includes progressive query and full query. The progressive query is used to retrieve query data for the second field after retrieving query data for the first field, with the first field having a higher priority than the second field. The full query is used to retrieve query data for all fields that match the query request. Based on the query strategy, query data matching the target field of the query request is retrieved, and the query results interface is displayed based on the configuration data and the query data.

2. The interface display method according to claim 1, characterized in that, The step of responding to a query request and determining a query strategy includes: If the target field includes at least the first field, the query strategy is determined to be the progressive query. If the target field only includes the second field, the query strategy is determined to be a full query.

3. The interface display method according to claim 1 or 2, characterized in that, The interface components include a table component, which is used to display the query data. The step of determining a query strategy in response to a query request includes: The query strategy is determined based on the amount of data to be displayed as configured in the table component.

4. The interface display method according to any one of claims 1-3, characterized in that, The process of querying the target field based on the query strategy and displaying the query results interface based on the configuration data and the query data includes: When the query strategy is the progressive query, the query data of the first field is obtained, and the query results interface is displayed based on the configuration data and the query data of the first field. After obtaining the query data for the first field, the query data for the second field is obtained, and the query results interface is updated based on the query data for the second field.

5. The interface display method according to any one of claims 1-3, characterized in that, The process of querying the target field based on the query strategy and displaying the query results interface based on the configuration data and the query data includes: When the query strategy is full query, the query data of the second field is obtained, and the query results interface is displayed based on the configuration data and the query data of the second field.

6. The interface display method according to any one of claims 1-5, characterized in that, The query data that matches the target field of the query request includes: Determine the third field for cross-table joins of each of the target fields; Batch query the query data of each of the target fields and the associated third field.

7. The interface display method according to claim 1, characterized in that, The interface components also include grouping components, and the method further includes: Based on the pre-configured grouping function of the grouping component, the query data for each target field is grouped to obtain grouping information; The grouping component is displayed based on the page display parameters of the grouping component and the grouping information.

8. The interface display method according to claim 7, characterized in that, Also includes: Based on the data processing function pre-configured in the grouping component, the query data of each group is processed to generate prompt information corresponding to each group. The prompt information includes at least one of time prompt information, workflow prompt information, and business logic prompt information. The corresponding prompt information for each group is displayed in the area where each group is located in the grouping component.

9. The interface display method according to claim 8, characterized in that, Also includes: The prompt information corresponding to the current query request is cached, and the cache is cleared when the next query request is received.

10. The interface display method according to claim 8, characterized in that, The current object is an object in any preset user group, and the method further includes: The number of times the data processing function is called and the execution time are obtained for each of the preset user groups to generate a performance analysis report.

11. The interface display method according to claim 7, characterized in that, Also includes: Perform parent-child relationship analysis on the fields within each group to adjust the hierarchical relationship of each group.

12. The interface display method according to claim 7, characterized in that, Also includes: Construct query indexes corresponding to each of the groups, and use the query indexes to locate query data for each field in the group; Upon receiving a data refresh request for a target group, the refresh data corresponding to the target group is queried based on the query index corresponding to the target group; The query results interface is updated based on the refreshed data.

13. The interface display method according to claim 1, characterized in that, The query data that matches the target field of the query request includes: The query data is retrieved based on the query request and the target fields matched by the current object. The current object is an object in any preset user group, and different preset user groups are allowed to access different sets of fields.

14. The interface display method according to claim 1, characterized in that, The interface component includes a filtering component, the filtering component includes at least one filtering condition component, and the method further includes: The query request is generated in response to the editing operation of each of the filter condition components.

15. The interface display method according to claim 1, characterized in that, Also includes: In response to the configuration operation, the configuration data corresponding to the current object is configured. The interface components include a grouping component, a table component, and a filtering component. The interface display parameters include at least one of the following: the interface rendering parameters of each interface component, the grouping parameters of the grouping component, the data display volume of the table component, and the filtering conditions of the filtering component.

16. The interface display method according to claim 1, characterized in that, Also includes: Retrieve the data update frequency of each field in a preset database; Cache fields whose data update frequency is lower than a preset frequency.

17. An electronic device, characterized in that, The electronic device includes a processor and a memory, the memory storing a computer program, and the processor executing the interface display method according to any one of claims 1-16 by calling the computer program stored in the memory.

18. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program adapted for loading by a processor to perform the interface display method as described in any one of claims 1-16.

Images