ParentNode is the bit that decides where to show the iframe. Width is the width of the iframe, while similarly height is its height. RoomName is the name of the room that this iframe joins. The options object however, contains some not-so-human-friendly properties. The “domain” constant keeps track of which jitsi installation to stream from. It’s not necessary, but go ahead and add it, if you want. I use it to record the state of the stream, so I can change how my buttons work according to that. Now, you can see, I also have another variable here called “isStreamOn”. ParentNode: document.querySelector('#ELEMENT_ID'), The API’s function will use them as parameters later. Defining some constantsĪfter importing the script, open a new tag and define two constants. ![]() Once you are done, the rest of the API is available for your use. You should start by importing the external api script into the page Importing the scriptĪll the scripting here takes place after the tag, but before, obviously, the tag. I’ll explain how or why something works, something doesn’t and what can be done about it piece by piece. But I would still read the rest, just in case. If you’re in a hurry, you can download the html file and be done. I’ve tried to write it as openly as I could. You can find the entirety of the code on GitHub. But it works without a hitch, and you can scavenge what wisdom you want without fear and flex your designer muscles on it. It is, to put it eloquently, veritably ugly. Now, without all the trademarked bells and whistles, the result looks startlingly close to a carrot you’ve purchased and forgot in the refrigerator. Mid-way through the project, I’ve decided to put together all the hurdles I’ve had to jump over into a neat little article. I’ve got to say, it is a nifty tool, but it has some shortcomings and oddities in the strangest of places. What is the guide about?Ĭhance would have it, recently I’ve got a request from a customer to design a Jitsi UI with rather distinct specifications. With the Jitsi IFrame API, you can embed a Jitsi meeting into your website design like you would any other IFrame. Mustache twirling will be examined in another article. It is the “go to” way of embeding Jitsi into your website and making it look like that was your plan all along. ![]() ![]() It’s a small little API that turns a Jitsi meeting into an iFrame element, so you can use it in the html. Do you want to embed Jitsi into your website page, and have it run through a UI of its own? Do you want the meeting function to be a small, secondary tidbit and have the rest of your website take the main stage, or, well, exist, at all? Meet Jitsi IFrame API.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |