Project construction configuration tool based on integrated development environment

Abstract

The invention relates to the technical field of computers, in particular to a project construction configuration tool based on an integrated development environment, which comprises a front end and a server, and the server comprises a project type analysis tool and a compilation grammar library module and is used for identifying project types, packaging a configuration template and sending the configuration template to the front end; and the front end serves as a graphical auxiliary configuration interface, obtains a grammar file and a data list corresponding to the server according to the obtained project type, displays the data list to a front end page, prompts a user to configure which attributes and grammar errors are required, and forms a json file which can be compiled and recognized according to user input for project construction. By means of the scheme, the user can be assisted in rapidly analyzing the imported project type through the visual program, and construction of different types of projects is achieved.

Description

Technical Field

[0001] This invention relates to the field of computer technology, specifically providing a project build configuration tool based on an integrated development environment. Background Technology

[0002] An Integrated Development Environment (IDE) is an application that provides a program development environment, typically including tools such as a code editor, compiler, debugger, and graphical user interface. Currently, IDEs are the choice of most developers and are widely used. IDEs offer various builders for everyday development, with commonly used languages ​​including C / C++, Java, and Python. To support project building for these languages, various configuration methods are available, such as VS Code's use of a `task.json` file to deploy build plugins.

[0003] Currently, configuration builds rely on command-line mode. While powerful, the command-line interface has cumbersome syntax, and the complexity of configuration commands makes it inconvenient for novice users, making it less user-friendly. Furthermore, the wide variety of project types, coupled with the lack of configuration options, makes editing corresponding configuration files complex, requiring the writing of numerous commands during the configuration build process. This not only increases workload but also raises the risk of errors. Summary of the Invention

[0004] To overcome the above-mentioned shortcomings, this invention proposes a project build configuration tool based on an integrated development environment.

[0005] A project build configuration tool based on an integrated development environment, including a front-end and a server-side. The server-side includes a project type analysis tool and a compilation syntax library module, which are used to identify project types, encapsulate configuration templates, and send them to the front end; The front-end serves as a graphical auxiliary configuration interface. Based on the obtained project type, it retrieves the corresponding syntax file and data list from the server, displays the data list on the front-end page, prompts the user on which attributes need to be configured and points out syntax errors, and generates a JSON file that can be recognized by the compiler based on the user's input for project building.

[0006] Furthermore, the workflow of the project type analysis tool includes: After a user imports a project into the integrated development environment, the project type analysis tool breaks down the imported project into multiple files, then uses a rule base to analyze each file in detail, and finally outputs the analyzed project type back to the front end.

[0007] Furthermore, the rule base includes: The file extensions are compared and filtered according to the file extension rules to determine the type of each file extension and obtain the first language type. By comparing the keywords and syntax rules corresponding to each language type, files with keywords are filtered out to determine the second language type; Provide a syntax comparison library for each language, and compare it with the project based on data type or declaration method to determine the third language type.

[0008] Obtain all language type results under the three rules, and select the type with the highest percentage as the project type to be built.

[0009] Furthermore, the compiled syntax library module provides data support to the front end, provides data attributes and data lists for configuration files, and also provides schema detection functionality to perform syntax analysis on the written format, prompt errors, and detect the existence of relevant dependency packages and provide feedback.

[0010] Furthermore, the data list is in the form of a multi-level list: The first layer includes multiple project types and multiple construction methods corresponding to each project type; The second layer includes data definition pages, which consist of fields such as attributes, descriptions, types, and order. Each data definition page can be obtained from the software toolkit documentation. The third layer includes a syntax definition page, which, based on the JSON schema syntax principle and combined with other language types, forms a syntax library consisting of syntax files for various new languages, which is then fed back to the front end.

