Program development auxiliary method, device and electronic equipment
By injecting web browser programs into the IDE and dynamically loading the visual designer or code editing interface, the problem of low development efficiency in low-code development platforms is solved, visual design and code editing in the same IDE tool is realized, and through the network Updates reduce the frequency of updates of IDE tools.
Patent Information
- Application Number
- CN202111583702.3
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2021-12-22
- Publication Date
- 2024-11-05
- Estimated Expiration
- 2041-12-22
AI Technical Summary
During the development process, existing low-code development platforms require frequent switching of code editing and visual designer tools, resulting in inefficient development.
By injecting web browser-related programs into the integrated development environment (IDE), providing metadata navigation and editing areas, dynamically loading the visual designer or code editing interface according to the metadata type, realizing visual design and code editing in the same IDE tool , and the visual designer is loading dynamically from the network, and only needs to update the website when updating.
Implementing one-stop visual design and code editing in the same IDE tool avoids the trouble of frequent switching tools, and improving update efficiency through silently upgrading plug-in programs and reducing the frequency of updates to IDE tools.
Smart Images

Figure CN114489613B_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the field of program development technology, and in particular to a program development auxiliary method, device and electronic device. Background Art
[0002] A low-code development platform (LCDP) is a development platform that can quickly generate applications without code (0 code) or with a small amount of code. This platform can provide users with a visual designer, and a method of developing applications through a visual designer, so that developers with different experience levels can use a graphical user interface, drag components and model-driven logic to create web pages and mobile applications. Of course, code editing may still be required in some logical calls and other aspects. For example, an application includes multiple pages, and the page design can be performed through a visual designer, but the calling logic between pages needs to be implemented by writing additional code.
[0003] In view of the above situation, one implementation method in the prior art is to provide two development environments for developers, one for writing code and the other for using a visual designer to perform visual design on pages, etc. However, the user needs to install two development tools, and in the process of application development, it is necessary to frequently switch between the two development tools, which seriously affects the development efficiency.
[0004] Therefore, how to further improve development efficiency has become a technical problem that needs to be solved by those skilled in the art. Summary of the invention
[0005] The present application provides a program development auxiliary method, device and electronic device, which can improve development efficiency and obtain the functions provided by the updated visual designer without updating the IDE tool.
[0006] This application provides the following solutions:
[0007] A program development auxiliary method, comprising:
[0008] Determine a target integrated development environment IDE tool, and inject a web browser related program into the IDE tool;
[0009] After receiving a request to edit the target development object through the IDE tool, providing an operation interface, the operation interface includes a metadata navigation area and an editing area, the metadata navigation area is used to create and / or display metadata associated with the target development object;
[0010] After receiving an editing request for the target metadata, if it is determined according to the type of the target metadata that the target metadata needs to be visually designed, the corresponding visual designer page is loaded through the web browser related program and the visual designer page is displayed in the editing area.
[0011] Among them, it also includes:
[0012] If the target metadata needs to be edited in code, a code editing interface provided by the IDE tool is displayed in the editing area.
[0013] Among them, there are multiple types of metadata that need to be visually designed, corresponding to different visual designers;
[0014] The method further comprises:
[0015] Determine a pre-configured network loading address, where the network loading address is multiple and corresponds to the multiple types of visual designers respectively;
[0016] The loading of the corresponding visual designer page through the web browser related program includes:
[0017] According to the type of the target metadata, a target network loading address corresponding to the type is determined so as to load a visual designer page corresponding to the type through a program related to the web browser.
[0018] Among them, it also includes:
[0019] According to the user's switching operation request, a linkage switching is performed between the visual designer page and the code editing interface in the editing area.
[0020] The step of performing a linkage switch between the visual designer page and the code editing interface in the editing area according to the user's switching operation request includes:
[0021] In a state where the visualizer design page is displayed in the editing area, upon receiving a target operation performed by a user on a target design node therein, switching the editing area to a code editing interface display state;
[0022] The code content generated for the target metadata is displayed in the code editing interface, and the code content corresponding to the target design node is located at the location for display.
[0023] Among them, it also includes:
[0024] After loading the visual designer page, injecting a target script method into the web browser-related program according to the signature information of the code content generated for the target metadata, so that the web browser-related program calls the target script method after receiving the target operation performed by the user on the target design node therein;
[0025] The switching of the editing area to the code editing interface display state includes:
[0026] The code content is called through an interface provided by the program related to the web browser so as to be displayed in the code editing interface.
[0027] Wherein, the step of performing linkage switching between the visual design page and the code editing interface in the editing area according to the user's switching operation request further includes:
[0028] After the editing area is switched to the code editing interface, if an operation request for viewing the visual designer submitted by the user is received, the editing area is switched back to the visual designer page display state.
[0029] Wherein, the method is performed by a plug-in program;
[0030] The method further includes: acquiring a new installation package for the plug-in program from a target file server, and silently upgrading the plug-in program.
[0031] Among them, it also includes:
[0032] By writing the user's login information on the server into the web browser-related program, the web browser-related program can achieve login-free access to the server.
[0033] A program development auxiliary device, comprising:
[0034] A web browser injection unit, used to determine a target integrated development environment IDE tool and inject a web browser related program into the IDE tool;
[0035] An operation interface providing unit, configured to provide an operation interface after receiving a request to edit the target development object through the IDE tool, wherein the operation interface includes a metadata navigation area and an editing area, wherein the metadata navigation area is used to create and / or display metadata associated with the target development object;
[0036] The visual designer page loading unit is used to receive an editing request for the target metadata, and if it is determined according to the type of the target metadata that the target metadata needs to be visually designed, load the corresponding visual designer page through the relevant program of the web browser, and display the visual designer page in the editing area.
[0037] A computer-readable storage medium stores a computer program, which, when executed by a processor, implements the steps of any of the methods described above.
[0038] An electronic device, comprising:
[0039] one or more processors; and
[0040] A memory associated with the one or more processors, the memory being used to store program instructions, wherein the program instructions, when read and executed by the one or more processors, execute the steps of any of the methods described above.
[0041] According to the specific embodiments provided in this application, this application discloses the following technical effects:
[0042] Through the embodiment of the present application, a plug-in can be provided for an IDE tool, and the IDE tool can be based on code editing as a basic function, that is, before the plug-in is used, the IDE tool itself does not support visual design, or can only perform limited visual design according to the built-in visual designer. The plug-in can inject the relevant program of the web browser into the IDE tool. In this way, after receiving a request to edit the target development object through the IDE tool, the plug-in can provide an operation interface, and the operation interface includes a metadata navigation area and an editing area. After receiving an editing request for the target metadata, the type of the target metadata can be determined, and whether the target metadata needs to be visually designed according to the type. If necessary, the corresponding visual designer page can be loaded through the relevant program of the web browser according to the pre-configured network loading address, and the visual editor page can be displayed in the editing area. In this way, a visual design function can be provided in the IDE tool, and a one-stop visual design and code editing capability can be provided to users in the same IDE tool without switching between a separate visual design tool and a code editing tool. Furthermore, since the pages of the visual designer can be dynamically loaded from a specific network loading address, if the visual designer needs to be updated, it only needs to be updated on the website without updating the IDE tool itself to obtain the latest functions provided by the visual designer.
[0043] Of course, any product implementing the present application does not necessarily need to achieve all of the advantages described above at the same time. BRIEF DESCRIPTION OF THE DRAWINGS
[0044] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings required for use in the embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying creative work.
[0045] Figure 1 It is a schematic diagram of the system architecture provided by the embodiment of the present application;
[0046] Figure 2 is a flow chart of the method provided in the embodiment of the present application;
[0047] Figure 3 is a schematic diagram of an interface provided by an embodiment of the present application;
[0048] Figure 4 is a schematic diagram of a device provided in an embodiment of the present application;
[0049] Figure 5 It is a schematic diagram of an electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION
[0050] The following will be combined with the drawings in the embodiments of the present application to clearly and completely describe the technical solutions in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. All other embodiments obtained by ordinary technicians in this field based on the embodiments in the present application belong to the scope of protection of this application.
[0051] In an embodiment of the present application, in order to improve development efficiency, a visual designer function can be provided in an IDE (Integrated Development Environment, an application program that provides a program development environment, generally including tools such as a code editor, a compiler, a debugger, and a graphical user interface, that is, an integrated development software service suite that integrates code writing, analysis, compilation, debugging, etc.) based on code editing, so that developers can complete visual design and code editing based on the same IDE tool without having to switch back and forth between the two tools.
[0052] In order to achieve the above purpose, a feasible way is to build a visual designer into the IDE so that the IDE tool has both visual design and code editing functions. However, the problem with this method is that the visual designer is usually updated frequently to provide more new functions, etc. If the visual designer is directly built into the IDE tool, it means that the high frequency of updating of the visual designer will require frequent version upgrades of the IDE tool, and developer users will need to frequently download new IDE tool installation packages and reinstall them.
[0053] In view of the above problems, an optimal solution is provided in the embodiments of the present application. In this solution, Figure 1 As shown, a plug-in program can be provided for the IDE tool, and the developer user can download and install the plug-in program. Through the plug-in program, a web browser-related program (for example, the kernel of a certain browser) can be injected into the specific IDE tool. In addition, the plug-in program can also provide specific interface display and operation control and other implementation logic, that is, after installing the above plug-in program, when the user needs to develop a selected object (for example, a web page or an application, etc.) in the IDE tool, the interface provided by the plug-in can be displayed. The interface may include a metadata navigation area and an editing area. The metadata navigation area can display the metadata that has been created (including pages, APIs, data models, etc.), and can also be used to create new metadata. After performing operations such as double-clicking on a certain metadata, a request for editing the metadata can be initiated. After that, the plug-in program can determine whether visual design or code editing is required based on the type of metadata. If code editing is required, the code editing interface provided by the IDE tool itself can be directly displayed in the editing area; and if visual design is required, the corresponding visual designer page can be loaded through the relevant program of the web browser, and displayed in the editing area of the interface. That is to say, the visual designer in the embodiment of the present application can be loaded from a specific website using a web browser, and the specific network loading address can be pre-configured in the plug-in. In this way, since the specific visual designer can be dynamically loaded from the website every time the IDE tool is needed to perform visual design, if the visual designer needs to be updated, it only needs to be updated in the specific website, and accordingly, the updated status can be obtained in the IDE tool without the need to frequently update the IDE tool.
[0054] In addition, since the interface that specifically supports visual design and code editing is provided by the plug-in, if the interface layout needs to be adjusted, such as adjusting some metadata navigation layout, etc., only the plug-in needs to be updated, and the IDE tool itself does not need to be updated. Among them, the update of the plug-in can be done in a silent upgrade mode to avoid disturbing users.
[0055] The specific implementation scheme provided in the embodiments of the present application is described in detail below.
[0056] First, the embodiment of the present application provides a program development auxiliary method from the perspective of the aforementioned plug-in program, see Figure 2 , the method may specifically include:
[0057] S201: Determine a target integrated development environment IDE tool, and inject web browser related programs into the IDE tool.
[0058] In the embodiment of the present application, a plug-in installation package can be provided to the developer user, and the developer user can complete the installation of the plug-in by downloading the installation package and installing it locally on the terminal device. After that, the plug-in can automatically determine the target IDE tool, and can inject web browser related programs into the IDE tool, such as the kernel program of a browser (usually referring to the rendering engine of the browser), etc. In this way, the IDE tool can obtain the ability to load and render the visual designer page in the network through the browser.
[0059] S202: After receiving a request to edit the target development object through the IDE tool, providing an operation interface, the operation interface includes a metadata navigation area and an editing area, the metadata navigation area is used to create and / or display metadata associated with the target development object.
[0060] After installing the plug-in, the plug-in can be activated when the user opens the specific IDE tool. After that, the user can select the target development object to be edited in the IDE tool. Among them, the development object can be a web page, an application, etc. The target development object can be a newly created development object, or a development object that has been created before but has not yet been developed, etc. In other words, assuming that the user wants to create a new application in the IDE tool and develop it, the project corresponding to the application can be created in the IDE tool, and then the development of the application can be started by double-clicking, that is, a request to edit the development object is initiated. Alternatively, assuming that the user has previously created an application in the IDE and has completed the development of some metadata, the developed data can be saved on the server side of the IDE tool. At this time, you can also choose to continue to develop and edit the application.
[0061] The metadata may correspond to the files that make up a specific web page or application program, and the specific metadata may include multiple types such as pages, APIs, data models, etc. For example, in the process of developing an application, you may need to develop multiple pages, multiple specific APIs, multiple data models, etc. Each page, API, and data model may correspond to one or more files. The specific development process through the IDE tool is the process of creating or editing these files.
[0062] When a user initiates a development and editing request for a newly created or previously created development object in the IDE tool, the specific plug-in program can display a specific operation interface. Figure 3 As shown, in the operation interface, a metadata navigation area 31 and an editing area 32 may be included. The metadata navigation area 31 may be used to display key metadata of the current target development object. If it is a new development object, the metadata displayed may be empty or only include the root directory in the initial state. The user may create metadata in the navigation area. If it is a development object that has been partially developed before, the metadata information associated with the development object may be obtained from the server and displayed in the navigation area.
[0063] When metadata is displayed in a specific navigation area, it can be displayed hierarchically in a tree structure, for example: Figure 3As shown at 311 in the figure, it is a first-level directory display area, which can display multiple first-level directories such as engineering, data, services, and interfaces. After selecting one of the first-level directories, the second-level directory can also be displayed at 312. For example, after selecting "Service" in the first-level directory, the second-level directory can include "API", "Excel Service", "Monitoring", etc. After that, you can continue to select in the second-level directory. For example, if you select API, you can display specific metadata in the area shown in 313. Alternatively, you can continue to provide a third-level directory, and then display specific metadata on the leaf node after continuing to select, and so on. For example, in the current development object, the specific API under the "Commodity" directory can include "Commodity Query", "Commodity Addition", "Commodity Query", etc. The specific metadata here can all be created by the user. In addition, the user can also create more metadata in the directory area. Among them, the new metadata is created specifically under the second-level category, and accordingly, the created metadata can have a type corresponding to the second-level category, such as API type, etc.
[0064] It should be noted here that Figure 3 The interface shown in, including the division of the metadata navigation area and the editing area, the specific layout method, and the specific operation logic, etc., can all be described in the plug-in program through data such as JSON (JavaScript Object Notation, JS object notation). In addition, with regard to specific metadata, if it is metadata that has been created before, the plug-in program can obtain its information by reading it from the server. In specific implementation, at the logic layer of the plug-in program, an operation interface can be dynamically created based on the aforementioned JSON data, and a connection between the plug-in program and the server can also be established to obtain data from the server, and subsequently submit specific data to the server, etc. In addition, at the core layer of the plug-in program, the ability to dynamically register and load the plug-in program's actions, extensions, services, listeners, etc. can also be provided.
[0065] It should also be noted that, in a specific implementation, the user login information can also be written into the web browser-related program to achieve login-free access to the server by the browser. For example, in a specific implementation, the plug-in program can first obtain the current user's login information on the server (for example, cookies (data stored on the user's terminal device) token, etc.), and then the cookie can be written into the browser. After that, the plug-in program loads the visual designer page through the browser, and the browser can submit the loading request of the visual designer page to the server. The page can be rendered by the server and then returned to the browser, and the browser then provides the rendering result to the plug-in program for display in a specific editing area.
[0066] S203: After receiving an editing request for the target metadata, if it is determined according to the type of the target metadata that the target metadata needs to be visually designed, a corresponding visual designer page is loaded through a related program of the web browser, and the visual designer page is displayed in the editing area.
[0067] After the specific metadata is displayed in the operation interface, the user can submit an edit request for the target metadata by double-clicking a certain target metadata. At this time, the specific plug-in program can take over the edit request, and can determine whether to perform visual design or code editing on the target metadata according to the type of the specific target metadata.
[0068] The types of metadata may include the aforementioned API, page, data model, etc. Depending on the type of metadata, it can be determined whether the user needs visual design or code editing. For example, if the type of the currently selected target metadata is API, page, etc., visual design is usually required. If the currently selected target metadata is metadata under the "project" directory, code editing is required in most cases, etc.
[0069] After determining the editing method required by the user, different editing interfaces can be provided in the editing area according to different editing methods. Among them, if the target metadata needs to be visually designed, the corresponding visual designer page can be loaded through the web browser-related program according to the pre-configured network loading address, and the visual editor page can be displayed in the editing area. In other words, if the current target metadata is an API or page type, visual design is usually required. At this time, the plug-in program can directly run the browser-related program pre-injected into the IDE and load the corresponding visual designer page. Among them, the visual designer page can be loaded from a specific website, and the network loading address can be pre-configured in the plug-in program. In this way, the visual design page displayed each time can be dynamically loaded from a specific website. In this way, if it involves updating the visual designer, it can be directly updated on the website side. After that, it can be ensured that the page of the visual designer loaded and displayed in the IDE is the latest page, without the need to upgrade and update the IDE tool.
[0070] The content of a specific visual designer page may be determined according to the logic in the specific visual designer. Figure 3 The interface shown in 32 may be a visual designer page, based on which the user can perform visual design on the currently selected API class metadata, for example, including adding nodes in the flowchart display area 321 and performing specific design in the specific node content display area 322, and so on.
[0071] It should be noted here that, as mentioned above, there are usually multiple types of metadata that need to be visually designed, including the aforementioned API, pages, data models, etc. For visual designers, there are usually visual designers corresponding to different types. Therefore, there can be multiple pre-configured network loading addresses, corresponding to the multiple types of visual designers. In this way, when loading a visual designer page, the target network loading address corresponding to the type of the target metadata can be determined, so that the visual designer page corresponding to the type can be loaded through the web browser related program.
[0072] Of course, if the target metadata that the user needs to edit belongs to engineering data, code editing is usually required instead of visual design. At this time, the specific plug-in program can display the code editing interface provided by the IDE tool in the editing area. Figure 3 The area shown in 32 can display specific codes, and the user can perform operations such as editing the code in this area.
[0073] In addition, in the embodiments of the present application, in addition to displaying a visual designer page or a code editing interface in the editing area according to the specific type of metadata that needs to be edited, it is also possible to perform a linkage switch between the visual design page and the code editing interface in the editing area according to the user's switching operation request.
[0074] For example, when the visual design page is displayed in the editing area, the user can Figure 3 In the example above, the user can double-click the "input" node in the 321 area, or other intermediate nodes, etc.) to initiate a request to view the specific code content. At this time, after receiving the target operation performed by the user on the target design node, the plug-in program can switch the editing area to the code editing interface display state. In addition, the code content generated for the target metadata can be displayed in the code editing interface, and the code content corresponding to the target design node can be located at the location where the code content is located for display. Among them, the code content corresponding to the specific target metadata can be generated in the IDE tool and saved locally on the terminal device. In other words, although the current target metadata is designed by the visual designer, in fact, as the user's design operation is executed, the background will also generate the corresponding code and save it. When the user initiates a request to view the code of a node in the visual design, the specific code saving path can be determined, the specific editing area can be switched to the code editing interface display state, and the specific code content saved under the path can be displayed in the code editing interface. In specific implementation, it can also be directly located at the location of the part of the code content corresponding to the target design node according to the target design node of the current operation for display, etc.
[0075] Among them, in order to realize the linkage between the display state of the above-mentioned visual design page and the display state of the code editing interface, from the background technology perspective, the communication capability between the plug-in program and the browser-related program can also be pre-implemented. For example, in one way, after loading the visual designer page, according to the signature information of the code content generated for the target metadata (which can be related to the save path of the specific code content), the target script method (for example, Javascript method, which can specifically include opening the API of the code editor, etc.) can be injected into the web browser-related program. In this way, after receiving the target operation performed by the user on the target design node, the web browser-related program can call the target script method. The plug-in program can call the specific code content through the interface provided by the web browser-related program. The communication between the plug-in program and the browser is realized in the above manner.
[0076] In addition, in addition to being able to switch from the visual designer state to the code editing state, it is also possible to switch from the code editing state back to the visual designer state. For example, after the editing area is switched to the code editing interface, if an operation request to view the visual designer submitted by the user is received, the editing area can be switched back to the visual designer page display state. Specifically, in the state of displaying the code editing interface, options such as "Open Visual Designer" can be provided through a right-click menu of the mouse, and the user can initiate a specific request to switch back to the visual designer state through this option, and so on.
[0077] Furthermore, as mentioned above, specific plug-in programs may also need to be updated. For example, when the layout of the operation interface or the operation logic needs to be modified, this can be achieved by updating the plug-in program without updating the entire IDE tool. In the specific implementation, in order to avoid excessive infection in the user's use process, the plug-in program can also be upgraded silently. Specifically, when the plug-in program needs to be updated, the provider of the plug-in program can publish the new plug-in installation package to the file server, and the plug-in program in the specific IDE can define the version list of the plug-in library, and compare the current version with the version in the list to determine whether there is a version update. If so, the latest version of the plug-in installation package can be downloaded. After that, the upgrade can be performed automatically. In an optional way, a restart prompt can also pop up, that is, after the user restarts the IDE tool, the functions provided by the latest version of the plug-in program can be obtained.
[0078] In summary, through the embodiment of the present application, a plug-in can be provided for the IDE tool, and the IDE tool can be based on code editing as a basic function, that is, before the plug-in is used, the IDE tool itself does not support visual design, or can only perform limited visual design according to the built-in visual designer. The plug-in can inject the relevant program of the web browser into the IDE tool. In this way, after receiving a request to edit the target development object through the IDE tool, the plug-in can provide an operation interface, and the operation interface includes a metadata navigation area and an editing area. After receiving an editing request for the target metadata, the type of the target metadata can be determined, and whether the target metadata needs to be visually designed according to the type. If necessary, the corresponding visual designer page can be loaded through the relevant program of the web browser according to the pre-configured network loading address, and the visual editor page can be displayed in the editing area. In this way, a visual design function can be provided in the IDE tool, and a one-stop visual design and code editing capability can be provided to users in the same IDE tool without switching between a separate visual design tool and a code editing tool. Furthermore, since the pages of the visual designer can be dynamically loaded from a specific network loading address, if the visual designer needs to be updated, it only needs to be updated on the website without updating the IDE tool itself to obtain the latest functions provided by the visual designer.
[0079] It should be noted that the embodiments of the present application may involve the use of user data. In actual applications, user-specific personal data can be used in the scheme described herein within the scope permitted by applicable laws and regulations, subject to the requirements of applicable laws and regulations of the country where the user is located (for example, with the user's explicit consent, effective notification to the user, etc.).
[0080] Corresponding to the above method embodiment, the present application embodiment also provides a program development auxiliary device, see Figure 4 , the device may include:
[0081] A web browser injection unit 401 is used to determine a target integrated development environment IDE tool and inject a web browser related program into the IDE tool;
[0082] The operation interface providing unit 402 is used to provide an operation interface after receiving a request to edit the target development object through the IDE tool, wherein the operation interface includes a metadata navigation area and an editing area, and the metadata navigation area is used to create and / or display metadata associated with the target development object;
[0083] The visual designer page loading unit 403 is used to receive an editing request for the target metadata, and if it is determined according to the type of the target metadata that the target metadata needs to be visually designed, load the corresponding visual designer page through the relevant program of the web browser, and display the visual designer page in the editing area.
[0084] In a specific implementation, the device may further include:
[0085] The code editing interface display unit is used to display the code editing interface provided by the IDE tool in the editing area if code editing is required for the target metadata.
[0086] Among them, there are multiple types of metadata that need to be visually designed, corresponding to different visual designers;
[0087] The device may also include:
[0088] A loading address determining unit, used to determine a pre-configured network loading address, wherein the network loading address is multiple and corresponds to the multiple types of visual designers respectively;
[0089] The visual designer page loading unit can be specifically used for:
[0090] According to the type of the target metadata, a target network loading address corresponding to the type is determined so as to load a visual designer page corresponding to the type through a program related to the web browser.
[0091] In addition, the device may also include:
[0092] The linkage switching unit is used to perform linkage switching between the visual designer page and the code editing interface in the editing area according to the user's switching operation request.
[0093] The linkage switching unit can be specifically used for:
[0094] In a state where the visualizer design page is displayed in the editing area, upon receiving a target operation performed by a user on a target design node therein, switching the editing area to a code editing interface display state;
[0095] The code content generated for the target metadata is displayed in the code editing interface, and the code content corresponding to the target design node is located at the location for display.
[0096] In addition, the device may also include:
[0097] A script injection unit, configured to inject a target script method into the web browser-related program according to the signature information of the code content generated for the target metadata after loading the visual designer page, so that the web browser-related program calls the target script method after receiving the target operation performed by the user on the target design node therein;
[0098] The linkage switching unit can be specifically used for:
[0099] The code content is called through an interface provided by the program related to the web browser so as to be displayed in the code editing interface.
[0100] In addition, the linkage switching unit can also be used for:
[0101] After the editing area is switched to the code editing interface, if an operation request for viewing the visual designer submitted by the user is received, the editing area is switched back to the visual designer page display state.
[0102] Wherein, the method is performed by a plug-in program;
[0103] The device may also include:
[0104] The silent upgrade unit is used to obtain a new installation package of the plug-in program from the target file server and silently upgrade the plug-in program.
[0105] In addition, the device may also include:
[0106] The login-free processing unit is used to write the user's login information on the server into the program related to the web browser, so as to realize the login-free access of the program related to the web browser to the server.
[0107] In addition, an embodiment of the present application further provides a computer-readable storage medium on which a computer program is stored, and when the program is executed by a processor, the steps of any one of the methods in the aforementioned method embodiments are implemented.
[0108] And an electronic device, comprising:
[0109] one or more processors; and
[0110] A memory associated with the one or more processors, the memory being used to store program instructions, wherein the program instructions, when read and executed by the one or more processors, execute the steps of the method described in any one of the aforementioned method embodiments.
[0111] in, Figure 5The architecture of the electronic device is shown as an example, which may include a processor 510, a video display adapter 511, a disk drive 512, an input / output interface 513, a network interface 514, and a memory 520. The processor 510, the video display adapter 511, the disk drive 512, the input / output interface 513, the network interface 514, and the memory 520 may be communicatively connected via a communication bus 530.
[0112] Among them, the processor 510 can be implemented by a general-purpose CPU (Central Processing Unit, processor), a microprocessor, an application specific integrated circuit (Application Specific Integrated Circuit, ASIC), or one or more integrated circuits, etc., to execute relevant programs to implement the technical solution provided in this application.
[0113] The memory 520 can be implemented in the form of ROM (Read Only Memory), RAM (Random Access Memory), static storage device, dynamic storage device, etc. The memory 520 can store an operating system 521 for controlling the operation of the electronic device 500, and a basic input and output system (BIOS) for controlling the low-level operation of the electronic device 500. In addition, a web browser 523, a data storage management system 524, and a program development auxiliary processing system 525, etc. can also be stored. The above-mentioned program development auxiliary processing system 525 can be an application program that specifically implements the aforementioned steps in the embodiment of the present application. In short, when the technical solution provided by the present application is implemented by software or firmware, the relevant program code is stored in the memory 520 and is called and executed by the processor 510.
[0114] The input / output interface 513 is used to connect the input / output module to realize information input and output. The input / output module can be configured in the device as a component (not shown in the figure), or it can be externally connected to the device to provide corresponding functions. The input device may include a keyboard, a mouse, a touch screen, a microphone, various sensors, etc., and the output device may include a display, a speaker, a vibrator, an indicator light, etc.
[0115] The network interface 514 is used to connect to a communication module (not shown) to realize communication interaction between the device and other devices. The communication module can realize communication through a wired mode (such as USB, network cable, etc.) or a wireless mode (such as mobile network, WIFI, Bluetooth, etc.).
[0116] The bus 530 comprises a pathway for transmitting information between the various components of the device (eg, the processor 510, the video display adapter 511, the disk drive 512, the input / output interface 513, the network interface 514, and the memory 520).
[0117] It should be noted that, although the above device only shows a processor 510, a video display adapter 511, a disk drive 512, an input / output interface 513, a network interface 514, a memory 520, a bus 530, etc., in the specific implementation process, the device may also include other components necessary for normal operation. In addition, it can be understood by those skilled in the art that the above device may also only include components necessary for implementing the solution of the present application, and does not necessarily include all the components shown in the figure.
[0118] It can be known from the description of the above implementation methods that those skilled in the art can clearly understand that the present application can be implemented by means of software plus a necessary general hardware platform. Based on such an understanding, the technical solution of the present application can be essentially or partly contributed to the prior art in the form of a software product, which can be stored in a storage medium such as ROM / RAM, a magnetic disk, an optical disk, etc., and includes several instructions for enabling a computer device (which can be a personal computer, a server, or a network device, etc.) to execute the methods described in the various embodiments of the present application or certain parts of the embodiments.
[0119] Each embodiment in this specification is described in a progressive manner, and the same or similar parts between the embodiments can refer to each other, and each embodiment focuses on the differences from other embodiments. In particular, for the system or system embodiment, since it is basically similar to the method embodiment, the description is relatively simple, and the relevant parts can refer to the partial description of the method embodiment. The system and system embodiments described above are merely schematic, wherein the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, they may be located in one place, or they may be distributed on multiple network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the scheme of this embodiment. Ordinary technicians in this field can understand and implement it without creative work.
[0120] The program development auxiliary method, device and electronic device provided by this application are introduced in detail above. The principle and implementation method of this application are explained in this article by using specific examples. The description of the above embodiments is only used to help understand the method and core idea of this application. At the same time, for those skilled in the art, according to the idea of this application, there will be changes in the specific implementation method and application scope. In summary, the content of this specification should not be understood as limiting this application.
Claims
1. A program development auxiliary method, characterized in that: The method is executed by a plug-in program and includes: Determine a target integrated development environment IDE tool, and inject a web browser related program into the IDE tool; the IDE tool has code editing as a basic function; After receiving a request for code editing of a target development object through the IDE tool, an operation interface is provided, wherein the operation interface includes a metadata navigation area and an editing area, wherein the metadata navigation area is used to create and / or display metadata associated with the target development object; wherein the metadata includes a plurality of files constituting the target development object, and the types of the metadata include pages, application programming interfaces APIs and / or data models; After receiving an editing request for the target metadata, if it is determined according to the type of the target metadata that the target metadata needs to be visually designed, a web browser-related program pre-injected into the IDE tool is run, and according to a network loading address pre-configured in the plug-in program, a corresponding visual designer page is loaded through the web browser-related program, and the visual designer page is displayed in the editing area; wherein the pre-configured network loading address includes a plurality of network loading addresses corresponding to a plurality of types of visual designers, respectively, so as to provide visual design and code editing capabilities in the same IDE tool.
2. The method according to claim 1, characterized in that: Also includes: If the target metadata needs to be edited in code, a code editing interface provided by the IDE tool is displayed in the editing area.
3. The method according to claim 1, characterized in that There are many types of metadata that need to be visually designed, corresponding to various types of visual designers; The loading of the corresponding visual designer page through the web browser related program includes: According to the type of the target metadata, a target network loading address corresponding to the type is determined so as to load a visual designer page corresponding to the type through a program related to the web browser.
4. The method according to claim 1, characterized in that: Also includes: According to the user's switching operation request, a linkage switching is performed between the visual designer page and the code editing interface in the editing area.
5. The method according to claim 4, characterized in that The step of performing a linkage switch between the visual designer page and the code editing interface in the editing area according to the user's switching operation request includes: In a state where the visual designer design page is displayed in the editing area, upon receiving a target operation performed by a user on a target design node therein, switching the editing area to a code editing interface display state; The code content generated for the target metadata is displayed in the code editing interface, and the code content corresponding to the target design node is located at the location for display.
6. The method according to claim 5, characterized in that Also includes: After loading the visual designer page, injecting a target script method into the web browser-related program according to the signature information of the code content generated for the target metadata, so that the web browser-related program calls the target script method after receiving the target operation performed by the user on the target design node therein; The switching of the editing area to the code editing interface display state includes: The code content is called through an interface provided by the program related to the web browser so as to be displayed in the code editing interface.
7. The method according to claim 5, characterized in that The step of performing linkage switching between the visual design page and the code editing interface in the editing area according to the user's switching operation request also includes: After the editing area is switched to the code editing interface, if an operation request for viewing the visual designer submitted by the user is received, the editing area is switched back to the visual designer page display state.
8. The method according to claim 1, characterized in that Also includes: A new installation package for the plug-in program is obtained from the target file server, and the plug-in program is silently upgraded.
9. The method according to claim 1, characterized in that: Also includes: By writing the user's login information on the server into the web browser-related program, the web browser-related program can achieve login-free access to the server.
10. A program development assisting device, characterized in that: The device is applied to a plug-in program, and includes: A web browser injection unit is used to determine a target integrated development environment IDE tool and inject web browser related programs into the IDE tool; the IDE tool has code editing as a basic function; An operation interface providing unit is used to provide an operation interface after receiving a request for code editing of a target development object through the IDE tool, wherein the operation interface includes a metadata navigation area and an editing area, wherein the metadata navigation area is used to create and / or display metadata associated with the target development object; wherein the metadata includes a plurality of files constituting the target development object, and the types of the metadata include pages, application programming interfaces APIs and / or data models; A visual designer page loading unit is used for, after receiving an editing request for target metadata, if it is determined according to the type of the target metadata that the target metadata needs to be visually designed, running a web browser-related program pre-injected into the IDE tool, loading a corresponding visual designer page through the web browser-related program according to a network loading address pre-configured in the plug-in program, and displaying the visual designer page in the editing area; wherein the pre-configured network loading address includes a plurality of network loading addresses corresponding to a plurality of types of visual designers, so as to provide visual design and code editing capabilities in the same IDE tool.
11. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the program is executed by a processor, the steps of the method described in any one of claims 1 to 9 are implemented.
12. An electronic device, characterized in that: include: one or more processors; as well as A memory associated with the one or more processors, the memory being used to store program instructions, wherein the program instructions, when read and executed by the one or more processors, execute the steps of the method described in any one of claims 1 to 9.
