CN114201464A

CN114201464A - Data display method and device, computer equipment and storage medium

Info

Publication number: CN114201464A
Application number: CN202111519325.7A
Authority: CN
Inventors: 胡晓思; 胡磊; 林跃龙; 杨柳
Original assignee: Kingdee Software China Co Ltd
Current assignee: Kingdee Software China Co Ltd
Priority date: 2021-12-13
Filing date: 2021-12-13
Publication date: 2022-03-18

Abstract

The application relates to a data display method, a data display device, computer equipment and a storage medium. The method comprises the following steps: determining a card description entity, wherein the card description entity is used for generating a display interface of target data; determining a data card corresponding to the target data, wherein the data card is used for displaying the target data; determining the corresponding relation between the card description and the data card, and generating a display interface of the data card by applying the card description based on the corresponding relation; and displaying the target data by using the data card on a display interface. By adopting the method, the corresponding interface is constructed through the card description entity, so that the rapid loading of the page is realized, the sharing is convenient, the dynamic use of the data card level is realized, and a user can look at a certain data index to check the data.

Description

Data display method and device, computer equipment and storage medium

Technical Field

The present application relates to the field of data display technologies, and in particular, to a data display method and apparatus, a computer device, and a storage medium.

Background

In mobile light applications, the content that can be presented is limited due to the limited cell phone interface view area. Each user desires to be able to obtain valuable content more quickly. But the valuable content is different for different users and the content that the same user is interested in at different stages is also different. In the practice of the prior art, in order to solve the above problems, a large amount of contents are put on a certain page for displaying as much as possible.

However, data cards in the current page are highly integrated, need to be laid out in metadata, are low in display efficiency, cannot be shared by single data cards, and can be shared by the whole page without data cards.

Disclosure of Invention

In view of the foregoing, there is a need to provide a data display method, device, computer device and computer readable storage medium capable of decoupling a data card and efficiently displaying data.

In a first aspect, the present application provides a data presentation method. The method comprises the following steps:

determining a card description entity, wherein the card description entity is used for generating a display interface of the target data;

determining a data card based on the target data, wherein the data card is used for displaying the target data;

determining the corresponding relation between the card description entity and the data card, and based on the corresponding relation, applying the card description entity to generate a display interface of the data card;

and displaying the target data by applying the data card on the display interface.

In one embodiment, the determining the card description entity includes:

obtaining a card description class, wherein the card description class comprises a method for scheduling the data card;

instantiating the card description class to obtain an initial card description object;

determining description data of the target data, wherein the description data is used for describing a data structure, an interface and/or business logic of the target data;

and combining the initial card description object and the description data to obtain a target card description object, wherein the target card description object is used for generating a display interface of the target data.

In one embodiment, the combining the initial card description object and the description data to obtain the target card description object includes:

acquiring the target card description object identifier, and determining a source page corresponding to the initial card description object, wherein the source page is used for generating the display interface;

and combining the target card description object identification with the source interface to obtain the target card description object.

In one embodiment, the determining the data card based on the target data comprises:

acquiring a data card base class, wherein the data card base class comprises preset display logic;

generating a data card subclass based on the display logic corresponding to the data card base class and the target data;

and acquiring the target data, and instantiating the data card subclass based on the target data to obtain the data card.

In one embodiment, the applying the card description to generate the display interface of the data card includes:

determining a light application page, wherein the light application page comprises the card description entity and the data card;

responding to a sharing instruction, determining a target card description entity from a card description entity in a light application page, and applying the target card description entity to generate the display interface, wherein the display interface carries a target data card corresponding to the target card description entity.

In one embodiment, the card description entity and the data card are both multiple, and the displaying the target data by applying the data card includes:

respectively applying each card description entity on the display interface to generate layout information corresponding to each card description entity;

and respectively loading the data cards corresponding to the card description entities based on the layout information, applying the data cards to load corresponding target data to obtain the filled data cards, and applying the filled data cards to display the target data.

In a second aspect, the present application further provides a data display apparatus, comprising:

the card description acquisition module is used for determining a card description entity, and the card description entity is used for generating a display interface of the target data;

the data card acquisition module is used for determining a data card based on the target data, and the data card is used for displaying the target data;

the display interface generating module is used for determining the corresponding relation between the card description entity and the data card and applying the card description entity to generate a display interface of the data card based on the corresponding relation; (ii) a

And the data display module is used for displaying the target data by applying the data card on the display interface.

