jiti-meet/app.js

60 lines
2.1 KiB
JavaScript
Raw Normal View History

2013-12-16 11:22:23 +00:00
/* application specific logic */
import 'jquery';
2016-09-16 03:22:56 +00:00
import 'olm';
import 'focus-visible';
2020-09-25 22:51:54 +00:00
// 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
2020-09-25 22:51:54 +00:00
// 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';
2017-06-16 03:47:04 +00:00
import conference from './conference';
import API from './modules/API';
2020-05-20 10:57:03 +00:00
import UI from './modules/UI/UI';
2017-06-16 03:47:04 +00:00
import keyboardshortcut from './modules/keyboardshortcut/keyboardshortcut';
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;
});
}
2017-06-16 03:47:04 +00:00
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
},
2017-06-16 03:47:04 +00:00
keyboardshortcut,
translation,
UI
};
2016-12-14 10:32:36 +00:00
// 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';