Information acquisition method and device, electronic equipment and computer readable storage medium

Abstract

Embodiments of the present application disclose an information acquisition method and device, electronic equipment and a computer readable storage medium. The method comprises: acquiring content information corresponding to a host application constructed based on a first integrated platform; generating a plug-in runtime environment according to the content information; and acquiring a target plug-in of the host application based on a second integrated platform according to the plug-in runtime environment. The integration processes of the first integrated platform and the second integrated platform are different. The difference between the integration processes of the first integrated platform and the second integrated platform enables the host application and the plug-in to be developed and constructed on different integrated platforms, i.e., reduces the requirement of the plug-in development on the platform environment, improves the development efficiency of the plug-in, facilitates the use of the plug-in to improve the functional diversity of the host application, and improves the efficiency of the development of the application functional diversity.

Description

Technical Field

[0001] This application relates to the field of computer technology, specifically to an information acquisition method, apparatus, electronic device, and computer-readable storage medium. Background Technology

[0002] With the rapid development of computer technology, the functions of applications are constantly increasing. In order to reduce the number of applications and the interaction costs between applications, the functions of multiple applications are usually integrated into a single application, so that a single application can complete the functions and roles of multiple applications. For example, plugins for a host application can extend the functions of the host application by integrating them into the host application.

[0003] However, currently, plugin development relies on the platform environment of the host application, which increases the difficulty and efficiency of plugin development and is not conducive to the development of diverse application functions. Summary of the Invention

[0004] This application provides an information acquisition method, apparatus, electronic device, and computer-readable storage medium, which can improve the efficiency of plug-in development.

[0005] In a first aspect, embodiments of this application provide an information acquisition method, including:

[0006] Obtain content information corresponding to the host application built based on the first integration platform;

[0007] Based on the aforementioned content information, a plugin runtime environment is generated;

[0008] Based on the plugin runtime environment, the target plugin corresponding to the host application is obtained using the second integration platform;

[0009] The integration processes of the first integration platform and the second integration platform are different.

[0010] Secondly, embodiments of this application also provide an information acquisition device, including:

[0011] The first acquisition module is used to acquire content information corresponding to the host application built based on the first integration platform.

[0012] The generation module is used to generate the plugin runtime environment based on the content information.

[0013] The second acquisition module is used to acquire the target plugin corresponding to the host application based on the second integration platform according to the plugin runtime environment; wherein the integration process of the first integration platform and the second integration platform is different.

[0014] In some embodiments of this application, the device further includes a plug-in application module, which includes:

[0015] An integration unit is used to integrate the target plugin into the host application;

[0016] A generation unit is used to generate a plugin icon for the target plugin in the host application;

[0017] An execution unit is used to execute the executable file corresponding to the target plugin in response to a touch operation by a target user on the plugin icon.

[0018] In some embodiments of this application, the generation module includes:

[0019] The extraction unit is used to extract the project source code and resource files corresponding to the host application from the content information;

[0020] The generation unit is used to generate a plugin runtime environment based on the project source code and the resource files through the first integration platform.

[0021] In some embodiments of this application, the integration unit includes:

[0022] The first determining subunit is used to determine the plugin executable file corresponding to the target plugin and the identification information corresponding to the plugin executable file;

[0023] An integration unit is used to establish a reference to the plugin executable file by the host application based on the identification information.

[0024] In some embodiments of this application, the second acquisition module includes:

[0025] The first acquisition unit is used to acquire the original plugin corresponding to the host application through the second integration platform, based on the plugin runtime environment.

[0026] The second acquisition unit is used to obtain the target plugin based on the plugin product requirement type and the original plugin.

[0027] In some embodiments of this application, the integration unit includes:

[0028] The second determining subunit is used to determine the plugin executable file corresponding to the target plugin and the identification information corresponding to the plugin executable file;

[0029] The third determining subunit is used to determine the target application product type based on the plugin product requirement type corresponding to the target plugin;

[0030] An integration subunit is used to establish a reference to the plugin executable file by the host application of the target application product type based on the identification information.

[0031] In some embodiments of this application, the determined subunit is specifically used for:

[0032] The plugin product cycle corresponding to the target plugin is determined based on the plugin product requirement type corresponding to the target plugin.

[0033] Based on the plugin product cycle, a target application product type is selected from several application product types corresponding to the host application, wherein the application product cycle corresponding to each application product type is different.

[0034] Thirdly, embodiments of this application also provide an electronic device, which includes a memory, a processor, and a computer program stored in the memory and executable on the processor. When the processor executes the computer program, it implements the steps in the information acquisition method described above.

[0035] Fourthly, embodiments of this application also provide a computer-readable storage medium storing a computer program, which, when executed by a processor, implements the steps in the information acquisition method described above.

[0036] In this embodiment, the content information of a host application built on a first integration platform is obtained. A plugin runtime environment is generated based on the host application's content information. A target plugin corresponding to the host application is obtained based on this plugin runtime environment and a second integration platform. Obtaining the target plugin based on the plugin runtime environment of the host application allows the obtained target plugin to be integrated and run on the host application. The different integration processes of the first and second integration platforms allow the host application and plugins to be developed and built separately on different integration platforms. This reduces the platform environment requirements for plugin development, improves plugin development efficiency, facilitates the use of plugins to enhance the functional diversity of the host application, and improves the efficiency of developing diverse application functionalities. Attached Figure Description

[0037] To more clearly illustrate the technical solutions in this application, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0038] Figure 1 This is a schematic diagram of a scenario illustrating the information acquisition method provided in an embodiment of this application;

[0039] Figure 2This is a flowchart illustrating the information acquisition method provided in an embodiment of this application;

[0040] Figure 3 This is a schematic diagram of the host application plug-in development process provided in the embodiments of this application;

[0041] Figure 4 This is a flowchart illustrating the method for obtaining meeting plugins based on office applications provided in an embodiment of this application;

[0042] Figure 5 This is a schematic diagram of the integration process of the SnapContinuous Integration Platform provided in this application embodiment;

[0043] Figure 6 This is a flowchart illustrating the process of developing plug-in applications for office applications provided in this embodiment.

[0044] Figure 7 This is a schematic diagram illustrating the process of integrating a meeting plugin into an office application, as provided in an embodiment of this application.

[0045] Figure 8 This is a schematic diagram of the process of integrating the meeting plugin into the Blue Whale Continuous Integration Platform provided in the embodiments of this application;

[0046] Figure 9 This is a flowchart illustrating the integration of office applications and meeting plugins provided in this application embodiment;

[0047] Figure 10 This is a schematic diagram of the execution flow of the Blue Whale Continuous Integration Platform during the development and testing of office applications provided in this application embodiment;

[0048] Figure 11 This is a schematic diagram of the structure of the information acquisition device provided in the embodiments of this application;

[0049] Figure 12 This is a schematic diagram of the result of the office application and meeting plugin integration device provided in the embodiments of this application;

