openvidu-custom-participants-panel#
The openvidu-custom-participants-panel tutorial demonstrates how to customize the participants panel, providing a more tailored user experience.
Replacing the default participants panel is made simple with the ParticipantsPanelDirective, which offers a straightforward way to replace and adapt the ParticipantsPanelComponent to your needs.
Running this tutorial#
1. Run OpenVidu Server#
-
Download OpenVidu
-
Configure the local deployment
-
Run OpenVidu
To use a production-ready OpenVidu deployment, visit the official deployment guide.
Configure Webhooks
All application servers have an endpoint to receive webhooks from OpenVidu. For this reason, when using a production deployment you need to configure webhooks to point to your local application server in order to make it work. Check the Send Webhooks to a Local Application Server section for more information.
2. Download the tutorial code#
git clone https://github.com/OpenVidu/openvidu-livekit-tutorials.git -b 3.0.0-beta3
git clone https://github.com/OpenVidu/openvidu-tutorials.git -b 3.0.0-beta3
3. Run a server application#
To run this server application, you need Node installed on your device.
- Navigate into the server directory
- Install dependencies
- Run the application
For more information, check the Node.js tutorial.
To run this server application, you need Go installed on your device.
- Navigate into the server directory
- Run the application
For more information, check the Go tutorial.
To run this server application, you need Ruby installed on your device.
- Navigate into the server directory
- Install dependencies
- Run the application
For more information, check the Ruby tutorial.
To run this server application, you need Java and Maven installed on your device.
- Navigate into the server directory
- Run the application
For more information, check the Java tutorial.
To run this server application, you need Python 3 installed on your device.
-
Navigate into the server directory
-
Create a python virtual environment
-
Activate the virtual environment
-
Install dependencies
-
Run the application
For more information, check the Python tutorial.
To run this server application, you need Rust installed on your device.
- Navigate into the server directory
- Run the application
For more information, check the Rust tutorial.
To run this server application, you need PHP and Composer installed on your device.
- Navigate into the server directory
- Install dependencies
- Run the application
Warning
LiveKit PHP SDK requires library BCMath. This is available out-of-the-box in PHP for Windows, but a manual installation might be necessary in other OS. Run sudo apt install php-bcmath
or sudo yum install php-bcmath
For more information, check the PHP tutorial.
To run this server application, you need .NET installed on your device.
- Navigate into the server directory
- Run the application
Warning
This .NET server application needs the LIVEKIT_API_SECRET
env variable to be at least 32 characters long. Make sure to update it here and in your OpenVidu Server.
For more information, check the .NET tutorial.
4. Run the openvidu-custom-participants-panel tutorial#
To run the client application tutorial, you need Node installed on your development computer.
-
Navigate into the application client directory:
-
Install the required dependencies:
-
Serve the application:
Once the server is up and running, you can test the application by visiting http://localhost:5080
.
Accessing your application client from other devices in your local network
One advantage of running OpenVidu locally is that you can test your application client with other devices in your local network very easily without worrying about SSL certificates.
Access your application client through https://xxx-yyy-zzz-www.openvidu-local.dev:5443
, where xxx-yyy-zzz-www
part of the domain is your LAN private IP address with dashes (-) instead of dots (.). For more information, see section Accessing your local deployment from other devices on your network.
Understanding the code#
This tutorial is an Angular project generated with Angular CLI tool. Therefore, you will see many configuration files and other components that are not the primary focus of this tutorial. We will concentrate on the following files in the src
directory:
main.ts
: This file defines the root application component. It imports theOpenViduComponentsModule
, where we configure the OpenVidu Components Angular library.app/app.component.ts
: This file defines the AppComponent, the primary and sole component of the application. It is responsible for requesting the OpenVidu token and passing it to the videoconference component, facilitating the connection to the OpenVidu Room.styles.scss
: This file defines the global styles of the application. Here, you can customize the UI of the OpenVidu Components Angular library.
To use OpenVidu Components Angular in your application, you need to install the library and import the OpenViduComponentsModule
in your Angular module. Let's see how to do this:
-
Create an Angular Project (version 17 or higher)
To begin, you will need to create a new Angular project if you haven't already. Ensure you have Node.js and the Angular CLI installed. Then, run the following command to create a new Angular project:
Replace
your-project-name
with the desired name for your project. -
Add Angular Material to your project
OpenVidu Components Angular needs Angular Material, which provides a range of UI components. To add Angular Material to your project, navigate to your project directory and run:
-
Install OpenVidu Components Angular
With your Angular project set up, it's time to add videoconferencing capabilities with OpenVidu Components Angular. Install the library using npm:
-
Import and use OpenVidu Components Angular
To use OpenVidu Components Angular in your application, you need to:
- Import the
OpenViduComponentsModule
in your Angular application. - Configure the module with the
OpenViduComponentsConfig
object. - Add the component to your template file.
- Assign the OpenVidu token and LiveKit URL to the component.
- Customize the appearance of the components using CSS variables.
- Import the
In your main.ts
application file, import the it and configure it as follows:
// Other imports ...
import { OpenViduComponentsModule, OpenViduComponentsConfig } from 'openvidu-components-angular';
const config: OpenViduComponentsConfig = {
production: true,
};
bootstrapApplication(AppComponent, {
providers: [
importProvidersFrom(
OpenViduComponentsModule.forRoot(config)
// Other imports ...
),
provideAnimations(),
],
}).catch((err) => console.error(err));
Use the ov-videoconference
component to create a videoconference. This component requires a token to connect to the OpenVidu Room. The AppComponent
class is responsible for requesting the token and passing it to the ov-videoconference
component.
import {
ParticipantModel,
ParticipantService,
OpenViduComponentsModule
} from 'openvidu-components-angular';
@Component({
selector: 'app-root',
template:`
<!-- OpenVidu Video Conference Component -->
<ov-videoconference
[token]="token"
[livekitUrl]="LIVEKIT_URL"
(onTokenRequested)="onTokenRequested($event)"
>
<!-- Custom Participants Panel -->
<div *ovParticipantsPanel id="my-panel">
<ul id="local">
<li>{{ localParticipant.name }}</li>
</ul>
<ul id="remote">
@for (p of remoteParticipants; track p) {
<li>{{ p.name }}</li>
}
</ul>
</div>
</ov-videoconference>
`,
styles: [''],
standalone: true,
imports: [OpenViduComponentsModule],
})
export class AppComponent implements OnInit, OnDestroy {
// For local development, leave these variables empty
// For production, configure them with correct URLs depending on your deployment
APPLICATION_SERVER_URL = ''; // (1)!
LIVEKIT_URL = ''; // (2)!
// The name of the room to join.
roomName = 'openvidu-custom-participants-panel'; // (3)!
// The token used to join the room.
token!: string; // (4)!
// Participant-related properties
localParticipant!: ParticipantModel; // (5)!
remoteParticipants!: ParticipantModel[]; // (6)!
localParticipantSubs!: Subscription; // (7)!
remoteParticipantsSubs!: Subscription; // (8)!
constructor(private httpClient: HttpClient, private participantService: ParticipantService) {
this.configureUrls();
}
private configureUrls() {
// If APPLICATION_SERVER_URL is not configured, use default value from local development
if (!this.APPLICATION_SERVER_URL) {
if (window.location.hostname === 'localhost') {
this.APPLICATION_SERVER_URL = 'http://localhost:6080/';
} else {
this.APPLICATION_SERVER_URL =
'https://' + window.location.hostname + ':6443/';
}
}
// If LIVEKIT_URL is not configured, use default value from local development
if (!this.LIVEKIT_URL) {
if (window.location.hostname === 'localhost') {
this.LIVEKIT_URL = 'ws://localhost:7880/';
} else {
this.LIVEKIT_URL = 'wss://' + window.location.hostname + ':7443/';
}
}
}
ngOnInit() {
// Subscribe to participants' updates
this.subscribeToParticipants();
}
ngOnDestroy() {
// Unsubscribe from participant updates to prevent memory leaks
this.localParticipantSubs?.unsubscribe();
this.remoteParticipantsSubs?.unsubscribe();
}
// Requests a token to join the room with the given participant name.
async onTokenRequested(participantName: string) { // (9)!
const { token } = await this.getToken(this.roomName, participantName);
this.token = token;
}
// Subscribe to updates for local and remote participants
private subscribeToParticipants() { // (10)!
this.localParticipantSubs = this.participantService.localParticipant$.subscribe((p) => {
if (p) this.localParticipant = p;
});
this.remoteParticipantsSubs = this.participantService.remoteParticipants$.subscribe((participants) => {
this.remoteParticipants = participants;
});
}
// Retrieves a token to join the room with the given name and participant name.
getToken(roomName: string, participantName: string): Promise<any> { // (11)!
// Requesting token to the server application
}
}
APPLICATION_SERVER_URL
: URL to communicate the client application with the server application to request OpenVidu tokens.LIVEKIT_URL
: URL to communicate the client application with the LiveKit server.roomName
: OpenVidu Room identifier. This is the room where the VideoconferenceComponent will connect.token
: OpenVidu Token used to connect to the OpenVidu Room.localParticipant
: Local participant model.remoteParticipants
: Remote participants model.localParticipantSubs
: Subscription to the local participant updates.remoteParticipantsSubs
: Subscription to the remote participants updates.onTokenRequested
method that fires when the VideoconferenceComponent requests a token to connect to the OpenVidu Room.subscribeToParticipants
method that subscribes to updates for local and remote participants.getToken
method that requests a token to the server application.
The app.component.ts
file declares the following properties and methods:
APPLICATION_SERVER_URL
: URL to communicate the client application with the server application to request OpenVidu tokens.LIVEKIT_URL
: URL to communicate the client application with the LiveKit server.roomName
: OpenVidu Room identifier. This is the room where the VideoconferenceComponent will connect.token
: OpenVidu Token used to connect to the OpenVidu Room.localParticipant
: Local participant model.remoteParticipants
: Remote participants model.localParticipantSubs
: Subscription to the local participant updates.remoteParticipantsSubs
: Subscription to the remote participants updates.onTokenRequested
method that fires when the VideoconferenceComponent requests a token to connect to the OpenVidu Room.subscribeToParticipants
method that subscribes to updates for local and remote participants.getToken
method that requests a token to the server application.
Configure the URLs
When running OpenVidu locally, leave APPLICATION_SERVER_URL
and LIVEKIT_URL
variables empty. The function configureUrls()
will automatically configure them with default values. However, for other deployment type, you should configure these variables with the correct URLs depending on your deployment.
The OpenVidu Components Angular library provides a set of CSS variables that you can use to customize the appearance of the components. You can define these variables in your application's global styles file (e.g. styles.scss
).
:root {
/* Basic colors */
--ov-background-color: #303030; // Background color
--ov-surface-color: #ffffff; // Surfaces colors (panels, dialogs)
/* Text colors */
--ov-text-primary-color: #ffffff; // Text color over primary background
--ov-text-surface-color: #1d1d1d; // Text color over surface background
/* Action colors */
--ov-primary-action-color: #273235; // Primary color for buttons, etc.
--ov-secondary-action-color: #f1f1f1; // Secondary color for buttons, etc.
--ov-accent-action-color: #0089ab; // Color for highlighted elements
/* Status colors */
--ov-error-color: #eb5144; // Error color
--ov-warn-color: #ffba53; // Warning color
/* Radius */
--ov-toolbar-buttons-radius: 50%; // Radius for toolbar buttons
--ov-leave-button-radius: 10px; // Radius for leave button
--ov-video-radius: 5px; // Radius for videos
--ov-surface-radius: 5px; // Radius for surfaces
}
Customizing participants panel#
This tutorial uses the *ovParticipantsPanel
directive with the aim of replacing the default participant panel with a custom one.
In the app.component.ts
file, you can see the following code snippet:
@Component({
selector: 'app-root',
template: `
<!-- OpenVidu Video Conference Component -->
<ov-videoconference
[token]="token"
[livekitUrl]="LIVEKIT_URL"
(onTokenRequested)="onTokenRequested($event)"
>
<!-- Custom Participants Panel -->
<div *ovParticipantsPanel id="my-panel">
<ul id="local">
<li>{{ localParticipant.name }}</li>
</ul>
<ul id="remote">
@for (p of remoteParticipants; track p) {
<li>{{ p.name }}</li>
}
</ul>
</div>
</ov-videoconference>
`,
styles: [''],
standalone: true,
imports: [OpenViduComponentsModule],
})
export class AppComponent implements OnInit, OnDestroy{
// ...
}