[0011] Furthermore, the data verification provides syntax checking and dependency package detection during the user's configuration editing process. The syntax detection utilizes schema completion and detection principles, providing multiple types of schema files for detection. It converts and generates a JSON schema through tools, then establishes an association with the target JSON file, defines regular expressions, uses functions to process data, and validates lists and dictionaries to achieve verification and prompt functions.

[0012] The working principle and beneficial effects of this invention: In implementing the technical solution of this invention, a visual program can assist users in quickly analyzing the imported project type, providing corresponding build type templates, assisting users in editing build scripts, providing prompts, syntax error prompts, and package availability prompts, directly saving the build script, and executing the build script in conjunction with the integrated development environment platform to achieve the construction of different types of projects. Attached Figure Description

[0013] The disclosure of this invention will become more readily understood with reference to the accompanying drawings. It will be readily understood by those skilled in the art that these drawings are for illustrative purposes only and are not intended to limit the scope of protection of this invention. Furthermore, similar numbers in the drawings are used to denote similar components, wherein: Figure 1 This is a schematic diagram of the overall structure of a project build configuration tool based on an integrated development environment according to the present invention; Figure 2 This is an implementation flowchart of a project build configuration tool based on an integrated development environment according to the present invention; Figure 3 This is a schematic diagram of the project type analysis tool in this invention; Figure 4 This is a schematic diagram of the structure of the compilation syntax library module in this invention. Detailed Implementation

[0014] Some embodiments of the present invention will now be described with reference to the accompanying drawings. Those skilled in the art should understand that these embodiments are merely illustrative of the technical principles of the present invention and are not intended to limit the scope of protection of the present invention.

[0015] Figure 1 This is a schematic diagram of the overall structure of a project build configuration tool based on an integrated development environment according to the present invention. Figure 1 As shown, this embodiment proposes a project build configuration tool based on an integrated development environment, including a front-end and a server. The front-end is a client and is a graphical auxiliary configuration interface. The server is used to identify the project type, encapsulate configuration templates and send them to the front-end. The front-end is used to receive detailed configurations from the back-end and provide feedback to the user, giving the user more comprehensive configuration assistance.

[0016] In one implementation, the server includes a project type analysis tool and a compiler syntax library module. The compiler syntax library module establishes a syntax pool for common project types (including C / C++, Python, Java, etc.). For each project type, there are multiple build methods; for example, C / C++ build methods include cmake and make compilation. The compiler syntax library module selects the corresponding sub-syntax library to support project building based on the project type.

[0017] In one implementation, the front-end retrieves the corresponding syntax file and data list from the server based on the project type, displays the data list on the front-end page, binds a corresponding description to each control, prompts the user which attributes need to be configured, integrates a syntax analysis page table, and alerts the user to syntax errors. It also provides a function to save as a JSON file, generating a JSON file that the compiler can recognize based on user input.

[0018] Figure 2This is a flowchart illustrating the implementation process of a project build configuration tool based on an integrated development environment according to the present invention. Figure 2 As shown, after a user imports a project into the integrated development environment (IDE), the project workspace sends the project to the front end, which then transmits it to the server-side project type analysis tool. The tool decomposes the imported project, analyzes each file in detail using a rule base, and finally outputs the analyzed project type back to the front end. The compiler syntax library module provides data support for the front end's graphical auxiliary configuration interface, providing data attributes and descriptive large data lists for configuration files. It also provides schema detection functionality, performing syntax analysis on the written format, indicating errors, and checking for the existence of relevant dependency packages, providing timely feedback. The metadata in the compiler syntax library provides configuration data, and the syntax detection (schema detection function) allows querying and detecting based on input content, returning rule detection results. The graphical interface first provides the compiler syntax library with the currently input content data, which the syntax library then analyzes and returns the detection results. Specifically: In one implementation, Figure 3 This is a schematic diagram of the project type analysis tool in this invention. For example... Figure 3 As shown, the project type analysis tool uses a multi-layered grid structure. The y-axis represents the rules, and the x-axis represents the input of each decomposed file. The tool first decomposes the imported projects by file, integrates multiple rules to form a rule base, imports each file into a custom model built on the rule base, and uses the rule base to analyze each file in detail, outputting the project type to be constructed.

