Data display method and device, computer device and storage medium

Abstract

The application relates to a data display method and device, computer equipment and a storage medium. The method comprises the following steps: determining a card description entity, the card description entity is used for generating a display interface of target data; determining a data card corresponding to the target data, the data card is used for displaying the target data; determining a corresponding relationship between the card description and the data card; based on the corresponding relationship, the card description is applied to generate a display interface of the data card; and in the display interface, the data card is applied to display the target data. After the method is used, the corresponding interface is constructed through the card description entity, quick loading of the page is realized, sharing is facilitated, dynamic use of the data card level is realized, and users can view data by focusing on a certain data index.

Description

Technical Field

[0001] This application relates to the field of data display technology, and in particular to a data display method, apparatus, computer equipment, and storage medium. Background Technology

[0002] In mobile micro-applications, the amount of content that can be displayed is limited due to the limited view area of ​​the mobile screen. Every user wants to access valuable content quickly. However, the valuable content differs for different users, and the content that a single user focuses on varies at different stages. In current solutions, to address these issues, a large amount of content is placed on a single page for display.

[0003] However, the data cards on the current page are highly integrated and need to be laid out in a single metadata layer, resulting in inefficient display and an inability to share individual data cards. Sharing the entire page would also share useless data cards. Summary of the Invention

[0004] Therefore, it is necessary to provide a data display method, apparatus, computer equipment, and computer-readable storage medium that can decouple data cards and efficiently display data, addressing the aforementioned technical problems.

[0005] Firstly, this application provides a data display method. The method includes:

[0006] Determine the card description entity, which is used to generate the display interface of the target data;

[0007] Based on the target data, a data card is determined, and the data card is used to display the target data;

[0008] Determine the correspondence between the card description entity and the data card, and based on the correspondence, use the card description entity to generate the display interface of the data card;

[0009] The target data is displayed using the data cards on the display interface.

[0010] In one embodiment, determining the card description entity includes:

[0011] Obtain a card description class, wherein the card description class includes a method for scheduling the data card;

[0012] Instantiate the card description class to obtain an initial card description object;

[0013] Determine the descriptive data of the target data, wherein the descriptive data is used to describe the data structure, interface and / or business logic of the target data;

[0014] The initial card description object and the description data are combined to obtain a target card description object, which is used to generate a display interface for the target data.

[0015] In one embodiment, combining the initial card description object with the description data to obtain the target card description object includes:

[0016] Obtain the identifier of the target card description object, determine the source page corresponding to the initial card description object, and the source page is used to generate the display interface;

[0017] The target card description object is combined with the source interface to obtain the target card description object.

[0018] In one embodiment, determining the data card based on the target data includes:

[0019] Obtain the base class of the data card, which includes preset display logic;

[0020] Based on the display logic corresponding to the base data card class and the target data, a subclass of data card is generated.

[0021] Obtain the target data, and instantiate the data card subclass based on the target data to obtain the data card.

[0022] In one embodiment, the application of the card description to generate the display interface of the data card includes:

[0023] Determine the lightweight application page, which includes the card description entity and the data card;

[0024] In response to a sharing command, a target card description entity is determined from the card description entity in the lightweight application page, and the display interface is generated using the target card description entity. The display interface carries the target data card corresponding to the target card description entity.

[0025] In one embodiment, there are multiple card description entities and multiple data cards, and the application of the data cards to display the target data includes:

[0026] In the display interface, each card description entity is applied to generate layout information corresponding to each card description entity.

[0027] Based on the layout information, the data cards corresponding to each card description entity are loaded respectively, and the target data is loaded by each data card to obtain the filled data card. The target data is then displayed by the filled data card.

[0028] In one embodiment, there are multiple card description entities and multiple data cards, and the application of the data cards to display the target data includes:

[0029] In the display interface, each card description entity is applied to generate layout information corresponding to each card description entity.

[0030] Based on the layout information, the data cards corresponding to each card description entity are loaded respectively, and the target data is loaded by each data card to obtain the filled data card. The target data is then displayed by the filled data card.

[0031] Secondly, this application also provides a data display device, characterized in that the device comprises:

[0032] The card description acquisition module is used to determine the card description entity, which is used to generate the display interface of the target data;

[0033] A data card acquisition module is used to determine a data card based on the target data, and the data card is used to display the target data.

