2 Commits (3cb0df579ca5b8615dfba1b8b901bca1c8ca9ac4)

Author	SHA1	Message	Date
Horatiu Muresan	768f10d966	feat(route) Redirect to a custom welcome page	3 years ago
Robert Pintilii	3e744c5ffe	ref(TS) Convert some files to TS (#12289)	3 years ago
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
Calinteodor	4e2fea1e12	feat(rn,welcome) React Navigation drawer	4 years ago
Saúl Ibarra Corretgé	cf7b10d53d	feature-flags: initial implementation ... The welcomePageEnabled and pictureInPictureEnabled props on mobile have been converted to feature flags.	7 years ago
virtuacoplenny	a667c9bff2	ref: js-utils for random and room name generator (#3975)	7 years ago
Bettenbuk Zoltan	3fdf944763	Fix eslint/jsdoc warnings (doc change only!)	7 years ago
Saúl Ibarra Corretgé	dc246960df	feat(App): refactor App and split it into BaseApp and App ... BaseApp does all the heavy-lifting related to creating the redux store, navigation, and so on. App currently handles URL props and actually triggering navigation based on them.	8 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	bd7c9473e7	[Android] Fix possible TypeError in multi-JitsiMeetView SDK consumers ... If multiple JitsiMeetView instances are created (not necessarily existing at once), it's possible to hit a TypeError when reading the React Component props of the currently mounted App. Anyway, in certain places we're already protecting against that out of abundance of caution so it makes no sense to not protect everywhere.	8 years ago
virtuacoplenny	74a92f83c7	feat(welcome): new design (#2492) ... * feat(welcome): new design * squash: update strings * squash: copy/paste error? * squash: remove welcome page disabling checks * squash: change strings again * squash: background var * squash: title and desc css as variables	8 years ago
Lyubo Marinov	4bf19d73fd	[RN] Fix documentation comments ... * Javadoc introduced @code as a replacement of <code> and <tt> which is better aligned with other javadoc tags such as @link. Use it in the Java source code. If we switch to Kotlin, then we'll definitely use Markdown. * There are more uses of @code in the JavaScript source code than <tt> so use @code for the sake of consistency. Eventually, I'd rather we switch to Markdown because it's easier on my eyes. * Xcode is plain confused by @code and @link. The Internet says that Xcode supports the backquote character to denote the beginning and end of a string of characters which should be formatted for display as code but it doesn't work for me. <tt> is not rendered at all. So use the backquote which is rendered itself. Hopefully, if we switch to Markdown, then it'll be common between JavaScript and Objective-C source code.	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