WO2021212636A1 - Form page generation method and device, terminal, and storage medium - Google Patents

Abstract

A form page generation method and device, a terminal, and a storage medium, relating to data processing technologies. The method comprises: creating a dictionary, the dictionary carrying a plurality of historical form names (S11); receiving control names of a plurality of form UI controls of a form to be created input by a user (S12); obtaining a plurality of form UI controls corresponding to the control names of the plurality of form UI controls from the dictionary (S13); dividing each form UI control into an interface layer and an implementation layer, wherein an isolation layer is constructed between the interface layer and the implementation layer of each form UI control (S14); splicing protocol content in the interface layer corresponding to each form UI control into an intermediate language (S15); generating a form UI control having an implementation layer on the basis of each intermediate language (S16); displaying the form UI control having the implementation layer in the implementation layer by means of the isolation layer (S17); and rendering the form UI control in the implementation layer to generate a form page (S18). According to the method, the interface layer and the implementation layer are separated by means of the technology of the form UI control, so that configuration and rendering of the control are separated, the rendering efficiency of a browser is improved, and customization requirements for various scenes are met. In addition, the method further relates to the technical field of blockchain, and the dictionary is stored in a blockchain node.

Description

Form page generation method, device, terminal and storage medium

This application claims the priority of a Chinese patent application filed with the Chinese Patent Office on April 23, 2020. The application number is 202010328627.5 and the invention title is "Method, Device, Terminal, and Storage Medium for Form Page Generation". The entire content is incorporated by reference. In this application.

Technical field

This application relates to the field of computer technology, in particular to a method, device, terminal and storage medium for generating a form page.

Background technique

The form is one of the interactive ways for users to submit information to the system. It almost takes on the information entry work of the website. With the increasing development of information construction, the diversity of data has become more obvious, and the workload of form UI development is increasing. Therefore, the form designer based on the visual operation interface not only simplifies the development of form UI development, but also reduces the development of form The threshold allows non-development business personnel to design interactive form UI and publish it to the system according to business needs, thereby reducing development costs and improving the delivery efficiency of forms.

However, the inventor found that the form designer on the market only provides a single technology stack, so that the generated form pages can only run on systems with a specific technology stack, and the generated form pages can only be published to designated third-party systems. This not only restricts the secondary development of the form to meet more customized scenarios, but also increases the difficulty of technical integration with the existing system; on the other hand, hosting the form in a third-party system is not conducive to the information security of the system. Therefore, the form page generated by this type of form designer can only solve simple form requirements and undertake simple information entry work, which is not conducive to its custom development and dynamic rendering.

Summary of the invention

In view of the above, it is necessary to propose a form page generation method, device, terminal and storage medium. By separating the technical realization of form UI controls into the interface layer and the implementation layer, the configuration and rendering of the controls are separated and the browser’s performance is improved. The rendering efficiency meets the customization needs of various scenes.

The first aspect of the present application provides a method for generating a form page, and the method includes:

Create a dictionary, where the dictionary carries multiple historical form names;

Receive the control names of multiple form UI controls of the form to be created input by the user;

Acquiring, from the dictionary, multiple form UI controls corresponding to the control names of the multiple form UI controls;

Divide each of the form UI controls into an interface layer and an implementation layer, where an architectural isolation layer is between the interface layer and the implementation layer of each of the form UI controls;

Splicing the protocol content in the interface layer corresponding to each of the form UI controls into an intermediate language;

Generating a form UI control with an implementation layer based on each of the intermediate languages;

Displaying a form UI control with an implementation layer in the implementation layer through the isolation layer;

Rendering the form UI controls in the implementation layer to generate a form page.

A second aspect of the present application provides a terminal, the terminal includes a memory and a processor, the memory is configured to store at least one computer-readable instruction, and the processor is configured to execute the at least one computer-readable instruction to implement the following step:

Create a dictionary, where the dictionary carries multiple historical form names;

Receive the control names of multiple form UI controls of the form to be created input by the user;

Acquiring, from the dictionary, multiple form UI controls corresponding to the control names of the multiple form UI controls;

Divide each of the form UI controls into an interface layer and an implementation layer, where an architectural isolation layer is between the interface layer and the implementation layer of each of the form UI controls;

Splicing the protocol content in the interface layer corresponding to each of the form UI controls into an intermediate language;

Generating a form UI control with an implementation layer based on each of the intermediate languages;

Displaying a form UI control with an implementation layer in the implementation layer through the isolation layer;

Rendering the form UI controls in the implementation layer to generate a form page.

A third aspect of the present application provides a computer-readable storage medium that stores at least one computer-readable instruction, and when the at least one computer-readable instruction is executed by a processor, the following steps are implemented:

Create a dictionary, where the dictionary carries multiple historical form names;

Receive the control names of multiple form UI controls of the form to be created input by the user;

Acquiring, from the dictionary, multiple form UI controls corresponding to the control names of the multiple form UI controls;

Divide each of the form UI controls into an interface layer and an implementation layer, where an architectural isolation layer is between the interface layer and the implementation layer of each of the form UI controls;

Splicing the protocol content in the interface layer corresponding to each of the form UI controls into an intermediate language;

Generating a form UI control with an implementation layer based on each of the intermediate languages;

Displaying a form UI control with an implementation layer in the implementation layer through the isolation layer;

Rendering the form UI controls in the implementation layer to generate a form page.

A fourth aspect of the present application provides a form page generating device, the device including:

The creation module is used to create a dictionary, where the dictionary carries multiple historical form names;

The receiving module is used to receive the control names of multiple form UI controls of the form to be created input by the user;

An obtaining module, configured to obtain multiple form UI controls corresponding to the control names of the multiple form UI controls from the dictionary;

The dividing module is used to divide each of the form UI controls into an interface layer and an implementation layer, where the interface layer and the implementation layer of each form UI control are an architectural isolation layer;

The splicing module is used to splice the protocol content in the interface layer corresponding to each of the form UI controls into an intermediate language;

A generating module for generating a form UI control with an implementation layer based on each of the intermediate languages;

A display module, configured to display a form UI control with an implementation layer in the implementation layer through the isolation layer;

The rendering module is used to render the form UI controls in the implementation layer to generate a form page.

In summary, the form page generation method, device, terminal and storage medium described in this application can be applied to the fields of smart government affairs, smart law, smart community, smart finance, smart life, etc. in the construction of smart cities to promote smart cities Construction development. This application, on the one hand, separates the configuration and rendering of the form UI control by dividing the form UI control into an interface layer and an implementation layer, thereby providing a technical foundation for custom development. It also sets up an isolation layer to make the implementation layer of each control mutually exclusive. Independent and non-interference, the purpose of different rendering results can be achieved by switching the implementation layer, and the rendering efficiency of the browser can be improved; finally, the protocol content in the interface layer corresponding to the form UI control is translated into an intermediate language, which is convenient for later use in different In the technical language of, at the same time, a form UI control with an implementation layer is generated based on the intermediate language, and any form UI control is re-developed without changing any form UI control protocol, which meets the customization requirements of various scenarios.

Description of the drawings

FIG. 1 is a flowchart of a method for generating a form page provided by Embodiment 1 of the present application.

Fig. 2 is a structural diagram of a form page generating apparatus provided in the second embodiment of the present application.

FIG. 3 is a schematic structural diagram of a terminal provided in Embodiment 3 of the present application.

Detailed ways

In order to be able to understand the above objectives, features and advantages of the application more clearly, the application will be described in detail below with reference to the accompanying drawings and specific embodiments. It should be noted that the embodiments of the application and the features in the embodiments can be combined with each other if there is no conflict.

Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by those skilled in the technical field of this application. The terms used in the specification of the application herein are only for the purpose of describing specific embodiments, and are not intended to limit the application.

Example one

FIG. 1 is a flowchart of a method for generating a form page provided by Embodiment 1 of the present application.

In this embodiment, the method for generating a form page can be applied to a terminal. For a terminal that needs to generate a form page, the function of generating the form page provided by the method of this application can be directly integrated on the terminal, or developed by software The tool kit (Software Development Kit, SKD) runs in the terminal.

As shown in FIG. 1, the method for generating a form page specifically includes the following steps. According to different requirements, the order of the steps in the flowchart can be changed, and some of the steps can be omitted.

S11: Create a dictionary, where the dictionary carries multiple historical form names.

In this embodiment, the dictionary refers to a collection of a series of protocol layers corresponding to the form UI controls of multiple historical forms. The dictionary stores the name of each historical form, the form UI control of each historical form, and the form UI. The protocol corresponding to the control and the corresponding protocol layer, wherein the protocol includes the control name, protocol content, HTMLElement tag name, attribute, method, interface layer, implementation layer and parameter list of each form UI control.

Preferably, the creating dictionary includes:

Acquire the multiple historical form names and the form UI control protocol layer corresponding to each historical form name, each of the form UI control protocol layers is composed of interface layers of multiple form UI controls corresponding to the historical form name , The interface layer of each form UI control carries a control name corresponding to the form UI control;

The multiple historical form names are taken as the first level of the dictionary, the interface layers of multiple form UI controls corresponding to each of the historical form names are taken as the second level of the dictionary, and the protocol corresponding to the interface layers of the multiple form UI controls The layer serves as the third layer of the dictionary, where the dictionary is stored in a blockchain node.

In this embodiment, each historical form name corresponds to a protocol layer, each protocol layer corresponds to the interface layers of multiple form UI controls, and each interface layer of the form UI controls corresponds to a form UI control, and each form UI control Corresponding to the control name of the form UI control, the historical form name, the form UI control corresponding to each historical punctuation name, and the protocol layer corresponding to the interface layer of the form UI control are defined as different levels, which improves the access to the form UI control efficient.

It should be emphasized that, in order to further ensure the privacy and security of the above dictionary, the above dictionary can also be stored in a node of a blockchain.

S12: Receive control names of multiple form UI controls of the form to be created input by the user.

In this embodiment, when the user needs to create a form, the form name of the form to be created and the control names of multiple form UI controls corresponding to the form name are input in the browser.

S13: Obtain multiple form UI controls corresponding to the control names of the multiple form UI controls from the dictionary.

In this embodiment, the dictionary stores the form name of each historical form and multiple form UI controls corresponding to the form name of each historical form and the control names of the form UI controls. When the form to be created input by the user is received When the control names of multiple form UI controls are used, the form UI control corresponding to the control name of each form UI control is obtained from the dictionary.

S14: Divide each form UI control into an interface layer and an implementation layer, where an isolation layer is structured between the interface layer and the implementation layer of each form UI control.

In this embodiment, the interface layer refers to the definition of the attributes and behaviors of the form UI control, that is, the internal operation of the form UI control and the external environment are independent of each other in the data processing process, for example, to modify the form UI The internal operation of the control will not affect the external environment of the form UI control; the implementation layer refers to the implementation of the protocol content defined by the interface layer of the form UI control to implement internal operations, in order to prevent the implementation layer from Internal details pollute the global environment, and an isolation layer is constructed between the implementation layer and the interface layer.

Preferably, the dividing each of the form UI controls into an interface layer and an implementation layer includes:

Creating each of the form UI controls as a custom label that can be natively recognized by the browser;

Call CustomElements.define to pass in the custom label to divide each form UI control into an interface layer and an implementation layer.

In this embodiment, by using the Custom Elements technology in Web Components technology, the form UI control is created as HTMLElement (custom) tags that can be natively recognized by the browser, and the customElements.define method is called to pass in the HTMLElement tags and JavaScript Class is used. Implement the practical layer obtained from the interface layer corresponding to each form UI control, thereby dividing each form UI control into an interface layer and an implementation layer. After dividing the form UI control into an interface layer and an implementation layer, the Shadow DOM technology is used An isolation layer is constructed between the interface layer and the implementation layer of each of the form UI controls.

In this embodiment, each control is divided into an interface layer and an implementation layer to separate configuration and rendering. The configuration is implemented through the interface layer, and the rendering is implemented through the implementation layer, which improves the rendering. Efficiency, the architecture isolation layer is due to the fact that the default operating environment provided by the browser is not isolated. The internal details of the implementation layer can easily pollute the global environment, causing other UI controls to be interfered and unable to work normally. The architecture isolation layer between the interface layers improves the rendering quality.

S15: Splice the protocol content in the interface layer corresponding to each of the form UI controls into an intermediate language.

In this embodiment, the protocol content in the interface layer corresponding to the form UI control is not conducive to storage and transmission in the form of code. In order to facilitate storage and transmission, the interface corresponding to each form UI control will be The content of the agreement in the layer is spliced into an intermediate language.

Preferably, the splicing the protocol content in the interface layer corresponding to each of the form UI controls into an intermediate language includes:

Receive the form UI controls dragged by the user in the form canvas;

Read the form UI controls in the form canvas according to the drag order of the user;

Each time a form UI control is read, the protocol content in the interface layer corresponding to the form UI control is spliced into an intermediate language.

Exemplarily, the user drags the form UI control list "I", "Ping", and "From" to the form canvas, and reads each form UI control according to the drag order of the user, and reads the interface corresponding to the first form UI control. The protocol content of the layer is "I", the protocol content of the interface layer corresponding to the second form UI control is read as "from", and the protocol content of the interface layer corresponding to the third form UI control is read as "Peace" , Splicing the protocol content in the interface layer corresponding to each of the form UI controls into the intermediate language "I come from Ping An" in the order of reading.

S16: Generate a form UI control with an implementation layer based on each of the intermediate languages.

In this embodiment, in the process of generating a form UI control with an implementation layer, each protocol layer corresponds to multiple implementation layers. In order to achieve the purpose of customization, a translator, a configuration center, and a registry are designed. The translator, The configuration center and the registry work together in the translation layer.

Preferably, the generating a form UI control with an implementation layer based on each of the intermediate languages includes:

Input each of the intermediate languages into the translator;

Calling the translator to request the dictionary corresponding to the intermediate language from the configuration center and setting the dictionary to an active state;

Calling the configuration center to read the form UI control corresponding to the dictionary in the active state from the registry;

Return the form UI control to the translator;

Calling the translator to read the control information of the corresponding form UI control from each of the intermediate languages according to the form UI control, wherein the control information of the form UI control corresponds to the control name;

Based on the control name of the form UI control, the first form UI control read from each intermediate language is matched with the second form UI control read from the registry by the configuration center, where , The first form UI control read from each of the intermediate languages corresponds to an interface layer, and the second form UI control read from the registry by the configuration center corresponds to an implementation Floor;

Associating the matching interface layer of the first form UI control and the implementation layer of the second form UI control to obtain a form UI control list corresponding to the interface layer and the implementation layer;

Invoking the translator to read each second form UI control in the form UI control list to generate a form UI control with an implementation layer.

In this embodiment, in order to generate a form UI control with an implementation layer for each intermediate language, the intermediate language is input to the translator, and the translator requests the corresponding dictionary in the configuration center according to the intermediate language, and in the configuration center Set the dictionary to the active state, then find the form UI control corresponding to the active state dictionary from the registry, return the form UI control to the translator, and the translator reads the corresponding data from each intermediate language. The first form UI control, the first form UI control read from the intermediate language only corresponds to an interface layer, and the second form UI control read from the registry by the configuration center only Corresponding to an implementation layer, the first form UI control is matched with the second form UI control, and the matched first form UI control is associated with the second form UI control to obtain a carrying The interface layer and the form UI control list of the implementation layer are called, the translator is called to read each first form UI control in the list one by one, and the corresponding first form UI control is obtained through the interface layer of each first form UI control. Second, the realization layer of the form UI control. Finally, the translator completes the generation of the form UI control with the realization layer from the intermediate language.

Exemplarily, input the intermediate language: "I come from Ping An" into the translator, call the translator to request the dictionary corresponding to the intermediate language from the configuration center and set it to the active state, and call the configuration The center reads the control name of the form UI control corresponding to the dictionary from the registration table: "I", "From" and "Ping An", returning "I", "From" and "Ping An" to the translator, and calling the translator according to "I", "From" and "Ping An" read the first form UI control "I", "From" and "Ping An" from the intermediate language. The configuration center reads the second form from the registry. Form UI controls "I", "come from", "PingAn", match the first form UI control with the second form UI control to obtain the correspondence between "I" and "I", and "from" and "come" The form UI control list corresponding to "from", "Ping An" and "PingAn" is called, and the translator is called to read the second form UI controls "I", "come from", and "PingAn" to generate an English implementation layer Form controls, for example: the form control with English implementation level corresponding to the intermediate language "I" is "I", and the form control with English implementation level corresponding to the intermediate language "from" is "come here", the The form control with English implementation layer corresponding to the intermediate language "Ping An" is "PingAn".

In this embodiment, the translation layer generates a form UI control with an implementation layer based on the intermediate language. The form UI control contains specific style codes and interactive logic codes. The secondary development of the form UI controls can also be implemented for each of the form UI controls to switch between different implementation layers, which meets the needs of various customized scenarios, promotes the development of smart city construction, and can be applied to the wisdom of smart city construction. Government affairs, smart law, smart community, smart finance, smart life and other fields.

S17: Display a form UI control with an implementation layer in the implementation layer through the isolation layer.

In this embodiment, a form UI control protocol layer includes multiple form UI controls, each form UI control corresponds to multiple implementation layers, and each implementation layer is independently presented in the isolation layer.

Preferably, the presenting the form UI control with the realization layer in the realization layer through the isolation layer includes:

Acquiring multiple rendering versions corresponding to the form UI control with an implementation layer;

Registering the multiple rendering versions in the registry, and modifying the status of the multiple rendering versions to a suspended state;

Determining that a rendering version in the registry is a target rendering version, and configuring the target rendering version to the configuration center;

Modifying the status of the target rendering version in the configuration center to an active status;

The translator obtains the implementation layer information of the rendering version corresponding to the activated state from the configuration center;

The realization layer of the form UI control corresponding to the realization layer information is displayed in the realization layer.

In this embodiment, each form UI control corresponds to multiple implementation layers, and each implementation layer corresponds to a rendering version, obtain multiple rendering versions corresponding to the form UI control with implementation layers, and register the multiple rendering versions Go to the registry and set the status to the suspended state; set the specified rendering version status to the active state in the configuration center, so that the "translator" will obtain the implementation of the only active rendering version from the "configuration center" Tier information.

In this embodiment, the registry, the configuration center, and the translator work together in the translation layer, and are cooperatively responsible for dynamically maintaining the relationship between the different implementation layers of each form UI control, and realize the switching of different implementation layers. Since the isolation layer is constructed between the interface layer and the implementation layer of each form UI control, the implementation layer of each form UI control is independent of each other and does not interfere with each other, avoiding the default operating environment provided by the browser Without isolation, the internal details of the implementation layer can easily pollute the global environment, causing other UI controls to be interfered and unable to work normally.

S18: Render the form UI control in the implementation layer to generate a form page.

In this embodiment, the form page is generated by rendering the form UI controls in the implementation layer into different rendering pieces and then connecting them.

Preferably, the rendering of the form UI control in the implementation layer to generate the form page includes:

Rendering the form UI control in the implementation layer to obtain a rendering piece of the form UI control;

Based on the rendering pieces, a rendering image of the entire form page is formed together;

A form page is generated based on the rendering image.

In this embodiment, the isolation layer wraps each form UI control into an independent rendering piece, and each rendering piece can be independently and dynamically rendered under certain conditions without affecting other rendering pieces, achieving different rendering results, and improving the browser’s performance. Rendering efficiency reduces the cost of rendering the entire form page.

In summary, the method for generating a form page according to this embodiment receives the control names of multiple form UI controls of the form to be created that are input by the user after creating a dictionary; and obtains the multiple form UI controls from the dictionary Multiple form UI controls corresponding to the control name of the form; divide each of the form UI controls into an interface layer and an implementation layer, wherein the interface layer and the implementation layer of each form UI control have an architectural isolation layer between the interface layer and the implementation layer; The protocol content in the interface layer corresponding to each of the form UI controls is spliced into an intermediate language; a form UI control with an implementation layer is generated based on each intermediate language; the implementation layer is displayed in the implementation layer through the isolation layer Form UI controls; render the form UI controls in the implementation layer to generate a form page. This embodiment, on the one hand, separates the configuration and rendering of the form UI control by dividing the form UI control into an interface layer and an implementation layer, thereby providing a technical basis for custom development, and setting up an isolation layer to make the implementation layer of each control They are independent of each other and do not interfere with each other. The purpose of different rendering results is achieved by switching the realization layer, and the rendering efficiency of the browser is improved; finally, the protocol content in the interface layer corresponding to the form UI control is translated into an intermediate language, which is convenient for later use Among different technical languages, form UI controls with implementation layers are generated based on the intermediate language at the same time, and any form UI controls are re-developed without changing the protocol of any form UI controls, which meets the customization needs of various scenarios .

