CN114356441A - Plug-in preloading method and device, electronic equipment and storage medium - Google Patents
Plug-in preloading method and device, electronic equipment and storage medium Download PDFInfo
- Publication number
- CN114356441A CN114356441A CN202111575549.XA CN202111575549A CN114356441A CN 114356441 A CN114356441 A CN 114356441A CN 202111575549 A CN202111575549 A CN 202111575549A CN 114356441 A CN114356441 A CN 114356441A
- Authority
- CN
- China
- Prior art keywords
- plug
- loaded
- result
- determining
- library file
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/445—Program loading or initiating
- G06F9/44521—Dynamic linking or loading; Link editing at or after load time, e.g. Java class loading
- G06F9/44526—Plug-ins; Add-ons
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Stored Programmes (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The application relates to the technical field of computers, in particular to a plug-in preloading method, a plug-in preloading device, an electronic device and a storage medium, wherein a file verification result of a plug-in to be loaded is determined in response to a preloading instruction for the plug-in to be loaded based on each library file to be verified associated with the plug-in to be loaded in combination with a library file verification strategy, wherein the file verification result is a verification result of whether all reference library files depended by the plug-in to be loaded exist; when the file verification result is determined to pass, loading the plug-in to be loaded in the hidden configuration page to obtain bitmap information when the plug-in to be loaded is loaded in the hidden configuration page; and determining a plug-in preloading result of the plug-in to be loaded based on the bitmap information, and carrying out corresponding loading processing on the plug-in to be loaded based on the plug-in preloading result, so that the plug-in passing verification can be normally loaded and used through a plug-in preloading mechanism.
Description
Technical Field
The present application relates to the field of computer technologies, and in particular, to a method and an apparatus for preloading a plug-in, an electronic device, and a storage medium.
Background
Currently, with the development of internet technology, many different plug-ins are run in a browser, so that different functions can be realized.
In the related technology, after a related plug-in is installed in a browser, a kernel can list the existing plug-ins by loading a configuration page, start a plug-in process, call internal functions of a plug-in library, load and run the plug-ins, so that the corresponding functions of the plug-ins are realized.
However, each plugin needs to rely on other library files to assist in realizing the function of the plugin when running, and if the dependent library file does not exist or the version is incorrect, plugin loading may fail, thereby affecting the normal running of subsequent plugins. Typical cases are as follows: if the first plug-in fails to load, the result of the plug-in with the same name in different paths influences the normal loading of the latter plug-in.
Therefore, how to pre-load the plug-in unit so as to ensure normal display and use of the plug-in unit in the loading process becomes a problem to be solved urgently.
Disclosure of Invention
The embodiment of the application provides a plug-in preloading method, a plug-in preloading device, electronic equipment and a storage medium, so that a plug-in preloading mechanism is realized, and normal display and use of the plug-in are guaranteed.
The embodiment of the application provides the following specific technical scheme:
a method of plug-in preloading, comprising:
responding to a preloading instruction for a to-be-loaded plugin, determining a file verification result of the to-be-loaded plugin based on each to-be-verified library file associated with the to-be-loaded plugin by combining a library file verification strategy, wherein the file verification result is a verification result of whether all reference library files depended by the to-be-loaded plugin exist;
when the file verification result is determined to pass, loading the plug-in to be loaded in the hidden configuration page to obtain bitmap information when the plug-in to be loaded is loaded in the hidden configuration page;
and determining a plug-in preloading result of the plug-in to be loaded based on the bitmap information, and carrying out corresponding loading processing on the plug-in to be loaded based on the plug-in preloading result.
Optionally, the determining, based on each library file to be verified associated with the plug-in to be loaded, a file verification result of the plug-in to be loaded by combining a library file verification policy includes:
executing a library file output command aiming at the plug-in to be loaded, and obtaining each reference library file of the plug-in to be loaded and a query result corresponding to each reference library file;
and determining the file verification result of the plug-in to be loaded based on each query result.
Optionally, the obtaining of the query result corresponding to each of the reference library files specifically includes:
and aiming at each reference library file, respectively executing the following operations:
matching in each library file to be verified based on any one reference library file, and determining whether the library file to be verified which is the same as the reference library file is matched;
if the matching is determined to be the same as the library file to be verified, determining the query result corresponding to the library file to be verified as the found;
and if the library file to be verified which is the same as the reference library file cannot be matched, determining that the query result corresponding to the reference library file is not found.
Optionally, determining a file verification result of the plug-in to be loaded based on each query result specifically includes:
if all the query results are found, determining that the file verification result of the plug-in to be loaded passes;
and if at least one query result in the query results is determined to be not found, determining that the file verification result of the plug-in to be loaded is failed.
Optionally, loading the plug-in to be loaded in the hidden configuration page to obtain bitmap information of the plug-in to be loaded when the plug-in to be loaded is loaded in the hidden configuration page, which specifically includes:
determining hidden coordinate values corresponding to the plug-ins to be loaded based on the original coordinate values corresponding to the plug-ins to be loaded and preset hidden parameters;
and loading the plug-in to be loaded based on the hidden coordinate values to obtain bitmap information of the plug-in to be loaded.
Optionally, determining, based on the bitmap information, a plug-in preloading result of the plug-in to be loaded, specifically including:
based on the plug-in identifier corresponding to the plug-in to be loaded, searching reference bitmap information associated with the plug-in identifier from a bitmap library;
and determining a plug-in preloading result of the plug-in to be loaded based on the bitmap information and the reference bitmap information.
Optionally, determining a plug-in preloading result of the plug-in to be loaded based on the bitmap information and the reference bitmap information specifically includes:
if the pixel values corresponding to the pixel points in the bitmap information are determined to be the same as the pixel values corresponding to the corresponding reference pixel points in the reference bitmap information, determining that the plug-in preloading result of the plug-in to be loaded is passed;
and if the pixel value corresponding to at least one pixel point in the bitmap information is determined to be different from the pixel value corresponding to the corresponding pixel point in the reference bitmap information, determining that the plug-in preloading result of the plug-in to be loaded is failed.
An insert preloading device comprising:
the system comprises a first checking module, a second checking module and a third checking module, wherein the first checking module is used for responding to a preloading instruction for a to-be-loaded plug-in, determining a file checking result of the to-be-loaded plug-in based on each to-be-checked library file associated with the to-be-loaded plug-in and combining a library file checking strategy, and the file checking result is a checking result of whether all reference library files depended by the to-be-loaded plug-in exist or not;
an obtaining module, configured to load the plug-in to be loaded in the hidden configuration page when the file verification result is determined to pass, and obtain bitmap information when the plug-in to be loaded is loaded in the hidden configuration page;
and the second check module is used for determining the plug-in preloading result of the plug-in to be loaded based on the bitmap information and carrying out corresponding loading processing on the plug-in to be loaded based on the plug-in preloading result.
Optionally, when determining a file verification result of the plug-in to be loaded based on each library file to be verified associated with the plug-in to be loaded in combination with a library file verification policy, the first verification module is specifically configured to:
executing a library file output command aiming at the plug-in to be loaded, and obtaining each reference library file of the plug-in to be loaded and a query result corresponding to each reference library file;
and determining the file verification result of the plug-in to be loaded based on each query result.
Optionally, when obtaining the query result corresponding to each of the reference library files, the first verification module is specifically configured to:
and aiming at each reference library file, respectively executing the following operations:
matching in each library file to be verified based on any one reference library file, and determining whether the library file to be verified which is the same as the reference library file is matched;
if the matching is determined to be the same as the library file to be verified, determining the query result corresponding to the library file to be verified as the found;
and if the library file to be verified which is the same as the reference library file cannot be matched, determining that the query result corresponding to the reference library file is not found.
Optionally, when determining the file verification result of the plug-in to be loaded based on each query result, the first verification module is specifically configured to:
if all the query results are found, determining that the file verification result of the plug-in to be loaded passes;
and if at least one query result in the query results is determined to be not found, determining that the file verification result of the plug-in to be loaded is failed.
Optionally, the plug-in to be loaded is loaded in the hidden configuration page, and bitmap information of the plug-in to be loaded when the plug-in to be loaded is loaded in the hidden configuration page is obtained, where the obtaining module is specifically configured to:
determining hidden coordinate values corresponding to the plug-ins to be loaded based on the original coordinate values corresponding to the plug-ins to be loaded and preset hidden parameters;
and loading the plug-in to be loaded based on the hidden coordinate values to obtain bitmap information of the plug-in to be loaded.
Optionally, based on the bitmap information, determining a plug-in preloading result of the plug-in to be loaded, where the second check module is specifically configured to:
based on the plug-in identifier corresponding to the plug-in to be loaded, searching reference bitmap information associated with the plug-in identifier from a bitmap library;
and determining a plug-in preloading result of the plug-in to be loaded based on the bitmap information and the reference bitmap information.
Optionally, when determining the plug-in preloading result of the plug-in to be loaded based on the bitmap information and the reference bitmap information, the second check module is specifically configured to:
if the pixel values corresponding to the pixel points in the bitmap information are determined to be the same as the pixel values corresponding to the corresponding reference pixel points in the reference bitmap information, determining that the plug-in preloading result of the plug-in to be loaded is passed;
and if the pixel value corresponding to at least one pixel point in the bitmap information is determined to be different from the pixel value corresponding to the corresponding pixel point in the reference bitmap information, determining that the plug-in preloading result of the plug-in to be loaded is failed.
An electronic device comprises a memory, a processor and a computer program stored on the memory and capable of running on the processor, wherein the processor executes the program to realize the steps of the plug-in preloading method.
A computer-readable storage medium, on which a computer program is stored which, when being executed by a processor, carries out the steps of the above-mentioned plug-in preloading method.
In the embodiment of the application, in response to a preloading instruction for a to-be-loaded plugin, determining a file verification result of the to-be-loaded plugin in combination with a library file verification strategy based on each to-be-verified library file associated with the to-be-loaded plugin, wherein the file verification result is a verification result of whether all reference library files depended by the to-be-loaded plugin exist, when the file verification result is passed, loading the to-be-loaded plugin in a hidden configuration page to obtain bitmap information of the to-be-loaded plugin loaded on the hidden configuration page, the bitmap information represents a set of display windows of the to-be-loaded plugin displayed on the hidden configuration page, determining a plugin preloading result of the to-be-loaded plugin based on the bitmap information, and performing corresponding loading processing on the to-be-loaded plugin based on the plugin preloading result. In this way, whether all the reference library files depended on by the plug-in to be loaded exist is determined by verifying all the library files to be verified, when the reference library files depended on by the plug-in to be loaded exist, the plug-in to be loaded is loaded on the hidden configuration page, whether the plug-in to be loaded can be normally displayed is verified, the plug-in to be loaded after verification is guaranteed to be the plug-in capable of being normally displayed, normal display and use of the plug-in the actual loading process are further guaranteed, and the corresponding functions of the plug-in are achieved.
Drawings
FIG. 1 is a schematic flowchart illustrating a method for preloading plug-ins according to an embodiment of the present disclosure;
FIG. 2 is another schematic flow chart illustrating a method for preloading a plug-in unit according to an embodiment of the present application;
FIG. 3 is a schematic structural diagram of a card preloading device according to an embodiment of the present application;
fig. 4 is a schematic structural diagram of an electronic device in an embodiment of the present application.
Detailed Description
The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are only a part of the embodiments of the present application, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.
Currently, there are many different plug-ins running in a browser, each capable of performing a different function.
In the related art, after a related plug-in is installed in a browser, the plug-in can be directly loaded through a preset configuration page, and in an address bar of the browser, plug-in information corresponding to the loaded plug-in can be checked by specifying a chrome:// plugs address.
In addition, in the process of loading the configuration page, plug-ins under all possible plug-in paths listed in the configuration page are searched in a traversing manner, a specified plug-in library can be opened by executing a system call function, and a plug-in internal function is called through a system function dlsym, so that the plug-ins are loaded.
However, each plugin needs to rely on other library files to assist in realizing the function of the plugin when running, but cannot solve the problem of library file dependency, including whether the dependent library file exists, whether the version of the dependent library file is correct, the path where the library file is located, and the like.
Therefore, how to pre-load the plug-in unit so as to ensure normal display and use of the plug-in unit in the loading process becomes a problem to be solved urgently.
In order to solve the above problem, embodiments of the present application provide a method and an apparatus for preloading a plug-in, an electronic device, and a storage medium, where in response to a preloading instruction for a plug-in to be loaded, a file verification result of the plug-in to be loaded is determined based on library files to be verified associated with the plug-in to be loaded, in combination with a library file verification policy, where the file verification result is a verification result of whether all library files depended on the plug-in to be loaded exist, and when the file verification result is determined to pass, loading the plug-in to be loaded in the hidden configuration page, obtaining bitmap information of the plug-in to be loaded when the plug-in to be loaded is loaded in the hidden configuration page, representing a set of display windows of the plug-in to be loaded when the plug-in to be loaded is displayed in the hidden configuration page by the bitmap information, determining a plug-in preloading result of the plug-in to be loaded based on the bitmap information, and carrying out corresponding loading processing on the plug-in to be loaded based on the plug-in preloading result. Therefore, whether the library file depended by the plug-in to be loaded exists or not is checked, whether the library file depended by the plug-in to be loaded can run normally or not is checked, and normal display and use of the plug-in can be guaranteed based on a pre-loading mechanism of the plug-in.
Based on the above embodiment, referring to fig. 1, a schematic flow chart of a plug-in preloading method in an embodiment of the present application is shown, which specifically includes:
s10: and responding to a preloading instruction aiming at the plug-in to be loaded, and determining a file verification result of the plug-in to be loaded based on each library file to be verified associated with the plug-in to be loaded and in combination with a library file verification strategy.
And the file verification result is the verification result of whether all the library files depended by the plug-in to be loaded exist.
In the embodiment of the application, firstly, the hidden configuration page is created, so that all the plug-ins to be loaded can be loaded through the hidden configuration page. Because the problem of loading failure may occur in the actual loading process of the plug-in to be loaded, the plug-in to be loaded needs to be preloaded, and when the plug-in is successfully preloaded, the plug-in is loaded.
The hidden configuration page is used to verify whether loading of the to-be-loaded plug-in is normal, and a page address of the hidden configuration page may be chrome:// invisible-plugs, for example, which is not limited in the embodiment of the present application.
It should be noted that, in the embodiment of the present application, when performing plug-in preloading, a hidden configuration page is used, so that a user cannot access the hidden configuration page through a browser address bar or a setup page.
In specific implementation, a preloading instruction for the plug-in to be loaded is triggered and generated in the browser, so that the browser searches the plug-in to be loaded in response to the preloading instruction for the plug-in to be loaded, determines library files to be verified associated with the plug-in to be loaded, determines whether the library files depended on by the plug-in to be loaded exist or not based on the library files to be verified and a file verification strategy, and obtains a file verification result of the plug-in to be loaded.
Optionally, in the embodiment of the present application, a possible implementation manner is provided for determining a file verification result, which specifically includes:
s101: and executing a library file output command aiming at the plug-in to be loaded, and obtaining each reference library file of the plug-in to be loaded and a query result corresponding to each reference library file.
In the embodiment of the application, the library file output command for the plug-in to be loaded can be adopted to query each reference library file of the plug-in to be loaded and the query result corresponding to each reference library file.
The library file output command may be, for example, a system command ldd, which is a tool provided by the system and may output a library file on which the plug-in to be loaded depends.
Optionally, in the embodiment of the present application, a possible implementation manner is provided for determining the query result corresponding to each of the reference library files, and a process of determining the query result corresponding to each of the reference library files in the embodiment of the present application is described in detail below by taking any one of the reference library files as an example, and specifically includes:
s1010: and matching in each library file to be verified based on any one reference library file, and determining whether the library file to be verified which is the same as the reference library file is matched.
In the embodiment of the application, after obtaining each reference library file, any one reference library file is matched in each library file to be verified, and whether the library file to be verified which is the same as the reference library file can be matched in each library file to be verified is determined.
In specific implementation, each reference library file and each library file to be verified can be provided with a file identifier for uniquely distinguishing each library file, so that when matching is performed in each library to be verified, matching can be performed with the file identifier corresponding to each library file to be verified based on the file identifier corresponding to the reference library file, and whether the library file to be verified with the file identifier of the reference library file is the same in each library file to be verified is determined.
S1011: and if the matching is determined to be the same as the library file to be verified, determining the query result corresponding to the library file to be verified as the found.
In the embodiment of the application, if it is determined that the library file to be verified which is the same as the reference library file can be matched, the query result corresponding to the reference library file is determined to be found.
In specific implementation, based on the file identifier corresponding to the reference library file, whether a library file to be verified corresponding to the same file identifier exists in each library file to be verified is searched, and if the library file to be verified corresponding to the same file identifier is determined to be searched, the query result of the reference library file is marked as searched.
For example, suppose that a file identifier corresponding to a reference library file is a, library files to be verified currently associated with a to-be-loaded plugin are respectively a library file to be verified 1, a library file to be verified 2, a library file to be verified 3 and a library file to be verified 4, where the file identifier corresponding to the library file to be verified 1 is b, the file identifier corresponding to the library file to be verified 2 is a, the file identifier corresponding to the library file to be verified 3 is v, and the file identifier corresponding to the library file to be verified 4 is x, and therefore, it is determined that a file identifier corresponding to the library file to be verified 2 is the same as a file identifier corresponding to the reference library file, it is determined that a library file matching the reference library file can be found in each library file to be verified, and it is determined that a query result corresponding to the reference library file is found.
S1012: and if the library file to be verified which is the same as the reference library file cannot be matched, determining that the query result corresponding to the reference library file is not found.
In specific implementation, based on the file identifier corresponding to the reference library file, whether a library file to be verified corresponding to the same file identifier exists in each library file to be verified is searched, and if it is determined that the library file to be verified corresponding to the same file identifier cannot be searched, the query result of the reference library file is marked as not-searched.
For example, assuming that the file identifier corresponding to the reference library file is f, the library files to be verified currently associated with the plug-in to be loaded are library file to be verified 1, library file to be verified 2, library file to be verified 3 and library file to be verified 4, wherein, the file identifier corresponding to the library file to be verified 1 is b, the file identifier corresponding to the library file to be verified 2 is a, the file identifier corresponding to the library file to be verified 3 is v, the file identifier corresponding to the library file to be verified 4 is x, therefore, the file identifications corresponding to the library file to be verified 1, the library file to be verified 2, the library file to be verified 3 and the library file to be verified 4 are determined to be different from the file identifications corresponding to the reference library file, determining that the library file matched with the reference library file cannot be found in each library file to be checked, and determining that the query result corresponding to the reference library file is not found.
S102: and determining a file verification result of the plug-in to be loaded based on each query result.
In the embodiment of the application, the file verification result of the plug-in to be loaded is determined based on the respective corresponding query result of each reference library file.
Optionally, in the embodiment of the present application, a possible implementation manner is provided for determining a file verification result of a to-be-loaded plug-in, and the following describes in detail a process of determining a file verification result in the embodiment of the present application, and specifically includes:
s1021: and if all the query results are found, determining that the file verification result of the plug-in to be loaded passes.
In the embodiment of the application, whether all the query results are found is judged, and if all the query results are found, the file verification result of the plug-in to be loaded is determined to be passed.
For example, assume plug-in X is to be loadediAfter the system command ldd is executed, the plug-in X to be loaded is outputiEach of (1)Reference library files which are respectively a reference library file 1, a reference library file 2, a reference library file 3 and a reference library file 4, wherein the query result corresponding to the reference library file 1 is Found, the query result corresponding to the reference library file 2 is Found, the query result corresponding to the reference library file 3 is Found, the query result corresponding to the reference library file 4 is Found, and then the plugin X to be loaded is determinediAll the library files which are depended on exist, so that the file verification result of the plug-in to be loaded is determined to be passed.
S1022: and if at least one query result in the query results is determined to be not found, determining that the file verification result of the plug-in to be loaded is failed.
In the embodiment of the application, whether all the query results are found is judged, and if at least one of the query results is determined to be not found, the file verification result of the plug-in to be loaded is determined to be failed.
For example, assume plug-in X is to be loadediAfter the system command ldd is executed, the plug-in X to be loaded is outputiThe reference library files are respectively a reference library file 1, a reference library file 2, a reference library file 3 and a reference library file 4, wherein the query result corresponding to the reference library file 1 is NOT Found, the query result corresponding to the reference library file 2 is Found, the query result corresponding to the reference library file 3 is Found, the query result corresponding to the reference library file 4 is Found, and then the plugin X to be loaded is determinediThe dependent reference library file 1 is absent, so that the file verification result of the plug-in to be loaded is determined to be failed.
Further, if the file verification result of the plug-in to be loaded is determined to be failed, the subsequent loading process of the plug-in to be loaded is determined to be terminated, each library file to be verified, which is depended by the plug-in to be loaded, can be downloaded again, and loading is carried out again.
S11: and when the file verification result is determined to pass, loading the plug-in to be loaded in the hidden configuration page to obtain bitmap information when the plug-in to be loaded is loaded in the hidden configuration page.
The bitmap information represents a set of pixel values corresponding to each pixel point of a display window when the plug-in to be loaded is displayed on the hidden configuration page.
In the embodiment of the application, whether the file verification result passes or not is judged, and if the file verification result is determined to pass, the plug-in to be loaded is loaded in the hidden configuration page, so that the bitmap information of the plug-in to be loaded when the plug-in to be loaded is loaded in the hidden configuration page is obtained.
Optionally, in this embodiment of the present application, a possible implementation manner is provided for determining bitmap information of a to-be-loaded plug-in loaded on a hidden configuration page, and details of obtaining bitmap information of a to-be-loaded plug-in loaded on a hidden configuration page in this embodiment of the present application are described below, which specifically include:
s111: and determining hidden coordinate values corresponding to the plug-ins to be loaded based on the original coordinate values corresponding to the plug-ins to be loaded and preset hidden parameters.
In the embodiment of the application, when the plug-in to be loaded is loaded, the original coordinate values corresponding to the display window loaded in the configuration page by the plug-in to be loaded can be obtained, so that the original coordinates corresponding to the plug-in to be loaded are converted based on the original coordinates corresponding to the plug-in to be loaded and the preset hidden parameters, and the hidden coordinates corresponding to the plug-in to be loaded are obtained.
The hidden parameter may be, for example, -1, which is not limited in the embodiment of the present application.
For example, if the loading coordinates corresponding to the plug-in to be loaded are (a, b), the plug-in to be loaded is displayed by using the coordinates (-Max + | a |, -Max + | b |) in the hidden configuration page, where the absolute values of a and b are taken, and Max is the maximum value range of the coordinates. Therefore, according to the screen coordinate system specification commonly used in the computer field, the coordinates of the plug-in to be loaded are located in the upper left corner outside the screen area at this time, and are invisible areas, so that the user cannot see the plug-in.
S112: and loading the plug-in to be loaded based on each hidden coordinate value to obtain the bitmap information of the plug-in to be loaded.
In the embodiment of the application, the plug-in to be loaded is loaded based on each hidden coordinate value, so that the plug-in to be loaded can be loaded in the hidden configuration page, and simultaneously, the bitmap information of the plug-in to be loaded when the plug-in to be loaded is loaded in the hidden configuration page is obtained.
S12: and determining a plug-in preloading result of the plug-in to be loaded based on the bitmap information, and carrying out corresponding loading processing on the plug-in to be loaded based on the plug-in preloading result.
Optionally, in the embodiment of the present application, a possible implementation manner is provided for determining a plug-in preloading result of a plug-in to be loaded based on bitmap information, and the following describes in detail a process of determining the plug-in preloading result in the embodiment of the present application, and specifically includes:
s121: and based on the plug-in identifier corresponding to the plug-in to be loaded, searching reference bitmap information associated with the plug-in identifier from a bitmap library.
In the embodiment of the application, the preloading instruction further includes a plug-in identifier corresponding to the plug-in to be loaded, so that the reference bitmap information associated with the plug-in identifier can be searched from the bitmap library based on the plug-in identifier corresponding to the plug-in to be loaded and the association relationship between the plug-in identifier and the reference bitmap information.
It should be noted that the bitmap library includes a plurality of plug-ins and reference bitmap information corresponding to each plug-in, and each reference bitmap information includes a pixel value corresponding to each reference pixel.
S122: and determining a plug-in preloading result of the plug-in to be loaded based on the bitmap information and the reference bitmap information.
In the embodiment of the application, whether the bitmap information is the same as the reference bitmap information is judged, if the bitmap information is determined to be the same as the reference bitmap information, the plug-in preloading result of the plug-in to be loaded is determined to be normal, and if the bitmap information is determined to be different from the reference bitmap information, the plug-in preloading result of the plug-in to be loaded is determined to be abnormal.
Optionally, in the embodiment of the present application, a possible implementation manner is provided for determining a plug-in preloading result of a plug-in to be loaded, and a process of determining the plug-in preloading result of the plug-in to be loaded in the embodiment of the present application is described in detail below, specifically including:
s1221: and if the pixel values corresponding to the pixel points in the bitmap information are determined to be the same as the pixel values corresponding to the corresponding reference pixel points in the reference bitmap information, determining that the plug-in preloading result of the plug-in to be loaded is passed.
In the embodiment of the present application, the following operations are respectively performed for each pixel point in the bitmap information:
determining a pixel point identifier and a pixel value corresponding to any pixel point, determining a reference pixel point which is the same as the pixel point identifier in reference bitmap information, determining a pixel value corresponding to the determined reference pixel point, judging whether the pixel value corresponding to the pixel point is the same as the pixel value corresponding to the reference pixel point, if the pixel value corresponding to the pixel point is determined to be the same as the pixel value corresponding to the reference pixel point, determining that a pixel point verification result corresponding to the pixel point passes, and if the pixel value corresponding to the pixel point is determined to be different from the pixel value corresponding to the reference pixel point, determining that the pixel point verification result corresponding to the pixel point does not pass.
And then, after determining the pixel point verification result corresponding to each pixel point in the bitmap information, judging whether the pixel point verification result passes or not, if so, determining the pixel value corresponding to each pixel point in the bitmap information, wherein the pixel values corresponding to the reference pixel points in the reference bitmap information are the same, and determining that the plug-in preloading result of the plug-in to be loaded passes.
The following describes in detail a process of determining a plug-in preloading result of a plug-in to be loaded in an embodiment of the present application by using an example. For example: when a plug-in to be loaded of a hidden configuration page is displayed, bitmap information of a display window of the plug-in to be loaded is stored, namely bitmap ID1, bitmap ID1 comprises pixel values corresponding to a plurality of pixel points respectively, when the plug-in is loaded normally, bitmap information of the display window of the plug-in to be loaded is stored, namely bitmap ID2, the bitmap ID2 is used as reference bitmap information, the bitmap ID2 comprises pixel values corresponding to the plurality of reference pixel points respectively, therefore, the reference bitmap information is the bitmap information of the plug-in when the plug-in is loaded normally, the pixel values of each pixel point in the bitmap ID1 are compared respectively, whether the pixel values corresponding to the corresponding reference pixel points in the bitmap ID2 are the same or not is judged, if the pixel value of any one pixel point in the bitmap ID1 is determined, the pixel values corresponding to the corresponding reference pixel points in the bitmap ID2 are different, the plug-in-plug-in-to-load result is determined to be failed, and if all the pixel values in the pixel points in the bitmap ID1 are determined, the pixel values corresponding to the corresponding reference pixel points in BitmapID2 are all the same, then the plug-in preload result for the plug-in to be loaded is determined to be passed.
S1222: and if the pixel value corresponding to at least one pixel point in the bitmap information is determined to be different from the pixel value corresponding to the corresponding pixel point in the reference bitmap information, determining that the plug-in preloading result of the plug-in to be loaded is failed.
In the embodiment of the application, after the pixel point verification results corresponding to the pixel points in the bitmap information are determined, whether the pixel point verification results pass or not is judged, if the pixel point verification results pass, the pixel values corresponding to the pixel points in the bitmap information are determined, the pixel values corresponding to the reference pixel points in the reference bitmap information are different, and the plug-in preloading result of the plug-in to be loaded is determined to be not passed.
It should be noted that, as long as the pixel value corresponding to any one pixel point in the bitmap information is determined, and the pixel value corresponding to the corresponding reference pixel point in the reference bitmap information is different, it can be determined that the plug-in preloading result of the plug-in to be loaded is failed.
Further, if it is determined that the plug-in preloading result of the plug-in to be loaded does not pass, the system command dlclose is used to unload the plug-in to be loaded, and a new search path is set again, where the search path may be, for example: export LD _ LIBRARY _ PATH is PATH.
It should be noted that Path belongs to the system search Path set {/usr/lib; /usr/lib 64; usr/local/lib; /usr/local/lib 64; … }.
In the embodiment of the application, whether each reference library file depended on by the plug-in to be loaded exists is checked, whether each reference library file depended on by the plug-in to be loaded can run normally is checked, and the plug-in to be loaded passing the check can run and be used normally.
Based on the foregoing embodiment, the following describes in detail a plug-in preloading method in an embodiment of the present application with reference to fig. 2, which is another schematic flow chart of the plug-in preloading method in an embodiment of the present application, and specifically includes:
s200: a hidden configuration page is created.
In the embodiment of the application, the hidden configuration page is used for verifying whether the loading of the plug-in to be loaded is normal.
S201: and loading the hidden configuration page, and traversing and searching the plug-ins to be loaded under all possible plug-in paths listed in the hidden configuration page.
S202: plug-in X to be loadediAnd executing the system command ldd and outputting each query result.
S203: and judging whether each query result contains NOT Found, if NOT, executing S204, and if so, executing S210.
It should be noted that, in the embodiment of the present application, if it is determined that the query result is Found, it is determined that the query result includes Found, and if it is determined that the query result is NOT Found, it is determined that the query result includes NOT Found.
S204: calling dlopen to load plug-in X to be loadedi。
S205: and obtaining hidden coordinates based on the hidden parameters and the original coordinates, displaying the plug-in to be loaded by the hidden coordinates in a hidden configuration page, and obtaining bitmap information of the plug-in to be loaded.
S206: and judging whether the bitmap information is the same as the reference bitmap information, if so, executing S207, and otherwise, executing S209.
S207: calling an internal function ss of the plug-in library through a system function dlsym, and loading a plug-in X to be loadedi。
S208: and judging whether the plug-ins to be loaded are not verified, if so, executing S202, and if not, executing S210.
S209: a new search path is set and execution returns to S202.
S210: and (6) ending.
Based on the same inventive concept, the embodiment of the present application further provides a plug-in preloading device, which may be a hardware structure, a software module, or a hardware structure plus a software module. Based on the above embodiments, referring to fig. 3, a schematic structural diagram of a plug-in preloading device in an embodiment of the present application is shown, which specifically includes:
the first checking module 300 is configured to, in response to a preload instruction for a to-be-loaded plugin, determine, based on each to-be-checked library file associated with the to-be-loaded plugin, a file checking result of the to-be-loaded plugin in combination with a library file checking policy, where the file checking result is a checking result of whether all reference library files depended by the to-be-loaded plugin exist;
an obtaining module 310, configured to load the plug-in to be loaded in the hidden configuration page when the file verification result is determined to pass, and obtain bitmap information when the plug-in to be loaded is loaded on the hidden configuration page;
the second checking module 320 is configured to determine a plug-in preloading result of the plug-in to be loaded based on the bitmap information, and perform corresponding loading processing on the plug-in to be loaded based on the plug-in preloading result.
Optionally, when determining a file verification result of the plug-in to be loaded based on each library file to be verified associated with the plug-in to be loaded and by combining a library file verification policy, the first verification module 300 is specifically configured to:
executing a library file output command aiming at the plug-in to be loaded, and obtaining each reference library file of the plug-in to be loaded and a query result corresponding to each reference library file;
and determining the file verification result of the plug-in to be loaded based on each query result.
Optionally, when obtaining the query result corresponding to each of the reference library files, the first verification module 300 is specifically configured to:
and aiming at each reference library file, respectively executing the following operations:
matching in each library file to be verified based on any one reference library file, and determining whether the library file to be verified which is the same as the reference library file is matched;
if the matching is determined to be the same as the library file to be verified, determining the query result corresponding to the library file to be verified as the found;
and if the library file to be verified which is the same as the reference library file cannot be matched, determining that the query result corresponding to the reference library file is not found.
Optionally, when determining the file verification result of the plug-in to be loaded based on each query result, the first verification module 300 is specifically configured to:
if all the query results are found, determining that the file verification result of the plug-in to be loaded passes;
and if at least one query result in the query results is determined to be not found, determining that the file verification result of the plug-in to be loaded is failed.
Optionally, the to-be-loaded plug-in is loaded in the hidden configuration page to obtain bitmap information of the to-be-loaded plug-in when loaded in the hidden configuration page, and the obtaining module 310 is specifically configured to:
determining hidden coordinate values corresponding to the plug-ins to be loaded based on the original coordinate values corresponding to the plug-ins to be loaded and preset hidden parameters;
and loading the plug-in to be loaded based on the hidden coordinate values to obtain bitmap information of the plug-in to be loaded.
Optionally, based on the bitmap information, a plug-in preloading result of the plug-in to be loaded is determined, and the second check module 320 is specifically configured to:
based on the plug-in identifier corresponding to the plug-in to be loaded, searching reference bitmap information associated with the plug-in identifier from a bitmap library;
and determining a plug-in preloading result of the plug-in to be loaded based on the bitmap information and the reference bitmap information.
Optionally, when determining the plug-in preloading result of the plug-in to be loaded based on the bitmap information and the reference bitmap information, the second check module 320 is specifically configured to:
if the pixel values corresponding to the pixel points in the bitmap information are determined to be the same as the pixel values corresponding to the corresponding reference pixel points in the reference bitmap information, determining that the plug-in preloading result of the plug-in to be loaded is passed;
and if the pixel value corresponding to at least one pixel point in the bitmap information is determined to be different from the pixel value corresponding to the corresponding pixel point in the reference bitmap information, determining that the plug-in preloading result of the plug-in to be loaded is failed.
Based on the above embodiments, referring to fig. 4, a schematic structural diagram of an electronic device in an embodiment of the present application is shown.
An embodiment of the present application provides an electronic device, which may include a processor 410 (CPU), a memory 420, an input device 430, an output device 440, and the like, wherein the input device 430 may include a keyboard, a mouse, a touch screen, and the like, and the output device 440 may include a Display device, such as a Liquid Crystal Display (LCD), a Cathode Ray Tube (CRT), and the like.
The processor 410 is configured to execute any one of the plug-in preloading methods according to the embodiments of the present application by calling the program instructions stored in the memory 420 and the processor 410 is configured to execute the plug-in preloading method according to the obtained program instructions.
Based on the foregoing embodiments, in the embodiments of the present application, a computer-readable storage medium is provided, on which a computer program is stored, and the computer program, when executed by a processor, implements any of the plug-in preloading methods in any of the above-described method embodiments.
As will be appreciated by one skilled in the art, embodiments of the present application may be provided as a method, system, or computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.
The present application is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to the application. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
It will be apparent to those skilled in the art that various changes and modifications may be made in the present application without departing from the spirit and scope of the application. Thus, if such modifications and variations of the present application fall within the scope of the claims of the present application and their equivalents, the present application is intended to include such modifications and variations as well.
Claims (16)
1. A method for preloading a card, comprising:
responding to a preloading instruction for a to-be-loaded plugin, determining a file verification result of the to-be-loaded plugin based on each to-be-verified library file associated with the to-be-loaded plugin by combining a library file verification strategy, wherein the file verification result is a verification result of whether all reference library files depended by the to-be-loaded plugin exist;
when the file verification result is determined to pass, loading the plug-in to be loaded in the hidden configuration page to obtain bitmap information when the plug-in to be loaded is loaded in the hidden configuration page;
and determining a plug-in preloading result of the plug-in to be loaded based on the bitmap information, and carrying out corresponding loading processing on the plug-in to be loaded based on the plug-in preloading result.
2. The method according to claim 1, wherein the determining a file verification result of the plug-in to be loaded based on each library file to be verified associated with the plug-in to be loaded in combination with a library file verification policy specifically includes:
executing a library file output command aiming at the plug-in to be loaded, and obtaining each reference library file of the plug-in to be loaded and a query result corresponding to each reference library file;
and determining the file verification result of the plug-in to be loaded based on each query result.
3. The method according to claim 2, wherein the obtaining of the query result corresponding to each of the reference library files specifically comprises:
and aiming at each reference library file, respectively executing the following operations:
matching in each library file to be verified based on any one reference library file, and determining whether the library file to be verified which is the same as the reference library file is matched;
if the matching is determined to be the same as the library file to be verified, determining the query result corresponding to the library file to be verified as the found;
and if the library file to be verified which is the same as the reference library file cannot be matched, determining that the query result corresponding to the reference library file is not found.
4. The method of claim 3, wherein determining the file verification result of the plug-in to be loaded based on the query results specifically comprises:
if all the query results are found, determining that the file verification result of the plug-in to be loaded passes;
and if at least one query result in the query results is determined to be not found, determining that the file verification result of the plug-in to be loaded is failed.
5. The method of claim 1, wherein loading the plug-in to be loaded in the hidden configuration page to obtain bitmap information of the plug-in to be loaded when the plug-in to be loaded is loaded in the hidden configuration page specifically includes:
determining hidden coordinate values corresponding to the plug-ins to be loaded based on the original coordinate values corresponding to the plug-ins to be loaded and preset hidden parameters;
and loading the plug-in to be loaded based on the hidden coordinate values to obtain bitmap information of the plug-in to be loaded.
6. The method according to any one of claims 1 to 5, wherein determining, based on the bitmap information, a plug-in preloading result for the plug-in to be loaded specifically includes:
based on the plug-in identifier corresponding to the plug-in to be loaded, searching reference bitmap information associated with the plug-in identifier from a bitmap library;
and determining a plug-in preloading result of the plug-in to be loaded based on the bitmap information and the reference bitmap information.
7. The method of claim 6, wherein determining the plug-in preloading result of the plug-in to be loaded based on the bitmap information and the reference bitmap information specifically comprises:
if the pixel values corresponding to the pixel points in the bitmap information are determined to be the same as the pixel values corresponding to the corresponding reference pixel points in the reference bitmap information, determining that the plug-in preloading result of the plug-in to be loaded is passed;
and if the pixel value corresponding to at least one pixel point in the bitmap information is determined to be different from the pixel value corresponding to the corresponding pixel point in the reference bitmap information, determining that the plug-in preloading result of the plug-in to be loaded is failed.
8. An insert preloading device, comprising:
the system comprises a first checking module, a second checking module and a third checking module, wherein the first checking module is used for responding to a preloading instruction for a to-be-loaded plug-in, determining a file checking result of the to-be-loaded plug-in based on each to-be-checked library file associated with the to-be-loaded plug-in and combining a library file checking strategy, and the file checking result is a checking result of whether all reference library files depended by the to-be-loaded plug-in exist or not;
an obtaining module, configured to load the plug-in to be loaded in the hidden configuration page when the file verification result is determined to pass, and obtain bitmap information when the plug-in to be loaded is loaded in the hidden configuration page;
and the second check module is used for determining the plug-in preloading result of the plug-in to be loaded based on the bitmap information and carrying out corresponding loading processing on the plug-in to be loaded based on the plug-in preloading result.
9. The apparatus according to claim 8, wherein when determining a file verification result of the plug-in to be loaded based on each library file to be verified associated with the plug-in to be loaded in combination with a library file verification policy, the first verification module is specifically configured to:
executing a library file output command aiming at the plug-in to be loaded, and obtaining each reference library file of the plug-in to be loaded and a query result corresponding to each reference library file;
and determining the file verification result of the plug-in to be loaded based on each query result.
10. The apparatus according to claim 9, wherein when obtaining the query result corresponding to each of the reference library files, the first checking module is specifically configured to:
and aiming at each reference library file, respectively executing the following operations:
matching in each library file to be verified based on any one reference library file, and determining whether the library file to be verified which is the same as the reference library file is matched;
if the matching is determined to be the same as the library file to be verified, determining the query result corresponding to the library file to be verified as the found;
and if the library file to be verified which is the same as the reference library file cannot be matched, determining that the query result corresponding to the reference library file is not found.
11. The apparatus according to claim 10, wherein, when determining the file verification result of the plug-in to be loaded based on each query result, the first verification module is specifically configured to:
if all the query results are found, determining that the file verification result of the plug-in to be loaded passes;
and if at least one query result in the query results is determined to be not found, determining that the file verification result of the plug-in to be loaded is failed.
12. The apparatus of claim 8, wherein the plug-in to be loaded is loaded in the hidden configuration page, and the bitmap information of the plug-in to be loaded when loaded in the hidden configuration page is obtained, and the obtaining module is specifically configured to:
determining hidden coordinate values corresponding to the plug-ins to be loaded based on the original coordinate values corresponding to the plug-ins to be loaded and preset hidden parameters;
and loading the plug-in to be loaded based on the hidden coordinate values to obtain bitmap information of the plug-in to be loaded.
13. The apparatus according to any of claims 8 to 12, wherein, based on the bitmap information, a plug-in preloading result of the plug-in to be loaded is determined, the second check-up module being specifically configured to:
based on the plug-in identifier corresponding to the plug-in to be loaded, searching reference bitmap information associated with the plug-in identifier from a bitmap library;
and determining a plug-in preloading result of the plug-in to be loaded based on the bitmap information and the reference bitmap information.
14. The apparatus of claim 13, wherein when determining the result of preloading the plug-in for the plug-in to be loaded based on the bitmap information and the reference bitmap information, the second check-up module is specifically configured to:
if the pixel values corresponding to the pixel points in the bitmap information are determined to be the same as the pixel values corresponding to the corresponding reference pixel points in the reference bitmap information, determining that the plug-in preloading result of the plug-in to be loaded is passed;
and if the pixel value corresponding to at least one pixel point in the bitmap information is determined to be different from the pixel value corresponding to the corresponding pixel point in the reference bitmap information, determining that the plug-in preloading result of the plug-in to be loaded is failed.
15. An electronic device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, wherein the steps of the method of any of claims 1-7 are implemented when the program is executed by the processor.
16. A computer-readable storage medium having stored thereon a computer program, characterized in that: the computer program when executed by a processor implements the steps of the method of any one of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111575549.XA CN114356441B (en) | 2021-12-22 | 2021-12-22 | Plug-in preloading method and device, electronic equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111575549.XA CN114356441B (en) | 2021-12-22 | 2021-12-22 | Plug-in preloading method and device, electronic equipment and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN114356441A true CN114356441A (en) | 2022-04-15 |
| CN114356441B CN114356441B (en) | 2022-09-23 |
Family
ID=81100664
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202111575549.XA Active CN114356441B (en) | 2021-12-22 | 2021-12-22 | Plug-in preloading method and device, electronic equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114356441B (en) |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20050060698A1 (en) * | 2003-09-11 | 2005-03-17 | International Business Machines Corporation | Mechanism for loading plugin classes at an appropriate location in the class loader hierarchy |
| CN1968154A (en) * | 2006-09-15 | 2007-05-23 | 华为技术有限公司 | System and method for service expansion using plug |
| CN105867956A (en) * | 2015-10-28 | 2016-08-17 | 乐视网信息技术（北京）股份有限公司 | Method and device for showing plugin view element in host application page |
| CN107038045A (en) * | 2017-03-30 | 2017-08-11 | 腾讯科技（深圳）有限公司 | Load the method and device of library file |
| CN108197020A (en) * | 2017-12-28 | 2018-06-22 | 掌阅科技股份有限公司 | Plug-in unit method of calibration, electronic equipment and computer storage media |
-
2021
- 2021-12-22 CN CN202111575549.XA patent/CN114356441B/en active Active
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20050060698A1 (en) * | 2003-09-11 | 2005-03-17 | International Business Machines Corporation | Mechanism for loading plugin classes at an appropriate location in the class loader hierarchy |
| CN1968154A (en) * | 2006-09-15 | 2007-05-23 | 华为技术有限公司 | System and method for service expansion using plug |
| CN105867956A (en) * | 2015-10-28 | 2016-08-17 | 乐视网信息技术（北京）股份有限公司 | Method and device for showing plugin view element in host application page |
| CN107038045A (en) * | 2017-03-30 | 2017-08-11 | 腾讯科技（深圳）有限公司 | Load the method and device of library file |
| CN108197020A (en) * | 2017-12-28 | 2018-06-22 | 掌阅科技股份有限公司 | Plug-in unit method of calibration, electronic equipment and computer storage media |
Also Published As
| Publication number | Publication date |
|---|---|
| CN114356441B (en) | 2022-09-23 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN111695156A (en) | Service platform access method, device, equipment and storage medium | |
| CN110162429B (en) | System repair method, server and storage medium | |
| US20160171104A1 (en) | Detecting multistep operations when interacting with web applications | |
| US20150242470A1 (en) | Systems and methods for recommending software applications | |
| CN112558946A (en) | Method, device and equipment for generating code and computer readable storage medium | |
| US20170169069A1 (en) | Data integrity checking in a distributed filesystem using object versioning | |
| CN105678168A (en) | Method and apparatus for detecting Shellcode based on stack frame abnormity | |
| CN110688111A (en) | Configuration method, device, server and storage medium of business process | |
| US7814334B2 (en) | Method and apparatus for changing and adding activation keys for functions of digital content without having to change and recompile the digital content | |
| CN105354490B (en) | Method and equipment for processing hijacked browser | |
| US11868465B2 (en) | Binary image stack cookie protection | |
| CN111966630B (en) | File type detection method, device, equipment and medium | |
| CN114356441B (en) | Plug-in preloading method and device, electronic equipment and storage medium | |
| US20090007277A1 (en) | System and Method for Automatically Hiding Sensitive Information Obtainable from a Process Table | |
| WO2017054731A1 (en) | Method and device for processing hijacked browser | |
| CN108197041B (en) | Method, device and storage medium for determining parent process of child process | |
| CN105354506A (en) | File hiding method and apparatus | |
| KR102310766B1 (en) | Application Integrity Checking Method | |
| CN115145674A (en) | Page jump method, device, equipment and medium based on dynamic anchor point | |
| CN115827125A (en) | Interface control testing method and device | |
| CN114443721A (en) | Data processing method and device, electronic equipment and storage medium | |
| US9477448B2 (en) | Screen-oriented computing program refactoring | |
| CN114489698A (en) | Application program installation method and device | |
| CN111859403A (en) | Method and device for determining dependency vulnerability, electronic equipment and storage medium | |
| CN112543104A (en) | Application program packaging method and device, electronic equipment and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |