CN111142863B

CN111142863B - Page generation method and device

Info

Publication number: CN111142863B
Application number: CN201911320047.5A
Authority: CN
Inventors: 杨云鹏; 周山明
Original assignee: Shenzhen Kingdom Technology Co ltd
Current assignee: Shenzhen Kingdom Technology Co ltd
Priority date: 2019-12-19
Filing date: 2019-12-19
Publication date: 2023-06-30
Anticipated expiration: 2039-12-19
Also published as: CN111142863A

Abstract

The application is applicable to the technical field of computer data processing, and provides a method and a device for generating a page, wherein the method comprises the following steps: acquiring task information for generating a target page, wherein the task information comprises a task type and task data; acquiring an assembly template and example data corresponding to the task type; respectively generating view data corresponding to each task data through the task data and the example data; generating a page component through the view data and the component template; and generating the target page according to all the page components. The method can enable the repeated utilization rate of the generated codes of the required pages to be high when the system is developed, and reduces the development workload.

Description

Page generation method and device

Technical Field

The application belongs to the technical field of computer data processing, and particularly relates to a method and a device for generating pages.

Background

With the progress of technology, internet technology is rapidly developing, more and more business processes are performed on various platforms of the internet, and manual operations are less and less. For example, the existing counter auditing platform generally operates on a web platform, displays the contents of different businesses needing auditing in the form of web pages, and after auditing, the staff at the auditing station confirms whether the business passes or is rejected. Although the business is various, the flow of each business is different, but the data type is different, and the auditing content is mostly displayed in the forms of text key value pairs, tables, forms and the like. Thus, many identical places, such as data formats, display levels, rendering components, etc., appear in the process of developing a business process platform, which may appear as many repeated processes, repeated operations, repeated code.

In the prior art, when a service platform system is developed, in order to meet the customization demands of different users on pages, different codes are required to be generated according to different user demands during development, and the structures of page data are different due to artificial factors such as coding habit, coding mode, data processing mode and flow processing mode of developers, so that the code structure of the whole system becomes very complex, difficult to understand and inconvenient for the developers to maintain.

Disclosure of Invention

The embodiment of the application provides a method and a device for generating a page, which solve the problems of low code reuse rate and high development workload of a service platform system in the prior art.

In a first aspect, an embodiment of the present application provides a method for generating a page, including:

acquiring task information for generating a target page, wherein the task information comprises a task type and task data;

acquiring a component template for constructing a target page and example data corresponding to the task type in the task information;

respectively generating view data corresponding to each task data through the task data and the example data;

Generating a page component through the view data and the component template;

and generating the target page according to all the page components.

In a possible implementation manner of the first aspect, if the rendering manner of each page component of the target page is to be changed, only the component template needs to be changed; if the display mode of each page component of the target page is to be changed, only the example data needs to be changed.

It should be appreciated that the example data is determined based on the task type of the task information of the target page, the component templates may be determined separately or based on the task type, and both may be preset before the task information is acquired, and may be modified based on the respective different page generation requirements.

In a second aspect, an embodiment of the present application provides a device for generating a page, including:

the task acquisition module is used for acquiring task information generated about the target page, including task types and task data;

the template acquisition module is used for acquiring a component template for constructing a target page and example data corresponding to the task type in the task information;

The data conversion module is used for generating view data corresponding to each task data in the task information through the task data and the example data;

the assembly generating module is used for generating a page assembly through the view data and the assembly template;

and the page generation module is used for generating the target page according to all the page components.

In a third aspect, an embodiment of the present application provides a terminal device, including: a memory, a processor and a computer program stored in the memory and executable on the processor, the processor implementing the method of any one of the above first aspects when the computer program is executed.

In a fourth aspect, embodiments of the present application provide a computer-readable storage medium, comprising: the computer readable storage medium stores a computer program which, when executed by a processor, implements the method of any of the above first aspects.

In a fifth aspect, embodiments of the present application provide a computer program product for, when run on a terminal device, causing the terminal device to perform the method of any one of the first aspects.

It will be appreciated that the advantages of the second to fifth aspects may be found in the relevant description of the first aspect, and are not described here again.

Compared with the prior art, the embodiment of the application has the beneficial effects that:

compared with the prior art, the method provided by the application has the advantages that the corresponding page components are generated by adopting the same component template, the code structures of the page components of the target page can be unified, the page components of the pages are developed based on the same component template library, and the code reuse rate of the page component codes is high; and the task data is associated with the page components through the example data and the component templates, when the requirements of page generation are different, only the codes corresponding to the example data or the component templates are required to be changed, the codes of all the page components are not required to be changed, and the maintenance is easy.

Drawings

In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings that are required for the embodiments or the description of the prior art will be briefly described below, it being obvious that the drawings in the following description are only some embodiments of the present application, and that other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.

Fig. 1 is a flowchart of an implementation of a page generating method provided in the first embodiment of the present application.

Fig. 2 is a schematic view of an application scenario provided in an embodiment of the present application.

Fig. 3 is a flowchart of an implementation of the page generating method provided in the second embodiment of the present application.

