Implementation method and device of page editor platform and storage medium

Abstract

The invention relates to the technical field of page editors, and particularly discloses a page editor platform implementation method and device and a storage medium, the page editor platform implementation method comprises the steps that a platform material library is configured, the platform material library at least comprises a component and a universal plug-in corresponding to the component, the component is used for implementing a page editing basic function, and the universal plug-in corresponds to the component; the universal plug-in is used for realizing a page editing universal function; receiving a page editing demand instruction of a user, and generating a material calling instruction according to the page editing demand instruction; calling components and universal plug-ins in the platform material library according to the material calling instruction; and executing the component and the universal plug-in according to a page editing operation instruction of a user to realize a page editing function, and obtaining a page editing set. According to the implementation method of the page editor platform, provided by the invention, the cost and complexity of component development can be reduced.

Description

Technical Field

[0001] The present invention relates to the technical field of page editors, and in particular to a method for implementing a page editor platform, an implementation device for the page editor platform, and a storage medium. Background Art

[0002] Building a platform based on a set of intelligent manufacturing visual page editors to achieve page display for various boundary scenarios requires the support of a rich component library. However, in the implementation mode of the existing technology, the component development process usually requires first ensuring the perfection of the component's own functions, and then adapting it according to the platform's capabilities so that the component can truly play a role on the platform. Developing a component from scratch requires familiarity with the platform's capabilities, the component's own functions, and compatibility, which increases the cost of getting started with component development. In addition, in order to adapt to multiple platforms, components need to make a lot of compatibility adjustments, which increases code redundancy and increases the cost of code maintenance. At the same time, when the platform mechanism is adjusted, the component also needs to be modified accordingly to maintain stability, which reduces the stability of the component.

[0003] It can be seen that traditional page editor platforms have problems in component development, such as high entry cost, low code maintainability and low stability.

[0004] Therefore, how to reduce the development cost of page editor platform components and the complexity of component implementation has become a technical problem that technical personnel in this field need to solve urgently. Summary of the invention

[0005] The present invention provides a method for implementing a page editor platform, an implementation device for the page editor platform and a storage medium, which solve the problem of high development cost of page editor platform components existing in the related art.

[0006] As a first aspect of the present invention, a method for implementing a page editor platform is provided, which includes: Configure a platform material library, the platform material library at least includes components and general plug-ins corresponding to the components, the components are used to implement basic page editing functions, and the general plug-ins are used to implement general page editing functions; Receive a page editing requirement instruction from a user, and generate a material call instruction according to the page editing requirement instruction; Calling components and general plug-ins in the platform material library according to the material calling instruction; The components and the general plug-in are executed according to the user's page editing operation instruction to realize the page editing function and obtain a page editing set.

[0007] Further, generating a material call instruction according to the page editing requirement instruction includes: Parsing the page editing requirement instruction to obtain target component requirement information; A target component calling instruction is generated according to the target component requirement information.

[0008] Further, calling the components and general plug-ins in the platform material library according to the material calling instruction includes: Calling the target component in the platform material library according to the target component calling instruction; The target general plug-in corresponding to the target component is called according to the target component.

[0009] Furthermore, the components and the general plug-in are executed according to the user's page editing operation instruction to implement the page editing function, and a page editing set is obtained, including: Receive page editing operation instructions from users; Determine a page target function according to a page editing operation instruction of a user, wherein the page target function includes at least a basic function and a common function; Execute the components and common plug-ins according to the page target function; Components that complete multiple page target functions form a page editing collection.

[0010] Further, executing the components and the general plug-in according to the page target function includes: Determine the execution order of multiple page target functions; The execution order of the target component and the target general plug-in under each page target function is determined according to the initialization configuration information of the page target function, wherein the execution priority of the target general plug-in of each page target function is higher than the execution priority of the target component.

