react-native/Libraries/Device/RCTDeviceEventEmitter.js

/**
 * Copyright (c) 2015-present, Facebook, Inc.
 * All rights reserved.
 *
 * This source code is licensed under the BSD-style license found in the
 * LICENSE file in the root directory of this source tree. An additional grant
 * of patent rights can be found in the PATENTS file in the same directory.
 *
 * @providesModule RCTDeviceEventEmitter
 * @flow
 */
'use strict';

var EventEmitter = require('EventEmitter');
var BatchedBridge = require('BatchedBridge');

var RCTDeviceEventEmitter = new EventEmitter();

BatchedBridge.registerCallableModule(
  'RCTDeviceEventEmitter',
  RCTDeviceEventEmitter
);

module.exports = RCTDeviceEventEmitter;
Initial commit 2015-01-29 17:10:49 -08:00			`/**`
Second Updates from Mon 23 Mar - [ReactNative] Use deprecated ix in TabBarExample \| Amjad Masad - [ReactNative] Expanded license on obj-c files \| Christopher Chedeau - [ReactNative] Expanded license on js files \| Christopher Chedeau - [ReactNative] Fix React Devtools integration \| Alex Kotliarskyi - [Text] Account for font leading so descenders are not clipped \| James Ide - [ReactNative] Expanded license on js packager files \| Christopher Chedeau - more UIExplorer flow \| Basil Hosmer - [react-packager] Pick up package changes while running \| Amjad Masad - Added a graph view and a ReactNative metric that displays current queue and execution time for the JS thread. \| Bryce Redd - [ReactNative] Add NativeModules and DeviceEventEmitter to react-native exports \| Alex Kotliarskyi 2015-03-23 15:07:33 -07:00			`* Copyright (c) 2015-present, Facebook, Inc.`
			`* All rights reserved.`
			`*`
			`* This source code is licensed under the BSD-style license found in the`
			`* LICENSE file in the root directory of this source tree. An additional grant`
			`* of patent rights can be found in the PATENTS file in the same directory.`
Initial commit 2015-01-29 17:10:49 -08:00			`*`
			`* @providesModule RCTDeviceEventEmitter`
Second Updates from Wed 25 Mar - [MAdMan][Android] Make things look more Androidy \| Philipp von Weitershausen - flowified Libraries from Avik \| Basil Hosmer - flowify some Libraries \| Basil Hosmer - [ReactKit] Add shake development menu \| Alex Kotliarskyi - [ReactNative] Add debugger and change SampleApp files structure \| Alex Kotliarskyi - Flowify ReactIOSEventEmitter \| Marshall Roch - [react_native] JS files from D1941151: Allow fontWeight to be 100,200,...,900 \| Krzysztof Magiera 2015-03-25 15:36:50 -07:00			`* @flow`
Initial commit 2015-01-29 17:10:49 -08:00			`*/`
			`'use strict';`

			`var EventEmitter = require('EventEmitter');`
