History

Adam Roben b2a79856ef Add InspectableWebContents This class can be used to create a content::WebContents that can be inspected by the Chrome Dev Tools. This requires embedding applications to copy content_shell.pak into their resource bundle. Right now the dev tools are always docked to the bottom of the view; we don't yet support undocking or changing the docked side. Fixes #1.		2013-03-14 09:05:42 -04:00
..
browser	Add InspectableWebContents	2013-03-14 09:05:42 -04:00
common	Add InspectableWebContents	2013-03-14 09:05:42 -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	Add InspectableWebContents	2013-03-14 09:05:42 -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.