[0034] The display interface generation module is used to determine the correspondence between the card description entity and the data card, and based on the correspondence, to generate the display interface of the data card using the card description entity;

[0035] The data display module is used to display the target data using the data cards on the display interface.

[0036] Thirdly, this application also provides a computer device. The computer device includes a memory and a processor, the memory storing a computer program, and the processor executing the computer program to perform the following steps:

[0037] Determine the card description entity, which is used to generate the display interface of the target data;

[0038] Based on the target data, a data card is determined, and the data card is used to display the target data;

[0039] Determine the correspondence between the card description entity and the data card, and based on the correspondence, use the card description entity to generate the display interface of the data card;

[0040] The target data is displayed using the data cards on the display interface.

[0041] Fourthly, this application also provides a computer-readable storage medium. The computer-readable storage medium stores a computer program thereon, which, when executed by a processor, performs the following steps:

[0042] Determine the card description entity, which is used to generate the display interface of the target data;

[0043] Based on the target data, a data card is determined, and the data card is used to display the target data;

[0044] Determine the correspondence between the card description entity and the data card, and based on the correspondence, use the card description entity to generate the display interface of the data card;

[0045] The target data is displayed using the data cards on the display interface.

[0046] Fifthly, this application also provides a computer program product. The computer program product includes a computer program that, when executed by a processor, performs the following steps:

[0047] Determine the card description entity, which is used to generate the display interface of the target data;

[0048] Based on the target data, a data card is determined, and the data card is used to display the target data;

[0049] Determine the correspondence between the card description entity and the data card, and based on the correspondence, use the card description entity to generate the display interface of the data card;

[0050] The target data is displayed using the data cards on the display interface.

[0051] The aforementioned data display methods, devices, computer equipment, storage media, and computer program products, by decoupling data cards from the page for data loading, further reduce the coupling between data cards and the page using card description entities. By constructing the corresponding interface using card description entities, rapid page loading is achieved, facilitating sharing, enabling dynamic use of the data card hierarchy, and allowing users to focus on a specific data indicator. Attached Figure Description

[0052] Figure 1 This is an application environment diagram of the data display method in one embodiment;

[0053] Figure 2 This is a flowchart illustrating a data display method in one embodiment;

[0054] Figure 3 This is a flowchart illustrating the steps for obtaining a card description entity in one embodiment;

[0055] Figure 4 This is a schematic diagram of the process for generating a target card description object in another embodiment;

[0056] Figure 5 This is a schematic diagram illustrating the relationship between the card description template and the card entity in another embodiment;

[0057] Figure 6 This is a schematic diagram of the data card acquisition process in another embodiment;

[0058] Figure 7 This is a schematic diagram illustrating the relationship between the data card base class and the data card subclasses in another embodiment;

[0059] Figure 8 This is a flowchart illustrating the process of generating the data display interface in another embodiment;

[0060] Figure 9 This is a flowchart illustrating the data display process in another embodiment;

[0061] Figure 10 This is a flowchart illustrating a specific application scenario in another embodiment;

[0062] Figure 11 This is a schematic diagram of a lightweight application page in another embodiment;

[0063] Figure 12 This is a schematic diagram of the landing page in another embodiment;

[0064] Figure 13 This is a structural block diagram of a data display device in one embodiment;

[0065] Figure 14 This is an internal structural diagram of a computer device in one embodiment. Detailed Implementation

[0066] To make the objectives, technical solutions, and advantages of this application clearer, the following detailed description is provided in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative and not intended to limit the scope of this application.

[0067] The data display method provided in this application embodiment can be applied to, for example, Figure 1In the application environment shown, terminal 102 communicates with server 104 via a network. A data storage system can store the data that server 104 needs to process. The data storage system can be integrated onto server 104 or placed on a cloud or other network server. Terminal 102 obtains a card description entity, which is used to generate a display interface for the target data; obtains the data card corresponding to the target data, which is used to display the target data; obtains the correspondence between the card description entity and the data card, and based on the correspondence, uses the card description entity to generate a display interface for the data card; in the display interface, uses the data card to display the target data. Terminal 102 can be, but is not limited to, various personal computers, laptops, smartphones, tablets, IoT devices, and portable wearable devices. IoT devices can be smart speakers, smart TVs, smart air conditioners, smart in-vehicle devices, etc. Portable wearable devices can be smartwatches, smart bracelets, head-mounted devices, etc. Server 104 can be implemented using a standalone server or a server cluster composed of multiple servers.