[0050] Figure 13 This is a schematic diagram of the structure of the electronic device provided in the embodiments of this application. Detailed Implementation

[0051] The technical solutions of this application will now be clearly and completely described with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0052] This application provides an information acquisition method, apparatus, electronic device, and computer-readable storage medium. Specifically, this application provides an information acquisition apparatus suitable for electronic devices, wherein the electronic device includes devices such as terminals or servers. The terminal can be a computer, personal computer, or mobile phone, etc. The server can be an independent physical server, a server cluster or distributed system composed of multiple physical servers, or a cloud server that provides basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communication, middleware services, domain name services, security services, content delivery networks (CDNs), and big data and artificial intelligence platforms. The server can be directly or indirectly connected via wired or wireless communication.

[0053] The embodiments of this application can be executed by a terminal device alone, or by a server alone, or by both the terminal and the server jointly. Please refer to [link to relevant documentation]. Figure 1 Taking the joint execution of an information acquisition method by a terminal device and a server as an example, the specific execution process of the information acquisition method is as follows:

[0054] Terminal device 10 obtains the host application built based on the first integration platform and the corresponding content information of the host application. It then generates a plugin runtime environment based on the content information of the host application and sends the plugin runtime environment to terminal device 11. Terminal device 11 then obtains the target plugin corresponding to the host application through the second integration platform and based on the plugin runtime environment. The integration processes of the first and second integration platforms are different.

[0055] In this embodiment, the plugin runtime environment can be deployed on server 12. Then, the terminal device 11 obtains the target plugin corresponding to the host application through the second integration platform based on the plugin runtime environment deployed on server 12.

[0056] In this embodiment, the host application includes an online office application, and the plugin includes an online meeting application. By using the online meeting application as a plugin for the online office application, the functionality of the online office application is enriched.

[0057] In this embodiment, content information of a host application built on a first integration platform is obtained. A plugin runtime environment is generated based on the host application's content information. A target plugin corresponding to the host application is obtained based on this plugin runtime environment and a second integration platform. Obtaining the target plugin based on the plugin runtime environment of the host application allows the obtained target plugin to be integrated and run on the host application. The different integration processes of the first and second integration platforms allow the host application and plugins to be developed and built separately on different integration platforms. This reduces the platform environment requirements for plugin development, improves plugin development efficiency, facilitates the use of plugins to enhance the functional diversity of the host application, and improves the efficiency of application functional diversity development.

[0058] The following sections provide detailed descriptions of each example. It should be noted that the order in which the embodiments are described is not intended to limit the priority of the embodiments.

[0059] Please see Figure 2 , Figure 2 This is a flowchart illustrating the information acquisition method provided in an embodiment of this application. The specific flow of this information acquisition method can be as follows:

[0060] 101. Obtain the content information corresponding to the host application built based on the first integration platform.

[0061] In this embodiment of the application, the host application includes an online office application, and the content information corresponding to the host application includes the project source code, resource files, etc. of the host application.

[0062] In this embodiment, the development of the host application relies on the collaboration of multiple development members. The development of the host application is achieved through the integration of the work results of these members. This integration approach allows the application project to be distributed among multiple independent members for development, enabling rapid application development and improving efficiency by integrating the work results.

[0063] In this embodiment of the application, the work results of multiple development members can be integrated through an integration platform. By integrating the work results, problems in the application development process can be discovered as early as possible, so that the problems can be fixed in a timely manner.

[0064] In this embodiment of the application, the integration platform is an integration tool that continuously integrates the work results of each member in the application. Continuous integration is a software development practice that uses integration tools to automatically integrate the development results of multiple members and build the host application.

[0065] In this embodiment, the integration platform may include the Blue Whale Continuous Integration Platform or the QQ Continuous Integration Platform. The Blue Whale Continuous Integration Platform (codenamed Blue Shield) is an open-source continuous integration and continuous delivery system. It is also the only platform in the industry to date to achieve Level 4 certification in DevOps and is part of the Blue Whale Smart Cloud ecosystem. Blue Shield eliminates tedious steps in the development process, allowing you to focus on coding. Blue Shield is typically used for: project compilation, static code analysis, running test cases, timely defect (bug) detection, and deployment and release. Blue Shield provides five core services: pipeline, code repository, credential management, environment management, and development store. These services offer multiple combinations to meet the needs of different enterprise scenarios. The pipeline visually presents the team's existing development processes, with compilation, testing, and deployment all completed in a single pipeline. Coding Continuous Integration Platform is a collaborative management platform for software development teams. It provides a series of tools and products, including cloud-native development environment, online coding, code hosting, project management, test management, continuous integration, artifact repository, continuous deployment, and team knowledge base, to help development teams practice agile development and operations (DevOps).

[0066] In this embodiment of the application, based on the product development requirements of the host application, one of the multiple integration platforms is selected to integrate and build the host application, thereby enabling the acquisition of the host application through the integration platform.

[0067] 102. Generate the plugin runtime environment based on the aforementioned content information.

[0068] In this embodiment of the application, the plugin runtime environment refers to the environment in which the plugin runs on the host application. It is a comprehensive representation of the content information corresponding to the host application and can be understood as the program basis for the plugin to run. For example, the plugin runtime environment corresponding to the host application can be obtained by summarizing multiple source code files corresponding to the host application.

[0069] The generation of the plugin runtime environment facilitates the development of the target plugin based on this runtime environment. In other words, the plugin runtime environment is generated based on the content information corresponding to the host application, so that the plugin built based on the plugin runtime environment can run on the host application.

[0070] Since the plugin runtime environment is the environment provided by the plugin to run on the host application, the plugin runtime environment that the plugin runs on the host application can be constructed based on the content information of the host application.

[0071] In this embodiment of the application, the content information of the host application includes the project source code and resource files of the host application. Therefore, a plugin runtime environment can be generated based on the project source code and resource files of the host application. That is, optionally, in some embodiments of this application, the step "generating a plugin runtime environment based on the content information" includes:

[0072] Extract the project source code and resource files corresponding to the host application from the content information;

[0073] The plugin runtime environment is generated using the first integration platform based on the project source code and the resource files.

[0074] In this embodiment of the application, the project source code includes the source code corresponding to the host application, and the resource files include the configuration files corresponding to the code of each module in the host application, as well as the images, icons, audio, video, text resources, etc. in the application.

[0075] The construction of the plugin runtime environment through the host application's project source code and resource files facilitates the development of corresponding plugins based on that runtime environment.

[0076] 103. Based on the plugin runtime environment, obtain the target plugin corresponding to the host application using the second integration platform; wherein the integration processes of the first integration platform and the second integration platform are different.

[0077] Specifically, the target plugin corresponding to the host application is obtained based on the plugin runtime environment, enabling the target plugin to run on the host application. The different integration processes of the first and second integration platforms allow the host application and plugins to be built through different integration platforms. That is, plugin development can be carried out through other integration platforms that are different from the host application's integration platform, reducing the difficulty of plugin development and solving the problem of traditionally requiring the use of the same integration platform for plugin construction.

