TWI488113B - Application Integration Method and Computer Program Based on Windows System Products - Google Patents

Description

Windows-based application integration method and computer program Product

The invention relates to an application integration method, in particular to a window system based application integration method and a computer program product.

In software practice applications, we often face the software we use, which can only be executed by traditional applications (for example, applications developed using the Windows API), but not on the browser; or the program can only be executed. For a specific browser.

For example, some malleable software, such as browsers, are commonly used; plug-in software (Plug-in) can be used to expand the inadequacy of its own functions. For example, Video Camera's web-based management program (Video/Audio Live Streaming) is implemented in the form of plug-in software on the browser. However, the development of such browser plug-in software requires one of the following two sets of mainstream plug-in software standards: 1. ActiveX standard, support Internet Explorer browser; or 2. NPAPI standard, Support for Firefox, Google Chrome Browsers such as Opera and Safari.

In addition, when using such standards for software development, the following problems are often derived:

1. The above two sets of different plug-in software standards cannot be compatible with each other; therefore, it is usually necessary to develop different software projects for different plug-in software standards.

2. Plug-ins compiled by different plug-in software standards are difficult to use by other non-browser other traditional applications.

3. The user interface of the plugin will also vary depending on the browser's support for each plug-in software standard.

In view of the above-mentioned problems extended by the software developed by different plug-in software standards, it is necessary to seek a solution.

Therefore, the object of the present invention is to provide a Windows system-based application integration method, so that the software developed by this method can be executed by both mainstream browsers and traditional applications.

Therefore, the application integration method based on the window system of the present invention is applicable to a window system placed on an electronic device; the window system includes an application program for the user to operate, a script file including a plurality of script materials, and a plurality of A plugin, and an integrated interface that includes multiple initialization programs. The Windows system-based application integration method includes the following steps.

First, the application loads the script file to read one of the script data from the script data, including an initialization program a list and a list of plugins, wherein the list of initializers records at least one of the initializers, the list of plugins recording at least one of the plugins.

Next, the application loads and executes an initialization program recorded in the initialization program list from the integration interface to obtain a globally unique identification component.

Then, the integration interface loads the plug-in recorded in the list of the plug-in according to the global unique identification component; and then, the integration interface matches the loaded plug-in.

Another object of the present invention is to provide a computer program product for storing a Windows-based application integration program, which can be completed after an electronic device loads the program and executes the above-mentioned window system-based application integration method. .

1‧‧‧Windows system

11‧‧‧Application

111‧‧‧User screen

12‧‧‧Script file

121‧‧‧Script data

13‧‧‧Plug

14‧‧‧ integrated interface

141‧‧‧Initialization program

21~27‧‧‧Steps

31~34‧‧‧Steps

Other features and effects of the present invention will be apparent from the following description of the drawings. FIG. 1 is a block diagram illustrating the window system of the application system integration method of the present invention; FIG. 2 is A flow chart illustrating a first embodiment of a window system-based application integration method of the present invention; FIG. 3 is a flow chart illustrating a second embodiment of the window system-based application integration method of the present invention; 4 is a schematic diagram illustrating the aspect of the present invention when executed in a browser Figure 5 is a schematic diagram showing the aspect of the present invention when executed by another browser; and Figure 6 is a schematic view showing the aspect of the present invention when executed in a window program.

Referring to FIG. 1, a preferred embodiment of a Windows system-based application integration method is implemented in a computer program product and executed in a window system 1 mounted on an electronic device. 1 includes an application 11 for user operation, a script file 12 including a plurality of script files 121, a plurality of plug-ins 13, and an integrated interface 14 including a plurality of initialization programs 141.

In the preferred embodiment, the electronic device can be, for example, a personal computer (PC), a laptop (Mobile), a mobile device, a tablet computer, or a personal digital assistant (PDA). The integration interface 14 is a software component developed by Microsoft technology.

The script data 121 includes an initialization program list, a plug-in program list, an identification data matching list, and a window size data. In the preferred embodiment, the initialization program list records at least one of the initialization programs 141, and the plug-in list records at least one of the plug-ins 13. In the preferred embodiment, the plug-ins are binary DLL files developed and compiled by Microsoft technologies, and can be divided into many types according to functions, for example, responsible for the user interface. Layout plugin", "Codec plugin" for video compression/decompression, etc...

It is worth mentioning that, in the preferred embodiment, the application 11 can be implemented by the following two implementations:

First embodiment

Referring to FIG. 1 and FIG. 2, in conjunction with the first embodiment, the application 11 includes a plurality of different browsers and a plurality of different plug-in interfaces. In this first embodiment, the browsers include Firefox, Google Chrome, Opera, Safari, Internet Explorer, and other browsers, and the plug-in interfaces are such that the plug-in 13 can be browsed as described above. A common interface (eg, ActiveX, NPAPI interface) executed in the device; and each of the browsers corresponds to one of the plugin interfaces.

