jiti-meet/react/features/app/functions.native.js

/* @flow */
import { NativeModules } from 'react-native';

export * from './getRouteToRender';

/**
 * Returns application name.
 *
 * @returns {string} The application name.
 */
export function getName() {
    return NativeModules.AppInfo.name;
}
Simplify route navigation I see it as the first step in simplifying the route navigate of the JavaScript app by removing BlankWelcomePage from _getRouteToRender. From a faraway point of view, the app is at the route at which it is not in a conference. Historically, the route was known as the Welcome page. But mobile complicated the route by saying that actually it may not want to see the room name input and join button. Additionally, I renamed BlankWelcomePage to BlankPage because I don't think of it as a WelcomePage alternative but rather as a more generic BlankPage which may be utilized elsewhere in the future. I plan for the next steps to: * Merge Entryway, _interceptComponent, and _getRouteToRender in one React Component rendered by AbstractApp so that the whole logic is in one file; * Get rid of RouteRegistry and routes. 2017-08-22 17:28:31 +00:00			`/* @flow */`
Adds application name to the initJitsiConference options. 2017-10-13 20:34:27 +00:00			`import { NativeModules } from 'react-native';`
Simplify route navigation I see it as the first step in simplifying the route navigate of the JavaScript app by removing BlankWelcomePage from _getRouteToRender. From a faraway point of view, the app is at the route at which it is not in a conference. Historically, the route was known as the Welcome page. But mobile complicated the route by saying that actually it may not want to see the room name input and join button. Additionally, I renamed BlankWelcomePage to BlankPage because I don't think of it as a WelcomePage alternative but rather as a more generic BlankPage which may be utilized elsewhere in the future. I plan for the next steps to: * Merge Entryway, _interceptComponent, and _getRouteToRender in one React Component rendered by AbstractApp so that the whole logic is in one file; * Get rid of RouteRegistry and routes. 2017-08-22 17:28:31 +00:00
Adds application name to the initJitsiConference options. 2017-10-13 20:34:27 +00:00			`export * from './getRouteToRender';`
Import jitsi/jitsi-meet-react#2f23d98 As an intermediate step on the path to merging jitsi-meet and jitsi-meet-react, import the whole source code of jitsi-meet-react as it stands at https://github.com/jitsi/jitsi-meet-react/commit/2f23d984245324e79156eeec9e447667b3c76d33 i.e. the lastest master at the time of this import. No modifications are applied to the imported source code in order to preserve a complete snapshot of it in the repository of jitsi-meet and, thus, facilitate comparison later on. Consequently, the source code of jitsi-meet and/or jitsi-meet-react may not work. For example, jitsi-meet's jshint may be unable to parse jitsi-meet-react's source code. 2016-10-05 14:36:59 +00:00
			`/**`
Adds application name to the initJitsiConference options. 2017-10-13 20:34:27 +00:00			`* Returns application name.`
Import jitsi/jitsi-meet-react#2f23d98 As an intermediate step on the path to merging jitsi-meet and jitsi-meet-react, import the whole source code of jitsi-meet-react as it stands at https://github.com/jitsi/jitsi-meet-react/commit/2f23d984245324e79156eeec9e447667b3c76d33 i.e. the lastest master at the time of this import. No modifications are applied to the imported source code in order to preserve a complete snapshot of it in the repository of jitsi-meet and, thus, facilitate comparison later on. Consequently, the source code of jitsi-meet and/or jitsi-meet-react may not work. For example, jitsi-meet's jshint may be unable to parse jitsi-meet-react's source code. 2016-10-05 14:36:59 +00:00			`*`
Adds application name to the initJitsiConference options. 2017-10-13 20:34:27 +00:00			`* @returns {string} The application name.`
Import jitsi/jitsi-meet-react#2f23d98 As an intermediate step on the path to merging jitsi-meet and jitsi-meet-react, import the whole source code of jitsi-meet-react as it stands at https://github.com/jitsi/jitsi-meet-react/commit/2f23d984245324e79156eeec9e447667b3c76d33 i.e. the lastest master at the time of this import. No modifications are applied to the imported source code in order to preserve a complete snapshot of it in the repository of jitsi-meet and, thus, facilitate comparison later on. Consequently, the source code of jitsi-meet and/or jitsi-meet-react may not work. For example, jitsi-meet's jshint may be unable to parse jitsi-meet-react's source code. 2016-10-05 14:36:59 +00:00			`*/`
Adds application name to the initJitsiConference options. 2017-10-13 20:34:27 +00:00			`export function getName() {`
			`return NativeModules.AppInfo.name;`
Import jitsi/jitsi-meet-react#2f23d98 As an intermediate step on the path to merging jitsi-meet and jitsi-meet-react, import the whole source code of jitsi-meet-react as it stands at https://github.com/jitsi/jitsi-meet-react/commit/2f23d984245324e79156eeec9e447667b3c76d33 i.e. the lastest master at the time of this import. No modifications are applied to the imported source code in order to preserve a complete snapshot of it in the repository of jitsi-meet and, thus, facilitate comparison later on. Consequently, the source code of jitsi-meet and/or jitsi-meet-react may not work. For example, jitsi-meet's jshint may be unable to parse jitsi-meet-react's source code. 2016-10-05 14:36:59 +00:00			`}`