A project configuration method, system, computer device and storage medium

By pre-storing target utility classes in the class library and binding them to the project, and leveraging the relationships between the visual configuration page and canvas elements, the problems of redundant definition of utility classes and excessively long call times are solved. This enables rapid invocation and decoupling of project functions, reducing development costs.

CN116107626BActive Publication Date: 2026-02-17SHENZHEN MIRACLE WISDOM NETWORK CO LTD
View PDF 2 Cites 0 Cited by

Patent Information

Application Number
CN202310196267.1
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2023-02-24
Publication Date
2026-02-17
Estimated Expiration
2043-02-24

AI Technical Summary

Technical Problem

In object-oriented programming development projects, utility classes are often repeatedly defined and called too frequently due to scattered storage, which increases development costs.

Method used

The target utility classes are stored in a pre-defined library, bound to the project to be built according to functional requirements, and the canvas elements are determined and associated with each other using a visual configuration page. The canvas elements are then triggered to start and stop the target utility classes for quick invocation.

Benefits of technology

It decouples project functionality from code, improves the efficiency of utility class calls, reduces development costs, and supports the rapid introduction of new features.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN116107626B_ABST
    Figure CN116107626B_ABST
Patent Text Reader

Abstract

The application relates to a project configuration method, system, computer device and storage medium. The method comprises the following steps: acquiring function requirement information of a to-be-built project; performing a preset processing procedure according to the function requirement information, so as to determine at least one canvas element in the to-be-built project by using a preset visual configuration page, and select a target tool class corresponding to the canvas element from a preset class library; initializing the to-be-built project by loading the target tool class, so as to establish an association between the target tool class and the canvas element; and starting and stopping the target tool class by triggering the canvas element, and executing the target tool class according to a preset calling rule. According to the method, the project and the function code are independent of each other, the target tool class corresponding to the function requirement can be called at will according to the project requirement, and the target tool class can be quickly introduced to achieve the technical effect of out-of-box use.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This application relates to the field of development aids technology, and in particular to a project configuration method, system, computer device, and storage medium. Background Technology

[0002] In object-oriented programming development projects, as development progresses, engineers continuously define utility classes for various functions. Due to different project divisions and configurations, these utility classes are scattered across different software program files in different paths within different projects. This leads to engineers repeatedly defining utility classes with the same functionality within the same project or across different projects. When an engineer needs to call a utility class for a specific function, they have to search for the already defined utility class in multiple files, resulting in excessively long call times, low efficiency, repetitive work, and increased development costs. Summary of the Invention

[0003] Based on this, it is necessary to provide a project configuration method, system, computer equipment, and storage medium to address the above-mentioned technical problems. This solves the technical problems of repetitive work and excessively long call times caused by repeatedly defining utility classes in the prior art. By pre-storing target utility classes corresponding to various functions in a pre-defined class library, the target utility classes can be bound to the project to be built according to the functional requirements. This achieves the effect of quickly introducing utility classes and decoupling the various projects. The functions no longer depend on various projects, and can be used out of the box after binding.

[0004] This application provides a project configuration method, the method including:

[0005] Obtain the functional requirements information of the project to be built;

[0006] Based on the functional requirements information, execute the preset processing flow to use the preset visual configuration page to determine at least one canvas element in the project to be built, and select the target utility class corresponding to the canvas element from the preset class library;

[0007] By loading the target utility class, the project to be built is initialized to establish the association between the target utility class and the canvas elements;

[0008] The target utility class is started or stopped by triggering the canvas element, and then executed according to the preset calling rules.

[0009] In one embodiment, prior to the step of obtaining the functional requirements information of the project to be built, the following steps are included:

[0010] According to preset query rules, check whether the preset class library stores the target utility class corresponding to the functional requirement information;

[0011] If a target utility class corresponding to the functional requirements information is stored, the target utility class will be called directly from the preset class library when executing the project configuration; otherwise, the target utility class will be created in advance and stored in the preset class library.

[0012] In one embodiment, the step of creating a target utility class and storing it in a preset class library includes:

[0013] Define a configuration file for the target utility class, which serves as the carrier for encapsulating functional software.

[0014] Design a constructor for the configuration file and set the parameters of the constructor to instantiate the target utility class;

[0015] After the target utility class completes the data configuration processing, it is stored in a preset class library for instance method calls, and then the corresponding instantiated object is generated when the target utility class is instantiated.

[0016] In one embodiment, the step of setting the parameters of the constructor includes:

[0017] Set the following parameters for the constructor: default and version.

[0018] The default parameter represents the default basic configuration data;

[0019] The `version` parameter identifies the current version of the configuration file. If the `version` parameter is set, its value will be used; otherwise, the value of the `version` field in the root directory will be used by default.

[0020] In one embodiment, the steps include: triggering a canvas element to start or stop the target utility class, and executing the target utility class according to a preset invocation rule, including:

[0021] In response to the establishment of a relationship between the target utility class and the canvas element, a utility class event system is generated;

[0022] When one of the canvas elements is triggered to start or stop the corresponding target utility class, the first event is generated through the utility class event system; when the canvas element is triggered again, or when other canvas elements are triggered, the second event is generated, and so on, forming an event queue;

[0023] Execute the corresponding target utility class according to the event queue.

[0024] In one embodiment, the utility event system is configured with registration and deregistration events;

[0025] When a canvas element is triggered to start or stop the corresponding target utility class, the first event is generated through the utility class's event system; when the canvas element is triggered again, or when other canvas elements are triggered, the second event is generated, and so on, forming an event queue. The steps include:

[0026] When one of the canvas elements is triggered, the corresponding target utility class's registration event is generated through the utility class event system and used as the first event;

[0027] When a canvas element is triggered again, the corresponding unregister event of the target utility class is generated through the utility class event system, or when other canvas elements are triggered, the corresponding register event of the target utility class is generated through the utility class event system as a second event;

[0028] For the same target utility class, registration and deregistration events are generated alternately.

[0029] In one embodiment, the project to be built is a surveillance video cloud platform; the functional requirements include: quick focus function and gesture movement function.

[0030] The steps of starting and stopping the target utility class by triggering a canvas element and executing the target utility class according to preset invocation rules also include:

[0031] When the rapid aggregation function of the surveillance video cloud platform is triggered, a rectangle is drawn in the surveillance video interface, and the focus position of the camera is controlled according to the rectangle.

[0032] When the gesture movement function of the surveillance video cloud platform is triggered, a pointing indicator is generated in the surveillance video interface. The pointing indicator is moved according to the gesture command to control the monitoring direction of the camera.

[0033] This application provides a project configuration system, the system including:

[0034] The information acquisition module is used to acquire the functional requirements information of the project to be built;

[0035] The preset processing module is used to execute a preset processing flow based on functional requirement information, so as to use a preset visual configuration page to determine at least one canvas element in the project to be built, and select the target utility class corresponding to the canvas element from the preset class library.

[0036] The relationship establishment module is used to initialize the project to be built by loading the target utility class, so as to establish the association between the target utility class and the canvas element;

[0037] The tool execution module is used to start and stop the target tool class by triggering canvas elements, and to execute the target tool class according to preset calling rules.

[0038] This application provides a computer device, including a memory and a processor. The memory stores a computer program, and the processor executes the computer program to perform the following steps:

[0039] Obtain the functional requirements information of the project to be built;

[0040] Based on the functional requirements information, execute the preset processing flow to use the preset visual configuration page to determine at least one canvas element in the project to be built, and select the target utility class corresponding to the canvas element from the preset class library;

[0041] By loading the target utility class, the project to be built is initialized to establish the association between the target utility class and the canvas elements;

[0042] The target utility class is started or stopped by triggering the canvas element, and then executed according to the preset calling rules.

[0043] This application provides a computer-readable storage medium storing a computer program thereon, which, when executed by a processor, performs the following steps:

[0044] Obtain the functional requirements information of the project to be built;

[0045] Based on the functional requirements information, execute the preset processing flow to use the preset visual configuration page to determine at least one canvas element in the project to be built, and select the target utility class corresponding to the canvas element from the preset class library;

