CN117435836A - Front-end page splicing method and system based on centralized management of database - Google Patents
Front-end page splicing method and system based on centralized management of database Download PDFInfo
- Publication number
- CN117435836A CN117435836A CN202311395345.7A CN202311395345A CN117435836A CN 117435836 A CN117435836 A CN 117435836A CN 202311395345 A CN202311395345 A CN 202311395345A CN 117435836 A CN117435836 A CN 117435836A
- Authority
- CN
- China
- Prior art keywords
- component
- model
- parameter
- parameters
- reading
- 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.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 38
- 238000009877 rendering Methods 0.000 claims abstract description 19
- 125000004122 cyclic group Chemical group 0.000 claims description 20
- 230000001174 ascending effect Effects 0.000 claims description 5
- 230000001351 cycling effect Effects 0.000 claims description 5
- 238000010586 diagram Methods 0.000 description 12
- 238000011161 development Methods 0.000 description 3
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 230000009286 beneficial effect Effects 0.000 description 1
- 238000012790 confirmation Methods 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 238000012423 maintenance Methods 0.000 description 1
- 238000005457 optimization Methods 0.000 description 1
- 239000007787 solid Substances 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
- 238000012360 testing method Methods 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
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/90—Details of database functions independent of the retrieved data types
- G06F16/901—Indexing; Data structures therefor; Storage structures
- G06F16/9017—Indexing; Data structures therefor; Storage structures using directory or table look-up
-
- 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/901—Indexing; Data structures therefor; Storage structures
- G06F16/9027—Trees
-
- 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
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Databases & Information Systems (AREA)
- General Engineering & Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Software Systems (AREA)
- Data Mining & Analysis (AREA)
- Human Computer Interaction (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The invention provides a front-end page splicing method and a system based on centralized management of a database, wherein the method comprises the following steps: acquiring component information, and loading the component information onto a directory tree; when the component information has corresponding records in the component configuration detail model, reading the component model, the parameter model and the relation model of the components and the parameters to conduct parameter rendering of a single component, reading specific data of the parameters corresponding to the component ID in the component configuration detail model and updating, reading the component catalog model and conducting content updating of a catalog tree; and when the component information does not have corresponding records in the component configuration detail model, reading the component model, the parameter model and the relation model of the component and the parameter to conduct parameter rendering of the single component. According to the front-end page splicing method and system based on the centralized management of the database, the front-end page is spliced by reading the component model, the parameter model and the relation model of the component and the parameter, so that the working efficiency is greatly improved.
Description
Technical Field
The invention relates to the technical field of centralized management of databases, in particular to a front-end page splicing method and system based on centralized management of databases.
Background
The existing front-end page splicing is realized, professional front-end developers are required to develop and maintain related tools according to requirements, and then the splicing of the pages is realized based on the tools, and any optimization or modification is required to be realized by the professional front-end software developers. The prior front-end technology has higher threshold, so that not only is a solid technical foundation and development experience needed, but also the design idea and mode of the splicing platform are needed to be understood and mastered. The development and maintenance costs of the splicing tool are high and a lot of development and testing work is required.
Therefore, it is necessary to provide a front-end page splicing method and system based on centralized management of databases, which can solve the above problems.
Disclosure of Invention
Aiming at the problems and the shortcomings of the prior art, the invention provides a front-end page splicing method and a front-end page splicing system based on centralized management of a database.
The invention solves the technical problems by the following technical proposal:
the invention provides a front-end page splicing method based on centralized management of a database, which comprises the following steps:
acquiring component information, and loading the component information onto a directory tree, wherein the component information comprises a component ID;
judging whether the component information has a corresponding record in a component configuration detail model according to the component ID;
when the component information has corresponding records in the component configuration detail model, reading a component model, a parameter model and a relation model of components and parameters to conduct parameter rendering of a single component, reading specific data of the parameters corresponding to the component ID in the component configuration detail model, updating, reading a component catalog model and conducting content updating of the catalog tree;
when the component information does not have corresponding records in the component configuration detail model, reading a component model, a parameter model and a relation model of the component and the parameter to conduct parameter rendering of a single component;
and storing the component information to a component directory structure model and the component configuration detail model by taking pages as dimensions.
Preferably, the component model comprises a component framework, the component framework being stored in JSON format;
the parametric model includes a parametric code and a data format including a text box, a numeric box, a boolean value, a date, and a selection.
Preferably, the relation model of the component and the parameter comprises a relation of configuring the component parameter and a corresponding default value.
Preferably, when the parameter included in the parameter model is a cyclic parameter, the specific value of each parameter is obtained by the following method:
under the same component ID, firstly, reading AttrDtl corresponding to main data of the same parameter class, judging which parameters are contained in the AttrDtl, then searching for replacement in the cyclic parameter by using a parameter name, if the parameter name does not exist, replacing the cyclic parameter by using a NULL value, and cycling until the AttrDtl does not contain the parameters, thereby obtaining the specific value of the parameter class.
Preferably, when the parameter included in the parameter model is a non-cyclic parameter, the specific value of each parameter is obtained by the following method:
and under the same component ID, the data of the same parameter class are arranged in an ascending order, splicing is carried out according to a preset format, and different parameters of the same component ID are spliced at intervals by commas to obtain specific values of the parameter class.
Preferably, the parameters in the different frame codes are replaced by the specific values of the parameter categories, so that the complete codes of the different components are obtained.
Preferably, the complete codes of the different components are spliced in a hierarchical and ordered manner to obtain page complete codes, and a directory structure among the different components is constructed according to the component IDs, the upper-level component IDs and the ordering in the component directory model.
Preferably, the complete code of the different components is page rendered.
Preferably, the routing form supporting the fixed website splicing page coding parameter variable is displayed.
The invention also provides a front-end page splicing system based on the centralized management of the database, which comprises the following steps:
the device comprises a component information acquisition module, a storage module and a storage module, wherein the component information acquisition module is used for acquiring component information and loading the component information onto a directory tree, and the component information comprises a component ID;
the record judging module is used for judging whether the corresponding record exists in the component configuration detail model or not according to the component ID;
the first component information reading module is used for reading a component model, a parameter model and a relation model of components and parameters to conduct parameter rendering of a single component when corresponding records exist in the component configuration detail model, reading specific data of the parameters corresponding to the component ID in the component configuration detail model, updating, reading a component catalog model and conducting content updating of the catalog tree;
the second component information reading module is used for reading the component model, the parameter model and the relation model of the component and the parameter to conduct parameter rendering of the single component when the corresponding record does not exist in the component configuration detail model;
and the component information storage module is used for storing the component information to a component directory structure model and the component configuration detail model by taking pages as dimensions.
Compared with the prior art, the technical scheme of the embodiment of the invention has the following beneficial effects:
according to the method and the system for automatically generating the page codes based on the centralized management of the database, which are provided by the embodiment of the invention, the component information is acquired, the component information is loaded on a directory tree, and the component information comprises the component ID; judging whether the component information has a corresponding record in a component configuration detail model according to the component ID; when the component information has corresponding records in the component configuration detail model, reading a component model, a parameter model and a relation model of components and parameters to conduct parameter rendering of a single component, reading specific data of the parameters corresponding to the component ID in the component configuration detail model, updating, reading a component catalog model and conducting content updating of the catalog tree; when the component information does not have corresponding records in the component configuration detail model, reading a component model, a parameter model and a relation model of the component and the parameter to conduct parameter rendering of a single component; the page is used as a dimension to store the component information into a component catalog structure model and a component configuration detail model, so that the access threshold of front-end page splicing is greatly reduced, and the page splicing efficiency is greatly improved;
further, when the parameter included in the parameter model is a cyclic parameter, a specific value of each parameter is obtained by: under the same component ID, firstly, reading AttrDtl corresponding to main data of the same parameter class, judging which parameters are contained in the AttrDtl, then searching for replacement in the cyclic parameter by using a parameter name, if the parameter name does not exist, replacing the cyclic parameter by using a NULL value, and cycling until the AttrDtl does not contain the parameters, and obtaining a specific value of the parameter class, thereby effectively obtaining a specific value of each parameter;
further, when the parameter included in the parameter model is a non-cyclic parameter, a specific value of each parameter is obtained by the following method: under the same component ID, the data of the same parameter class are arranged in an ascending order, splicing is carried out according to a preset format, and different parameters of the same component ID are spliced at intervals by commas to obtain specific values of the parameter class, so that the specific value of each parameter is rapidly obtained.
Drawings
Fig. 1 is a schematic flow chart of a front-end page splicing method based on centralized management of databases according to an embodiment of the present invention;
fig. 2 is a schematic structural diagram of a front-end page splicing system based on centralized management of databases according to an embodiment of the present invention;
FIG. 3 is a schematic diagram illustrating component selection in a front-end page stitching method based on database centralized management according to an embodiment of the present invention;
FIG. 4 is a schematic diagram of component parameters in a front-end page splicing method based on centralized management of databases according to an embodiment of the present invention;
FIG. 5 is a schematic diagram of an added component in a front end page splicing method based on centralized management of databases according to an embodiment of the present invention;
FIG. 6 is another schematic diagram of a newly added component in a front end page splicing method based on centralized management of databases according to an embodiment of the present invention;
FIG. 7 is a schematic diagram of a loading template in a front end page stitching method based on database centralized management according to an embodiment of the present invention;
FIG. 8 is a schematic diagram of page loading in a front-end page stitching method based on centralized management of databases according to an embodiment of the present invention;
FIG. 9 is a schematic diagram of components in a front-end page stitching method based on centralized management of databases according to an embodiment of the present invention;
FIG. 10 is a schematic diagram illustrating component saving in a front-end page stitching method based on database centralized management according to an embodiment of the present invention;
FIG. 11 is a schematic diagram illustrating a configuration platform preview in a front end page stitching method based on database centralized management according to an embodiment of the present invention;
FIG. 12 is a schematic diagram of an input website in a front-end page splicing method based on database centralized management according to an embodiment of the present invention;
fig. 13 is a schematic diagram of parameter storage in a front-end page splicing method based on centralized management of databases according to an embodiment of the present invention.
Detailed Description
For the purpose of making the objects, technical solutions and advantages of the embodiments of the present invention more apparent, the technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present invention, and it is apparent that the described embodiments are some embodiments of the present invention, but not all embodiments of the present invention. All other embodiments, which can be made by those skilled in the art based on the embodiments of the invention without making any inventive effort, are intended to be within the scope of the invention.
The technical scheme of the invention is described in detail below by specific examples. The following embodiments may be combined with each other, and some embodiments may not be repeated for the same or similar concepts or processes.
Based on the problems existing in the prior art, as shown in fig. 1, the invention provides a front-end page splicing method based on centralized management of databases, which comprises the following steps:
step S101: and acquiring component information, and loading the component information onto a directory tree, wherein the component information comprises a component ID.
Step S102: and judging whether the corresponding record exists in the component configuration detail model according to the component ID.
Step S103: when the component information has corresponding records in the component configuration detail model, reading the component model, the parameter model and the relation model of the components and the parameters to conduct parameter rendering of a single component, reading the specific data of the parameters corresponding to the component ID in the component configuration detail model and updating, reading the component catalog model and conducting content updating of the catalog tree.
Specifically, the component model field is described below, where the component framework field stores the body framework of the component in JSON format and relates to parameter categories that remain consistent with the following parameter models, and the configuration platform reads the component models to support the user in making the selection of the component.
Component model field descriptions are specifically shown in the following table:
| field information | Annotating | Field information | Annotating |
| ID | ID | InserTime | Publication time |
| CompotCd | Component numbering | UpdateTime | Update time |
| CompotName | Component name | ||
| CompotFendInterf | Assembly frame | ||
| isEff | Whether or not to be effective |
The data format of the parameter model is mainly a data format which controls the parameter to be configurable in a configuration platform, the configuration platform clicks any component, the right side column can display parameter information related to the component, and each parameter can support the data format maintained by a user to be controlled by a ConfigFendInterf field.
The parametric model field descriptions are specifically shown in the following table:
the model can control maintainable parameters and corresponding default values which are displayed by each component correspondingly, and the number of the parameters and the default values which can be displayed by each component are controlled by the component and parameter relation model.
Component and parameter relationship model field descriptions are specifically shown in the following table:
| field information | Annotating | Field information | Annotating |
| ID | ID | InserTime | Publication time |
| CompotCd | Component code | UpdateTime | Update time |
| CompotAttr | Parameter code | ||
| Ordn | Parameter ordering | ||
| DefConfig | Default value |
Specifically, the component configuration detail model field descriptions are specifically shown in the following table:
| field information | Annotating | Field information | Annotating |
| ID | ID | CompotId | Component ID |
| PageNo | Page coding | AttrDtl | Parameter value |
| CompotCd | Component code | InserTime | Publication time |
| CompotAttr | Parameter code | UpdateTime | Update time |
| Ordn | Ordering of |
Specifically, the component catalog model field description is specifically shown in the following table:
| field information | Annotating | Field information | Annotating |
| ID | ID | CompotId | Component ID |
| PageNo | Page coding | ColuType | Column type |
| CompotCd | Component code | CataOrdn | Ordering of |
| CataName | Directory name | InserTime | Publication time |
| SuprId | Superior ID | UpdateTime | Update time |
Step S104: and when the component information does not have corresponding records in the component configuration detail model, reading the component model, the parameter model and the relation model of the component and the parameter to conduct parameter rendering of the single component.
Step S105: and storing the component information to a component directory structure model and the component configuration detail model by taking pages as dimensions.
In a specific implementation, the component model includes a component framework, the component framework being stored in JSON format;
the parametric model includes a parametric code and a data format including a text box, a numeric box, a boolean value, a date, and a selection.
In a specific implementation, the relation model of the component and the parameter includes a relation of configuring the component parameter and a corresponding default value.
In a specific implementation, when the parameter included in the parameter model is a cyclic parameter, a specific value of each parameter is obtained by the following way:
under the same component ID, firstly, reading AttrDtl corresponding to main data of the same parameter class, judging which parameters are contained in the AttrDtl, then searching for replacement in the cyclic parameter by using a parameter name, if the parameter name does not exist, replacing the cyclic parameter by using a NULL value, and cycling until the AttrDtl does not contain the parameters, thereby obtaining the specific value of the parameter class.
In a specific implementation, when the parameter included in the parameter model is a non-cyclic parameter, a specific value of each parameter is obtained by the following way:
and under the same component ID, the data of the same parameter class are arranged in an ascending order, splicing is carried out according to a preset format, and different parameters of the same component ID are spliced at intervals by commas to obtain specific values of the parameter class.
In specific implementation, the parameters in different frame codes are replaced by the specific values of the parameter categories, so that complete codes of different components are obtained.
In specific implementation, the complete codes of the different components are subjected to hierarchical and ordering splicing to obtain page complete codes, and a directory structure among the different components is constructed according to the component IDs, the previous-stage component IDs and the ordering in the component directory model.
In a specific implementation, the complete codes of the different components are subjected to page rendering.
In the implementation, the routing form supporting the fixed website splicing page coding parameter variable is displayed.
The invention also provides a front-end page splicing system based on the centralized management of the database, which comprises the following steps:
a component information obtaining module 11, configured to obtain component information, and load the component information onto a directory tree, where the component information includes a component ID;
a record judging module 12, configured to judge whether a corresponding record exists in the component configuration detail model according to the component ID;
a first component information reading module 13, configured to, when the component information has a corresponding record in the component configuration detail model, read a component model, a parameter model, and a relation model of components and parameters, perform parameter rendering of a single component, read specific data of parameters corresponding to the component ID in the component configuration detail model, update the specific data, read a component catalog model, and update the content of the catalog tree;
a second component information reading module 14, configured to read a component model, a parameter model, and a relation model of components and parameters to perform parameter rendering of a single component when the component information does not have a corresponding record in the component configuration detail model;
and the component information storage module 15 is used for storing the component information to a component directory structure model and the component configuration detail model by taking pages as dimensions.
Referring now to fig. 5-12, the stitching of meeting room reservation pages is taken as an example:
1) First, entering the configuration platform, as shown in fig. 5, a component newly added by a right key in a blank is a component newly added in a hierarchy corresponding to the outermost layer, or as shown in fig. 6, a lower component newly added by a right key of a certain component may be selected. The loading template and page loading are the same as the newly added component, and the user can select freely. As shown in fig. 7, the loading template is to precipitate some common component combinations as a template, which can be quickly multiplexed. As shown in FIG. 8, the function of the page loading is to select the spliced page and quickly modify the configuration content.
2) As shown in fig. 9, clicking any component, the right side will display all the parameter details corresponding to the component, and divide the parameter details into several different pages according to the parameter types, and the number of the parameters displayed in the right side column, the default values corresponding to the parameters and the data format can be controlled by modifying the parameter model table of the database.
3) After the configuration is completed, as shown in fig. 10, the corresponding page code and page name are maintained, and the click confirmation can be saved.
4) As shown in fig. 11, clicking the preview of the configuration platform, or as shown in fig. 12, inputting a fixed website for displaying and using a predetermined page of the conference room. Web site: http://192.168.11.35:8095/# page/3001. Wherein 3001 is a page code, the page code is variable, and different pages can be displayed by inputting different codes.
5) As shown in fig. 13, the parameter level information of the page 3001 is already stored in the database, and all the back-end interface codes of the page can be queried only by simple SQL statements.
In summary, according to the method and the system for automatically generating the page code based on the centralized management of the database provided by the embodiment of the invention, component information is acquired, the component information is loaded on the directory tree, and the component information comprises component IDs; judging whether the component information has a corresponding record in a component configuration detail model according to the component ID; when the component information has corresponding records in the component configuration detail model, reading a component model, a parameter model and a relation model of components and parameters to conduct parameter rendering of a single component, reading specific data of the parameters corresponding to the component ID in the component configuration detail model, updating, reading a component catalog model and conducting content updating of the catalog tree; when the component information does not have corresponding records in the component configuration detail model, reading a component model, a parameter model and a relation model of the component and the parameter to conduct parameter rendering of a single component; the page is used as a dimension to store the component information into a component catalog structure model and a component configuration detail model, so that the access threshold of front-end page splicing is greatly reduced, and the page splicing efficiency is greatly improved;
further, when the parameter included in the parameter model is a cyclic parameter, a specific value of each parameter is obtained by:
under the same component ID, firstly, reading AttrDtl corresponding to main data of the same parameter class, judging which parameters are contained in the AttrDtl, then searching for replacement in the cyclic parameter by using a parameter name, if the parameter name does not exist, replacing the cyclic parameter by using a NULL value, and cycling until the AttrDtl does not contain the parameters, and obtaining a specific value of the parameter class, thereby effectively obtaining a specific value of each parameter;
further, when the parameter included in the parameter model is a non-cyclic parameter, a specific value of each parameter is obtained by the following method: under the same component ID, the data of the same parameter class are arranged in an ascending order, splicing is carried out according to a preset format, and different parameters of the same component ID are spliced at intervals by commas to obtain specific values of the parameter class, so that the specific value of each parameter is rapidly obtained.
Finally, it should be noted that: the above embodiments are only for illustrating the technical solution of the present invention, and not for limiting the same; although the invention has been described in detail with reference to the foregoing embodiments, it will be understood by those of ordinary skill in the art that: the technical scheme described in the foregoing embodiments can be modified or some or all of the technical features thereof can be replaced by equivalents; such modifications and substitutions do not depart from the spirit of the invention.
Claims (10)
1. The front-end page splicing method based on the centralized management of the database is characterized by comprising the following steps of:
acquiring component information, and loading the component information onto a directory tree, wherein the component information comprises a component ID;
judging whether the component information has a corresponding record in a component configuration detail model according to the component ID;
when the component information has corresponding records in the component configuration detail model, reading a component model, a parameter model and a relation model of components and parameters to conduct parameter rendering of a single component, reading specific data of the parameters corresponding to the component ID in the component configuration detail model, updating, reading a component catalog model and conducting content updating of the catalog tree;
when the component information does not have corresponding records in the component configuration detail model, reading a component model, a parameter model and a relation model of the component and the parameter to conduct parameter rendering of a single component;
and storing the component information to a component directory structure model and the component configuration detail model by taking pages as dimensions.
2. The method for splicing front-end pages based on centralized management of databases according to claim 1, wherein,
the component model comprises a component framework, wherein the component framework is stored in a JSON format;
the parametric model includes a parametric code and a data format including a text box, a numeric box, a boolean value, a date, and a selection.
3. The method for splicing front-end pages based on centralized management of databases according to claim 1, wherein the relation model of the components and parameters comprises the relation of configuration component parameters and corresponding default values.
4. The method for splicing front-end pages based on centralized management of databases according to claim 1, wherein when the parameters included in the parameter model are cyclic parameters, the specific value of each parameter is obtained by:
under the same component ID, firstly, reading AttrDtl corresponding to main data of the same parameter class, judging which parameters are contained in the AttrDtl, then searching for replacement in the cyclic parameter by using a parameter name, if the parameter name does not exist, replacing the cyclic parameter by using a NULL value, and cycling until the AttrDtl does not contain the parameters, thereby obtaining the specific value of the parameter class.
5. The method for splicing front-end pages based on centralized management of databases according to claim 1, wherein when the parameters included in the parameter model are non-cyclic parameters, the specific value of each parameter is obtained by:
and under the same component ID, the data of the same parameter class are arranged in an ascending order, splicing is carried out according to a preset format, and different parameters of the same component ID are spliced at intervals by commas to obtain specific values of the parameter class.
6. The method for splicing front-end pages based on centralized management of databases according to claim 4 or 5, wherein parameters in different frame codes are replaced by the specific values of the parameter categories, so as to obtain complete codes of different components.
7. The method for splicing front-end pages based on centralized management of databases according to claim 6, wherein the complete codes of different components are spliced in a hierarchical and ordered manner to obtain the complete codes of the pages, and the directory structure among different components is constructed according to the component IDs, the upper-level component IDs and the ordering in the component directory model.
8. The database centralized management-based front-end page stitching method according to claim 6, wherein the complete codes of the different components are page rendered.
9. The method for splicing front-end pages based on centralized management of databases according to claim 6, wherein the routing form supporting the encoding parameter variables of the fixed website spliced pages is displayed.
10. A front-end page stitching system based on centralized management of databases, the system comprising:
the device comprises a component information acquisition module, a storage module and a storage module, wherein the component information acquisition module is used for acquiring component information and loading the component information onto a directory tree, and the component information comprises a component ID;
the record judging module is used for judging whether the corresponding record exists in the component configuration detail model or not according to the component ID;
the first component information reading module is used for reading a component model, a parameter model and a relation model of components and parameters to conduct parameter rendering of a single component when corresponding records exist in the component configuration detail model, reading specific data of the parameters corresponding to the component ID in the component configuration detail model, updating, reading a component catalog model and conducting content updating of the catalog tree;
the second component information reading module is used for reading the component model, the parameter model and the relation model of the component and the parameter to conduct parameter rendering of the single component when the corresponding record does not exist in the component configuration detail model;
and the component information storage module is used for storing the component information to a component directory structure model and the component configuration detail model by taking pages as dimensions.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202311395345.7A CN117435836A (en) | 2023-10-25 | 2023-10-25 | Front-end page splicing method and system based on centralized management of database |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202311395345.7A CN117435836A (en) | 2023-10-25 | 2023-10-25 | Front-end page splicing method and system based on centralized management of database |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN117435836A true CN117435836A (en) | 2024-01-23 |
Family
ID=89545659
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202311395345.7A Pending CN117435836A (en) | 2023-10-25 | 2023-10-25 | Front-end page splicing method and system based on centralized management of database |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN117435836A (en) |
Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20190266225A1 (en) * | 2018-02-26 | 2019-08-29 | Servicenow, Inc. | System for Building and Modeling Web Pages |
| CN110990008A (en) * | 2019-11-28 | 2020-04-10 | 北京三快在线科技有限公司 | Method, device, storage medium and electronic equipment for updating page |
| CN111984235A (en) * | 2020-08-19 | 2020-11-24 | 上海翘腾科技有限公司 | Customizable front-end low-code development system and method |
| CN112579084A (en) * | 2020-12-17 | 2021-03-30 | 深圳集智数字科技有限公司 | Page assembling method and device |
| CN114020256A (en) * | 2021-10-29 | 2022-02-08 | 平安国际智慧城市科技股份有限公司 | Front-end page generation method, device and equipment and readable storage medium |
| CN114036425A (en) * | 2021-11-24 | 2022-02-11 | 上海哔哩哔哩科技有限公司 | Page access method, client, server and system |
| CN115617327A (en) * | 2022-11-08 | 2023-01-17 | 浙江极氪智能科技有限公司 | Low code page building system, method and computer readable storage medium |
-
2023
- 2023-10-25 CN CN202311395345.7A patent/CN117435836A/en active Pending
Patent Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20190266225A1 (en) * | 2018-02-26 | 2019-08-29 | Servicenow, Inc. | System for Building and Modeling Web Pages |
| CN110990008A (en) * | 2019-11-28 | 2020-04-10 | 北京三快在线科技有限公司 | Method, device, storage medium and electronic equipment for updating page |
| CN111984235A (en) * | 2020-08-19 | 2020-11-24 | 上海翘腾科技有限公司 | Customizable front-end low-code development system and method |
| CN112579084A (en) * | 2020-12-17 | 2021-03-30 | 深圳集智数字科技有限公司 | Page assembling method and device |
| CN114020256A (en) * | 2021-10-29 | 2022-02-08 | 平安国际智慧城市科技股份有限公司 | Front-end page generation method, device and equipment and readable storage medium |
| CN114036425A (en) * | 2021-11-24 | 2022-02-11 | 上海哔哩哔哩科技有限公司 | Page access method, client, server and system |
| CN115617327A (en) * | 2022-11-08 | 2023-01-17 | 浙江极氪智能科技有限公司 | Low code page building system, method and computer readable storage medium |
Non-Patent Citations (2)
| Title |
|---|
| 喻莹莹, 等: "前后端分离的终端自适应动态表单设计", 计算机系统应用, vol. 27, no. 4, 30 April 2018 (2018-04-30), pages 70 - 75 * |
| 赵东福, 等: "UG NX数控编程技术基础", 31 May 2007, 南京大学出版社, pages: 327 - 328 * |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US9514115B2 (en) | Method for creating form validation program and corresponding form interface according to result set metadata | |
| JP4827834B2 (en) | Method and apparatus for modifying process control data | |
| CN112650766B (en) | Database data operation method, system and server | |
| US7093207B1 (en) | Data analysis flow engine | |
| CN110543303B (en) | Visual service platform | |
| RU2406115C2 (en) | Accessing complex data | |
| CN109933311A (en) | A kind of information system creation method and relevant apparatus | |
| CN104133772A (en) | Automatic test data generation method | |
| KR20150082418A (en) | Automated report generation method | |
| EP2026222A1 (en) | Data and application model for configurable tracking and reporting system | |
| CN104715032A (en) | Mapping system and method of Chinese and English table name and field name of report system | |
| CN116028653B (en) | Method and system for constructing map by visually configuring multi-source heterogeneous data | |
| CN111126019A (en) | Report generation method and device based on mode customization and electronic equipment | |
| CN105224527A (en) | Be applicable to the general ETL method of multiple object table update mode | |
| CN117009422B (en) | Method for realizing data import by convenience business personnel | |
| CN111475602B (en) | Multi-version knowledge graph storage method and device, storage medium and electronic equipment | |
| KR101022716B1 (en) | System for generating automatically electronic document and method thereof | |
| CN117435836A (en) | Front-end page splicing method and system based on centralized management of database | |
| CN116842076A (en) | Data analysis method, device, analysis equipment and readable storage medium | |
| CN116958293A (en) | Flow chart drawing system for planning optimization software | |
| CN116756261A (en) | GIS data processing method based on relational database management tool | |
| KR100428706B1 (en) | Method for Creating Program Code Automatically Using Pattern and Component | |
| CN103678420B (en) | Method for establishing multi-dimension data set and multi-dimension data set processing device | |
| CN103177064B (en) | A kind of method automatically enrolling given content in electronic document | |
| US7814413B2 (en) | System and method for controlling web pages |
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 |