CN111930380B - Self-descriptive front-end interaction implementation method capable of being dynamically defined - Google Patents
Self-descriptive front-end interaction implementation method capable of being dynamically defined Download PDFInfo
- Publication number
- CN111930380B CN111930380B CN202010813554.9A CN202010813554A CN111930380B CN 111930380 B CN111930380 B CN 111930380B CN 202010813554 A CN202010813554 A CN 202010813554A CN 111930380 B CN111930380 B CN 111930380B
- Authority
- CN
- China
- Prior art keywords
- self
- data
- service data
- interaction
- component
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/30—Creation or generation of source code
- G06F8/38—Creation or generation of source code for implementing user interfaces
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/30—Creation or generation of source code
- G06F8/35—Creation or generation of source code model driven
- G06F8/355—Round-trip engineering
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/445—Program loading or initiating
- G06F9/44521—Dynamic linking or loading; Link editing at or after load time, e.g. Java class loading
- G06F9/44526—Plug-ins; Add-ons
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/451—Execution arrangements for user interfaces
Abstract
The invention discloses a self-descriptive front-end interaction realizing method capable of being dynamically defined, which comprises a definition process of interactive data, a presentation process of the interactive data and an analysis and reduction process of an interactive result. The method of the invention dynamically generates the front-end interactive code by dynamically defining the front-end interactive elements and interactive modes, thereby ensuring the stability and consistency of the front-end service man-machine interactive code.
Description
Technical Field
The invention relates to the technical field of front-end and back-end development of mobile internet, in particular to a self-descriptive front-end interaction implementation method capable of being dynamically defined.
Background
In the field of current mobile internet, in order to accelerate rapid development and iteration of software and improve production efficiency, especially attention is paid to division of labor and cooperation, so in most cases, a front-end and back-end separation implementation mode is adopted in the used development mode, a data interface of a service function is realized by a back-end engineer, human-computer interaction of the software function is realized by a front-end engineer, namely, the back-end engineer makes service data, and the front-end engineer presents the service data.
In this mode, the man-machine interaction elements of the software functions are completely solidified in the front-end code and completely defined by the front-end engineer according to the currently available business data, and the disadvantages are that:
firstly, the front-end human-computer interaction code needs to be modified every time the data interface of the service function changes, and for the service scenes with unstable functions and high-frequency service data interface changes, the front end needs to synchronously and frequently modify the human-computer interaction code, so the cost is high;
and secondly, service interaction codes among different functional modules are difficult to multiplex, and because service data of different modules are different, the attributes of front-end components used in service function interaction are different. The technical reason for this frequent modification is that the human-computer interaction elements are completely solidified in the front-end code, and are not dynamically defined and self-described.
Disclosure of Invention
The invention aims to overcome the defects in the background technology, and provides a dynamically-definable self-descriptive front-end interaction realization method aiming at the problem that the front-end human-computer interaction code is passively changed due to the change of a data interface, in particular to a dynamically-definable front-end and back-end connection protocol which is completed aiming at human-computer interaction elements and modes and takes a markup language as a carrier, and the current front-end and back-end technology is utilized to realize a dynamically-definable front-end interaction realization process and method with self-descriptive capability.
In order to achieve the technical effects, the invention adopts the following technical scheme:
a self-descriptive front-end interaction realizing method capable of being dynamically defined comprises a definition process of interaction data, a presentation process of the interaction data and an analysis and reduction process of an interaction result;
the definition process of the interactive data comprises the following steps:
A1. defining a service data transmission model, a man-machine interaction element and an interaction mode according to service requirements, and dynamically defining a self-descriptive front-end and back-end connection protocol; the docking protocol takes json as a carrier and has the following description capacity: defining format information of service data which is returned to the back-end program by the front end; defining a display mode of the business data item at the front end; defining the display sequence of the service data items; defining a default value of the service data item; defining the dependency relationship of the business data items; defining a hiding condition of a service data item; dynamically calculating to obtain a default value of the service data; defining nested service data items;
A2. dynamically defining a self-descriptive front-end and back-end connection protocol design human-machine interaction self-description file according to the service data transmission model, the human-machine interaction elements and the interaction mode, and storing the human-machine interaction self-description file to define the human-machine interaction mode of the service data item needing front-end processing;
A3. designing and storing a service data template by combining the service data transmission model and the human-computer interaction self-description file;
A4. establishing a corresponding relation between the business data template and a man-machine interaction self-description file;
the presentation process of the interactive data comprises the following steps:
B1. providing an interface to transmit the data content of the man-machine interaction self-description file;
B2. designing a reusable front-end component for analyzing and processing the data content of the human-computer interaction self-description file;
B3. the reusable front-end component in the step B2 is applied to realize the front-end service function;
the analysis and reduction process of the interaction result comprises the following steps:
C1. submitting the business data to a back-end program;
C2. and the back-end program analyzes and restores the service data transmission model.
The method of the invention dynamically generates the front-end interactive code by dynamically defining the front-end interactive elements and interactive modes, ensures the stability and consistency of the front-end service man-machine interactive code, utilizes the man-machine interactive elements and modes in the invention to complete the dynamically defined self-descriptive front-end and back-end connection protocol, redefines the front-end interactive elements and interactive modes of the changed service data or the service data of different modules, automatically and dynamically generates the front-end interactive service logic in a browser after the front-end requests the changed interactive elements and interactive method description information, and re-renders the front-end page, does not need to manually modify the front-end code, and solves the problems that the front-end service interactive code is easy to change and has low reusability.
Further, in the step a2, specifically, according to the service data transmission model, the service data item required to be processed by the front end is determined, then the self-descriptive front-back end connection protocol is dynamically defined by applying the human-computer interaction element and the interaction mode, a human-computer interaction self-description file is designed, and the human-computer interaction mode of the service data item required to be processed by the front end is defined.
Furthermore, the human-computer interaction element and interaction mode dynamic definition self-descriptive front-back end docking protocol is composed of a json array, and the array element is a section description object;
the section description object is used for describing interaction information of one step in front-end operation and consists of two elements, namely section description information and components description information; the section description information is used for describing the section interaction content, and the components description information is used for describing which display elements the current section has and is composed of a json map element.
Further, the key of the json map element is a data name in the service data transmission model, and the value is a component description object.
Further, the component description object is used for describing an interaction mode of business data at a front end and a data format accepted at a back end, and includes the following elements: value, value _ type and ui _ setting describe objects, wherein value represents a result value of front-end operation, value _ type represents a data type returned to a back end by the reusable front-end component, and ui _ setting describes objects used for describing an interaction mode of fields at the front end.
Furthermore, json or jsonnet is used as a carrier for the service data template, the key value of the service data template corresponds to the key value of the service data transmission model one by one, and the key value of the service data template is jsonnath corresponding to each service data value in the human-computer interaction self-description file.
Further, the description information of the ui _ setting description object includes extension description information, general description information, and description information related to a specific control type.
Further, each description information in the ui _ setting description object is defined as follows:
label: label information corresponding to the service data on the UI;
component _ type: the service data displays the used component categories on the UI, and comprises the following components: input, auto _ complete, text _ area, select, group, representing input box, drop-down selection combination input box, text area, drop-down selection box, combination box, respectively;
placeholder: the placeholder information of the service data displayed on the UI;
position: the sequence of the service data displayed on the UI;
required: whether the service data is a mandatory item;
hit: error prompt information displayed when the business data is wrongly input;
hide _ where: a condition of whether display data is displayed on the UI;
vc _ notify: a component list which needs to be notified when the service data changes;
evaluation: the verification rule of the validity of the service data is a regular expression; only if the component is input, auto _ complete, text _ area;
option _ values: only the components are used when auto _ complete and select, and represent the service data value list;
option _ texts: the component is used when the component is select and represents a service data display text list;
multiple: only the component is used when selected, indicating whether multi-selection operation is supported;
components: only components used when they are group, represent a list of components that are placed in the combo box.
Further, the design steps of the reusable front-end component are as follows:
receiving data content of the human-computer interaction self-description file as a parameter;
analyzing each section description object in the human-computer interaction self-description file into a section element, and adding an in-page navigation link for each section element;
and extracting the section description information aiming at each section element, setting the name and layout of the section according to the content of the section description information, extracting the components description information and performing element display processing.
Further, the element display processing procedure is specifically as follows:
scanning all the components in the component description information, sequencing all the components according to the position field in the ui _ setting, and sequentially storing the keys of the components corresponding to the positions into an array, wherein the keys are recorded as: sorted _ components;
traversing the sorted _ components, and finding out the description information of the corresponding component from the description information of the components in the human-computer interaction self-description file according to the value of the sorted _ components;
and assembling corresponding front-end component codes according to the obtained description information of the components and the content of the components interacting with the UI.
Further, the step B3 is specifically:
the front-end component code requests the content of the human-computer interaction self-description file corresponding to the current business function and the identification number (such as ID) of the business data template corresponding to the human-computer interaction self-description file from the back-end according to the business function requirement, and transmits the obtained information to the reusable front-end component designed in the step B2 to complete the display and interactive processing of the business data item.
Further, the step C1 is specifically:
after the input of service data is completed through the service function of the front-end program, the reusable front-end component automatically updates the data content of the human-computer interaction self-description file;
and the front-end program submits the data content of the updated man-machine interaction self-description file and the identification number of the business data template corresponding to the data content to the background program.
Further, in step C2, after the back-end program receives the data content of the human-computer interaction self-description file submitted by the front-end program and the identification number of the service data template corresponding to the data content, the processing flow is as follows:
s1, reading the content of the business data template corresponding to the identification number of the business data template;
s2, traversing data nodes in the service data template, and finding values of the corresponding data nodes in the human-computer interaction self-description file;
s3, splicing the data nodes and the data node values in the substep S2;
and S4, the service data transmission object is processed by the service logic processing module.
Compared with the prior art, the invention has the following beneficial effects:
firstly, in the technical scheme of the invention, when a new service function module is developed, a back-end program designs a service data template and a man-machine interaction self-description file and provides an HTTP transmission interface for the service data template and the man-machine interaction self-description file, and then the front end only needs to quote the designed reusable front-end component and complete the request of the service data template and the man-machine interaction self-description file, so that the development of the front-end service function can be completed without processing a service data item;
secondly, in the technical scheme of the invention, when the service function is changed and the service data items are added, deleted or modified, the back end only needs to update the service data template and the man-machine interaction self-description file to complete the change of the service function without the need of a front-end program to realize the change;
thirdly, the technical scheme of the invention supports common component types such as a text box, a drop-down list text combination box, a text area, a drop-down list, a combination box and the like on UI display, and has more diverse display effects;
fourthly, the technical scheme of the invention supports the data types such as coolean, number, string, array, object and the like on the back end data type, and has wider application range.
Drawings
FIG. 1 is a flow chart diagram of a dynamically definable self-descriptive front-end interaction implementation method of the present invention.
Detailed Description
The invention will be further elucidated and described with reference to the embodiments of the invention described hereinafter.
Example (b):
the first embodiment is as follows:
a self-descriptive front-end interaction realizing method capable of dynamic definition adopts self-defined man-machine interaction elements and an interaction mode to dynamically define a self-descriptive front-end and back-end connection protocol, takes a markup language as a carrier to dynamically define the man-machine interaction elements and the interaction mode of each function in software, and dynamically generates a front-end interaction code after the front-end code analyzes the protocol content, thereby solving the problems that a front-end service interaction code is easy to change and has low reusability.
The method specifically comprises a definition process of interactive data, a presentation process of the interactive data and an analysis and reduction process of an interactive result.
The definition process of the interactive data is processed by a back-end program, and the method mainly realizes that a service data template and a man-machine interaction self-description file are defined by a service data transmission model by using a man-machine interaction element and an interaction mode dynamic definition self-descriptive front-end and back-end docking protocol, and a Restful interface is submitted for the front-end program to call for the man-machine interaction self-description file.
The presentation flow of the interactive data is processed by a front-end program, and the reusable front-end component is mainly used for automatically rendering the human-computer interaction self-description file into a WEB interaction page and returning the updated human-computer interaction self-description file to a back-end program for processing.
The analysis and reduction flow of the interaction result is processed by a back-end program, and the method mainly realizes the purpose of receiving the updated human-computer interaction self-description file returned by the front end and restoring the updated human-computer interaction self-description file into a service data transmission model according to a service data template for further processing by a service module.
Specifically, the three processes can be subdivided into the following steps:
s101, according to business requirements, defining a traditional business data transmission model, man-machine interaction elements and an interaction mode dynamic definition self-descriptive front-end and back-end connection protocol.
The service data transmission model is defined as the prior art, and is not described herein again.
The design scheme of the human-computer interaction element and interaction mode dynamic definition self-descriptive front-end and back-end docking protocol is as follows:
it should be noted that, in this embodiment, the protocol is composed of a json array, and the array element is a "section description object".
Specifically, section describes an object: describing interactive information of one step in the front-end operation, wherein the object consists of two elements of 'section description information' and 'components description information'.
section description information: describing section interaction content, comprising: and elements such as name and layout, wherein the name element represents the name of the section, and the layout is used for selecting the layout template of the section.
The components description information: and describing which display elements the current section has, wherein the display elements are composed of a json map element, the key of the map element is the data name in the service data transmission model, and the value of the key is 'component description object'.
component describes an object: the interactive mode of the service data at the front end and the data format accepted at the back end are described, and the data format is composed of values, value _ types, ui _ setting description objects and other elements. value represents the result value of the front-end operation, and value _ type represents the data type returned by the component to the back-end, which may be one of the types of bootean, number, string, array, object, etc.
ui _ setting describes the object: the way the fields interact in the front end is described. The control system comprises general description information such as label, component _ type, placeholder, position, required and the like, extension description information such as hit, hide _ while, vc _ notify and the like, and description information such as validity, option _ values, option _ textures, multiple, components and the like related to specific control types.
Specifically, each description information in the ui _ setting is designed in detail as follows:
label: and the service data corresponds to the label information on the UI.
component _ type: the service data displays the used component categories on the UI, and comprises the following components: input, auto _ complete, text _ area, select, group, representing input box, drop-down selection combo input box, text area, drop-down selection box, combo box, respectively.
placeholder: and displaying placeholder information of the service data on the UI.
position: the order in which the service data is displayed on the UI.
required: whether the service data is a mandatory item.
hit: and error prompt information displayed when the business data is wrongly recorded.
hide _ where: a condition of whether the display data is displayed on the UI.
vc _ notify: and the service data is a component list to be notified when the value change occurs.
Evaluation: and the service data validity check rule is a regular expression. It is only used when the components are input, auto _ complete, text _ area.
option _ values: only the components are used for auto _ complete, select, representing the business data value list.
option _ texts: the component is used only when the component is select, and the service data display text list is represented.
multiple: only the component is used when it is select, indicating whether multiple selection operations are supported.
components: only components used when they are group, represent a list of components that are placed in the combo box.
S102, defining a service data item needing to be processed by a front end according to a service data transmission model, and designing a human-computer interaction self-description file by applying a self-defined human-computer interaction element and an interaction mode dynamic definition self-descriptive front-end and back-end connection protocol to define a human-computer interaction mode of the service data item needing to be processed by the front end.
Specifically, in this embodiment, assume that the service data object templates to be processed are as follows:
then, a self-descriptive front-end and back-end connection protocol is dynamically defined according to the customized human-computer interaction elements and the interaction mode, and the human-computer interaction self-description file of the embodiment is defined as follows:
the integral structure is as follows:
operation step 01 component definition:
operation step 02 component definition:
and S103, designing a business data template.
And designing a service data template by combining the service data transmission model and the human-computer interaction self-description file, and establishing an incidence relation aiming at the service data item value between the human-computer interaction self-description file and the service data transmission model. The specific design scheme is as follows:
the service data template uses json or jsonnet as a carrier, key keys of the service data template correspond to key values in a service data transmission model one by one, and the key values are jsonnpath corresponding to service data values in the human-computer interaction self-description file.
Specifically, in this embodiment, the service data template designed by combining the service data transmission model and the human-computer interaction self-description file is as follows:
and S104, persistently storing the human-computer interaction self-description file in the step S102 and the service data template in the step S103, establishing an association relation, and designing a restful HTTP interface for the front end to call the content of the human-computer interaction self-description file.
S105, the front end requests the content of the human-computer interaction self-description file corresponding to the current service function and a service data template identification number (such as ID) corresponding to the human-computer interaction self-description file from the rear end through a restful HTTP interface according to the service function requirement, and transmits the content of the human-computer interaction self-description file to a reusable front end component for analyzing and processing the content of the human-computer interaction self-description file; and the front end finishes rendering processing on the service data page.
Specifically, the design scheme of the reusable front-end component for parsing and processing the content of the human-computer interaction self-description file in the implementation is as follows:
the component receives human-computer interaction self-description file content as a parameter.
Analyzing each section description object in the human-computer interaction self-description file into a section element, and adding an in-page navigation link for each section element.
For each section element, extracting section description information, setting the name and layout of the section according to the content of the section description information, extracting component description information, and performing element display processing, wherein the specific processing process comprises the following steps:
scanning all the components in the component description information, sequencing all the components according to the position fields in the ui _ setting, and sequentially storing the keys of the components corresponding to the positions into an array, wherein the keys are recorded as: sorted _ components.
And traversing the sorted _ components, and finding corresponding 'component description information' in the 'component description information' of the man-machine interaction self-description file according to the value of the sorted _ components.
And aiming at the component description information, assembling corresponding front-end component codes according to the content of the UI interaction.
S106, the user operates the page content, and the front-end program automatically updates the content of the man-machine interaction self-description file
And S107, the user completes the page operation and initiates a service operation request.
And S108, the front-end program transmits the updated man-machine interaction self-description file content back to the back-end system.
In the process, the data content of the man-machine interaction self-description file is automatically updated through the reusable front-end component, and the front-end program submits the updated man-machine interaction self-description file content and the corresponding business data template identification number to the background program.
S109, the back-end program analyzes and restores the service data transmission model from the content of the human-computer interaction self-description file, and completes the subsequent service logic processing, which specifically comprises the following steps:
1) reading the service data template content corresponding to the service data template identification number;
2) traversing data nodes in the service data template, and finding values of the corresponding data nodes in the human-computer interaction self-description file;
3) splicing the data nodes and the data node values in the substep 2) into a service data transmission object;
4) and the service data transmission object is processed by the service logic processing module.
And S110, finishing the processing.
It will be understood that the above embodiments are merely exemplary embodiments taken to illustrate the principles of the present invention, which is not limited thereto. It will be apparent to those skilled in the art that various modifications and improvements can be made without departing from the spirit and substance of the invention, and these modifications and improvements are also considered to be within the scope of the invention.
Claims (11)
1. A self-descriptive front-end interaction realizing method capable of being dynamically defined is characterized in that when a new business function module is developed, a back-end program designs a business data template and a man-machine interaction self-description file, provides an HTTP transmission interface for the business data template and the man-machine interaction self-description file, a reusable front-end component is quoted by a front end, and the request of the business data template and the man-machine interaction self-description file is completed, so that the development of the front-end business function is completed without processing a business data item;
when the service function is changed and the service data items are added, deleted or modified, the back end updates the service data template and the human-computer interaction self-description file to complete the change of the service function without a front-end program to realize the change; the method comprises a definition process of interactive data, a presentation process of the interactive data and an analysis and reduction process of an interactive result;
the definition process of the interactive data comprises the following steps:
A1. dynamically defining a self-descriptive front-end and back-end connection protocol according to the man-machine interaction elements and the interaction mode; the self-descriptive front-end and back-end docking protocol is composed of a json array, and array elements are section description objects;
the section description object is used for describing interaction information of one step in front-end operation and consists of two elements, namely section description information and components description information; the section description information is used for describing section interaction content, and the components description information is used for describing which display elements the current section has and is composed of a json map element;
A2. defining a service data item to be processed by a front end according to a service data transmission model, then dynamically defining a self-descriptive front-end and back-end connection protocol by applying the human-computer interaction element and an interaction mode, designing a human-computer interaction self-description file, and defining a human-computer interaction mode of the service data item to be processed by the front end;
A3. designing and storing a service data template by combining the service data transmission model and the human-computer interaction self-description file;
A4. establishing a corresponding relation between the business data template and a man-machine interaction self-description file;
the presentation process of the interactive data comprises the following steps:
B1. providing an interface to transmit the data content of the man-machine interaction self-description file;
B2. designing a reusable front-end component for analyzing and processing the data content of the human-computer interaction self-description file;
B3. the reusable front-end component in the step B2 is applied to realize the front-end service function;
the analysis and reduction process of the interaction result comprises the following steps:
C1. submitting the business data to a back-end program;
C2. and the back-end program analyzes and restores the service data transmission model.
2. The method as claimed in claim 1, wherein the key of the json map element is a data name in the service data transmission model, and the value is a component description object.
3. The method for implementing self-descriptive front-end interaction capable of being dynamically defined according to claim 2, wherein the component description object is used for describing interaction modes of business data at a front end and a data format accepted at a back end, and comprises the following elements: value, value _ type and ui _ setting describe objects, wherein value represents a result value of front-end operation, value _ type represents a data type returned to a back end by the reusable front-end component, and ui _ setting describes objects used for describing an interaction mode of fields at the front end.
4. The method as claimed in claim 3, wherein json or jsonnet is used as a carrier for the service data template, the key values of the service data template correspond to the key values of the service data transmission model one by one, and the key values of the service data template are jsonnath corresponding to the service data values in the human-computer interaction self-description file.
5. The method as claimed in claim 4, wherein the description information of the ui _ setting description object includes extended description information, general description information, and description information related to specific control types.
6. The method for implementing dynamically definable self-descriptive front-end interaction according to claim 5, wherein the respective description information in the ui _ setting description object is defined as follows:
label: label information corresponding to the service data on the UI;
component _ type: the service data displays the used component categories on the UI, and comprises the following components: input, auto _ complete, text _ area, select, group, representing input box, drop-down selection combination input box, text area, drop-down selection box, combination box, respectively;
placeholder: the placeholder information of the service data displayed on the UI;
position: the sequence of the service data displayed on the UI;
required: whether the service data is a mandatory item;
hit: error prompt information displayed when the business data is wrongly input;
hide _ where: a condition of whether display data is displayed on the UI;
vc _ notify: a component list which needs to be notified when the service data changes;
evaluation: the verification rule of the validity of the service data is a regular expression; only if the component is input, auto _ complete, text _ area;
option _ values: only the components are used when auto _ complete and select, and represent the service data value list;
option _ texts: the component is used when the component is select and represents a service data display text list;
multiple: only the component is used when selected, indicating whether multi-selection operation is supported;
components: only components used when they are group, represent a list of components that are placed in the combo box.
7. The dynamically definable, self-descriptive front-end interaction implementation method of claim 6, wherein the reusable front-end component is designed by the steps of:
receiving data content of the human-computer interaction self-description file as a parameter;
analyzing each section description object in the human-computer interaction self-description file into a section element, and adding an in-page navigation link for each section element;
and extracting the section description information aiming at each section element, setting the name and layout of the section according to the content of the section description information, extracting the components description information and performing element display processing.
8. The method for implementing dynamically definable self-descriptive front-end interaction according to claim 7, wherein the element display processing procedure is specifically as follows:
scanning all the components in the component description information, sequencing all the components according to the position field in the ui _ setting, and sequentially storing the keys of the components corresponding to the positions into an array, wherein the keys are recorded as: sorted _ components;
traversing the sorted _ components, and finding out the description information of the corresponding component from the description information of the components in the human-computer interaction self-description file according to the value of the sorted _ components;
and assembling corresponding front-end component codes according to the obtained description information of the components and the content of the components interacting with the UI.
9. The method for implementing dynamically definable self-descriptive front-end interaction according to claim 8, wherein the step B3 specifically includes:
and the front-end component code requests the content of the human-computer interaction self-description file corresponding to the current business function and the identification number of the business data template corresponding to the human-computer interaction self-description file from the back end according to the business function requirement, and transmits the obtained information to the reusable front-end component designed in the step B2 to finish the display and interactive processing of the business data item.
10. The dynamically definable self-descriptive front-end interaction implementing method according to claim 9, wherein the step C1 is specifically:
after the input of service data is completed through the service function of the front-end program, the reusable front-end component automatically updates the data content of the human-computer interaction self-description file;
and the front-end program submits the data content of the updated man-machine interaction self-description file and the identification number of the business data template corresponding to the data content to the background program.
11. The method for implementing self-descriptive front-end interaction capable of being dynamically defined according to claim 10, wherein in step C2, after the back-end program receives the data content of the man-machine interaction self-descriptive file submitted by the front-end program and the identification number of the business data template corresponding to the data content, the processing flow is as follows:
s1, reading the content of the business data template corresponding to the identification number of the business data template;
s2, traversing data nodes in the service data template, and finding values of the corresponding data nodes in the human-computer interaction self-description file;
s3, splicing the data nodes and the data node values in the substep S2;
and S4, the service data transmission object is processed by the service logic processing module.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010813554.9A CN111930380B (en) | 2020-08-13 | 2020-08-13 | Self-descriptive front-end interaction implementation method capable of being dynamically defined |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010813554.9A CN111930380B (en) | 2020-08-13 | 2020-08-13 | Self-descriptive front-end interaction implementation method capable of being dynamically defined |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111930380A CN111930380A (en) | 2020-11-13 |
| CN111930380B true CN111930380B (en) | 2022-02-01 |
Family
ID=73311699
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010813554.9A Active CN111930380B (en) | 2020-08-13 | 2020-08-13 | Self-descriptive front-end interaction implementation method capable of being dynamically defined |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111930380B (en) |
Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105760159A (en) * | 2016-02-01 | 2016-07-13 | 四川长虹电器股份有限公司 | Website developing method and system |
| CN106528169A (en) * | 2016-11-25 | 2017-03-22 | 浙江工业大学 | Web system development reusable method based on AnGo dynamic evolution model |
| CN107291523A (en) * | 2017-08-01 | 2017-10-24 | 北京亚鸿世纪科技发展有限公司 | A kind of web front end message bus system |
| CN107943737A (en) * | 2017-10-30 | 2018-04-20 | 上海君协光电科技发展有限公司 | A kind of general-purpose machine control interface card based on PXI Express buses |
| CN110968319A (en) * | 2019-12-24 | 2020-04-07 | 平安普惠企业管理有限公司 | Method, device and computer equipment for converting H5 project into Vue framework |
| CN111221522A (en) * | 2020-01-13 | 2020-06-02 | 大汉软件股份有限公司 | Automatic code generation method of front-end and back-end separation architecture for government intensive application development |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US8195823B2 (en) * | 2000-04-17 | 2012-06-05 | Circadence Corporation | Dynamic network link acceleration |
-
2020
- 2020-08-13 CN CN202010813554.9A patent/CN111930380B/en active Active
Patent Citations (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105760159A (en) * | 2016-02-01 | 2016-07-13 | 四川长虹电器股份有限公司 | Website developing method and system |
| CN106528169A (en) * | 2016-11-25 | 2017-03-22 | 浙江工业大学 | Web system development reusable method based on AnGo dynamic evolution model |
| CN107291523A (en) * | 2017-08-01 | 2017-10-24 | 北京亚鸿世纪科技发展有限公司 | A kind of web front end message bus system |
| CN107943737A (en) * | 2017-10-30 | 2018-04-20 | 上海君协光电科技发展有限公司 | A kind of general-purpose machine control interface card based on PXI Express buses |
| CN110968319A (en) * | 2019-12-24 | 2020-04-07 | 平安普惠企业管理有限公司 | Method, device and computer equipment for converting H5 project into Vue framework |
| CN111221522A (en) * | 2020-01-13 | 2020-06-02 | 大汉软件股份有限公司 | Automatic code generation method of front-end and back-end separation architecture for government intensive application development |
Non-Patent Citations (1)
| Title |
|---|
| 组件化的数字内容呈现系统设计与实现;王谷旸 等;《北京印刷学院学报》;20180104;第25卷(第07期);161-163,181 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111930380A (en) | 2020-11-13 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US9733820B2 (en) | Methods, systems and computer readable media for pasting data | |
| RU2419847C2 (en) | Integrating diagrams into documents | |
| US20190018659A1 (en) | Method and system for visual data mapping and code generation to support data integration | |
| US6973625B1 (en) | Method for creating browser-based user interface applications using a framework | |
| US7814404B2 (en) | System and method for applying workflow of generic services to component based applications for devices | |
| CA2498540C (en) | System and method for building wireless applications with intelligent mapping between user interface and data components | |
| US20030055748A1 (en) | Methods and systems for providing a document with interactive elements to retrieve information for processing by business applications | |
| US20070124320A1 (en) | Modeling a data element | |
| WO2007067578A1 (en) | Metadata driven user interface | |
| WO2010036457A2 (en) | Editing 2d structures using natural input | |
| WO2006051958A1 (en) | Information distribution system | |
| CN108647019B (en) | Control layer coding method for service combination | |
| CN114239504A (en) | Form configuration method, device, equipment, readable storage medium and program product | |
| EP2098964A1 (en) | System and method for conversion of WEB services' applications into component based applications for mobile devices | |
| US20070261037A1 (en) | Methods and systems for displaying multiple unique dynamic messages on a user interface | |
| CN111930380B (en) | Self-descriptive front-end interaction implementation method capable of being dynamically defined | |
| WO2010017525A1 (en) | System and method for designing and generating online stationery | |
| CN103164217B (en) | Independent data entity for back-end system | |
| CN113361242A (en) | Method and device for customizing questionnaire template | |
| CN114237560A (en) | Data storage method, storage device, electronic equipment and storage medium | |
| CN108984318B (en) | Message delivery method and device based on driving model and readable storage medium | |
| CN110780970A (en) | Data screening method, device, equipment and computer readable storage medium | |
| CN114860367B (en) | User interface event processing method, device and system | |
| CN116627986A (en) | Form realization method and system capable of dynamically configuring display and search | |
| CA2538531C (en) | System and method for applying workflow of generic services to component based applications for devices |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |