SDK (Software Development Kit) loading execution method and equipment of Web view and storage medium

Abstract

The invention relates to the field of plug-in loading, and discloses an SDK (Software Development Kit) loading execution method and equipment of a Web view and a storage medium. The method comprises the following steps: receiving a selection instruction of a user, and loading an SDK file corresponding to the selection instruction into preset memory data; displaying an HTML (Hypertext Markup Language) page on a Web view, and receiving an SDK (Software Development Kit) execution parameter on the Calling an SDK file corresponding to the SDK number in the memory data, and performing execution processing on the entity parameter according to the SDK file corresponding to the SDK number to obtain execution data; sending the execution data to an IP address corresponding to the instance number, and monitoring a state code fed back by the IP address; and when the status code is received, the status code is sent to the HTML page. In the embodiment of the invention, the dynamic loading execution of the SDK file in the application program is realized, and the system maintenance cost is reduced.

Description

Technical Field

[0001] The present invention relates to the field of plug-in loading, and in particular to a method, device, and storage medium for loading and executing an SDK of a Web view. Background Art

[0002] In modern software development, the use of SDKs (Software Development Kits) has become extremely common. An SDK provides developers with a series of pre-packaged functions, interfaces, and tools, enabling developers to quickly implement specific functional modules without having to write code from scratch. This "out-of-the-box" feature greatly improves development efficiency, shortens the development cycle, and reduces development costs. For example, a mobile application developer can quickly implement location positioning and navigation functions by integrating a map SDK without having to delve into complex map rendering and positioning algorithms.

[0003] However, traditional SDK integration methods often have some limitations. The most common problem is that developers need to hard-code SDK method calls in the application. This means that developers must know exactly which SDK functions need to be called at compile time and write these calls into the code. Although this method is simple and straightforward, it lacks flexibility. Once the SDK interface changes, or developers need to dynamically load and execute methods in the SDK, this hard-coded approach becomes very inconvenient. Developers may need to modify the code, recompile, and redeploy the application, which not only increases maintenance costs but may also lead to version compatibility issues.

[0004] In addition, the hard-coded SDK integration method is also difficult to meet the requirements of some advanced development scenarios. For example, in some cases, users need to switch between different SDK implementations in different runtime environments. The traditional hard-coded method is difficult to achieve this dynamicity and flexibility because it cannot dynamically resolve and execute methods in the SDK at runtime. Therefore, in order to solve the problem that current SDK coding is difficult to dynamically load and execute in an application, resulting in excessive maintenance costs, a new technology is needed to solve the current problem. Summary of the Invention

[0005] The main purpose of the present invention is to solve the technical problem that current SDK coding is difficult to dynamically load and execute in an application, resulting in excessive maintenance costs.

[0006] The first aspect of the present invention provides a method for loading and executing an SDK of a Web view, and the method for loading and executing an SDK of a Web view includes:

[0007] Receiving a selection instruction from a user, and loading the SDK file corresponding to the selection instruction into a preset memory data;

[0008] Display an HTML page in the Web view and receive the SDK execution parameters in the HTML page, where the SDK execution parameters include: instance number, SDK number, and entity parameters;

[0009] Retrieve the SDK file corresponding to the SDK number in the memory data, and perform execution processing on the entity parameters according to the SDK file corresponding to the SDK number to obtain execution data;

[0010] Send the execution data to the IP address corresponding to the instance number, and monitor the status code feedback from the IP address;

[0011] When the status code is received, send the status code to the HTML page.

[0012] Optionally, in the first implementation manner of the first aspect of the present invention, the displaying an HTML page in the Web view and receiving the SDK execution parameters in the HTML page includes:

[0013] Use the WebView2 control to load and display the HTML page, where the HTML page includes: a first input box, a second input box, and a third input box;

[0014] Receive the instance number in the first input box, receive the SDK number in the second input box, and receive the entity parameters in the third input box;

[0015] Combine and package the instance number, the SDK number, and the entity parameters to generate SDK execution parameters in the HTML page;

[0016] Receive the SDK execution parameters in the HTML page.

[0017] Optionally, in the second implementation manner of the first aspect of the present invention, the receiving the SDK execution parameters in the HTML page includes:

[0018] Use the WPF framework to receive the SDK execution parameters passed by the HTML page based on the WebMessageReceived event.

[0019] Optionally, in the third implementation manner of the first aspect of the present invention, the performing execution processing on the entity parameters according to the SDK file corresponding to the SDK number to obtain execution data includes:

[0020] According to the SDK file corresponding to the SDK number, write the entity parameters into the command function corresponding to the SDK number to generate execution data.

[0021] Optionally, in the fourth implementation manner of the first aspect of the present invention, the instance number includes: the AGV vehicle code, the entity parameters include: the motion coordinates and the speed setting, and the entity parameters are processed according to the SDK number corresponding to the SDK file to obtain the execution data including:

[0022] Determine whether the command function corresponding to the SDK number is a motion function;

[0023] When it is a motion function, write the motion coordinates and the speed setting into the motion function to generate execution data;

[0024] When it is not a motion function, encapsulate the command function corresponding to the SDK number to generate execution data.

[0025] Optionally, in the fifth implementation manner of the first aspect of the present invention, the status codes listened to the feedback of the IP address include:

[0026] Reset the preset timer;

[0027] Listen to the feedback data sent by the IP address, and determine whether the feedback data belongs to the status code;

[0028] When it does not belong to the status code, determine whether the duration of the timer exceeds the preset listening duration;

[0029] When it does not exceed the preset listening duration, continue to listen to the feedback data sent by the IP address;

[0030] When it exceeds the preset listening duration, resend the execution data to the IP address corresponding to the instance number.

[0031] Optionally, in the sixth implementation manner of the first aspect of the present invention, the sending the status code to the HTML page includes:

[0032] Use the WPF framework and use the PostMessageAsString function or the PostWebMessageAsJson function to send the status code to the HTML page.

[0033] Optionally, in the seventh implementation manner of the first aspect of the present invention, the sending the execution data to the IP address corresponding to the instance number includes:

[0034] Perform a query process in the preset address data table with the instance number as the key character to obtain the query result;

[0035] When the query result is empty, send an alarm message to the HTML page;

[0036] When the query result is not empty, extract the query value characters in the query result, and use the SDK number as the key character to perform a query process in the query value characters to obtain the SDK number value characters;

[0037] Determine the SDK number value characters as the IP address corresponding to the instance number.

[0038] The second aspect of the present invention provides an SDK loading and execution device for a Web view, including: a memory and at least one processor, wherein instructions are stored in the memory, and the memory and the at least one processor are interconnected by a line; the at least one processor calls the instructions in the memory to enable the SDK loading and execution device of the Web view to execute the above-mentioned SDK loading and execution method of the Web view.

[0039] The third aspect of the present invention provides a computer-readable storage medium, in which instructions are stored, and when it runs on a computer, it enables the computer to execute the above-mentioned SDK loading and execution method of the Web view.

[0040] In the embodiments of the present invention, the SDK loading and execution based on WebView2 can dynamically load the SDK and execute the methods therein, and at the same time realize the efficient communication between the Web view and the native application. There is no need to redeploy the relevant environment locally, effectively reducing the incompatibility during the compilation process. The present invention has the advantages of high flexibility and easy extensibility, and is applicable to various scenarios that require dynamic loading and execution of the SDK. It does not require all executions at the backend to be on the client, solving the problem of high maintenance costs caused by the difficulty of dynamically loading and executing the current SDK coding in the application. Description of the Drawings

[0041] Figure 1 It is a schematic diagram of an embodiment of the SDK loading and execution method of the Web view in the embodiments of the present invention;

[0042] Figure 2 It is a schematic diagram of a specific embodiment of step 104 in the embodiments of the present invention;

[0043] Figure 3 It is a schematic diagram of another specific embodiment of step 104 in the embodiments of the present invention;

[0044] Figure 4 It is a schematic diagram of an embodiment of the SDK loading and execution device of the Web view in the embodiments of the present invention. Detailed Embodiments

[0045] The embodiments of the present invention provide an SDK loading and execution method, device and storage medium for a Web view.