[0019] The working logic of the rule base is as follows: The file extensions are compared and filtered according to the file extension rules to determine the type of each file extension and obtain the first language type. By comparing the keywords and syntax rules corresponding to each project, files with keywords are filtered out to determine the second language type; Provide a syntax comparison library for each language, and compare it with the project based on data type or declaration method to determine the third language type.

[0020] Obtain all language type results under the three rules, and select the type with the highest percentage as the project type to be built.

[0021] In one implementation, Figure 4 This is a structural diagram of the compilation syntax library module in this invention. For example... Figure 4As shown, the compilation syntax library module is divided into two parts: a data list and data validation. After the project type analysis tool identifies the project type, it calls the corresponding configuration template composed of the data list. The configuration template is then returned to the front end, creating a dynamic graphical editable table for the user to edit. After the user completes the editing, a JSON file is generated for project building and can be used by the integrated development environment.

[0022] In this embodiment, the relevant definitions and descriptions of each language are used as metadata items. This metadata is used to provide raw data (i.e., "grammar rules" or "language specifications") for syntax checking. Based on this metadata, syntax checking files (which may be rule files, configuration files, or scripts) for different languages ​​can be generated for actual syntax checking (such as static code analysis, real-time syntax checking, etc.). Furthermore, the underlying logic of the graphical parameter editing relies on: language metadata (definitions and descriptions): providing hints about the language's structure, keywords, parameter types, etc.; and syntax checking files: real-time detection of whether user input conforms to the syntax rules.

[0023] The data list is in the form of a multi-level list: The first layer includes multiple project types and multiple build methods for each project type. First, obtain the project type and build method, then select the corresponding data definition page and syntax definition page.

[0024] The second layer includes the data definition page, which consists of fields such as attributes, descriptions, types, and order (i.e., ...). Figure 4 This includes definitions and descriptions of CMake and Maven commands. Each data definition page is obtained from the software toolkit documentation. Common templates are provided for building based on project type. The relationships between each attribute and their corresponding relationships are also provided for user-defined configurations.

[0025] The third layer includes a syntax definition page, which is based on the JSON schema syntax principle and combined with other language types to form a syntax library of syntax files for various new languages. This library is fed back to the front end, and users rely on the syntax library mechanism to complete the editing when editing the page.

[0026] Data validation provides syntax checking and dependency package detection (corresponding to "System Dependency Analysis" in the diagram) during the user's configuration editing process: Syntax detection utilizes schema completion and detection principles, providing multiple types of schema files for detection (corresponding to...). Figure 4 The "cmake syntax check file" and "maven syntax check file" are converted into JSONSchema by a tool, and then associated with the target JSON file. Regular expressions are defined, functions are used to process data, and lists and dictionaries are validated to implement validation and prompt functions.

[0027] The configuration process promptly detects user-inputted software packages and provides timely feedback on any software packages not installed on the system.

[0028] In one implementation, the following functions can be achieved on the front end: 1. Project type selection: This plugin not only automatically identifies project types through its parsing function, but also allows users to select project types via an intuitive interface. Each type has a pre-set parameter template to simplify the configuration process.

[0029] 2. Common parameter input: A user-friendly form interface is provided where users can fill in or select common parameters required for the project. These parameters will dynamically adjust based on the project type selected by the user.

[0030] 3. Dynamic management of parameter lists: The interface provides clear "Add" and "Delete" buttons, allowing users to flexibly add or delete parameter items to meet specific configuration needs.

[0031] 4. Parameter prompts and explanations: When a user hovers their mouse over any parameter or option, a pop-up window will appear, providing a detailed description and meaning of that parameter or option, enhancing the user experience.

[0032] 5. Configuration file script generation and saving: After the user completes the parameter input and saves it, the client will automatically convert these parameters into a file format that the platform can recognize, ensuring seamless integration and compilation with the platform.

[0033] 6. Configure script commands in the integrated development environment platform so that users can automatically build projects by calling the platform's built-in build tasks.

[0034] Based on the above-described project build configuration tool, a visual program can help users quickly analyze the imported project type, provide corresponding build type templates, assist users in editing build scripts, provide prompts, syntax error prompts, and package availability prompts, directly save the build script, and execute the build script in conjunction with the integrated development environment platform to achieve the build of different types of projects.

[0035] It should be noted that although the steps in the above embodiments are described in a specific order, those skilled in the art will understand that in order to achieve the effects of the present invention, different steps do not necessarily have to be executed in such an order. They can be executed simultaneously (in parallel) or in other orders, and these variations are all within the scope of protection of the present invention.

[0036] The technical solution of the present invention has been described above with reference to the preferred embodiments shown in the accompanying drawings. However, it will be readily understood by those skilled in the art that the scope of protection of the present invention is obviously not limited to these specific embodiments. Without departing from the principles of the present invention, those skilled in the art can make equivalent changes or substitutions to the relevant technical features, and the technical solutions after such changes or substitutions will all fall within the scope of protection of the present invention.

Claims

1. A project build configuration tool based on an integrated development environment, characterized in that, Including front-end and server-side, The server-side includes a project type analysis tool and a compilation syntax library module, which are used to identify project types, encapsulate configuration templates, and send them to the front end; The front-end serves as a graphical auxiliary configuration interface. Based on the obtained project type, it retrieves the corresponding syntax file and data list from the server, displays the data list on the front-end page, prompts the user on which attributes need to be configured and points out syntax errors, and generates a JSON file that can be recognized by the compiler based on the user's input for project building.

2. The project build configuration tool based on an integrated development environment according to claim 1, characterized in that, The workflow of the project type analysis tool includes: After a user imports a project into the integrated development environment, the project type analysis tool breaks down the imported project into multiple files, then uses a rule base to analyze each file in detail, and finally outputs the analyzed project type back to the front end.

3. The project build configuration tool based on an integrated development environment according to claim 2, characterized in that, The rule base includes: The file extensions are compared and filtered according to the file extension rules to determine the type of each file extension and obtain the first language type. By comparing the keywords and syntax rules corresponding to each language type, files with keywords are filtered out to determine the second language type; Provide a syntax comparison library for each language, compare it with the project based on data type or declaration method, and determine the third language type; Obtain all language type results under the three rules, and select the type with the highest percentage as the project type to be built.

4. The project build configuration tool based on an integrated development environment according to claim 1, characterized in that, The compiled syntax library module provides data support to the front end, provides data attributes and data lists for configuration files, and also provides schema detection function to perform syntax analysis on the written format, prompt errors, and detect whether the relevant dependency package system exists and provide feedback.

5. A project build configuration tool based on an integrated development environment according to claim 4, characterized in that, The data list is in the form of a multi-level list: The first layer includes multiple project types and multiple construction methods corresponding to each project type; The second layer includes data definition pages, which consist of fields such as attributes, descriptions, types, and order. Each data definition page can be obtained from the software toolkit documentation. The third layer includes a syntax definition page, which, based on the JSON schema syntax principle and combined with other language types, forms a syntax library consisting of syntax files for various new languages, which is then fed back to the front end.

6. A project build configuration tool based on an integrated development environment according to claim 4, characterized in that, The data verification provides syntax checking and dependency package detection during the user's configuration editing process. The syntax detection utilizes schema completion and detection principles, providing multiple types of schema files for detection. It converts and generates a JSON schema through tools, then establishes an association with the target JSON file, defines regular expressions, uses functions to process data, and validates lists and dictionaries to achieve verification and prompt functions.

Images