[0078] For example, traditionally, a host application is built through a first integration platform. New plugins for the host application need to be developed and integrated on the first integration platform to build an application containing the plugin. However, if the plugin project is large, it will increase the difficulty of building the integration platform. Therefore, plugins can be built through other integration platforms, and new plugins can be developed through the plugin runtime environment corresponding to the host application. This allows the resulting plugins to run on the host application and have the ability to be developed by a second integration platform, reducing the difficulty of plugin development and facilitating the improvement of the efficiency of application diversity development.

[0079] In this embodiment, the target plugin may include at least one of an online meeting plugin, an online email plugin, an online live streaming plugin, or an online video plugin. To meet the needs of different types of plugin products, corresponding plugin products can be obtained through different integration platforms based on the plugin runtime environment corresponding to the host application, enabling the development of multiple types of plugin products suitable for the host application. When a plugin product is integrated into the host application, the corresponding functionality is integrated into the application.

[0080] In this embodiment, the integration platform includes integration tools. It should be understood that different integration processes refer to two different integration tools. That is, in this embodiment, the difference between the first and second integration platforms is not limited to the integration process itself; rather, it emphasizes that the first and second integration platforms correspond to different integration development tools. This difference in integration tools eliminates the need for development team members to become familiar with and adapt to other integration platforms, thus improving plugin development efficiency.

[0081] In this embodiment of the application, after obtaining the plugin built by the second integration platform, the plugin can be integrated into the host application, making it convenient to operate the corresponding functions of the plugin through the host application. That is, optionally, in some embodiments of this application, after the step "obtaining the target plugin corresponding to the host application based on the second integration platform according to the plugin runtime environment", the method further includes:

[0082] Integrate the target plugin into the host application;

[0083] The host application generates a plugin icon for the target plugin;

[0084] In response to a target user's touch operation on the plugin icon, the executable file corresponding to the target plugin is executed.

[0085] The plugin icon includes the graphic identifier corresponding to the plugin. The plugin icon can be drawn according to the product type of the plugin. In order to distinguish plugins of different product types, the plugin icon corresponding to plugins of different product types can be set to different.

[0086] In this embodiment of the application, the plugin icon can be set in the main function menu or the secondary menu of the application. In this embodiment of the application, the position of the plugin icon in the application interface can be adjusted according to the priority, importance or functional scope of the plugin.

[0087] This involves integrating the plugin into the host application and generating a corresponding plugin icon within the host application. When a user touches the plugin icon, the executable file corresponding to the plugin is launched, thus activating the plugin's functionality and allowing the user to easily use the plugin's features through the application interface.

[0088] In this embodiment of the application, the touch operation includes the user touching the plugin icon in the host application. For example, the user clicks or slides the plugin icon in the host application interface with their finger, thereby triggering the executable file of the plugin corresponding to the plugin icon and realizing the execution of the plugin function.

[0089] For example, please see Figure 3 , Figure 3 This is a schematic diagram of the host application plug-in development process provided in an embodiment of this application, wherein the host application plug-in development process includes:

[0090] 111. Export the source code and resource files of the host application from the host project corresponding to the host application;

[0091] 112. Generate the runtime environment for the plugins corresponding to the host application based on the project source code and resource files;

[0092] 113. Import the plugin runtime environment into the plugin development project;

[0093] 114. The plugin development project generates plugins (including plugin source code and plugins integrated through the second integration platform) based on the plugin runtime environment.

[0094] 115. Integrate the generated plugin into the host project to achieve the integration of the plugin into the host application.

[0095] This involves generating a plugin runtime environment, acquiring plugins based on that environment, and integrating those plugins into the host application to extend the functionality of the host application.

[0096] In this embodiment of the application, a reference to the plugin in the host application can be established based on the plugin's identification information, thereby integrating the plugin into the host application. Optionally, in some embodiments of this application, the step "integrating the target plugin into the host application" includes:

[0097] Determine the executable file corresponding to the target plugin and the identification information corresponding to the executable file;

[0098] Based on the identification information, a reference is established between the host application and the plugin executable file.

[0099] In this embodiment of the application, the plugin executable file refers to the program file corresponding to the plugin, including the plugin source code file, configuration file, etc.

[0100] In this embodiment, the plugin is integrated into the host application by establishing a reference to the plugin executable file. Specifically, the identification information of the plugin executable file can be added to the configuration file of the host application to achieve the reference to the plugin executable file.

[0101] In this embodiment, the plugin is a program product. The product has different product forms at different stages. For example, for the development version of the plugin product, the code corresponding to the plugin contains debugging switches and functions to facilitate joint debugging during development and to discover and locate problems; for the test version of the plugin product, the code corresponding to the plugin contains coverage instrumentation and other related logic; for the product experience version of the plugin product, the code corresponding to the plugin does not contain any debugging information and is consistent with the code information of the final release.

[0102] Therefore, in this embodiment of the application, the corresponding target plugin can also be obtained according to the product requirements of the plugin. That is, optionally, in some embodiments of this application, the step "obtaining the target plugin corresponding to the host application based on the second integration platform according to the plugin runtime environment" includes:

[0103] The original plugin corresponding to the host application is obtained through the second integration platform based on the plugin runtime environment.

[0104] The target plugin is obtained based on the plugin product requirement type and the original plugin.

[0105] The term "original plugin" refers to a plugin containing only the basic functional code, excluding instrumentation or event tracking code unrelated to the plugin's functionality. For example, for a meeting plugin, the original plugin only includes the meeting functionality. The term "target plugin" refers to a plugin deployed by adding instrumentation and event tracking to the original plugin based on the product's requirements. For instance, for a development version of a meeting plugin, event tracking and debug switches are added to the original plugin to create a target plugin for the development version. For a test version of a meeting plugin, test-related code such as instrumentation and event tracking is added to the integration of the original version to create a target plugin for the test version. For a product experience version, the original meeting plugin can be directly used as the target plugin. The appropriate plugin product is obtained based on different product requirements. Specifically, the development version corresponds to the application or plugin in the development phase, the test version corresponds to the application or plugin in the testing phase, and the product experience version corresponds to the application or plugin in the product experience phase.

[0106] In this application embodiment, for different plugin products, the plugin product can be integrated into the corresponding different versions of the host application to obtain the host application artifacts. That is, optionally, in some embodiments of this application, the step "integrating the target plugin into the host application" includes:

[0107] Determine the executable file corresponding to the target plugin and the identification information corresponding to the executable file;

[0108] The target application product type is determined based on the plugin product requirement type corresponding to the target plugin.

[0109] Based on the identification information, a host application for the target application product type is established to reference the plugin executable file.

[0110] Specifically, by referencing plugins of the corresponding product requirement type in the host application of the corresponding product type, the plugins are integrated into the host application of the corresponding product type. By integrating the plugins into the host application of the corresponding product type, the product type of the plugins is kept consistent with the product type of the host application, making it easier to obtain the corresponding integrated output.

