XML-based low-code development methods, devices, electronic devices, and storage media

CN122569902APending Publication Date: 2026-08-14PETROCHINA CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2025-02-12
Publication Date
2026-08-14

AI Technical Summary

Technical Problem

[0003]传统的软件开发模式,例如,全手工编码存在开发周期长、成本高昂、难以快速响应业务需求变化等问题,制约了油气行业数字化转型的步伐

Benefits of technology

[0016]本发明实施例的技术方案,通过低代码前端引擎响应于数据库建模操作,得到数据库建模数据,然后基于低代码后端引擎根据数据库建模数据,生成可扩展标记语言表单配置文件。利用低代码前端引擎将所述可扩展标记语言表单配置文件通过Web应用页面进行展示。本技术方案,通过利用可扩展标记语言的标准化和结构化特性,简化开发流程,减少手工编码工作量,以提高开发效率并降低技术门槛,从而加速Web应用的创建与部署过程,对加快油气数字化转型具有重要意义。

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN122569902A_ABST
    Figure CN122569902A_ABST
Patent Text Reader

Abstract

This invention discloses a low-code development method, apparatus, electronic device, and storage medium based on XML. The method includes: obtaining database modeling data through a low-code front-end engine responding to database modeling operations; wherein the low-code front-end engine supports various user interactive operations; generating an Extensible Markup Language (XML) form configuration file based on the database modeling data using a low-code back-end engine; wherein the low-code back-end engine provides page rendering data to the low-code front-end engine; and displaying the XML form configuration file through a web application page using the low-code front-end engine. This technical solution, by utilizing the standardized and structured characteristics of XML, simplifies the development process, reduces manual coding workload, improves development efficiency, and lowers the technical threshold, thereby accelerating the creation and deployment of web applications, which is of great significance for accelerating the digital transformation of the oil and gas industry.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This invention relates to the field of computer technology, and more particularly to XML-based low-code development methods, apparatus, electronic devices, and storage media. Background Technology

[0002] With the rapid development of information technology, the oil and gas industry is undergoing a profound digital transformation. Enterprises are investing more and more in software development, and the costs of software development and maintenance are also rising.

[0003] Traditional software development models, such as entirely manual coding, suffer from problems such as long development cycles, high costs, and difficulty in quickly responding to changes in business needs, which hinder the pace of digital transformation in the oil and gas industry. Summary of the Invention

[0004] This invention provides a low-code development method, apparatus, electronic device, and storage medium based on XML. By utilizing the standardized and structured characteristics of Extensible Markup Language (XML), it simplifies the development process, reduces manual coding workload, improves development efficiency, and lowers the technical threshold, thereby accelerating the creation and deployment of Web applications. This is of great significance for accelerating the digital transformation of oil and gas.

[0005] According to one aspect of the present invention, an XML-based low-code development method is provided, the method comprising:

[0006] The database modeling data is obtained by responding to database modeling operations through a low-code front-end engine; wherein, the low-code front-end engine is used to support various interactive operations by users;

[0007] Based on the database modeling data, the low-code backend engine generates an Extensible Markup Language (XML) form configuration file; wherein, the low-code backend engine is used to provide page rendering data to the low-code frontend engine;

[0008] The extensible markup language form configuration file is displayed through a web application page using a low-code front-end engine.

[0009] According to another aspect of the present invention, an XML-based low-code development apparatus is provided, the apparatus comprising:

[0010] The database modeling data acquisition module is used to obtain database modeling data in response to database modeling operations through a low-code front-end engine; wherein, the low-code front-end engine is used to support various interactive operations by users;

[0011] An Extensible Markup Language (XML) form configuration file generation module is used to generate an XML form configuration file based on the database modeling data from the low-code backend engine; wherein, the low-code backend engine is used to provide page rendering data to the low-code frontend engine;

[0012] The Web application page display module is used to display the Extensible Markup Language form configuration file through the Web application page using a low-code front-end engine.

[0013] According to another aspect of the present invention, an electronic device is provided, the electronic device comprising:

[0014] At least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores a computer program executable by the at least one processor, the computer program being executed by the at least one processor to enable the at least one processor to perform the XML-based low-code development method according to any embodiment of the present invention.

[0015] According to another aspect of the present invention, a computer-readable storage medium is provided, the computer-readable storage medium storing computer instructions for causing a processor to execute and implement the XML-based low-code development method according to any embodiment of the present invention.

[0016] The technical solution of this invention involves a low-code front-end engine responding to database modeling operations to obtain database modeling data. Then, a low-code back-end engine generates an Extensible Markup Language (XML) form configuration file based on this data. The low-code front-end engine then displays the XML form configuration file through a web application page. This technical solution, by leveraging the standardized and structured characteristics of XML, simplifies the development process, reduces manual coding workload, improves development efficiency, and lowers the technical barrier, thereby accelerating the creation and deployment of web applications. This is of great significance for accelerating the digital transformation of the oil and gas industry.

[0017] It should be understood that the description in this section is not intended to identify key or essential features of the embodiments of the present invention, nor is it intended to limit the scope of the invention. Other features of the invention will become readily apparent from the following description. Attached Figure Description

[0018] To more clearly illustrate the technical solutions in the embodiments of the present invention, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the accompanying drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0019] Figure 1 This is a flowchart of an XML-based low-code development method provided according to Embodiment 1 of the present invention;

[0020] Figure 2 This is a schematic diagram of the XML-based low-code development process provided in Embodiment 1 of this application;

[0021] Figure 3 This is a flowchart of the development process of the Web application system provided in Embodiment 1 of this application;

[0022] Figure 4 This is an object model diagram of the XML form provided in Embodiment 1 of this application;

[0023] Figure 5 A schematic diagram of the table provided in Embodiment 1 of this application;

[0024] Figure 6 A schematic diagram of a dialog box provided in Embodiment 1 of this application;

[0025] Figure 7 This is a schematic diagram illustrating the form control and data validation provided in Embodiment 1 of this application;

[0026] Figure 8 This is a schematic diagram of the structure of the XML-based low-code development device provided in Embodiment 2 of the present invention;

[0027] Figure 9 This is a schematic diagram of the structure of an electronic device that implements the XML-based low-code development method of this invention. Detailed Implementation

[0028] To enable those skilled in the art to better understand the present invention, the technical solutions of the present invention will be clearly and completely described below with reference to the accompanying drawings of the embodiments of the present invention. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort should fall within the scope of protection of the present invention.

[0029] It should be noted that the terms "target," etc., in the specification, claims, and accompanying drawings of this invention are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that embodiments of the invention described herein can be implemented in orders other than those illustrated or described herein. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover a non-exclusive inclusion; for example, a process, method, system, product, or apparatus that comprises a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or apparatus.

[0030] Example 1

[0031] Figure 1 This is a flowchart of an XML-based low-code development method according to Embodiment 1 of the present invention. This embodiment is applicable to improving the efficiency of Web application software development. The method can be executed by an XML-based low-code development device, which can be implemented in hardware and / or software and can be configured in a device. For example, the device can be a backend server or other device with communication and computing capabilities. Figure 1 As shown, the method includes:

[0032] S110. The database modeling data is obtained by responding to the database modeling operation through the low-code front-end engine; wherein, the low-code front-end engine is used to support users to perform various interactive operations.

[0033] In this approach, low-code is a software development methodology that enables developers to build and deploy applications more quickly by minimizing the need for manual coding. Figure 2 This is a schematic diagram of the XML-based low-code development process provided in Embodiment 1 of this application, as shown below. Figure 2 As shown, the low-code engine includes a low-code front-end engine. The low-code front-end engine is used for page rendering, data initialization, user interaction support, front-end data processing, front-end event handling, responding to user actions, calling back-end APIs, and performing data validation, all based on XML (Extensible Markup Language) descriptions.

[0034] The databases used are relational databases, including Oracle, SQL Server, and MySQL.

[0035] Specifically, Figure 3 This is a flowchart of the development process of the Web application system provided in Embodiment 1 of this application, as follows: Figure 3As shown, users perform database modeling operations through their browsers. The low-code front-end engine responds to these operations, retrieving the corresponding database modeling data. The user's browser is one of various mainstream browsers, including Chrome, Firefox, Edge, and IE, ensuring good compatibility.