In a third aspect, the present application also provides a computer device. The computer device comprises a memory storing a computer program and a processor implementing the following steps when executing the computer program:

In a fourth aspect, the present application further provides a computer-readable storage medium. The computer-readable storage medium having stored thereon a computer program which, when executed by a processor, performs the steps of:

In a fifth aspect, the present application further provides a computer program product. The computer program product comprising a computer program which when executed by a processor performs the steps of:

According to the data display method, the data display device, the computer equipment, the storage medium and the computer program product, the card description entity is used for further reducing the coupling relation between the data card and the page on the basis of decoupling the data card from the page for data loading. Corresponding interfaces are constructed through the card description entities, rapid page loading is achieved, sharing is convenient, dynamic use of data card levels is achieved, and a user can look at a certain data index.

Drawings

FIG. 1 is a diagram of an application environment of a data presentation method according to an embodiment;

FIG. 2 is a flow diagram illustrating a method for displaying data according to one embodiment;

FIG. 3 is a flowchart illustrating the steps of obtaining card description entities in one embodiment;

FIG. 4 is a schematic diagram of a process for generating a target card description object according to another embodiment;

FIG. 5 is a diagram illustrating the relationship between a card description template and a card entity in another embodiment;

FIG. 6 is a schematic flow chart of data card acquisition in another embodiment;

FIG. 7 is a diagram illustrating the relationship between the data card base class and the data card subclass in another embodiment;

FIG. 8 is a schematic diagram illustrating a flowchart of the generation of a data presentation interface in accordance with an alternative embodiment;

FIG. 9 is a flow chart illustrating data presentation according to another embodiment;

FIG. 10 is a schematic flowchart of another embodiment in a specific application scenario;

FIG. 11 is a diagram of a light application page in another embodiment;

FIG. 12 is a diagram of a landing page in another embodiment;

FIG. 13 is a block diagram of the structure of a data presentation device in one embodiment;

FIG. 14 is a diagram illustrating an internal structure of a computer device according to an embodiment.

Detailed Description

In order to make the objects, technical solutions and advantages of the present application more apparent, the present application is described in further detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the present application and are not intended to limit the present application.

The data display method provided by the embodiment of the application can be applied to the application environment shown in fig. 1. Wherein the terminal 102 communicates with the server 104 via a network. The data storage system may store data that the server 104 needs to process. The data storage system may be integrated on the server 104, or may be located on the cloud or other network server. The terminal 102 acquires a card description entity, and the card description entity is used for generating a display interface of the target data; acquiring a data card corresponding to the target data, wherein the data card is used for displaying the target data; acquiring a corresponding relation between a card description entity and a data card, and generating a display interface of the data card by applying the card description entity based on the corresponding relation; and displaying the target data by using the data card on a display interface. The terminal 102 may be, but not limited to, various personal computers, notebook computers, smart phones, tablet computers, internet of things devices and portable wearable devices, and the internet of things devices may be smart speakers, smart televisions, smart air conditioners, smart car-mounted devices, and the like. The portable wearable device can be a smart watch, a smart bracelet, a head-mounted device, and the like. The server 104 may be implemented as a stand-alone server or as a server cluster comprised of multiple servers.

In one embodiment, as shown in fig. 2, a data presentation method is provided, which is described by taking the method as an example applied to the terminal 102 in fig. 1, and includes the following steps:

step 202, determining a card description entity, wherein the card description entity is used for generating a display interface of the target data.

The card description entity, which may also be referred to as data card metadata, is used to decouple a complete webpage into a plurality of separable data entities, and each separable data entity is used to construct a display interface to which the data card is attached, so as to reduce development difficulty and implement multi-party development. In an optional embodiment, the card description entity may be generated through a card description template, may be generated based on a card description class, and may be acquired through a database according to the identifier. The target data is data corresponding to data to be displayed, and may be specific service data or may include service logic of the service data.

In an optional embodiment, before obtaining the card description entity, the method further includes a step of generating the card description entity, which may be: and generating a specific card style according to the card description template. The step of generating the card description entity may also be to construct data such as a method, an event, a function, a parameter, and the like of the card description entity based on the card description class.

In an alternative embodiment, one card description entity is embedded in another card description entity. In an alternative embodiment, the card description entity may be directly obtained from the card description entity database; or acquiring corresponding personalized data based on the card description entity identification, combining the personalized data with the card description template, and defining a card description entity; and corresponding personalized data can be obtained based on the card description entity identification, and a card description entity is generated based on the personalized data and calculated according to the card description class.