[0111] For example, for a development version of a plugin product, the plugin can be integrated into the development version of the host application; for a test version of a plugin product, the plugin can be integrated into the test version of the host application; for a product trial version of a plugin product, the plugin can be integrated into the product trial version of the host application.

[0112] In this process, the corresponding host application product is obtained by integrating the corresponding version products. For example, after integrating the development version plugin product into the development version host application, the host application product of the development version is obtained; after integrating the test version plugin product into the test version host application, the host application product of the test version is obtained; and after integrating the product experience version plugin product into the product experience version host application, the host application product of the product experience version is obtained.

[0113] In this embodiment, product types can be categorized based on product lifecycles. Therefore, the application product type of the host application can be determined based on the product lifecycle. Optionally, in some embodiments of this application, the step "determine the target application product type based on the plugin product requirement type corresponding to the target plugin" includes:

[0114] The plugin product cycle corresponding to the target plugin is determined based on the plugin product requirement type corresponding to the target plugin.

[0115] Based on the plugin product cycle, a target application product type is selected from several application product types corresponding to the host application, wherein the application product cycle corresponding to each application product type is different.

[0116] The product cycle refers to the production stage of a product. In this embodiment, the product cycle includes development, testing, and application (product experience) cycles. The development cycle corresponds to the development version of the product, the testing stage corresponds to the test version of the product, and the application cycle corresponds to the product experience version of the product. The product experience version of the product is consistent with the content of the product tested by the user.

[0117] By identifying a host application that is in the same product lifecycle as the plugin, the plugin can be integrated into that host application, thus achieving integration of the plugin into a host application within the same product lifecycle.

[0118] In this embodiment, the content information of a host application built on a first integration platform is obtained. A plugin runtime environment is generated based on the host application's content information. A target plugin corresponding to the host application is obtained based on this plugin runtime environment and a second integration platform. Obtaining the target plugin based on the plugin runtime environment of the host application allows the obtained target plugin to be integrated and run on the host application. The different integration processes of the first and second integration platforms allow the host application and plugins to be developed and built separately on different integration platforms. This reduces the platform environment requirements for plugin development, improves plugin development efficiency, facilitates the use of plugins to enhance the functional diversity of the host application, and improves the efficiency of developing diverse application functionalities.

[0119] Based on the above description, the following will describe the method for obtaining the meeting plugin based on office applications in the embodiments of this application. Please refer to [link / reference]. Figure 4 , Figure 4 This is a flowchart illustrating the method for obtaining meeting plugins based on office applications provided in this application embodiment, including:

[0120] 201. Obtain the content information corresponding to the office applications built based on the Blue Whale Continuous Integration Platform.

[0121] In this embodiment, the development of the office application relies on the collaboration of multiple development members. The application is developed by integrating the work of these members. This integration approach allows the development of the office application to be distributed among multiple independent members, enabling rapid development and improving application development efficiency through the integration of their work.

[0122] In this embodiment of the application, the work results of multiple development members can be integrated through an integration platform. By integrating the work results, problems in the development process of office applications can be discovered as early as possible, so that the problems can be fixed in a timely manner.

[0123] In this embodiment of the application, the office application is the content file of the office application, and the content information corresponding to the office application includes the project source code, resource files, etc. of the office application.

[0124] Among them, the Blue Whale Continuous Integration Platform (codenamed Blue Shield) is an open-source continuous integration and continuous delivery system. It is the only platform in the industry to date to achieve Level 4 certification in DevOps, and is part of the Blue Whale Smart Cloud ecosystem. Blue Shield eliminates tedious steps in the development process, allowing you to focus on coding. Blue Shield is typically used for: project compilation, static code analysis, running test cases, timely defect (bug) detection, and deployment and release. Blue Shield provides five core services: pipelines, code repositories, credential management, environment management, and a development store. These services offer multiple combinations to meet the needs of different enterprise scenarios. The pipeline visually presents the team's existing development processes, handling compilation, testing, and deployment all in one pipeline.

[0125] 202. Generate the plugin runtime environment based on the content information.

[0126] In this embodiment of the application, the plugin runtime environment refers to the environment in which the plugin runs on the office application. It is a comprehensive representation of the content information corresponding to the office application and can be understood as the program basis for the plugin to run. For example, the plugin runtime environment corresponding to the office application can be obtained by summarizing multiple source code files corresponding to the office application.

[0127] The generation of the plugin runtime environment facilitates the development of meeting plugins based on this runtime environment. In other words, the plugin runtime environment is generated based on the content information corresponding to the office application, so that the meeting plugin built based on the plugin runtime environment can run on the office application.

[0128] In this embodiment of the application, the content information of the office application includes the project source code and resource files of the office application. Therefore, a plugin runtime environment can be generated based on the project source code and resource files of the office application. That is, optionally, in some embodiments of this application, the step "generating a plugin runtime environment based on the content information" includes:

[0129] Extract the project source code and resource files corresponding to the office application from the content information;

[0130] The Blue Whale Continuous Integration Platform generates a plugin runtime environment based on the project source code and resource files.

[0131] In this embodiment of the application, the project source code includes the source code corresponding to the office application, and the resource files include the configuration files corresponding to the code of each module in the office application, as well as the images, icons, audio, video, text resources, etc. in the application.

[0132] The construction of the plugin runtime environment using the project source code and resource files of the office application facilitates the development of corresponding plugins based on this runtime environment. In this embodiment, to meet the requirements for generating the plugin runtime environment, a corresponding header file can also be set, and the plugin runtime environment for the office application can be generated based on the header file, the project source code, and resource files.

[0133] 203. Based on the plugin runtime environment, obtain the target meeting plugin corresponding to the office application using the QQ Continuous Integration Platform.

[0134] Specifically, the meeting plugin for the office application is obtained based on the plugin's runtime environment, enabling the meeting plugin to run on the office application. The meeting plugin is built and obtained through the QQ Continuous Integration Platform, while the office application is built and obtained through the Blue Whale Continuous Integration Platform. By selecting different integration platforms to obtain the office application and meeting plugin separately, the office application and meeting plugin can be built through different integration platforms. That is, the meeting plugin can be developed through an integration platform different from the office application's integration platform, reducing the development difficulty of the meeting plugin, reducing the dependence of the meeting plugin development on the office application development platform, and solving the problem of traditionally requiring the use of a single integration platform for plugin building and integration.

[0135] For example, traditionally, a host application is built using the Blue Whale Continuous Integration Platform. Adding new plugins to this host application requires development and integration within the same platform to build the application containing the plugin. However, if the plugin project is large, this increases the complexity of building with the Blue Whale platform and requires developers to adapt to its development process. Therefore, plugins can be built using other integration platforms, and new plugins can be developed using the host application's corresponding plugin runtime environment. This allows the resulting plugins to run on the host application and be developed using other integration platforms, reducing plugin development difficulty and improving the efficiency of application diversity development.

