History

Adam Roben 6908eecd0c Allow embedders to specify extra .pak files		2013-04-26 11:04:51 -04:00
..
browser	Fix DCHECK() assertion in BrowserClient	2013-04-24 10:54:53 -04:00
common	Allow embedders to specify extra .pak files	2013-04-26 11:04:51 -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 to latest libchromiumcontent	2013-04-24 15:56:43 -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	Include the application's version number in the user agent string	2013-04-08 12:41:30 -04:00
brightray.gypi	Bump the base SDK and deployment target to 10.8	2013-03-28 17:50:07 -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.