And step 204, determining a data card based on the target data, wherein the data card is used for displaying the target data.

The data cards and the target data to be displayed have corresponding relations, the data cards are loaded in parallel, when a plurality of data cards exist in one page, the loading speed is higher compared with the loading speed of a single page, and the higher loading speed means better user experience. The data card may correspond to a service unit, and may display a certain service index or a certain type of service data in a text, picture, or video manner. For example: the data card can display any quantifiable data or type data such as service organization distribution, the number of tasks in a task pool, the number of tasks to be processed, task stock trend, quality inspection reject ratio and the like.

In an optional embodiment, the data card associated with the card description entity does not exist, the whole data page of the complete page is used as an interface of the data card, the data card can be dynamically placed on a homepage, a theme page, a sharing page, an early warning notification page and the like of one application or light application, the data card is directly reused, additional development is not needed, and only some state and authority difference controls are provided. The home page needs to be laid out in one metadata, and the loading can be completed only in one request, resulting in slow loading. The display of the same index on different pages needs to be repeatedly realized, the sharing of a single data index is realized, and the whole page sharing can share useless data.

Step 206, determining the corresponding relationship between the card description entity and the data card, and based on the corresponding relationship, applying the card description entity to generate a display interface of the data card.

In an optional embodiment, the correspondence between the card description entity and the data card is obtained based on a mapping table, or dynamically obtained by performing matching calculation through some algorithm, or the correspondence is constructed through a data dependent relationship.

In an optional embodiment, in the process of generating the display interface of the data card by using the card description entity, that is, the card metadata, is used for defining the view interface; and the data card corresponding to the card description entity, namely the card plug-in is used for calculating and counting specific data. The data is bound to the interface through the plug-in formed by the card description entity, so that a detachable display interface is formed, and the display interface is decoupled from a specific page, so that the display interface can be used in light applications such as any small programs.

The display interface is embedded in an application program such as a light application, or a landing page compatible with various programs, and may be a view interface, or may be called a user interface or a user interaction interface. Through the display interface, a user can provide input data, and schedule the card description entity and the data card.

Therefore, based on the corresponding relation, the application card describes and generates a display interface of the data card, and application programs such as light application and the like are embedded, so that development, recombination and generation are facilitated; or a landing page, which is convenient for cross-platform scheduling.

And step 208, displaying the target data on the display interface by using the data card.

In an optional embodiment, when the application data card displays the target data, various display interfaces can be displayed, one request can correspond to one or more card description entities, one or more interfaces are further constructed synchronously, and the loading speed is high. Data corresponding to the same index does not need to be repeatedly realized in the calculation process of different pages, and the sharing of single data index can be realized, key data can be shared, and useless data cannot be shared out. The display interface can be a group network interaction platform, an instant messaging program, a multi-end platform for communication and collaboration and the like.

According to the data display method, on the basis of decoupling the data card from the page to carry out data loading, the card description entity is used for further reducing the coupling relation between the data card and the page, the card description entity generates a display interface of target data through data such as a data structure of the target data, business data and/or a logic function, a corresponding interface is constructed through the card description entity, the data card is loaded rapidly, dynamic use of the data card level is realized, and a user can split the data card at will to share the split data card.

Based on the same reason, the corresponding interface is constructed through the card description entity, and the rapid expansion development of the page is also realized. In light application or common application such as a WeChat applet and the like, all data of the whole page does not need to be directly controlled, and the data card can be conveniently developed, scheduled, used and shared by taking the data card as a unit.

In one embodiment, as shown in FIG. 3, determining a card description entity comprises:

step 302, a card description class is obtained, the card description class including a method of scheduling data cards.

The card description class is generated based on a preset data set, and can also be called as a metadata template or a description card module; the card description template can be a card description template, the card description template comprises a card description template identification field and a page type field, the card description template identification field is used for identifying the card description template, and the page type field is used for representing the page type corresponding to the card description template.

Step 304, instantiating the card description class to obtain an initial card description object.

And step 306, determining description data of the target data, wherein the description data is used for describing a data structure, an interface and/or business logic of the target data.

And 308, combining the initial card description object and the description data to obtain a target card description object, wherein the target card description object is used for generating a display interface of the target data.