First, in step 21, one of the browsers searches for a tag data from a web page file obtained by the browser. In the first embodiment, the webpage file is taken as an example, and the label information is, for example, label data defined in the <object> and </object> tags in the webpage file.

Next, in step 22, the browser loads the plug-in interfaces corresponding thereto according to the description content of the tag data in the webpage file.

Next, in step 23, the browser loads the script file 12 to read one of the script data 121 from it. In this first embodiment, the script material 121 is a value encoded by a Base64 algorithm and can be JSON (JavaScript Object Notation). format.

Next, in step 24, the browser loads and executes the initialization program 141 recorded in the initialization program list from the integration interface 14 to obtain a globally unique identification component. The global unique identifier includes a plurality of Global Unique Identifiers (GUIDs).

In this first embodiment, reference is made to the following table 1 to describe the environment information established by the initialization program 141 after the execution of the script data 121; wherein the initialization programs 141 perform initialization mainly according to the script data 121. Work, for example, the archive directory, name (for example, the proj_name field in Table 1), version information (for example, the proj_id field in Table 1), etc. required for the establishment of the work project, but the naming and use thereof are not This should be limited to the first embodiment.

Next, in step 25, the integration interface 14 loads the plug-in 13 recorded in the list of the plug-in according to the global unique identification component. .

In this first embodiment, the global unique identifiers are used to separately record the required plug-ins 13 in the script data 121. For example, refer to the following table 2, which is used to describe the list of plug-ins in the script material 121, wherein the global unique identifiers are the strings consisting of 22 hexadecimal values in Table 2; Each of the strings uniquely corresponds to a single plug-in program 13, and it can be seen from Table 2 that the plug-in program 13 required for the work project is four, but is not limited thereto, and the number and type of the plug-in programs 13 can be Work items have different attributes and have increased or decreased.

Next, in step 26, the integration interface 14 matches the loaded plug-in 13 . The loaded plug-in 13 includes a plurality of provider plug-ins (Providers) and a plurality of consumer plug-ins (Consumers), and the identification data matching list has a plurality of descriptions of the provider plug-ins and the The matching data of the corresponding relationship of the demander plug-in.

In this first embodiment, the provider plug-ins respectively have a unique identification data, and the demander plug-ins respectively have A unique identification material. Refer to Table 3 below to illustrate how the provider plug-in can establish a matching relationship with the demander plug-in: First, one of the demand plug-ins provides the service interface (Service ID) string to the integration interface 14. Service request; then, the integration interface 14 queries the service provider string to query whether all loaded provider plug-ins provide services corresponding to the service identification string; when the identification data of one of the provider plug-ins is When the identification data of one of the demander plug-ins is exactly the same (ie, the provider plug-in program and the demander plug-in provide the same service at this time), the integration interface 14 is based on the same The matching data matches the provider plug-in program with the same identification data to the demander plug-in program, and then the integration interface 14 thus connects the connection between the provider plug-in program and the demander plug-in program. The relationship, that is, the "provider", "consumer", and "services" described in the brackets "{}" in Table 3 indicates that the matching of the same service has been established. The suppliers, who demand plugin.

Further, in step 27, the browser generates a user screen 111 (see FIG. 4 or FIG. 5) for the electronic device to display based on the window size data. For example, as shown in FIG. 4, a schematic diagram of executing a webcam management plug-in on the Google Chrome browser according to the present invention; and as shown in FIG. 5, the present invention is executed on the Internet Explorer browser. A schematic diagram of performing a webcam management plug-in program is not limited to the example of the webcam management plug-in disclosed in the present case.

Second embodiment

Referring to FIG. 1 and FIG. 3, in conjunction with the second embodiment, the application 11 is a window program generated based on an application interface. In this second embodiment, the interface standard of the window program is mainly based on the operating platform preloaded by the electronic device. For example, it is assumed that the electronic device is loaded. For a computer or notebook computer of the Windows series of Windows 1 system, the Windows program may use Windows API, Windows Forms, or WPF (Windows Presentation Foundation) window program standard, but is not limited thereto. The second embodiment is similar to the first embodiment. The main difference is that step 21 to step 23 in the first embodiment are not required to be performed in the second embodiment.

The operations performed in steps 31-34 are similar to the steps 24-27, so detailed implementation details are not described herein.

First, in step 31, the window program loads and executes the initialization program 141 recorded in the initialization program list from the integration interface 14 to obtain a globally unique identification component. The global unique identification component includes a plurality of global unique identifiers.

Next, in step 32, the integration interface 14 loads the plug-in 13 recorded in the list of plug-ins according to the globally unique identification component.

