electron/brightray
Cheng Zhao 2cd6dd791e Setup devtools in the correct phase.
* RegisterDevToolsClientHostFor should be called right after the agent_host and
  the frontend host are created.
* SetupDevToolsFrontendClient should be called before the devtools window is
  going to start navigation.
2013-10-11 07:17:03 -04:00
..
browser Setup devtools in the correct phase. 2013-10-11 07:17:03 -04:00
common Update #includes for moves of string-related headers 2013-10-07 16:31:57 -04:00
script Include gyp as a submodule 2013-08-23 07:48:37 -04:00
tools Use abusolute path when linking to external libraries. Fixes #22. 2013-07-02 15:24:24 +08:00
vendor Update libchromiumcontent to use Xcode's clang 2013-10-09 12:58:36 -04:00
.gitattributes Ensure consistent line endings in all files 2013-05-16 09:15:05 -04:00
.gitignore Beef up .gitignore 2013-05-22 13:54:07 -04:00
.gitmodules Include gyp as a submodule 2013-08-23 07:48:37 -04:00
brightray.gyp Use the "chrome-devtools://" scheme to open devtools. 2013-10-10 16:56:52 -04:00
brightray.gypi Compile as C++11 on Linux 2013-08-14 08:14:54 -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

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 isnt all that interesting, since its 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.