The target card description object is an entity, can be used independently or multiplexed, and can be used for constructing an interface corresponding to target data, constructing a partial interface of a page, or constructing a page independently. The display interface generated by the target card description object is equivalent to a separable data structure, and the data card required to be displayed can be separated from the light application based on the light application. Optionally, the display interface generated by the target card description object may include layout information of the corresponding data card, so that one or more corresponding data cards are displayed on the display interface.

In an alternative embodiment, combining the initial card description object with the description data is a process in which the initial card description object adds data. And adding the personalized data of the target card description object into the initial card description object by combining the initial card description object and the description data to obtain the target card description object for constructing a display interface of the target data.

In the embodiment, the scheduling method of the data card can be reused for multiple times by defining the card description class, so that the development efficiency can be greatly improved; by combining the initial card description object and the description data, the interface of the target data can be configured conveniently, the display interface corresponding to the target data can be generated efficiently, the customized sequencing of the home page is facilitated, and the multiplexing of the theme page is facilitated.

In one embodiment, as shown in fig. 4, combining the initial card description object with the description data to obtain the target card description object includes:

step 402, acquiring a target card description object identifier, and determining a source interface corresponding to the initial card description object, where the source interface is used to generate a display interface.

The source interface is equivalent to a path for acquiring a card description class, is used for acquiring a data sharing function, method or data, and can construct a display interface corresponding to the data card through the source interface corresponding to a data type or a data set scheduled by the data card; in an optional embodiment, the initial card description object is provided with an initial card description identifier, the initial card description identifier corresponds to a corresponding page type, and the page type is a mobile form and the like for characterizing a data sharing function, method or data.

And step 404, combining the target card description object identifier with the source interface to obtain a target card description object.

In this embodiment, the source interface of the object is described by the initial card, which may be used to generate a landing page, or may be used to obtain a ready-made data template. Therefore, the generation speed of the card description is further increased, the user can conveniently perform self-definition, and the development threshold is reduced.

In an alternative embodiment, the relationship between the card description template and the card description entity is described, as shown in fig. 5, the card description template is simply referred to as a card template, and the card description entity may be a card a, a card B, or a card C;

the card template comprises a page coding field and a page type field, wherein the page coding field is used for representing the card template so as to construct a card description entity, the page type field is used for representing an interface or an interface type of the card description template, and the page type can be a mobile form;

correspondingly, the card description entity comprises a page coding field, a page type field and a source page field; the page code field of the card description entity is filled with the target card description object identification; the page type field is an interface or an interface type of a card description template used by the card description entity; the source page is a page code field of the card template for determining the card template of the card description entity.

In an alternative embodiment, as shown in fig. 6, discussing the step of obtaining a data card, the step of determining the data card based on the target data comprises:

step 602, a data card base class is obtained, where the data card base class includes a preset display logic.

Step 604, generating a data card subclass based on the display logic corresponding to the data card base class and the target data.

The data card base class is formed by abstracting entity commonalities of the data cards, all information in the base class can be inherited by data card subclasses, new information can be added into the data card subclasses to form new classes so as to construct personalized subclasses, and the information added into the data card subclasses can be one or more of display logic, methods, functions, events, instructions, business logic, logic functions and the like.

And 606, acquiring target data, and instantiating the data card subclass based on the target data to obtain the data card.

In an alternative embodiment, as shown in fig. 7, a relationship between a data card base class and a data card sub class is described, wherein the name of the data card base class may be a card template plug-in (cardteleplaceplugin), and the name of the data card sub class may be a card a plug-in "cardplugin", a card B plug-in "cardplugin", a card C plug-in "cardplugin", and the like; wherein:

the card template plug-in can be generated based on a plug-in base class, such as abstract plug-in (abstract mobformplogic) of a table class, and a function for controlling loading exists in the abstract plug-in of the table class, so that the card template plug-in and the plug-in related to the card template plug-in are loaded after certain events occur; for example, the relevant functions of the card template plug-in may be loaded after the creation of the new data (afterCreateNewData).

In the card template plug-in, relevant attributes, functions or events for presentation, including relevant functions for sharing, relevant functions for judging whether the presented card is modifiable, relevant functions for hiding prompts, relevant functions for adding mapping relationships between data to be presented, and the like are included, and specifically, as shown in fig. 7, "store mpo menu (String)", "share to ()" is a relevant function for sharing; "onlyRead ()" is a related function for determining that the displayed card is not modifiable; "setnodataview (string tip)" is a correlation function for hiding hints; "FilcaldShareParam (Map < String, Object >)" is a correlation function for adding a mapping, where "true" indicates that this attribute is selected.

