Low-code page development method, device and equipment based on frame component and medium

Abstract

This invention discloses a low-code page development method, apparatus, device, and medium based on Frame components. The method includes: obtaining a target project file to guide the construction of a business page; developing a low-code business page using pre-registered standard components in a low-code development platform, based on the target project file; and supplementing the business page development by rendering secondary local components based on Frame components when the standard components cannot meet the business page construction requirements. Upon fulfilling the construction requirements of the target project file, the target business page corresponding to the target project file is obtained. This invention's technical solution supports dynamic loading of external local component files through Frame components, enabling hybrid development of local and standard components. While meeting the requirements of low-code development, it also satisfies the personalized depth requirements of page development, reducing page development costs and difficulty, and improving page development efficiency.

Description

Technical Field

[0001] This invention relates to the field of low-code page development technology, and in particular to low-code page development methods, apparatus, devices and media based on Frame components. Background Technology

[0002] Enterprise-level low-code development platforms typically support users in quickly building standard business pages through drag-and-drop functionality via standardized component libraries and visual configuration interfaces. Existing hybrid development practices mainly rely on two technical paths: one is iframe embedding technology, which involves developing customized functions as independent web pages and then embedding them; the other is standard component extension technology, which involves selecting and configuring components based on pre-registered components on the platform.

[0003] However, these solutions have significant drawbacks when dealing with high customization and deep integration requirements. The iframe solution, due to the isolation of the internal and external DOM environments, prevents the main application from directly sharing authentication information, global theme variables, and page context data, creating data silos. This not only results in high communication costs but also a fragmented user experience. Standard component extension technologies, on the other hand, are limited by predefined component libraries and struggle to meet the needs of personalized, deep integration.

[0004] In summary, existing technologies have bottlenecks in building business pages, which restricts the application of low-code platforms in complex business scenarios. There is an urgent need for an innovative solution to achieve efficient and deep component integration. Summary of the Invention

[0005] This invention provides a low-code page development method, apparatus, device, and medium based on Frame components. By supporting the dynamic loading of external local component files through Frame components, it enables the hybrid development of local components and standard components. While meeting the requirements of low-code development, it can also meet the personalized needs of page development, reduce page development costs and difficulties, and improve the timeliness of page development.

[0006] According to one aspect of the present invention, a low-code development method based on Frame components is provided, the method comprising:

[0007] Obtain the target project files used to guide the construction of business pages;

[0008] Based on the low-code development platform, and according to the target project file, low-code business pages are developed using pre-registered standard components in the low-code development platform.

[0009] When the standard components cannot meet the requirements for building business pages, local components that are secondarily developed based on the Frame component are used to supplement the development of business pages. The local components are non-platform pre-registered components that are secondarily developed according to the building requirements.

[0010] If the requirements for building the target project file are met, the target business page corresponding to the target project file is obtained.

[0011] According to another aspect of the present invention, a low-code page development apparatus based on Frame components is provided. The apparatus includes:

[0012] The project file acquisition module is used to acquire the target project files that guide the construction of business pages;

[0013] The first page development module is used to develop low-code business pages based on the low-code development platform and according to the target project file, using pre-registered standard components in the low-code development platform.

[0014] The second page development module is used to supplement the business page development by rendering a second-developed local component based on the Frame component when the standard component cannot meet the business page construction requirements. The local component is a non-platform pre-registered component that is second-developed according to the construction requirements.

[0015] The business page determination module is used to obtain the target business page corresponding to the target project file when the construction requirements of the target project file are met.

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

[0017] At least one processor; and

[0018] A memory communicatively connected to the at least one processor; wherein,

[0019] The memory stores a computer program that can be executed 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 execute the low-code page development method based on the Frame component as described in any embodiment of the present invention.

[0020] 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 low-code page development method based on the Frame component as described in any embodiment of the present invention.