Decouple Module System from Native Calls Summary: The JavaScript ecosystem doesn't have the notion of a built-in native module loader. Even Node is decoupled from its module loader. The module loader system is just JS that runs on top of the global `process` object which has all the built-in goodies. Additionally there is no such thing as a global require. That is something unique to our providesModule system. In other module systems such as node, every require is contextual. Even registered npm names are localized by version. The only global namespace that is accessible to the host environment is the global object. Normally module systems attaches itself onto the hooks provided by the host environment on the global object. Currently, we have two forms of dispatch that reaches directly into the module system. executeJSCall which reaches directly into require. Everything now calls through the BatchedBridge module (except one RCTLog edge case that I will fix). I propose that the executors calls directly onto `BatchedBridge` through an instance on the global so that everything is guaranteed to go through it. It becomes the main communication hub. I also propose that we drop the dynamic requires inside of MessageQueue/BatchBridge and instead have the modules register themselves with the bridge. executeJSCall was originally modeled after the XHP equivalent. The XHP equivalent was designed that way because the act of doing the call was the thing that defined a dependency on the module from the page. However, that is not how React Native works. The JS side is driving the dependencies by virtue of requiring new modules and frameworks and the existence of dependencies is driven by the JS side, so this design doesn't make as much sense. The main driver for this is to be able to introduce a new module system like Prepack's module system. However, it also unlocks the possibility to do dead module elimination even in our current module system. It is currently not possible because we don't know which module might be called from native. Since the module system now becomes decoupled we could publish all our providesModule modules as npm/CommonJS modules using a rewrite script. That's what React Core does. That way people could use any CommonJS bundler such as Webpack, Closure Compiler, Rollup or some new innovation to create a JS bundle. This diff expands the executeJSCalls to the BatchedBridge's three individual pieces to make them first class instead of being dynamic. This removes one layer of abstraction. Hopefully we can also remove more of the things that register themselves with the BatchedBridge (various EventEmitters) and instead have everything go through the public protocol. ReactMethod/RCT_EXPORT_METHOD. public Reviewed By: vjeux Differential Revision: D2717535 fb-gh-sync-id: 70114f05483124f5ac5c4570422bb91a60a727f6 2015-12-08 15:57:34 -08:00			`var BatchedBridge = require('BatchedBridge');`
Initial commit 2015-01-29 17:10:49 -08:00
			`var RCTDeviceEventEmitter = new EventEmitter();`

Decouple Module System from Native Calls Summary: The JavaScript ecosystem doesn't have the notion of a built-in native module loader. Even Node is decoupled from its module loader. The module loader system is just JS that runs on top of the global `process` object which has all the built-in goodies. Additionally there is no such thing as a global require. That is something unique to our providesModule system. In other module systems such as node, every require is contextual. Even registered npm names are localized by version. The only global namespace that is accessible to the host environment is the global object. Normally module systems attaches itself onto the hooks provided by the host environment on the global object. Currently, we have two forms of dispatch that reaches directly into the module system. executeJSCall which reaches directly into require. Everything now calls through the BatchedBridge module (except one RCTLog edge case that I will fix). I propose that the executors calls directly onto `BatchedBridge` through an instance on the global so that everything is guaranteed to go through it. It becomes the main communication hub. I also propose that we drop the dynamic requires inside of MessageQueue/BatchBridge and instead have the modules register themselves with the bridge. executeJSCall was originally modeled after the XHP equivalent. The XHP equivalent was designed that way because the act of doing the call was the thing that defined a dependency on the module from the page. However, that is not how React Native works. The JS side is driving the dependencies by virtue of requiring new modules and frameworks and the existence of dependencies is driven by the JS side, so this design doesn't make as much sense. The main driver for this is to be able to introduce a new module system like Prepack's module system. However, it also unlocks the possibility to do dead module elimination even in our current module system. It is currently not possible because we don't know which module might be called from native. Since the module system now becomes decoupled we could publish all our providesModule modules as npm/CommonJS modules using a rewrite script. That's what React Core does. That way people could use any CommonJS bundler such as Webpack, Closure Compiler, Rollup or some new innovation to create a JS bundle. This diff expands the executeJSCalls to the BatchedBridge's three individual pieces to make them first class instead of being dynamic. This removes one layer of abstraction. Hopefully we can also remove more of the things that register themselves with the BatchedBridge (various EventEmitters) and instead have everything go through the public protocol. ReactMethod/RCT_EXPORT_METHOD. public Reviewed By: vjeux Differential Revision: D2717535 fb-gh-sync-id: 70114f05483124f5ac5c4570422bb91a60a727f6 2015-12-08 15:57:34 -08:00			`BatchedBridge.registerCallableModule(`
			`'RCTDeviceEventEmitter',`
			`RCTDeviceEventEmitter`
			`);`

Initial commit 2015-01-29 17:10:49 -08:00			`module.exports = RCTDeviceEventEmitter;`