[0036] Optionally, after obtaining the database modeling data, the method further includes:

[0037] The low-code front-end engine sends database modeling data to the low-code back-end engine through a standard interface.

[0038] In this plan, such as Figure 2 As shown, the low-code front-end engine and the low-code back-end engine interact with each other through a standard interface. After obtaining the database modeling data, the low-code front-end engine sends the database modeling data to the low-code back-end engine through the standard interface.

[0039] By sending database modeling data to a low-code backend engine, the database modeling data can be generated into Extensible Markup Language (XML) data. Utilizing the standardized and structured characteristics of XML, the development process can be simplified, the amount of manual coding can be reduced, thereby improving development efficiency and lowering the technical threshold. This accelerates the creation and deployment of web applications, which is of great significance for speeding up the digital transformation of oil and gas.

[0040] S120. Based on the database modeling data, the low-code backend engine generates an extensible markup language form configuration file; wherein, the low-code backend engine is used to provide page rendering data to the low-code frontend engine.

[0041] In this embodiment, as Figure 2 As shown, the low-code engine includes a low-code backend engine. The low-code backend engine is used for XML file parsing, page element construction, event handling, backend data processing, database operations, and providing supporting interfaces to the low-code frontend engine. In addition, both the low-code frontend engine and the low-code backend engine provide corresponding extension mechanisms, making it easy for developers to extend or modify existing functional components, controls, and operations based on the existing low-code engine.

[0042] The Extensible Markup Language (Extreme Markup Language) form configuration file defines all the elements required to implement a Web (Web Application) application, including page layout, functional components, form controls, user action definitions, SQL statements, and other elements.

[0043] Specifically, such as Figure 3As shown, the database modeling data is parsed based on a low-code backend engine, the corresponding SQL statements are executed, and an extensible markup language form configuration file is generated.

[0044] By using Extensible Markup Language (EXPLAIN) to define functional forms in web applications, and developing a corresponding low-code engine, the system can interpret and render the various page elements defined in the forms, and accurately execute the various operations submitted by the user. This allows software developers to implement common software functions by only modifying the XML files corresponding to the configuration forms, without writing any code or writing very little code.

[0045] Optionally, based on the database modeling data, the low-code backend engine generates an Extensible Markup Language (EXPLAIN) form configuration file, including:

[0046] Based on the modeling data in the database, generate an Extensible Markup Language (Extreme Markup Language) form;

[0047] The Extensible Markup Language (XML) form is parsed to generate an XML form configuration file.

[0048] Specifically, such as Figure 3 As shown, the database modeling data is processed based on a low-code backend engine to generate an Extensible Markup Language (XML) form. Then, the XML form is processed according to the database configuration to generate an XML form configuration file.

[0049] Leveraging the standardized and structured features of Extensible Markup Language (EXPLAIN) simplifies the development process, reduces manual coding workload, improves development efficiency, and lowers the technical threshold, thereby accelerating the creation and deployment of web applications. This is of great significance for speeding up the digital transformation of the oil and gas industry.

[0050] Optionally, the object model of the Extensible Markup Language (Extreme Markup Language) form includes a form collection and form objects; the form objects include scripts, resource sets, resources, grids, tables, controls, dialog boxes, SQL script sets, and event sets;

[0051] Wherein, the resource refers to the external links referenced in the form; the grid is used for page layout; the table is used to define table components; the dialog box is used to define dialog boxes that pop up inside the form; the SQL script set is used to define various SQL scripts, and the SQL scripts are used to define SQL statements; the event set is used to define events and actions.

[0052] Specifically, Figure 4 This is an object model diagram of the XML form provided in Embodiment 1 of this application, such as... Figure 4 As shown, multiple forms can be defined in the same XML file. Each form contains a complete form definition and corresponds to a functional page in the system.

[0053] In this embodiment, JavaScript scripts can be written in the Content property of the script object in the form, and the front-end engine is responsible for calling and executing them. When there are multiple scripts, a script collection (Scripts) object can be defined in the form.