[0021] The technical solution of this invention involves obtaining a target project file to guide the construction of a business page. Based on a low-code development platform, and according to the target project file, low-code business page development is performed using pre-registered standard components within the low-code development platform. If the standard components cannot meet the business page construction requirements, supplementary business page development is performed using local components rendered based on the Frame component. By fulfilling the construction requirements of the target project file, the target business page corresponding to the target project file is obtained. This solves the communication difficulties caused by context isolation in traditional Iframe solutions. By dynamically loading external local component files through the Frame component, highly personalized page development needs can be met based on the low-code development platform, greatly enriching the capabilities of low-code page development and improving its personalization and timeliness.

[0022] 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

[0023] 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.

[0024] Figure 1 This is a flowchart of a low-code page development method based on a Frame component according to an embodiment of the present invention;

[0025] Figure 2 This is a flowchart of a low-code page development method based on a Frame component according to an embodiment of the present invention;

[0026] Figure 3 This is a structural diagram of a low-code page development apparatus based on a Frame component according to an embodiment of the present invention;

[0027] Figure 4 This is a schematic diagram of the structure of an electronic device that implements the low-code page development method based on the Frame component according to an embodiment of the present 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 "first," "second," 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 the 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] Figure 1 This is a flowchart illustrating a low-code page development method based on Frame components, provided by an embodiment of the present invention. This embodiment is applicable to personalized page development needs based on a low-code development platform. The method can be executed by a low-code page development device based on Frame components, which can be implemented in hardware and / or software and can be configured in an electronic device. Figure 1 As shown, the method includes:

[0031] S101. Obtain the target project file used to guide the construction of business pages.

[0032] It should be noted that the business page development in this invention is based on a low-code development platform. Enterprise-level low-code development platforms typically provide a standardized component library and a visual configuration interface, allowing users to quickly build common business pages through drag-and-drop and configuration.

[0033] The business page is built based on a structured target project file, which clearly defines the core elements of the business page in advance, ensuring that the final generated business page can accurately achieve the preset business objectives.

[0034] S102. Based on the low-code development platform, according to the target project file, develop low-code business pages using pre-registered standard components in the low-code development platform.

[0035] It should be noted that low-code development platforms pre-package, test, and register standard components to improve development efficiency. These standard components form the cornerstone of visual development.

[0036] Standard components typically encompass basic UI controls (such as buttons, tables, and forms), business logic modules (such as approval workflows and data validation), and system integration interfaces (such as API connectors). Each standard component has preset properties, configurable events, and standardized data interfaces, allowing developers to quickly combine functions by adjusting parameters.

[0037] Specifically, enterprise-level low-code development platforms are centered around visual development. Developers use the rich standardized component library provided by the low-code development platform, and through the intuitive drag-and-drop interface and configurable business logic units, the technical threshold for application development is greatly reduced, enabling the development of low-code business pages.

[0038] S103. If the standard components cannot meet the requirements for building business pages, supplementary development of business pages is carried out using local components that are secondarily developed based on the Frame component rendering.

[0039] In fact, while enterprise-level low-code platforms offer significant advantages in development efficiency, they also have obvious limitations, primarily stemming from the inherent constraints of their pre-registered standard components and visual modes. When faced with highly complex, uniquely interactive, or deeply customized front-end interfaces and business logic, the standard components provided by the platform often fail to meet the page building requirements.

[0040] This invention supplements business page development by using locally developed components based on Frame component rendering to meet business page requirements that cannot be built with standard components. These locally developed components are non-platform pre-registered components developed according to specific setup needs.

[0041] In hybrid development models, the Frame component serves as a container for hosting and integrating external components. Frame components allow embedding local component code within low-code business pages and configuring these local components to work collaboratively with standard components.

[0042] In this invention, the secondary-developed native component refers to a software module developed entirely in-code by developers based on specific page requirements. Native components are independent of the low-code platform. By retaining the technical freedom and performance potential of native development, and being configured and driven by the low-code designer similar to standard platform components, native components become a core carrier for extending the platform's capabilities and meeting highly customized needs.

[0043] Specifically, when the standard components cannot meet the requirements for building business pages, a Frame component is used to load and render local components to supplement the business page development, thereby obtaining the project page required by the target project file. Furthermore, within the rendering context created by the Frame component, an isolated execution environment is created for the code module to prevent it from polluting the global context of the low-code development platform.

[0044] After the local component, which is based on the Frame component for secondary rendering, is used to supplement the business page development, the method further includes: establishing an event proxy mechanism between the local component and the low-code development platform; and using the event proxy mechanism to convert the native events inside the local component into standard actions that can be processed by the low-code development platform.

[0045] Specifically, after local component rendering is complete, a bidirectional event proxy mechanism is established between the local component and the low-code development platform. This mechanism acts as a listener proxy, converting events emitted from the local component into standard action flows that the low-code development platform can process. Through this event proxy mechanism, uplink communication between the local component and the low-code platform is achieved.

[0046] In addition, Frame can also use scope penetration technology to automatically inject the global state (Store), theme styles, and permission tokens of the low-code development platform into the Props or Provide / Inject context of the local component, so as to realize the downlink communication from the low-code platform to the local component.

[0047] S104. If the requirements for building the target project file are met, obtain the target business page corresponding to the target project file.

[0048] Specifically, business pages are built based on a hybrid development model of local components and standard components. Once the requirements for building the target project file are met, the target business page corresponding to the target project file is obtained.

[0049] The technical solution of this invention involves obtaining a target project file to guide the construction of a business page. Based on a low-code development platform, and according to the target project file, low-code business page development is performed using pre-registered standard components within the low-code development platform. If the standard components cannot meet the business page construction requirements, supplementary business page development is performed using local components rendered based on the Frame component. By fulfilling the construction requirements of the target project file, the target business page corresponding to the target project file is obtained. This solves the communication difficulties caused by context isolation in traditional Iframe solutions. By dynamically loading external local component files through the Frame component, highly personalized page development needs can be met based on the low-code development platform, greatly enriching the capabilities of low-code page development and improving its personalization and timeliness.

[0050] Based on the above embodiments, the supplementary development of business pages using local components for secondary rendering based on Frame components includes: in the business page under construction in the low-code development platform, the Frame component is connected to the page canvas as a local component hosting container; in the configuration panel of the Frame component, the file path and business parameters of the local component are configured; based on the configuration information of the Frame component, the Frame component completes the rendering and integration of the local component at runtime, thereby realizing the supplementary development of business pages.

[0051] Specifically, the Frame component's rendering of local components includes specifying the component path and configuring parameters. In the visual design interface of the low-code development platform, the Frame component is dragged and dropped onto the page canvas as a standard component. In the Frame component's configuration panel, the file path and business parameters of the local component are configured. Based on this configuration, the Frame component completes the rendering and integration of the local component at runtime.

[0052] For example, configuring the file path and business parameters of the local component in the configuration panel of the Frame component includes: determining the target local component to be loaded into the Frame component according to the page building requirements, and determining the component file path corresponding to the target local component. Based on the component file path, configuring the data source of the Frame component, thereby registering the target local component as a local component of the current business page. Using an attribute mapping bridge, converting static configuration data into component attribute data that conforms to the interface definition of the target local component.

[0053] The static configuration data refers to the attribute data configured for the Frame component on the low-code development platform. The target native component is the native component to be loaded into the Frame component.

[0054] Specifically, based on the component file path corresponding to the target local component, the data source of the Frame component is configured. The Frame component starts a dynamic module loader, pulls the compiled code package from the specified component file path based on the asynchronous module specification, and registers it as the current local component.

[0055] The system retrieves static configuration data configured for the Frame component on the low-code development platform and converts this static configuration data into attribute data that conforms to the local component interface definition via an attribute mapping bridge. This enables the configuration of file paths and business parameters for the local component. For example, the system reads structured JSON configuration stored on the low-code platform through the attribute mapping bridge and converts it into reactive properties recognizable by the local component (such as a Vue component) using predefined mapping rules.