[0046] By loading the target utility class, the project to be built is initialized to establish the association between the target utility class and the canvas elements;

[0047] The target utility class is started or stopped by triggering the canvas element, and then executed according to the preset calling rules.

[0048] The above-mentioned project configuration method, system, computer equipment, and storage media have the following technical effects:

[0049] By using the functional requirements of the project to be built to determine the canvas elements and the corresponding target utility classes, and then establishing an association between the canvas elements and the target utility classes, the project to be built can have the functions corresponding to the target utility classes. This decouples the functions of the project to be built from the project code itself, making the project code and the functional code independent of each other, which makes it easy to maintain and expand the project and various functions.

[0050] By establishing a direct association between the target utility class and the canvas element, the target utility class is started and stopped by triggering the canvas element and executed according to the preset calling rules. This allows each function to be stored in the preset class library in the form of a target utility class. By calling the target utility class, it can be used out of the box without any dependencies between them. When a new function is quickly introduced into the target utility class, it will not affect the use of other functions in the project. Attached Figure Description

[0051] Figure 1 This is a flowchart illustrating the project configuration method in one embodiment;

[0052] Figure 2 This is a schematic diagram of the configuration process of a surveillance video cloud platform in one embodiment;

[0053] Figure 3 A block diagram of the project configuration system in one embodiment;

[0054] Figure 4 This is an internal structural diagram of a computer device in one embodiment. Detailed Implementation

[0055] Embodiments of the present invention are described in detail below. Examples of these embodiments are shown in the accompanying drawings, wherein the same or similar reference numerals denote the same or similar elements or elements having the same or similar functions throughout. The embodiments described below with reference to the accompanying drawings are exemplary and are only used to explain the present invention, and should not be construed as limiting the present invention.

[0056] Those skilled in the art will understand that, unless otherwise stated, the singular forms “a,” “an,” “the,” and “the” used herein may also include the plural forms. It should be further understood that the term “and / or” used herein includes all or any one and all combinations of one or more of the associated listed items.

[0057] It will be understood by those skilled in the art that, unless otherwise defined, all terms used herein (including technical and scientific terms) have the same meaning as commonly understood by one of ordinary skill in the art to which this invention pertains. It should also be understood that terms such as those defined in general dictionaries should be understood to have the same meaning as in the context of the prior art, and should not be interpreted in an idealized or overly formal sense unless specifically defined as herein.

[0058] In one embodiment, such as Figure 1 As shown, Figure 1 This is a flowchart illustrating a project configuration method in one embodiment. This embodiment proposes a project configuration method that can be applied to computer devices and specifically includes the following steps:

[0059] Step S101: Obtain the functional requirements information of the project to be built;

[0060] Step S102: Based on the functional requirements information, execute the preset processing flow to use the preset visual configuration page to determine at least one canvas element in the project to be built, and select the target tool class corresponding to the canvas element from the preset class library.

[0061] Step S103: Initialize the project to be built by loading the target utility class to establish the association between the target utility class and the canvas elements;

[0062] Step S104: The target utility class is enabled by triggering the canvas element, and the target utility class is executed according to the preset calling rules.

[0063] Before obtaining the functional requirements information of the project to be built in step S101, the following steps are included:

[0064] The system queries the preset class library to see if a target utility class corresponding to the functional requirements is stored. If a target utility class corresponding to the functional requirements is stored, the target utility class is directly called from the preset class library when the project configuration is executed. Otherwise, the target utility class is created in advance and stored in the preset class library.

[0065] In this context, the target utility class refers to the class type in the software project file. The step of querying the preset class library to see if a target utility class corresponding to the functional requirements is stored, based on preset query rules, involves identifying all defined target utility classes in the preset class library and extracting their definition content. This can also be understood as extracting the functional definition information of each target utility class in each preset class library. The functional definition information of the target utility class includes the data structures and functions defined by the class type. Furthermore, the extracted functional definition information can be used to create subsequent development tool templates, facilitating the computer's compilation by calling the structure types and functions within the functional definition information from the development tool template during program execution.