Fig. 4 is a flowchart of an implementation of the page generating method S103 provided in the third embodiment of the present application.

Fig. 5 is a flowchart of an implementation of the page generating method S402 provided in the fourth embodiment of the present application.

Fig. 6 is a flowchart illustrating an implementation of the page generating method S5022 according to the fifth embodiment of the present application.

Fig. 7 is a flowchart of an implementation of the page generating method S104 provided in the sixth embodiment of the present application.

Fig. 8 is a specific application scenario effect diagram provided in another embodiment of the present application.

Fig. 9 is a schematic structural diagram of a page generating apparatus according to an embodiment of the present application.

Fig. 10 is a schematic structural diagram of a terminal device according to an embodiment of the present application.

Detailed Description

In the following description, for purposes of explanation and not limitation, specific details are set forth, such as particular system configurations, techniques, etc. in order to provide a thorough understanding of the embodiments of the present application. It will be apparent, however, to one skilled in the art that the present application may be practiced in other embodiments that depart from these specific details. In other instances, detailed descriptions of well-known systems, devices, circuits, and methods are omitted so as not to obscure the description of the present application with unnecessary detail.

It should be understood that the terms "comprises" and/or "comprising," when used in this specification and the appended claims, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.

It should also be understood that the term "and/or" as used in this specification and the appended claims refers to any and all possible combinations of one or more of the associated listed items, and includes such combinations.

As used in this specification and the appended claims, the term "if" may be interpreted as "when..once" or "in response to a determination" or "in response to detection" depending on the context. Similarly, the phrase "if a determination" or "if a [ described condition or event ] is detected" may be interpreted in the context of meaning "upon determination" or "in response to determination" or "upon detection of a [ described condition or event ]" or "in response to detection of a [ described condition or event ]".

In addition, in the description of the present application and the appended claims, the terms "first," "second," "third," and the like are used merely to distinguish between descriptions and are not to be construed as indicating or implying relative importance.

Reference in the specification to "one embodiment" or "some embodiments" or the like means that a particular feature, structure, or characteristic described in connection with the embodiment is included in one or more embodiments of the application. Thus, appearances of the phrases "in one embodiment," "in some embodiments," "in other embodiments," and the like in the specification are not necessarily all referring to the same embodiment, but mean "one or more but not all embodiments" unless expressly specified otherwise. The terms "comprising," "including," "having," and variations thereof mean "including but not limited to," unless expressly specified otherwise.

In the embodiment of the present invention, the execution subject of the flow is a terminal device. The terminal device includes, but is not limited to: a server, a computer, a smart phone, a tablet computer, etc. capable of executing the method of the present application. Fig. 1 shows a flowchart of an implementation of the page generation method provided in the first embodiment of the present application, which is described in detail below:

in S101, task information for generating a target page is acquired, including a task type and task data.

In this embodiment, the task information includes a task type and task data. The task type represents personalized demand information of the target page, and the task type obtained according to the target page generated by the demand of the client data change service is shown as a target page which can display the specific condition of the client data change. The task type may be represented by a corresponding task identification, which may be an identification encoded by an integer int type or a string char type. The task data includes various data required for generating the target page, and for generating the corresponding target page based on the client data changing service, the task data includes client data before changing and client data after changing, specifically, the client data includes client data such as name, sex, contact phone and the like of the client, and the task data may also include a source of the client data changing.

In this embodiment, the manner of acquiring the task information may specifically be: the terminal equipment generates a corresponding task information input page, a salesman inputs the task information on the task information input page, specifically, the salesman inputs a task type on the task information input page, the terminal equipment generates an input page for collecting task data based on the task type, and the salesman inputs task data corresponding to the task information on the task data input page. Or the terminal equipment can send a task information acquisition request to the database, and acquire the task information from the database; the database may be a local database or a network database. The terminal device can also send a request to the database, obtain the original data corresponding to the task information, generate an original data display page based on the original data, determine the task data of the task information based on the display page and the task type of the task information by a salesman, thereby determining the task information, and then input the task information to the terminal device.

In S102, a component template for building a target page and example data corresponding to the task type within the task information are acquired.

In this embodiment, the example data is stored in association with the task type, and one example data may correspond to one task type. The example data includes data processing logic corresponding to the task data, where the data processing logic is configured to determine a display manner of each task data in generating a target page, for example: in the "customer profile change" target page, the field "customer's contact phone of" customer's name of three "in the task data is changed from '18888888888' to '17777777777', the customer's name of three" is displayed in the region for displaying customer's name in the target page, and the contact phone '18888888888' before customer's change and the contact phone' 17777777777 'after customer's change are displayed in the region for displaying specific change contents of customer profile in the target page.

In an exemplary embodiment, before the component template and the example data corresponding to the task type are obtained, the component template for building the target page is further configured, and associated example data are configured for each task type, so that when the target page with the same task type is generated, different task data generate the target page based on the same example data and the same component template, and then the code specifications of the target pages corresponding to the different task data are unified, so that the code recycling rate is high. The example data represents the personalized requirements of the task corresponding to the task type and generating the target page, and the data processing logic of the task data can be changed according to different requirements of generating the target page.