[0054] Specifically, Figure 4 This is an object model diagram of the XML form provided in Embodiment 1 of this application, such as... Figure 4 As shown, multiple forms can be defined in the same XML file. Each form contains a complete form definition and corresponds to a functional page in the system.

[0055] In this embodiment, the script is an executable file written in a specific descriptive language according to a certain format. JavaScript scripts can be written in the Content property of the script object in the form, and are called and executed by the low-code front-end engine. When there are multiple scripts, a script collection object can be defined in the form.

[0056] In this solution, resources refer to external links that need to be referenced in the form, defined in the Content attribute. Common external resources include external scripts and external styles.

[0057] Among them, the grid is mainly used for page layout. By defining row and column attributes, it supports dividing the page into multiple areas of different sizes.

[0058] In this embodiment, Figure 5 A schematic diagram of the table provided in Embodiment 1 of this application, as shown below. Figure 5 As shown, the table is used to define table components. It supports configuration through properties to realize table controls for different needs, including whether rows can be selected, whether multiple selections are supported, whether field sorting is supported, the number of rows displayed per page, etc. At the same time, the header area (Header) object can define whether the table has custom multiple headers, the footer area (Footer) object can define additional controls to be displayed at the bottom of the table, and the toolbar object can define the table's query and operation buttons.

[0059] Furthermore, Figure 6 A schematic diagram of the dialog box provided in Embodiment 1 of this application, as shown below. Figure 6 As shown, the dialog box object is used to define the dialog box that pops up inside the form. Simple controls can be defined directly below the dialog box, or the display area of ​​the dialog box can be divided by defining a grid object to support the display of complex interfaces.

[0060] In this plan, Figure 7This is a schematic diagram illustrating the form control and data validation provided in Embodiment 1 of this application. Figure 7 As shown, controls are the basic elements in a form. Forms support defining controls under parent objects such as column objects of table components, dialog components, and grid components. Controls come in various types, including text boxes, text labels, single-choice boxes, checkboxes, dropdown lists, calendar selectors, hyperlinks, images, buttons, file selectors, password boxes, and hidden text boxes. Controls have some common properties, including name, title, style definition, default value, and operation behavior definition. For specific controls that require a data source, such as dropdown lists and checkboxes, the data source can be defined, and the front-end engine automatically obtains the data source and initializes the data based on the definition. It also supports defining validation properties for each control, supporting validation types including non-empty validation, numeric type validation, text length validation, custom mathematical formula validation, and custom regular expression validation. The low-code front-end engine and low-code back-end engine can automatically perform data validation and provide user prompts through the validation properties defined in the controls.

[0061] The SQL script collection allows for the definition of multiple SQL scripts. Each SQL script object can define an SQL statement in its Content property. SQL scripts have a category attribute to distinguish the database types they support, including Oracle, SQL Server, and MySQL. For scripts with the same identifier, multiple SQL statements for different database types can be defined simultaneously, enabling the same system to adapt to multiple databases. SQL scripts can use form controls in the format {control name}, and the backend engine will automatically assign parameters during execution.

[0062] Furthermore, the same form supports defining multiple different events through event sets, and each event supports defining multiple different actions to respond to the event. Actions can be divided into front-end actions and back-end actions. Front-end actions can be associated with a script to execute a piece of JavaScript code, while back-end actions can be associated with a SQL script, which is then executed by the back-end engine. The low-code front-end engine is responsible for event-driven execution. When cooperation from the low-code back-end engine is required, it drives the process by calling standard interfaces. After event execution is complete, the low-code front-end engine is responsible for notifying the user or providing error messages. During event execution by the low-code back-end engine, if an exception is encountered, the low-code back-end engine will automatically output file logs to facilitate troubleshooting and problem analysis for developers.

[0063] By leveraging the standardized and structured features of Extensible Markup Language (EXPLAIN), the development process can be simplified, the amount of manual coding can be reduced, development efficiency can be improved, and the technical threshold can be lowered, thereby accelerating the creation and deployment of web applications. This is of great significance for accelerating the digital transformation of the oil and gas industry.