In the card plug-in, on the basis of the card template plug-in, some functions can be optionally added to form a data card subclass so as to generate a data card.

In the embodiment, the preset display logic is determined by defining the data card base class, so that a specific data card subclass is conveniently constructed without repeatedly constructing at least part of codes; the preset display logic is combined with the personalized display logic corresponding to the target data to obtain the data card subclass, so that the data card subclass can be reused for multiple times, dynamic use is facilitated, and a plurality of data cards can be generated conveniently. Therefore, the difficulty of data card development is further reduced, the efficiency of data card development is improved, and dynamic data cards can be conveniently used.

In an alternative embodiment, as shown in fig. 8, the application card description generates a display interface of the data card, including:

step 802, determining a light application page, wherein the light application page comprises a card description entity and a data card.

The light application page is a page of a light application program and comprises small program pages on various platforms. The light application web pages in the prior art all have higher integration level, the data cards in the light application web pages cannot be separated, and after the light application web pages are decoupled again, the data cards in the light application web pages correspond to the card description entities to realize separation.

Step 804, in response to the sharing instruction, determining a target card description entity from the card description entity in the light application page, and applying the target card description entity to generate a display interface, where the display interface carries a target data card corresponding to the target card description entity.

In this embodiment, the target card description entity is selected through the card description entity under the light application page, and the display interface of the target data is generated by the target card description, so as to obtain the display interface with separable data, where the display interface with separable data does not depend on light application, and can be used in a cross-end, cross-platform, cross-system, and cross-program manner, and the flexibility of development convenience of the data card is displayed from a user plane. Even on the user level, one webpage can be freely split and combined and can be freely shared, and the user-defined effect is realized.

In an optional embodiment, as shown in fig. 9, the card description entity and the data card are both multiple, and displaying the target data by using the data card includes:

and 902, respectively applying each card description entity to a display interface to generate layout information corresponding to each card description entity.

In an optional embodiment, the card description entities are applied to generate layout information corresponding to the card description entities, and one or more second data display interfaces are set in the first data display interface. In one embodiment, the first data presentation interface corresponds to a light application page and the second data presentation interface corresponds to a portion of the light application page; in another embodiment, the first data presentation interface corresponds to a portion of the page that is detached from the light application page, and the second data presentation interface is a detachable interface of the first data presentation interface.

And 904, respectively loading the data cards corresponding to the card description entities based on the layout information, applying the data cards to load corresponding target data to obtain the filled data cards, and applying the filled data cards to display the target data.

In the embodiment, the layout of each data card is generated through card description, so that a developer can conveniently perform modular data scheduling, and the difficulty of data generation is further reduced. More developers can be used for developing data, and the development efficiency is improved.

In a specific embodiment, the method for analyzing the application in a specific application scenario is discussed without focusing on the description of the innovation point but focusing on the user perspective.

As a whole, as shown in fig. 10, fig. 10 is a sequence diagram of card sharing. When a user clicks the additional menu at the upper right corner of the card in the light application, if the current light application runs in a specific program such as a cloud home, a sharing menu is available, the sharing menu is clicked, a contact person or a group is selected, and then sharing is carried out. After the sharer sees the sharing information, the sharer clicks the sharing message body, enters a sharing landing page, and dynamically loads a related data card according to the information attached to sharing and displays the related data card to the sharee for viewing. Specifically, the process of sharing the webpage by the user includes:

(1) the sharing user accesses one or more of the light application home page, the subject page, or the sharing page.

(2) And loading the light application data card, wherein the light application data card is separable if the data card and the card description entity have corresponding relation.

(3) And acquiring a running environment, wherein the running environment refers to a running platform and comprises various data such as a browser and the like.

(4) And judging whether the data card is the detachable light application page or not based on the running environment.

(5) If the data card and the card description entity have the corresponding relation, the data card is separable, and the data card is returned to the light application sharing page.

(6) And sending the separated data card to the sharing user from the light application sharing page.

(7) The sharing user clicks an additional menu of the data card to carry out sharing operation events; the additional menu of the data card is generated by the card description entity, belongs to a display interface, and can realize the sharing process of the data card with or without the additional menu.

(8) And generating a sharing page by using the data card corresponding to the sharing operation event, and sharing the sharing page to the light application platforms or individuals or groups of the application platforms.

