Implementing the Chrome extension to start the local process-supplemental

implementing the Chrome extension to start the local process-supplementalTags: Chrome extension launches local program Access local disk2014-10-17 11:42 6753 people read review (+) collection report Classification:Chrome Plugin

Copyright NOTICE: This article for Bo Master original article, without Bo Master permission not reproduced.

Examples mainly include the following sections Com.google.chrome.demo-win.jsonnative_cmd.batmanifest.jsonpopup.htmlpopup.js Feature Description:Implementation of an extension, the user click on a button will start the local Notepad program (also can write for their own program, where the example starts Notepad, similar to the function of thunder extension) Implementation Overview:Call start Notepad.exe by starting a local batch process Expansion:You can change the batch to a program you write, and then implement access to local disk data or something else in that program.

Program source code in the network disk (Chrome plugin directory of Demo.rar):

Http://pan.baidu.com/s/1hcVuQ

：

Part of the code:

Manifest.json

[JavaScript]View PlainCopy  

2. {
4. //Extension ID:NDNIGONBFJHPJLCABMADMKPDCFOMENLP
6. "Manifest_version": 2,
10. "name": "Invoke Native application",
12. " description": "Example",
14. "version": "1.0",
18. "Browser_action": {
20. " Default_icon": "Icon.png",
22. "Default_popup": "popup.html" //defines the page that appears after clicking Expand
24. },
26. "Permissions": [
28. "nativemessaging" //define permissions and need to communicate with local applications
30. ]
32. }

Popup.js [JavaScript]View PlainCopy 

2. function Updateresult (obj, state) {
4. document.getElementById (obj). InnerHTML = State;
6. }
8. function Invoke () {
10. //hostname The name of the item on the registry
12. var hostName = "Com.google.chrome.demo";
14. //Start the local application
16. var port = chrome.runtime.connectNative (HostName);
18. Updateresult ("Result1", "invoke..");
20. }
24. Adding Listener events for Button1
26. Document.addeventlistener (' domcontentloaded ', function () {
28. Document.queryselector (' #button1 '). AddEventListener (
30. ' click ', Invoke);
32. });
36. Com.google.chrome.demo-win.json
40. {
42. "name": "Com.google.chrome.demo",
44. " description": "Chrome Native Messaging API Example Host",
46. //path must be an absolute path, pointing to the program to start
48. " path": "d:\\work\\chrome plugin\\native Messaging example\\demo\\native_cmd.bat",
50. "type": "Stdio",
52. "Allowed_origins": [
54. "chrome-extension://niekdnkneilndiimkikogmplndpcfknp/"
56. ]
58. }

Com.google.chrome.demo-win.json [JavaScript]View PlainCopy 

2. {
4. "name": "Com.google.chrome.demo",
6. " description": "Chrome Native Messaging API Example Host",
8. //path must be an absolute path, pointing to the program to start
10. " path": "d:\\work\\chrome plugin\\native Messaging example\\demo\\native_cmd.bat",
12. "type": "Stdio",
14. "Allowed_origins": [
16. "chrome-extension://niekdnkneilndiimkikogmplndpcfknp/"
18. ]
20. }

Native_cmd.bat notepad.exe The value of my registry export (the location to be noted under Heky: ):Windows Registry Editor Version 5.00

[Hkey_current_user\software\google\chrome\nativemessaginghosts\com.google.chrome.demo]
@= "D:\\work\\chrome plugin\\native Messaging Example\\demo\\com.google.chrome.demo-win.json"

======================2016.2.15 Supplement =============================================

Before I have a private information about the problem can not be started, here is my negligence of a very important step, is the authority problem.

The chrome-extension under Allowed_origins represents the allowed plugins. This string of letters is important to match the ID you installed. as follows, this plugin is Hnaekmhaniojodkaageacnjfldljhiek, then the ID must be consistent with respect to the installation.

[JavaScript]View PlainCopy 

1. "Allowed_origins": [
2. "chrome-extension://hnaekmhaniojodkaageacnjfldljhiek/"
3. ]

This involves the problem of plugin packaging, and incidentally.

as follows, select Package Extender, where the root directory is the plug-in location, which will generate two files, one PEM key file, and the other for the CRX installer. After installation can see the plug-in ID, and then copy down to fill in, and then remove the CRX installer, re-packaged once, but this time the following private key file to choose just generated. This will correspond to the ID.

The origin of complementary implementations:

Here for the time when I was asked to write a Chrome plugin task, when the first time to contact the plug-in, the solution is to collect data first, and then determine the use of native messaging way to achieve, to see the relevant documents and the official demo, and then study the Thunderbolt plug-ins, See how the Thunder is called (not research source, is to see how related, such as the registry), this process does not take much time, a week or so time.

Implementing the Chrome extension to start the local process-supplemental