Editor version updating method and device, equipment and storage medium
By displaying the version information of the branch and editor version and automatically obtaining and loading the resources of the target editor version, the time-consuming and error-prone editor version switching in the existing technology is solved, and a fast and intelligent editor version switching is achieved.
Patent Information
- Application Number
- CN202510237786.7
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2025-02-28
- Publication Date
- 2025-06-10
AI Technical Summary
In the existing game development field, the way of managing editor versions requires developers to manually enter paths and operation instructions, which have problems such as operation errors and time-consuming, and lacks an easy-to-operate version switching method.
By displaying the version information of the branch and editor version, after receiving the switch trigger operation, obtain the resource of the target editor version, load and run the target editor version.
It realizes quick switching of any branch and editor version and automatically downloads required resources, simplifying the management and switching process of editor versions and improving efficiency.
Smart Images
Figure CN120122966A_ABST
Abstract
Description
Technical Field
[0001] The present disclosure relates to the field of data processing, and in particular, to a method, apparatus, device, and storage medium for updating an editor version. Background Art
[0002] In the existing game development field, the management method of the editor version usually requires developers to manually input the paths of the editors of each version and related operation instructions to interact with the version control system to implement the update and switching of the editor version.
[0003] However, accurately inputting various paths and related operation instructions has a certain technical threshold, and manually implementing the update and switching of the editor version has problems such as time-consuming version update and switching caused by operation errors.
[0004] Therefore, how to provide an easy-to-operate method for developers to switch the editor version is a technical problem that needs to be solved urgently at present. Summary of the Invention
[0005] In order to solve the above technical problems or at least partially solve the above technical problems, the present disclosure provides a method, apparatus, device, and storage medium for updating an editor version.
[0006] In a first aspect, an embodiment of the present disclosure provides a method for updating an editor version, the method including:
[0007] Displaying at least one branch and version information of at least one editor version corresponding to each branch; wherein, the at least one editor version corresponding to each branch is determined based on editor version management information;
[0008] After receiving a switching trigger operation for a target editor version corresponding to a target branch among the at least one branch, obtaining resources under the resource version corresponding to the target editor version;
[0009] Loading and running an editor of the target editor version based on the resources under the target branch.
[0010] In an optional implementation manner, before the displaying at least one branch and version information of at least one editor version corresponding to each branch, further included:
[0011] Obtaining an editor commit log of a version management system, and parsing the editor commit log to obtain an editor version list; wherein, the editor version list records the correspondence between branches and editor versions;
[0012] Determine at least one branch from the list of editor versions, and at least one editor version corresponding to each branch in the at least one branch; wherein, the at least one editor version belongs to a part or all of the editor versions of the corresponding branch.
[0013] In an alternative implementation, after receiving a switching trigger operation for a target editor version corresponding to a target branch in the at least one branch, obtaining resources under the resource version corresponding to the target editor version includes:
[0014] After receiving a switching trigger operation for a target editor version corresponding to a target branch in the at least one branch, based on the resource difference between the local editor version and the target editor version, obtain resources under the resource version corresponding to the target editor version from the target resource server.
[0015] In an alternative implementation, the resources under the resource version corresponding to the target editor version include various types of resources, and each of the various types of resources has a corresponding resource version. After receiving a switching trigger operation for a target editor version corresponding to a target branch in the at least one branch, obtaining resources under the resource version corresponding to the target editor version includes:
[0016] After receiving a switching trigger operation for a target editor version corresponding to a target branch in the at least one branch, based on the resource versions corresponding to the various types of resources respectively, obtain the resources required for the operation of the editor of the target editor version respectively.
[0017] In an alternative implementation, after receiving a switching trigger operation for a target editor version corresponding to a target branch in the at least one branch, obtaining resources under the resource version corresponding to the target editor version includes:
[0018] After receiving a switching trigger operation for a target editor version corresponding to a target branch in the at least one branch, obtain the target type resources under the resource version corresponding to the target editor version; wherein, the target type resources are necessary part of the resources required for the operation of the editor of the target editor version.
[0019] In an alternative implementation, the method further includes:
[0020] In response to a local editor management trigger operation, identify local files through editor feature information, determine the local files that match the editor feature information as local editors, and add the editor versions to which the local editors belong to the editor management directory; wherein, the editor management directory is used to manage editor versions.
[0021] In a second aspect, the present disclosure provides an editor version update device, the device comprising:
[0022] a display module, configured to display at least one branch and version information of at least one editor version corresponding to each branch; wherein, the at least one editor version corresponding to each branch is determined based on editor version management information;
[0023] an acquisition module, configured to acquire resources under the resource version corresponding to the target editor version after receiving a switching trigger operation for the target editor version corresponding to the target branch among the at least one branch;
[0024] a running module, configured to load and run an editor of the target editor version based on the resources under the target branch.
[0025] In a third aspect, an embodiment of the present disclosure further provides an electronic device, the electronic device comprising: a processor; a memory for storing executable instructions of the processor; the processor is configured to read the executable instructions from the memory and execute the instructions to implement the editor version update method provided by the embodiment of the present disclosure.
[0026] In a fourth aspect, an embodiment of the present disclosure further provides a computer-readable storage medium, the storage medium stores a computer program, and the computer program is used to execute the editor version update method provided by the embodiment of the present disclosure.
[0027] In a fifth aspect, the present disclosure provides a computer program product, the computer program product comprising a computer program / instructions, and when the computer program / instructions are executed by a processor, the above method is implemented.
[0028] The technical solution provided by the embodiment of the present disclosure has the following advantages compared with the prior art:
[0029] In the editor version update method provided by the embodiment of the present disclosure, first, at least one branch and version information of at least one editor version corresponding to each branch are displayed, wherein, the at least one editor version corresponding to each branch is determined based on editor version management information. Then, after receiving a switching trigger operation for the target editor version corresponding to the target branch among the at least one branch, resources under the resource version corresponding to the target editor version are acquired. An editor of the target editor version is loaded and run based on the resources under the target branch.
[0030] Embodiments of the present disclosure support quick switching for any editor version corresponding to any branch, and at the same time automatically download the resources required for the operation of the editor of that editor version, realizing the one-key intelligent editor version switching function. Compared with the method of switching the editor version by manually inputting the path and relevant operation instructions, the embodiments of the present disclosure provide an easy-to-operate method for switching the editor version, improving the switching efficiency of the editor version. BRIEF DESCRIPTION OF THE DRAWINGS
[0031] In combination with the accompanying drawings and with reference to the following specific embodiments, the above and other features, advantages and aspects of the various embodiments of the present disclosure will become more apparent. Throughout the drawings, the same or similar reference numerals represent the same or similar elements. It should be understood that the drawings are schematic and the original elements and elements are not necessarily drawn to scale.
[0032] Figure 1 It is a schematic flowchart of a method for updating an editor version provided by an embodiment of the present disclosure;
[0033] Figure 2 It is a schematic flowchart of another method for updating an editor version provided by an embodiment of the present disclosure;
[0034] Figure 3 It is a schematic structural diagram of an apparatus for updating an editor version provided by an embodiment of the present disclosure;
[0035] Figure 4 It is a schematic structural diagram of a device for updating an editor version provided by an embodiment of the present disclosure. DETAILED DESCRIPTION OF THE EMBODIMENTS
[0036] The embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. Although some embodiments of the present disclosure are shown in the drawings, it should be understood that the present disclosure can be implemented in various forms and should not be construed as limited to the embodiments set forth herein. On the contrary, these embodiments are provided to more thoroughly and completely understand the present disclosure. It should be understood that the drawings and embodiments of the present disclosure are only for exemplary purposes and are not used to limit the protection scope of the present disclosure.
[0037] It should be understood that the various steps recorded in the method embodiments of the present disclosure can be executed in different orders and / or executed in parallel. In addition, the method embodiments may include additional steps and / or omit the steps shown. The scope of the present disclosure is not limited in this regard.
[0038] As used herein, the term "including" and its variations are open-ended, that is, "including but not limited to". The term "based on" means "at least partially based on". The term "one embodiment" means "at least one embodiment"; the term "another embodiment" means "at least one additional embodiment"; the term "some embodiments" means "at least some embodiments". The relevant definitions of other terms will be given in the following description.
[0039] It should be noted that the concepts such as "first", "second", etc. mentioned in this disclosure are only used to distinguish different devices, modules or units, and are not used to limit the order or interdependence relationship of the functions performed by these devices, modules or units.
[0040] It should be noted that the modifications of "one" and "a plurality of" mentioned in this disclosure are illustrative rather than restrictive. Those skilled in the art should understand that unless clearly stated otherwise in the context, it should be understood as "one or more".
[0041] The names of the messages or information exchanged between multiple devices in the embodiments of this disclosure are only for illustrative purposes and are not used to limit the scope of these messages or information.
[0042] In the existing game development field, the management method of editor versions usually requires developers to manually input the paths of editors of each version and related operation instructions to interact with the version control system to achieve the update and switching of editor versions.
[0043] However, there is a certain technical threshold for accurately inputting various paths and related operation instructions. There are problems such as time-consuming version update and switching caused by operation errors in manually implementing the update and switching of editor versions.
[0044] Therefore, how to provide an easy-to-operate editor version switching method for developers is a technical problem that urgently needs to be solved at present.
[0045] For this purpose, the embodiments of this disclosure provide an editor version update method. Specifically, first, at least one branch and the version information of at least one editor version corresponding to each branch are displayed, where the at least one editor version corresponding to each branch is determined based on editor version management information. After receiving a switching trigger operation for the target editor version corresponding to the target branch among the at least one branch, the resources under the resource version corresponding to the target editor version are obtained. The editor of the target editor version is loaded and run based on the resources under the target branch.
[0046] The embodiments of the present disclosure support quick switching for any editor version corresponding to any branch, and automatically download the resources required for the operation of the editor of this editor version at the same time, realizing the one-key intelligent editor version switching function. Compared with the method of switching the editor version by manually inputting the path and related operation instructions, the embodiments of the present disclosure provide an easy-to-operate method for switching the editor version, improving the switching efficiency of the editor version.
[0047] Based on this, the embodiments of the present disclosure provide a method for updating the editor version. The following introduces this method in combination with specific embodiments.
[0048] Figure 1 FIG. is a schematic flowchart of a method for updating the editor version provided by the embodiments of the present disclosure. This method can be executed by an editor version update device, where the device can be implemented by software and / or hardware and is generally integrated in an electronic device. As Figure 1 shown, this method includes:
[0049] S101: Display the version information of at least one branch and at least one editor version corresponding to each branch.
[0050] Among them, the at least one editor version corresponding to each branch is determined based on the editor version management information.
[0051] The method for updating the editor version provided by the embodiments of the present disclosure is applied to a client. Specifically, the client can be deployed on terminals such as smart phones, tablet computers, and desktop computers.
[0052] In a version management system, a branch can refer to an independent development line separated from the main trunk code. Developers can develop different functions and test different functions in parallel on different branches without affecting the main trunk code, that is, each branch is independent and does not affect each other. Each branch contains corresponding code files and resource files, and the resource files are files such as images, audio, and special effects. Each branch corresponds to one or more editor versions. The editor version can refer to a specific form released by the editor at different stages, and different versions of the editor have differences in functions, performance, etc. Among them, the version management system is a software tool used to track and manage project file changes.
[0053] In the embodiments of the present disclosure, the version information of at least one branch and at least one editor version corresponding to each branch is obtained from the editor version management information, and then the above-obtained information is displayed on the client interface. Among them, the version information of the editor version can include information such as the version number of the editor.
[0054] The editor version management information can be a file that records information such as branch versions, editor versions, and their related resources, dependencies, compatibility, etc. The editor version management information can include branch information, editor version information, etc. This editor version management information can be obtained from a version management system.
[0055] In an alternative implementation, to display the version information of at least one branch and at least one editor version corresponding to each branch, it is also necessary to obtain the editor commit log of the version management system, so as to be able to determine the branch and the editor version corresponding to the branch from the editor version list. Specifically, obtain the editor commit log of the version management system, use a parsing tool to parse the editor commit log, extract the corresponding relationship between the branch and the editor version, and construct an editor version list for the corresponding relationship between the two. For the specific method of obtaining the editor commit log of the version management system, the embodiments of the present disclosure do not make limitations.
[0056] Among them, the version management system is a software tool used to track and manage changes to project files. The version management system is specifically, for example, an SVN tool. The editor commit log can refer to the log information related to the editor version recorded in the version management system. Among them, the editor commit log can include the editor version number, the engine version number, the resource version number corresponding to the editor, and the resources corresponding to the editor can include resources such as special effects, audio, and planning configurations.
[0057] After obtaining the editor version list, determine at least one branch and at least one editor version corresponding to each branch from the editor version list. The at least one editor version can be some or all of the editor versions corresponding to the determined branch above. That is to say, one or more editor versions determined from the editor version list can be all or some of the editor versions corresponding to each branch determined from the editor version list.
[0058] In an alternative implementation, in editor version management, the version information is continuously updated over time and development progress. To facilitate users to understand the version information of the current latest branch and the latest editor version corresponding to the latest branch, the current latest branch and the latest editor version corresponding to each branch can be determined from the editor version list and displayed on the client interface.
[0059] In an alternative embodiment, based on the above embodiments, during the process of displaying the version information of at least one branch and at least one editor version corresponding to each branch, in order to facilitate real-time display of the latest branch and the version information of the editor version corresponding to the branch to the user, a timing refresh policy may also be set. Specifically, when displaying the version information of the branch and the editor version corresponding to the branch, start timing. When the timing reaches a preset first time, re-obtain the editor commit log of the version management system, parse the editor commit log to obtain a new list of editor versions, and re-determine the latest branch and the version information of the editor version corresponding to the branch from the list of editor versions. The preset first time is a period of time set in advance.
[0060] In practical applications, during the process of displaying the version information of at least one branch and at least one editor version corresponding to each branch, if it is detected that there is a local editor, the version information of the editor version of the local editor can also be displayed to facilitate the user to understand the version information of the currently used editor. The version information of the editor version of the local editor can be obtained from the editor management directory.
[0061] S102: After receiving a switching trigger operation for the target editor version corresponding to the target branch among the at least one branch, obtain the resources under the resource version corresponding to the target editor version.
[0062] Among them, the target branch is one of the at least one branch displayed, and one of the editor versions corresponding to the target branch is the target editor version. The switching trigger operation for the target editor version corresponding to the target branch may include a trigger operation for a switching control. The switching trigger operation can be used to indicate switching from the editor of the current editor version to the editor of the target editor version. Specifically, the switching trigger operation can switch from an editor of a lower version to an editor of a higher version, or can also be switching from an editor of a higher version to an editor of a lower version.
[0063] In the embodiments of the present disclosure, when receiving a switching trigger operation for the target editor version corresponding to the target branch, obtain the resources under the resource version corresponding to the target editor version. Among them, the resource version is a kind of mark or number for resources in different stages and different states, that is, resources will generate different versions due to operations such as modification and update. For example, in a game development project, the character model in the game will be continuously updated due to reasons such as design optimization and detail increase. Each updated character model can be regarded as a new version of the resource, and is distinguished by a specific version number or version identifier. The resources under the resource version can refer to assets such as images, audio, video, planning, and configuration files, and these resources affect the operation and loading of the editor.
[0064] In an alternative embodiment, after receiving a switching trigger operation for the target editor version corresponding to the target branch, obtaining the resources under the resource version corresponding to the target editor version may include: when receiving a switching trigger operation for the target editor version corresponding to the target branch, comparing and analyzing the target editor version with the local editor version to determine the resource difference between the local editor version and the target editor version, and then based on the resource difference, obtaining the resources under the resource version corresponding to the target editor version from the target resource server. The local editor version may refer to the version of the editor currently installed locally.
[0065] The resource difference may refer to the differences between the resources included in the local editor version and the resources corresponding to the target editor version. The resource difference may include resource differences in aspects such as addition, modification, and deletion. By comparing the resources between the local editor version and the target editor version, the different resources between the two can be determined, and these different resources can also be referred to as incremental resources. The target resource server may be a server storing resources related to the target editor version.
[0066] In practical applications, if the switching trigger operation for the target editor version corresponding to the target branch is a rollback operation, the present disclosure may further set a rollback mechanism for the external link resources included in the resource difference. Specifically, when triggering a rollback operation for the target editor version corresponding to the target branch, the external link resources in the resource difference are rolled back to the state in the target editor version. Among them, the target type of resource may be an external resource associated with the resources under the resource path of a certain resource, and the path of this external resource is different from the resource path of the certain resource. That is to say, the target type of resource is a resource referenced through an external link. For example, assume that there is a B folder under the A path, and audio resources are stored in the B folder. The actual storage path of the audio resources is in the D folder under the C path. Then, an external link can be referenced in the B file under the A path to associate with the D file. The audio resources in the D file under the C path are external resources for the B folder under the A path.
[0067] In the embodiment of the present disclosure, when triggering a rollback operation for the target editor version, setting a rollback mechanism for the target type of resource can reduce the probability of the rollback failure of the target type of resource caused by using the version management system.
[0068] In another alternative embodiment, since the resources under the resource version corresponding to the target editor version can include various types of resources, that is to say, the operation of the editor of the target editor version requires various types of resources, and different types of resources correspond to different resource versions. On the basis of the above embodiments, it is also possible to obtain the resources required for the operation of the editor of the target editor version based on multiple resource versions corresponding to the target editor version.
[0069] Specifically, after receiving a switching trigger operation for the target editor version corresponding to the target branch, determine the resource versions of various types of resources corresponding to the target editor version, and respectively obtain the resources required for the operation of the editor of the target editor version from each resource version based on the resource versions corresponding to various types of resources. The resources can include resources of types such as pictures, special effects, planning, and configuration files.
[0070] In yet another alternative embodiment, to save the switching time of the editor version and improve the efficiency of switching versions, it is also possible to complete the switching of the editor of the target editor version based on the target type of resources. Among them, the target type of resources can be the necessary part of the resources required for the operation of the editor of the target editor version, that is, a part of the resources essential for the normal operation of the editor of the target editor version. Without these resources, the editor will not be able to start or run normally. The target type of resources can be core code resources, core configuration file resources, etc. Specifically, after receiving a switching trigger operation for the target editor version corresponding to the target branch, obtain the target type of resources under the resource version corresponding to the target editor version.
[0071] S103: Load and run the editor of the target editor version based on the resources under the target branch.
[0072] After obtaining the resources under the resource version corresponding to the target editor version, load and run the editor of the target editor version based on these resources under the target branch, so as to be used for subsequent development and other work directly using this editor.
[0073] After loading and running the editor of the target editor version based on the resources under the resource version corresponding to the target editor version under the target branch, the current local editor is switched to the editor of the target editor version.
[0074] The editor version update method provided by the embodiments of the present disclosure. Specifically, first, at least one branch and the version information of at least one editor version corresponding to each branch are displayed, where the at least one editor version corresponding to each branch is determined based on the editor version management information. After receiving a switching trigger operation for the target editor version corresponding to the target branch among the at least one branch, the resources under the resource version corresponding to the target editor version are obtained. The editor of the target editor version is loaded and run based on the resources under the target branch.
[0075] The embodiments of the present disclosure support quick switching of any editor version corresponding to any branch, and at the same time automatically download the resources required for running the editor of this editor version, realizing the one-key intelligent editor version switching function. Compared with the method of realizing editor version switching by manually inputting paths and related operation instructions, the embodiments of the present disclosure provide an easy-to-operate method for editor version switching, improving the switching efficiency of editor versions.
[0076] In an optional implementation manner, in order to facilitate users to manage editor versions, an editor management directory can also be set. The editor management directory includes the version information of the currently existing local editors, and the editor management directory is a directory for managing editor versions. Specifically, when a trigger operation for local editor management is received, the local files are identified based on the editor feature information, and the local file that matches the editor feature information successfully is determined as the local editor, and the editor version to which the local editor belongs is added to the editor management directory.
[0077] Among them, the trigger operation for local editor management can be a trigger operation on the management control on the interface. The editor feature information can be preset information, which is used to distinguish different editors, and the editor feature information can include editor name, version number, specific file structure or code feature, etc.
[0078] In practical applications, when a trigger operation for local editor management is received, each local file is traversed and scanned using the editor feature information to determine whether there is a local file that matches the editor feature information. If the match is successful, the editor represented by the successfully matched local file is determined as the local editor, and then the editor version to which the local editor belongs is added to the editor management directory for subsequent effective search and other management operations on the local editor.
[0079] In practical applications, if the editor is not installed locally, to facilitate users to install and use the editor, the embodiments of the present disclosure also support the intelligent installation function of the editor. Specifically, during the process of displaying the version information of multiple branches and one or more editor versions corresponding to each branch, when a download trigger operation for the first editor version is received, relevant plugins are called to pull the resources corresponding to the first editor version from the corresponding server, and the relevant information of the first editor version is saved locally. Then, when a build operation is performed on the first editor version, the relevant resources are executed to start the editor.
[0080] In the embodiments of the present disclosure, by triggering the download and build operations for the editor, the installation of the editor can be completed in one key, simplifying the installation process and improving the installation efficiency.
[0081] To facilitate the understanding of the content of the above embodiments, the embodiments of the present disclosure also provide a flowchart of a method for updating the editor version in a specific application scenario. Refer to Figure 2 . Taking the SVN version management system as an example of the version management system, specifically:
[0082] First, obtain the editor commit log from the SVN version management system, parse the editor commit log to obtain the editor version list. Specifically, relevant parsing tools can be used to parse the editor commit log, and the corresponding relationship between branches and editor versions is recorded in the editor version list.
[0083] Then, based on the editor version list, determine and display at least one branch and at least one editor version corresponding to each branch in the at least one branch, and display the local editor version on the client.
[0084] In an optional implementation manner, the branches and at least one editor version corresponding to each branch can be determined from the editor version list based on a recommendation strategy.
[0085] When a selection operation for the target editor version corresponding to the target branch is received, compare and analyze the target editor version with the local editor version to determine the resource difference between the target editor version and the local editor version.
[0086] Furthermore, based on the resource difference, obtain the resources under the resource version corresponding to the target editor version from the resource server.
[0087] After obtaining the resources under the resource version corresponding to the target editor version, load and run the editor of the target editor version based on the resources, so as to facilitate the subsequent direct use of the editor.
[0088] To implement the above embodiments, the present disclosure also provides an editor version update device. Figure 3 As shown in the structural schematic diagram of an editor version update device provided by an embodiment of the present disclosure, the device can be implemented by software and / or hardware, and is generally integrated in an electronic device. As Figure 3 shown, the device includes:
[0089] A display module 301, configured to display at least one branch and version information of at least one editor version corresponding to each branch; wherein, the at least one editor version corresponding to each branch is determined based on editor version management information;
[0090] An acquisition module 302, configured to acquire resources under the resource version corresponding to the target editor version after receiving a switching trigger operation for the target editor version corresponding to the target branch among the at least one branch;
[0091] An operation module 303, configured to load and run an editor of the target editor version based on the resources under the target branch.
[0092] In an optional implementation manner, the device further includes:
[0093] A parsing module, configured to acquire an editor commit log of a version management system and parse the editor commit log to obtain an editor version list; wherein, the corresponding relationship between branches and editor versions is recorded in the editor version list;
[0094] A determination module, configured to determine at least one branch from the editor version list, and at least one editor version corresponding to each branch among the at least one branch; wherein, the at least one editor version belongs to a part or all of the editor versions of the corresponding branch.
[0095] In an optional implementation manner, the acquisition module is specifically configured to:
[0096] After receiving a switching trigger operation for the target editor version corresponding to the target branch among the at least one branch, acquire resources under the resource version corresponding to the target editor version from a target resource server based on the resource difference between the local editor version and the target editor version.
[0097] In an optional implementation manner, the resources under the resource version corresponding to the target editor version include various types of resources, and each of the various types of resources has a corresponding resource version. The acquisition module is specifically configured to:
[0098] After receiving a switching trigger operation for a target editor version corresponding to a target branch in the at least one branch, obtain the resources required for running the editor of the target editor version respectively based on the resource versions corresponding to the multiple types of resources.
[0099] In an optional implementation manner, the obtaining module is specifically configured to:
[0100] After receiving a switching trigger operation for a target editor version corresponding to a target branch in the at least one branch, obtain target type resources under the resource version corresponding to the target editor version; wherein, the target type resources are necessary partial resources required for running the editor of the target editor version.
[0101] In an optional implementation manner, the apparatus further includes:
[0102] An adding module, configured to, in response to a local editor management trigger operation, identify a local file through editor feature information, determine the local file that successfully matches the editor feature information as a local editor, and add the editor version to which the local editor belongs to an editor management directory; wherein, the editor management directory is used to manage editor versions.
[0103] In the editor version update apparatus provided in the embodiments of the present disclosure, specifically, first, display version information of at least one branch and at least one editor version corresponding to each branch, wherein the at least one editor version corresponding to each branch is determined based on editor version management information. After receiving a switching trigger operation for a target editor version corresponding to a target branch in the at least one branch, obtain the resources under the resource version corresponding to the target editor version. Load and run the editor of the target editor version based on the resources under the target branch.
[0104] The embodiments of the present disclosure support quick switching of any editor version corresponding to any branch, and at the same time automatically download the resources required for running the editor of this editor version, realizing a one-key intelligent editor version switching function. Compared with switching the editor version by manually inputting a path and related operation instructions, the embodiments of the present disclosure provide an easy-to-operate method for switching the editor version, improving the switching efficiency of the editor version.
[0105] The editor version update apparatus provided in the embodiments of the present disclosure can execute the editor version update method provided in any embodiment of the present disclosure, and has corresponding functional modules and beneficial effects for executing the method.
[0106] To implement the above embodiments, the present disclosure also provides a computer program product, including a computer program / instructions, which when executed by a processor, implement the editor version update method in the above embodiments.
[0107] In addition to the above methods and apparatuses, the embodiments of the present disclosure also provide a computer-readable storage medium, in which instructions are stored. When the instructions run on a terminal device, the terminal device implements the editor version update method described in the embodiments of the present disclosure.
[0108] In addition, the embodiments of the present disclosure also provide an editor version update device, as shown in Figure 4 which may include:
[0109] A processor 401, a memory 402, an input device 403, and an output device 404. The number of processors 401 in the editor version update device may be one or more. Figure 4 Taking one processor as an example. In some embodiments of the present disclosure, the processor 401, the memory 402, the input device 403, and the output device 404 may be connected through a bus or other means. Among them, Figure 4 taking the connection through a bus as an example.
[0110] The memory 402 can be used to store software programs and modules. The processor 401 runs the software programs and modules stored in the memory 402, thereby implementing various functional applications and data processing of the editor version update device. The memory 402 mainly includes a program storage area and a data storage area. Among them, the program storage area can store an operating system, application programs required for at least one function, etc. In addition, the memory 402 may include a high-speed random access memory, and may also include a non-volatile memory, such as at least one magnetic disk storage device, a flash memory device, or other volatile solid-state storage devices. The input device 403 can be used to receive input digital or character information, and generate signal inputs related to user settings and function controls of the editor version update device.
[0111] Specifically in this embodiment, the processor 401 will load the executable files corresponding to the processes of one or more application programs into the memory 402 according to the following instructions, and the processor 401 will run the application programs stored in the memory 402, thereby implementing various functions of the above editor version update device.
[0112] It should be noted that in this document, relational terms such as "first" and "second" are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any actual relationship or order between these entities or operations. Moreover, the term "comprising", "including" or any other variation thereof is intended to cover non-exclusive inclusion, so that a process, method, article or device comprising a series of elements not only includes those elements but also includes other elements not expressly listed, or elements inherent to such process, method, article or device. Without further limitation, an element defined by the statement "comprising an..." does not exclude the presence of additional identical elements in the process, method, article or device comprising said element.
[0113] The above are only specific embodiments of the present disclosure, enabling those skilled in the art to understand or implement the present disclosure. Various modifications to these embodiments will be obvious to those skilled in the art, and the general principles defined herein can be implemented in other embodiments without departing from the spirit or scope of the present disclosure. Therefore, the present disclosure will not be limited to these embodiments described herein, but rather to the broadest scope consistent with the principles and novel features disclosed herein.
Claims
1. A method for updating an editor version, characterized in that: include: Displaying version information of at least one branch and at least one editor version corresponding to each branch; wherein the at least one editor version corresponding to each branch is determined based on editor version management information; After receiving a switch trigger operation for a target editor version corresponding to a target branch in the at least one branch, obtaining resources under a resource version corresponding to the target editor version; An editor of the target editor version is loaded and run based on the resource under the target branch.
2. The method according to claim 1, characterized in that Before displaying the version information of at least one branch and at least one editor version corresponding to each branch, the method further includes: Obtaining an editor submission log of the version management system, and parsing the editor submission log to obtain an editor version list; wherein the editor version list records the correspondence between branches and editor versions; Determine at least one branch from the editor version list, and at least one editor version corresponding to each branch in the at least one branch; wherein the at least one editor version belongs to part or all of the editor versions of the corresponding branch.
3. The method according to claim 1, characterized in that After receiving a switch trigger operation for a target editor version corresponding to a target branch in the at least one branch, obtaining resources under a resource version corresponding to the target editor version includes: After receiving a switch trigger operation for a target editor version corresponding to a target branch in at least one of the branches, resources under a resource version corresponding to the target editor version are obtained from a target resource server based on resource differences between a local editor version and the target editor version.
4. The method according to claim 1, characterized in that: The resources under the resource version corresponding to the target editor version include multiple types of resources, each of which has a corresponding resource version. After receiving a switch trigger operation for the target editor version corresponding to the target branch in the at least one branch, obtaining the resources under the resource version corresponding to the target editor version includes: After receiving a switch trigger operation for a target editor version corresponding to a target branch in the at least one branch, resources required for running an editor of the target editor version are acquired based on resource versions corresponding to the multiple types of resources.
5. The method according to claim 1, characterized in that After receiving a switch trigger operation for a target editor version corresponding to a target branch in the at least one branch, obtaining resources under a resource version corresponding to the target editor version includes: After receiving a switch trigger operation for a target editor version corresponding to a target branch in at least one of the branches, a target type resource under a resource version corresponding to the target editor version is obtained; wherein the target type resource is a necessary part of the resources required for the editor of the target editor version to run.
6. The method according to claim 1, characterized in that The method further comprises: In response to a local editor management trigger operation, local files are identified through editor feature information, and local files that successfully match the editor feature information are determined as local editors, and the editor version to which the local editor belongs is added to an editor management directory; wherein the editor management directory is used to manage editor versions.
7. An editor version updating device, characterized in that: The device comprises: A display module, used to display at least one branch and version information of at least one editor version corresponding to each branch; wherein the at least one editor version corresponding to each branch is determined based on editor version management information; An acquisition module, configured to acquire resources under a resource version corresponding to a target editor version of a target branch in the at least one branch after receiving a switch trigger operation for the target editor version corresponding to the target branch in the at least one branch; A running module is used to load and run the editor of the target editor version based on the resource under the target branch.
8. An electronic device, characterized in that: The electronic device comprises: processor; a memory for storing instructions executable by the processor; The processor is used to read the executable instructions from the memory and execute the instructions to implement the editor version update method described in any one of claims 1-6 above.
9. A computer-readable storage medium, characterized in that: The storage medium stores a computer program, and the computer program is used to execute the editor version updating method described in any one of claims 1-6.
10. A computer program product, characterized in that The computer program product comprises a computer program / instruction, and when the computer program / instruction is executed by a processor, the method according to any one of claims 1 to 6 is implemented.