(9) And after the sharing is successful, returning the sharing successful message to the sharing user and/or the shared user.

(10) The sharing user and the shared user can load the data card through the sharing page without accessing the light application platform;

(11) after the data cards in the sharing page are viewed, the data cards can return to the sharing page of the light application;

(12) and returning the shared page to other drivers or application programs of the user terminal.

In this specific application scenario, as shown in fig. 11, the first page of the light application includes two data cards, and each data card has its corresponding content; in the sharing landing page, as shown in fig. 12, there is a data card, and the user can directly access the data card without going through the platform page.

It should be understood that, although the steps in the flowcharts related to the embodiments as described above are sequentially displayed as indicated by arrows, the steps are not necessarily performed sequentially as indicated by the arrows. The steps are not performed in the exact order shown and described, and may be performed in other orders, unless explicitly stated otherwise. Moreover, at least a part of the steps in the flowcharts related to the embodiments described above may include multiple steps or multiple stages, which are not necessarily performed at the same time, but may be performed at different times, and the execution order of the steps or stages is not necessarily sequential, but may be rotated or alternated with other steps or at least a part of the steps or stages in other steps.

Based on the same inventive concept, the embodiment of the application also provides a data display device for realizing the data display method. The implementation scheme for solving the problem provided by the device is similar to the implementation scheme recorded in the method, so the specific limitations in one or more embodiments of the data display device provided below can be referred to the limitations of the data display method in the above, and are not described herein again.

In one embodiment, as shown in fig. 13, there is provided a data presentation apparatus including: the card description determining module, the data card determining module, the display interface generating module and the data display module are arranged, wherein:

the card description determining module is used for determining a card description entity, and the card description entity is used for generating a display interface of the target data;

the data card determining module is used for determining a data card based on the target data, and the data card is used for displaying the target data;

the display interface generating module is used for determining the corresponding relation between the card description entity and the data card and applying the card description entity to generate a display interface of the data card based on the corresponding relation;

In one embodiment, a card description determination module includes: a description class acquisition unit, a description data acquisition unit, a second description object generation unit, wherein:

the description acquisition unit is used for acquiring card description classes, and the card description classes comprise methods for scheduling data cards;

the first description object generation unit is used for instantiating the card description class to obtain an initial card description object;

the description data determining unit is used for determining the description data of the target data, and the description data is used for describing the data structure, the interface and/or the business logic of the target data;

and the second description object generation unit is used for combining the initial card description object and the description data to obtain a target card description object, and the target card description object is used for generating a display interface of the target data.

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

the data acquisition subunit is used for acquiring the target card description object identifier and determining a source page corresponding to the initial card description object, wherein the source page is used for generating a display interface;

and the second description object constructing subunit is used for combining the target card description object identifier with the source interface to obtain the target card description object.

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

the base class acquiring unit is used for acquiring a data card base class, and the data card base class comprises preset display logic;

the subclass definition unit is used for generating a data card subclass based on the display logic corresponding to the data card base class and the target data;

and the data generation unit is used for acquiring target data and instantiating the data card subclass based on the target data to obtain the data card.

In one embodiment, a presentation interface generation module includes: light application page acquisition unit shares page generation unit, wherein:

the light application page acquisition unit is used for determining a light application page, and the light application page comprises a card description entity and a data card;

the sharing page generation unit is used for responding to a sharing instruction, determining a target card description entity from the card description entity in the light application page, applying the target card description entity to generate a display interface, and enabling the display interface to carry a target data card corresponding to the target card description entity.

In one embodiment, the presentation interface generation module further comprises: layout information acquisition unit, data presentation unit, wherein:

the layout information acquisition unit is used for respectively applying each card description entity on the display interface to generate layout information corresponding to each card description entity;

and the data display unit is used for loading the data cards corresponding to the card description entities respectively based on the layout information, loading corresponding target data by applying the data cards to obtain the filled data cards, and displaying the target data by applying the filled data cards.

The various modules in the data presentation device described above may be implemented in whole or in part by software, hardware, and combinations thereof. The modules can be embedded in a hardware form or independent from a processor in the computer device, and can also be stored in a memory in the computer device in a software form, so that the processor can call and execute operations corresponding to the modules.