[0064] Optionally, generate an Extensible Markup Language (EXPLAIN) form configuration file, including:

[0065] The low-code backend engine sends Extensible Markup Language (EXPLAIN) form configuration files to the low-code frontend engine via a standard interface.

[0066] In this plan, such as Figure 2 As shown, the low-code front-end engine and the low-code back-end engine interact with each other through standard interfaces. After obtaining the Extensible Markup Language (XML) form configuration file, the low-code back-end engine sends the XML form configuration file to the low-code front-end engine through the standard interface.

[0067] By sending Extensible Markup Language (EXPLAIN) form configuration files to a low-code front-end engine through a standard interface, the presentation of functional pages in a web application can be achieved, improving the efficiency of web application software development and reducing software development and maintenance costs.

[0068] S130. The Extensible Markup Language form configuration file is displayed through a web application page using a low-code front-end engine.

[0069] Specifically, such as Figure 3 As shown, the low-code front-end engine displays the operation results through web application pages based on the Extensible Markup Language (EXPLAIN) form configuration file. This enables the presentation of functional web application pages, improving web application software development efficiency and reducing software development and maintenance costs.

[0070] Optionally, the Extensible Markup Language form configuration file can be displayed through a web application page using a low-code front-end engine, including:

[0071] If the database modeling operation is successful, the extensible markup language form configuration file will be displayed through a web application page using a low-code front-end engine.

[0072] If the database modeling operation fails, the low-code front-end engine will be used to display the operation error and error message.

[0073] In this solution, the low-code front-end engine supports various interactive operations by users and allows users to submit user data and operation behaviors to the low-code back-end engine through standard interfaces. The low-code back-end engine executes the corresponding SQL statements according to the user operation definition in XML, completes the database interaction operation, and feeds back the operation results to the low-code front-end engine. The low-code front-end engine then feeds back the operation results to the user, including whether the operation was successful or failed, as well as specific error information.

[0074] By presenting functional pages in web applications, we can improve the efficiency of web application software development and reduce software development and maintenance costs.

[0075] Optionally, the method further includes:

[0076] The modified data is obtained by responding to data modification operations through a low-code front-end engine;

[0077] Based on the modified data, the low-code backend engine generates a target extensible markup language form configuration file.

[0078] The target Extensible Markup Language (XML) form configuration file is displayed through a web application page using a low-code front-end engine.

[0079] In this solution, the XML file can be modified and improved according to business needs. Specifically, data modification operations can be performed to change the corresponding data, thereby modifying the XML file.

[0080] Furthermore, you can view the display effect of the corresponding form in the development environment, and further adjust the XML file according to the display effect until it meets the user's needs.

[0081] In this embodiment, it also supports automatically generating corresponding XML based on the design of the table structure in the database, directly completing common add, delete, modify, and query operations. For more complex functions, developers can complete the development of related functions by making minor modifications and improvements based on the automatically generated XML.

[0082] Furthermore, to facilitate the rapid application of XML forms and low-code engines in the development of various web application systems, a supporting prototype system is also provided. In addition to the built-in low-code backend and frontend engines, the prototype system also possesses common basic management functions for application systems, including organizational structure management, user management, role management, function management, permission management, and system log management. It also provides basic user login, main framework, menu navigation, and user logout interfaces and operations. Developers can easily configure the prototype system to associate system function menus one-to-one with XML forms, thereby enabling the rapid application of XML forms and the low-code engine.

[0083] The technical solution of this invention involves a low-code front-end engine responding to database modeling operations to obtain database modeling data. Then, a low-code back-end engine generates an Extensible Markup Language (XML) form configuration file based on this data. The low-code front-end engine then displays the XML form configuration file through a web application page. By implementing this technical solution, common components and operations are highly encapsulated for frequently used development scenarios. This allows developers to complete the development of complex functions by defining and configuring only a small number of elements and attributes in XML and writing the corresponding SQL statements. Furthermore, subsequent software expansion and maintenance only require modifying the XML corresponding to the relevant function pages, without modifying the front-end and back-end code, significantly improving software development and maintenance efficiency.