[0066] The functional definition information also includes program code and comment text. The comment text is used to mark and explain the program code, reflecting the functionality of the class type. Furthermore, the program code contains the names of data structure elements and functions; these names can sometimes also reflect the functionality of the class type through their meaning. Therefore, the functional definition information contains content reflecting the functionality of the target utility class. By extracting the functional identifier information that identifies the corresponding functionality of the target utility class from the functional definition information, the target utility class in the preset class library can be queried.

[0067] In one embodiment, the step of creating a target utility class and storing it in a preset class library includes:

[0068] Define a configuration file for the target utility class, which serves as the carrier for encapsulating functional software.

[0069] Design a constructor for the configuration file and set the parameters of the constructor to instantiate the target utility class;

[0070] After the target utility class completes the data configuration processing, it is stored in a preset class library for instance method calls, and then the corresponding instantiated object is generated when the target utility class is instantiated.

[0071] The steps for setting the parameters of the constructor include:

[0072] Set the following parameters for the constructor: default and version.

[0073] The `default` parameter represents the default basic configuration data; the `version` parameter identifies the version of the current configuration file. If the `version` parameter is set, its value will be used; otherwise, the value of the `version` field in the root directory will be used by default.

[0074] In step S102, based on the functional requirements information, a preset processing flow is executed to determine at least one canvas element in the project to be built using a preset visual configuration page, and to select the target tool class corresponding to the canvas element from a preset class library. This includes the following steps:

[0075] Based on the functional requirements information, at least one canvas element in the project to be built is determined using the preset visual configuration page.

[0076] Based on the functional requirements, select the target utility class corresponding to the canvas element from the preset class library.

[0077] The functional requirement information obtained in this embodiment may include a functional requirement form, which may be configured with keywords related to the class type, usage method, function, principle, etc. of various tools.

[0078] In this embodiment, a visual interface is used to display the configuration page of the project to be built. The configuration page has at least one configurable canvas element. Based on the functional requirements information, the canvas element to be configured is selected from the configuration page.

[0079] In one embodiment, the step of selecting a target utility class corresponding to a canvas element from a preset class library based on functional requirement information includes:

[0080] Based on the functional requirements information, obtain search terms. Search terms can be keywords such as the class type, usage method, function, and principle of the target tool.

[0081] The system matches search terms with function definition information or function identification information, selects target tool classes that match search terms from a preset class library, and then returns the matched target tool classes.

[0082] Based on functional requirements, a search is performed on a pre-defined class library to identify several similar or related target utility classes. Functional definition information and functional identifier information reflect the usage, function, and principles of the utility classes. For example, part of the naming in the program code of the functional definition information can reflect the function and usage of the utility class. Especially when coding is done according to coding rules, some naming conventions allow functional and principle information to be directly recorded in the member names of the target utility class; the functional identifier information can also directly reflect the function of the utility class. Matching from the definition information and functional identifier information allows for the rapid identification of matching utility classes.

[0083] In step S103, which initializes the project to be built by loading the target utility class to establish the association between the target utility class and the canvas elements, the target utility class is downloaded according to the determined canvas elements and the target utility class, and the target utility class is stored in the program file of the project to be built.

[0084] In step S103, the method for calling the target utility class selects the target utility corresponding to the canvas element from the preset class library, downloads the target utility class and stores it in the program file of the project to be built. This makes it easier for the project to call the target utility class, reduces the need to search multiple files in the project file to call the target utility class, improves the efficiency of calling the utility class, and avoids opening multiple files containing the utility class during compilation, thus reducing memory consumption.

[0085] In step S104, the process of starting and stopping the target utility class by triggering the canvas element and executing the target utility class according to the preset calling rules is as follows.

[0086] In response to the establishment of a relationship between the target utility class and the canvas element, a utility class event system is generated. When one of the canvas elements is triggered to start or stop the corresponding target utility class, the first event is generated through the utility class event system. When the canvas element is triggered again, or when other canvas elements are triggered, the second event is generated, and so on, forming an event queue. The corresponding target utility class is executed according to the event queue.