[0011] Furthermore, the platform material library is configured, including: Initialize the page editor platform; Determining a component type for page editing according to a page editing model of the page editor platform; Determine the basic and common functions of each component type; Configure components according to the basic functions of each component type, and configure common plug-ins corresponding to the components according to the common functions of each component type; Configure the relationship and execution order between multiple components, and configure the execution order of each component and the corresponding common plug-in.

[0012] Furthermore, the configuration platform material library also includes: Configure the custom plug-in corresponding to the component according to the extended functions of the component type.

[0013] Furthermore, it also includes: calling a custom plug-in corresponding to the target component according to the material calling instruction, and executing the custom plug-in when executing the target component.

[0014] As another aspect of the present invention, a device for implementing a page editor platform is provided, which is used to implement the method for implementing the page editor platform described above, and includes: A configuration module, used to configure a platform material library, wherein the platform material library includes at least a component and a general plug-in corresponding to the component, wherein the component is used to implement a basic page editing function, and the general plug-in is used to implement a general page editing function; A receiving module, used for receiving a user's page editing requirement instruction, and generating a material call instruction according to the page editing requirement instruction; A calling module, used to call components and general plug-ins in the platform material library according to the material calling instruction; The execution module is used to execute the components and the general plug-in according to the user's page editing operation instruction to realize the page editing function and obtain the page editing set.

[0015] As another aspect of the present invention, a storage medium is provided, which is used to store computer instructions. When the computer instructions are called and executed by a processor, the implementation method of the page editor platform described above is implemented.

[0016] The implementation method of the page editor platform provided by the present invention configures the general functions of page editing into a general plug-in in the platform material library, and configures the basic functions of page editing into components in the platform material library, so that users can implement basic functions based on components when editing pages, while general functions are implemented by general plug-ins. This can reduce the development cost of components and the complexity of component implementation, making the functions of components and plug-ins more refined and facilitating the delivery and use of industrial software. BRIEF DESCRIPTION OF THE DRAWINGS

[0017] The accompanying drawings are used to provide further understanding of the present invention and constitute a part of the specification. Together with the following specific embodiments, they are used to explain the present invention, but do not constitute a limitation of the present invention.

[0018] Figure 1 A flowchart of a method for implementing the page editor platform provided by the present invention.

[0019] Figure 2 This is a flow chart of the configuration platform material library provided by the present invention.

[0020] Figure 3 This is a schematic diagram of the editing state and the running state of the universal plug-in provided by the present invention.

[0021] Figure 4 A flow chart of generating material call instructions provided by the present invention.

[0022] Figure 5 A flowchart of the calling component and the general plug-in provided by the present invention.

[0023] Figure 6 A flowchart of the execution component and the general plug-in provided by the present invention.

[0024] Figure 7 A structural block diagram of an implementation device of the page editor platform provided by the present invention.

[0025] Figure 8 This is a structural block diagram of the electronic device provided by the present invention. DETAILED DESCRIPTION

[0026] It should be noted that, in the absence of conflict, the embodiments of the present invention and the features in the embodiments may be combined with each other. The present invention will be described in detail below with reference to the accompanying drawings and in combination with the embodiments.

[0027] In order to enable those skilled in the art to better understand the scheme of the present invention, the technical scheme in the embodiment of the present invention will be clearly and completely described below in conjunction with the drawings in the embodiment of the present invention. Obviously, the described embodiment is only a part of the embodiment of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without making creative work should fall within the scope of protection of the present invention.

[0028] It should be noted that the terms "first", "second", etc. in the specification and claims of the present invention and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the data used in this way can be interchanged where appropriate, so as to describe the embodiments of the present invention described herein. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions, for example, a process, method, system, product or device that includes a series of steps or units is not necessarily limited to those steps or units clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.

[0029] In this embodiment, a method for implementing a page editor platform is provided. Figure 1 is a flow chart of a method for implementing a page editor platform according to an embodiment of the present invention. Figure 1 As shown, including: S100, configuring a platform material library, wherein the platform material library includes at least components and general plug-ins corresponding to the components, wherein the components are used to implement basic page editing functions, and the general plug-ins are used to implement general page editing functions; In an embodiment of the present invention, when configuring the platform material library, the basic functions of page editing are configured as components, and the general functions of page editing are configured as general plug-ins, that is, the components in the platform material library implement only the basic functions of page editing, and the general functions are implemented by the general plug-ins.

