mirrors/electron
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
electron/brightray
History
Robo 3b09c370d4 allow client to decide displaying web notifications
2016-01-25 22:09:36 +05:30
..
browser allow client to decide displaying web notifications 2016-01-25 22:09:36 +05:30
common Initialize resource bundle on browser process separately 2016-01-08 12:04:23 +08:00
script Fix build error 2015-11-10 23:26:42 +09:00
tools/mac Link with component build shared libraries 2015-04-02 14:05:43 +08:00
vendor update libchromiumcontent 47.0.2526.110 2016-01-15 22:39:20 +02:00
.gitattributes
.gitignore Ignore a couple more files on Windows 2014-06-27 13:45:04 -04:00
.gitmodules Update URLs for new atom org location 2015-03-17 11:24:10 -07:00
brightray.gyp componenet_updater is not needed 2015-12-30 16:14:36 +08:00
brightray.gypi Initialize resource bundle on browser process separately 2016-01-08 12:04:23 +08:00
filename_rules.gypi Move filename rules to another file 2015-04-09 10:03:01 +08:00
filenames.gypi linux: Adapt to new Notification style 2015-12-25 11:52:19 +08:00
LICENSE Time goes on 2014-07-11 00:39:21 -07:00
LICENSE-CHROMIUM
README.md Update URLs for new atom org location 2015-03-17 11:24:10 -07:00

README.md

Brightray

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

Using it in your app

See brightray_example for a sample 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 (like brightray_example) 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.