CN112380477B - Form assembly structure - Google Patents
Form assembly structure Download PDFInfo
- Publication number
- CN112380477B CN112380477B CN202011268086.8A CN202011268086A CN112380477B CN 112380477 B CN112380477 B CN 112380477B CN 202011268086 A CN202011268086 A CN 202011268086A CN 112380477 B CN112380477 B CN 112380477B
- Authority
- CN
- China
- Prior art keywords
- component
- verification
- header
- short
- function
- 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
- 238000012795 verification Methods 0.000 claims abstract description 85
- 230000006870 function Effects 0.000 claims abstract description 51
- 238000004458 analytical method Methods 0.000 claims abstract description 32
- 230000014509 gene expression Effects 0.000 claims description 12
- 230000007246 mechanism Effects 0.000 claims description 5
- 238000012545 processing Methods 0.000 claims description 5
- 238000012986 modification Methods 0.000 claims description 4
- 230000004048 modification Effects 0.000 claims description 4
- 238000007792 addition Methods 0.000 claims description 3
- 230000008859 change Effects 0.000 claims description 3
- 238000012217 deletion Methods 0.000 claims description 3
- 230000037430 deletion Effects 0.000 claims description 3
- 238000003780 insertion Methods 0.000 claims description 3
- 230000037431 insertion Effects 0.000 claims description 3
- 238000005315 distribution function Methods 0.000 claims description 2
- 238000000034 method Methods 0.000 abstract description 22
- 230000008569 process Effects 0.000 abstract description 9
- 239000000306 component Substances 0.000 description 185
- 238000011161 development Methods 0.000 description 10
- 238000010586 diagram Methods 0.000 description 5
- 230000004044 response Effects 0.000 description 3
- 238000003491 array Methods 0.000 description 2
- 239000000463 material Substances 0.000 description 2
- 230000009466 transformation Effects 0.000 description 2
- 230000001131 transforming effect Effects 0.000 description 2
- 230000009286 beneficial effect Effects 0.000 description 1
- 238000006243 chemical reaction Methods 0.000 description 1
- 239000008358 core component Substances 0.000 description 1
- 238000012544 monitoring process Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 230000000007 visual effect Effects 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/90—Details of database functions independent of the retrieved data types
- G06F16/95—Retrieval from the web
- G06F16/958—Organisation or management of web site content, e.g. publishing, maintaining pages or automatic linking
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F40/00—Handling natural language data
- G06F40/10—Text processing
- G06F40/166—Editing, e.g. inserting or deleting
- G06F40/177—Editing, e.g. inserting or deleting of tables; using ruled lines
- G06F40/18—Editing, e.g. inserting or deleting of tables; using ruled lines of spreadsheets
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Databases & Information Systems (AREA)
- Audiology, Speech & Language Pathology (AREA)
- Computational Linguistics (AREA)
- General Health & Medical Sciences (AREA)
- Health & Medical Sciences (AREA)
- Artificial Intelligence (AREA)
- Data Mining & Analysis (AREA)
- Document Processing Apparatus (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The application relates to a form assembly structure, comprising: the meter comprises a meter head component, a meter body component, a short meter body component, a status bar component and a form verification component. In the application, a developer can write a field configuration file by himself, the field configuration file is used as an input item to be input into the form component, the field configuration file is analyzed by the header component, the body component and the short body component, and the header component, the body component and the short body component are analyzed to generate a form according to the form configuration data obtained by analysis. The developer only needs to complete the process of writing the field configuration file, the form component can generate a form required by the developer according to the field configuration file written by the developer, and the process of writing HTML label codes line by the developer according to the field document is omitted. The form verification component verifies the values of all fields in the form configuration data obtained through analysis; the status bar component displays the generation status of the form and the verification result output by the form verification component, and the functions of the form component are more diversified.
Description
Technical Field
The application relates to the technical field of front-end development of pages, in particular to a form component structure.
Background
Because of the rapid development of front-end development frameworks such as Vue and practice, front-end development has entered the component development era, but the current front-end components are mostly aimed at mobile-end applications or simple data submission (such as user registration, user information submission, etc.), and page development, which requires a large number of form fills and data submission like cross-border electric business, has almost no corresponding development component library support. And the user group of the filling system is not the common public but an operator with a certain professional, so that the form component structure can simply input and submit, and the high efficiency, convenience and accuracy of the input data are also considered. However, the current form component structure requires a development engineer to write a large number of repeated HTML tag codes, and is relatively large in operation amount, relatively low in efficiency and prone to errors. Moreover, the current form component structure cannot monitor the current state of the form.
Disclosure of Invention
To overcome at least some of the problems associated with the related art, the present application provides a form assembly structure.
The scheme of the application is as follows:
A form assembly structure, comprising:
the meter comprises a meter head component, a meter body component, a short meter body component, a status bar component and a form checking component;
the status bar component is a public component, and the header component, the body component and the short body component both refer to the status bar component;
the form verification component is a public component, and the header component, the table body component and the short table body component both refer to the form verification component;
The header component is configured with a field configuration file analysis function;
the table body component refers to the table head component and is configured with a field configuration file analysis function and a list operation function;
The short table body component refers to the table head component and is configured with a field configuration file analysis function and a list operation function;
the header component is used for analyzing the input field configuration file and generating a form header according to the form configuration data obtained by analysis;
The table body component is used for analyzing the input field configuration file and generating a table body and an editable list operation item according to the table configuration data obtained by analysis;
The short table body component is used for analyzing the input field configuration file and generating a short table body of a table and an editable list operation item according to the table configuration data obtained by analysis;
the form verification component is used for verifying values of all fields in the form configuration data obtained through analysis and outputting a verification result;
The status bar component is used for displaying the generation status of the form and the verification result output by the form verification component.
Preferably, in one realisation of the application,
The meter head assembly, the meter body assembly and the short meter body assembly are also provided with a form state initialization function;
the gauge outfit component, the gauge body component and the short gauge body component are also used for initializing data in the components according to the form configuration data obtained through analysis.
Preferably, in one realisation of the application,
The header component is also provided with a default value configuration function;
and the header component configures a function based on the default value, and configures default values for each field according to the analyzed form configuration data.
Preferably, in one realisation of the application,
The header assembly is also provided with an event configuration function;
the header component is further used for binding the event for the form page element and configuring an event processing mechanism according to the analyzed form configuration data.
Preferably, in one realisation of the application,
The gauge outfit component is also provided with a verification rule configuration function;
and the header component further converts the document verification rule in the form configuration data obtained through analysis into a regular expression based on the verification rule configuration function.
Preferably, in one realisation of the application,
The list operation function of the table body component configuration at least comprises the following steps: add, delete, and modify functions to the list.
Preferably, in one realisation of the application,
The list operation function of the short list body component configuration at least comprises: addition, deletion, modification, ordering, movement, insertion, duplication, and distribution functions to the list.
Preferably, in one realisation of the application,
The form verification component is specifically configured to verify values of all fields in the form configuration data obtained by parsing according to the regular expression converted by the header component, and output a verification result;
The form verification component is further configured to perform remote background verification when all values of the fields pass verification and a remote verification interface is configured.
Preferably, in one realisation of the application,
The status bar component is specifically used for displaying newly-built, edited or saved status according to the change condition of the form data when the form data changes in the generation status of the form;
Displaying a verification failure state when the verification result output by the form verification component is verification failure;
The form disabled state is displayed when the form is disabled.
Preferably, in one realisation of the application,
The output value of the header component is a data object containing a plurality of key value pairs;
The output values of the table body component and the short table body component are a list containing a plurality of data objects.
The technical scheme provided by the application can comprise the following beneficial effects: the form component structure in the application comprises: the meter comprises a meter head component, a meter body component, a short meter body component, a status bar component and a form verification component. The status bar component and the form verification component are common components and are referenced by the header component, the body component and the short body component. In the application, a developer can write a field configuration file by himself, the field configuration file is used as an input item to be input into the form component structure, the field configuration file is analyzed by the header component, the body component and the short body component, and the header component, the body component and the short body component are analyzed to generate a form according to the form configuration data obtained by analysis. The developer only needs to complete the process of writing the field configuration file, the form component structure can generate a form required by the developer according to the field configuration file written by the developer, the process that the developer writes HTML label codes line by line according to the field document is omitted, the operation amount of the developer is reduced, and the efficiency and the accuracy are improved. The form verification component is used for verifying values of all fields in the form configuration data obtained through analysis; the status bar component displays the generation status of the form and the verification result output by the form verification component, and the functions of the form component structure are more diversified.
It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the application as claimed.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the application and together with the description, serve to explain the principles of the application.
FIG. 1 is a schematic diagram of a form component structure according to one embodiment of the present application;
FIG. 2 is a transformation rule for transforming a document verification rule into a regular expression in a form component structure, according to one embodiment of the present application;
FIG. 3 is a schematic diagram of an application flow of a form component architecture provided by one embodiment of the present application;
FIG. 4 is a code execution flow diagram of a form component architecture provided by one embodiment of the present application;
FIG. 5 is a schematic diagram of a form assembly structure according to another embodiment of the present application.
Reference numerals: a header assembly-1; a watch body component-2; short watch body component-3; status bar component-4; form verification component-5.
Detailed Description
Reference will now be made in detail to exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, the same numbers in different drawings refer to the same or similar elements, unless otherwise indicated. The implementations described in the following exemplary examples do not represent all implementations consistent with the application. Rather, they are merely examples of apparatus and methods consistent with aspects of the application as detailed in the accompanying claims.
A form assembly structure, referring to fig. 1, comprising:
A gauge outfit component 1, a gauge body component 2, a short gauge body component 3, a status bar component 4 and a form verification component 5;
The status bar component 4 is a common component, the gauge outfit component 1, the gauge body component 2 and the short gauge body component 3 both refer to the status bar component 4;
The form verification component 5 is a common component, the gauge head component 1, the gauge body component 2 and the short gauge body component 3 both refer to the form verification component 5;
The header component 1 is configured with a field configuration file analysis function;
The table body component 2 refers to the table head component 1 and is configured with a field configuration file analysis function and a list operation function;
The short table body component 3 refers to the table head component 1 and is configured with a field configuration file analysis function and a list operation function;
the header component 1 is used for analyzing an input field configuration file and generating a form header according to form configuration data obtained through analysis;
The table body component 2 is used for analyzing the input field configuration file and generating a table body and an editable list operation item according to the table configuration data obtained by analysis;
The short table body component 3 is used for analyzing the input field configuration file and generating a short table body of the table and an editable list operation item according to the table configuration data obtained by analysis;
the form verification component 5 is used for verifying values of all fields in the form configuration data obtained through analysis and outputting a verification result;
The status bar component 4 is used for displaying the generation status of the form and the verification result output by the form verification component 5.
In this embodiment, a field configuration file keys (also referred to as a field library file) is defined, and a developer may write the keys file by himself, store it in a json format in a front-end item and refer to it on a page, or perform visual setting by a service person familiar with the service through a system to finally generate the keys file. The key file is input into the form component structure as an input item, the form component structure analyzes the key file, and a front-end code is automatically generated according to field attributes in the key, namely, the code is simply written by the code.
The form component structure in this embodiment includes: a header component 1, a watch body component 2, a short watch body component 3, a status bar component 4 and a form verification component 5. Wherein, the status bar component 4 and the form verification component 5 are both public components and are referenced by the header component 1, the body component 2 and the short body component 3. In the application, a developer can write a field configuration file by himself, the field configuration file is used as an input item to be input into the form component structure, the field configuration file is analyzed by the header component 1, the body component 2 and the short body component 3, the header component 1, the body component 2 and the short body component 3 are analyzed, and a form is generated according to form configuration data obtained through analysis. The developer only needs to complete the process of writing the field configuration file, the form component structure can generate a form required by the developer according to the field configuration file written by the developer, the process that the developer writes HTML label codes line by line according to the field document is omitted, the operation amount of the developer is reduced, and the efficiency and the accuracy are improved. The form verification component 5 is used for verifying values of all fields in the form configuration data obtained through analysis; the status bar component 4 displays the generation status of the form and the verification result output by the form verification component 5, and the functions of the form component structure are more diversified.
The form component structure in some embodiments,
The meter head component 1, the meter body component 2 and the short meter body component 3 are also provided with a form state initialization function;
The header component 1, the table body component 2 and the short table body component 3 are also used for initializing data in the components according to the analyzed form configuration data.
In the form component structure in the prior art, data needs to be initialized outside the component, and in the form component structure in this embodiment, data is initialized inside the form component structure according to form configuration data obtained through analysis of a key file.
Further, the method comprises the steps of,
The header assembly 1 is also configured with a default configuration function;
The header component 1 configures a default value for each field according to the form configuration data obtained by parsing based on a default value configuration function.
After the state initialization, default values need to be configured for the data space of the header component 1 according to default values in the form configuration data obtained through the analysis of the key file.
Further, the method comprises the steps of,
The header assembly 1 is also configured with an event configuration function;
The header component 1 is further configured to bind an event and configure an event processing mechanism for a form page element according to the form configuration data obtained by parsing.
There is a need in the art for a response method that configures events (focus event, out-of-focus event, carriage return event, etc.) for each field individually.
In this embodiment, an event configuration function is configured for the header component 1, and a developer only needs to write an event related processing mode in a key file, so that a process of independently configuring an event response method for each field by the developer is omitted, and development efficiency is improved.
Further, the method comprises the steps of,
The header assembly 1 is also provided with a verification rule configuration function;
The header component 1 also converts the document verification rules in the parsed form configuration data into regular expressions based on the verification rule configuration function.
The transformation rule for transforming a document verification rule into a regular expression may refer to fig. 2.
In the prior art, the front-end verification is mostly performed by using a regular expression, and the writing method of the regular expression is complicated and difficult to understand.
In this embodiment, an escape mechanism, that is, a verification rule configuration function is built in the header component 1, so that a developer only needs to write the document verification rule in the key file to automatically convert the document verification rule into a regular expression, thereby improving the development efficiency.
In this embodiment, the application flow of the form component structure refers to fig. 3.
In this embodiment, the code execution flow of the form component structure refers to fig. 4.
In this embodiment, the structural diagram of the form component structure is referred to fig. 5.
In the prior art, the declaration type service of the declaration form is characterized by more fields, and each field has own data type, check rule and input mode. When writing a form component structure, a conventional developer needs to write handwritten HTML labels in a row-to-row manner according to field documents, then carries out data initialization and complicated regular check expressions for each field, and finally configures a response method of events (focus events, defocus events, carriage return events and the like) for each field independently.
Form component architecture in some embodiments referring to fig. 5, list manipulation functions configured by the form component 2 include at least: add, delete, and modify functions to the list.
The list operation functions configured by the short list body component 3 include at least: addition, deletion, modification, ordering, movement, insertion, duplication, and distribution (specific field value duplication) functions to the list.
The form body component 2 and the short form body component 3 of the form component structure add a plurality of practical list operations, such as copying, inserting, moving, distributing, exchanging and the like, so that the generated forms are more convenient to perform the list operations.
The form component structure in some embodiments,
The form verification component 5 is specifically configured to verify values of all fields in the form configuration data obtained by parsing according to the regular expression converted by the header component 1, and output a verification result;
The form verification component 5 is further configured to perform a remote background verification when all values of the fields pass and a remote verification interface is configured.
The form component structure in some embodiments,
The status bar component 4 is specifically configured to display a newly-built, edited or saved status according to a change condition of form data when the form data changes in a generated status of the form;
displaying a verification failure state when the verification result output by the form verification component 5 is verification failure;
The form disabled state is displayed when the form is disabled.
Preferably, five states of new (blue), in-edit (yellow), saved (green), failed verification (red) and disabled (gray) are set in the status bar component 4.
The new state is initially established, and when the form data is changed or verification fails, the status bar component 4 automatically enters an editing state or verification failure state.
The form verification component 5 performs front-end verification on the values of all the fields according to the verification rule, if the field values failing to verify exist, the status bar component 4 displays that the form status is changed to fail to verify (red), and the input frame ground color and the text corresponding to the form are also changed to red.
After the form configuration is completed and saved, the status bar component 4 automatically enters the saved (green) state.
When the contents of the edited form are too much, it is necessary for the user to know the current state of the form in real time, and a state management mechanism is creatively added for the form component structure in the embodiment, so that five states of newly added, edited, completed, failed in verification and disabled are defined, and the form component structure performs real-time conversion on the states by monitoring all form data in real time without human intervention.
The form component structure in some embodiments,
The output value of the header assembly 1 is a data object containing a plurality of key value pairs;
the output values of the table body component 2 and the short table body component 3 are a list containing a plurality of data objects.
The header component 1 is a core component, and its output value is a data object containing a plurality of key value pairs. The table body component 2 and the short table body component 3 output values are a list containing a plurality of data objects, which refer to the header component 1 for adding or editing a single data object.
It is to be understood that the same or similar parts in the above embodiments may be referred to each other, and that in some embodiments, the same or similar parts in other embodiments may be referred to.
It should be noted that in the description of the present application, the terms "first," "second," and the like are used for descriptive purposes only and are not to be construed as indicating or implying relative importance. Furthermore, in the description of the present application, unless otherwise indicated, the meaning of "plurality" means at least two.
Any process or method descriptions in flow charts or otherwise described herein may be understood as representing modules, segments, or portions of code which include one or more executable instructions for implementing specific logical functions or steps of the process, and further implementations are included within the scope of the preferred embodiment of the present application in which functions may be executed out of order from that shown or discussed, including substantially concurrently or in reverse order, depending on the functionality involved, as would be understood by those reasonably skilled in the art of the present application.
It is to be understood that portions of the present application may be implemented in hardware, software, firmware, or a combination thereof. In the above-described embodiments, the various steps or methods may be implemented in software or firmware stored in a memory and executed by a suitable instruction execution system. For example, if implemented in hardware, as in another embodiment, may be implemented using any one or combination of the following techniques, as is well known in the art: discrete logic circuits having logic gates for implementing logic functions on data signals, application specific integrated circuits having suitable combinational logic gates, programmable Gate Arrays (PGAs), field Programmable Gate Arrays (FPGAs), and the like.
Those of ordinary skill in the art will appreciate that all or a portion of the steps carried out in the method of the above-described embodiments may be implemented by a program to instruct related hardware, where the program may be stored in a computer readable storage medium, and where the program, when executed, includes one or a combination of the steps of the method embodiments.
In addition, each functional unit in the embodiments of the present application may be integrated in one processing module, or each unit may exist alone physically, or two or more units may be integrated in one module. The integrated modules may be implemented in hardware or in software functional modules. The integrated modules may also be stored in a computer readable storage medium if implemented in the form of software functional modules and sold or used as a stand-alone product.
The above-mentioned storage medium may be a read-only memory, a magnetic disk or an optical disk, or the like.
In the description of the present specification, a description referring to terms "one embodiment," "some embodiments," "examples," "specific examples," or "some examples," etc., means that a particular feature, structure, material, or characteristic described in connection with the embodiment or example is included in at least one embodiment or example of the present application. In this specification, schematic representations of the above terms do not necessarily refer to the same embodiments or examples. Furthermore, the particular features, structures, materials, or characteristics described may be combined in any suitable manner in any one or more embodiments or examples.
While embodiments of the present application have been shown and described above, it will be understood that the above embodiments are illustrative and not to be construed as limiting the application, and that variations, modifications, alternatives and variations may be made to the above embodiments by one of ordinary skill in the art within the scope of the application.
Claims (8)
1. A form assembly structure, comprising:
the meter comprises a meter head component, a meter body component, a short meter body component, a status bar component and a form checking component;
the status bar component is a public component, and the header component, the body component and the short body component both refer to the status bar component;
the form verification component is a public component, and the header component, the table body component and the short table body component both refer to the form verification component;
The header component is configured with a field configuration file analysis function;
the table body component refers to the table head component and is configured with a field configuration file analysis function and a list operation function;
The short table body component refers to the table head component and is configured with a field configuration file analysis function and a list operation function;
the header component is used for analyzing the input field configuration file and generating a form header according to the form configuration data obtained by analysis;
The table body component is used for analyzing the input field configuration file and generating a table body and an editable list operation item according to the table configuration data obtained by analysis;
The short table body component is used for analyzing the input field configuration file and generating a short table body of a table and an editable list operation item according to the table configuration data obtained by analysis;
the form verification component is used for verifying values of all fields in the form configuration data obtained through analysis and outputting a verification result;
The status bar component is used for displaying the generation status of the form and the verification result output by the form verification component;
The meter head assembly, the meter body assembly and the short meter body assembly are also provided with a form state initialization function;
the meter head assembly, the meter body assembly and the short meter body assembly are also used for initializing data in the assembly according to the analyzed form configuration data;
the header assembly is also provided with an event configuration function;
the header component is further used for binding the event for the form page element and configuring an event processing mechanism according to the analyzed form configuration data.
2. The form component structure of claim 1, wherein,
The header component is also provided with a default value configuration function;
and the header component configures a function based on the default value, and configures default values for each field according to the analyzed form configuration data.
3. The form component structure of claim 2, wherein,
The gauge outfit component is also provided with a verification rule configuration function;
and the header component further converts the document verification rule in the form configuration data obtained through analysis into a regular expression based on the verification rule configuration function.
4. The form component structure of claim 1, wherein,
The list operation function of the table body component configuration at least comprises the following steps: add, delete, and modify functions to the list.
5. The form component structure of claim 1, wherein,
The list operation function of the short list body component configuration at least comprises: addition, deletion, modification, ordering, movement, insertion, duplication, and distribution functions to the list.
6. The form component structure of claim 3, wherein,
The form verification component is specifically configured to verify values of all fields in the form configuration data obtained by parsing according to the regular expression converted by the header component, and output a verification result;
The form verification component is further configured to perform remote background verification when all values of the fields pass verification and a remote verification interface is configured.
7. The form component structure of claim 1, wherein,
The status bar component is specifically used for displaying newly-built, edited or saved status according to the change condition of the form data when the form data changes in the generation status of the form;
Displaying a verification failure state when the verification result output by the form verification component is verification failure;
The form disabled state is displayed when the form is disabled.
8. The form component structure of claim 1, wherein,
The output value of the header component is a data object containing a plurality of key value pairs;
The output values of the table body component and the short table body component are a list containing a plurality of data objects.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011268086.8A CN112380477B (en) | 2020-11-13 | 2020-11-13 | Form assembly structure |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011268086.8A CN112380477B (en) | 2020-11-13 | 2020-11-13 | Form assembly structure |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN112380477A CN112380477A (en) | 2021-02-19 |
| CN112380477B true CN112380477B (en) | 2024-04-30 |
Family
ID=74583911
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011268086.8A Active CN112380477B (en) | 2020-11-13 | 2020-11-13 | Form assembly structure |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112380477B (en) |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1662011A (en) * | 2004-02-27 | 2005-08-31 | 捷讯研究有限公司 | System and method for building component applications using metadata defined mapping between message and data domains |
| EP1571560A2 (en) * | 2004-03-03 | 2005-09-07 | Microsoft Corporation | Assisted form filling |
| CN102063306A (en) * | 2011-01-06 | 2011-05-18 | 夏春秋 | Technical implementation method for application development through electronic form |
| CN110109979A (en) * | 2018-01-16 | 2019-08-09 | 北京京东尚科信息技术有限公司 | A kind of allocation list radio button method and apparatus |
| CN110232173A (en) * | 2018-03-06 | 2019-09-13 | 福建天泉教育科技有限公司 | List configuration method and its system based on configurableization list engine |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20040268229A1 (en) * | 2003-06-27 | 2004-12-30 | Microsoft Corporation | Markup language editing with an electronic form |
-
2020
- 2020-11-13 CN CN202011268086.8A patent/CN112380477B/en active Active
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1662011A (en) * | 2004-02-27 | 2005-08-31 | 捷讯研究有限公司 | System and method for building component applications using metadata defined mapping between message and data domains |
| EP1571560A2 (en) * | 2004-03-03 | 2005-09-07 | Microsoft Corporation | Assisted form filling |
| CN102063306A (en) * | 2011-01-06 | 2011-05-18 | 夏春秋 | Technical implementation method for application development through electronic form |
| CN110109979A (en) * | 2018-01-16 | 2019-08-09 | 北京京东尚科信息技术有限公司 | A kind of allocation list radio button method and apparatus |
| CN110232173A (en) * | 2018-03-06 | 2019-09-13 | 福建天泉教育科技有限公司 | List configuration method and its system based on configurableization list engine |
Also Published As
| Publication number | Publication date |
|---|---|
| CN112380477A (en) | 2021-02-19 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN102754072B (en) | Regulation user interface element | |
| US9754059B2 (en) | Graphical design verification environment generator | |
| CN101996131A (en) | Automatic test method and automatic test platform for graphic user interface (GUI) based on x extensive makeup language (XML) packaging key word | |
| US7127641B1 (en) | System and method for software testing with extensible markup language and extensible stylesheet language | |
| US8122428B2 (en) | Methods and apparatus for automation and facilitating design of register maps | |
| JP2006506710A (en) | Method and apparatus for disassembling and verifying configurable hardware | |
| US7747942B2 (en) | System and method for obtaining a markup language template through reversing engineering | |
| CN109032577B (en) | Data simulation method | |
| CN103493013A (en) | Graphically based method for developing connectivity drivers | |
| CN105117215A (en) | Development method and device of automobile function | |
| CN115495069B (en) | Model-driven coal industry software process implementation method, device and equipment | |
| CN112380477B (en) | Form assembly structure | |
| US8230353B2 (en) | Iterative development of services from WSDL | |
| US6970816B1 (en) | Method and system for efficiently generating parameterized bus transactions | |
| CN112632938A (en) | Form generation method and device and controller | |
| Wing et al. | Unintrusive ways to integrate formal specifications in practice | |
| US7770113B1 (en) | System and method for dynamically generating a configuration datasheet | |
| Kaliappan et al. | Improving consistency of uml diagrams and its implementation using reverse engineering approach | |
| Behrens et al. | Requirements analysis and prototyping using scenarios and statecharts | |
| Dranidis et al. | Formal modelling of use cases with X-machines | |
| JP5208891B2 (en) | Hybrid model simulation apparatus and method | |
| US7882487B2 (en) | Method of generating C code on the basis of UML specifications | |
| CN111190872B (en) | Inheritable and extensible data processing method and application thereof to analysis log | |
| Bastl et al. | A Design Flow and EDA-Tool for an Automated Implementation of ASIC Configuration Interfaces | |
| EP1208426A2 (en) | Hierarchically structured control information editor |
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 |