[0136] For example, please see Figure 5 , Figure 5 This is a schematic diagram of the integration process of the QQ Continuous Integration Platform provided in this application embodiment, wherein the integration process of the QQ Continuous Integration Platform includes:

[0137] 211. Begin;

[0138] 212. Clean up and update code, install related components and branch use the trunk translation machine, etc. Among them, related components include Develop certificate, Ad Hoc certificate, App Store certificate, overseas App Store certificate, and private App Store certificate;

[0139] 213. Compilation;

[0140] 214. Generate and upload data packages and related artifacts, and activate the corresponding pipeline (Blue Shield pipeline) of the Blue Whale Continuous Integration Platform, including generating build package links, generating experience package links, generating App Store packages, uploading build artifacts, simulator artifacts, and backing up symbol tables.

[0141] Specifically, by starting the pipeline corresponding to the QQ Continuous Integration Platform, the plugin is integrated through the updating of relevant code, installation, compilation, generation and uploading of data packages, and the integration of the plugin into the office application is achieved by waking up the pipeline corresponding to the Blue Whale Continuous Integration Platform.

[0142] In this embodiment, after obtaining the meeting plugin built based on the plugin runtime environment of the office application, the plugin can be integrated into the office application to facilitate the use of the plugin's corresponding functions within the office application. Please refer to [link to relevant documentation]. Figure 6 , Figure 6 This is a schematic diagram of the process for developing plug-in applications for office applications, provided in an embodiment of this application. The process for developing plug-in applications for office applications includes:

[0143] 221. Obtain the office applications built based on the Blue Whale Continuous Integration Platform;

[0144] 222. Using the Blue Whale Continuous Integration Platform, generate the corresponding plugin runtime environment for the office application based on the project source code and resource files in the office application;

[0145] 223. Based on the plugin's runtime environment, obtain the corresponding meeting plugin for office applications through the QQ Continuous Integration Platform;

[0146] 224. Integrate the meeting plugin into office applications.

[0147] By integrating the meeting plugin into office applications, the functionality of office applications is enriched, the diversity of application functions is enhanced, and users can experience the product functions corresponding to the plugin through the interface of the office application.

[0148] In this embodiment of the application, after integrating the meeting plugin into the office application, the process of plugin-based development of the office application may further include:

[0149] Generate a plugin icon for the target meeting plugin in the office application;

[0150] In response to a target user's touch operation on the plugin icon, the executable file corresponding to the target meeting plugin is executed.

[0151] The plugin icon includes the graphic identifier corresponding to the plugin. The plugin icon can be drawn according to the product type of the plugin. In order to distinguish plugins of different product types, the plugin icon corresponding to plugins of different product types can be set to different.

[0152] This involves integrating the meeting plugin into office applications and generating a corresponding plugin icon within those applications. When a user taps the icon, the executable file corresponding to the meeting plugin is launched, activating the plugin's functionality and allowing users to easily access its features through the application interface.

[0153] In this embodiment of the application, the plugin icon can be set in the main function menu or the secondary menu of the office application. In this embodiment of the application, the position of the plugin icon in the office application interface can be adjusted according to the priority, importance or functional scope of the meeting plugin.

[0154] In this embodiment of the application, the touch operation includes the user touching the plugin icon in the office application. For example, the user clicks or swipes the plugin icon in the office application interface with their finger, thereby triggering the executable file of the plugin corresponding to the plugin icon and realizing the execution of the plugin function.

[0155] In this embodiment of the application, a reference to the meeting plugin in the office application can be established based on the plugin's identification information, thereby integrating the meeting plugin into the office application. Optionally, in some embodiments of this application, the step "integrating the target meeting plugin into the office application" includes:

[0156] Determine the executable file corresponding to the target conference plugin and the identification information corresponding to the executable file;

[0157] Based on the identification information, the office application establishes a reference to the plugin executable file.

[0158] In this embodiment of the application, the plugin executable file refers to the program file corresponding to the plugin, including the plugin source code file, configuration file, etc.

[0159] In this embodiment, the meeting plugin is integrated into the office application by establishing a reference to the plugin executable file. Specifically, the identification information of the plugin executable file can be added to the configuration file of the office application to achieve the reference to the plugin executable file.

[0160] In this embodiment, the plugin is a program product, and the product has different product forms at different stages. For example, for the development version of the plugin product, the code corresponding to the meeting plugin contains debugging switches and functions to facilitate joint debugging during development and to discover and locate problems; for the test version of the plugin product, the code corresponding to the meeting plugin contains coverage instrumentation and other related logic; for the product experience version of the plugin product, the code corresponding to the meeting plugin does not contain any debugging information and is consistent with the code information of the final release.

[0161] In some embodiments of this application, the corresponding meeting plugin can also be obtained according to the product requirements of the plugin. That is, optionally, in some embodiments of this application, the step "obtaining the target meeting plugin corresponding to the office application based on the second integration platform according to the plugin runtime environment" includes:

[0162] The original plugin corresponding to the office application is obtained through the second integration platform based on the plugin runtime environment.

[0163] The target meeting plugin is obtained based on the plugin product requirement type and the original plugin.

[0164] The original plugin refers to the plugin containing the basic functional code of the conference plugin, that is, it does not contain instrumentation or event tracking code unrelated to the plugin's functionality. The target conference plugin refers to the plugin after instrumentation and event tracking have been deployed on the basis of the original plugin according to the product's requirements. Different plugin products are obtained according to different product requirements. Plugin products with different product requirements can be identified by different version numbers to distinguish between different versions of the plugin product.

[0165] In this embodiment of the application, for different plug-in products, the plug-in product can be integrated into the corresponding version of the office application. That is, optionally, in some embodiments of this application, the step "integrating the target meeting plug-in into the office application" includes:

[0166] Determine the executable file corresponding to the target conference plugin and the identification information corresponding to the executable file;

[0167] The target application product type is determined based on the plugin product requirement type corresponding to the target meeting plugin.

[0168] Based on the identification information, a reference is established between the office application of the target application product type and the plugin executable file.

[0169] This involves integrating meeting plugins into office applications of corresponding product types by referencing those plugins with specific product requirements. This integration ensures consistency between the product type of the meeting plugin and the office application, facilitating the acquisition of the corresponding integrated deliverables. For example, a development version of a meeting plugin can be integrated into a development version of an office application; a test version can be integrated into a test version; and a product trial version can be integrated into a product trial version, thus obtaining the corresponding office application deliverables.

[0170] In this embodiment of the application, product types can be categorized based on product lifecycles. Therefore, the application product type for office applications can be determined based on the product lifecycle. Optionally, in some embodiments of this application, the step "determine the target application product type based on the plugin product requirement type corresponding to the target meeting plugin" includes:

[0171] The plugin product cycle corresponding to the target meeting plugin is determined based on the plugin product requirement type corresponding to the target meeting plugin.

[0172] Based on the plug-in product cycle, a target application product type is selected from several application product types corresponding to the office application, wherein the application product cycle corresponding to each application product type is different.

[0173] The product lifecycle includes development, testing, and application phases. The development phase corresponds to the development version of the product, the testing phase corresponds to the test version of the product, and the application phase corresponds to the product experience version.

[0174] In this way, by identifying an office application that is in the same product lifecycle as the meeting plugin, the meeting plugin can be integrated into that office application, thus achieving the integration of the meeting plugin into office applications in the same product lifecycle.

[0175] In this embodiment, the content information of an office application built on a first integration platform is obtained. A plugin runtime environment is generated based on this content information. A target meeting plugin corresponding to the office application is then obtained based on this runtime environment and a second integration platform. Obtaining the target meeting plugin based on the plugin runtime environment allows it to be integrated and run on the office application. The different integration processes of the first and second integration platforms allow the office application and meeting plugin to be developed and built separately on different integration platforms. This reduces the platform environment requirements for plugin development, improves the development efficiency of meeting plugins, and facilitates the use of meeting plugins to enhance the functional diversity of office applications, thereby increasing the efficiency of developing diverse application functionalities.

[0176] For example, please see Figure 7 , Figure 7 This is a schematic diagram illustrating the process of integrating a meeting plugin into an office application, as provided in an embodiment of this application. The process of integrating the meeting plugin into the office application includes:

[0177] 231. Based on the plugin runtime environment, obtain the target meeting plugin corresponding to the office application using the second integration platform;

[0178] 232. Upload the target meeting plugin to the cache;

[0179] 233. Wake up or remotely call the Blue Whale Continuous Integration Platform. The Blue Whale Continuous Integration Platform determines the target application product type based on the plugin product requirement type of the target meeting plugin.

[0180] 234. Integrate the target meeting plugin into the office application of the target application product type to obtain the office application product after integrating the meeting plugin.

[0181] Please refer to Figure 7 In this application embodiment, "integrating the target meeting plugin into an office application of the target application product type to obtain an office application product after integrating the meeting plugin" specifically includes;

[0182] When the meeting plugin is in development mode, the update pipeline corresponding to the development version of the office application in the Blue Whale Continuous Integration Platform is executed, updating the development version of the office application based on the meeting plugin. When the meeting plugin is in test mode, the update pipeline corresponding to the test version of the office application in the Blue Whale Continuous Integration Platform is executed, updating the test version of the office application based on the meeting plugin. When the meeting plugin is in product trial mode, the update pipeline corresponding to the product trial office application in the Blue Whale Continuous Integration Platform is executed, updating the product trial office application based on the meeting plugin.

[0183] Specifically, the integration and update of the corresponding version of the office application is performed based on the version of the generated meeting plugin, thereby enabling the acquisition of the corresponding integration artifacts of the office application.

[0184] Specifically, by storing the meeting plugin artifacts in the cache, the strong association between the Blue Whale Continuous Integration Platform and the QQ Continuous Integration Platform is reduced, and the dependency between the Blue Whale Continuous Integration Platform pipeline and the QQ Continuous Integration Platform pipeline is decoupled.

[0185] Please refer to Figure 8 , Figure 8 This is a flowchart illustrating the process of integrating a meeting plugin into the Blue Whale Continuous Integration Platform, as provided in this embodiment of the application. The process of integrating the meeting plugin into the Blue Whale Continuous Integration Platform includes:

[0186] 235. Triggering wake-up or remote invocation of the Blue Whale Continuous Integration Platform, wherein the triggering includes build triggering, manual triggering, timed triggering or remote triggering, etc., wherein, in the embodiments of this application, build triggering includes automatically triggering wake-up of the Blue Whale Continuous Integration Platform after the plugin integration build is completed;

[0187] 236. Application building and signing, checking for task cancellation, cleaning the workspace, cleaning up integrated (git) data, pulling integrated (git) data, compiling and archiving artifacts, etc.

[0188] Based on the above introduction, the method for integrating office applications and meeting plugins in the embodiments of this application will be described below. Please refer to [link / reference]. Figure 9 , Figure 9 This is a flowchart illustrating the integration of office applications and meeting plugins provided in an embodiment of this application, including:

[0189] 241. Obtain office applications built on the Blue Whale Continuous Integration Platform from the office application development project;

[0190] 242. Submit the office applications to the Blue Whale Continuous Integration Platform;

[0191] 243. Based on the office applications, generate the corresponding plugin runtime environment through the Blue Whale Continuous Integration Platform;

[0192] 244. Storage plugin runtime environment;

[0193] 245. The plugin development project obtains the plugin project source code corresponding to the plugin and submits the plugin project source code and plugin runtime environment to the QQ Continuous Integration Platform.

[0194] 246. The QQ Continuous Integration Platform generates corresponding plugin artifacts (including development versions, test versions, or product experience versions) based on the plugin product requirements.

[0195] 247. The QQ Continuous Integration Platform remotely calls the Blue Whale Continuous Integration Platform; the Blue Whale Continuous Integration Platform identifies the product type of the plug-in product, updates the plug-in product to the corresponding office application, and generates the meeting plug-in data package (SDK) in the corresponding office application.

[0196] In this embodiment of the application, the integration of office applications, the generation of plugin runtime environments, and the integration of meeting plugins use different integration command libraries (repo libraries).

[0197] The QQ Continuous Integration Platform uses a single pipeline to build different versions of artifacts. After each successful build, the platform uploads the artifact and adds a version number. By using intermediate storage for the plugin runtime environment, the strong dependency between the QQ Continuous Integration Platform and the Blue Whale Continuous Integration Platform is reduced, decoupling the dependencies between their pipelines.

[0198] In this embodiment of the application, the product lifecycle of the office application includes development, testing, and final product. Please refer to the relevant documentation for details. Figure 10 , Figure 10 This is a schematic diagram of the execution flow of the Blue Whale Continuous Integration Platform during the office application development and testing process provided in this application embodiment. The execution process of the Blue Whale Continuous Integration Platform during the office application development and testing process includes:

[0199] 251. Trigger or wake up the corresponding pipeline of the Blue Whale Continuous Integration Platform. Triggering includes build triggering, manual triggering, scheduled triggering and remote triggering.

[0200] 252. Clean up the workspace, clean up the integration environment, pull integration content, pull email plugin code, pull meeting data packets, compile, archive components, resign enterprise certificate (iOS enterprise certificate), publish the pulled email plugin, publish the pulled integration commands, etc.

[0201] 253. Reverse unpacking of pull-based constructs, command processor (Bash), pull-based component pipeline repository, unpacking scripts, symbol table processing, job platform-component distribution, job platform-script execution, and publishing job platform-script execution, etc.;

[0202] 254. Start the test, command processor;