[0056] For example, the step of converting static configuration data into component attribute data that conforms to the target local component interface definition through the attribute mapping bridge includes: mapping the configuration item key name in the static configuration data to the attribute name adapted by the target local component according to the mapping rules predefined in the attribute mapping bridge; and performing type conversion on the configuration item value in the static configuration data to obtain an attribute value type that matches the attribute type required by the local component, thereby obtaining component attribute data.

[0057] The core function of the property mapping bridge is to perform key transformations based on a predefined, flexibly configurable set of mapping rules. By querying mapping rules, the property mapping bridge transforms platform-specific configuration item keys in static configuration data into property names that the target native component expects in its programming interface, thereby resolving naming semantic differences between different systems.

[0058] The property mapping bridge can also automatically handle data type conversions, performing necessary type conversions, such as converting numeric strings to numeric types, to ensure that they match the strict types declared by local component properties. This eliminates the need for hardcoding in local code, allowing you to obtain component property data and ensuring the correctness and reliability of configuration-driven development.

[0059] Figure 2 This is a flowchart illustrating a low-code page development method based on the Frame component, provided by an embodiment of the present invention. Based on the aforementioned embodiments, this embodiment introduces the reuse and rendering of already developed pages using the Frame component. Figure 2 As shown, the method includes:

[0060] S201. Obtain the target project file used to guide the construction of business pages.

[0061] S202. Based on the low-code development platform, according to the target project file, develop low-code business pages using pre-registered standard components in the low-code development platform.

[0062] S203. If the standard components cannot meet the requirements for building business pages, supplementary development of business pages is carried out using local components that are secondarily developed based on the Frame component rendering.

[0063] S204. If the functional interface required by the target project file already exists in other created low-code pages, the functional interface of the low-code page is accessed recursively through the Frame component.

[0064] If the required functional interfaces for the target project files already exist in other created low-code pages, the development cost of business pages can be reduced by reusing the functional interfaces at the low-code page level.

[0065] Take the requirement to display a unified message center on multiple portal homepages as an example. The "message center" has already been developed on other low-code pages, including complex interactions such as lists and carousels. Developers can recursively integrate the "message center" from the low-code pages into the new low-code portal homepage using the Frame component. This achieves page component reuse, maintains consistent page component styles and state isolation, and reduces the development cost of business pages.

[0066] For example, the step of recursively accessing the functional interface of the low-code page through the Frame component includes: determining the page identifier corresponding to the low-code page and configuring the data source of the Frame component as the page identifier of the low-code page; in response to the mounting of the Frame component, obtaining the page structure data of the low-code page according to the page identifier; based on the page structure data, inheriting the global style of the business page to be built within the Frame component, and recursively rendering the functional interface.

[0067] Specifically, developers drag a Frame component into the business page and set its component source to the page identifier corresponding to the low-code page. When the business page runs, the Frame component obtains the page structure data of the low-code page and recursively renders the complete functional interface within the Frame component. The functional interface automatically inherits the theme color, font, and other global styles of the low-code page. However, this functional interface has independent data states, such as the number of unread messages and list data, which are independent and isolated from the data states of the original functional page interface of the low-code page.

[0068] S205. If the requirements for building the target project file are met, obtain the target business page corresponding to the target project file.

[0069] The technical solution of this invention addresses the situation where the required functional interface for the target project file already exists in another created low-code page. The Frame component recursively accesses the functional interface of the low-code page, inheriting its global style, thus ensuring visual consistency and basic logic uniformity. The reused functional interface has independent data state, guaranteeing data isolation between reused modules and avoiding conflicts.

[0070] Figure 3 This is a schematic diagram of a low-code page development device based on a Frame component, provided as an embodiment of the present invention. Figure 3 As shown, the device includes:

[0071] Project file acquisition module 301 is used to acquire the target project files used to guide the construction of business pages;