In one embodiment, a computer device is provided, which may be a terminal, and its internal structure diagram may be as shown in fig. 14. The computer device includes a processor, a memory, a communication interface, a display screen, and an input device connected by a system bus. Wherein the processor of the computer device is configured to provide computing and control capabilities. The memory of the computer device comprises a nonvolatile storage medium and an internal memory. The non-volatile storage medium stores an operating system and a computer program. The internal memory provides an environment for the operation of an operating system and computer programs in the non-volatile storage medium. The communication interface of the computer device is used for carrying out wired or wireless communication with an external terminal, and the wireless communication can be realized through WIFI, a mobile cellular network, NFC (near field communication) or other technologies. The computer program is executed by a processor to implement a data presentation method. The display screen of the computer equipment can be a liquid crystal display screen or an electronic ink display screen, and the input device of the computer equipment can be a touch layer covered on the display screen, a key, a track ball or a touch pad arranged on the shell of the computer equipment, an external keyboard, a touch pad or a mouse and the like.

Those skilled in the art will appreciate that the architecture shown in fig. 14 is merely a block diagram of some of the structures associated with the disclosed aspects and is not intended to limit the computing devices to which the disclosed aspects apply, as particular computing devices may include more or less components than those shown, or may combine certain components, or have a different arrangement of components.

In one embodiment, a computer device is further provided, which includes a memory and a processor, the memory stores a computer program, and the processor implements the steps of the above method embodiments when executing the computer program.

In an embodiment, a computer-readable storage medium is provided, on which a computer program is stored which, when being executed by a processor, carries out the steps of the above-mentioned method embodiments.

In an embodiment, a computer program product is provided, comprising a computer program which, when being executed by a processor, carries out the steps of the above-mentioned method embodiments.

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 for analysis, stored data, presented data, etc.) referred to in the present application are information and data authorized by the user or sufficiently authorized by each party.

It will be understood by those skilled in the art that all or part of the processes of the methods of the embodiments described above can be implemented by hardware instructions of a computer program, which can be stored in a non-volatile computer-readable storage medium, and when executed, can include the processes of the embodiments of the methods described above. Any reference to memory, database, or other medium used in the embodiments provided herein may include at least one of non-volatile and volatile memory. The nonvolatile Memory may include Read-Only Memory (ROM), magnetic tape, floppy disk, flash Memory, optical Memory, high-density embedded nonvolatile Memory, resistive Random Access Memory (ReRAM), Magnetic Random Access Memory (MRAM), Ferroelectric Random Access Memory (FRAM), Phase Change Memory (PCM), graphene Memory, and the like. Volatile Memory can include Random Access Memory (RAM), external cache Memory, and the like. 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), among others. The databases referred to in various embodiments provided herein may include at least one of relational and non-relational databases. The non-relational database may include, but is not limited to, a block chain based distributed database, and the like. The processors referred to in the embodiments provided herein may be general purpose processors, central processing units, graphics processors, digital signal processors, programmable logic devices, quantum computing based data processing logic devices, etc., without limitation.

The technical features of the above embodiments can be arbitrarily combined, and for the sake of brevity, all possible combinations of the technical features in the above embodiments are not described, but should be considered as the scope of the present specification as long as there is no contradiction between the combinations of the technical features.

The above-mentioned embodiments only express several embodiments of the present application, and the description thereof is more specific and detailed, but not construed as limiting the scope of the present application. It should be noted that, for a person skilled in the art, several variations and modifications can be made without departing from the concept of the present application, which falls within the scope of protection of the present application. Therefore, the protection scope of the present application shall be subject to the appended claims.

Claims

1. A method for presenting data, the method comprising:

2. The method of claim 1, wherein the determining a card description entity comprises:

3. The method of claim 2, wherein said combining said initial card description object with said description data to obtain a target card description object comprises:

4. The method of claim 1, wherein the determining a data card based on the target data comprises:

5. The method of claim 1, wherein applying the card description to generate a presentation interface for the data card comprises:

6. The method of claim 1, wherein the card description entity and the data card are both multiple, and the applying the data card to display the target data comprises:

7. A data presentation device, the device comprising:

8. A computer device comprising a memory and a processor, the memory storing a computer program, characterized in that the processor, when executing the computer program, implements the steps of the method of any of claims 1 to 6.

9. A computer-readable storage medium, on which a computer program is stored, which, when being executed by a processor, carries out the steps of the method of any one of claims 1 to 6.

10. A computer program product comprising a computer program, characterized in that the computer program realizes the steps of the method of any one of claims 1 to 6 when executed by a processor.