bigbluebutton-Github/bbb-screenshare/webrtc-extensions/chrome
2017-05-03 16:59:03 +00:00
..
background.js Extension allows source override 2017-05-03 16:40:21 +00:00
logo-16x16.png Initial extension push 2017-04-20 17:36:52 +00:00
logo-48x48.png Initial extension push 2017-04-20 17:36:52 +00:00
logo-128x128.png Initial extension push 2017-04-20 17:36:52 +00:00
manifest.json Remove invalid characters from manifest 2017-05-03 16:59:03 +00:00
README.md Initial extension push 2017-04-20 17:36:52 +00:00

BigBlueButton Screen Sharing Extension for Chrome

Customizing your own extension

  1. Fork, clone, or download this repository

  2. Modify the manifest.json file. Add the domain of your server to externally_connectable.matches. For a public/distributed deployment you may want to change the icons, homepage_url, name, and author. For an extension on the Google Web Store you will have to increment the version with each release.

For more information, see the Chrome extension manifest documentation.

You have 3 options for using the extension

  • loading your extension locally
  • uploading your extension to the Google Web Store
  • packaging your extension locally and manually distributing

Loading your extension locally

Open chrome://extensions and drag the extension's directory onto the page, or click 'Load unpacked extension...' and select the extension directory. If these options do not show up you may need to check Developer mode. For more information see Chrome's documentation on loading unpacked extensions

After loaded into Google Chrome you will see the extension's unique Hash Id which is what allows an application to communicate with the extension and check the extension's status.

Uploading your extension to the Google Web Store

Publishing in the Chrome Web Store

Packaging your extension locally and manually distributing

https://developer.chrome.com/extensions/packaging

In chrome://extensions select "Pack extension". This will bundle your extension into a .CRX file. When you initially package your extension Google will give you a private key so you can retain the same hash after updates. You can then distribute your extension manually to your users.