Example two

Fig. 2 is a structural diagram of a form page generating apparatus provided in the second embodiment of the present application.

In some embodiments, the form page generating device 20 may include multiple functional modules composed of program code segments. The program code of each program segment in the form page generating device 20 may be stored in the memory of the terminal and executed by the at least one processor to perform (see FIG. 1 for details) form page generation.

In this embodiment, the form page generating device 20 can be divided into multiple functional modules according to the functions it performs. The functional modules may include: a creation module 201, a receiving module 202, an acquisition module 203, a division module 204, a splicing module 205, a generation module 206, a display module 207, and a rendering module 208. The module referred to in this application refers to a series of computer program segments that can be executed by at least one processor and can complete fixed functions, and are stored in a memory. In this embodiment, the function of each module will be described in detail in subsequent embodiments.

Creation module 201: used to create a dictionary, where the dictionary carries multiple historical form names.

In this embodiment, the dictionary refers to a collection of a series of protocol layers corresponding to the form UI controls of multiple historical forms. The dictionary stores the name of each historical form, the form UI control of each historical form, and the form UI. The protocol corresponding to the control and the corresponding protocol layer, wherein the protocol includes the control name, protocol content, HTMLElement tag name, attribute, method, interface layer, implementation layer and parameter list of each form UI control.

Preferably, the creation of the dictionary by the creation module 201 includes:

Acquire the multiple historical form names and the form UI control protocol layer corresponding to each historical form name, each of the form UI control protocol layers is composed of interface layers of multiple form UI controls corresponding to the historical form name , The interface layer of each form UI control carries a control name corresponding to the form UI control;

The multiple historical form names are taken as the first level of the dictionary, the interface layers of multiple form UI controls corresponding to each of the historical form names are taken as the second level of the dictionary, and the protocol corresponding to the interface layers of the multiple form UI controls The layer serves as the third layer of the dictionary, where the dictionary is stored in a blockchain node.

In this embodiment, each historical form name corresponds to a protocol layer, each protocol layer corresponds to the interface layers of multiple form UI controls, and each interface layer of the form UI controls corresponds to a form UI control, and each form UI control Corresponding to the control name of the form UI control, the historical form name, the form UI control corresponding to each historical punctuation name, and the protocol layer corresponding to the interface layer of the form UI control are defined as different levels, which improves the access to the form UI control efficient.

It should be emphasized that, in order to further ensure the privacy and security of the above-mentioned dictionary, the above-mentioned dictionary can also be stored in a node of a blockchain.

Receiving module 202: used to receive control names of multiple form UI controls of the form to be created input by the user.

In this embodiment, when the user needs to create a form, the form name of the form to be created and the control names of multiple form UI controls corresponding to the form name are input in the browser.

The obtaining module 203 is configured to obtain multiple form UI controls corresponding to the control names of the multiple form UI controls from the dictionary.

In this embodiment, the dictionary stores the form name of each historical form and multiple form UI controls corresponding to the form name of each historical form and the control names of the form UI controls. When the form to be created input by the user is received When the control names of multiple form UI controls are used, the form UI control corresponding to the control name of each form UI control is obtained from the dictionary.

The dividing module 204 is configured to divide each of the form UI controls into an interface layer and an implementation layer, where the interface layer and the implementation layer of each form UI control are structured as an isolation layer.

In this embodiment, the interface layer refers to the definition of the attributes and behaviors of the form UI control, that is, the internal operation of the form UI control and the external environment are independent of each other in the data processing process, for example, to modify the form UI The internal operation of the control will not affect the external environment of the form UI control; the implementation layer refers to the implementation of the protocol content defined by the interface layer of the form UI control to implement internal operations, in order to prevent the implementation layer from Internal details pollute the global environment, and an isolation layer is constructed between the implementation layer and the interface layer.

Preferably, the dividing module 204 dividing each of the form UI controls into an interface layer and an implementation layer includes:

Creating each of the form UI controls as a custom label that can be natively recognized by the browser;

Call CustomElements.define to pass in the custom label to divide each form UI control into an interface layer and an implementation layer.

In this embodiment, by using the Custom Elements technology in Web Components technology, the form UI control is created as HTMLElement (custom) tags that can be natively recognized by the browser, and the customElements.define method is called to pass in the HTMLElement tags and JavaScript Class is used. Implement the practical layer obtained from the interface layer corresponding to each form UI control, thereby dividing each form UI control into an interface layer and an implementation layer. After dividing the form UI control into an interface layer and an implementation layer, the Shadow DOM technology is used An isolation layer is constructed between the interface layer and the implementation layer of each of the form UI controls.

In this embodiment, each control is divided into an interface layer and an implementation layer to separate configuration and rendering. The configuration is implemented through the interface layer, and the rendering is implemented through the implementation layer, which improves the rendering. Efficiency, the architecture isolation layer is due to the fact that the default operating environment provided by the browser is not isolated. The internal details of the implementation layer can easily pollute the global environment, causing other UI controls to be interfered and unable to work normally. The architecture isolation layer between the interface layers improves the rendering quality.

The splicing module 205 is used to splice the protocol content in the interface layer corresponding to each of the form UI controls into an intermediate language.

In this embodiment, the protocol content in the interface layer corresponding to the form UI control is not conducive to storage and transmission in the form of code. In order to facilitate storage and transmission, the interface corresponding to each form UI control will be The content of the agreement in the layer is spliced into an intermediate language.

Preferably, the splicing module 205 splicing the protocol content in the interface layer corresponding to each of the form UI controls into an intermediate language includes:

Receive the form UI controls dragged by the user in the form canvas;

Read the form UI controls in the form canvas according to the drag order of the user;

Each time a form UI control is read, the protocol content in the interface layer corresponding to the form UI control is spliced into an intermediate language.

Exemplarily, the user drags the form UI control list "I", "Ping", and "From" to the form canvas, and reads each form UI control according to the drag order of the user, and reads the interface corresponding to the first form UI control. The protocol content of the layer is "I", the protocol content of the interface layer corresponding to the second form UI control is read as "from", and the protocol content of the interface layer corresponding to the third form UI control is read as "Peace" , Splicing the protocol content in the interface layer corresponding to each of the form UI controls into the intermediate language "I come from Ping An" in the order of reading.

The generating module 206 is configured to generate a form UI control with an implementation layer based on each intermediate language.