In S103, view data corresponding to each task data is generated by the task data and the example data, respectively.

In the present embodiment, the data type of each data of the above-described example data corresponds to the data type of each data of the above-described task data. Each data of the above example data has a certain data processing logic, and S103 gives each task data a corresponding data processing logic of the task data in the example data, so as to obtain the view data.

Illustratively, in the task of generating a target page of a client profile change, two items of task data are "contact phone before client profile change: 18888888888 "customer profile post change contact: 17777777777", the example data corresponding to the two items of task data are" tel-bef = 12345678900 "and" tel-las= 12345678901", and the view data corresponding to the two items of task data are" tel-bef = 18888888888 "and" tel-las= 17777777777", in which view data there is data processing logic: "tel-bef = 18888888888" indicates that the value of the 3 rd item of data "tel-bef" of the customer material before the change is "18888888888" (the first two items are the name and sex of the customer), and "tel-las= 17777777777" indicates that the value of the 3 rd item of data "tel-las" of the customer material after the change is "17777777777".

It will be appreciated that in the view data described above, there may be another data processing logic: traversing the client data before and after the change, comparing the values of the data corresponding to the data types of the two parties, for example, comparing the 3 rd item of data 'tel-bef' of the client data before the change and the 3 rd item of data 'tel-las' of the client data after the change, and if the values of the data corresponding to the data types of the two parties are the same, not displaying the data corresponding to the data types of the two parties; and if the values of the data corresponding to the data types of the two parties are different, displaying the data corresponding to the data types of the two parties.

In S104, a page component is generated from the view data and the component template.

In this embodiment, at least one tag data exists in the view data, at least one data group data exists in each tag data, and at least one data unit data exists in each data group data; each of the tag data, the data group data, and the data unit data has rendering logic corresponding to the data group data in the component template, and each of the tag data, the data group data, and the data unit data in the view data is rendered based on the rendering logic corresponding to each of the tag data, the data group data, and the data unit data in the view data, to obtain the page component. Rendering refers to the personalized setting of various aspects such as the background, the size, the word size, the color and the like of each data on a rendering object.

In an exemplary task of generating a target page of a client data change, the view data includes two tag data, namely a "client data change" tag data and a "sponsor information", wherein the "client data change" tag data represents a change condition of data b of all clients, and rendering the "client data change" tag data to obtain a "client data change" tag assembly based on rendering logic corresponding to the "client data change" tag data, specifically, setting a title of the tag data to be three smaller in word size, a font Song Ti and an oval frame; at least one customer data change data group data exists in the customer data change label data, the data group represents the data change condition of one customer, the data group data is rendered to obtain a customer data change data group component based on rendering logic corresponding to the data group data, specifically, the title of the data group data is set to be a number four and a font Song Ti, and the data group component is packaged in the customer data change label component; there is "customer modified info" data unit data in the data group, the data unit data identifies the specific profile of the customer as more condition, for example, the contact phone number is changed from "18888888888" to "17777777777", the data unit data is rendered to obtain "customer modified info" data unit component based on rendering logic corresponding to the data unit data, specifically, "18888888888" is set to number five, font script, and "17777777777" is set to number five, font script, and highlighted, and the data unit component is encapsulated in the "customer profile change" data group component.

It should be understood that the above exemplary description describes only a portion, and not all, of the process steps and is not intended to limit the process steps.

In S105, the target page is generated according to all the page components.

In this embodiment, all the page components are displayed on the target page. The page components contain the position information of the page components on the target page, and based on the position information, the page components are arranged on the target page according to a certain rule.

It should be understood that the page generation method provided by the application can be realized based on Uni-App application, and the page generation method provided by the application can be implemented based on Uni-App, so that the page generation method is applicable to different platforms (android system, IOS system, web, etc.), namely, the target page can be generated on different platforms, that is, the codes forming the target page are automatically adapted to different platforms based on Uni-App.

In this embodiment, based on the example data and the component templates, the code structures of the components of the target page can be unified, so that the code reuse rate of the page component codes is high. Based on the rendering logic corresponding to the view data corresponding to the task data, dynamic rendering of the page component can be realized. According to different requirements of target page generation, different requirements of target page generation can be met by modifying example data or component templates, specific page component codes are not required to be modified, maintenance is easy, and workload is reduced.

Fig. 2 shows an application scenario schematic diagram provided in an embodiment of the present application, and details are as follows:

in this embodiment, referring to fig. 2, the target page includes a page component including two tab components, where the "client data change" tab component includes a data group component including three data unit modules, where the "client modified information" data unit component includes sub-data unit components corresponding to each task data, and in particular includes a contact phone related to "before client data change: 18888888888 "customer profile post change contact: 17777777777", which generates view data by way of example data, which correspond to" tel-bef = 18888888888 "and" tel-las= 17777777777", the view data having data processing logic comprising: traversing the client data before and the client data after the change, comparing the values of the data corresponding to the data types of the two parties, and if the values of the data corresponding to the data types of the two parties are the same, not displaying the data corresponding to the data types of the two parties; and if the values of the data corresponding to the data types of the two parties are different, displaying the data corresponding to the data types of the two parties. Illustratively, the data processing logic determines that the customer's "change profile" is "contact" and the "contact" is "18888888888" and the "17777777777" is the "17777777777" and, in particular, "17777777777" is highlighted (bold font instead of highlighting in fig. 2).