[0084] Example 2

[0085] Figure 8 This is a schematic diagram of the structure of the XML-based low-code development device provided in Embodiment 2 of the present invention. Figure 8 As shown, the device includes:

[0086] The database modeling data acquisition module 810 is used to obtain database modeling data in response to database modeling operations through a low-code front-end engine; wherein, the low-code front-end engine is used to support users to perform various interactive operations;

[0087] The Extensible Markup Language (XML) form configuration file generation module 820 is used to generate an XML form configuration file based on the database modeling data using a low-code backend engine; wherein, the low-code backend engine is used to provide page rendering data to the low-code frontend engine.

[0088] Web application page display module 830 is used to display the Extensible Markup Language form configuration file through the Web application page using a low-code front-end engine.

[0089] Optional, the Extensible Markup Language (EXPLAIN) form configuration file generation module 820 is specifically used for:

[0090] Based on the modeling data in the database, generate an Extensible Markup Language (Extreme Markup Language) form;

[0091] The Extensible Markup Language (XML) form is parsed to generate an XML form configuration file.

[0092] Optionally, the object model of the Extensible Markup Language (Extreme Markup Language) form includes a form collection and form objects; the form objects include scripts, resource sets, resources, grids, tables, controls, dialog boxes, SQL script sets, and event sets;

[0093] Wherein, the resource refers to the external links referenced in the form; the grid is used for page layout; the table is used to define table components; the dialog box is used to define dialog boxes that pop up inside the form; the SQL script set is used to define various SQL scripts, and the SQL scripts are used to define SQL statements; the event set is used to define events and actions.

[0094] Optionally, the Extensible Markup Language form configuration file generation module 820 is also used for:

[0095] The low-code backend engine sends Extensible Markup Language (EXPLAIN) form configuration files to the low-code frontend engine via a standard interface.

[0096] Optional, the Web application page display module 830 is specifically used for:

[0097] If the database modeling operation is successful, the extensible markup language form configuration file will be displayed through a web application page using a low-code front-end engine.

[0098] If the database modeling operation fails, the low-code front-end engine will be used to display the operation error and error message.

[0099] Optionally, the device further includes:

[0100] The data sending module is used by the low-code front-end engine to send database modeling data to the low-code back-end engine through a standard interface.

[0101] Optionally, the device further includes:

[0102] The data modification module is used to respond to data modification operations and obtain the modified data through a low-code front-end engine;

[0103] The Target Extensible Markup Language (Target Extensible Markup Language) form configuration file generation module is used to generate Target Extensible Markup Language (Target Extensible Markup Language) form configuration files based on the modified data using a low-code backend engine.

[0104] The presentation module is used to display the target Extensible Markup Language form configuration file through a web application page using a low-code front-end engine.

[0105] The XML-based low-code development apparatus provided in this embodiment of the invention can execute the XML-based low-code development method provided in any embodiment of the invention, and has the corresponding functional modules and beneficial effects of the method execution.

[0106] Example 3

[0107] Figure 9A schematic diagram of an electronic device 10 that can be used to implement embodiments of the present invention is shown. The electronic device is intended to represent various forms of digital computers, such as laptop computers, desktop computers, workstations, personal digital assistants, servers, blade servers, mainframe computers, and other suitable computers. The electronic device can also represent various forms of mobile devices, such as personal digital processors, cellular phones, smartphones, wearable devices (e.g., helmets, glasses, watches, etc.), and other similar computing devices. The components shown herein, their connections and relationships, and their functions are merely illustrative and are not intended to limit the implementation of the invention described and / or claimed herein.

[0108] like Figure 9 As shown, the electronic device 10 includes at least one processor 11 and a memory, such as a read-only memory (ROM) 12 or a random access memory (RAM) 13, communicatively connected to the at least one processor 11. The memory stores computer programs executable by the at least one processor. The processor 11 can perform various appropriate actions and processes based on the computer program stored in the ROM 12 or loaded from storage unit 18 into the RAM 13. The RAM 13 may also store various programs and data required for the operation of the electronic device 10. The processor 11, ROM 12, and RAM 13 are interconnected via a bus 14. An input / output (I / O) interface 15 is also connected to the bus 14.

