History

Adam Roben e1b5e5e1bf Store the disk cache in an app-specific location We deduce the name of the application from the CFBundleName of the .app bundle and use a path based on that. Similar logic should be implementable for other platforms. Fixes #3.		2013-03-13 16:45:00 -04:00
..
browser	Store the disk cache in an app-specific location	2013-03-13 16:45:00 -04:00
common	Store the disk cache in an app-specific location	2013-03-13 16:45:00 -04:00
script	Initial commit	2013-03-13 15:31:24 -04:00
tools/mac	Initial commit	2013-03-13 15:31:24 -04:00
vendor	Initial commit	2013-03-13 15:31:24 -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	Store the disk cache in an app-specific location	2013-03-13 16:45:00 -04:00
brightray.gypi	Initial commit	2013-03-13 15:31:24 -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.