[0072] The first page development module 302 is used to develop low-code business pages based on the target project file and using pre-registered standard components in the low-code development platform.

[0073] The second page development module 303 is used to supplement the business page development by rendering a second-developed local component based on the Frame component when the standard component cannot meet the business page construction requirements. The local component is a non-platform pre-registered component that is second-developed according to the construction requirements.

[0074] The business page determination module 304 is used to obtain the target business page corresponding to the target project file when the construction requirements of the target project file are met.

[0075] The technical solution of this invention involves obtaining a target project file to guide the construction of a business page. Based on a low-code development platform, and according to the target project file, low-code business page development is performed using pre-registered standard components within the low-code development platform. If the standard components cannot meet the business page construction requirements, supplementary business page development is performed using local components rendered based on the Frame component. By fulfilling the construction requirements of the target project file, the target business page corresponding to the target project file is obtained. This solves the communication difficulties caused by context isolation in traditional Iframe solutions. By dynamically loading external local component files through the Frame component, highly personalized page development needs can be met based on the low-code development platform, greatly enriching the capabilities of low-code page development and improving its personalization and timeliness.

[0076] Optional, the second page development module 303 includes:

[0077] The Frame component access unit is used to access the Frame component as a local component hosting container to the page canvas in the business page that is in the building stage in the low-code development platform.

[0078] The Frame component configuration unit is used to configure the file path and business parameters of the local component in the configuration panel of the Frame component.

[0079] The page supplementary development unit is used to complete the rendering and integration of local components by the Frame component at runtime based on the configuration information of the Frame component, so as to realize the supplementary development of business pages.

[0080] Optional, Frame component configuration unit, used for:

[0081] The component path configuration sub-unit is used to determine the target local component to be loaded into the Frame component according to the page building requirements, and to determine the component file path corresponding to the target local component;

[0082] The local component loading sub-unit is used to configure the data source of the Frame component according to the component file path, so as to register the target local component as a local component of the current business page;

[0083] The attribute data configuration subunit is used to convert static configuration data into component attribute data that conforms to the target local component interface definition through an attribute mapping bridge, wherein the static configuration data is the attribute data configured for the Frame component on the low-code development platform.

[0084] Optional, attribute data configuration sub-unit, specifically used for:

[0085] According to the predefined mapping rules in the attribute mapping bridge, the configuration item key name in the static configuration data is mapped to the attribute name adapted by the target local component;

[0086] In addition, the configuration item values ​​in the static configuration data are type-converted to obtain attribute value types that match the attribute types required by the local component, thereby obtaining component attribute data.

[0087] Optionally, the device further includes an event communication proxy module. The event communication proxy module is used for:

[0088] After the local component, which is based on the Frame component rendering secondary development, is used to supplement the business page development, an event proxy mechanism is established between the local component and the low-code development platform.

[0089] The event delegation mechanism converts native events within the local component into standard actions that can be processed by the low-code development platform.

[0090] Optionally, the device further includes a development page reuse module. The development page reuse module is used for:

[0091] If the required functional interface for the target project file already exists in another created low-code page, the functional interface of the low-code page can be accessed recursively through the Frame component.

[0092] Optionally, develop a page reuse module, specifically for:

[0093] Determine the page identifier corresponding to the low-code page, and configure the data source of the Frame component to the page identifier of the low-code page;

[0094] In response to the mounting of the Frame component, the page structure data of the low-code page is obtained according to the page identifier;

[0095] Based on the page structure data, the global style of the business page to be built is inherited within the Frame component, and the functional interface is rendered recursively.

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

[0097] Figure 4 A schematic diagram of an electronic device 10, which 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.

[0098] like Figure 4As 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 can 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.

[0099] 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.

[0100] 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 low-code page development methods based on Frame components.

[0101] In some embodiments, the Frame component-based low-code page 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 Frame component-based low-code page development method described above can be performed. Alternatively, in other embodiments, processor 11 can be configured to perform the Frame component-based low-code page development method by any other suitable means (e.g., by means of firmware).

