History

Adam Roben e4e4cb6ec4 Allow embedders to customize the deployment target and base SDK		2013-03-28 15:56:35 -04:00
..
browser	Support undocking the devtools view into its own window	2013-03-27 12:35:01 -04:00
common	Allow overriding MainDelegate::BasicStartupComplete	2013-03-28 12:34:49 -04:00
script	Allow overwriting vendor/download/libchromiumcontent when its version changes	2013-03-25 12:23:37 -04:00
tools/mac	Initial commit	2013-03-13 15:31:24 -04:00
vendor	Update libchromiumcontent	2013-03-26 16:30:32 -04:00
.gitignore	Initial commit	2013-03-13 15:31:24 -04:00
.gitmodules	Initial commit	2013-03-13 15:31:24 -04:00
brightray.gyp	Merge InspectableWebContentsImpl and DevToolsFrontend	2013-03-27 11:20:15 -04:00
brightray.gypi	Allow embedders to customize the deployment target and base SDK	2013-03-28 15:56:35 -04:00
LICENSE	Initial commit	2013-03-13 15:31:24 -04:00
LICENSE-CHROMIUM	Initial commit	2013-03-13 15:31:24 -04:00
README.md	Initial commit	2013-03-13 15:31:24 -04: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

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.