haskal/jiti-meet - GitLain - Git with a cup of Lain

Author	SHA1	Message	Date
Bettenbuk Zoltan	2a5adfc601	Remove some Flow annotations	2019-03-25 13:53:08 +01:00
Saúl Ibarra Corretgé	e729f0948c	android: fix deep-linking from web Looks like custom-scheme links no longer work in all browsers. They do on Firefox, but the don't in Chrome and other default browsers. So, switch to intent links on Android: https://developer.chrome.com/multidevice/android/intents Example: ``` <a href="intent://meet.jit.si/test123#Intent;scheme=org.jitsi.meet;package=org.jitsi.meet;end">Open Jitsi Meet</a> ```	2019-02-01 09:30:09 +01:00
damencho	c13424f7c0	Fixes some lint warnings.	2019-01-11 15:11:17 +01:00
srmcgann	e7d0bf7b66	feat(DeepLinkingMobilePage): fix nested iframe button	2019-01-11 09:42:52 +01:00
Leonard Kim	c288d0e18c	ref(deep-linking): set initial state in constructor	2018-11-21 08:08:45 -08:00
Leonard Kim	486e8e35d9	ref: move all prop type declaration to flow For the most part the changes are taking the "static propTypes" declaration off of components and declaring them as Flow types. Sometimes to support flow some method signatures had to be added. There are some exceptions in which more had to be done to tame the beast: - AbstractVideoTrack: put in additional truthy checks for videoTrack. - Video: add truthy checks for the _videoElement ref. - shouldRenderVideoTrack function: Some component could pass null for the videoTrack argument and Flow wanted that called out explicitly. - DisplayName: Add a truthy check for the input ref before acting on it. - NumbersList: Move array checks inline for Flow to comprehend array methods could be called. Add type checks in the Object.entries loop as the value is assumed to be a mixed type by Flow. - AbstractToolbarButton: add additional truthy check for passed in type.	2018-11-07 17:38:10 +01:00
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	2018-07-11 22:58:41 -05:00