7 Commits (3cb0df579ca5b8615dfba1b8b901bca1c8ca9ac4)

Author	SHA1	Message	Date
Calinteodor	dbf7bf4750	feat(prejoin) native prejoin screen and other navigation updates ... * feat(prejoin) created native Prejoin screen * feat(prejoin) fixed useState callback and updates warnings * feat(prejoin) created styles file * feat(prejoin) moved nav from middleware to appNavigate, created native DeviceStatus * feat(prejoin) updated styles * feat(prejoin) review remarks pt. 1 * feat(prejoin) removed unused styles * feat(prejoin) review remarks pt. 2 * feat(prejoin) comment fix * feat(prejoin) added header title * feat(prejoin) review remarks * feat(lobby) updated styles * feat(prejoin) updated lobby screen header button functionality * feat(prejoin) review remarks pt 3 * feat(welcome) removed VideoSwitch component * feat(mobile/navigation) fixed linter * feat(welcome) moved isWelcomePageEnabled to functions.ts * feat(mobile/navigation) screen options and order updates * feat(app) review remark * feat(welcome) added translation for screen header title and fixed build * feat(mobile/navigation) added screen title translation and created screen option * feat(mobile/navigation) fixed screenOptions import * feat(mobile/navigation) added DialInSummary title translation, fixed animation and close button * feat(welcome) fixed build * feat(welcome) removed extra check * feat(prejoin) review remarks pt 4 * feat(prejoin) added Join in low bandwidth mode btn * feat(welcome) changed welcome screen header title * fixup lobby close	4 years ago
Saúl Ibarra Corretgé	6e679f952f	redux: refactor loading of middlewares and reducers ... Up until now we relied on implicit loading of middlewares and reducers, through having imports in each feature's index.js. This leads to many complex import cycles which result in (sometimes) hard to fix bugs in addition to (often) breaking mobile because a web-only feature gets imported on mobile too, thanks to the implicit loading. This PR changes that to make the process explicit. Both middlewares and reducers are imported in a single place, the app entrypoint. They have been divided into 3 categories: any, web and native, which represent each of the platforms respectively. Ideally no feature should have an index.js exporting actions, action types and components, but that's a larger ordeal, so this is just the first step in getting there. In order to both set example and avoid large cycles the app feature has been refactored to not have an idex.js itself.	6 years ago
Saúl Ibarra Corretgé	155e02bbfb	core: refactor routing ... Unfortunately, as the Jitsi Meet development evolved the routing mechanism became more complex and thre logic ended up spread across multiple parts of the codebase, which made it hard to follow and extend. This change aims to fix that by rewriting the routing logic and centralizing it in (pretty much) a single place, with no implicit inter-dependencies. In order to arrive there, however, some extra changes were needed, which were not caught early enough and are thus part of this change: - JitsiMeetJS initialization is now synchronous: there is nothing async about it, and the only async requirement (Temasys support) was lifted. See [0]. - WebRTC support can be detected early: building on top of the above, WebRTC support can now be detected immediately, so take advantage of this to simplify how we handle unsupported browsers. See [0]. The new router takes decissions based on the Redux state at the time of invocation. A route can be represented by either a component or a URl reference, with the latter taking precedence. On mobile, obviously, there is no concept of URL reference so routing is based solely on components. [0]: https://github.com/jitsi/lib-jitsi-meet/pull/779	8 years ago
Lyubo Marinov	9f69c4d730	Grow features/settings from features/app-settings and features/settings-menu	8 years ago
zbettenbuk	04690dfc8f	Facelift Welcome screen	8 years ago
Lyubo Marinov	45a1ae26ca	[RN] Prepare to display BlankPage more ... For example, while config.js and other files are being loaded before the navigation to Conference is feasible.	8 years ago
Lyubomir Marinov	d55e0f70d9	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 2f23d98424 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.	9 years ago