[0046] Embodiments of the present disclosure will be described in more detail below with reference to the accompanying drawings. Although some embodiments of the present disclosure are shown in the drawings, it should be understood that the present disclosure can be implemented in various forms and should not be construed as limited to the embodiments set forth herein. On the contrary, these embodiments are provided to more thoroughly and completely understand the present disclosure. It should be understood that the drawings and embodiments of the present disclosure are only for exemplary purposes and are not used to limit the protection scope of the present disclosure.

[0047] In the description of the embodiments of the present disclosure, the term "comprising" and its like shall be understood as an open inclusion, i.e., "including but not limited to". The term "based on" shall be understood as "at least partially based on". The term "one embodiment" or "the embodiment" shall be understood as "at least one embodiment". The terms "first", "second", etc. may refer to different or the same objects. There may also be other explicit and implicit definitions hereinafter.

[0048] For ease of understanding, the specific process of the embodiments of the present invention will be described below. Please refer to Figure 1 , an embodiment of the SDK loading and execution method for the Web view in the embodiments of the present invention includes:

[0049] 101. Receive a selection instruction from the user and load the SDK file corresponding to the selection instruction into the pre-set memory data;

[0050] In this embodiment, receive the user's interface click selection instruction, and based on the interface click instruction, load the corresponding SDK file into the pre-set memory data and the application program, so that functions in the SDK data can be called to process various types of task data subsequently.

[0051] 102. Display an HTML page on the Web view and receive the SDK execution parameters on the HTML page, where the SDK execution parameters include: instance number, SDK number, entity parameter;

[0052] In this embodiment, HTML page data is displayed on the Web view, and the SDK execution parameters filled in by the user using the HTML page are received. The user can input information such as the instance number, SDK number, and entity parameter into the HTML page in an input line based on the set string format, and then the HTML page transmits it to the application program for data processing to execute various tasks.

[0053] Further, the following specific implementation manners are included in step 102:

[0054] 1021. Use the WebView2 control to load and display the HTML page, where the HTML page includes: a first input box, a second input box, and a third input box;

[0055] 1022. Receive the instance number in the first input box, receive the SDK number in the second input box, and receive the entity parameters in the third input box;

[0056] 1023. Combine and package the instance number, the SDK number, and the entity parameters, and generate SDK execution parameters in the HTML page;

[0057] 1024. Receive the SDK execution parameters in the HTML page.

[0058] In steps 1021 - 1024, the HTML page is embedded in the WebView2 control. The WebView2 control is used to start the HTML page. The WebView2 control will render and display according to the content of the HTML page, in accordance with the layout, style, and script of the web page, and supports HTML, CSS, and JavaScript. WebView2 is based on the Chromium kernel. Therefore, when displaying web page content, it can be well compatible with various modern web standards, reducing the workload of development and debugging. In the UI design of the HTML page, there are a first input box, a second input box, and a third input box designed to receive the data input of the instance number, the SDK number, and the entity parameters respectively.

[0059] After the user finishes inputting and clicks the input confirmation information, the instance number, the SDK number, and the entity parameters will be combined and packaged, and SDK execution parameters will be generated on the HTML page. Then, the HTML page will transmit the SDK execution parameters, and the SDK execution parameters will be parsed and run.

[0060] Further, step 1024 includes the following specific implementation manners:

[0061] 10241. Use the WPF framework to receive the SDK execution parameters passed by the HTML page based on the WebMessageReceived event.

[0062] In step 10241, WebView2 will trigger the WebMessageReceived event. The WPF application obtains the message data in JSON format through e.TryGetWebMessageAsString(), and the SDK execution parameters will be passed into the WPF application.

[0063] 103. Retrieve the SDK file corresponding to the SDK number in the memory data, and perform execution processing on the entity parameters according to the SDK file corresponding to the SDK number to obtain execution data;

[0064] In this embodiment, the message communication module receives the message sent by the HTML page of WebView2 through postMessage, retrieves the SDK file library corresponding to the SDK number in the memory data to parse the SDK method and parameter information included in the message, and performs compilation and execution processing on the entity parameter data to generate execution data.

[0065] Further, the following specific implementation manners are included in step 103:

[0066] 1031. Write the entity parameters into the command function corresponding to the SDK number according to the SDK file corresponding to the SDK number, and generate execution data.

[0067] In step 1031, the SDK number is the SDK file to be called and the command instruction to be called. The entity parameters, that is, the actual data to be run, are written into the command function corresponding to the SDK number for compilation to generate execution data.

[0068] Specifically, the instance number includes: AGV vehicle code, and the entity parameters include: movement coordinates, speed setting. The following specific implementation manners are included in step 103:

[0069] 1032. Determine whether the command function corresponding to the SDK number is a movement function;

[0070] 1033. When it is a movement function, write the movement coordinates and the speed setting into the movement function to generate execution data;

[0071] 1034. When it is not a movement function, encapsulate the command function corresponding to the SDK number to generate execution data.

[0072] In steps 1032 - 1034, when the instance number is the AGV vehicle code, the entity parameters are movement coordinates ((4, 9), (8, 6)), the speed setting is speed = 4, and the command functions of the SDK number are start(), stop(), move (starting point, ending point). First, analyze whether the command function is the movement function move (starting point, ending point). If it is a movement function, write the movement coordinates and the speed setting into the movement function to generate execution data.

[0073] If it is not a movement function, the command function is start() or stop(), then there is no need to write parameter data into the function, and the function is directly used as the execution data.

[0074] 104. Send the execution data to the IP address corresponding to the instance number, and listen to the status code feedback by the IP address;

[0075] In this embodiment, the execution data is sent to the IP address corresponding to the instance number. For example, the instance number is the AGV vehicle code, and different AGV vehicle codes correspond to different IP addresses. The status code feedback by the IP address is monitored.

[0076] Specifically, please refer to Figure 2 , Figure 2 which is a schematic diagram of a specific embodiment of step 104 in the embodiment of the present invention. In step 104, "sending the execution data to the IP address corresponding to the instance number" includes the following specific implementation manners:

[0077] 1041. Query and process in the preset address data table with the instance number as the key character to obtain a query result;

[0078] 1042. When the query result is empty, send an alarm message to the HTML page;

[0079] 1043. When the query result is not empty, extract the query value character in the query result, and query and process in the query value character with the SDK number as the key character to obtain the SDK number value character;

[0080] 1044. Determine the SDK number value character as the IP address corresponding to the instance number.

[0081] In steps 1041-1044, the address data table stores {id / mskslaaad:{SDK1:XXX, SDK2:YYY, SDK3:ZZZ}}. First, query and process in the address data table based on the instance number id / mskslaaad to obtain a query result.

[0082] If the query is null, it means that the instance number is not stored in the address data table.

[0083] If the query result is {id / mskslaaad:{SDK1:XXX, SDK2:YYY, SDK3:ZZZ}}, then extract the value character in {id / mskslaaad:{SDK1:XXX, SDK2:YYY, SDK3:ZZZ}}. Different ports are called for different SDK numbers. Using the SDK number (SDK3) as the key character, query to obtain the IP address corresponding to SDK3 as ZZZ, and determine this IP address ZZZ as the IP address corresponding to the instance number.

[0084] Specifically, please refer to Figure 3 , Figure 3It is a schematic diagram of another specific embodiment of step 104 in the embodiments of the present invention. In step 104, "monitoring the status code fed back by the IP address" includes the following specific implementations:

[0085] 1045. Reset the preset timer;

[0086] 1046. Monitor the feedback data sent by the IP address and determine whether the feedback data belongs to a status code;

[0087] 1047. When it does not belong to a status code, determine whether the duration of the timer exceeds the preset monitoring duration;

[0088] 1048. When it does not exceed the preset monitoring duration, continue to monitor the feedback data sent by the IP address;

[0089] 1049. When it exceeds the preset monitoring duration, resend the execution data to the IP address corresponding to the instance number.

[0090] In steps 1045-1049, first reset the internal timer to 00:00:00, then start timing and monitor the feedback data returned by the IP address to determine whether the feedback data is the status code corresponding to the executed execution data. When it does not belong to a status code, check whether the timer 00:02:04 exceeds the set monitoring duration 00:05:00. When it does not exceed the monitoring duration, continue to monitor the feedback data sent by the IP address, that is, return to step 1046. When it exceeds the monitoring duration, it is necessary to resend the execution data to the IP address corresponding to the instance number and return to step 1045 to reset the timer.

[0091] 105. When receiving the status code, send the status code to the HTML page.

[0092] In this embodiment, after receiving the status code, the status code is sent to the HTML page, and the HTML page displays the corresponding execution success information or execution failure information based on the status code.

[0093] Specifically, step 105 includes the following specific implementations:

[0094] 1051. Use the WPF framework and use the PostMessageAsString function or the PostWebMessageAsJson function to send the status code to the HTML page.

[0095] In step 1051, the HTML page uses window.chrome.webview.addWebMessageListener to listen for messages from WPF. WPF directly sends a string status code using CoreWebView2.PostWebMessageAsString or sends data in JSON format using CoreWebView2.PostWebMessageAsJson, and finally sends the status code to the HTML page.

[0096] In the embodiment of the present invention, the SDK loading and execution based on WebView2 can dynamically load the SDK and execute the methods therein, while achieving efficient communication between the Web view and the native application, without the need for local redeployment of the relevant environment, effectively reducing the incompatibility during the compilation process. The present invention has the advantages of high flexibility and easy extensibility, is applicable to various scenarios that require dynamic loading and execution of the SDK, does not require all executions at the backend to be on the client side, and solves the problem of the high maintenance cost caused by the difficulty of dynamically loading and executing the current SDK coding in the application.

[0097] Figure 4 FIG. is a schematic structural diagram of an SDK loading and execution device for a Web view provided by an embodiment of the present invention. The SDK loading and execution device 400 for the Web view may vary greatly due to configuration or performance, and may include one or more processors (central processing units, CPUs) 410 (for example, one or more processors) and a memory 420, and one or more storage media 430 (for example, one or more mass storage devices) for storing application programs 433 or data 432. Among them, the memory 420 and the storage media 430 may be transient storage or persistent storage. The program stored in the storage media 430 may include one or more modules (not shown in the figure), and each module may include a series of instruction operations on the SDK loading and execution device 400 for the Web view. Further, the processor 410 may be configured to communicate with the storage media 430 and execute a series of instruction operations in the storage media 430 on the SDK loading and execution device 400 for the Web view.

[0098] The SDK loading and execution device 400 for the Web view may further include one or more power supplies 440, one or more wired or wireless network interfaces 450, one or more input / output interfaces 460, and / or one or more operating systems 431, such as Windows Server, Mac OS X, Unix, Linux, FreeBSD, and so on. Those skilled in the art can understand, Figure 4The SDK loading execution device structure of the shown Web view does not constitute a limitation on the Web view-based SDK loading execution device, and may include more or fewer components than shown, or combine certain components, or have a different component arrangement.

[0099] The present invention also provides a computer-readable storage medium, which may be a non-volatile computer-readable storage medium or a volatile computer-readable storage medium. Instructions are stored in the computer-readable storage medium. When the instructions run on a computer, the computer is caused to execute the steps of the SDK loading execution method of the Web view.

[0100] In the context of the present disclosure, a machine-readable medium may be a tangible medium that can contain or store a program for use by or in connection with an instruction execution system, apparatus, or device. A machine-readable medium may be a machine-readable signal medium or a machine-readable storage medium. A machine-readable medium may include, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, apparatus, or devices, or any suitable combination of the foregoing. More specific examples of a machine-readable storage medium would include an electrical connection based on one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

[0101] Furthermore, although the operations are depicted in a particular order, this should be understood as requiring that such operations be performed in the particular order shown or in sequential order, or that all illustrated operations be performed to achieve the desired result. In certain circumstances, multitasking and parallel processing may be advantageous. Likewise, although several specific implementation details are included in the above discussion, these should not be construed as limiting the scope of the present disclosure. Certain features described in the context of separate embodiments may also be implemented in combination in a single implementation. Conversely, various features described in the context of a single implementation may also be implemented separately or in any suitable subcombination in multiple implementations.

[0102] Although the subject matter has been described in language specific to structural features and / or methodological logical acts, it should be understood that the subject matter defined in the appended claims is not necessarily limited to the specific features or acts described above. Rather, the specific features and acts described above are merely example forms of implementing the claims.

Claims

1. A method for loading and executing a Web view SDK, characterized in that: Includes steps: Receive a user's selection instruction, and load the SDK file corresponding to the selection instruction into the preset memory data; Displaying an HTML page on a Web view, and receiving SDK execution parameters on the HTML page, wherein the SDK execution parameters include: an instance number, an SDK number, and entity parameters; Retrieving the SDK file corresponding to the SDK number in the memory data, and performing execution processing on the entity parameters according to the SDK file corresponding to the SDK number to obtain execution data; Send the execution data to the IP address corresponding to the instance number, and monitor the status code fed back by the IP address; When the status code is received, the status code is sent to the HTML page.

2. The method for loading and executing the SDK of a Web view according to claim 1, characterized in that: The displaying of the HTML page on the Web view and receiving the SDK execution parameter on the HTML page include: Using the WebView2 control to load and display an HTML page, wherein the HTML page includes: a first input box, a second input box, and a third input box; Receive an instance number in the first input box, receive an SDK number in the second input box, and receive entity parameters in the third input box; Pack the instance number, the SDK number, and the entity parameter combination to generate SDK execution parameters in the HTML page; Receive SDK execution parameters in the HTML page.

3. The method for loading and executing the SDK of a Web view according to claim 1, characterized in that: The SDK execution parameters received on the HTML page include: The WPF framework is utilized to receive the SDK execution parameters transmitted by the HTML page based on the WebMessageReceived event.

4. The method for loading and executing the SDK of a Web view according to claim 1, characterized in that: The executing process of the entity parameters according to the SDK file corresponding to the SDK number to obtain the execution data includes: According to the SDK file corresponding to the SDK number, the entity parameters are written into the command function corresponding to the SDK number to generate execution data.

5. The method for loading and executing the SDK of a Web view according to claim 1, characterized in that: The instance number includes: AGV vehicle code, the entity parameters include: motion coordinates, speed settings, the execution processing of the entity parameters according to the SDK file corresponding to the SDK number, and the execution data obtained also includes: Determine whether the command function corresponding to the SDK number is a motion function; When it is a motion function, the motion coordinates and the speed setting are written into the motion function to generate execution data; When it is not a motion function, the command function corresponding to the SDK number is encapsulated to generate execution data.

6. The method for loading and executing the SDK of a Web view according to claim 1, characterized in that: The status code of monitoring the IP address feedback includes: Reset preset timer; Monitoring feedback data sent by the IP address, and determining whether the feedback data belongs to a status code; If it does not belong to the status code, determining whether the duration of the timer exceeds the preset monitoring duration; When the preset monitoring time is not exceeded, the feedback data sent by the IP address continues to be monitored; When the preset monitoring time is exceeded, the execution data is resent to the IP address corresponding to the instance number.

7. The method for loading and executing the SDK of a Web view according to claim 1, characterized in that: The sending of the status code to the HTML page includes: The WPF framework is used to send the status code to the HTML page using the PostMessageAsString function or the PostWebMessageAsJson function.

8. The method for loading and executing the SDK of a Web view according to claim 1, characterized in that: The sending the execution data to the IP address corresponding to the instance number includes: Using the instance number as a key character, query processing is performed in the preset address data table to obtain a query result; When the query result is empty, an alarm message is sent to the HTML page; When the query result is not empty, the query value character in the query result is extracted, the SDK number is used as a key character, and query processing is performed in the query value character to obtain the SDK number value character; The SDK number value character is determined as the IP address corresponding to the instance number.

9. A web view SDK loading and execution device, characterized in that: The SDK loading and executing device of the Web view includes: a memory and at least one processor, the memory stores instructions, and the memory and the at least one processor are interconnected through a line; The at least one processor calls the instruction in the memory to enable the SDK loading and execution device of the Web view to execute the SDK loading and execution method of the Web view according to any one of claims 1 to 8.

10. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the SDK loading and execution method of the Web view according to any one of claims 1 to 8 is implemented.

Images