[0102] 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), system-on-a-chip (SoCs), complex 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.

[0103] 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.

[0104] 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.

[0105] 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).

[0106] The systems and technologies described herein can be implemented in computing systems that include backend components (e.g., as data servers), or middleware components (e.g., application servers), or 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.

[0107] 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.

[0108] 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.

[0109] 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 Frame components, characterized in that, include: Obtain the target project files used to guide the construction of business pages; Based on the low-code development platform, and according to the target project file, low-code business pages are developed using pre-registered standard components in the low-code development platform. When the standard components cannot meet the requirements for building business pages, local components that are secondarily developed based on the Frame component are used to supplement the development of business pages. The local components are non-platform pre-registered components that are secondarily developed according to the building requirements. If the requirements for building the target project file are met, the target business page corresponding to the target project file is obtained.

2. The method according to claim 1, characterized in that, The local component, which is based on the secondary development of the Frame component rendering, is used to supplement the business page development, including: In the business page that is in the building phase in the low-code development platform, the Frame component is connected to the page canvas as a local component hosting container; In the configuration panel of the Frame component, configure the file path and business parameters of the local component; Based on the configuration information of the Frame component, the Frame component completes the rendering and integration of local components at runtime, enabling supplementary development of business pages.

3. The method according to claim 2, characterized in that, In the configuration panel of the Frame component, the file path and business parameters of the local component are configured, including: Based on the page building requirements, determine the target local component to be loaded into the Frame component, and determine the component file path corresponding to the target local component; Based on the component file path, configure the data source of the Frame component to register the target local component as a local component of the current business page; The static configuration data is converted into component attribute data that conforms to the target local component interface definition through the attribute mapping bridge, wherein the static configuration data is the attribute data configured for the Frame component on the low-code development platform.

4. The method according to claim 3, characterized in that, The step of converting static configuration data into component attribute data that conforms to the target local component interface definition through the attribute mapping bridge includes: According to the predefined mapping rules in the attribute mapping bridge, the configuration item key name in the static configuration data is mapped to the attribute name adapted by the target local component; In addition, the configuration item values ​​in the static configuration data are type-converted to obtain attribute value types that match the attribute types required by the local component, thereby obtaining component attribute data.

5. The method according to claim 1, characterized in that, After the local component based on the Frame component rendering secondary development is used to supplement the business page development, it also includes: Establish an event proxy mechanism between the local component and the low-code development platform; The event delegation mechanism converts native events within the local component into standard actions that can be processed by the low-code development platform.

6. The method according to claim 1, characterized in that, The method further includes: If the required functional interface for the target project file already exists in another created low-code page, the functional interface of the low-code page can be accessed recursively through the Frame component.

7. The method according to claim 6, characterized in that, The functional interface that recursively accesses the low-code page through the Frame component includes: Determine the page identifier corresponding to the low-code page, and configure the data source of the Frame component to the page identifier of the low-code page; In response to the mounting of the Frame component, the page structure data of the low-code page is obtained according to the page identifier; Based on the page structure data, the global style of the business page to be built is inherited within the Frame component, and the functional interface is rendered recursively.

8. A low-code page development device based on Frame components, characterized in that, include: The project file acquisition module is used to acquire the target project files that guide the construction of business pages; The first page development module is used to develop low-code business pages based on the low-code development platform and according to the target project file, using pre-registered standard components in the low-code development platform. The second page development module is used to supplement the business page development by rendering a second-developed local component based on the Frame component when the standard component cannot meet the business page construction requirements. The local component is a non-platform pre-registered component that is second-developed according to the construction requirements. The business page determination module is used to obtain the target business page corresponding to the target project file when the construction requirements of the target project file are met.

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 that can be executed 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 low-code page development method based on the Frame component as described in 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 low-code page development method based on the Frame component as described in any one of claims 1-7.

Images