rzerres/element-call
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Justify the use of a participant count threshold

Browse Source
This commit is contained in:
Robin
2024-07-18 10:00:26 -04:00
parent 183d2d9050
commit e04affe93e
1 changed files with 9 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
src/state/CallViewModel.ts
View File

@@ -74,6 +74,13 @@ import { ObservableScope } from "./ObservableScope";
// list again // list again
const POST_FOCUS_PARTICIPANT_UPDATE_DELAY_MS = 3000; const POST_FOCUS_PARTICIPANT_UPDATE_DELAY_MS = 3000;
// This is the number of participants that we think constitutes a "large" grid.
// The hypothesis is that, after this many participants there's enough cognitive
// load that it makes sense to show the speaker in an easy-to-locate spotlight
// tile. We might change this to a scroll-based condition or do something else
// entirely with the spotlight tile, if we workshop this further.
const largeGridThreshold = 20;
// Represents something that should get a tile on the layout, // Represents something that should get a tile on the layout,
// ie. a user's video feed or a screen share feed. // ie. a user's video feed or a screen share feed.
// TODO: This exposes too much information to the view layer, let's keep this // TODO: This exposes too much information to the view layer, let's keep this
@@ -504,7 +511,8 @@ export class CallViewModel extends ViewModel {
(grid, spotlight, screenShares): Layout => ({ (grid, spotlight, screenShares): Layout => ({
type: "grid", type: "grid",
spotlight: spotlight:
screenShares.length > 0 || grid.length > 20 screenShares.length > 0 ||
grid.length > largeGridThreshold
? spotlight ? spotlight
: undefined, : undefined,
grid, grid,