[0030] It should be noted here that a component is a general function implementation and is a static resource; a component needs to be bound to a plug-in to interact with the platform to form a dynamic resource. The platform's components need to be integrated with plug-ins to be used in conjunction with the platform, otherwise it is only a static display content and cannot form dynamic data display and control.

[0031] It should be understood that multiple components in the platform material library are configured in the same way, and common functions are implemented in the form of common plug-ins. In this way, when editing different pages or implementing different editing functions on the same page, common plug-ins can solve problems faced by developers in the component development process, such as data source access, chart component access, option data source access, visibility, event handling, editability, and design capabilities. Encapsulating these common functions into common plug-ins can reduce component access costs and make component functions clearer.

[0032] S200, receiving a page editing requirement instruction from a user, and generating a material call instruction according to the page editing requirement instruction; For page editing users, when they need to implement the page editing function, they issue a page editing demand instruction through the interface. After receiving the page editing demand instruction, a material call instruction is generated according to the page editing demand instruction.

[0033] S300, calling the components and general plug-ins in the platform material library according to the material calling instruction; In the embodiment of the present invention, the corresponding component and the general plug-in corresponding to the component are called based on the material calling instruction.

[0034] It should be noted that the material call instruction here calls the component in the material library, while the call of the general plug-in can be determined by the component.

[0035] S400: Execute the components and the general plug-in according to the user's page editing operation instruction to implement the page editing function and obtain a page editing set.

[0036] In the embodiment of the present invention, when implementing page editing, the page editing user can issue a page editing operation instruction through the interface, and based on the page editing operation instruction execution component and the general plug-in, the page editing function can be implemented.

[0037] The implementation method of the page editor platform provided by the embodiment of the present invention configures the general functions of page editing into a general plug-in in the platform material library, and configures the basic functions of page editing into components in the platform material library, so that users can implement basic functions based on components when editing pages, while general functions are implemented by general plug-ins. This can reduce the development cost of components and the complexity of component implementation, making the functions of components and plug-ins more refined and facilitating the delivery and use of industrial software.

[0038] It should be noted that as a page editing platform, when page editing users perform page editing functions, users can still edit in the original way. When the page editing platform calls a component, it will call the general plug-in corresponding to the component, that is, the general plug-in is invisible to the page editing user. Therefore, this implementation method of the page editing platform will not increase the complexity of use for page editing users, and at the same time can reduce the development cost of component developers of the page editing platform.

[0039] In an embodiment of the present invention, a platform material library is configured, such as Figure 2 As shown, including: S110, initializing the page editor platform; S120, determining a component type for page editing according to a page editing model of the page editor platform; S130, determining the basic functions and common functions of each component type; S140, configuring a component according to the basic functions of each component type, and configuring a general plug-in corresponding to the component according to the general functions of each component type; S150: Configure the relationship and execution order between multiple components, and configure the execution order of each component and the corresponding general plug-in.

[0040] It should be understood that when configuring the platform material library, for the page editor platform, it is first necessary to determine the page editing model of the current page editor platform, and then determine the component type required for page editing based on the page editing model.

[0041] For the required component types, the common functions of each component type are split and encapsulated into common plug-ins, and the basic functions to be implemented by the component type are configured as components, that is, when configuring components and common plug-ins, they are configured according to the function types to be implemented, and the common functions are configured as common plug-ins, and the basic functions are configured as components. The execution order of the common plug-ins corresponding to the components is also configured. It should be understood here that the communication between multiple components is specifically implemented through platform management control, that is, communication is implemented through common plug-ins.

[0042] In an embodiment of the present invention, configuring the platform material library further includes: Configure the custom plug-in corresponding to the component according to the extended functions of the component type.

[0043] More specifically, the implementation method also includes: calling a custom plug-in corresponding to the target component according to the material call instruction, and executing the custom plug-in when executing the target component.

