All Projects → electron-archive → Brightray

electron-archive / Brightray

Licence: other
A thin shim over Chromium’s Content module, no longer active, the source code has been directly imported into Electron in https://github.com/electron/electron/pull/9423

Projects that are alternatives of or similar to Brightray

Chrome Protocol Proxy
Chrome DevTools Protocol Proxy - intelligent proxy for debugging purposes
Stars: ✭ 94 (-57.27%)
Mutual labels:  chrome, chromium
Pychromeless
Python Lambda Chrome Automation (naming pending)
Stars: ✭ 219 (-0.45%)
Mutual labels:  chrome, chromium
Kdeconnect Chrome Extension
A browser extension to send pages and content from your browser to connected KDE Connect devices.
Stars: ✭ 124 (-43.64%)
Mutual labels:  chrome, chromium
Uget Chrome Wrapper
Moved to https://github.com/ugetdm/uget-integrator and https://github.com/ugetdm/uget-extension
Stars: ✭ 74 (-66.36%)
Mutual labels:  chrome, chromium
Sponsorblock
Skip YouTube video sponsors (browser extension)
Stars: ✭ 3,627 (+1548.64%)
Mutual labels:  chrome, chromium
Chrome Pak Customizer
a simple command-line tool to pack and unpack pak files in chrome or chromium-based browser
Stars: ✭ 79 (-64.09%)
Mutual labels:  chrome, chromium
Surfingkeys Conf
A SurfingKeys configuration which adds 130+ key mappings for 20+ sites & OmniBar search suggestions for 50+ sites
Stars: ✭ 137 (-37.73%)
Mutual labels:  chrome, chromium
San Devtools
Browser developer tools extension for debugging San.
Stars: ✭ 51 (-76.82%)
Mutual labels:  chrome, chromium
Chrome Extensions Reloader
A chrome extension for reloading unpacked extensions
Stars: ✭ 154 (-30%)
Mutual labels:  chrome, chromium
Puppeteer Sharp
Headless Chrome .NET API
Stars: ✭ 2,122 (+864.55%)
Mutual labels:  chrome, chromium
Html2image
A package acting as a wrapper around the headless mode of existing web browsers to generate images from URLs and from HTML+CSS strings or files.
Stars: ✭ 69 (-68.64%)
Mutual labels:  chrome, chromium
Chromium Ipc Sniffer
A tool to capture communication between Chromium processes on Windows
Stars: ✭ 197 (-10.45%)
Mutual labels:  chrome, chromium
Puppeteer Docs Zh Cn
Google Puppeteer 文档的中文版本 , 目标版本 1.9.0, 翻译中...
Stars: ✭ 61 (-72.27%)
Mutual labels:  chrome, chromium
Chrome Export Passwords
Show all your chromium passwords in format ready to import in other browser like FireFox
Stars: ✭ 80 (-63.64%)
Mutual labels:  chrome, chromium
Mue
Fast, open and free-to-use new tab page for modern browsers
Stars: ✭ 56 (-74.55%)
Mutual labels:  chrome, chromium
Phpchrometopdf
A slim PHP wrapper around google-chrome to convert url to pdf or to take screenshots , easy to use and clean OOP interface
Stars: ✭ 127 (-42.27%)
Mutual labels:  chrome, chromium
Web Media Controller
Allows controlling media player on different sites with Media Player widget on your desktop
Stars: ✭ 36 (-83.64%)
Mutual labels:  chrome, chromium
Ferrum
Headless Chrome Ruby API
Stars: ✭ 1,009 (+358.64%)
Mutual labels:  chrome, chromium
Chromecontroller
Comprehensive wrapper and execution manager for the Chrome browser using the Chrome Debugging Protocol.
Stars: ✭ 143 (-35%)
Mutual labels:  chrome, chromium
Phpdesktop
Develop desktop GUI applications using PHP, HTML5, JavaScript and SQLite
Stars: ✭ 2,101 (+855%)
Mutual labels:  chrome, chromium

Brightray

Brightray is a static library that makes libchromiumcontent easier to use in applications.

Using it in your app

See electron for example of an application written using Brightray.

Development

Prerequisites

  • Python 2.7
  • Linux:
    • Clang 3.0
  • Mac:
    • Xcode
  • Windows:
    • Visual Studio 2010 SP1

One-time setup

You must previously have built and uploaded libchromiumcontent using its script/upload script.

$ script/bootstrap http://base.url.com/used/by/script/upload

Building

$ script/build

Building Brightray on its own isn’t all that interesting, since it’s just a static library. Building it into an application is the only way to test it.

License

In general, everything is covered by the LICENSE file. Some files specify at the top that they are covered by the LICENSE-CHROMIUM file instead.

Note that the project description data, including the texts, logos, images, and/or trademarks, for each open source project belongs to its rightful owner. If you wish to add or remove any projects, please contact us at [email protected].