Fig. 3 shows a flowchart of an implementation of the page generating method according to the second embodiment of the present application, referring to fig. 1, with respect to the embodiment described in fig. 1, before S103, the page generating method according to the present embodiment further includes: s301 to S302 are specifically described below:

further, before generating view data corresponding to each task data according to the task data and the example data, the method further includes:

in S301, it is determined whether or not the value corresponding to each data type in the example data is legal.

In this embodiment, in order to prevent errors, before the view data is generated, the above example data is checked, specifically, it is determined whether the value corresponding to each data type in the example data is legal, for example, the character length of the contact phone is not more than 12, and the values corresponding to the contact phone data types in the example data are "12345678900" and "12345678901", which meet the condition that the character length is not more than 12, so it is determined that the value corresponding to the contact phone data type in the example data is legal.

It should be understood that before determining whether the value corresponding to each data type in the example data is legal, a verification algorithm of the value corresponding to each data type is preset, specifically, the terminal device may configure a corresponding verification algorithm for each data type, where the verification algorithm may be used to detect a data length, a data type, a sensitive word identification, and the like, and may also be used to detect whether the display data of the example data matches the current display time. The terminal device can acquire the corresponding verification algorithm from the example data according to the data type, and output a verification result of the example data through the verification algorithm.

In S302, if the determination results of all the values corresponding to the data types in the example data are legal, executing the passing task data and the example data, and generating view data corresponding to each task data in the task information.

In this embodiment, if the determination results of the values corresponding to the data types in the example data are legal, S103 is executed, and if the determination result of the values corresponding to at least one data type in the example data is illegal, error reporting information is generated based on the illegal value corresponding to the data type, so as to remind an operator that the example data are illegal, and instruct the operator to perform corresponding modification.

In this embodiment, the above example data is checked before S103 is executed, so that it is possible to prevent the generation of a wrong target page caused by an error in the example data, and ensure that the target page meets the generation requirement.

Fig. 4 shows a flowchart of an implementation of the page generating method S103 provided in the third embodiment of the present application. Referring to fig. 4, with respect to the embodiment described in fig. 1, the page generating method S103 provided in this embodiment includes S401 to S403, which are specifically described as follows:

Further, the generating view data corresponding to each task data in the task information through the task data and the example data includes:

in S401, template data groups corresponding to the respective task data groups in the example data in the task data are searched for, respectively.

In this embodiment, the task data includes at least one task data group, and each data type in the task data can find a corresponding data type in the example data. Illustratively, the task data includes a task data group including a group header, a group display identifier, a group name identifier, and the like, and an example data group including a group header, a group display identifier, a group name identifier, and the like, which is the template data group.

In S402, a target data group is generated from the task data group and the template data group.

In this embodiment, the task data group corresponds to each data type in the template data group, and the target data group is obtained by overlaying the value of each data type of each task data group with the value of the corresponding data type in the corresponding template data group.

In S403, view data is generated according to all the target data groups.

In this embodiment, the view data is obtained by encapsulating the target data group corresponding to each task data group in the task data.

It should be understood that the number of data groups in the task data is the same as the number of target data groups.

In this embodiment, by covering the values of the respective data types of the respective task data groups in the task data with the values of the respective data types of the respective template data groups in the example data, view data having the same data processing logic as the example data and the values of the respective data types as the task data are obtained, so as to generate the page component later.

Fig. 5 shows a flowchart of an implementation of the page generating method S402 provided in the fourth embodiment of the present application. Referring to fig. 5, with respect to the embodiment described in fig. 4, the page generating method S402 provided in this embodiment includes S501 to S502, which are specifically described as follows:

further, the generating the target data group according to the task data group and the corresponding template data group includes:

in S501, the template data group is initialized to obtain an initialized data group.

In this embodiment, the task data group includes a group display identifier and at least one task data unit, where a data type of the task data unit is a data unit. Illustratively, the task data group includes data types such as group title, group display identifier, group name identifier, data unit, etc., and the template data group also includes data types such as group title, group display identifier, group name identifier, data unit, etc.

In this embodiment, the template data group is initialized, specifically, illustratively, values corresponding to data types such as a group header, a group display identifier, a group name identifier, a data unit, and the like in the template data group are replaced with null values, so as to obtain the initialized data group.

In S502, the task data group is assigned to the initialization data group, and the target data group is generated.

In this embodiment, the target data group is obtained by assigning values corresponding to data types such as a group header, a group display identifier, a group name identifier, and a data unit in the task data group to data types corresponding to respective data types in the task data group in the initialization data group.

Further, S502 includes: s5021 to S5022 are specifically described below:

and if the group display flag of the task data group is true, executing S5021 to S5022.

In S5021, template data units corresponding to the task data units in the example data are searched for respectively.

In this embodiment, only if the group display flag of the task data group is determined to be true, the value of the task data unit (data type is data unit) in the task data group is assigned to the value corresponding to the data type as the data unit in the initialization data group.

In this embodiment, the template data unit corresponding to the task data unit should be included in the example data, where the template data unit includes data processing logic corresponding to the task data unit. Illustratively, the task data unit contains a data type such as a unit title, a unit name identification, etc., and the template data unit also contains a data type such as a unit title, a unit name identification, etc.

In S5022, a target data unit is generated according to the task data unit and the template data unit.

In this embodiment, the task data unit corresponds to each data type in the template data unit, and the value of each data type of each task data unit is overlaid on the value of the corresponding data type in the corresponding template data unit, so as to obtain the target data unit.

In this embodiment, by assigning the same data processing logic as the template data group corresponding to the task data group to the value of each data type of the task data group, the target data group whose data processing logic is the same as the template data group in the example view and whose value of each data type is the same as the task data group is obtained, so that view data is generated subsequently.

Fig. 6 shows a flowchart of implementation of the page generating method S5022 provided in the fifth embodiment of the present application. Referring to fig. 6, with respect to the embodiment described in fig. 5, the page generating method S5022 provided in this embodiment includes S601 to S602, which are specifically described as follows:

further, the generating a target data unit according to the task data unit and the template data unit includes:

in S601, the template data unit is initialized, and an initialized data unit is obtained.

In this embodiment, the task data unit includes a unit display identifier, a repeated rendering identifier, and one or more task delivery data. Illustratively, the task data unit includes data types such as a unit title, a unit display identifier, a unit name identifier, a repeated rendering identifier, and transfer data, and the template data group also includes data types such as a unit title, a unit display identifier, a unit name identifier, a repeated rendering identifier, and transfer data.

In this embodiment, the template data unit is initialized, specifically, illustratively, values corresponding to data types such as a unit title, a unit display identifier, a unit name identifier, a repeated rendering identifier, task delivery data and the like in the template data unit are replaced by null values, so as to obtain the initialized data unit.

In S602, the assignment of the task data unit to the initialization data unit generates the target data unit.

In this embodiment, illustratively, values corresponding to data types such as a unit title, a unit display identifier, a unit name identifier, a repeated rendering identifier, and transfer data in the task data unit are assigned to data types corresponding to each data type in the task data unit in the initialization data unit, so as to obtain the target data unit.

Further, S602 includes: s6021 to S6023 are specifically described below:

and if the unit display identification of the task data unit is true, executing S6021-S6022.

In S6021, the template transfer data corresponding to the task transfer data of the task data unit in the template data unit is searched for respectively.

In this embodiment, only if it is determined that the unit display identifier of the task data unit is true, the value of the task transfer data (the data type is transfer data) in the task data unit is assigned to the value corresponding to the data type in the initialization data unit as transfer data.

In this embodiment, the template transfer data corresponding to the task transfer data is included in the example data, where the template transfer data includes data processing logic corresponding to the task transfer data.

In S6022, target transfer data is generated from the task transfer data and the template transfer data.

In this embodiment, the task transfer data corresponds to each data type in the template transfer data, and the value of each data type of each task transfer data is overlaid on the value of the corresponding data type in the corresponding template transfer data, so as to obtain the target transfer data.

In S6023, a sub-target data unit corresponding to a sub-task data unit of the task data unit is determined based on the repeated rendering identification of the task data unit.

In this embodiment, if the repeated rendering flag is true, it indicates that the task data unit includes at least one sub-task data unit. And if the repeated rendering mark is false, the task data unit does not contain the subtask data unit. And the value of each data type of the subtask data unit covers the value of the data type of the subtask data unit in the template data unit corresponding to each data type of the subtask data unit, so as to obtain the subtask data unit.

It should be understood that, in this embodiment, the specific implementation of obtaining the sub-target data unit may refer to the step of obtaining the target data unit in S502 above, and the specific implementation of obtaining the sub-target data unit is compared with the specific implementation of obtaining the target data unit, where no data with the data type being the data unit exists in the sub-target data unit.

Further, S6023 includes: s60231 to S60233 are specifically described as follows:

and if the repeated rendering identification of the task data unit is true, executing S60231-S60233.

In S60231, the position of the subtask data unit of the task data unit is determined based on the data type of the task delivery data of the task data unit.

In this embodiment, if the data type of the task transfer data is a data unit, the subtask data unit is within the task transfer data. If the data type of the task transfer data is a field, the subtask data unit is within the task data unit and outside the task transfer data.

In S60232, sub-template data units corresponding to the sub-task data units of the task data units in the template data units are searched respectively.

In this embodiment, the sub-template data unit corresponding to the sub-task data unit should be in the template data units in the template data group in the example data.

In S60233, the sub-target data unit is generated from the sub-task data unit and the sub-template data unit.

In this embodiment, the subtask data unit corresponds to each data type in the subtask data unit, and the subtask data unit is obtained by covering the value of each data type of each subtask data unit with the value of the corresponding data type in the corresponding subtask data unit.