[0044] It should be noted that when the general functions of the components in the embodiments of the present invention are implemented as plug-ins, the onion model can be used to split the functions. One part is the general logic of the platform, one part is the component extension function, and the other is the basic function of the component. The general capabilities of the platform are abstracted as general plug-in capabilities, and the component extension functions are abstracted as customized plug-in capabilities. By connecting the functions of these plug-ins and components in series, a low-coupling and simple component development model is formed, so that both plug-ins and components can be reused.

[0045] like Figure 3 As shown, the general plug-in in the embodiment of the present invention provides 6 editing state life cycle functions and 3 running state life cycle functions, which run through the entire life cycle stage of component development and operation.

[0046] Specifically, the page editor platform has accumulated 6 common plug-ins, including: (1) Data container plug-in: Provides a general data source plug-in that can quickly access single data sources, collection data sources, and tree structure data sources. It solves the data source configuration solution in the editing state and solves the platform data source acquisition capability in the running state.

[0047] (2) Simple-chart-plugin: helps developers easily configure echarts components and works with the data container plug-in to achieve seamless connection between data sources and echarts configuration information and display rich chart content.

[0048] (3) Form-item-plugin: It can automatically bind form configuration, support the configuration and parsing of editable expressions, and help users achieve one-click access between components and form submission.

[0049] (4) Data source plug-in: Provides the ability to obtain the data source of the selection element options, without the user having to process the data source of the option content. Through this plug-in, you can quickly access the edit mode configuration and run mode to obtain the drop-down box options, allowing developers to obtain data without writing code.

[0050] (5) Event-trigger-plugin system: helps components to implement one-click access to common events, mainly supporting container click events and form element change events.

[0051] (6) Common-plugin unit: solves the configuration and parsing of component visibility expressions, as well as the configuration and parsing of common styles.

[0052] The universal plug-ins in the embodiments of the present invention are all maintained by the platform, and the plug-in capabilities can be given to the components through configuration. Therefore, the components only need to develop their own functions to seamlessly connect with the editing state and running state of the platform. This greatly reduces the maintenance cost of the components and improves the efficiency of component development.

[0053] For some components with more complex functions, the onion model can also be used to decouple complex logic into customized plug-ins, thereby reducing the difficulty and complexity of component implementation through plug-in empowerment.

[0054] The page editor platform in the embodiment of the present invention is constructed into a platform component plug-in ecosystem by implementing a general scaffold, a general plug-in registration mechanism, a custom plug-in registration and identification mechanism, and the above-mentioned platform general plug-in, component custom plug-in, plug-in configuration and platform plug-in parsing capabilities. Through this system, the execution order of component plug-ins can be determined by configuration, and the dependencies between plug-ins can be clarified during the execution process. This combination of clear component implementation and plug-in capabilities significantly reduces the difficulty of component access and implementation, and improves the stability and maintainability of components.

[0055] In an embodiment of the present invention, a material call instruction is generated according to the page editing requirement instruction, such as Figure 4 As shown, including: S210, parsing the page editing requirement instruction to obtain target component requirement information; S220. Generate a target component calling instruction according to the target component requirement information.

[0056] It should be understood that based on the user's page editing requirement instruction, the target component requirement information required for the user's current page editing can be determined, and then the target component calling instruction is generated according to the target component requirement information.

[0057] In an embodiment of the present invention, components and general plug-ins in the platform material library are called according to the material call instruction, such as Figure 5 As shown, including: S310, calling the target component in the platform material library according to the target component calling instruction; S320: Call the corresponding target general plug-in according to the target component.

[0058] It should be understood that the corresponding target component is called in the platform material library according to the target component calling instruction. After the target component is determined, the corresponding target general plug-in is called according to the target component. Therefore, the general plug-in in the embodiment of the present invention is invisible to the user, that is, the user only needs to select the corresponding target component according to the original page editing habit, and the general plug-in corresponding to the target component is automatically called by the platform. When the function is realized, the target component still realizes the basic function, while the target general plug-in realizes the general function. In this way, while the user does not need to change the page editing habit, the development requirements for component developers are reduced, and the component development cost is reduced.

