7 Commits (52ce9a86ed2c78b94de2586cbf39fbcbb4d69fbd)

Author	SHA1	Message	Date
Calinteodor	f3f9cd3d05	feat(dynamic-branding) add initial mobile SDK customization ... * feat(dynamic-branding) sdk customization * feat(dynamic-branding) unsetDynamicBranding when we disconnect * feat(dynamic-branding) added branding colors to conference * feat(dynamic-branding) extracted logger to its own file * feat(dynamic-branding) reverted style change * feat(dynamic-branding) unset branding if connection failed * feat(dynamic-branding) removed index.js, updated imports, added ImageBackground component * feat(dynamic-branding) created logger feature object * feat(dynamic-branding) moved brandingStyles to mapStateToProps, used SvGUri * feat(dynamic-branding) created BrandingImageBackground component, fixed styles * feat(dynamic-branding) moved BrandingImageBackground to dynamic-branding feature * feat(dynamic-branding) fixed linter * feat(dynamic-branding) added style comment	4 years ago
Robert Pintilii	1355876f83	feat(gif, rn) Added GIPHY integration on native (#11236) ... Update Android build to support gif Use GIF format instead of animated webp Show GIFs in chat messages Display GIF over tile Add Giphy button in reactions menu Added Giphy dialog Fix isGifMessage to also allow upper case	4 years ago
Saúl Ibarra Corretgé	26b3eb34f0	fix(android,back-button) rework back button handling on Android ... We used to have a registry which registered a single handlerwith RN. THis was registered really early in the app. When React Navigation was introduced we ddidn't realize it interacts with the back button. In a stack nagigator it will navigate to the previous screen. This meant our back button handling was broken. This commit removes our previous registry and uses the RN back button handler directly in the 2 components that use it: the conference and bottom sheets. Since these handlers are registered after navigation, our handlers are going to run first so we cna implement the behavior we need, namely to dismiss an open botom sheet or set the conference in PiP mode.	4 years ago
Saúl Ibarra Corretgé	c84e6eecdd	feat(rn) drop incoming call handling ... This "feature" has been dead (and most likely buggy) for years. The recommended way is for apps to implement their own incoming call handling and then call into the JitsiMeetActivity. We did not have those APIs back then.	4 years ago
Calinteodor	b9433368ee	feat(rn,app) unified navigators	4 years ago
Calinteodor	430591bd1e	feat(shared-video) refactor dialog to use React ... Also unify the mobile and web features into one, even though internally they still have separate ways to enable the functionality.	5 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