In this embodiment, in the process of generating a form UI control with an implementation layer, each protocol layer corresponds to multiple implementation layers. In order to achieve the purpose of customization, a translator, a configuration center, and a registry are designed. The translator, The configuration center and the registry work together in the translation layer.

Preferably, the generation module 206 generates a form UI control with an implementation layer based on each of the intermediate language includes:

Input each of the intermediate languages into the translator;

Calling the translator to request the dictionary corresponding to the intermediate language from the configuration center and setting the dictionary to an active state;

Calling the configuration center to read the form UI control corresponding to the dictionary in the active state from the registry;

Return the form UI control to the translator;

Calling the translator to read the control information of the corresponding form UI control from each of the intermediate languages according to the form UI control, wherein the control information of the form UI control corresponds to the control name;

Based on the control name of the form UI control, the first form UI control read from each intermediate language is matched with the second form UI control read from the registry by the configuration center, where , The first form UI control read from each of the intermediate languages corresponds to an interface layer, and the second form UI control read from the registry by the configuration center corresponds to an implementation Floor;

Associating the matching interface layer of the first form UI control and the implementation layer of the second form UI control to obtain a form UI control list corresponding to the interface layer and the implementation layer;

Invoking the translator to read each second form UI control in the form UI control list to generate a form UI control with an implementation layer.

In this embodiment, in order to generate a form UI control with an implementation layer for each intermediate language, the intermediate language is input to the translator, and the translator requests the corresponding dictionary in the configuration center according to the intermediate language, and in the configuration center Set the dictionary to the active state, then find the form UI control corresponding to the active state dictionary from the registry, return the form UI control to the translator, and the translator reads the corresponding data from each intermediate language. The first form UI control, the first form UI control read from the intermediate language only corresponds to an interface layer, and the second form UI control read from the registry by the configuration center only Corresponding to an implementation layer, the first form UI control is matched with the second form UI control, and the matched first form UI control is associated with the second form UI control to obtain a carrying The interface layer and the form UI control list of the implementation layer are called, the translator is called to read each first form UI control in the list one by one, and the corresponding first form UI control is obtained through the interface layer of each first form UI control. Second, the realization layer of the form UI control. Finally, the translator completes the generation of the form UI control with the realization layer from the intermediate language.

Exemplarily, input the intermediate language: "I come from Ping An" into the translator, call the translator to request the dictionary corresponding to the intermediate language from the configuration center and set it to the active state, and call the configuration The center reads the control name of the form UI control corresponding to the dictionary from the registry: "I", "From" and "Ping An", returning "I", "From" and "Ping An" to the translator, and calling the translator to read Take the first form UI control "I", "From" and "Ping An" read from the intermediate language according to "I", "From" and "Ping An", the configuration center reads from the registry The second form UI control is generated: "I", "come from", "PingAn", the first form UI control is matched with the second form UI control to obtain the correspondence between "I" and "I", , "From" corresponds to "come from", "PingAn" and "PingAn" correspond to the form UI control list, call the translator to read the second form UI control "I", "come from", " "PingAn" generates a form control with an English implementation level, for example: the form control with an English implementation level corresponding to the intermediate language "I" is "I", and the intermediate language "from" corresponds to a form control with an English implementation level. Is "come here", and the form control with English implementation layer corresponding to the intermediate language "Ping An" is "PingAn".

In this embodiment, the translation layer generates a form UI control with an implementation layer based on the intermediate language. The form UI control contains specific style codes and interactive logic codes. The secondary development of the form UI control can also be performed for each of the form UI controls to switch between different implementation layers, which meets the requirements of various customization scenarios.

The display module 207 is used to display the form UI control with the realization layer in the realization layer through the isolation layer.

In this embodiment, a form UI control protocol layer includes multiple form UI controls, each form UI control corresponds to multiple implementation layers, and each implementation layer is independently presented in the isolation layer.

Preferably, the display module 207 displays the form UI control with the realization layer in the realization layer through the isolation layer, including:

Acquiring multiple rendering versions corresponding to the form UI control with an implementation layer;

Registering the multiple rendering versions in the registry, and modifying the status of the multiple rendering versions to a suspended state;

Determining that a rendering version in the registry is a target rendering version, and configuring the target rendering version to the configuration center;

Modifying the status of the target rendering version in the configuration center to an active status;

The translator obtains the implementation layer information of the rendering version corresponding to the activated state from the configuration center;

The realization layer of the form UI control corresponding to the realization layer information is displayed in the realization layer.

In this embodiment, each form UI control corresponds to multiple implementation layers, and each implementation layer corresponds to a rendering version, obtain multiple rendering versions corresponding to the form UI control with implementation layers, and register the multiple rendering versions Go to the registry and set the status to the suspended state; set the specified rendering version status to the active state in the configuration center, so that the "translator" will obtain the implementation of the only active rendering version from the "configuration center" Tier information.

In this embodiment, the registry, the configuration center, and the translator work together in the translation layer, and are cooperatively responsible for dynamically maintaining the relationship between the different implementation layers of each form UI control, and realize the switching of different implementation layers. Since the isolation layer is constructed between the interface layer and the implementation layer of each form UI control, the implementation layer of each form UI control is independent of each other and does not interfere with each other, avoiding the default operating environment provided by the browser Without isolation, the internal details of the implementation layer can easily pollute the global environment, causing other UI controls to be interfered and unable to work normally.

The rendering module 208 is used to render the form UI controls in the implementation layer to generate a form page.

In this embodiment, the form page is generated by rendering the form UI controls in the implementation layer into different rendering pieces and then connecting them.

Preferably, the rendering module 208 renders the form UI controls in the implementation layer, and generating a form page includes:

Rendering the form UI control in the implementation layer to obtain a rendering piece of the form UI control;

Based on the rendering pieces, a rendering image of the entire form page is formed together;

A form page is generated based on the rendering image.

In this embodiment, the isolation layer wraps each form UI control into an independent rendering piece, and each rendering piece can be independently and dynamically rendered under certain conditions without affecting other rendering pieces, achieving different rendering results, and improving the browser’s performance. Rendering efficiency reduces the cost of rendering the entire form page.

To sum up, the form page generating device of this embodiment receives the control names of multiple form UI controls of the form to be created input by the user after creating a dictionary; obtains the multiple form UI controls from the dictionary Multiple form UI controls corresponding to the control name of the form; divide each of the form UI controls into an interface layer and an implementation layer, wherein the interface layer and the implementation layer of each form UI control have an architectural isolation layer between the interface layer and the implementation layer; The protocol content in the interface layer corresponding to each of the form UI controls is spliced into an intermediate language; a form UI control with an implementation layer is generated based on each intermediate language; the implementation layer is displayed in the implementation layer through the isolation layer Form UI controls; render the form UI controls in the implementation layer to generate a form page. This embodiment, on the one hand, separates the configuration and rendering of the form UI control by dividing the form UI control into an interface layer and an implementation layer, thereby providing a technical basis for custom development, and setting up an isolation layer to make the implementation layer of each control They are independent of each other and do not interfere with each other. The purpose of different rendering results is achieved by switching the realization layer, and the rendering efficiency of the browser is improved; finally, the protocol content in the interface layer corresponding to the form UI control is translated into an intermediate language, which is convenient for later use Among different technical languages, form UI controls with implementation layers are generated based on the intermediate language at the same time, and any form UI controls are re-developed without changing the protocol of any form UI controls, which meets the customization needs of various scenarios .