[0059] In the embodiment of the present invention, the components and the general plug-in are executed according to the user's page editing operation instruction to implement the page editing function, and a page editing set is obtained, such as Figure 6 As shown, including: S410, receiving a page editing operation instruction from a user; S420, determining a page target function according to a page editing operation instruction of a user, wherein the page target function includes at least a basic function and a general function; It should be understood that when editing a page, the user issues a page editing operation instruction, and the page editing platform is able to parse the page editing operation instruction to obtain the page target function, that is, determine the editing goal to be achieved, and then the page target function determines its basic functions and general functions to facilitate calling components and corresponding general plug-ins.

[0060] S430, executing the components and the general plug-in according to the page target function; Execute the corresponding components and corresponding general plug-ins according to the determined page target functions. It should be noted here that since the execution order of components and the execution order of general plug-ins are configured when the platform material library is configured, it can be executed according to the configuration.

[0061] More specifically, executing the components and the general plug-in according to the page target function includes: Determine the execution order of multiple page target functions; The execution order of the target component and the target general plug-in under each page target function is determined according to the initialization configuration information of the page target function, wherein the execution priority of the target general plug-in of each page target function is higher than the execution priority of the target component.

[0062] It should be noted here that when a component is configured with a custom plug-in, the function of the general plug-in is usually executed first, then the function of the custom plug-in is executed, and finally the function of the component itself is executed.

[0063] S440, forming a page editing set with components that complete multiple page target functions.

[0064] In summary, the implementation method of the page editor platform provided by the present invention reduces the coupling between components and improves the robustness of components by designing the general capabilities of platform components as plug-ins. This plug-in design allows general capabilities to be independently developed, maintained and upgraded, and also makes the development and iteration of components more efficient and flexible. In addition, by highly abstracting the functional points of the components and designing them as plug-ins, each plug-in capability is isolated from each other, and each plug-in capability is relatively clear, thereby reducing the difficulty of implementing the main functions of the components. This design allows components and plug-ins to be developed independently, and different combinations achieve different component capabilities, further realizing the diversified expansion of component functions. Finally, the platform has a plug-in registration and identification mechanism, and provides general scaffolding for general plug-ins, custom plug-ins, components and elements. These scaffoldings help users generate general plug-ins, custom plug-ins, components and elements in an imperative manner, so that users can get started quickly. Such scaffolding capabilities greatly improve the user's development efficiency and learning curve.

[0065] As another embodiment of the present invention, a device 10 for implementing a page editor platform is provided, which is used to implement the method for implementing the page editor platform described above, wherein: Figure 7 As shown, including: Configuration module 100, used to configure the platform material library, the platform material library at least includes components and general plug-ins corresponding to the components, the components are used to implement the basic functions of page editing, and the general plug-ins are used to implement the general functions of page editing; The receiving module 200 is used to receive a page editing requirement instruction from a user, and generate a material call instruction according to the page editing requirement instruction; A calling module 300 is used to call components and general plug-ins in the platform material library according to the material calling instruction; The execution module 400 is used to execute the components and the general plug-in according to the user's page editing operation instruction to implement the page editing function and obtain a page editing set.

[0066] The implementation device of the page editor platform provided by the present invention configures the general functions of page editing into a general plug-in in the platform material library, and configures the basic functions of page editing into components in the platform material library, so that users can implement basic functions based on components when editing pages, while general functions are implemented by general plug-ins. This can reduce the development cost of components and the complexity of component implementation, making the functions of components and plug-ins more refined and facilitating the delivery and use of industrial software.

[0067] The specific working process of the implementation device of the page editor platform provided in the embodiment of the present invention can refer to the description of the implementation method of the page editor platform in the previous text, which will not be repeated here.

