CN112965717A - Front-end deployment system and method for integrated deployment of multiple systems and keeping interface uniform - Google Patents
Front-end deployment system and method for integrated deployment of multiple systems and keeping interface uniform Download PDFInfo
- Publication number
- CN112965717A CN112965717A CN202110301474.XA CN202110301474A CN112965717A CN 112965717 A CN112965717 A CN 112965717A CN 202110301474 A CN202110301474 A CN 202110301474A CN 112965717 A CN112965717 A CN 112965717A
- Authority
- CN
- China
- Prior art keywords
- module
- deployment
- product
- interface
- management
- 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 27
- 238000007726 management method Methods 0.000 claims abstract description 53
- 238000011161 development Methods 0.000 claims abstract description 19
- 230000008569 process Effects 0.000 claims abstract description 13
- 230000006870 function Effects 0.000 claims description 24
- 230000010354 integration Effects 0.000 claims description 10
- 230000003993 interaction Effects 0.000 claims description 10
- 238000010276 construction Methods 0.000 claims description 6
- 230000003213 activating effect Effects 0.000 claims description 2
- 238000005538 encapsulation Methods 0.000 claims description 2
- 230000002452 interceptive effect Effects 0.000 abstract description 4
- 230000018109 developmental process Effects 0.000 description 16
- 238000005516 engineering process Methods 0.000 description 5
- 238000010586 diagram Methods 0.000 description 4
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 238000012356 Product development Methods 0.000 description 1
- 230000006399 behavior Effects 0.000 description 1
- 230000009286 beneficial effect Effects 0.000 description 1
- 230000008859 change Effects 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 230000004927 fusion Effects 0.000 description 1
- 230000008676 import Effects 0.000 description 1
- 238000012423 maintenance Methods 0.000 description 1
- 238000004519 manufacturing process Methods 0.000 description 1
- 230000007246 mechanism Effects 0.000 description 1
- 230000033772 system development Effects 0.000 description 1
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
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- General Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Human Computer Interaction (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Stored Programmes (AREA)
Abstract
The invention relates to a front-end deployment system and a front-end deployment method for integrated deployment of multiple systems and keeping interface uniformity, belonging to the field of computer front-end application; the problems that a subsystem lacks a uniform technical chassis, a uniform basic component is lacked, and when the subsystem is integrally deployed, the theme styles cannot be rapidly switched and the consistent interactive experience cannot be ensured are solved; the system comprises a bottom layer front end frame, an open source library module, a product public component module, a customized page module, a product system module, a system management module, a theme module and a delivery project module; defining main variables deployed at the front end by using a bottom front end framework, compiling a style by a customized page module, accessing system management, determining the data state of each interface, and completing integrated deployment and keeping the front end deployment process of unified interfaces; the invention supports independent development, independent operation and independent deployment, allows the function of customized development, and supports the switching of interface theme styles on the premise of not changing any requirement.
Description
Technical Field
The invention discloses a front-end deployment system and a front-end deployment method for integrated deployment of multiple systems and keeping interface uniformity, in particular relates to a front-end deployment system which can complete front-end deployment of multiple interfaces in a unified manner, and belongs to the field of computer front-end application.
Background
At the beginning of the web, the web page mainly provides the function of a document, and people only move much knowledge and documents to the internet, so that the web page mainly provides the function of browsing and reading, and the complexity of a website system is relatively simple.
In the 2.0 period of the web, with the continuous development of the technology of the website, especially the development of JavaScript and CSS and the progress of ajax technology, the functions of the website are more and more enriched, the website not only provides the browsing function, but also provides a great deal of interaction, better access experience is brought to the user, and meanwhile, the complexity of webpage development is greatly increased.
A complex website system often has tens of thousands or even hundreds of thousands of lines of page codes, and usually consists of a great number of webpage modules, and a plurality of development teams usually exist, and each team comprises a plurality of developers. Thus providing a device capable of: different services are split into different subsystems, different teams independently develop the different services, meanwhile, a set of development and interface specifications are followed, finally, fusion deployment is carried out, and a website architecture capable of rapidly changing theme styles according to customer requirements is very necessary.
Software projects of intelligent transportation are often composed of a plurality of independent subsystems, and interfaces, logics and the like between the systems are independent and separated. In the product development phase, different subsystems are developed by different business teams. The subsystems may be delivered independently or multiple subsystems and customized functions may be delivered together as a large project.
The existing iframe embedding scheme: the production system is independently developed, operated and deployed, but is embedded in an iframe mode used in the form of integrated delivery. The scheme has the advantages that: the product systems are completely separated and do not influence each other, and the integrated deployment is very simple; the disadvantages are that: interaction, interface and experience are difficult to be consistent, and blank gaps exist during system switching.
Micro front-end scheme based on single-spa open source library: single-spa is a solution that allows for the system-integrated deployment of multiple front-end technology developments. The scheme has the advantages that: the development technology of the subsystem is irrelevant, and the subsystem can be independently developed, operated and deployed; the disadvantages are that: a uniform interface chassis framework is not provided, and the experience and interaction consistency of subsystems is difficult to achieve.
As can be seen from the above description, although the existing technology can achieve independent development and deployment of each subsystem, and can also achieve integrated deployment, theme styles, interactive experiences and the like of the integrated deployment cannot be consistent, and when different projects are deployed, the theme styles cannot be changed, for the following reasons:
the subsystems lack a uniform technical chassis, a uniform basic component and a uniform theme style specification, and when the subsystems are integrally deployed, the theme styles cannot be rapidly switched, and the consistency of interactive experience and the like cannot be guaranteed.
Disclosure of Invention
In order to solve the problems that a subsystem lacks a uniform technical chassis, lacks a uniform basic component, lacks a uniform theme style specification, cannot realize rapid theme style switching during integrated deployment, and cannot ensure consistent interactive experience, the invention provides a front-end deployment system and a method for multi-system integrated deployment and keeping uniform interfaces, wherein the scheme is as follows:
the first scheme is as follows: the system comprises a bottom layer front end frame, an open source library module, a product common component module, a customized page module, a product system module, a system management module, a theme module and a delivery project module;
the bottom layer front end frame module and the open source library module form a front end deployed foundation structure;
the product public component module comprises a plurality of product public components;
the customized page module comprises a plurality of project pages, and a plurality of product system modules are specified through the customized page module;
the system management module is responsible for login and related functions of the user;
the theme module is responsible for defining a style variable and customizing a style;
and the delivery project module is responsible for finally realizing multi-system integrated deployment and keeping front-end deployment with uniform interface.
Further, the bottom front section frame module takes a front end frame vue as a core, and comprises functions of board card routing management, data state management, ui frame construction, chart generation, two-dimensional map construction and three-dimensional map construction;
and the bottom layer front end framework and the open source library module are subjected to secondary development and encapsulation to obtain a unified ui specification, a unified interaction specification, a public function library and a basic component.
Furthermore, the delivery item module provides final integration for the customized page module, the product system module, the system management module and the theme module, and enables a user to view the module presentation content at any time in the process of operating the system.
Furthermore, the product system module comprises functions of data state management, routing page judgment and parameter customization construction.
Further, the related functions of the system management module include prompting user information, menu, button, data authority control, and user, role, menu and log management.
Further, the theme module includes style variables less and js variable definitions, ui framework theme definitions, map style definitions, and project customization style definition functions.
Scheme II: a front-end deployment method for integrated deployment of multiple systems and keeping interfaces uniform is realized on the basis of the system, and comprises the following specific steps:
step one, using the bottom layer front end frame, the open source library module and the product public component module to define main variables deployed at the front end;
secondly, compiling the theme variable obtained in the first step through the customized page module;
activating the system management module, and simultaneously accessing the system management by the user;
step four, determining the data state of each interface through the product system module, and implementing product system integration deployment;
and fifthly, utilizing the theme module to finally confirm the interface, and completing the integrated deployment and keeping the unified front-end deployment process of the interface.
Further, in step three, the user access system management process is subdivided into:
step three, system management introduction is executed, and system management is placed in a single code warehouse;
step two, carry out the route registration of system management, register the relevant route of system management through the route configuration;
and step three, registering the system management state aiming at the user.
Further, in step four, the product system module determines the data state and deployment process of each interface to be detailed as follows:
step four, entering system configuration product system information;
step two, judging whether to enter a product system or not according to the routing prefix;
step four, judging whether the targetApp function is empty or not, indicating that the targetApp function belongs to a product system, and executing script mounting product routing of the loaded product and registering product state data; otherwise, loading the product project script to mount the product route and the registration state data, and finishing and prompting the success of entering the system.
Compared with the prior art, the invention has the following beneficial effects:
the invention realizes seamless integrated deployment of a plurality of independent subsystems based on independent development and independent deployment of product projects, and can also integrate deployment and support the switching of interface theme styles. The method has the following advantages:
(1) the product system supports independent development, independent operation and independent deployment;
(2) the product system can be packaged together for integrated deployment and integrated delivery;
(3) integrated delivery projects, allowing for customized development functionality;
(4) the integrated delivered item supports the switching of the interface theme style on the premise that the product system does not need any change.
Drawings
FIG. 1 is a front-end deployment system architecture diagram for integrated deployment of multiple systems and maintaining interface uniformity;
FIG. 2 is a flowchart of a system page generation product directory;
FIG. 3 is a schematic diagram of a front-end deployment system loading process for integrated deployment of multiple systems and keeping interfaces uniform;
FIG. 4 is a flow diagram of a method for front-end deployment with integrated deployment of multiple systems and maintaining interface uniformity;
FIG. 5 is an exemplary diagram of a front-end deployment system interface for integrated deployment and interface uniformity maintenance for multiple systems.
Detailed Description
The following description of the embodiments of the present invention is provided with reference to the accompanying drawings:
the first embodiment is as follows: a front-end deployment system for integrated deployment of multiple systems and keeping uniform interfaces comprises a bottom-layer front-end frame, an open source library module, a product common component module, a customized page module, a product system module, a system management module, a theme module and a delivery project module; firstly, a bottom layer front end frame module and an open source library module are utilized to form a front end deployed foundation structure; then, the product public component module comprises a plurality of product public components, the customized page module comprises a plurality of project pages, and the customized page module standardizes a plurality of product system modules;
in addition, the system management module is responsible for login and related functions of users, finally, the theme module is responsible for defining style variables and customizing styles, the delivery project module is responsible for finally realizing multi-system integrated deployment and keeping front-end deployment with uniform interfaces, and the modules are as shown in the attached drawing 1.
The second embodiment is as follows: a front-end deployment method for integrated deployment of multiple systems and keeping interfaces uniform is concretely implemented as follows:
1. technical implementation mode
1.1 topic variables define:
in src/global/style/the/var.less, the subject variable is defined using the less language, and the execution core code is as follows:
@color-primary:#21a7ed;
@small-font-size:12px;
@color-text-default:#fff;
@color-success:#67C23A;
@color-warning:#ffc600;
@color-danger:#F56C6C;
@color-info:#909399;
1.2 subject variable compilation style:
(1) a new document extensions-skin.less is created under src/global/style, as follows:
(2) in the webpack configuration, pages of a less-loader are defined, src/global/style is added, so that extensions-skin.less files can be found during webpack compiling, and the service style code is written in the following form:
thereby enabling compilation of theme styles
1.3 system management access:
a. system management introduction, system management is placed in a separate git code warehouse and installed in a dependency in the form of npm introduced git, and the specific operation is that the dependency field in a package json file is added:
”system-manager”:
"git+http://git.xxx.cc:/system-manager/system-manager.git#master"
b. the system management route registration registers the relevant route of the system management through route configuration:
import SystemManager from"system-manager";
let routeConfig=[SystemManager.getRouterConfig()];
export defaulr routeConfig;
c. and (3) system management state registration:
1.4 product system integration deployment: firstly, executing product independent engineering; then establishing a project env file and configuring a style path; and secondly, executing: run built-mode system; finally, outputting the product catalog to a system page;
1.5 product system loading process:
s1, entering a system;
s2, judging whether the retaining wall routing prefix is a product item or not, if so, executing S3, and if not, directly finishing and prompting that the entry into the system is successful;
s3, loading a product project script;
s4, hanging the routing and registering state data, completing and prompting the success of entering the system;
the core code of the process is as follows:
A. configuring product system information:
let applicationConfig=[{
path:'/product/',
umdName:'__PRODUCT__',
storeNamespace:product,
manifest:isDev?`http://127.0.0.1:4000/manifest.json`:
'./product/manifest.json',
}]
B. judging whether to enter a product system or not according to the route
let targetApp=applicationConfig.find(item=>{
return currentRoutePath.indexOf(item.path)!=-1;
});
If targetApp is not empty, the script that represents belonging to the product system and needs to load the product mounts the product routing and registers the product status data:
the third concrete implementation mode:
2. constructing an integrated deployment and keeping an interface uniform front-end deployment specific process:
2.1 the bottom layer front end framework and the engineering framework are unified:
the bottom layer framework takes a front end framework vue of a hot door as a core, routing management is vue-router, data state management is vuex, ui framework element-ui, chart echarts, two-dimensional map leaf-let and three-dimensional map mapbox-gl. The development of each block must be based on the above underlying framework. The source code engineering for project development must also follow a uniform engineering architecture.
2.2, establishing interaction and style specifications, developing a general basic component and establishing a component specification:
the specification includes at least: style specification, interaction specification, component usage specification. The style is developed by using a less framework, the style specification is embodied as a series of defined less variables in engineering, and each less variable has a detailed use scene description. Interaction specifications mainly refer to specifications of some common interaction behaviors. The universal basic components are developed, the use scenes of each component are specified, and for some similar scenes, unified components must be used in an agreed mode.
2.3 framework building of integration projects:
the integration project is a standard vue project, but adds a mechanism for loading subsystems, which is detailed as follows:
(1) the user enters a system page;
(2) judging whether the page belongs to a subsystem or not, if so, executing (3), if not, directly executing (5) and prompting that the page entering the system is successful;
(3) judging whether a subsystem is loaded or not, if so, directly executing (5), and if not, executing (4);
(4) loading a routing and data state management script of the subsystem;
(5) and completing and prompting that the system page is successfully entered.
2.4 general system management integration:
the system management module belongs to a business logic independent module, is developed and maintained by a special team, can be integrated in each delivery project, and also needs to follow a series of specifications defined above. The functions generally include: user management, role management, menu management, rights management, log management, and the like.
2.5 product system development and integration:
the product system is developed using a special engineering architecture. The special points are mainly as follows:
based on the output customization of webpack, the functions of a product system are exposed to a window object by using a libraryTarget, and a project engineering can obtain a routing and data state management object of a sub-engineering through the window object so as to be integrated into the project engineering;
to achieve seamless integration, some constraints on source code development are provided, including: the method comprises the steps of contract of partial global variables, catalog contract of style compiling, contract of routing path and state module names, use contract of public libraries and the like.
The subsystems developed according to the engineering architecture can be seamlessly integrated into the project engineering.
2.6 customized Page development:
the delivery items generally include at least customized pages such as a top page and a login page. The customized page is placed in a project delivered project, belongs to a specific page of the project, has no universality, and only needs to follow an interaction specification. It may have its own unique pattern.
2.7 interface theme style customization:
based on the style less variables defined above, by customizing the values of these variables, the overall interface style can be modified after the project is compiled and integrated. Meanwhile, a set of global special styles are compiled aiming at the delivery project, and some standard styles are covered, so that the purpose of customizing styles is achieved, and a better delivery effect is achieved.
It should be understood by those skilled in the art that the foregoing embodiments are merely for clearly illustrating the present invention and are not to be construed as limiting the scope of the present invention. It is possible for the person skilled in the art to freely combine changes or modifications according to the requirements in accordance with the steps disclosed in the present invention, but these changes or modifications are still within the scope of the present invention.
Claims (9)
1. A front-end deployment system for integrated deployment of multiple systems and keeping interfaces uniform is characterized in that: the system comprises a bottom layer front end frame, an open source library module, a product public component module, a customized page module, a product system module, a system management module, a theme module and a delivery project module;
the bottom layer front end frame module and the open source library module form a front end deployed foundation structure;
the product public component module comprises a plurality of product public components;
the customized page module comprises a plurality of project pages, and a plurality of product system modules are specified through the customized page module;
the system management module is responsible for login and related functions of the user;
the theme module is responsible for defining a style variable and customizing a style;
and the delivery project module is responsible for finally realizing multi-system integrated deployment and keeping front-end deployment with uniform interface.
2. The front-end deployment system for integrated deployment of multiple systems and maintaining interface uniformity of claim 1, wherein: the bottom front section frame module takes a front end frame vue as a core and comprises the functions of board card routing management, data state management, ui frame construction, chart generation, two-dimensional map establishment and three-dimensional map establishment;
and the bottom layer front end framework and the open source library module are subjected to secondary development and encapsulation to obtain a unified ui specification, a unified interaction specification, a public function library and a basic component.
3. The multi-system integrated deployment and interface unification front-end deployment system of claim 2, wherein: the delivery item module provides final integration for the customized page module, the product system module, the system management module and the theme module, and enables a user to check the module presentation content at any time in the process of operating the system.
4. The multi-system integrated deployment and interface unification front-end deployment system of claim 3, wherein: the product system module comprises functions of data state management, route page judgment and parameter customization construction.
5. The multi-system integrated deployment and interface unification front-end deployment system of claim 3, wherein: the related functions of the system management module comprise prompting user information, menu, button and data authority control, and user, role, menu and log management.
6. The multi-system integrated deployment and interface unification front-end deployment system of claim 3, wherein: the theme module comprises style variable less and js variable definitions, ui frame theme definitions, map style definitions and project customization style definition functions.
7. A front-end deployment method for integrated deployment of multiple systems and keeping interfaces uniform, which is implemented based on the system of any one of claims 1-6, characterized in that: the specific method comprises the following steps:
step one, using the bottom layer front end frame, the open source library module and the product public component module to define main variables deployed at the front end;
secondly, compiling the theme variable obtained in the first step through the customized page module;
activating the system management module, and simultaneously accessing the system management by the user;
step four, determining the data state of each interface through the product system module, and implementing product system integration deployment;
and fifthly, utilizing the theme module to finally confirm the interface, and completing the integrated deployment and keeping the unified front-end deployment process of the interface.
8. The method for front-end deployment with integrated deployment and interface unification of multiple systems of claim 7, wherein: in step three, the management process of the user access system is detailed as follows:
step three, system management introduction is executed, and system management is placed in a single code warehouse;
step two, carry out the route registration of system management, register the relevant route of system management through the route configuration;
and step three, registering the system management state aiming at the user.
9. The method for front-end deployment with integrated deployment and interface unification of multiple systems of claim 7, wherein: in step four, the product system module determines the data state and deployment process of each interface to be detailed as follows:
step four, entering system configuration product system information;
step two, judging whether to enter a product system or not according to the routing prefix;
step four, judging whether the targetApp function is empty or not, indicating that the targetApp function belongs to a product system, and executing script mounting product routing of the loaded product and registering product state data; otherwise, loading the product project script to mount the product route and the registration state data, and finishing and prompting the success of entering the system.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN202110301474.XA CN112965717A (en) | 2021-03-22 | 2021-03-22 | Front-end deployment system and method for integrated deployment of multiple systems and keeping interface uniform |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
CN202110301474.XA CN112965717A (en) | 2021-03-22 | 2021-03-22 | Front-end deployment system and method for integrated deployment of multiple systems and keeping interface uniform |
Publications (1)
Publication Number | Publication Date |
---|---|
CN112965717A true CN112965717A (en) | 2021-06-15 |
Family
ID=76278267
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
CN202110301474.XA Pending CN112965717A (en) | 2021-03-22 | 2021-03-22 | Front-end deployment system and method for integrated deployment of multiple systems and keeping interface uniform |
Country Status (1)
Country | Link |
---|---|
CN (1) | CN112965717A (en) |
Cited By (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN115658084A (en) * | 2022-11-09 | 2023-01-31 | 华润数字科技有限公司 | Web front-end architecture and page deployment method, device, equipment and medium thereof |
CN117950661A (en) * | 2023-11-20 | 2024-04-30 | 易方达基金管理有限公司 | UI generation method and device |
CN117950661B (en) * | 2023-11-20 | 2024-08-02 | 易方达基金管理有限公司 | UI generation method and device |
Citations (9)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN103605527A (en) * | 2013-12-06 | 2014-02-26 | 普元信息技术股份有限公司 | System and method for realizing cloud computing application interface integration and unified style display |
CN104133675A (en) * | 2014-07-15 | 2014-11-05 | 国家电网公司 | Distribution network multi-theme application interface integrating method based on dynamic configuration technology |
CN105657053A (en) * | 2016-03-04 | 2016-06-08 | 浪潮软件集团有限公司 | SOA architecture-based data integration exchange platform |
CN105893014A (en) * | 2015-12-08 | 2016-08-24 | 乐视云计算有限公司 | Project development method and system for front end |
CN109325203A (en) * | 2018-09-10 | 2019-02-12 | 北京亚鸿世纪科技发展有限公司 | The device of Web system visualization multiplexing is realized in a kind of automation |
CN109656617A (en) * | 2018-11-30 | 2019-04-19 | 武汉烽火信息集成技术有限公司 | A kind of front end Web Service dispositions method, storage medium, electronic equipment and system |
CN111090823A (en) * | 2019-12-23 | 2020-05-01 | 广州市百果园信息技术有限公司 | Integration platform of page application and application access method, device and equipment |
US20200211692A1 (en) * | 2018-12-31 | 2020-07-02 | GE Precision Healthcare, LLC | Facilitating artificial intelligence integration into systems using a distributed learning platform |
CN112114784A (en) * | 2020-09-21 | 2020-12-22 | 广东电网有限责任公司电力科学研究院 | Single-Spa-based front-end micro-service system |
-
2021
- 2021-03-22 CN CN202110301474.XA patent/CN112965717A/en active Pending
Patent Citations (9)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN103605527A (en) * | 2013-12-06 | 2014-02-26 | 普元信息技术股份有限公司 | System and method for realizing cloud computing application interface integration and unified style display |
CN104133675A (en) * | 2014-07-15 | 2014-11-05 | 国家电网公司 | Distribution network multi-theme application interface integrating method based on dynamic configuration technology |
CN105893014A (en) * | 2015-12-08 | 2016-08-24 | 乐视云计算有限公司 | Project development method and system for front end |
CN105657053A (en) * | 2016-03-04 | 2016-06-08 | 浪潮软件集团有限公司 | SOA architecture-based data integration exchange platform |
CN109325203A (en) * | 2018-09-10 | 2019-02-12 | 北京亚鸿世纪科技发展有限公司 | The device of Web system visualization multiplexing is realized in a kind of automation |
CN109656617A (en) * | 2018-11-30 | 2019-04-19 | 武汉烽火信息集成技术有限公司 | A kind of front end Web Service dispositions method, storage medium, electronic equipment and system |
US20200211692A1 (en) * | 2018-12-31 | 2020-07-02 | GE Precision Healthcare, LLC | Facilitating artificial intelligence integration into systems using a distributed learning platform |
CN111090823A (en) * | 2019-12-23 | 2020-05-01 | 广州市百果园信息技术有限公司 | Integration platform of page application and application access method, device and equipment |
CN112114784A (en) * | 2020-09-21 | 2020-12-22 | 广东电网有限责任公司电力科学研究院 | Single-Spa-based front-end micro-service system |
Non-Patent Citations (2)
Title |
---|
樊彩棣: "基于A架构的多***集成高 校 资 产管理***的设计与实现", 中国知网, 16 December 2019 (2019-12-16) * |
胡首, 陈定方, 陶德馨: "基于J2EE和PDM的企业应用集成研究和应用", 武汉理工大学学报(交通科学与工程版), no. 03, 30 June 2004 (2004-06-30) * |
Cited By (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN115658084A (en) * | 2022-11-09 | 2023-01-31 | 华润数字科技有限公司 | Web front-end architecture and page deployment method, device, equipment and medium thereof |
CN117950661A (en) * | 2023-11-20 | 2024-04-30 | 易方达基金管理有限公司 | UI generation method and device |
CN117950661B (en) * | 2023-11-20 | 2024-08-02 | 易方达基金管理有限公司 | UI generation method and device |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
Yu et al. | A framework for rapid integration of presentation components | |
CN110020307B (en) | Drawing method and device for client end view | |
US8839192B2 (en) | System and method for presentation of cross organizational applications | |
CN101777004B (en) | Method and system for realizing BPEL sub-process multiplexing based on template in service-oriented environment | |
US7836119B2 (en) | Distributed execution model for cross-organizational declarative web applications | |
KR100995592B1 (en) | Method and Apparatus for Embedded System Design using Target Independent Model | |
CN114510231A (en) | Application construction method, device, equipment and computer readable storage medium | |
Linaje et al. | A method for model based design of rich internet application interactive user interfaces | |
Rodríguez-Echeverría et al. | Modernization of legacy web applications into rich internet applications | |
CN103646023A (en) | Page and control increasing method based on WEB | |
CN112965717A (en) | Front-end deployment system and method for integrated deployment of multiple systems and keeping interface uniform | |
Miravet et al. | Framework for the declarative implementation of native mobile applications | |
CN112068879B (en) | Method and device for constructing client application program development framework based on configuration | |
CN115113850A (en) | Cross-platform application construction and operation method, server, terminal and system | |
CN112631563A (en) | System development method and device based on framework, computer equipment and storage medium | |
Fujima | Building a meme media platform with a JavaScript MVC framework and HTML5 | |
CN116909553A (en) | Page online development and local compiling operation system | |
Sabraoui et al. | A MDA-based model-driven approach to generate GUI for mobile applications | |
Ruiz | Mastering Android Application Development | |
Gupta et al. | Creating website as a service using web components | |
Korva | Developing a web application with Angular 2: Graphical editor for Happywise’s Cove Trainer | |
CN113608726B (en) | Code generation method, device, electronic equipment and storage medium | |
Anderson et al. | Adaptation: the Continuing Evolution of the New York Public Library’s Digital Design System | |
CN118363581A (en) | Visual large screen management method, device, program product, equipment and medium | |
Freudenstein et al. | A workflow-driven approach for the efficient integration of web services in portals |
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 |