electron/brightray
Adam Roben f7fb6371c2 Increase the open file limit on OS X to 1024
The default (256) is too low for pages that load a lot of resources all at
once. See https://codereview.chromium.org/125151 and bugs like
https://code.google.com/p/chromium/issues/detail?id=14137 and
https://code.google.com/p/chromium/issues/detail?id=151039. The new limit
matches what Chrome itself uses.
2014-01-31 10:43:38 -05:00
..
browser Increase the open file limit on OS X to 1024 2014-01-31 10:43:38 -05:00
common Create a BrowserClient by default 2013-12-03 17:13:40 -05:00
script Enable passing --commit to download script. 2014-01-30 22:01:22 +08:00
tools Use abusolute path when linking to external libraries. Fixes #22. 2013-07-02 15:24:24 +08:00
vendor Update libchromiumcontent for --commit argument of download script. 2014-01-30 21:58:55 +08:00
.gitattributes Ensure consistent line endings in all files 2013-05-16 09:15:05 -04:00
.gitignore WIP: builds (but displys nothing) on Linux 2013-11-07 14:02:35 -06:00
.gitmodules Run cpplint as part of our CI build 2013-11-17 17:38:09 -05:00
brightray.gyp Add flag to disable clang under Linux. 2013-12-31 11:11:46 +00:00
brightray.gypi '-std=gnu++11' is also needed by g++. 2014-01-01 02:29:27 +00: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.