[0068] As another embodiment of the present invention, a storage medium is provided for storing computer instructions. When the computer instructions are called and executed by a processor, the implementation method of the page editor platform described above is implemented.

[0069] In an embodiment of the present invention, a non-transitory computer-readable storage medium is provided, wherein the computer-readable storage medium stores computer-executable instructions, and the computer-executable instructions can execute the implementation method of the page editor platform in any of the above method embodiments. The storage medium may be a disk, an optical disk, a read-only memory (ROM), a random access memory (RAM), a flash memory, a hard disk (HDD) or a solid-state drive (SSD), etc.; the storage medium may also include a combination of the above types of memories.

[0070] As another embodiment of the present invention, an electronic device is provided, which includes a memory and a processor, the memory and the processor are communicatively connected, the memory is used to store computer instructions, and the processor is used to load and execute the computer instructions to implement the implementation method of the page editor platform mentioned above.

[0071] like Figure 8As shown, the electronic device 80 may include: at least one processor 81, such as a CPU (Central Processing Unit), at least one communication interface 83, a memory 84, and at least one communication bus 82. The communication bus 82 is used to realize the connection and communication between these components. The communication interface 83 may include a display screen (Display) and a keyboard (Keyboard), and the optional communication interface 83 may also include a standard wired interface and a wireless interface. The memory 84 may be a high-speed RAM memory (Random Access Memory, volatile random access memory) or a non-volatile memory (non-volatile memory), such as at least one disk memory. The memory 84 may also be at least one storage device located away from the aforementioned processor 81. The memory 84 stores an application program, and the processor 81 calls the program code stored in the memory 84 to execute any of the above method steps.

[0072] The communication bus 82 may be a peripheral component interconnect (PCI) bus or an extended industry standard architecture (EISA) bus. The communication bus 82 may be divided into an address bus, a data bus, a control bus, etc. For ease of representation, Figure 8 Only one thick line is used in the diagram, but this does not mean that there is only one bus or only one type of bus.

[0073] Among them, the memory 84 may include a volatile memory (English: volatile memory), such as a random access memory (English: random-access memory, abbreviated: RAM); the memory may also include a non-volatile memory (English: non-volatile memory), such as a flash memory (English: flash memory), a hard disk drive (English: hard disk drive, abbreviated: HDD) or a solid-state drive (English: solid-state drive, abbreviated: SSD); the memory 84 may also include a combination of the above types of memory.

[0074] The processor 81 may be a central processing unit (CPU), a network processor (NP), or a combination of a CPU and a NP.

[0075] The processor 81 may further include a hardware chip. The hardware chip may be an application-specific integrated circuit (ASIC), a programmable logic device (PLD), or a combination thereof. The PLD may be a complex programmable logic device (CPLD), a field-programmable gate array (FPGA), a generic array logic (GAL), or any combination thereof.

[0076] Optionally, the memory 84 is also used to store program instructions. The processor 81 can call the program instructions to implement the present invention. Figure 1 The implementation method of the page editor platform shown in the embodiment.

[0077] In summary, the implementation method, device, storage medium and electronic device of the page editor platform provided by the present invention solve various problems faced by developers in the component development process through general plug-ins, such as data source access, chart component access, option data source access, visibility, event processing, editability and design capabilities. By abstractly encapsulating the platform capabilities into plug-ins, the component access cost is reduced by configuring the plug-ins, making the component capabilities clearer; the problems of excessive code volume and poor readability in the implementation of complex components are solved through custom plug-ins. By disassembling the special functions of the component into custom plug-ins for abstract encapsulation, the plug-in implementation is highly decoupled from the component implementation, reducing the difficulty of component implementation. Rich hook functions can run through the entire life cycle of the editing state and the running state of the component, helping the plug-in to expand at various stages and improving the stability and scalability of the component; through configuration, it is determined whether the component executes a plug-in to obtain specific capabilities, and the execution order of the plug-ins can also be determined through configuration to achieve different combinations of results.