[0203] 255. Automatic updates of trial packages, component retrieval - pipeline warehouse management and uploading to office application clients, etc.

[0204] Among them, the Blue Whale Continuous Integration Platform integrates and builds office application products by pulling plug-in code, and tests the office application products to obtain the final office application products, thereby realizing the production cycle control of office application products.

[0205] To facilitate better implementation of the information acquisition method of this application, this application also provides an information acquisition device based on the above-described information acquisition method. The meaning of the third target term is the same as in the above-described information acquisition method; specific implementation details can be found in the description of the method embodiments.

[0206] Please see Figure 11 , Figure 11 A schematic diagram of the structure of the information acquisition device provided in this application, wherein the information acquisition device may include:

[0207] The first acquisition module 301 is used to acquire content information corresponding to the host application built based on the first integration platform;

[0208] The generation module 302 is used to generate the plugin runtime environment based on the content information;

[0209] The second acquisition module 303 is used to acquire the target plugin corresponding to the host application based on the second integration platform according to the plugin runtime environment; wherein the integration process of the first integration platform and the second integration platform is different.

[0210] In some embodiments of this application, the device further includes a plug-in application module, which includes:

[0211] An integration unit is used to integrate the target plugin into the host application;

[0212] A generation unit is used to generate a plugin icon for the target plugin in the host application;

[0213] An execution unit is used to execute the executable file corresponding to the target plugin in response to a touch operation by a target user on the plugin icon.

[0214] In some embodiments of this application, the generation module 302 includes:

[0215] The extraction unit is used to extract the project source code and resource files corresponding to the host application from the content information;

[0216] The generation unit is used to generate a plugin runtime environment based on the project source code and the resource files through the first integration platform.

[0217] In some embodiments of this application, the integration unit includes:

[0218] The first determining subunit is used to determine the plugin executable file corresponding to the target plugin and the identification information corresponding to the plugin executable file;

[0219] An integration unit is used to establish a reference to the plugin executable file by the host application based on the identification information.

[0220] In some embodiments of this application, the second acquisition module 303 includes:

[0221] The first acquisition unit is used to acquire the original plugin corresponding to the host application through the second integration platform, based on the plugin runtime environment.

[0222] The second acquisition unit is used to obtain the target plugin based on the plugin product requirement type and the original plugin.

[0223] In some embodiments of this application, the integration unit includes:

[0224] The second determining subunit is used to determine the plugin executable file corresponding to the target plugin and the identification information corresponding to the plugin executable file;

[0225] The third determining subunit is used to determine the target application product type based on the plugin product requirement type corresponding to the target plugin;

[0226] An integration subunit is used to establish a reference to the plugin executable file by the host application of the target application product type based on the identification information.

[0227] In some embodiments of this application, the determined subunit is specifically used for:

[0228] The plugin product cycle corresponding to the target plugin is determined based on the plugin product requirement type corresponding to the target plugin.

[0229] Based on the plugin product cycle, a target application product type is selected from several application product types corresponding to the host application, wherein the application product cycle corresponding to each application product type is different.

[0230] In this embodiment, the first acquisition module 301 acquires the content information corresponding to the host application built based on the first integration platform. Then, the generation module 302 generates a plugin runtime environment based on the content information. Finally, the second acquisition module 303 acquires the target plugin corresponding to the host application based on the plugin runtime environment and the second integration platform. The integration processes of the first integration platform and the second integration platform are different.

[0231] In this embodiment, the content information of a host application built on a first integration platform is obtained. A plugin runtime environment is generated based on this content information, and a target plugin corresponding to the host application is obtained using this runtime environment and a second integration platform. Obtaining the target plugin based on the plugin runtime environment allows the target plugin to be integrated and run on the host application. The different integration processes of the first and second integration platforms allow the host application and plugins to be developed and built separately on different integration platforms. This reduces the platform environment requirements for plugin development, improves plugin development efficiency, facilitates the use of plugins to enhance the functional diversity of the host application, and increases the efficiency of application functional diversity development.

[0232] Please see Figure 12 , Figure 12 The schematic diagram of the office application and meeting plugin integration device provided in the embodiments of this application shows that the office application and meeting plugin integration device may include:

[0233] The office application development engineering module 311 is used to obtain the office application built based on the Blue Whale continuous integration platform and send the project source code and resource files of the office application to the plugin runtime environment generation module 312.

[0234] The plugin runtime environment generation module 312 is used to receive the project source code and resource files of the office application sent by the office application development project module 311, and generate the plugin runtime environment through the Blue Whale Continuous Integration Platform based on the project source code and resource files of the office application; and store the generated plugin runtime environment in the plugin code development project module 313.

[0235] The plugin code development engineering module 313 is used to receive the plugin runtime environment sent by the plugin runtime environment generation module 312, obtain the conference plugin source code according to the conference plugin product requirements, and send the conference plugin source code and plugin runtime environment to the plugin integration module 314.

[0236] The plugin integration module 314 is used to receive the meeting plugin source code and plugin runtime environment sent by the plugin code development project module 313, and obtain the integrated meeting plugin through the QQ Continuous Integration Platform based on the meeting plugin source code and plugin runtime environment, and send the integrated meeting plugin to the product fusion module 315.

[0237] Product integration module 315 is used to wake up or remotely call the Blue Whale Continuous Integration Platform, enabling the Blue Whale Continuous Integration Platform to update the meeting plugin to the corresponding version of the office application according to the product type of the meeting plugin, so as to obtain the integrated office application product, so that the office application and the meeting plugin have a unified product type or version when integrated.

[0238] In this embodiment, the target plugin is obtained based on the runtime environment of the plugin corresponding to the host application, enabling the obtained target plugin to be integrated and run on the host application. The different integration processes of the first and second integration platforms allow the host application and plugin to be developed and built separately on different integration platforms. This reduces the platform environment requirements for plugin development, improves plugin development efficiency, facilitates the use of plugins to enhance the functional diversity of the host application, and increases the efficiency of application functional diversity development.

[0239] In addition, this application also provides an electronic device, such as Figure 13 As shown, it illustrates the structural diagram of the electronic device involved in this application, specifically:

[0240] The electronic device may include components such as a processor 401 with one or more processing cores, a memory 402 with one or more computer-readable storage media, a power supply 403, and an input unit 404. Those skilled in the art will understand that... Figure 13 The electronic device structure shown does not constitute a limitation on the electronic device and may include more or fewer components than shown, or combine certain components, or have different component arrangements. Wherein:

[0241] The processor 401 is the control center of the electronic device, connecting various parts of the device via various interfaces and lines. It executes various functions and processes data by running or executing software programs and / or modules stored in the memory 402, and by calling data stored in the memory 402. Optionally, the processor 401 may include one or more processing cores; preferably, the processor 401 may integrate an application processor and a modem processor, wherein the application processor mainly handles the operating system, user interface, and applications, and the modem processor mainly handles wireless communication. It is understood that the modem processor may not be integrated into the processor 401.

