mirrors/electron
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions
electron/brightray
History
Milan Burda 8f5463faab Simplify ToastEventHandler using WRL::RuntimeClass, which implements the IUnknown interface
2015-11-09 20:47:18 +01:00
..
browser Simplify ToastEventHandler using WRL::RuntimeClass, which implements the IUnknown interface 2015-11-09 20:47:18 +01:00
common Fix API changes in DevToolsManagerDelegate. 2015-08-11 09:49:57 +08:00
script Update libchromiumcontent for filenames.gypi fix 2015-11-09 18:19:32 +08:00
tools/mac Link with component build shared libraries 2015-04-02 14:05:43 +08:00
vendor Update libchromiumcontent for filenames.gypi fix 2015-11-09 18:19:32 +08: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 Update URLs for new atom org location 2015-03-17 11:24:10 -07:00
brightray.gyp Merge pull request #161 from atom/windows-notifications-lib 2015-11-09 22:49:49 +08:00
brightray.gypi Add option to build local libchromiumcontent 2015-11-08 17:08:42 +09:00
filename_rules.gypi Move filename rules to another file 2015-04-09 10:03:01 +08:00
filenames.gypi Windows Toasts: Enable Basic Notifications 2015-11-09 12:00:21 +01:00
LICENSE Time goes on 2014-07-11 00:39:21 -07:00
LICENSE-CHROMIUM Initial commit 2013-03-13 15:31:24 -04:00
README.md Update URLs for new atom org location 2015-03-17 11:24:10 -07: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.