[0068] In one embodiment, such as Figure 2 As shown, a data visualization method is provided, which can be applied to... Figure 1 Taking terminal 102 as an example, the explanation includes the following steps:

[0069] Step 202: Determine the card description entity, which is used to generate the display interface for the target data.

[0070] Card description entities, also known as data card metadata, are used to decouple a complete webpage into multiple separable data entities. Each separable data entity is used to construct the display interface to which the data card is attached, reducing development difficulty and enabling multi-party development. In an optional implementation, the card description entity can be generated from a card description template, generated based on a card description class, or obtained from a database according to an identifier. Target data is the data corresponding to the data to be displayed; it can be specific business data or business logic that includes the business data.

[0071] In an optional implementation, before obtaining the card description entity, a step of generating the card description entity is included. This step may involve generating a specific card style according to a card description template. Alternatively, the step of generating the card description entity may involve constructing methods, events, functions, parameters, and other data of the card description entity based on a card description class.

[0072] In one optional implementation, a card description entity is embedded within another card description entity. In another optional implementation, a card description entity can be obtained directly from a card description entity database; alternatively, corresponding personalized data can be obtained based on the card description entity identifier, and the personalized data can be combined with a card description template to define a card description entity; alternatively, corresponding personalized data can be obtained based on the card description entity identifier, and a card description entity can be generated based on the personalized data and calculations performed according to the card description class.

[0073] Step 204: Determine data cards based on the target data. Data cards are used to display the target data.

[0074] Data cards correspond to target data to be displayed. Data cards are loaded in parallel; when a page has multiple data cards, loading speed is faster compared to a single-page implementation, resulting in a better user experience. Data cards can correspond to business units and can display specific business metrics or types of business data through text, images, or videos. For example, data cards can display service organization distribution, the number of tasks in the task pool, the number of tasks pending processing, task inventory trends, quality inspection failure rates, and any other quantifiable or categorized data.

[0075] In an optional embodiment, a data card associated with an entity that does not have a card description uses the entire data page of the full page as its interface. It can be dynamically placed on the homepage, topic page, sharing page, alert notification page, etc., of an application or mini-application. The data card is directly reusable, requiring no additional development, with only some differences in status and permissions. The homepage needs to be laid out in metadata, which can only be loaded in a single request, resulting in slow loading. Displaying the same metric on different pages requires repeated implementation, and sharing a single data metric is not possible; sharing the entire page would also share useless data.

[0076] Step 206: Determine the correspondence between card description entities and data cards. Based on the correspondence, use card description entities to generate the display interface of data cards.

[0077] In one alternative implementation, the correspondence between card description entities and data cards can be obtained based on a mapping table, dynamically obtained by calculating the matching degree using a certain algorithm, or constructed based on data dependency relationships.

[0078] In one optional implementation, during the process of generating a data card display interface using card description entities, the card description entities, i.e., card metadata, are used to define the view interface; while the data cards corresponding to the card description entities, i.e., card plugins, are used to perform calculations and statistics on specific data. By binding data to the interface through plugins composed of card description entities, a separable display interface is formed. Because the display interface has been decoupled from the specific page, it can be used in various mini-programs and other lightweight applications.

[0079] The display interface, embedded in lightweight applications or as a landing page compatible with various programs, can be a view interface, user interface, or user interaction interface. Through the display interface, users can provide input data and schedule cards describing entities and data cards.

[0080] Therefore, based on the correspondence, the application card description generates a data card display interface, which can be embedded in applications such as lightweight applications to facilitate development, reorganization, and generation; it can also be a landing page to facilitate cross-platform scheduling.

[0081] Step 208: On the display interface, use data cards to display the target data.

[0082] In an optional embodiment, when displaying target data using application data cards, it can be displayed on various interfaces. A single request can correspond to one or more card description entities, thereby simultaneously constructing one or more interfaces with fast loading speed. The calculation process for the same indicator on different pages does not need to be repeated, and the sharing of individual data indicators can also be achieved, sharing key data and avoiding the sharing of useless data. The display interface can be a group chat or other online interactive platform, an instant messaging program, or a multi-terminal platform for communication and collaboration, etc.

[0083] In the above data display method, based on data loading by decoupling data cards from the page, the coupling relationship between data cards and the page is further reduced by using card description entities. The card description entities generate the display interface of the target data through the data structure, business data and / or logical functions of the target data. The corresponding interface is constructed through the card description entities, which enables fast loading and dynamic use of data card hierarchy. Users can freely split data cards and share the split data cards.

