` which will display the video of its Stream property, as well as the user's nickname in a `` element.
-
-Let's see how `app.component.ts` uses `openvidu-browser`:
-
-- First line imports the necessary objects from `openvidu-browser`:
-
- ```typescript
- import { OpenVidu, Session, Stream } from 'openvidu-browser';
- ```
-- `app.component.ts` declares the following properties:
-
- ```typescript
- // OpenVidu objects
- OV: OpenVidu;
- session: Session;
-
- // Streams to feed StreamComponent's
- remoteStreams: Stream[] = [];
- localStream: Stream;
-
- // Join form
- sessionId: string;
- token: string;
- ```
- `OpenVidu` object will allow us to get a `Session` object, which is declared just after it. `remoteStreams` array will store the active streams of other users in the video-call and `localStream` will be your own local webcam stream. Finally, `sessionId` and `token` params simply represent the video-call and your participant's nickname, as you will see in a moment.
-
-- Whenever a user clicks on the submit input defined in `app.component.html`, `joinSession()` method is called:
-
- ```javascript
- // --- 1) Get an OpenVidu object and init a session with a sessionId ---
-
- // OpenVidu listening on "localhost:8443"
- this.OV = new OpenVidu('wss://' + location.hostname + ':8443/');
-
- // We will join the video-call "sessionId"
- this.session = this.OV.initSession(this.sessionId);
- ```
- Since we are in a local sample app, `OV` is initialize with `localhost:8443` as its _openvidu-server_ URL. `session` is initialize with `sessionId` param: this means we will connect to `sessionId` video-call. In this case, this parameter is binded from an `
- ```
-
- - `streamDestroyed`: for each Stream that has been destroyed (which means a user has left the video-call), we remove it from `remoteStreams` array, so Angular will automatically delete the required StreamComponent from HTML. We call `event.preventDefault()` to cancel OpenVidu default behaviour towards `streamDestroyed` event, which is the deletion of the previously created HTML video element on `streamCreated` event. Because we are handling the video elements by ourselves taking advantage of Angular capabilities, we tell OpenVidu not to create them on `streamCreated` and not to delete them on `streamDestroyed`, by passing an empty string as second parameter on `Session.subscribe()` method on `streamCreated` and by calling `event.preventDefault()` on `streamDestroyed`.
-
-- Finally connect to the session and publish your webcam:
-
- ```javascript
-
- // --- 3) Connect to the session ---
-
- // 'token' param irrelevant when using insecure version of OpenVidu. Second param will be received by every user
- // in Stream.connection.data property, which will be appended to DOM as the user's nickname
- this.session.connect(this.token, '{"clientData": "' + this.token + '"}', (error) => {
-
- // If the connection is successful...
- if (!error) {
-
- // --- 4) Get your own camera stream with the desired resolution ---
-
- // Both audio and video will be active. HTML video element will be appended to element with 'publisher' id
- let publisher = this.OV.initPublisher('', {
- audio: true,
- video: true,
- quality: 'MEDIUM'
- });
-
- //Store your webcam stream in 'localStream' object
- this.localStream = publisher.stream;
-
- // --- 5) Publish your stream ---
-
- this.session.publish(publisher);
-
- } else {
- console.log('There was an error connecting to the session:', error.code, error.message);
- }
- });
- ```
-
- `token` param is irrelevant when using insecure version of OpenVidu. Second parameter will supply the user's nickname showed by StreamComponent inside its `` element. So in this case it is a JSON formatted string with a "clientData" tag with "token" value, which is retrieved from HTML input `
- ```
- Last point worth considering is the `ngDoCheck()` implementation of StreamComponent. As we are handling Stream objects by ourselves (task which usually is taken care by OpenVidu), and because the URL of Stream objects takes some time to get its final value as the WebRTC negotiation takes place, we must listen to any change in `stream` @Input property. This allows us to update `videoSrc` value of the component, which finally ends up being the _src_ value of the `` element. If we didn't do this, the Stream object will update its _src_ property, but our StreamComponent would keep the same initial `videoSrc` value. This ensures that all our StreamComponent's will properly display all the videos in the video-call using the correct _src_ value.
-
- ```javascript
- ngDoCheck() { // Detect any change in 'stream' property
-
- // If 'src' of Stream object has changed, 'videoSrc' value must be updated
- if (!(this.videSrcUnsafe === this.stream.getVideoSrc())) {
-
- // Angular mandatory URL sanitization
- this.videoSrc = this.sanitizer.bypassSecurityTrustUrl(this.stream.getVideoSrc());
-
- // Auxiliary value to store the URL as a string for upcoming comparisons
- this.videSrcUnsafe = this.stream.getVideoSrc();
- }
- }
- ```
\ No newline at end of file
+LINK: [openvidu.io/docs/tutorials/openvidu-insecure-angular/](http://openvidu.io/docs/tutorials/openvidu-insecure-angular/)
diff --git a/openvidu-insecure-js/README.md b/openvidu-insecure-js/README.md
index 30d077f5..5afa7099 100644
--- a/openvidu-insecure-js/README.md
+++ b/openvidu-insecure-js/README.md
@@ -1,147 +1,3 @@
# openvidu-insecure-js
-This is the simplest demo you can try to get started with OpenVidu. It has the minimum set of features to make a video-call. You will only need a few minutes to get your first application working.
-
-## Understanding this example
-
-
-
-
-OpenVidu is composed by the three modules displayed on the image above in its insecure version.
-
-- **openvidu-browser**: JavaScript library for the browser. It allows you to manage your video-calls straight away from your clients
-- **openvidu-server**: Java application that controls Kurento Media Server
-- **Kurento Media Server**: server that handles low level operations of media flows transmission
-
-> You will only have to make use of **openvidu-browser** to get this sample app working.
-
-## Executing this example
-
-1. Clone the repo:
-
- ```bash
- git clone https://github.com/OpenVidu/openvidu-tutorials.git
- ```
-
-2. You will need an http web server installed in your development computer to execute the sample application. If you have _node.js_ installed, you can use [http-server](https://github.com/indexzero/http-server) to serve application files. It can be installed with:
-
- ```bash
- npm install -g http-server
- ```
-
-3. To run the sample application, execute the following command in the project:
-
- ```bash
- cd openvidu-insecure-js/web
- http-server
- ```
-
-4. _openvidu-server_ and _Kurento Media Server_ must be up and running in your development machine. The easiest way is running this Docker container which wraps both of them (you will need [Docker CE](https://store.docker.com/search?type=edition&offering=community)):
-
- ```bash
- docker run -p 8443:8443 --rm -e KMS_STUN_IP=193.147.51.12 -e KMS_STUN_PORT=3478 openvidu/openvidu-server-kms
- ```
-
-5. Go to [`localhost:8080`](http://localhost:8080) to test the app once the server is running. The first time you use the docker container, an alert message will suggest you accept the self-signed certificate of _openvidu-server_ when you first try to join a video-call.
-
-## Understanding the code
-
-This application is very simple. It has only 4 files:
-
-- `OpenVidu.js`: openvidu-browser library. You don't have to manipulate this file.
-- `app.js`: sample application main JavaScritp file, which makes use of _OpenVidu.js_. You can manipulate this file to suit your needs.
-- `index.html`: HTML code for the form to connect to a video-call and for the video-call itself. You can manipulate this file to adapt it to suit your needs.
- It has two links to both JavaScript files:
- ```html
-
-
- ```
-
-- `style.css`: some CSS classes to style _index.html_. You can manipulate this file to suit your needs.
-
-Let's see how `app.js` uses `OpenVidu.js`:
-
-- First lines declare the two variables that will be needed in different points along the code. `OV` will be our OpenVidu object and `session` the video-call we will connect to:
-
- ```javascript
- var OV;
- var session;
- ```
-
-- Let's initialize a new session and configure our events:
-
- ```javascript
- // --- 1) Get an OpenVidu object and init a session with a sessionId ---
-
- // OpenVidu listening on "localhost:8443"
- OV = new OpenVidu("wss://" + location.hostname + ":8443/");
-
- // We will join the video-call "sessionId"
- session = OV.initSession(sessionId);
- ```
- Since we are in a local sample app, `OV` object is initialize with `localhost:8443` as its _openvidu-server_ URL. `session` object is initialize with `sessionId` param: this means we will connect to `sessionId` video-call. In this case, this parameter is retrieve from HTML input ` element for the user's nickname just below its video
- appendUserData(event.element, subscriber.stream.connection);
- });
- });
-
- // On every Stream destroyed...
- session.on('streamDestroyed', function (event) {
-
- // Delete the HTML element with the user's nickname. HTML videos are automatically removed from DOM
- removeUserData(event.stream.connection);
- });
- ```
- Here we subscribe to the events that interest us. In this case, we want to receive all videos published to the video-call, as well as displaying every user's nickname nex to its video. To achieve this:
- - `streamCreated`: for each new Stream received by OpenVidu, we immediately subscribe to it so we can see its video. A new HTML video element will be appended to element with id 'subscriber'.
- - `videoElementCreated`: event triggered by Subscriber object (returned by the previous `Session.subscribe` method). This allows us to add the participant nickname to the new video previously added in `streamCreated` event. Auxiliary method `appendUserData` is responsible for appending a new paragraph element just below the `event.element` video, containing `subscriber.stream.connection.data` field (which has the user's nickname).
- - `streamDestroyed`: for each Stream that has been destroyed (which means a user has left the video-call), we remove the paragraph element with the user's nickname that we added in the previous event (`appendUserData` method created the element with an _id_ containing `event.stream.connection.connectionId` unique value, so we can now identify the right element to be removed). The video element is automatically deleted by default, so we don't need to do anything else.
-
-- Finally connect to the session and publish your webcam:
-
- ```javascript
- // --- 3) Connect to the session ---
-
- // 'token' param irrelevant when using insecure version of OpenVidu. Second param will be received by every user
- // in Stream.connection.data property, which will be appended to DOM as the user's nickname
- session.connect(token, '{"clientData": "' + token + '"}', function (error) {
-
- // If the connection is successful, initialize a publisher and publish to the session
- if (!error) {
-
- // --- 4) Get your own camera stream with the desired resolution ---
-
- // Both audio and video will be active. HTML video element will be appended to element with 'publisher' id
- var publisher = OV.initPublisher('publisher', {
- audio: true,
- video: true,
- quality: 'MEDIUM'
- });
-
- // --- 5) Publish your stream ---
-
- session.publish(publisher);
-
- } else {
- console.log('There was an error connecting to the session:', error.code, error.message);
- }
- });
- ```
-
- `token` param is irrelevant when using insecure version of OpenVidu. Remember `videoElementCreated` event, when we added the user's nickname to the HTML? Well, second parameter is the actual value you will receive in `Stream.connection.data` property. So in this case it is a JSON formatted string with a "clientData" tag with "token" value, which is retrieved from HTML input `