 The question was, because of the live stream. Yeah. What's going on? It's going to be recorded, yeah. Yeah, will be too boring. OK, so contextual groups. You have seen what I will talk about. It's the idea behind this realization. Notebook buyers are just a blank canvas. You can't put anything onto it. And it should enable you to quickly deal with the features of the program. So how was the idea to create a notebook bar? And in particular, the contextual group. So that's what I will talk about. And I think it's always a good idea to take a look back to the start, where we come from. And especially if we make huge changes to the UI. For those of you that are not really young, a style writer from the late 90s with a couple of toolbars. Which is pretty nice. You can see that we do not change too much. But I would have problems to deal with all the icons and buttons. Not that easy. And it didn't change with the updates. Got a little bit cleaner from the UI. But the functionality behind the toolbar is very complex. You get a lot of features and functions. And you need to understand what an icon means is. Let's say this compass throws. I believe it's a navigator. But you have to know that there is a navigator to understand what a navigator icon means. And after that, you can use this control to show it or not. And later version, a bit more clean UI. OK. And this liberal is starting from 3, 5, 4, and down there, 5. You didn't change too much. To be honest, I put the images onto the presentation to illustrate that our functionality grows and that we get more and clutter the toolbar. It's the opposite, it's true. We are working on a better UI. We do it for years, for more than 10 years. And it gets better and better. For instance, it is with the two toolbars at top, presenting the most important information to the user. It's pretty clear. It's similar to other programs, and you can use it easily. And this introduction of the sidebar, check it here, the lower part, we get more room in the conventional toolbars. So it was, it is still a clean interface. And yes, failed for my side. The question remains, what is it good for? What are toolbars good for? First of all, a toolbar is a quick access to frequently used functions. Often it is up used to present all the features and awesomeness to the user. I guess every one of you knows a program that is hard to use if you don't often start it and frequently use it because every function is cluttered in the toolbar. It's just a convenience feature for the experts. But it mustn't be. And especially for an office suite like Clip of the Office, which is used for many users, there has to be a precise and clear concept behind it. So quick access to frequently used functions, that's the purpose of a toolbar. What I scribbled above, by the way, is an example, I will talk later about it. And it should illustrate the idea. It is filled with icons that you may know. Of course, you can figure out that a disk, second icon from the left, a disk is likely a function to save the document. We made a number of icon tests over the last years that shows that a disk is really a good indicator for save. But next to it, left, new. It could be something different, but it isn't because it's the leftmost icon. Back to my notes. Increasing functionality, I told about it. You have to trust the icon. The save icon is very clear. And it's obvious what happens there. But if you move icons around and if you would move the new icon from the leftmost position to somewhere else in the toolbar, no one would be able to find it because the new icon is not that striking clear. It is often called the muscle memory. You know where you have to click to find a certain function. All the clipboard stuff. Undo, redo, left, right, not that clear always. But copy, paste, it's next to undo, redo. So it's kind of a positional information that you are using to figure out where a function is on the toolbar. And the most worst part of all these things is that new users require to learn all this stuff. It has to look at the toolbar, get the tooltips from it, and understand what it means to show icons like this one. Or it's just a stupid example. Let's say this one. I wouldn't know. So what could you do to improve the usability facing all of the issues? You could, of course, remove functionality from the toolbar. Make it cleaner. It's a good approach. I put the question mark onto it. I think developers are not so easy to convince to remove functionality from the toolbar. OK, so let's try another option, grouping. Grouping is always a good idea. Grouping makes it easy to quickly find a chunk in the amount of information. Leftmost kind of file information. The next one is about clipboard and so on. So this one, it's just a little bit space between groups. And you get an additional information. You can, of course, have also labels under it. It's not easy to read. It writes file, clipboard, format, objects, and help. Just an example. If you label the groups, it gives an additional information for the users. What else? You can use labels for the functionality because at least me, I always struggle with undo, redo. Is it really left to go back? Not so sure. If there is a label for this function, I'm absolutely clear. And if the style, I can hear the target, whatever it is. If there is a label style, you will know that it opens the menu for applying a style to the option. So at least the less often or less well-known functions should get a label. And finally, it's always a good idea to focus the user's attention to features that you want to acknowledge to the user. So it's just an example. The leftmost is new. You want to get the users are looking for a new, so you make it a larger icon. Users should use styling features, so you make style icon larger. And of course, you can do the same for objects and perhaps also help if you want to draw the attention to these features. And it works even better if you add some more information to it. If you add a modality like color in this case or add more details to the icons, for instance. If you have a very plain icon seam and you add more details to the relevant icons, it pops out of the crowd of the other functions. So features are possible. So what did we do? We put it onto a contextual groups. Because it's a simple canvas, you can enlarge the icons within the restrictions that we have in the process. We have three different sizes. So icons on the toolbar are small-sized, medium-sized, and large-sized in this case. And the large icons are the most relevant functions. I guess people are looking for save, for paste, which has also a drop down menu where you can get a special and whatever option paste has. Style gets a big menu. I showed you in advance. The idea is that we want to promote style rather than the direct formatting. And style should open the menu with all the styles. And a user can quickly change the appearing of a text rather than all the formatting options. And all the tools, the right part, this one, are hidden away a little bit. Because the idea is that our new user, we call him Benjamin, this Benjamin would likely just write a simple text. And he wants to make sure it is saved. That's the reason to make the save big. And he wants to format it in a certain way. That's all. But sometimes, he may want to add a table. And if you edit a table, you know, or in the past, rather in the past, we had changing UI. It flipped from a text editing mode to the table editing mode, which was kind of awkward. The idea is that most parts of the toolbar should remain static. And only a few things have to be depending on the context. That's why this thing is called contextual groups. The right most part is not any more tools. Because if you are in a table editing mode, you cannot add or maybe you can add an image. But you likely want to style the table. That's why the table style has a big icon. You may also want to change the background of the table and access also to the border. But what else? There are maybe a lot of more features in the table that could be changed. But it's not what you frequently do. So just this one. And similarly, for images, if you are in an image edit mode, if you have an image selected, you get everything is static from the left part. And disabled, in case you cannot use it, text formatting is not available for images. But styling could be an option. Right now, we do not have a style feature for images. But it could be added in the future. For instance, make it a water sign. I believe it's possible right now. I'm running a little bit out of time. So going over it more quickly, you have that? I think for images, relevant information or element functionality, it's cropping. It's at least me. I do it quite often. And reset, it's not that easy to find today. We hide the original size. It's a function that's called original size. We hide it really good a way in, at least an impress. It was not so easy because switching the resolution of the presentation back and resetting the image size was not easy to find. It's a function that is often used. What else? Chart mode? Of course, if we are in a chart, we need to get some kind of styling feature, which is on the same position. You can trust that a big icon on this position will present you with a kind of preset with something that enables you to quickly switch from one kind of visualization or modification to another one. And the chart would, for instance, change from a bar chart to a scatterplot or 3D chart or whatever. And finally, with shapes, it wasn't that easy to find relevant functions, but similar for this one. And this one is writer for writer. It was writer, how writer looks. For calc and impress, it should be similar to writer. Another goal is to not only have a static part within one module, so writer with file, clipboard, and formatting option, but also for other modules. Here in calc and impress, you also get file, clipboard, and formatting in this case with slightly different features, or properties, but the same functionality behind it. And again, the rightmost part is reserved for things that you contextually change. In the case of draw, it could look like this. You don't have usually a formatting feature, so it's rather kind of positioning that you want to change. Positioning feels a little bit like formatting. So the idea was to put, instead of the formatting, the position information into this menu, which means you have to disable it if you get to a text in draw. You disable the positioning features. And show formatting stuff in the contextual section. The lowest part here. Don't get a mouse here. OK. So my conclusion. The outlook for the future. Of course, we need to fix all the bugs. Stylers do not work really well. All the ideas of functions are not implemented. The aggregated functionality, for instance, of manipulating images is not available right now. We have bugs for the size-shrinked normal toolbar. It gets a kind of chevron where all the remaining items are collected in the menu. We do not have it right now. At least it's not really well-working. But if everything is done, we need of course a better configurability. Right now, it's a technical way to deal with it. It's a UI file that you change with Glade. You do not have a good means to add your own UI file. So it's a dirty hack. But you can change it, but it's very dirty. If that's all done, I think we need to muffinize the sidebar, meaning the sidebar should also get the freedom to be configured by the user. And if I say configured by the user, I have something in mind like Mozilla is doing for the Firefox in the customized mode. It should be kind of visivic configuration. You select the Unicomand and drag and drop it to the position where you want to get it. It has to be as simple as possible. And in a way, that's a challenge for us. Because in Mozilla, you have 20 or so functions. I get a few more because Adblock is an add-on. So we have hundreds of functions that needs to be offered to the user. And the UI is more complex in this case. But I think it should be easy in a way that every user can configure his own UI simply, share it with others, or download, for instance. So and finally, all the kudos go to the developers. And you can read the whole story, background information on the block. So thank you. Just ask. Up to now, there's a clear distinction between the top toolbar and the subbar in the sense that the toolbar must be static and the sidebar must be contextual. Now, is there a clear vision of what should go to the sidebar and what should go?