Example three

Refer to FIG. 3, which is a schematic structural diagram of a terminal provided in Embodiment 3 of this application. In a preferred embodiment of the present application, the terminal 3 includes a memory 31, at least one processor 32, at least one communication bus 33, and a transceiver 34.

Those skilled in the art should understand that the structure of the terminal shown in FIG. 3 does not constitute a limitation of the embodiment of the present application. It may be a bus-type structure or a star structure. The terminal 3 may also include more More or less other hardware or software, or different component arrangements.

In some embodiments, the terminal 3 is a terminal that can automatically perform numerical calculation and/or information processing in accordance with pre-set or stored instructions. Its hardware includes, but is not limited to, a microprocessor, an application specific integrated circuit, and Programming gate arrays, digital processors and embedded devices, etc. The terminal 3 may also include client equipment. The client equipment includes, but is not limited to, any electronic product that can interact with the client through a keyboard, a mouse, a remote control, a touch panel, or a voice control device, for example, a personal computer. Computers, tablets, smart phones, digital cameras, etc.

It should be noted that the terminal 3 is only an example, and other existing or future electronic products that can be adapted to this application should also be included in the scope of protection of this application and included here by reference.

In some embodiments, the memory 31 is used to store program codes and various data, such as the form page generating device 20 installed in the terminal 3, and realize the high-speed and automatic completion of the program during the operation of the terminal 3 Or data access. The memory 31 includes random access memory (Ramdom Access Memory, RAM), read-only memory (Read-Only Memory, ROM), programmable read-only memory (Programmable Read-Only Memory, PROM), and erasable programmable read-only memory (Erasable Programmable Read-Only Memory, EPROM), One-time Programmable Read-Only Memory (OTPROM), Electronically-Erasable Programmable Read-Only Memory, EEPROM ), CD-ROM (Compact Disc Read-Only Memory) or other optical disk storage, magnetic disk storage, tape storage, or any other computer-readable medium that can be used to carry or store data.

In some embodiments, the at least one processor 32 may be composed of integrated circuits, for example, may be composed of a single packaged integrated circuit, or may be composed of multiple integrated circuits with the same function or different functions, including one Or a combination of multiple central processing units (CPU), microprocessors, digital processing chips, graphics processors, and various control chips. The at least one processor 32 is the control core (Control Unit) of the terminal 3. Various interfaces and lines are used to connect the various components of the entire terminal 3, and by running or executing programs or modules stored in the memory 31, And call the data stored in the memory 31 to execute various functions of the terminal 3 and process data.

In some embodiments, the at least one communication bus 33 is configured to implement connection and communication between the memory 31 and the at least one processor 32 and the like.

Although not shown, the terminal 3 may also include a power source (such as a battery) for supplying power to various components. Preferably, the power source may be logically connected to the at least one processor 32 through a power management device, so as to realize management through the power management device. Functions such as charging, discharging, and power management. The power supply may also include any components such as one or more DC or AC power supplies, recharging devices, power failure detection circuits, power converters or inverters, and power status indicators. The terminal 3 may also include various sensors, Bluetooth modules, Wi-Fi modules, etc., which will not be repeated here.

It should be understood that the embodiments are only for illustrative purposes, and are not limited by this structure in the scope of the patent application.

The above-mentioned integrated unit implemented in the form of a software function module may be stored in a computer readable storage medium. The above-mentioned software function module is stored in a storage medium and includes several instructions to make a computer device (which may be a personal computer, a terminal, or a network device, etc.) or a processor execute the method described in each embodiment of the present application. part.

In a further embodiment, with reference to FIG. 2 (device module), the at least one processor 32 can execute the operating device of the terminal 3 and various installed applications (such as the form page generating device 20), Program code, etc., for example, the above-mentioned modules.

The memory 31 stores program codes, and the at least one processor 32 can call the program codes stored in the memory 31 to perform related functions. For example, the various modules described in FIG. 2 are program codes stored in the memory 31 and executed by the at least one processor 32, so as to realize the functions of the various modules to achieve the purpose of generating a form page.

In an embodiment of the present application, the memory 31 stores a plurality of instructions, and the plurality of instructions are executed by the at least one processor 32 to realize the generation of a form page.

Specifically, for the specific implementation method of the at least one processor 32 on the foregoing instructions, reference may be made to the description of the relevant steps in the embodiment corresponding to FIG. 1, which will not be repeated here.

In the several embodiments provided in this application, it should be understood that the disclosed device and method may be implemented in other ways. For example, the device embodiments described above are merely illustrative. For example, the division of the modules is only a logical function division, and there may be other division methods in actual implementation.

Further, the computer-readable storage medium may be non-volatile or volatile.

Further, the computer-readable storage medium may mainly include a storage program area and a storage data area, where the storage program area may store an operating system, an application program required by at least one function, etc.; the storage data area may store Data created by the use of nodes, etc.

The blockchain referred to in this application is a new application mode of computer technology such as distributed data storage, point-to-point transmission, consensus mechanism, and encryption algorithm. Blockchain, essentially a decentralized database, is a series of data blocks associated with cryptographic methods. Each data block contains a batch of network transaction information for verification. The validity of the information (anti-counterfeiting) and the generation of the next block. The blockchain can include the underlying platform of the blockchain, the platform product service layer, and the application service layer.

The modules described as separate components may or may not be physically separated, and the components displayed as modules may or may not be physical units, that is, they may be located in one place, or they may be distributed on multiple network units. Some or all of the modules can be selected according to actual needs to achieve the objectives of the solutions of the embodiments.

In addition, the functional modules in the various embodiments of the present application may be integrated into one processing unit, or each unit may exist alone physically, or two or more units may be integrated into one unit. The above-mentioned integrated unit may be implemented in the form of hardware, or may be implemented in the form of hardware plus software functional modules.

For those skilled in the art, it is obvious that the present application is not limited to the details of the foregoing exemplary embodiments, and the present application can be implemented in other specific forms without departing from the spirit or basic characteristics of the application. Therefore, no matter from which point of view, the embodiments should be regarded as exemplary and non-limiting. The scope of this application is defined by the appended claims rather than the above description, and therefore it is intended to fall into the claims. All changes in the meaning and scope of the equivalent elements of are included in this application. Any reference signs in the claims should not be regarded as limiting the claims involved. In addition, it is obvious that the word "including" does not exclude other elements or the singular number does not exclude the plural number. Multiple units or devices stated in the device claims can also be implemented by one unit or device through software or hardware. Words such as first and second are used to denote names, but do not denote any specific order.