[0087] To further explain, in this step, triggering the canvas element enables or stops the corresponding target tool class, and installs or uninstalls the corresponding functional software. It can be seen that the target tool classes do not interfere with each other, and the target tool classes do not depend on the project to be built itself. They can be used by any project to be built with functional requirements. Each canvas element only needs to be responsible for its corresponding target tool class, and they do not interfere with each other. The target tool class can be started or stopped by triggering the canvas element, achieving the effect of being ready to use out of the box.

[0088] To further explain, in one embodiment, the utility event system is configured with registration events and deregistration events;

[0089] When a canvas element is triggered to start or stop the corresponding target utility class, the first event is generated through the utility class's event system; when the canvas element is triggered again, or when other canvas elements are triggered, the second event is generated, and so on, forming an event queue. The steps include:

[0090] When one canvas element is triggered, a registration event for the corresponding target utility class is generated through the utility class event system as the first event. When the canvas element is triggered again, a deregistration event for the corresponding target utility class is generated through the utility class event system, or when other canvas elements are triggered, a registration event for the corresponding target utility class is generated through the utility class event system as the second event. For the same target utility class, registration and deregistration events alternate.

[0091] In one embodiment, the project to be built is a surveillance video cloud platform; the functional requirements include: quick focus function and gesture movement function;

[0092] The steps of starting and stopping the target utility class by triggering a canvas element and executing the target utility class according to preset invocation rules also include:

[0093] When the rapid aggregation function of the surveillance video cloud platform is triggered, a rectangle is drawn in the surveillance video interface, and the focus position of the camera is controlled according to the rectangle.

[0094] When the gesture movement function of the surveillance video cloud platform is triggered, a pointing indicator is generated in the surveillance video interface. The pointing indicator is moved according to the gesture command to control the monitoring direction of the camera.

[0095] For further explanation, please refer to the appendix. Figure 2The diagram illustrates the configuration process of a surveillance video cloud platform in one embodiment. Within the platform, the quick focus and gesture movement functions from a preset library are bound to preset canvas elements on the visual configuration page. This enables the platform to possess these functions. Furthermore, by executing the operation to launch the target utility class, the corresponding canvas element is triggered, thus obtaining the desired functionality. In this embodiment, triggering the quick focus function results in drawing a rectangle, and the data for the drawn rectangle can be obtained through the mouse events bound to the quick focus function.

[0096] The above project configuration method, by determining canvas elements and corresponding target utility classes based on the functional requirements of the project to be built, and then establishing an association between the canvas elements and the target utility classes, enables the project to have the functionality corresponding to the target utility classes. This decouples the functionality of the project to be built from the project's own code, making the project code and functional code independent of each other, facilitating the maintenance and expansion of the project and its various functions. Because the direct association between the target utility classes and canvas elements is established, the target utility classes are started and stopped by triggering the canvas elements and executed according to preset calling rules. This allows each function to be stored in a preset class library as a target utility class, achieving out-of-the-box usability by calling the target utility class. The functions are independent of each other, and the rapid introduction of new functional target utility classes does not affect the use of other functions in the project.

[0097] It should be understood that although the steps in the attached flowchart are shown sequentially as indicated by the arrows, these steps are not necessarily executed in the order indicated by the arrows. Unless otherwise expressly stated herein, there is no strict order requirement for the execution of these steps, and they can be executed in other orders.

[0098] In one embodiment, such as Figure 3 As shown, a project configuration system is provided, including: an information acquisition module 201, a preset processing module 202, a relationship establishment module 203, and a tool execution module 204, wherein:

[0099] The information acquisition module 201 is used to acquire the functional requirements information of the project to be built;

[0100] The preset processing module 202 is used to determine at least one canvas element in the project to be built based on the functional requirements information and using a preset visual configuration page, and to select the target utility class corresponding to the canvas element from the preset class library.

[0101] The relationship establishment module 203 is used to initialize the project to be built by loading the target utility class, so that the target utility class and the canvas element have an association relationship;

[0102] The tool execution module 204 is used to start and stop the target tool class by triggering the canvas element, and to execute the target tool class according to the preset calling rules.

