History

Cheng Zhao 1722532e6d No need to remember dock state. All devtools states are remembered by devtools itself now.		2014-07-09 10:24:10 +08:00
..
browser	No need to remember dock state.	2014-07-09 10:24:10 +08:00
common	Update for move of string conversion functions into base::	2014-06-27 14:02:44 -04:00
script	Make sure our copy of gyp is used	2014-07-07 14:42:02 -04:00
tools	Use abusolute path when linking to external libraries. Fixes #22 .	2013-07-02 15:24:24 +08:00
vendor	Update libchromiumcontent for better Chrome 35 support	2014-07-07 12:27:38 -04:00
.gitattributes	Ensure consistent line endings in all files	2013-05-16 09:15:05 -04:00
.gitignore	Ignore a couple more files on Windows	2014-06-27 13:45:04 -04:00
.gitmodules	Run cpplint as part of our CI build	2013-11-17 17:38:09 -05:00
brightray.gyp	Place DevTools WebContents underneath inspected WebContents.	2014-07-09 10:24:10 +08:00
brightray.gypi	Link against chromiumviews	2014-07-07 13:53:02 -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	Include gyp as a submodule	2013-08-23 07:48:37 -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

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.

README.md Unescape Escape