Claims (20)

1. A method for generating a form page, wherein the method for generating a form page includes:

   Create a dictionary, where the dictionary carries multiple historical form names;

   Receive the control names of multiple form UI controls of the form to be created input by the user;

   Acquiring, from the dictionary, multiple form UI controls corresponding to the control names of the multiple form UI controls;

   Divide each of the form UI controls into an interface layer and an implementation layer, where an architectural isolation layer is between the interface layer and the implementation layer of each of the form UI controls;

   Splicing the protocol content in the interface layer corresponding to each of the form UI controls into an intermediate language;

   Generating a form UI control with an implementation layer based on each of the intermediate languages;

   Displaying a form UI control with an implementation layer in the implementation layer through the isolation layer;

   Rendering the form UI controls in the implementation layer to generate a form page.
2. The method for generating a form page according to claim 1, wherein said generating a form UI control with an implementation layer based on each of said intermediate language comprises:

   Input each of the intermediate languages into the translator;

   Calling the translator to request the dictionary corresponding to the intermediate language from the configuration center, and setting the dictionary to an active state;

   Calling the configuration center to read the form UI control corresponding to the dictionary in the active state from the registry;

   Return the form UI control to the translator;

   Calling the translator to read the control information of the corresponding form UI control from each of the intermediate languages according to the form UI control, wherein the control information of the form UI control corresponds to the control name;

   Based on the control name of the form UI control, the first form UI control read from each intermediate language is matched with the second form UI control read from the registry by the configuration center, where , The first form UI control read from each of the intermediate languages corresponds to an interface layer, and the second form UI control read from the registry by the configuration center corresponds to an implementation Floor;

   Associating the matching interface layer of the first form UI control and the implementation layer of the second form UI control to obtain a form UI control list corresponding to the interface layer and the implementation layer;

   Invoking the translator to read each second form UI control in the form UI control list to generate a form UI control with an implementation layer.
3. 8. The method for generating a form page according to claim 1, wherein the splicing protocol content in the interface layer corresponding to each of the form UI controls into an intermediate language comprises:

   Receive the form UI controls dragged by the user in the form canvas;

   Read the form UI controls in the form canvas according to the drag order of the user;

   Each time a form UI control is read, the protocol content in the interface layer corresponding to the form UI control is spliced into an intermediate language.
4. The method for generating a form page according to claim 1, wherein the presenting the form UI control with the realization layer in the realization layer through the isolation layer comprises:

   Acquiring multiple rendering versions corresponding to the form UI control with an implementation layer;

   Registering the multiple rendering versions in the registry, and modifying the status of the multiple rendering versions to a suspended state;

   Determining that a rendering version in the registry is a target rendering version, and configuring the target rendering version to the configuration center;

   Modifying the status of the target rendering version in the configuration center to an active status;

   The translator obtains the implementation layer information of the rendering version corresponding to the activated state from the configuration center;

   The realization layer of the form UI control corresponding to the realization layer information is displayed in the realization layer.
5. The method for generating a form page according to claim 1, wherein said rendering the form UI control in the realization layer to generate the form page comprises:

   Rendering the form UI control in the implementation layer to obtain a rendering piece of the form UI control;

   Based on the rendering pieces, a rendering image of the entire form page is formed together;

   A form page is generated based on the rendering image.
6. The method for generating a form page according to claim 1, wherein said creating a dictionary comprises:

   Acquire the multiple historical form names and the form UI control protocol layer corresponding to each historical form name, each of the form UI control protocol layers is composed of interface layers of multiple form UI controls corresponding to the historical form name , The interface layer of each form UI control carries a control name corresponding to the form UI control;

   The multiple historical form names are taken as the first level of the dictionary, the interface layers of multiple form UI controls corresponding to each of the historical form names are taken as the second level of the dictionary, and the protocol corresponding to the interface layers of the multiple form UI controls The layer serves as the third layer of the dictionary, where the dictionary is stored in a blockchain node.
7. The method for generating a form page according to claim 1, wherein the dividing each of the form UI controls into an interface layer and an implementation layer comprises:

   Creating each of the form UI controls as a custom label that can be natively recognized by the browser;

   Call CustomElements.define to pass in the custom label to divide each form UI control into an interface layer and an implementation layer.
8. A terminal, wherein the terminal includes a memory and a processor, the memory is configured to store at least one computer-readable instruction, and the processor is configured to execute the at least one computer-readable instruction to implement the following steps:

   Create a dictionary, where the dictionary carries multiple historical form names;

   Receive the control names of multiple form UI controls of the form to be created input by the user;

   Acquiring, from the dictionary, multiple form UI controls corresponding to the control names of the multiple form UI controls;

   Divide each of the form UI controls into an interface layer and an implementation layer, where an architectural isolation layer is between the interface layer and the implementation layer of each of the form UI controls;

   Splicing the protocol content in the interface layer corresponding to each of the form UI controls into an intermediate language;

   Generating a form UI control with an implementation layer based on each of the intermediate languages;

   Displaying a form UI control with an implementation layer in the implementation layer through the isolation layer;

   Rendering the form UI controls in the implementation layer to generate a form page.
9. The terminal according to claim 8, wherein when the processor executes the at least one computer-readable instruction to implement the generation of a form UI control with an implementation layer based on each of the intermediate languages, the specific steps include:

   Input each of the intermediate languages into the translator;

   Calling the translator to request the dictionary corresponding to the intermediate language from the configuration center, and setting the dictionary to an active state;

   Calling the configuration center to read the form UI control corresponding to the dictionary in the active state from the registry;

   Return the form UI control to the translator;

   Calling the translator to read the control information of the corresponding form UI control from each of the intermediate languages according to the form UI control, wherein the control information of the form UI control corresponds to the control name;

   Based on the control name of the form UI control, the first form UI control read from each intermediate language is matched with the second form UI control read from the registry by the configuration center, where , The first form UI control read from each of the intermediate languages corresponds to an interface layer, and the second form UI control read from the registry by the configuration center corresponds to an implementation Floor;

   Associating the matching interface layer of the first form UI control and the implementation layer of the second form UI control to obtain a form UI control list corresponding to the interface layer and the implementation layer;

   Invoking the translator to read each second form UI control in the form UI control list to generate a form UI control with an implementation layer.
10. The terminal according to claim 8, wherein the processor executes the at least one computer-readable instruction to realize the splicing of protocol content in the interface layer corresponding to each of the form UI controls into an intermediate language, Specifically:

    Receive the form UI controls dragged by the user in the form canvas;

    Read the form UI controls in the form canvas according to the drag order of the user;

    Each time a form UI control is read, the protocol content in the interface layer corresponding to the form UI control is spliced into an intermediate language.