Next, in step 33, the integration interface 14 matches the loaded plug-in 13 . The loaded plug-in program 13 includes a plurality of provider plug-ins and a plurality of demander plug-ins, and the identification data matching list has a plurality of descriptions of the provider plug-ins and the plug-ins corresponding to the demanders. Matching information for the relationship.

Then, in step 34, the window program generates a user screen 111 (see FIG. 6) for the electronic device to display based on the window size data. For example, as shown in FIG. 6, in order to illustrate the webcam management plug-in developed by the Windows API technology of the present invention, and to use a window program The schematic diagram of the implementation, but not limited to the example of the webcam management plug-in disclosed in this case.

In summary, since the plug-in programs 13 are software component files using Microsoft development technology and the sub-file name is DLL; therefore, under the above architecture, the following advantages are achieved: (a) Simplified development difficulty: in the plug-in program 13 In terms of development, it is not necessary to understand the standards and implementation of browser plug-ins, and it is not necessary to develop different software projects for different browser plug-in software. (b) Cross-browser and traditional applications to enhance reusability: the same plug-in 13 suite can be executed in different browsers and traditional applications; (c) easy to install: since the plug-in 13 is Windows Standard installer, so it only needs to be installed once, no certificate is required, and there is no need to install different programs for different ActiveX, NPAPI or traditional applications. (d) Consistent and unified user interface: When the plug-in is executed in a browser or a window program, a consistent user interface is provided to make the user interface different from the browser and window program support standards (for example, HTML5) is different. (e) Protect the original code: These plug-ins 13 are compiled binary DLL files, unlike the plaintext source code description of HTML and JavaScript, which will cause the original code to flow out. (f) Support initialization script: The window system can flexibly perform execution environment setting according to script data (using JSON or XML), load plug-in program 13 and serial plug-in program relationship, etc., so that the object of the present invention can be achieved. Therefore, each browser needs to handle differently according to the difference of the respective plug-in software standards.

However, the above is only the preferred embodiment of the present invention, and the scope of the present invention cannot be limited thereto. The simple equivalent changes and modifications made by the patent scope and the contents of the patent specification are still within the scope of the invention.

1‧‧‧Windows system

11‧‧‧Application

12‧‧‧Script file

121‧‧‧Script data

13‧‧‧Plug

14‧‧‧ integrated interface

141‧‧‧Initialization program

Claims (10)

A window system-based application integration method for a window system placed on an electronic device, the window system includes an application program for a user operation, a script file including a plurality of script materials, and a plurality of plug-ins And an integrated interface including a plurality of initialization programs, the window system-based application integration method comprising: (A) the application loading the script file to read one of the script materials from the script The data includes an initialization program list and a list of external programs, wherein the initialization program list records at least one of the initialization programs, the list of external programs records at least one of the external programs; (B) the application is integrated from the The interface loads and executes an initialization program recorded in the initialization program list to obtain a globally unique identification component; (C) the integration interface loads the plug-in recorded in the list of the plug-in according to the global unique identification component; and (D) The integration interface matches the loaded plugins. The method for integrating a Windows-based application according to claim 1, wherein in the step (D), the loaded plug-ins include a plurality of provider plug-ins and a plurality of demander plug-ins, the providers The plug-ins respectively have a unique identification data, and the demander plug-ins respectively have a unique identification data, and the identification data of one of the provider plug-ins and the identification data of one of the demand plug-ins When identical, the integration interface will identify the same data. The provider plugin matches the consumer plugin. The window system-based application integration method of claim 2, wherein the script data further includes an identification data matching list, the identification data matching list having a plurality of descriptions of the provider plug-ins and the demander plug-ins Corresponding data of the matching relationship, and in step (D), the integration interface further matches the provider plug-in program with the same identification data with the demander plug-in according to the matching data. The window system-based application integration method of claim 2, wherein the application is a window program generated based on an application interface. The window system-based application integration method of claim 2, wherein the application comprises a plurality of different browsers and a plurality of different plug-in interfaces, each browser corresponding to one of the plug-in interfaces. The window system-based application integration method according to claim 5, further comprising a step (E) before the step (A): (E) one of the browsers is obtained from a webpage file obtained by the browser Search for a tag data. The window system-based application integration method according to claim 6, further comprising a step (F) between the step (E) and the step (A): (F) the browser loads the tag data according to the tag Corresponding to these plugin interfaces. The window system-based application integration method of claim 7, wherein in the step (A), the plugin interface loads the script file to The script data is read, wherein the script data is a value encoded by a Base64 algorithm. The window system-based application integration method according to claim 1, further comprising a step (G) after the step (D), wherein the script data further includes a window size data: (G) the application according to the The window size data produces a user screen for display by the electronic device. A computer program product that stores a Windows-based application integration program, and when an electronic device loads the program and executes it, the functions described in any one of the items 1 to 9 can be completed.