[0242] The memory 402 can be used to store software programs and modules. The processor 401 executes various functional applications and data processing by running the software programs and modules stored in the memory 402. The memory 402 may mainly include a program storage area and a data storage area. The program storage area may store the operating system, application programs required for at least one function (such as sound playback function, image playback function, etc.), etc.; the data storage area may store data created according to the use of the electronic device, etc. In addition, the memory 402 may include high-speed random access memory, and may also include non-volatile memory, such as at least one disk storage device, flash memory device, or other volatile solid-state storage device. Accordingly, the memory 402 may also include a memory controller to provide the processor 401 with access to the memory 402.

[0243] The electronic device also includes a power supply 403 that supplies power to the various components. Preferably, the power supply 403 can be logically connected to the processor 401 through a power management system, thereby enabling functions such as charging, discharging, and power consumption management through the power management system. The power supply 403 may also include one or more DC or AC power supplies, recharging systems, power fault detection circuits, power converters or inverters, power status indicators, and other arbitrary components.

[0244] The electronic device may also include an input unit 404, which can be used to receive input digital or character information, and generate keyboard, mouse, joystick, optical or trackball signal inputs related to object settings and function control.

[0245] Although not shown, the electronic device may also include a display unit, etc., which will not be described in detail here. Specifically, in this embodiment, the processor 401 in the electronic device loads the executable files corresponding to the processes of one or more applications into the memory 402 according to the following instructions, and the processor 401 runs the applications stored in the memory 402, thereby implementing the steps in any of the information acquisition methods provided in this application.

[0246] This application embodiment obtains the content information of a host application built on a first integration platform, generates a plugin runtime environment based on the host application's content information, and obtains the target plugin corresponding to the host application based on this plugin runtime environment and a second integration platform. Obtaining the target plugin based on the plugin runtime environment corresponding to the host application allows the obtained target plugin to be integrated and run on the host application. The different integration processes of the first and second integration platforms allow the host application and plugins to be developed and built separately on different integration platforms. This reduces the platform environment requirements for plugin development, improves plugin development efficiency, facilitates the use of plugins to enhance the functional diversity of the host application, and improves the efficiency of application functional diversity development.

[0247] Those skilled in the art will understand that all or part of the steps in the various methods of the above embodiments can be performed by instructions, or by instructions controlling related hardware. These instructions can be stored in a computer-readable storage medium and loaded and executed by a processor.

[0248] Therefore, this application provides a computer-readable storage medium storing a computer program that can be loaded by a processor to execute the steps in any of the information acquisition methods provided in this application.

[0249] The computer-readable storage medium may include: read-only memory (ROM), random access memory (RAM), disk or optical disk, etc.

[0250] Since the instructions stored in the computer-readable storage medium can execute the steps of any of the information acquisition methods provided in this application, the beneficial effects that any of the information acquisition methods provided in this application can achieve can be realized, as detailed in the preceding embodiments, and will not be repeated here.

[0251] The above provides a detailed description of an information acquisition method, apparatus, electronic device, and computer-readable storage medium provided in this application. Specific examples have been used to illustrate the principles and implementation methods of the present invention. The description of the above embodiments is only for the purpose of helping to understand the method and core ideas of the present invention. At the same time, those skilled in the art will recognize that there will be changes in the specific implementation methods and application scope based on the ideas of the present invention. Therefore, the content of this specification should not be construed as a limitation of the present invention.

[0252] It is understood that, in the specific embodiments of this application, data related to user information, application usage data, and plugin usage data are involved. When the above embodiments of this application are applied to specific products or technologies, user permission or consent is required, and the collection, use and processing of related data must comply with the relevant laws, regulations and standards of the relevant countries and regions.

Claims

1. An information acquisition method, characterized in that, include: Obtain content information corresponding to the host application built based on the first integration platform; Based on the content information, a plugin runtime environment is generated, including: exporting the project source code and resource files of the host application from the content information corresponding to the host application; the first integration platform generates a plugin runtime environment corresponding to the host application based on the project source code and resource files; and submitting the plugin runtime environment to the second integration platform. Based on the plugin runtime environment, obtaining the target plugin corresponding to the host application through the second integration platform includes: obtaining the original plugin corresponding to the host application through the second integration platform based on the plugin runtime environment; obtaining the target plugin based on the plugin product requirement type and the original plugin; wherein, the original plugin refers to a plugin containing basic plugin function code; the plugin product requirement type refers to the version type of the plugin product; The integration processes of the first integration platform and the second integration platform are different.

2. The method according to claim 1, characterized in that, After obtaining the target plugin corresponding to the host application based on the second integration platform according to the plugin runtime environment, the method further includes: Integrate the target plugin into the host application; The host application generates a plugin icon for the target plugin; In response to a target user's touch operation on the plugin icon, the executable file corresponding to the target plugin is executed.

3. The method according to claim 2, characterized in that, The process of integrating the target plugin into the host application includes: Determine the executable file corresponding to the target plugin and the identification information corresponding to the executable file; Based on the identification information, a reference is established between the host application and the plugin executable file.

4. The method according to claim 1, characterized in that, The process of integrating the target plugin into the host application includes: Determine the executable file corresponding to the target plugin and the identification information corresponding to the executable file; The target application product type is determined based on the plugin product requirement type corresponding to the target plugin. Based on the identification information, a host application for the target application product type is established to reference the plugin executable file.

5. The method according to claim 4, characterized in that, The step of determining the target application product type based on the plugin product requirement type corresponding to the target plugin includes: The plugin product cycle corresponding to the target plugin is determined based on the plugin product requirement type corresponding to the target plugin. Based on the plugin product cycle, a target application product type is selected from several application product types corresponding to the host application, wherein the application product cycle corresponding to each application product type is different.

6. An information acquisition device, characterized in that, include: The first acquisition module is used to acquire content information corresponding to the host application built based on the first integration platform. The generation module is used to generate a plugin runtime environment based on the content information, including: exporting the project source code and resource files of the host application from the content information corresponding to the host application; the first integration platform generating a plugin runtime environment corresponding to the host application based on the project source code and resource files; and submitting the plugin runtime environment to the second integration platform. The second acquisition module is used to acquire the target plugin corresponding to the host application based on the plugin runtime environment and the second integration platform, including: acquiring the original plugin corresponding to the host application through the second integration platform according to the plugin runtime environment; obtaining the target plugin according to the plugin product requirement type and the original plugin; wherein, the original plugin refers to a plugin containing basic plugin function code; the plugin product requirement type refers to the version type of the plugin product; wherein, the integration process of the first integration platform and the second integration platform is different.

7. An electronic device, characterized in that, The electronic device includes a memory, a processor, and a computer program stored in the memory and executable on the processor. When the processor executes the computer program, it implements the steps of the information acquisition method as described in any one of claims 1-5.

8. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program that, when executed by a processor, implements the steps of the information acquisition method as described in any one of claims 1-5.

Images