In this embodiment, the data processing logic is given to the value of each data type of the task data unit, which is the same as the template data unit corresponding to the task data unit, so as to obtain a target data group, which is the same as the template data unit in the template data group in the example view, of the data processing logic, and the value of each data type is the same as the task data unit, so as to generate view data subsequently.

Fig. 7 shows a flowchart of an implementation of the page generating method S104 provided in the sixth embodiment of the present application. Referring to fig. 7, with respect to the embodiment described in fig. 1, the page generating method S104 provided in this embodiment includes S701 to S703, which are specifically described as follows:

Further, generating a page component through the view data and the component template, including:

in S701, tag rendering logic corresponding to each view data is acquired based on the component template.

In this embodiment, the component template should include the tag rendering logic corresponding to the view data, which is used to indicate how to render the view data, so as to obtain the page component.

In S702, rendering the view data based on the tag rendering logic, resulting in a tag rendering component.

In this embodiment, the tag rendering logic illustratively has a data processing logic: the title font of the label is set as a font size of a small three, a font Song Ti and an oval frame.

In S703, all the tag rendering components are encapsulated to obtain the page component.

In this embodiment, the page component includes at least one tag rendering component. Illustratively, the page component contains two label rendering components, a "client materials change" and a "sponsor information," the title of the label rendering component that the page component is displaying is highlighted, the display color is blue, and the title of the label rendering component that the page component is not displaying is gray.

Further, S702 includes S7021 to S7023, and the details are as follows:

in S7021, data group rendering logic corresponding to each of the target data groups is acquired based on the component template.

In this embodiment, the component template should include the data group rendering logic corresponding to the target data group, so as to instruct how to render the target data group, thereby obtaining the tag rendering component.

In S7022, the target data group is rendered based on the data group rendering logic, resulting in a data group rendering component.

In the present embodiment, the title of the target data group is exemplarily set to the font size four, the font Song Ti.

In S7023, all the data group rendering components are encapsulated in the tag rendering components corresponding to the respective data group rendering components.

In this embodiment, the tag rendering component includes at least one data group rendering component.

Further, S7022 includes S70221 to S70223, and the specific details are as follows:

in S70221, data unit rendering logic corresponding to each target data unit is obtained based on the unit type of the target data unit and the component template.

In this embodiment, the component template should include the data unit rendering logic corresponding to the target data unit, so as to instruct how to render the target data unit, thereby obtaining the data group rendering component.

In S70222, the target data unit is rendered based on the data unit rendering logic, resulting in a data unit rendering component.

In this embodiment, exemplarily, the title in the data unit rendering component is set to be the font size of four, the font Song Ti, the content is set to be the font size of five, the font regular script, and the specific content is highlighted, specifically, in the target page generating task of the client profile modification, the title "client modified information" is set to be the font size of four, the font Song Ti, the contact phone "18888888888" before the client modification and the contact phone "17777777777" after the client modification are set to be the font size of five, the font regular script, wherein the contact phone "17777777777" after the client modification is highlighted, and the display color is orange.

In S70223, all the data unit rendering components are encapsulated in the data group rendering component corresponding to each data unit rendering component.

In this embodiment, the data group rendering component includes at least one data unit rendering component.

In this embodiment, based on the method of this embodiment, the display mode of each task data in the target page may be made to meet the personalized requirement of generating the task of the target page. If the display mode of the task data of a certain data type in the target page is to be changed, only the corresponding component template is required to be changed, so that the code of the target page is easy to maintain, and the development workload is reduced.

Fig. 8 shows a specific application scenario effect diagram provided in another embodiment of the present application, which is described in detail below:

in the new target page generation task, specifically, in the new "client profile change" target page generation task, it is required to change the display mode of the client modified information so as to more emphasize the change of the client profile.

Referring to fig. 8, the module of "operation type" is exemplarily added to fig. 8, and the operation type is not limited to modification, as compared with fig. 2. In the transition between fig. 2 to fig. 8, based on the page generating method provided in the present application, only the corresponding example data or component template needs to be modified (for example, in this embodiment, the corresponding example data or component template refers to the example data or component template corresponding to the same task type in which the task type is changed by the client material), so that the code of the page does not need to be specifically modified, and the development workload is reduced.

Corresponding to the page generating method described in the above embodiments, fig. 9 shows a schematic structural diagram of the page generating apparatus provided in an embodiment of the present application, and for convenience of explanation, only the portions related to the embodiments of the present application are shown.

Referring to fig. 9, the apparatus includes: the task acquisition module is used for acquiring task information generated about the target page, including task types and task data; the template acquisition module is used for acquiring a component template for constructing a target page and example data corresponding to the task type in the task information; the data conversion module is used for generating view data corresponding to each task data in the task information through the task data and the example data; the assembly generating module is used for generating a page assembly through the view data and the assembly template; and the page generation module is used for generating the target page according to all the page components.

It should be noted that, because the content of information interaction and execution process between the devices is based on the same concept as the method embodiment of the present application, specific functions and technical effects thereof may be referred to in the method embodiment section, and will not be described herein again.