[0103] For specific limitations regarding the project configuration system, please refer to the limitations on the project configuration method above, which will not be repeated here. Each module in the aforementioned project configuration system can be implemented entirely or partially through software, hardware, or a combination thereof. These modules can be embedded in or independent of the processor in a computer device, or stored in the memory of a computer device as software, so that the processor can call and execute the corresponding operations of each module.

[0104] In one embodiment, a computer device is provided, which may be a server, and its internal structure diagram may be as follows: Figure 4 As shown, the computer device includes a processor, memory, network interface, and database connected via a system bus. The processor provides computing and control capabilities. The memory includes non-volatile storage media and internal memory. The non-volatile storage media stores the operating system, computer programs, and database. The internal memory provides an environment for the operation of the operating system and computer programs in the non-volatile storage media. The database stores project configuration data. The network interface communicates with external terminals via a network connection. When the computer program is executed by the processor, it implements a project configuration method.

[0105] Those skilled in the art will understand that Figure 4 The structure shown is merely a block diagram of a portion of the structure related to the present application and does not constitute a limitation on the computer device to which the present application is applied. Specific computer devices may include more or fewer components than those shown in the figure, or combine certain components, or have different component arrangements.

[0106] In one embodiment, a computer device is provided, including a memory and a processor, wherein the memory stores a computer program, and the processor executes the computer program to perform the following steps:

[0107] Obtain the functional requirements information of the project to be built; based on the functional requirements information, execute the preset processing flow to determine at least one canvas element in the project to be built using the preset visual configuration page, and select the target utility class corresponding to the canvas element from the preset class library; initialize the project to be built by loading the target utility class to establish the association between the target utility class and the canvas element; start and stop the target utility class by triggering the canvas element, and execute the target utility class according to the preset calling rules.

[0108] In one embodiment, a computer-readable storage medium is provided having a computer program stored thereon, the computer program performing the following steps when executed by a processor:

[0109] Obtain the functional requirements information of the project to be built;

[0110] Based on the functional requirements, a preset processing flow is executed to determine at least one canvas element in the project to be built using a preset visual configuration page, and to select the target utility class corresponding to the canvas element from the preset class library; by loading the target utility class, the project to be built is initialized to establish the association between the target utility class and the canvas element; by triggering the canvas element, the target utility class is started and stopped, and the target utility class is executed according to the preset calling rules.

[0111] Those skilled in the art will understand that all or part of the processes in the methods of the above embodiments can be implemented by a computer program instructing related hardware. The computer program can be stored in a non-volatile computer-readable storage medium. When executed, the computer program can include the processes of the embodiments of the above methods. Any references to memory, storage, databases, or other media used in the embodiments provided in this application can include non-volatile and / or volatile memory. Non-volatile memory can include read-only memory (ROM), programmable ROM (PROM), electrically programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM), or flash memory. Volatile memory can include random access memory (RAM) or external cache memory. By way of illustration and not limitation, RAM is available in various forms, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), dual data rate SDRAM (DDRSDRAM), enhanced SDRAM (ESDRAM), synchronous link DRAM (SLDRAM), Rambus direct RAM (RDRAM), direct memory bus dynamic RAM (DRDRAM), and memory bus dynamic RAM (RDRAM), etc.

[0112] The technical features of the above embodiments can be combined in any way. For the sake of brevity, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

[0113] The embodiments described above are merely illustrative of several implementation methods of this application, and while the descriptions are relatively specific and detailed, they should not be construed as limiting the scope of the invention patent. It should be noted that those skilled in the art can make various modifications and improvements without departing from the concept of this application, and these all fall within the protection scope of this application. Therefore, the protection scope of this patent application should be determined by the appended claims.

Claims

1. A project configuration method, characterized by, The method comprises: acquiring functional requirement information of a project to be built; performing a preset processing procedure according to the functional requirement information to determine at least one canvas element in the project to be built by using a preset visual configuration page, and to select a target tool class corresponding to the canvas element from a preset class library; initializing the project to be built by loading the target tool class to establish an association between the target tool class and the canvas element; starting and stopping the target tool class by triggering the canvas element, and executing the target tool class according to a preset calling rule.

