62 lines
2.3 KiB
JavaScript
62 lines
2.3 KiB
JavaScript
/* application specific logic */
|
|
|
|
import 'jquery';
|
|
import 'jquery-contextmenu';
|
|
import 'jQuery-Impromptu';
|
|
|
|
import 'olm';
|
|
|
|
// We need to setup the jitsi-local-storage as early as possible so that we can start using it.
|
|
// NOTE: If jitsi-local-storage is used before the initial setup is performed this will break the use case when we use
|
|
// the local storage from the parent page when the localStorage is disabled. Also the setup is relying that
|
|
// window.location is not changed and still has all URL parameters.
|
|
import './react/features/base/jitsi-local-storage/setup';
|
|
import conference from './conference';
|
|
import API from './modules/API';
|
|
import UI from './modules/UI/UI';
|
|
import keyboardshortcut from './modules/keyboardshortcut/keyboardshortcut';
|
|
import remoteControl from './modules/remotecontrol/RemoteControl';
|
|
import translation from './modules/translation/translation';
|
|
|
|
// Initialize Olm as early as possible.
|
|
if (window.Olm) {
|
|
window.Olm.init().catch(e => {
|
|
console.error('Failed to initialize Olm, E2EE will be disabled', e);
|
|
delete window.Olm;
|
|
});
|
|
}
|
|
|
|
window.APP = {
|
|
API,
|
|
conference,
|
|
|
|
// Used by do_external_connect.js if we receive the attach data after
|
|
// connect was already executed. status property can be 'initialized',
|
|
// 'ready', or 'connecting'. We are interested in 'ready' status only which
|
|
// means that connect was executed but we have to wait for the attach data.
|
|
// In status 'ready' handler property will be set to a function that will
|
|
// finish the connect process when the attach data or error is received.
|
|
connect: {
|
|
handler: null,
|
|
status: 'initialized'
|
|
},
|
|
|
|
// Used for automated performance tests.
|
|
connectionTimes: {
|
|
'index.loaded': window.indexLoadedTime
|
|
},
|
|
|
|
keyboardshortcut,
|
|
remoteControl,
|
|
translation,
|
|
UI
|
|
};
|
|
|
|
// TODO The execution of the mobile app starts from react/index.native.js.
|
|
// Similarly, the execution of the Web app should start from react/index.web.js
|
|
// for the sake of consistency and ease of understanding. Temporarily though
|
|
// because we are at the beginning of introducing React into the Web app, allow
|
|
// the execution of the Web app to start from app.js in order to reduce the
|
|
// complexity of the beginning step.
|
|
import './react';
|