It will be apparent to those skilled in the art that, for convenience and brevity of description, only the above-described division of the functional units and modules is illustrated, and in practical application, the above-described functional distribution may be performed by different functional units and modules according to needs, i.e. the internal structure of the apparatus is divided into different functional units or modules to perform all or part of the above-described functions. The functional units and modules in the embodiment may be integrated in one processing unit, or each unit may exist alone physically, or two or more units may be integrated in one unit, where the integrated units may be implemented in a form of hardware or a form of a software functional unit. In addition, specific names of the functional units and modules are only for convenience of distinguishing from each other, and are not used for limiting the protection scope of the present application. The specific working process of the units and modules in the above system may refer to the corresponding process in the foregoing method embodiment, which is not described herein again.

Fig. 10 shows a schematic structural diagram of a terminal device according to an embodiment of the present application. As shown in fig. 10, the terminal device 10 of this embodiment includes: at least one processor 100 (only one is shown in fig. 10), a memory 101, and a computer program 102 stored in the memory 101 and executable on the at least one processor 100, the processor 100 executing the computer program 102 implementing the steps in any of the various shared services metrics determination method embodiments described above based on a communication credential sharing service.

The terminal device 10 may be a computing device such as a desktop computer, a notebook computer, a palm computer, a cloud server, etc. The terminal device may include, but is not limited to, a processor 100, a memory 101. It will be appreciated by those skilled in the art that fig. 10 is merely an example of the terminal device 10 and is not intended to limit the terminal device 10, and may include more or fewer components than shown, or may combine certain components, or may include different components, such as input-output devices, network access devices, etc.