[0084] For the same reason, the interface is constructed by describing entities using cards, which also enables rapid expansion and development of the page. In lightweight applications such as WeChat Mini Programs or ordinary applications, there is no need to directly control all the data on the entire page. Data cards can be developed, scheduled, used, and shared conveniently.

[0085] In one embodiment, such as Figure 3 As shown, the card description entity is determined to include:

[0086] Step 302: Obtain the card description class, which includes methods for scheduling data cards.

[0087] Card description classes are generated based on a preset data set and can also be called metadata templates or card description modules. They can be card description templates, which include a card description template identifier field and a page type field. The card description template identifier field is used to identify the card description template, and the page type field is used to represent the page type corresponding to the card description template.

[0088] Step 304: Instantiate the card description class to obtain the initial card description object.

[0089] Step 306: Determine the descriptive data of the target data. The descriptive data is used to describe the data structure, interface and / or business logic of the target data.

[0090] Step 308: Combine the initial card description object and the description data to obtain the target card description object. The target card description object is used to generate the display interface of the target data.

[0091] A target card description object is an entity that can be used independently or reused. It can be used to construct the interface corresponding to target data, to construct part of the interface of a page, or to construct a page on its own. The display interface generated by the target card description object is equivalent to a separable data structure, which can be based on and separated from lightweight applications to extract the data cards to be displayed. Optionally, the display interface generated by the target card description object may include the layout information of the corresponding data cards, so that one or more corresponding data cards are displayed on the display interface.

[0092] In an optional implementation, combining the initial card description object and the description data is the process of adding data to the initial card description object. By combining the initial card description object and the description data, personalized data of the target card description object is added to the initial card description object to obtain the target card description object, which is used to construct the display interface of the target data.

[0093] In this embodiment, by defining a card description class, the data card scheduling method can be reused multiple times, which can greatly improve development efficiency. By combining the initial card description object and the description data, the interface of the target data can be easily configured, which facilitates the efficient generation of the display interface corresponding to the target data. This is beneficial for custom sorting on the homepage and for reuse of theme pages.

[0094] In one embodiment, such as Figure 4 As shown, by combining the initial card description object and the description data, the target card description object is obtained, including:

[0095] Step 402: Obtain the target card description object identifier and determine the source interface corresponding to the initial card description object. The source interface is used to generate the display interface.

[0096] The source interface is equivalent to a path for obtaining card description classes, used to obtain data sharing functions, methods, or data, corresponding to the data type or data set of the data card scheduling. The display interface corresponding to the data card can be constructed through the source interface. In an optional embodiment, the initial card description object is provided with an initial card description identifier, which corresponds to the corresponding page type. The page type is a mobile form or similar, used to represent the data sharing functions, methods, or data.

[0097] Step 404: Combine the target card description object identifier with the source interface to obtain the target card description object.

[0098] In this embodiment, the source interface of the initial card description object can be used to generate landing pages or to obtain ready-made data templates. This further improves the speed of card description generation, makes it easier for users to customize, and lowers the development threshold.

[0099] In an optional embodiment, the relationship between the card description template and the card description entity is described, such as... Figure 5 As shown, the card description template is simply referred to as the card template, and the card description entity can be card A, card B, or card C;

[0100] The card template includes a page encoding field and a page type field. The page encoding field is used to represent the card template so as to construct the card description entity, while the page type field is used to characterize the interface or interface type of the card description template. The page type can be a mobile form.

[0101] Correspondingly, the card description entity includes a page encoding field, a page type field, and a source page field; among them, the page encoding field of the card description entity is filled with the identifier of the target card description object; the page type field is the interface or interface type of the card description template used by the card description entity; the source page is the page encoding field of the card template, used to determine the card template of the card description entity.

[0102] In an alternative embodiment, such as Figure 6 As shown, the steps for generating data cards are discussed. The steps for determining data cards based on the target data include:

[0103] Step 602: Obtain the data card base class, which includes preset display logic.

[0104] Step 604: Generate a data card subclass based on the display logic corresponding to the target data and the base class of the data card.