[0078] Through the above functions, it is possible to stably and quickly develop page editor building platform components and realize rapid accumulation of components to meet the complex and ever-changing industrial software page delivery scenarios. The technical innovation of the present invention reduces the cost of component access platform, makes component and plug-in functions more refined, and provides important support for the delivery of industrial software.

[0079] It is to be understood that the above embodiments are merely exemplary embodiments used to illustrate the principles of the present invention, but the present invention is not limited thereto. For those of ordinary skill in the art, various modifications and improvements can be made without departing from the spirit and essence of the present invention, and these modifications and improvements are also considered to be within the scope of protection of the present invention.

Claims

1. A method for implementing a page editor platform, characterized in that: include: Configure a platform material library, the platform material library at least includes components and general plug-ins corresponding to the components, the components are used to implement basic page editing functions, and the general plug-ins are used to implement general page editing functions; Receive a page editing requirement instruction from a user, and generate a material call instruction according to the page editing requirement instruction; Calling components and general plug-ins in the platform material library according to the material calling instruction; The components and the general plug-in are executed according to the user's page editing operation instruction to realize the page editing function and obtain a page editing set.

2. The method for implementing the page editor platform according to claim 1, characterized in that: Generate a material call instruction according to the page editing requirement instruction, including: Parsing the page editing requirement instruction to obtain target component requirement information; A target component calling instruction is generated according to the target component requirement information.

3. The method for implementing the page editor platform according to claim 2, characterized in that: Calling components and general plug-ins in the platform material library according to the material calling instruction includes: Calling the target component in the platform material library according to the target component calling instruction; The target general plug-in corresponding to the target component is called according to the target component.

4. The method for implementing the page editor platform according to claim 1, characterized in that: Execute the components and the general plug-in according to the user's page editing operation instruction to implement the page editing function, and obtain a page editing set, including: Receive page editing operation instructions from users; Determine a page target function according to a page editing operation instruction of a user, wherein the page target function includes at least a basic function and a common function; Execute the components and common plug-ins according to the page target function; Components that complete multiple page target functions form a page editing collection.

5. The method for implementing the page editor platform according to claim 4, characterized in that: Executing the components and common plug-ins according to the page target function includes: Determine the execution order of multiple page target functions; The execution order of the target component and the target general plug-in under each page target function is determined according to the initialization configuration information of the page target function, wherein the execution priority of the target general plug-in of each page target function is higher than the execution priority of the target component.

6. The method for implementing the page editor platform according to any one of claims 1 to 5, characterized in that: Configure the platform material library, including: Initialize the page editor platform; Determine the component type of page editing according to the page editing model of the page editor platform; Determine the basic and common functions of each component type; Configure components according to the basic functions of each component type, and configure common plug-ins corresponding to the components according to the common functions of each component type; Configure the relationship and execution order between multiple components, and configure the execution order of each component and the corresponding common plug-in.

7. The method for implementing the page editor platform according to claim 6, characterized in that: The configuration platform material library also includes: Configure the custom plug-in corresponding to the component according to the extended functions of the component type.

8. The method for implementing the page editor platform according to claim 7, characterized in that: Also includes: The custom plug-in corresponding to the target component is called according to the material calling instruction, and the custom plug-in is executed when the target component is executed.

9. A device for implementing a page editor platform, used to implement the method for implementing a page editor platform according to any one of claims 1 to 8, characterized in that: include: A configuration module, used to configure a platform material library, wherein the platform material library includes at least a component and a general plug-in corresponding to the component, wherein the component is used to implement a basic page editing function, and the general plug-in is used to implement a general page editing function; A receiving module, used to receive a user's page editing requirement instruction, and generate a material call instruction according to the page editing requirement instruction; A calling module, used to call the components and general plug-ins in the platform material library according to the material calling instruction; The execution module is used to execute the components and the general plug-in according to the user's page editing operation instruction to realize the page editing function and obtain the page editing set.

10. A storage medium, characterized in that: Used to store computer instructions, when the computer instructions are called and executed by a processor, to implement the implementation method of the page editor platform described in any one of claims 1 to 8.

Images