The processor 100 may be a central processing unit (Central Processing Unit, CPU), and the processor 100 may also be other general purpose processors, digital signal processors (Digital Signal Processor, DSP), application specific integrated circuits (Application Specific Integrated Circuit, ASIC), off-the-shelf programmable gate arrays (Field-Programmable Gate Array, FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, or the like. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.

The memory 101 may in some embodiments be an internal storage unit of the terminal device 10, such as a hard disk or a memory of the terminal device 10. The memory 101 may in other embodiments also be an external storage device of the terminal device 10, such as a plug-in hard disk, a Smart Media Card (SMC), a Secure Digital (SD) Card, a Flash memory Card (Flash Card) or the like, which are provided on the terminal device 10. Further, the memory 101 may also include both an internal storage unit and an external storage device of the terminal device 10. The memory 101 is used for storing an operating system, application programs, boot loader (BootLoader), data, other programs, etc., such as program codes of the computer program. The memory 101 may also be used to temporarily store data that has been output or is to be output.

Embodiments of the present application also provide a computer readable storage medium storing a computer program which, when executed by a processor, implements steps that may implement the various method embodiments described above.

Embodiments of the present application provide a computer program product which, when run on a mobile terminal, causes the mobile terminal to perform steps that may be performed in the various method embodiments described above.

The integrated units, if implemented in the form of software functional units and sold or used as stand-alone products, may be stored in a computer readable storage medium. Based on such understanding, the present application implements all or part of the flow of the method of the above embodiments, and may be implemented by a computer program to instruct related hardware, where the computer program may be stored in a computer readable storage medium, where the computer program, when executed by a processor, may implement the steps of each of the method embodiments described above. Wherein the computer program comprises computer program code which may be in source code form, object code form, executable file or some intermediate form etc. The computer readable medium may include at least: any entity or device capable of carrying computer program code to a photographing device/terminal apparatus, recording medium, computer Memory, read-Only Memory (ROM), random access Memory (RAM, random Access Memory), electrical carrier signals, telecommunications signals, and software distribution media. Such as a U-disk, removable hard disk, magnetic or optical disk, etc. In some jurisdictions, computer readable media may not be electrical carrier signals and telecommunications signals in accordance with legislation and patent practice.

In the foregoing embodiments, the descriptions of the embodiments are emphasized, and in part, not described or illustrated in any particular embodiment, reference is made to the related descriptions of other embodiments.

Those of ordinary skill in the art will appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.

In the embodiments provided in the present application, it should be understood that the disclosed apparatus/terminal device and method may be implemented in other manners. For example, the apparatus/terminal device embodiments described above are merely illustrative, e.g., the division of the modules or units is merely a logical function division, and there may be additional divisions in actual implementation, e.g., multiple units or components may be combined or integrated into another system, or some features may be omitted or not performed. Alternatively, the coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection via interfaces, devices or units, which may be in electrical, mechanical or other forms.

The units described as separate units may or may not be physically separate, and units shown as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

The above embodiments are only for illustrating the technical solution of the present application, and are not limiting; although the present application has been described in detail with reference to the foregoing embodiments, it should be understood by those of ordinary skill in the art that: the technical scheme described in the foregoing embodiments can be modified or some technical features thereof can be replaced by equivalents; such modifications and substitutions do not depart from the spirit and scope of the technical solutions of the embodiments of the present application, and are intended to be included in the scope of the present application.

Claims

1. A method of page generation, comprising:

acquiring a component template for constructing a target page and example data corresponding to the task type in the task information; wherein the example data is stored in association with the task type, one example data corresponding to each task type; the example data comprises data processing logic corresponding to the task data, and the data processing logic is used for determining the display mode of each task data in the generation of a target page;

Respectively generating view data corresponding to each task data through the task data and the example data; at least one label data exists in the view data, at least one data group data exists in each label data, and at least one data unit data exists in each data group data; each piece of label data, each piece of data group data and each piece of data unit data exist in the component template, rendering logic corresponding to the data group data is used for rendering each piece of label data, each piece of data group data and each piece of data unit data in the view data based on each piece of label data, each piece of data group data and each piece of data unit data in the view data and the rendering logic corresponding to each piece of label data, each piece of data group data and each piece of data unit data in the view data, so as to obtain a page component;

the task data includes at least one task data group;

and generating view data corresponding to each task data in the task information through the task data and the example data respectively, wherein the view data comprises:

respectively searching template data groups corresponding to the task data groups in the example data in the task data;

Generating a target data group according to the task data group and the corresponding template data group;

generating view data according to all the target data groups;

generating a page component through the view data and the component template, wherein the page component comprises:

acquiring label rendering logic corresponding to each view data based on the component template;

rendering the view data based on the tag rendering logic to obtain a tag rendering component;

packaging all the tag rendering components to obtain the page component;

and generating the target page according to all the page components.

2. The method of claim 1, further comprising, prior to the obtaining component templates for building target pages and example data corresponding to the task types within the task information:

configuring the component template for constructing a target page;

associated example data is configured for each of the task types.

3. The method of claim 1, further comprising, prior to said generating view data corresponding to each of said task data within said task information from said task data and said example data:

Judging whether the value corresponding to each data type in the example data is legal or not;

and if the judging results of all the values corresponding to the data types in the example data are legal, executing the task data and the example data to generate view data corresponding to each task data in the task information.

4. The method of claim 1, wherein the task data group comprises a group display identification and at least one task data unit; the generating the target data group according to the task data group and the corresponding template data group includes:

initializing the template data group to obtain an initialized data group;

assigning the task data group to the initialization data group, generating the target data group, including:

if the group display identification of the task data group is true, respectively searching corresponding template data units of each task data unit of the task data group in the example data; and

and generating a target data unit according to the task data unit and the template data unit.

5. The method of claim 4, wherein the task data unit includes a unit display identifier, a repeated rendering identifier, and one or more task delivery data; the generating a target data unit according to the task data unit and the template data unit includes:

Initializing the template data unit to obtain an initialized data unit;

assigning the task data unit to the initialization data unit, generating the target data unit, including:

if the unit display identification of the task data unit is true, respectively searching the template transfer data corresponding to the task transfer data of the task data unit in the template data unit; and

generating target transfer data according to the task transfer data and the template transfer data; and

and determining a sub-target data unit corresponding to the sub-task data unit of the task data unit based on the repeated rendering identification of the task data unit.

6. The method of claim 4, wherein the target data unit comprises a unit type; the generating a page component through the view data and the component template comprises the following steps:

acquiring data group rendering logic corresponding to each target data group based on the component template;

Rendering the target data group based on the data group rendering logic to obtain a data group rendering component;

acquiring data unit rendering logic corresponding to each target data unit based on the unit type of the target data unit and the component template;

rendering the target data unit based on the data unit rendering logic to obtain a data unit rendering component;

and packaging all the data unit rendering components in the data group rendering components corresponding to the data unit rendering components, packaging all the data group rendering components in the tag rendering components corresponding to the data group rendering components, and packaging all the tag rendering components to obtain the page component.

7. An apparatus for generating a page, comprising:

the template acquisition module is used for acquiring a component template for constructing a target page and example data corresponding to the task type in the task information; wherein the example data is stored in association with the task type, one example data corresponding to each task type; the example data comprises data processing logic corresponding to the task data, and the data processing logic is used for determining the display mode of each task data in the generation of a target page;

The data conversion module is used for generating view data corresponding to each task data in the task information through the task data and the example data; at least one label data exists in the view data, at least one data group data exists in each label data, and at least one data unit data exists in each data group data; each piece of label data, each piece of data group data and each piece of data unit data exist in the component template, rendering logic corresponding to the data group data is used for rendering each piece of label data, each piece of data group data and each piece of data unit data in the view data based on each piece of label data, each piece of data group data and each piece of data unit data in the view data and the rendering logic corresponding to each piece of label data, each piece of data group data and each piece of data unit data in the view data, so as to obtain a page component;

the task data includes at least one task data group;

generating view data according to all the target data groups;

the component generating module is used for generating a page component through the view data and the component template, and comprises the following steps:

packaging all the tag rendering components to obtain the page component;

8. A terminal device comprising a memory, a processor and a computer program stored in the memory and executable on the processor, characterized in that the processor implements the method according to any of claims 1 to 6 when executing the computer program.

9. A computer readable storage medium storing a computer program, characterized in that the computer program when executed by a processor implements the method according to any one of claims 1 to 6.