2. The item configuration method of claim 1, wherein, Before the step of acquiring the functional requirement information of the project to be built, the method comprises: querying whether the target tool class corresponding to the functional requirement information is stored in the preset class library according to a preset query rule; if the target tool class corresponding to the functional requirement information is stored, directly calling the target tool class in the preset class library when performing project configuration, otherwise, creating the target tool class in advance and storing it in the preset class library.

3. The item configuration method of claim 2, wherein, The step of creating the target tool class and storing it in the preset class library comprises: defining a configuration file for the target tool class, the target tool class serving as a carrier of functional software encapsulation; designing a constructor for the configuration file and setting parameters of the constructor to instantiate the target tool class; after completing data configuration processing of the target tool class, storing it in the preset class library for instance method calling, thereby generating a corresponding instantiation object when instantiating the target tool class.

4. The item configuration method of claim 3, wherein, The step of setting the parameters of the constructor comprises: setting default parameters and version parameters for the constructor; the default parameters represent default basic configuration data; the version parameters represent a version identifying the current configuration file, if the version parameters are set, the parameter value of the version parameters is used as a reference, if the parameters are not set, the field value of the version field in the root directory is used by default.

5. The item configuration method of claim 4, wherein, The step of starting and stopping the target tool class by triggering the canvas element, and executing the target tool class according to a preset calling rule comprises: generating a tool class event system in response to the establishment of the association between the target tool class and the canvas element; generating a first event through the tool class event system when one of the canvas elements is triggered to start and stop the corresponding target tool class, generating a second event when the canvas element is triggered again or other canvas elements are triggered, and so on to form an event queue; executing the corresponding target tool class according to the event queue.

6. The item configuration method of claim 5, wherein, The tool class event system is configured with registration events and deregistration events; the first event is generated through the tool class event system when one of the canvas elements is triggered to start and stop the corresponding target tool class; the second event is generated when the canvas element is triggered again or other canvas elements are triggered, and so on to form an event queue. When one of the canvas elements is triggered, a registration event corresponding to the target tool class is generated as a first event through the tool class event system; When the canvas element is triggered again, a deregistration event corresponding to the target tool class is generated through the tool class event system, or when another canvas element is triggered, a registration event corresponding to the target tool class is generated as a second event through the tool class event system; Wherein, for the same target tool class, the registration event and the deregistration event are generated alternately.

7. The item configuration method of claim 5, wherein, The to-be-built project is a monitoring video cloud platform; The functional requirement information includes: a fast focusing function, a gesture moving function; The step of starting and stopping the target tool class by triggering the canvas element and executing the target tool class according to a preset calling rule further includes: When the fast focusing function of the monitoring video cloud platform is triggered, a rectangular frame is drawn in the monitoring video interface, and the focusing position of the camera is controlled according to the rectangular frame; When the gesture moving function of the monitoring video cloud platform is triggered, a pointing identifier is generated in the monitoring video interface, and the pointing identifier is moved to control the monitoring direction of the camera according to the gesture instruction.

8. A project configuration system characterized by The system comprises: An information acquisition module configured to acquire functional requirement information of a to-be-built project; A preset processing module configured to perform a preset processing procedure according to the functional requirement information, determine at least one canvas element in the to-be-built project by using a preset visual configuration page, and select a target tool class corresponding to the canvas element from a preset class library; A relationship establishing module configured to initialize the to-be-built project by loading the target tool class, and establish an association relationship between the target tool class and the canvas element; A tool executing module configured to start and stop the target tool class by triggering the canvas element, and execute the target tool class according to a preset calling rule. 9.A computer device, comprising a memory and a processor, wherein the memory stores a computer program, and the computer device is configured to perform the method according to any one of claims 1-8 when the computer program is executed by the processor. The processor executes the computer program to realize the steps of the method of any one of claims 1 to 7.

10. A computer-readable storage medium having stored thereon a computer program, characterized in that, The computer program is executed by the processor to realize the steps of the method of any one of claims 1 to 7.

Citation Information

Patent Citations

  • Customized software generation method and system, electronic device and storage medium

    CN110244977A

  • Information display method, device and equipment and computer storage medium

    CN113127586A