[0105] The base class of data cards is formed by abstracting the commonalities of data card entities. All information in this base class can be inherited by data card subclasses. New information can also be added to the data card subclasses to form new classes and build personalized subclasses. The information added to the data card subclasses can be one or more of the following: display logic, methods, functions, events, instructions, business logic, and logical functions.

[0106] Step 606: Obtain the target data, and instantiate the data card subclass based on the target data to obtain the data card.

[0107] In an alternative embodiment, such as Figure 7 The diagram illustrates the relationship between the base class and subclasses of data cards. The base class can be named "CardTemplatePlugin," while the subclasses can be named "CardAPlugin" (for Card A), "CardBPlugin" (for Card B), "CardCPlugin" (for Card C), etc.

[0108] Card template plugins can be generated based on a plugin base class, such as an abstract plugin for tables (AbstractMobFormPlugin). The abstract plugin for tables contains functions to control loading, so that the card template plugin and related plugins are loaded after certain events occur; for example, the relevant functions of the card template plugin can be loaded after creating new data (afterCreateNewData).

[0109] The card template plugin includes display-related attributes, functions, and events, such as functions for sharing, functions for determining whether the displayed card is editable, functions for hiding hints, and functions for adding mapping relationships between data to be displayed. Specifically, for example... Figure 7 In the code, "customPopoverMenu(String, String)" and "shareTo()" are functions related to sharing; "onlyRead()" is a function to ensure that the displayed card cannot be modified; "setNoDataView(String tip)" is a function to hide the tip; and "fillcardShareParam(Map<String,Object> ")" is a function used to add mapping relationships, where "true" indicates that this attribute is selected.

[0110] In the card plugin, based on the card template plugin, you can also choose to add some functions to form a data card subclass, so as to generate data cards.

[0111] In this embodiment, by defining a base class for data cards and determining the preset display logic, it is easy to construct specific data card subclasses without repeatedly constructing at least part of the code. By combining the preset display logic with the personalized display logic corresponding to the target data, data card subclasses are obtained, enabling multiple reuse of these subclasses, facilitating dynamic use, and allowing for the generation of multiple data cards. This further reduces the difficulty of data card development, increases the efficiency of data card development, and also facilitates the use of dynamic data cards.

[0112] In an alternative embodiment, such as Figure 8 As shown, the application card description generates a display interface for data cards, including:

[0113] Step 802: Determine the lightweight application page, which includes card description entities and data cards.

[0114] A lightweight application page is the page for a lightweight application, including mini-program pages on various platforms. Existing lightweight application web pages have a high degree of integration, making it impossible to separate the data cards. However, when a lightweight application web page is decoupled again, the data cards correspond to card description entities, thus achieving separation.

[0115] Step 804: In response to the sharing instruction, determine the target card description entity from the card description entity in the lightweight application page, apply the target card description entity to generate a display interface, and the display interface carries the target data card corresponding to the target card description entity.

[0116] In this embodiment, the target card description entity is selected through the card description entity under the mini-app page. The target card description is then used to generate a display interface for the target data, resulting in a data-separable display interface. This data-separable display interface is independent of the mini-app and can be used across terminals, platforms, systems, and programs, demonstrating the flexibility of data cards in development from the user perspective. Even at the user level, a webpage can be arbitrarily split and combined, and freely shared to achieve a customized effect.

[0117] In an alternative embodiment, such as Figure 9 As shown, there are multiple card description entities and data cards. The application of data cards to display target data includes:

[0118] Step 902: On the display interface, apply each card description entity to generate the layout information corresponding to each card description entity.

[0119] In one optional implementation, generating layout information corresponding to each card description entity using each card description entity involves setting one or more second data display interfaces within a first data display interface. In one embodiment, the first data display interface is equivalent to a mini-application page, while the second data display interface is equivalent to a portion of the mini-application page; in another embodiment, the first data display interface is equivalent to a portion of the page separated from the mini-application page, while the second data display interface is a separable interface within the first data display interface.

[0120] Step 904: Based on the layout information, load the data cards corresponding to each card description entity, apply the corresponding target data to each data card to obtain the populated data cards, and apply the populated data cards to display the target data.

[0121] In this embodiment, the layout of each data card is generated through card descriptions, which facilitates modular data scheduling for developers and further reduces the difficulty of data generation. More developers can be used for data development, improving development efficiency.

[0122] In one specific embodiment, the focus is not on describing the innovative aspects, but rather on describing it from the user's perspective, discussing and analyzing how this application is used in a specific application scenario.