11. The terminal according to claim 8, wherein the processor executes the at least one computer-readable instruction to realize the display of the form UI control with the realization layer in the realization layer through the isolation layer, specifically include:

    Acquiring multiple rendering versions corresponding to the form UI control with an implementation layer;

    Registering the multiple rendering versions in the registry, and modifying the status of the multiple rendering versions to a suspended state;

    Determining that a rendering version in the registry is a target rendering version, and configuring the target rendering version to the configuration center;

    Modifying the status of the target rendering version in the configuration center to an active status;

    The translator obtains the implementation layer information of the rendering version corresponding to the activated state from the configuration center;

    The realization layer of the form UI control corresponding to the realization layer information is displayed in the realization layer.
12. The terminal according to claim 8, wherein the processor executes the at least one computer-readable instruction to implement the rendering of the form UI control in the implementation layer, and when the form page is generated, it specifically includes:

    Rendering the form UI control in the implementation layer to obtain a rendering piece of the form UI control;

    Based on the rendering pieces, a rendering image of the entire form page is formed together;

    A form page is generated based on the rendering image.
13. The terminal according to claim 8, wherein, when the processor executes the at least one computer-readable instruction to implement the dictionary creation, it specifically includes:

    Acquire the multiple historical form names and the form UI control protocol layer corresponding to each historical form name, each of the form UI control protocol layers is composed of interface layers of multiple form UI controls corresponding to the historical form name , The interface layer of each form UI control carries a control name corresponding to the form UI control;

    The multiple historical form names are taken as the first level of the dictionary, the interface layers of multiple form UI controls corresponding to each of the historical form names are taken as the second level of the dictionary, and the protocol corresponding to the interface layers of the multiple form UI controls The layer serves as the third layer of the dictionary, where the dictionary is stored in a blockchain node.
14. A computer-readable storage medium having computer-readable instructions stored thereon, wherein the computer-readable storage medium stores at least one computer-readable instruction, and when the at least one computer-readable instruction is executed by a processor, the following step:

    Create a dictionary, where the dictionary carries multiple historical form names;

    Receive the control names of multiple form UI controls of the form to be created input by the user;

    Acquiring, from the dictionary, multiple form UI controls corresponding to the control names of the multiple form UI controls;

    Divide each of the form UI controls into an interface layer and an implementation layer, where an architectural isolation layer is between the interface layer and the implementation layer of each of the form UI controls;

    Splicing the protocol content in the interface layer corresponding to each of the form UI controls into an intermediate language;

    Generating a form UI control with an implementation layer based on each of the intermediate languages;

    Displaying a form UI control with an implementation layer in the implementation layer through the isolation layer;

    Rendering the form UI controls in the implementation layer to generate a form page.
15. The storage medium according to claim 14, wherein, when the at least one computer-readable instruction is executed by the processor to realize the generation of a form UI control with an implementation layer based on each of the intermediate languages, it specifically comprises:

    Input each of the intermediate languages into the translator;

    Calling the translator to request the dictionary corresponding to the intermediate language from the configuration center, and setting the dictionary to an active state;

    Calling the configuration center to read the form UI control corresponding to the dictionary in the active state from the registry;

    Return the form UI control to the translator;

    Calling the translator to read the control information of the corresponding form UI control from each of the intermediate languages according to the form UI control, wherein the control information of the form UI control corresponds to the control name;

    Based on the control name of the form UI control, the first form UI control read from each intermediate language is matched with the second form UI control read from the registry by the configuration center, where , The first form UI control read from each of the intermediate languages corresponds to an interface layer, and the second form UI control read from the registry by the configuration center corresponds to an implementation Floor;

    Associating the matching interface layer of the first form UI control and the implementation layer of the second form UI control to obtain a form UI control list corresponding to the interface layer and the implementation layer;

    Invoking the translator to read each second form UI control in the form UI control list to generate a form UI control with an implementation layer.
16. The storage medium of claim 14, wherein the at least one computer-readable instruction is executed by the processor to implement the splicing of protocol content in the interface layer corresponding to each of the form UI controls into an intermediate language When, specifically include:

    Receive the form UI controls dragged by the user in the form canvas;

    Read the form UI controls in the form canvas according to the drag order of the user;

    Each time a form UI control is read, the protocol content in the interface layer corresponding to the form UI control is spliced into an intermediate language.
17. The storage medium according to claim 14, wherein the at least one computer-readable instruction is executed by the processor to realize the display of the form UI control with the realization layer in the realization layer through the isolation layer , Specifically including:

    Acquiring multiple rendering versions corresponding to the form UI control with an implementation layer;

    Registering the multiple rendering versions in the registry, and modifying the status of the multiple rendering versions to a suspended state;

    Determining that a rendering version in the registry is a target rendering version, and configuring the target rendering version to the configuration center;

    Modifying the status of the target rendering version in the configuration center to an active status;

    The translator obtains the implementation layer information of the rendering version corresponding to the activated state from the configuration center;

    The realization layer of the form UI control corresponding to the realization layer information is displayed in the realization layer.
18. The storage medium of claim 14, wherein the at least one computer-readable instruction is executed by the processor to implement the rendering of the form UI control in the implementation layer, and when the form page is generated, it specifically includes :

    Rendering the form UI control in the implementation layer to obtain a rendering piece of the form UI control;

    Based on the rendering pieces, a rendering image of the entire form page is formed together;

    A form page is generated based on the rendering image.
19. The storage medium according to claim 14, wherein, when the at least one computer-readable instruction is executed by the processor to implement the dictionary creation, it specifically comprises:

    Acquire the multiple historical form names and the form UI control protocol layer corresponding to each historical form name, each of the form UI control protocol layers is composed of interface layers of multiple form UI controls corresponding to the historical form name , The interface layer of each form UI control carries a control name corresponding to the form UI control;

    The multiple historical form names are taken as the first level of the dictionary, the interface layers of multiple form UI controls corresponding to each of the historical form names are taken as the second level of the dictionary, and the protocol corresponding to the interface layers of the multiple form UI controls The layer serves as the third layer of the dictionary, where the dictionary is stored in a blockchain node.
20. A form page generating device, wherein the form page generating device includes:

    The creation module is used to create a dictionary, where the dictionary carries multiple historical form names;

    The receiving module is used to receive the control names of multiple form UI controls of the form to be created input by the user;

    An obtaining module, configured to obtain multiple form UI controls corresponding to the control names of the multiple form UI controls from the dictionary;

    The dividing module is used to divide each of the form UI controls into an interface layer and an implementation layer, where the interface layer and the implementation layer of each form UI control are an architectural isolation layer;

    The splicing module is used to splice the protocol content in the interface layer corresponding to each of the form UI controls into an intermediate language;

    A generating module for generating a form UI control with an implementation layer based on each of the intermediate languages;

    A display module, configured to display a form UI control with an implementation layer in the implementation layer through the isolation layer;

    The rendering module is used to render the form UI controls in the implementation layer to generate a form page.

Images