jiti-meet/react/features/base/participants/components
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.
2018-05-23 09:46:15 -05:00
..
Avatar.native.js [RN] Dynamically adjust LargeView's Avatar to available size (Coding style: comments, flow) 2018-02-13 09:58:43 -06:00
Avatar.web.js [RN] Dynamically adjust LargeView's Avatar to available size (Coding style: comments, flow) 2018-02-13 09:58:43 -06:00
ParticipantView.native.js Reduce direct read access to the features/base/participants redux state 2018-05-23 09:46:15 -05:00
ParticipantView.web.js ref(avatar): Move Avatar and Participant view to base/participants 2017-03-02 16:57:43 -06:00
index.js feat(Avatar): Implement Avatar for web 2017-03-07 21:54:37 -06:00
styles.js [RN] Dynamically adjust LargeView's Avatar to available size 2018-02-13 09:58:43 -06:00