[0123] Overall, such as Figure 10 As shown, Figure 10 This is a sequence diagram for card sharing. When a user clicks the additional menu in the upper right corner of a card within a mini-app, a share menu will appear if the mini-app is running on a specific program such as Yunzhijia. Clicking the share menu allows the user to select a contact or group, and then share. Once the sharer sees the sharing information, they click the share message body to enter the sharing landing page. The program dynamically loads relevant data cards based on the information attached to the share and displays them to the recipient. Specifically, the process of a user sharing a webpage includes:

[0124] (1) Share users access one or more of the homepage, topic page or sharing page of the mini application.

[0125] (2) Load the lightweight application data card. If the data card and the card description entity have a corresponding relationship, they can be separated.

[0126] (3) Obtain the runtime environment. The runtime environment refers to the runtime platform, including various data such as browsers.

[0127] (4) Based on the operating environment, determine whether the data card is a detachable lightweight application page.

[0128] (5) If there is a corresponding relationship between the data card and the card description entity, the data card is separable, and the data card is returned to the mini application sharing page.

[0129] (6) From the lightweight application sharing page, send the separate data card to the sharing user.

[0130] (7) Share the event when the user clicks the additional menu of the data card to perform the sharing operation; where the additional menu of the data card is generated by the card description entity and belongs to the display interface. Whether there is an additional menu or not, the sharing process of the data card can be realized.

[0131] (8) Generate a sharing page from the data card corresponding to the sharing operation event and share it to individuals or groups on various light application platforms or application platforms.

[0132] (9) After successful sharing, return a message of successful sharing to the sharing user and / or the user being shared with.

[0133] (10) Both the sharing user and the shared user can load the data card through the sharing page without having to access the lightweight application platform;

[0134] (11) After viewing the data card in the sharing page, you can return to the sharing page of the mini app from the data card;

[0135] (12) Then return from the sharing page to other drivers or applications on the user terminal.

[0136] In this specific application scenario, the homepage of the aforementioned lightweight application is as follows: Figure 11 As shown, there are two data cards, each with its own content; and in the sharing landing page, as... Figure 12 As shown, there is a data card that users can access directly without going through the platform page.

[0137] It should be understood that although the steps in the flowcharts of the embodiments described above are shown sequentially according to the arrows, these steps are not necessarily executed in the order indicated by the arrows. Unless explicitly stated herein, there is no strict order restriction on the execution of these steps, and they can be executed in other orders. Moreover, at least some steps in the flowcharts of the embodiments described above may include multiple steps or multiple stages. These steps or stages are not necessarily completed at the same time, but can be executed at different times. The execution order of these steps or stages is not necessarily sequential, but can be performed alternately or in turn with other steps or at least some of the steps or stages of other steps.

[0138] Based on the same inventive concept, this application also provides a data display device for implementing the data display method described above. The solution provided by this device is similar to the implementation scheme described in the above method; therefore, the specific limitations in one or more data display device embodiments provided below can be found in the limitations of the data display method described above, and will not be repeated here.

[0139] In one embodiment, such as Figure 13 As shown, a data display device is provided, including: a card description determination module, a data card determination module, a display interface generation module, and a data display module, wherein:

[0140] The card description determination module is used to determine the card description entity, which is used to generate the display interface of the target data;

[0141] A data card determination module is used to determine a data card based on the target data, wherein the data card is used to display the target data;

[0142] The display interface generation module is used to determine the correspondence between the card description entity and the data card, and based on the correspondence, to generate the display interface of the data card using the card description entity.

[0143] The data display module is used to display the target data using the data cards on the display interface.

[0144] In one embodiment, the card description determination module includes: a description class acquisition unit, a description data acquisition unit, and a second description object generation unit, wherein:

[0145] The description class acquisition unit is used to acquire the card description class, which includes methods for scheduling data cards;

[0146] The first description object generation unit is used to instantiate the card description class to obtain the initial card description object;

[0147] The description data determination unit is used to determine the description data of the target data. The description data is used to describe the data structure, interface and / or business logic of the target data.

[0148] The second description object generation unit is used to combine the initial card description object and description data to obtain the target card description object, which is used to generate the display interface of the target data.

[0149] In one embodiment, the second description object generation unit includes: a data acquisition subunit and a second description object construction subunit, wherein:

[0150] The data acquisition subunit is used to acquire the identifier of the target card description object and determine the source page corresponding to the initial card description object. The source page is used to generate the display interface.

