Yeah, shaman, shaman, shaman, shaman, shaman, shaman.
Okay, as shaman, we have changed us in presentations, and I think Shaman did two presentations,
and I think this might be the second one he did, and I didn't have much time to review this one as the first one.
But anyway, so the previous set-up with slight shows in online was that it's generated a big SVG,
we download the SVG, and then the SVG itself is the presentation.
So the bigger your presentation is, the bigger the download is, so the longer it takes you to see the presentation.
Unlike maybe the desktop mode, where it goes straight to the slide you're looking at and generates that,
the old case for online was, you get a big multi-page SVG.
And the SVG then apparently wasn't embedding funds, so it's whatever funds are available on the system that opens up the SVG.
On your browser side, the browser is opening up the SVG, whatever funds you have installed locally are what more available.
So that was where they were coming from, and to improve that then they wanted to get something similar to the desktop scenario where you get one slide at a time.
That slide starts off being displayed immediately. If you make changes, you only get the modified parts need to be regenerated.
You don't need to read a 50 slide SVG to get away from that, but you don't have that problem with the fund.
And the solution behind it is that they can be pretty much guaranteed that WebGL is available on our browsers and is efficiently fast and all of that.
So WebGL is, so then this thing gives you the 3G transitions are available on the online version of presentations as well.
So that's demonstration of the WebGL doing 3D transitions.
As a video inside another presentation, so just do it again for smoothness purposes of the WebGL version.
What matters here is not the content of the video. I think I think a matter of theory is the fact that the video itself can be hosted inside this new WebGL based presentation.
So animations and videos are in the new WebGL mode.
Apparently there was trouble especially in the past with positioning of videos in the SVG one, being overlaid in the wrong place.
And this is an example or demonstration that those issues of the older SVG version and playing videos and the positioning of them are all fixed in this new version.
A rough idea how a fixed is that the slide has now been split up into various layers and various identifiable parts.
And they can all be cached on the browser side. So if the title zone hasn't changed, then that does not need to be retransmited back down.
But if one of these smaller areas of text has been changed, then just that needs to be sent down to the browser side to be played back.
The code to run the actual slide is of course built into collaborative online itself. The browser side itself.
So that code is already in your browser when you need to do the presentation.
Previously there was an additional JavaScript thing that was downloaded along with the SVG in order to interact with the SVG to get the slides.
So there is inherently listly anyway because you're not downloading an extra component. You have that already.
And then the actual sequence of things to do with the basically cached elements are sent down from the server as a queue of events.
And that queue then you can go back and restart the queue from an earlier period if you need to as well.
So that's your webGL replacement for the previous slideshow using SVGs.
And the additional component then is that the online has now developed and is now grown.
The same type of presenter console might be familiar with in the offline desktop experience.
So if you decision when to do with the presenter very similar design and layout to the desktop one gives you your time your notes preview what's coming up next.
And then a timer and a countdown of how much lift you.
And that I believe is the end of the changes to presenter work in the latest version.
Thank you.