electron/brightray
2017-04-17 16:16:02 +09:00
..
browser base::WrapUnique has changed its API 2017-04-17 16:16:02 +09:00
common Fix cpplint: at least two spaces between code and comments. 2017-03-31 20:59:27 +02:00
script Run cpplint on CI build 2017-03-23 10:08:25 -07:00
tools/mac Link with component build shared libraries 2015-04-02 14:05:43 +08:00
vendor Update libchromiumcontent to Chrome 58 2017-04-17 16:16:02 +09:00
.clang-format Add .clang-format file 2017-03-23 10:08:25 -07:00
.gitattributes Ensure consistent line endings in all files 2013-05-16 09:15:05 -04:00
.gitignore Ignore a couple more files on Windows 2014-06-27 13:45:04 -04:00
.gitmodules Use cpplint from depot_tools 2017-03-23 10:08:25 -07:00
.travis.yml Build through Electron in cibuild and add Travis config 2017-01-12 11:37:52 -08:00
appveyor.yml Initialize submodules in appveyor build 2017-03-24 09:52:27 -07:00
brightray.gyp Add gen/third_party/WebKit to include dirs 2017-04-17 16:16:02 +09:00
brightray.gypi Remove the ENABLE_WEBRTC define 2017-04-17 16:16:02 +09:00
CPPLINT.cfg Format line length to 80 instead of 100 2017-03-23 15:47:30 -07:00
filename_rules.gypi Move filename rules to another file 2015-04-09 10:03:01 +08:00
filenames.gypi Added desktop notifications implementation for Windows 7 (and earlier) 2017-04-05 14:30:15 +02:00
LICENSE Time goes on 2014-07-11 00:39:21 -07:00
LICENSE-CHROMIUM
README.md Link to electron instead of brightray_example 2016-10-03 15:46:09 -07:00

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 isnt all that interesting, since its 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.