[0151] The second description object construction subunit is used to combine the target card description object identifier with the source interface to obtain the target card description object.

[0152] In one embodiment, the data card determination module includes: a base class acquisition unit, a subclass definition unit, and a data generation unit, wherein:

[0153] The base class retrieval unit is used to retrieve the data card base class, which includes preset display logic.

[0154] The subclass definition unit is used to generate data card subclasses based on the display logic corresponding to the data card base class and the target data;

[0155] The data generation unit is used to acquire target data and instantiate the data card subclass based on the target data to obtain the data card.

[0156] In one embodiment, the display interface generation module includes: a lightweight application page acquisition unit and a sharing page generation unit, wherein:

[0157] The lightweight application page acquisition unit is used to determine the lightweight application page, which includes card description entities and data cards;

[0158] The sharing page generation unit is used to respond to the sharing command, determine the target card description entity from the card description entity in the lightweight application page, generate a display interface using the target card description entity, and carry the target data card corresponding to the target card description entity in the display interface.

[0159] In one embodiment, the display interface generation module further includes: a layout information acquisition unit and a data display unit, wherein:

[0160] The layout information acquisition unit is used to apply each card description entity to the display interface and generate layout information corresponding to each card description entity.

[0161] The data display unit is used to load the data cards corresponding to each card description entity based on the layout information, apply the target data to each data card to obtain the populated data card, and then apply the populated data card to display the target data.

[0162] Each module in the aforementioned data display device can be implemented entirely or partially through software, hardware, or a combination thereof. These modules can be embedded in the processor of a computer device in hardware form or independent of it, or stored in the memory of a computer device in software form, so that the processor can call and execute the operations corresponding to each module.

[0163] In one embodiment, a computer device is provided, which may be a terminal, and its internal structure diagram may be as follows: Figure 14 As shown, the computer device includes a processor, memory, communication interface, display screen, and input devices connected via a system bus. The processor provides computing and control capabilities. The memory includes non-volatile storage media and internal memory. The non-volatile storage media stores the operating system and computer programs. The internal memory provides an environment for the operation of the operating system and computer programs stored in the non-volatile storage media. The communication interface is used for wired or wireless communication with external terminals; wireless communication can be achieved through Wi-Fi, mobile cellular networks, NFC (Near Field Communication), or other technologies. When the computer program is executed by the processor, it implements a data display method. The display screen can be an LCD screen or an e-ink screen. The input devices can be a touch layer covering the display screen, buttons, a trackball, or a touchpad mounted on the computer device casing, or an external keyboard, touchpad, or mouse.

[0164] Those skilled in the art will understand that Figure 14 The structure shown is merely a block diagram of a portion of the structure related to the present application and does not constitute a limitation on the computer device to which the present application is applied. Specific computer devices may include more or fewer components than those shown in the figure, or combine certain components, or have different component arrangements.

[0165] In one embodiment, a computer device is also provided, 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 method embodiments.

[0166] In one embodiment, a computer-readable storage medium is provided having a computer program stored thereon that, when executed by a processor, implements the steps in the above method embodiments.

[0167] In one embodiment, a computer program product is provided, including a computer program that, when executed by a processor, implements the steps in the above method embodiments.

[0168] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, data stored, data displayed, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties.

[0169] Those skilled in the art will understand that all or part of the processes in the methods of the above embodiments can be implemented by a computer program instructing related hardware. The computer program can be stored in a non-volatile computer-readable storage medium, and when executed, it can include the processes of the embodiments of the above methods. Any references to memory, databases, or other media used in the embodiments provided in this application can include at least one of non-volatile and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetic random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory can include random access memory (RAM) or external cache memory, etc. By way of illustration and not limitation, RAM can take many forms, such as Static Random Access Memory (SRAM) or Dynamic Random Access Memory (DRAM). The databases involved in the embodiments provided in this application may include at least one type of relational database and non-relational database. Non-relational databases may include, but are not limited to, blockchain-based distributed databases. The processors involved in the embodiments provided in this application may be general-purpose processors, central processing units, graphics processing units, digital signal processors, programmable logic devices, quantum computing-based data processing logic devices, etc., and are not limited to these.

[0170] The technical features of the above embodiments can be combined in any way. For the sake of brevity, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

[0171] The embodiments described above are merely illustrative of several implementation methods of this application, and while the descriptions are specific and detailed, they should not be construed as limiting the scope of this patent application. It should be noted that those skilled in the art can make various modifications and improvements without departing from the concept of this application, and these all fall within the protection scope of this application. Therefore, the protection scope of this application should be determined by the appended claims.

Claims

1. A data display method, characterized in that, The method includes: Obtain a card description class, wherein the card description class includes a method for scheduling data cards; Instantiate the card description class to obtain an initial card description object; determine the target card description object identifier of the target data, wherein the target card description object identifier belongs to the description data, and the description data is used to describe the data structure, interface and / or business logic of the target data; Obtain the identifier of the target card description object, determine the source interface corresponding to the initial card description object, and the source interface is used to generate the display interface; the card description template represented by the source interface includes the initial card description object and the description data; the source interface includes a path for obtaining the card description class, and the source interface corresponds to the data type or data set of the data card scheduling. The target card description object is combined with the source interface to obtain the target card description object. The target card description object is used to generate the display interface of the target data. The target card description object belongs to the card description entity. The card description entity is used to decouple the webpage into multiple separable data entities. Each data entity is used to generate the display interface of the target data, and the data card is attached to the display interface. Based on the target data, a data card is determined, and the data card is used to display the target data; Determine the correspondence between the card description entity and the data card, and based on the correspondence, use the card description entity to generate the display interface of the data card; The target data is displayed using the data cards on the display interface.

2. The method according to claim 1, characterized in that, The card description entity generates a display interface for the target data through the data structure, business data, and / or logical functions of the target data, thereby reducing the coupling between the data card and the page.

3. The method according to claim 1, characterized in that, The initial card description object is provided with an initial card description identifier, which corresponds to a corresponding page type. The page type is used to characterize a data sharing function, method, or data.

4. The method according to claim 1, characterized in that, The data card determined based on the target data includes: Obtain the base class of the data card, which includes preset display logic; Based on the display logic corresponding to the base data card class and the target data, a subclass of data card is generated. Obtain the target data, and instantiate the data card subclass based on the target data to obtain the data card.

5. The method according to claim 1, characterized in that, The application of the card description entity to generate the display interface of the data card includes: Determine the lightweight application page, which includes the card description entity and the data card; In response to a sharing command, a target card description entity is determined from the card description entity in the lightweight application page, and the display interface is generated using the target card description entity. The display interface carries the target data card corresponding to the target card description entity.

6. The method according to claim 1, characterized in that, Both the card description entity and the data card are multiple, and the application of the data card to display the target data includes: In the display interface, each card description entity is applied to generate layout information corresponding to each card description entity. Based on the layout information, the data cards corresponding to each card description entity are loaded respectively, and the target data is loaded by each data card to obtain the filled data card. The target data is then displayed by the filled data card.

7. A data display device, characterized in that, The device includes: The card description acquisition module is used to acquire a card description class, which includes a method for scheduling data cards; instantiate the card description class to obtain an initial card description object; determine the target card description object identifier of the target data, which belongs to the description data and is used to describe the data structure, interface and / or business logic of the target data. The card description acquisition module is used to acquire the identifier of the target card description object and determine the source interface corresponding to the initial card description object. The source interface is used to generate the display interface. The card description template represented by the source interface includes the initial card description object and the description data. The source interface includes a path for acquiring the card description class. The source interface corresponds to the data type or data set of the data card scheduling. The card description acquisition module is used to combine the target card description object identifier with the source interface to obtain a target card description object. The target card description object is used to generate a display interface for the target data. The target card description object belongs to a card description entity. The card description entity is used to decouple the webpage into multiple separable data entities. Each data entity is used to generate a display interface for the target data, and the data card is attached to the display interface. A data card acquisition module is used to determine a data card based on the target data, and the data card is used to display the target data. The display interface generation module is used to determine the correspondence between the card description entity and the data card, and based on the correspondence, to generate the display interface of the data card using the card description entity. The data display module is used to display the target data using the data cards on the display interface.

8. A computer device comprising a memory and a processor, wherein the memory stores a computer program, characterized in that, When the processor executes the computer program, it implements the steps of the method according to any one of claims 1 to 6.

9. 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 steps of the method according to any one of claims 1 to 6.

10. A computer program product, comprising a computer program, characterized in that, When the computer program is executed by a processor, it implements the steps of the method according to any one of claims 1 to 6.

Images