CN115033235A - System and method for flexibly multiplexing web page based on low-code development platform - Google Patents
System and method for flexibly multiplexing web page based on low-code development platform Download PDFInfo
- Publication number
- CN115033235A CN115033235A CN202210756228.8A CN202210756228A CN115033235A CN 115033235 A CN115033235 A CN 115033235A CN 202210756228 A CN202210756228 A CN 202210756228A CN 115033235 A CN115033235 A CN 115033235A
- Authority
- CN
- China
- Prior art keywords
- page
- component
- metadata
- rendering
- multiplexing
- 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
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/36—Software reuse
-
- 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)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Human Computer Interaction (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The invention discloses a system and a method for flexibly multiplexing web pages based on a low-code development platform, belonging to the technical field of program development and comprising the following steps: s1, establishing a web page through the visual design end, and storing the page metadata of the web page to the server end; s2, acquiring page metadata of the server through the deployment terminal to obtain a page view; s3, according to the page view multiplexing required by the user, triggering the assembly binding event to obtain an event script example; and S4, carrying out data interaction between page views according to the event script instance call. The method and the device enable the original static metadata to have the characteristic of dynamic use, provide basic support for multiplexing rendering and event isolation operation of all components in the page by combining the generated page metadata instance and the calling API method, and can realize flexible multiplexing interaction of the web page in a low-code development platform.
Description
Technical Field
The invention belongs to the technical field of program development, and particularly relates to a system and a method for flexibly multiplexing web pages based on a low-code development platform.
Background
In the low-code development platform, each web page is designed by visual drag of a component template, the components contain a complete set of event or method configuration definitions, and the web pages are a component template set and are usually driven by JSON metadata. At present, low-code development platforms are all designed in a single page, information of another page cannot be flexibly multiplexed and displayed in the page, and data can only flow in the single page.
The design mode of the low-code development platform is single in use, flexible data interaction cannot be carried out on a complex page structure, and the maintenance and the change of all the components stacked in one page are difficult. In addition, in some special components or service scenarios, one information page is inevitably displayed by event-triggered embedded multiplexing in another page, and no related technology exists so far to solve the problem that the same page can be flexibly multiplexed for data interaction in a low-code development platform:
1. for example, the tab page component may need to dynamically add content for which the designed page is displayed as a tab.
2. For example, different rows of the data table component require expansion of the display detail view.
3. For example, new or edited events require the same external dialog box operator form information to be opened.
Disclosure of Invention
Aiming at the defects in the prior art, the system and the method for flexibly multiplexing the web page based on the low-code development platform solve the problem that the low-code development platform cannot flexibly interact data on a general page structure with a data transmission function.
In order to achieve the purpose of the invention, the invention adopts the technical scheme that: a system for flexibly multiplexing web pages based on a low-code development platform comprises a visual design end, a server end and a deployment end which are connected in sequence;
the visual design end is used for generating a web page; the server is used for storing page metadata of the web page, and the deployment end is used for rendering the page.
Further, the method comprises the following steps: the visual design end is specifically a low-code development platform which is provided with a web page component library; the web page component library includes a number of components.
The beneficial effects of the above further scheme are: the low-code platform can independently develop a management end for designing a system web page, and can quickly generate the development platform of the application program without coding or with a small amount of codes.
Further: the deployment end comprises a back-end rendering service module and a front-end rendering framework;
the back-end rendering service module is used for generating an instance of page metadata and a rendering batch number; the front-end rendering framework is used to render instances of the page metadata and component templates into a page view.
A method for flexibly multiplexing web pages based on a low code development platform of a system for flexibly multiplexing web pages based on the low code development platform comprises the following steps:
s1, establishing a web page through the visual design end, and storing the page metadata of the web page to the server end;
s2, acquiring page metadata of the server through the deployment terminal to obtain a page view;
s3, according to the page view multiplexing required by the user, triggering the assembly binding event to obtain an event script instance;
and S4, carrying out data interaction between the page views according to the event script instance call.
Further: the step S1 includes the following sub-steps:
s11, selecting a designated component to establish a web page in a dragging mode based on the components in the web page component library of the visual design end;
s12, configuring metadata of the assembly based on the assembly of the web page to obtain page metadata;
wherein the page metadata includes a first identification ID and all component metadata including building a web page, each of the component metadata including a second identification ID, a component type, a style definition, an attribute definition, an event definition, and a method definition;
the component type is used for associating a packaged component template to perform data binding rendering, the style is used for defining a rendering style script of the component, and the event is used for defining a linkage operation event which can be triggered by the component; the method is used for defining a built-in processing callback method of the component.
The beneficial effects of the above further scheme are: and performing operations such as style adjustment, component attribute configuration, interactive event script definition and the like according to the service requirements of the user, and generating the web page.
Further: the step S2 includes the following sub-steps:
s21, calling a back-end rendering service module according to the page metadata to generate a page metadata instance;
and S22, calling a front-end rendering frame according to the page metadata instance to generate a page view.
Further: in step S21, the generated page metadata instance has a rendering batch number, and the generating method specifically includes:
processing the second identification ID of each component metadata in the page metadata through a rear-end rendering service module to generate a rendering batch number;
the step S22 specifically includes: and according to the components in the page metadata example, designating the rendered components through component syntax tags of a front-end rendering frame, and dynamically binding the component metadata corresponding to the designated rendered components with the component template to generate the page view.
Further: the step S3 specifically includes:
and based on the fact that a user needs to reuse a specified page view, triggering a component binding event, acquiring a rendering batch number of page metadata, and calling the rendering batch number and an event ID through a rear-end rendering service module to perform event script query to obtain an event script example.
Further, the method comprises the following steps: the step S4 specifically includes:
s41, triggering a page interaction event according to the event script example, and calling a back-end rendering service module to request a sub-page for association multiplexing;
s42, rendering the page metadata examples of the multiplexed sub-pages through a front-end rendering frame; and returning a first identification ID in the sub-page metadata;
s43, determining the component of the first identification ID corresponding to the second identification ID in the event script according to the returned first identification ID, and backfilling page data according to the mounting method of data interaction of the determined component to realize data interaction of the page view.
Further: in step S4, the data interaction mounting method specifically includes:
acquiring a data mount KEY value, creating an interactive mount object, caching the mount object on a root instance object of an Vue root container component, issuing the mount object as a KEY value subject message to an interactive component embedded in a page, and judging whether the interactive component is created;
if yes, immediately executing a mount interaction method according to the KEY value theme message received by the interaction component, and updating the executed identification state;
if not, asynchronously initializing and creating the interactive component, acquiring the data mount KEY value of the interactive component, inquiring Vue mount objects cached on root instance objects of the root container components, and executing a mount interactive method and updating the executed identification state when the mount objects exist.
The invention has the beneficial effects that:
(1) according to the method, identification ID rule variables capable of being calculated and managed are added to conventional metadata of a design page, so that the original static metadata has the characteristic of dynamic use, and a page metadata example, a component event script example and a calling API method which are generated by a back-end rendering service module are combined, so that basic support is provided for multiplexing rendering and event isolation operation of all components in the page, and flexible multiplexing interaction of the web page can be realized in a low-code development platform.
(2) According to the invention, through carrying out data interaction on the web page, the general flexibility of the page data model can be enhanced, the data structure of the whole page is not too bloated, the management and maintenance become simpler, and the functional design requirements of more web systems can be met.
Drawings
FIG. 1 is a system framework diagram for flexible multiplexing of web pages based on a low code development platform.
FIG. 2 is a flowchart of a method for flexibly multiplexing web pages based on a low-code development platform.
Detailed Description
The following description of the embodiments of the present invention is provided to facilitate the understanding of the present invention by those skilled in the art, but it should be understood that the present invention is not limited to the scope of the embodiments, and it will be apparent to those skilled in the art that various changes may be made without departing from the spirit and scope of the invention as defined and defined in the appended claims, and all matters produced by the invention using the inventive concept are protected.
Example 1:
as shown in fig. 1, in an embodiment of the present invention, a system for flexibly multiplexing a web page based on a low-code development platform includes a visual design end, a service end, and a deployment end, which are connected in sequence;
the visual design end is used for generating a web page; the server is used for storing page metadata of the web page; and the deployment terminal is used for carrying out view binding rendering on the instance of the page metadata and the component template.
The visual design end is specifically a low-code development platform which is provided with a web page component library; the web page component library includes a number of components.
In this embodiment, the low-code development platform is a development platform that can generate an application program quickly without coding or with a small amount of code.
The deployment end comprises a back-end rendering service module and a front-end rendering framework;
the back-end rendering service module is used for generating an example of page metadata; the front-end rendering framework is used for rendering the page metadata and the component templates into a page view.
Example 2:
the embodiment is directed to an implementation method of a system for flexibly multiplexing web pages based on a low-code development platform.
As shown in fig. 2, a method for flexibly multiplexing web pages based on a low-code development platform includes the following steps:
s1, establishing a web page through the visual design end, and storing the page metadata of the web page to the server end;
s2, acquiring page metadata of the server through the deployment terminal to obtain a page view;
s3, according to the page view multiplexing required by the user, triggering the assembly binding event to obtain an event script example;
and S4, carrying out data interaction between page views according to the event script instance call.
The step S1 includes the following sub-steps:
s11, selecting a designated component to establish a web page in a dragging mode based on the components in the web page component library of the visual design end;
the component type is used for performing data binding rendering by associating with a packaged component template, the style is used for defining a rendering style script of the component, and the event is used for defining a linkage operation event which can be triggered by the component; the method is used for defining a built-in processing callback method of the component.
In this embodiment, when a user designs a management system page, a design page needs to be newly built in a data file directory of a visual design end, and after the design page is opened, a suitable component is selected for drag design.
When a user designs a data table with an expansion row, a table component needs to be dragged and placed in a design page, and the attribute of a table column object needs to be configured.
When a user designs a new adding/editing button and clicks and pops up an external dialog box to maintain a form information interface, the new adding/editing button needs to be dragged and placed in a main operation page, and then the form information content is independently designed in a dialog box design page.
S12, configuring metadata of the assembly based on the assembly of the web page to obtain page metadata;
the page metadata comprises a first identification ID and all component metadata for establishing the web page, and each component metadata comprises a second identification ID, a component type, a style definition, an attribute definition, an event definition and a method definition;
the first identification ID of the page metadata is BatchNo, the whole page can be kept to be globally unique when the batch number of the rendered BatchNo is multiplexed, and any sub-component in the page can quickly acquire the root page object rendered in the same batch. The UUID in the BatchNo _ UUID of the second identification ID is used for keeping the component to be globally unique during dragging design, and the separator is used for acquiring a rendering batch number and distinguishing the component during rendering processing of the front end.
The first identifier of the invention is used for keeping the rendering batch number BatchNo globally unique when the whole page is multiplexed, the second identifier is used for keeping the UUID globally unique when the component is dragged, and the separator is used for acquiring the rendering batch number and distinguishing the component when the front end performs rendering processing. And the page root container identifier ID is only the rendering batch number BatchNo, so that any sub-component in the page can quickly acquire the root page object rendered in the same batch.
In this embodiment, when a management system page is configured, a metadata attribute of a menu item of a menu component needs to be configured, the metadata attribute is bound with a menu component template and displayed as a menu selection item, then a menu item selection event of the menu component continues to be configured, a user-defined method for adding a tab to a public new tab is called in a processing script of the event, and a page address dynamic request of a selected menu item is generated into a metadata instance and rendered and displayed in a corresponding tab area.
When a data form with an expansion row is configured, embedding address attributes of multiplexing pages expanded by form component rows into detailed information pages which are independently designed in advance, then configuring a form row expansion event, defining a data interaction processing script embedded into the multiplexing pages, traversing all form element component identifications ID in the expanded detailed pages by the processing script, and then referring to a user-defined data mounting method to carry out assignment and backfill data operation on the form element components.
Configuring a click event script of a button assembly when a newly added/edited button is configured to click and pop up an external dialog box to maintain a form information interface, defining and popping up a separately designed target dialog box page in the script, adding event execution logic before popup window triggering, and backfilling and assigning value to newly added/edited form data when the component in the dialog box is initialized by calling a data mounting and rendering method; and then, configuring a click event of a submission button in the dialog box form, adding a step script for calling a service interface to process form data, and caching interface request return data into step variables.
The step S2 includes the following sub-steps:
s21, calling a back-end rendering service module according to the page metadata to generate a page metadata instance;
and S22, calling the front-end rendering frame according to the page metadata instance to generate a page view.
In step S21, the generated page metadata instance has a rendering batch number, and the generating method specifically includes:
processing the second identification ID of each component metadata in the page metadata through a rear-end rendering service module to generate a rendering batch number;
in this embodiment, the main page has already called the backend service to uniformly generate the rendering batch number batchnos of the first identifier IDs of all the components (excluding the multiplexed sub-page) during rendering, and when the sub-page is multiplexed, the backend service also needs to be called to generate the rendering batch number batchnos of the sub-page. The flow of multiplexing and rendering the sub-pages comprises the following steps: accessing a home page address; requesting a homepage surface element data template; returning a page metadata instance of the main page rendering batch number and rendering; requesting to render a sub-page metadata instance; and returning the page metadata instance of the sub-page rendering batch number and rendering.
The step S22 specifically includes: and according to the components in the page metadata example, designating the rendered components through component syntax tags of a front-end rendering framework, and dynamically binding the component metadata corresponding to the designated rendered components with the component template to generate the page view.
The usage of the component grammar tag is as follows: rendering a meta-component as a dynamic component, and determining that a component is rendered according to the is value; the is value is a string that can be either the HTML tag name or the component name.
The step S3 specifically includes:
based on the fact that a user needs to multiplex a specified page view, a component binding event is triggered, a first identification ID of page metadata is obtained, an event ID is obtained by intercepting a prefix, a rendering batch number and the event ID are called through a rear-end rendering service module to conduct event script query, and an event script instance is obtained.
In this embodiment, the method for triggering the main page data list row expansion event includes:
the user triggers a line expansion event bound by a data list, calls a back-end service request line to expand a related multiplexing sub-page, the front end renders the sub-page metadata instance of the multiplexing sub-page (after the front end rendering is finished, related component objects are cached and managed so as to be used by a second identification ID of component metadata in the following, calls an event script defined by the back-end service request line expansion, and declares an event script instance of a data list rendering batch (when an event definition calling component method is arranged in the main page, only components belonging to the same batch can be operated, a first identification ID rendering batch number BatchNo of component reference page metadata in the event script needs to be synchronously updated), data mount parameter transmission needs to be carried out through a UUID suffix of the component identification ID); and in the process of initializing and rendering each form component in the sub-page, performing a data mounting method to perform data backfill binding display.
The step S4 specifically includes:
s41, triggering a page interaction event according to the event script example, and calling a back-end rendering service module to request a sub-page for association multiplexing;
s42, rendering the page metadata instance of the multiplexed sub-page through a front-end rendering frame; and returning a first identification ID in the sub-page metadata;
s43, determining the component of the first identification ID corresponding to the second identification ID in the event script according to the returned first identification ID, and backfilling page data according to the mounting method of data interaction of the determined component to realize data interaction of the page view.
In step S4, the data interaction mounting method specifically includes:
acquiring a data mount KEY value, creating an interactive mount object, caching the mount object on a root instance object of an Vue root container component, issuing the mount object as a KEY value subject message to an interactive component embedded in a page, and judging whether the interactive component is created;
if yes, immediately executing a mount interaction method according to the KEY value theme message received by the interaction component, and updating the executed identification state;
if not, asynchronously initializing and creating the interactive component, acquiring the data mount KEY value of the interactive component, inquiring Vue mount objects cached on root instance objects of the root container components, and executing a mount interactive method and updating the executed identification state when the mount objects exist.
The data interaction method for the data table with the development rows comprises the following specific steps:
and carrying out data backfill processing on the detailed information page in the event script of the line expansion of the table, calling a rear-end rendering service module to obtain a page metadata example corresponding to the expanded page address in the event, transmitting the example data to the event script as a JSON parameter, so that a user can traverse all the second identification ID information of the components of the detailed information page and the attribute values of the line data object of the table associated with the components, and processing backfill assignment of the components in the detailed information page by calling a page data mounting method.
The data interaction method for maintaining the form information interface by clicking and popping up the external dialog box by the newly added/edited button specifically comprises the following steps:
when the new adding/editing button pops up the external common dialog box, if data of the main page need to be transmitted, interaction needs to be carried out through a data mounting method, the whole main page Vue root container component is taken as a father container component of the external dialog box embedded page by default, and the second identification ID of the root container component of the main page is embedded into the UUID suffix of the interactive component.
When the event script triggers the data mounting method, the second identification ID of the direct father container component of the mounting point is transmitted to the father container component instance object, the mounting KEY value temporarily stored by the father container component object is obtained to serve as an iterative service data KEY value, the transmitted UUID suffix of the embedded interactive component is intercepted, and the data mounting KEY value is generated.
The invention has the beneficial effects that: according to the method, identification ID rule variables which can be calculated and managed are added to conventional metadata of a design page, so that the original static metadata has the characteristic of dynamic use, and a page metadata example, a component event script example and an API calling method which are generated by a back-end rendering service module are combined, so that basic support is provided for multiplexing rendering and event isolation operation of all components in the page, and flexible multiplexing interaction of the web page can be realized in a low-code development platform.
The invention can enhance the general flexibility of the page data model by carrying out data interaction on the web page, ensures that the data structure of the whole page is not bloated any more, has simpler management and maintenance, and can meet the design requirements of more web system functions.
In the description of the present invention, it is to be understood that the terms "center", "thickness", "upper", "lower", "horizontal", "top", "bottom", "inner", "outer", "radial", and the like, indicate orientations and positional relationships based on the orientations and positional relationships shown in the drawings, and are used merely for convenience in describing the present invention and for simplicity in description, and do not indicate or imply that the referenced devices or elements must have a particular orientation, be constructed and operated in a particular orientation, and thus, are not to be construed as limiting the present invention. Furthermore, the terms "first," "second," and "third" are used for descriptive purposes only and are not to be construed as indicating or implying relative importance or an implicit indication of the number of technical features. Thus, features defined as "first", "second", "third" may explicitly or implicitly include one or more of the features.
Claims (10)
1. A system for flexibly multiplexing web pages based on a low-code development platform is characterized by comprising a visual design end, a service end and a deployment end which are sequentially connected;
the visual design end is used for generating a web page; the server is used for storing page metadata of the web page; the deployment terminal is used for rendering pages.
2. The system for flexibly multiplexing the web page based on the low-code development platform as claimed in claim 1, wherein the visualization design end is specifically a low-code development platform, which is provided with a web page component library; the web page component library includes a number of components.
3. The system for flexible multiplexing of web pages based on a low-code development platform according to claim 2, wherein the deployment end comprises a back-end rendering service module and a front-end rendering framework;
the back-end rendering service module is used for generating an instance of page metadata and a rendering batch number; the front-end rendering framework is used to render instances of the page metadata and component templates into a page view.
4. A method for flexibly multiplexing web pages based on a low code development platform of a system for flexibly multiplexing web pages based on a low code development platform according to any one of claims 1 to 3, comprising the following steps:
s1, establishing a web page through the visual design end, and storing the page metadata of the web page to the server end;
s2, acquiring page metadata of the server through the deployment terminal to obtain a page view;
s3, according to the page view multiplexing required by the user, triggering the assembly binding event to obtain an event script instance;
and S4, carrying out data interaction between page views according to the event script instance call.
5. The method for web page flexible multiplexing based on low code development platform of claim 4, wherein the step S1 comprises the following sub-steps:
s11, selecting a designated component to establish a web page in a dragging mode based on the components in the web page component library of the visual design end;
s12, configuring metadata of the assembly based on the assembly of the web page to obtain page metadata;
wherein the page metadata includes a first identification ID and all component metadata including a build web page, each of the component metadata including a second identification ID, a component type, a style definition, an attribute definition, an event definition, and a method definition;
the component type is used for associating a packaged component template to perform data binding rendering, the style is used for defining a rendering style script of the component, and the event is used for defining a linkage operation event which can be triggered by the component; the method is used for defining a built-in processing callback method of the component.
6. The method for web page flexible multiplexing based on low code development platform of claim 4, wherein the step S2 comprises the following sub-steps:
s21, calling a back-end rendering service module according to the page metadata to generate a page metadata instance;
and S22, calling a front-end rendering frame according to the page metadata instance to generate a page view.
7. The method for flexibly multiplexing the web page based on the low-code development platform according to claim 6, wherein in the step S21, the generated page metadata instance is provided with a rendering batch number, and the generation method specifically comprises:
processing the second identification ID of each component metadata in the page metadata through a rear-end rendering service module to generate a rendering batch number;
the step S22 specifically includes: and according to the components in the page metadata example, designating the rendered components through component syntax tags of a front-end rendering framework, and dynamically binding the component metadata corresponding to the designated rendered components with the component template to generate the page view.
8. The method for flexibly multiplexing web pages based on a low code development platform according to claim 7, wherein the step S3 specifically comprises:
and based on the fact that a user needs to reuse a specified page view, triggering a component binding event, acquiring a rendering batch number of page metadata, and calling the rendering batch number and an event ID through a rear-end rendering service module to perform event script query to obtain an event script example.
9. The method for flexibly multiplexing web pages based on a low code development platform according to claim 8, wherein the step S4 specifically comprises:
s41, triggering a page interaction event according to the event script example, and calling a back-end rendering service module to request a sub-page for association multiplexing;
s42, rendering the page metadata instance of the multiplexed sub-page through a front-end rendering frame; and returning a first identification ID in the sub-page metadata;
s43, determining the component of the first identification ID corresponding to the second identification ID in the event script according to the returned first identification ID, and backfilling page data according to the mounting method of data interaction of the determined component to realize data interaction of the page view.
10. The method for flexibly multiplexing the web page based on the low code development platform as claimed in claim 9, wherein in the step S4, the mounting method of the data interaction specifically comprises:
acquiring a data mount KEY value, creating an interactive mount object, caching the mount object on a root instance object of an Vue root container component, issuing the mount object as a KEY value subject message to an interactive component embedded in a page, and judging whether the interactive component is created;
if yes, immediately executing a mount interaction method according to the KEY value theme message received by the interaction component, and updating the executed identification state;
and if not, asynchronously initializing and creating the interactive component, acquiring the data mount KEY value of the interactive component, inquiring Vue mount objects cached on root instance objects of the root container components, executing a mount interactive method when the mount objects exist, and updating the executed identification state.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210756228.8A CN115033235A (en) | 2022-06-30 | 2022-06-30 | System and method for flexibly multiplexing web page based on low-code development platform |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210756228.8A CN115033235A (en) | 2022-06-30 | 2022-06-30 | System and method for flexibly multiplexing web page based on low-code development platform |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN115033235A true CN115033235A (en) | 2022-09-09 |
Family
ID=83126366
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202210756228.8A Pending CN115033235A (en) | 2022-06-30 | 2022-06-30 | System and method for flexibly multiplexing web page based on low-code development platform |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN115033235A (en) |
Cited By (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115775622A (en) * | 2023-02-10 | 2023-03-10 | 成都瑞华康源科技有限公司 | Visualization method based on port configuration of operating room equipment set |
| CN115841102A (en) * | 2022-12-30 | 2023-03-24 | 深圳市金政软件技术有限公司 | Method, device, equipment and storage medium for generating dynamic data report |
| CN115964075A (en) * | 2022-12-28 | 2023-04-14 | 苏州峰之鼎信息科技有限公司 | Application export and import method and device, computer equipment and storage medium |
| CN116560637A (en) * | 2023-04-13 | 2023-08-08 | 珠海沃德尔软件科技有限公司 | Method and system for developing application system in configuration form for digital transformation |
-
2022
- 2022-06-30 CN CN202210756228.8A patent/CN115033235A/en active Pending
Cited By (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115964075A (en) * | 2022-12-28 | 2023-04-14 | 苏州峰之鼎信息科技有限公司 | Application export and import method and device, computer equipment and storage medium |
| CN115964075B (en) * | 2022-12-28 | 2024-03-01 | 苏州峰之鼎信息科技有限公司 | Application export import method and device, computer equipment and storage medium |
| CN115841102A (en) * | 2022-12-30 | 2023-03-24 | 深圳市金政软件技术有限公司 | Method, device, equipment and storage medium for generating dynamic data report |
| CN115775622A (en) * | 2023-02-10 | 2023-03-10 | 成都瑞华康源科技有限公司 | Visualization method based on port configuration of operating room equipment set |
| CN115775622B (en) * | 2023-02-10 | 2023-04-21 | 成都瑞华康源科技有限公司 | Visualization method based on port configuration of operating room equipment set |
| CN116560637A (en) * | 2023-04-13 | 2023-08-08 | 珠海沃德尔软件科技有限公司 | Method and system for developing application system in configuration form for digital transformation |
| CN116560637B (en) * | 2023-04-13 | 2023-10-20 | 珠海沃德尔软件科技有限公司 | Method and system for developing application system in configuration form for digital transformation |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN115033235A (en) | System and method for flexibly multiplexing web page based on low-code development platform | |
| CN109840429B (en) | Intelligent contract deployment and calling method and device | |
| US7219305B2 (en) | Mark-up language implementation of graphical or non-graphical user interfaces | |
| US8166396B2 (en) | User interface rendering | |
| US20050198646A1 (en) | Method, data processing device, computer program product and arrangement for processing electronic data | |
| US20070078925A1 (en) | Porting an interface defining document between mobile device platforms | |
| KR20090127158A (en) | Service program generation technology | |
| EP2587371A1 (en) | Improved configuration of a user interface for a mobile communications terminal | |
| CN115826963A (en) | Process event development multiplexing method and system based on low-code development platform | |
| CN109240697B (en) | Call processing method and device and storage medium | |
| CN110297636A (en) | A kind of automatic production of HTML page and parameter management method based on page configuration file, system and device | |
| CN110297624B (en) | Implementation method of Widget system based on electron framework and television adopting system | |
| CN111068328A (en) | Game advertisement configuration table generation method, terminal device and medium | |
| CN112394931A (en) | Static page configuration optimization control method and device for front-end page | |
| US20050188295A1 (en) | Systems and methods for an extensible administration tool | |
| CN105516333A (en) | Interactive method and system based on webpage | |
| CN101147128A (en) | Method to automate resource management in computer applications | |
| CN115061685A (en) | Interface element positioning method of software client, electronic device and storage medium | |
| EP2924565A1 (en) | Web-application-launch application programming interface | |
| CN110941471A (en) | Method and device for internationalizing basic data of software system | |
| JP2007128166A (en) | Network system, server, client, program, web browsing function achieving method | |
| CN107977277B (en) | Method and device for integrating third-party system in ERP system and computer equipment | |
| US7213033B2 (en) | Automatically populating an application's working directory with files having a specified type from other directory locations | |
| CN111124386B (en) | Animation event processing method, device, equipment and storage medium based on Unity | |
| CN113504898A (en) | Front-end component rapid processing method, system and computer storage medium for realizing business arrangement |
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 |