[0109] Multiple components in electronic device 10 are connected to I / O interface 15, including: input unit 16, such as keyboard, mouse, etc.; output unit 17, such as various types of displays, speakers, etc.; storage unit 18, such as disk, optical disk, etc.; and communication unit 19, such as network card, modem, wireless transceiver, etc. Communication unit 19 allows electronic device 10 to exchange information / data with other devices through computer networks such as the Internet and / or various telecommunications networks.

[0110] Processor 11 can be a variety of general-purpose and / or special-purpose processing components with processing and computing capabilities. Some examples of processor 11 include, but are not limited to, a central processing unit (CPU), a graphics processing unit (GPU), various special-purpose artificial intelligence (AI) computing chips, various processors running machine learning model algorithms, a digital signal processor (DSP), and any suitable processor, controller, microcontroller, etc. Processor 11 performs the various methods and processes described above, such as XML-based low-code development methods.

[0111] In some embodiments, the XML-based low-code development method can be implemented as a computer program tangibly contained in a computer-readable storage medium, such as storage unit 18. In some embodiments, part or all of the computer program can be loaded and / or installed on electronic device 10 via ROM 12 and / or communication unit 19. When the computer program is loaded into RAM 13 and executed by processor 11, one or more steps of the XML-based low-code development method described above can be performed. Alternatively, in other embodiments, processor 11 can be configured to execute the XML-based low-code development method by any other suitable means (e.g., by means of firmware).

[0112] Various embodiments of the systems and techniques described above herein can be implemented in digital electronic circuit systems, integrated circuit systems, field-programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), application-specific standard products (ASSPs), systems-on-a-chip (SoCs), payload-programmable logic devices (CPLDs), computer hardware, firmware, software, and / or combinations thereof. These various embodiments may include implementations in one or more computer programs that can be executed and / or interpreted on a programmable system including at least one programmable processor, which may be a dedicated or general-purpose programmable processor, capable of receiving data and instructions from a storage system, at least one input device, and at least one output device, and transmitting data and instructions to the storage system, the at least one input device, and the at least one output device.

[0113] Computer programs used to implement the methods of the present invention may be written in any combination of one or more programming languages. These computer programs may be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing device, such that when executed by the processor, the computer programs cause the functions / operations specified in the flowcharts and / or block diagrams to be performed. The computer programs may be executed entirely on a machine, partially on a machine, or as a standalone software package, partially on a machine and partially on a remote machine, or entirely on a remote machine or server.

[0114] In the context of this invention, a computer-readable storage medium can be a tangible medium that may contain or store a computer program for use by or in conjunction with an instruction execution system, apparatus, or device. A computer-readable storage medium may include, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, apparatus, or devices, or any suitable combination thereof. Alternatively, a computer-readable storage medium may be a machine-readable signal medium. More specific examples of machine-readable storage media include electrical connections based on one or more wires, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fibers, portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination thereof.

[0115] To provide interaction with a user, the systems and techniques described herein can be implemented on an electronic device having: a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to the user; and a keyboard and pointing device (e.g., a mouse or trackball) through which the user provides input to the electronic device. Other types of devices can also be used to provide interaction with the user; for example, feedback provided to the user can be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user can be received in any form (including sound input, voice input, or tactile input).

[0116] The systems and technologies described herein can be implemented in computing systems that include backend components (e.g., as data servers), or computing systems that include middleware components (e.g., application servers), or computing systems that include frontend components (e.g., user computers with graphical user interfaces or web browsers through which users can interact with implementations of the systems and technologies described herein), or any combination of such backend, middleware, or frontend components. The components of the system can be interconnected via digital data communication of any form or medium (e.g., communication networks). Examples of communication networks include local area networks (LANs), wide area networks (WANs), blockchain networks, and the Internet.

