apitech/jitsi-meet - jitsi-meet - Gitea: Git with a cup of tea

Author	SHA1	Message	Date
Lyubo Marinov	c203215c54	core: refactor routing (continued)	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
hristoterezov	769e782c6f	feat(callee-info): Redesign.	8 years ago
Bettenbuk Zoltan	4ac367d403	[RN] Implement Labels on mobile	8 years ago
Bettenbuk Zoltan	ffd0827354	[RN] Implement Notifications on mobile	8 years ago
Lyubo Marinov	546651e51f	[RN] Hide conference indicators on reduced UI (coding style)	8 years ago
Bettenbuk Zoltan	79b31543c5	[RN] Hide conference indicators on reduced UI	8 years ago
Guus der Kinderen	acc41e6d0b	feat(toolbar): add 'always-visibile' config option The visibility of the toolbar can be toggled by interacting with the main screen. This change allows the toolbar to be configured to be 'always visible'. This voids the 'toggle' functionality.	8 years ago
Bettenbuk Zoltan	d15753f719	[RN] Add indicator container	8 years ago
Bettenbuk Zoltan	5499599720	[RN] Add RecordingLabel indicator for mobile	8 years ago
Bettenbuk Zoltan	118250750a	[RN] Add VideoQualityLabel indicator for mobile	8 years ago
Lyubo Marinov	8cd2bd272b	Reduce direct read access to the features/base/participants redux state As part of the work on fixing the problem with the multiplying thumbnails, we've associated remote participant w/ JitsiConference. However, there are periods of time when multiple JitsiConferences are in the redux state (and that period is going to be shorted by StateListenerRegistry). In order to give more control to the feature base/participants, reduce the occurrences of direct access to the features/base/participants redux state and utilize the feature's existing read access functions. Which will allow us in the future to enhance these functions to access participants which are relevant to the current conference of interest to the user only.	8 years ago
Lyubo Marinov	ccbf3efa38	Coding style: comments, sorting order	8 years ago
Lyubo Marinov	21c1e4abc4	Coding style: formatting, comments	8 years ago
Saúl Ibarra Corretgé	5bd975e3f3	[RN] Show / hide the toolbox based on the participant count Show it if we are the only participant, and hide it the moment someone else joins the conference.	8 years ago
zbettenbuk	54b6db02d8	Fix error on conference join when calendar is disabled	8 years ago
paweldomas	2af76ebcf9	fix(testing): add TestHint for LargeVideo Since the main conference container is no longer "clickable" there must be a way for clicking on the "large video". A clickable TestHint nested in ParticipantView makes it easier for dealing with the fact that the click handler is not always on the same component (required for the pinch and zoom feature to work correctly).	8 years ago
paweldomas	382c548cf9	ref(testing): move 'testing' feature to base	8 years ago
Saúl Ibarra Corretgé	8daa13cd99	[iOS] Fix statusbar color while in a conference Be explciit about the appearance we desire, since each mounted StaturBar component will override the existing values. In this case, the problem was caused because the default on iOS is dark, whereas it's light on Android. Set it to light so it works consistently across both, which is what we want.	8 years ago
paweldomas	4d942440db	feat: add TestConnectionInfo for mobile Adds TestConnectionInfo component which exposes some internal app state to the jitsi-meet-torture through the UI accessibility layer. This component will render only if config.testing.testMode is set to true.	8 years ago
Zoltan Bettenbuk	decbcefbd4	[RN] Don't press on Conference in preparation for 'pinch to zoom' TouchableWithoutFeedback and TouchableHighlight interfere with the implementation of 'pinch to zoom' to come. We prepare for it by driving the onClick/onPress handler(s) out of Conference, through LargeVideo and ParticipantView into Video itself where the bulk of 'pinch to zoom' will be implemented.	8 years ago
Zoltan Bettenbuk	cb70c084b3	[RN] "The View is never the target of touch events" In preparation for "pinch to zoom" support in desktop streams on mobile, make certain Views not intervene in touch event handling. While the modification is necessary for "pinch to zoom" which is coming later, it really makes sense for the modified Views to not be involved in touching because they're used to aid layout and/or animations and are to behave to the user as if they're not there.	8 years ago
zbettenbuk	ae0bf876a8	Add conference notification	8 years ago
zbettenbuk	04690dfc8f	Facelift Welcome screen	8 years ago
zbettenbuk	9a9890f86c	Introduce SafeArea for Settings and Header	8 years ago
Lyubo Marinov	0bbcd3181c	[RN] Adjust Conference for the reduced UI mode (Coding style)	8 years ago
Saúl Ibarra Corretgé	7a9ff9975a	[RN] Adjust Conference for the reduced UI mode	8 years ago
Lyubo Marinov	240fff74c7	[RN] Add ability to enable / disable the filmstrip (Coding style: comments, naming)	8 years ago
Saúl Ibarra Corretgé	ac09233558	[RN] Add TintedView component It's designed to cover a container and give it a "tint" by using a color and opacity.	8 years ago
Lyubo Marinov	ad497fed7c	Reduce duplication	8 years ago
Saúl Ibarra Corretgé	0f6243ee88	feat(overlays): CallOverlay is not really an overlay It's not supposed to go on top of everything, like an error would. It's tied to a conference, so render it outside of the OverlayContainer.	8 years ago
Saúl Ibarra Corretgé	870e6bbddc	feat(overlays): render overlays outside of Conference On web Conference is pretty much all there is, but on mobile we have the welcome page and the blank page. If we fail to load config.js, for example we will still be in the welcome page and we want to show an error overlay.	8 years ago
Lyubo Marinov	75bf7638b3	ref: define state and property types (2)	8 years ago
paweldomas	379bad0ce6	ref: define state and property types	8 years ago
paweldomas	cd48ee3dbf	feat: add more accessibility labels Adds more accessibility labels required for mobile automated testing.	8 years ago
Lyubo Marinov	8fd91573fc	Fix eslint & flow errors Prepares for the latest eslint & flow-related npm packages which cause these errors.	8 years ago
Lyubo Marinov	78d1fd10e2	[RN] Tap to toggle Toolbox	8 years ago
Lyubo Marinov	d0c079dba5	Coding style	8 years ago
Lyubo Marinov	bce2a9fba9	[RN] Fix eslint & flow errors	8 years ago
paweldomas	c0a7d6144a	feat: display filmstrip on the short side Adds the ability to detect app area's aspect ratio on react-native through the features/base/aspect-ratio. Makes conference, filmstrip and toolbox react to the aspect ratio changes and display filmstrip on the shorter side of the screen.	8 years ago
Lyubo Marinov	dfebd692f3	eslint 4.8.0 ESLint 4.8.0 discovers a lot of error related to formatting. While I tried to fix as many of them as possible, a portion of them actually go against our coding style. In such a case, I've disabled the indent rule which effectively leaves it as it was before ESLint 4.8.0. Additionally, remove jshint because it's becoming a nuisance with its lack of understanding of ES2015+.	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	03d337612b	[Android] Hardware back in Conference and Dialog	8 years ago
Saúl Ibarra Corretgé	720ae18194	[RN] LoadingIndicator while joining a conference	8 years ago
Saúl Ibarra Corretgé	9bca0e3b3d	[RN] Create tracks right when they are required When do we need tracks? - Welcome page (only the video track) - Conference (depends if starting with audio / video muted is requested) When do we need to destroy the tracks? - When we are not in a conference and there is no welcome page In order to accommodate all the above use cases, a new component is introduced: BlankWelcomePage. Its purpose is to take the place of the welcome page when it is disabled. When this component is mounted local tracks are destroyed. Analogously, a video track is created when the (real) welcome page is created, and all the desired tracks are created then the Conference component is created. What are desired tracks? These are the tracks we'd like to use for the conference that is about to happen. By default both audio and video are desired. It's possible, however, the user requested to start the call with no video/audio, in which case it's muted in base/media and a track is not created. The first time the app starts (with the welcome page) it will request permission for video only, since there is no need for audio in the welcome page. Later, when a conference is joined permission for audio will be requested when an audio track is to be created. The audio track is not destroyed when the conference ends. Yours truly thinks this is not needed since it's a stopped track which is not using system resources.	8 years ago
Saúl Ibarra Corretgé	0bf9a78e4c	misc: fix dispatching actions twice when mapDispatchToProps is used The functions need not return anything, or it will be dispatched as another action.	9 years ago
Lyubo Marinov	25ec8ac6a7	Prepare for eslint 4	9 years ago
Lyubo Marinov	ca94563c51	[RN] Coding style The files styles.js are used (pretty much) on React Native only and each of them exports 1 name. Export it as default to cut down on source code.	9 years ago
Lyubo Marinov	b7c4ebba84	Web Filmstrip & LargeVideo React Components We've had Filmstrip & LargeVideo React Components on mobile/React Native from the start. We didn't have them on Web (because the rewrite in React is not complete yet). However, that led to differences in the React Component Conference on Web and mobile. In an effort to get closer to merging the React Component Conference on Web and mobile, introduce the React Components Filmstrip & LargeVideo on Web even if a minimal render-only form at this time.	9 years ago
Lyubo Marinov	a9bdde193d	Approach consistent filmstrip naming We seemed to be using the names "film strip" and "filmstrip" (and, consequently, their source code-conscious forms such as film-strip, FilmStrip, etc.) In order to comply with our coding style which requires a consistent one name for a given abstraction, choose one name and rename the uses of the other name. Wikipedia has a definition of a "filmstrip", I couldn't find a "film strip". I guess our abstraction can be seen as what's described there. When I google "film strip", I get results about "filmstrip" at the top. That's why I chose "filmstrip". Certain uses of "film strip" such as interfaceConfig.filmStripOnly and in the external API I left untouched in an attempt to preserve compatibility. I wasn't sure whether CSS was tangled in compatibility so I made a choice and renamed there was well.	9 years ago

1 2