[0117] A computing system can include clients and servers. Clients and servers are generally located far apart and typically interact through communication networks. The client-server relationship is created by computer programs running on the respective computers and having a client-server relationship with each other. The server can be a cloud server, also known as a cloud computing server or cloud host, which is a hosting product within the cloud computing service system to address the shortcomings of traditional physical hosts and VPS services, such as high management difficulty and weak business scalability.

[0118] It should be understood that the various forms of processes shown above can be used, with steps reordered, added, or deleted. For example, the steps described in this invention can be executed in parallel, sequentially, or in different orders, as long as the desired result of the technical solution of this invention can be achieved, and this is not limited herein.

[0119] The specific embodiments described above do not constitute a limitation on the scope of protection of this invention. Those skilled in the art should understand that various modifications, combinations, sub-combinations, and substitutions can be made according to design requirements and other factors. Any modifications, equivalent substitutions, and improvements made within the spirit and principles of this invention should be included within the scope of protection of this invention.

Claims

1. A low-code development method based on XML, characterized in that, include: The database modeling data is obtained by responding to database modeling operations through a low-code front-end engine; wherein, the low-code front-end engine is used to support various interactive operations by users; Based on the database modeling data, the low-code backend engine generates an Extensible Markup Language (XML) form configuration file; wherein, the low-code backend engine is used to provide page rendering data to the low-code frontend engine; The extensible markup language form configuration file is displayed through a web application page using a low-code front-end engine.

2. The method according to claim 1, characterized in that, Based on the database modeling data, the low-code backend engine generates an Extensible Markup Language (Extreme Markup Language) form configuration file, including: Based on the modeling data in the database, generate an Extensible Markup Language (Extreme Markup Language) form; The Extensible Markup Language (XML) form is parsed to generate an XML form configuration file.

3. The method according to claim 2, characterized in that, The object model of the Extensible Markup Language (XML) form includes a collection of forms and form objects; the form objects include scripts, resource sets, resources, grids, tables, controls, dialog boxes, SQL script sets, and event sets. Wherein, the resource refers to the external links referenced in the form; the grid is used for page layout; the table is used to define table components; the dialog box is used to define dialog boxes that pop up inside the form; the SQL script set is used to define various SQL scripts, and the SQL scripts are used to define SQL statements; the event set is used to define events and actions.

4. The method according to claim 2, characterized in that, Generate an Extensible Markup Language (EXPLAIN) form configuration file, including: The low-code backend engine sends Extensible Markup Language (EXPLAIN) form configuration files to the low-code frontend engine via a standard interface.

5. The method according to claim 1, characterized in that, The Extensible Markup Language (EXPLE) form configuration file is displayed through a web application page using a low-code front-end engine, including: If the database modeling operation is successful, the extensible markup language form configuration file will be displayed through a web application page using a low-code front-end engine. If the database modeling operation fails, the low-code front-end engine will be used to display the operation error and error message.

6. The method according to claim 1, characterized in that, After obtaining the database modeling data, the method further includes: The low-code front-end engine sends database modeling data to the low-code back-end engine through a standard interface.

7. The method according to claim 1, characterized in that, The method further includes: The modified data is obtained by responding to data modification operations through a low-code front-end engine; Based on the modified data, the low-code backend engine generates a target extensible markup language form configuration file. The target Extensible Markup Language (XML) form configuration file is displayed through a web application page using a low-code front-end engine.

8. An XML-based low-code development device, characterized in that, include: The database modeling data acquisition module is used to obtain database modeling data in response to database modeling operations through a low-code front-end engine; wherein, the low-code front-end engine is used to support various interactive operations by users; An Extensible Markup Language (XML) form configuration file generation module is used to generate an XML form configuration file based on the database modeling data from the low-code backend engine; wherein, the low-code backend engine is used to provide page rendering data to the low-code frontend engine; The Web application page display module is used to display the Extensible Markup Language form configuration file through the Web application page using a low-code front-end engine.

9. An electronic device, characterized in that, The electronic device includes: At least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores a computer program executable by the at least one processor, the computer program being executed by the at least one processor to enable the at least one processor to perform the XML-based low-code development method according to any one of claims 1-7.

10. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer instructions that cause a processor to execute the XML-based low-code development method according to any one of claims 1-7.