WEBVTT 00:00.000 --> 00:15.000 Okay everybody, attention is so, we are for the next talk of the day, so we have Michael 00:15.000 --> 00:22.000 Anne, here from collaboration with GVT and there talk of the events and to boys collaboration 00:22.000 --> 00:24.000 on and off collaboration. 00:24.000 --> 00:26.000 Oh, look at that, fantastic, thank you so much. 00:26.000 --> 00:27.000 Very good to have you come. 00:27.000 --> 00:30.000 Look at this. 00:30.000 --> 00:32.000 Just a quick background check. 00:32.000 --> 00:36.000 Who have you was here for my earlier talk downstairs, if you've raised a hand? 00:36.000 --> 00:38.000 Ah, good, I can give the same talk and all, no. 00:38.000 --> 00:39.000 That's brilliant. 00:39.000 --> 00:41.000 Oh, I mean, all these guys are cool, kids. 00:41.000 --> 00:43.000 Right, excellent, let's get on with it. 00:43.000 --> 00:46.000 So, one of the things that I should click on the right thing. 00:46.000 --> 00:52.000 One of the things that we're doing is talking about this new office suite we're building for the desktop, 00:52.000 --> 00:53.000 which is particularly cool. 00:54.000 --> 01:01.000 They've pun intended, bringing the same UI from collaboration line to the desktop, as you can see. 01:01.000 --> 01:04.000 And actually, we've been doing this for years. 01:04.000 --> 01:09.000 So, this was already compiled into our Chrome OS version, so if you have an Android phone, you can run collaboration 01:09.000 --> 01:10.000 and it looks beautiful for your phone. 01:10.000 --> 01:17.000 In fact, Skyler, smiling over here in the front row is responsible for the wonderful, you know, mobile UI, which is great. 01:17.000 --> 01:21.000 But we're used to put a bigger screen on that, so you install the APK on a Chrome OS book. 01:21.000 --> 01:25.000 You discover, actually, the whole application is there, it's just a responsive. 01:25.000 --> 01:30.000 And actually, probably if you resize your browser window too aggressively, you might discover you've become a phone. 01:30.000 --> 01:33.000 So, you know, be careful, what you wish for. 01:33.000 --> 01:34.000 Anyway, so it's always there. 01:34.000 --> 01:38.000 And if you compile our iPhone version right, you could also run that on a Mac. 01:38.000 --> 01:46.000 But in recent time, we've decided then to bring that as a full native app to the desktop. 01:46.000 --> 01:47.000 And so, why is that? 01:47.000 --> 01:49.000 Well, the first thing is, of course, offline support. 01:49.000 --> 01:54.000 The term and train system, I'm told about, is, you know, a wonder of the world. 01:54.000 --> 01:58.000 And, you know, people travel everywhere, but its connectivity is probably not great. 01:58.000 --> 02:03.000 And so, that's great, save the world, but without an internet connection. 02:03.000 --> 02:08.000 And so, yeah, bringing that to these long-suffering people is very helpful. 02:08.000 --> 02:10.000 And then, so that's one strand of goodness. 02:10.000 --> 02:13.000 The other strand of goodness is rich platform APIs. 02:13.000 --> 02:17.000 So, web browsers are created by rightfully paranoid people, 02:17.000 --> 02:19.000 so they turn off all interesting APIs. 02:19.000 --> 02:22.000 And even APIs, they do have, like, the clipboard APIs, 02:22.000 --> 02:25.000 are deliberately vandalized, tragically. 02:25.000 --> 02:29.000 So, you know, we used to be able to copy and paste rich text format into documents. 02:29.000 --> 02:32.000 So, you know, if you had, like, a chart in Microsoft Office, 02:32.000 --> 02:34.000 you could paste it into a collaborate online, 02:34.000 --> 02:38.000 and you got a chart, and it had axes and labels and formats and colours, 02:38.000 --> 02:40.000 and you could edit it as a chart. 02:40.000 --> 02:43.000 No longer, it has to be decided that rich text format is too dangerous. 02:43.000 --> 02:46.000 I know it's only a string, but it could be dangerous. 02:46.000 --> 02:49.000 So, that's been disabled in the new tipboard APIs. 02:49.000 --> 02:51.000 So, you can either have a really old lane API that does it, 02:51.000 --> 02:54.000 or a really brand new sparkly API that doesn't do it. 02:54.000 --> 02:56.000 So, sad. 02:56.000 --> 02:57.000 Quite typical of the browsers. 02:57.000 --> 03:00.000 It would be nice if we could work around those and actually do a good job. 03:00.000 --> 03:03.000 Because we get a lot of blame for copy and paste not working, 03:03.000 --> 03:07.000 and it's pretty, well, it will become our fault. 03:07.000 --> 03:09.000 Monty screen project management. 03:09.000 --> 03:12.000 So, you're sitting able to detect what projectors are attached 03:12.000 --> 03:14.000 and adapt dynamically to that. 03:14.000 --> 03:15.000 We need you to do that. 03:15.000 --> 03:17.000 You know, being able to discover your printers. 03:17.000 --> 03:18.000 Do you have a printer? 03:18.000 --> 03:20.000 What page sizes it and so on? 03:20.000 --> 03:23.000 Just the really basic stuff that the web just can't do, 03:23.000 --> 03:26.000 and then various other nasty image formats. 03:26.000 --> 03:28.000 So, here we go. 03:28.000 --> 03:30.000 It used to look like this with a browser, 03:30.000 --> 03:33.000 and a URL bar at the top, and now it looks like that without a browser, 03:33.000 --> 03:36.000 and a URL bar, but these are kind of similar, which is good. 03:36.000 --> 03:40.000 And the same UI then, one set of training, pretty welcome screen. 03:40.000 --> 03:42.000 We actually did a chunk of work to translate templates. 03:42.000 --> 03:43.000 So, you can have templates. 03:43.000 --> 03:46.000 Now, you can load and translate and show you all sorts of stuff. 03:46.000 --> 03:48.000 There's a little slide show that uses our engine, of course, 03:48.000 --> 03:52.000 animated videos, web jail transitions, introduction, very nice. 03:52.000 --> 03:56.000 And then, yeah, well, you know the classic look, something like that. 03:56.000 --> 03:59.000 So, same document then looks, you know, just different. 03:59.000 --> 04:02.000 I mean, I guess, you know, it's simplified, more discoverable, 04:02.000 --> 04:04.000 arguably more efficient. 04:04.000 --> 04:07.000 And based on lots of UI research, which perhaps will look at later, if you have time. 04:07.000 --> 04:10.000 Nice, you know, pieces like this. 04:11.000 --> 04:14.000 I'm trying to get to the collaboration bit, which is Stephens, Stephens, Baby. 04:14.000 --> 04:16.000 So, you know, we'll get there in a second. 04:16.000 --> 04:18.000 Nice integration with Max. 04:18.000 --> 04:20.000 If you are, if you're a Mac user, don't confess. 04:20.000 --> 04:22.000 Don't show your Mac here, or falls down. 04:22.000 --> 04:23.000 You get my get lynched, you know. 04:23.000 --> 04:25.000 So, what can you do? 04:25.000 --> 04:28.000 And this is really complementary to the classic mode. 04:28.000 --> 04:31.000 So, classic, of course, will continue to be there. 04:31.000 --> 04:32.000 It has huge code base. 04:32.000 --> 04:36.000 It has a whole load of fascinating integrations and things. 04:36.000 --> 04:39.000 It's a vital, a piece of the community backing that. 04:39.000 --> 04:41.000 But we really complement you to that. 04:41.000 --> 04:45.000 So, shipping and stripping lots of pieces out to simplify it. 04:45.000 --> 04:46.000 Right. 04:46.000 --> 04:49.000 And the fun bit, though, of course, is when I take this off. 04:49.000 --> 04:51.000 And then we talk about how we can then collaborate. 04:51.000 --> 04:52.000 Why don't they? 04:52.000 --> 04:56.000 Collaborate whilst, you know, swallowing the microphone. 04:56.000 --> 04:58.000 It sounds better inside. 04:58.000 --> 04:59.000 I promise you. 04:59.000 --> 05:01.000 And that's all good. 05:01.000 --> 05:02.000 Well, that'll work. 05:02.000 --> 05:03.000 Do you hear me? 05:03.000 --> 05:04.000 Okay. 05:04.000 --> 05:06.000 How do I operate this? 05:06.000 --> 05:08.000 Just the page down. 05:08.000 --> 05:09.000 Okay. 05:09.000 --> 05:13.000 So, yes. 05:13.000 --> 05:19.000 So, you have your great new offline office suite. 05:19.000 --> 05:22.000 And you have those multiple documents that are working on. 05:22.000 --> 05:24.000 And you're working on your private sailing yacht, 05:24.000 --> 05:28.000 document, and on your whatever archit. 05:28.000 --> 05:34.000 But you also want to actually do things that are not that private to yourself. 05:34.000 --> 05:39.000 You want to be one of these busy beavers that are collaborating and working together. 05:39.000 --> 05:45.000 So, you need some way to actually access documents that other people could access as well. 05:45.000 --> 05:53.000 And you're working on them collaboratively, as you know, from the online office suite. 05:53.000 --> 05:55.000 And you want all of that packed into one. 05:55.000 --> 06:01.000 So, you don't want to go from your local app to the browser just to collaborate. 06:01.000 --> 06:06.000 And then move back if you want to work on your sailing yacht again. 06:06.000 --> 06:13.000 So, this should all be in one local app that also has access to the browser, 06:13.000 --> 06:17.000 to the server documents that you want to collaborate on. 06:17.000 --> 06:26.000 And the great thing is, most of that is already there due to how we built this offline application. 06:26.000 --> 06:30.000 So, on the server in the in the server world, we have this server. 06:30.000 --> 06:40.000 And we have the client-side JavaScript that is responsible for drawing all the UI and the integration. 06:40.000 --> 06:45.000 And on the client side, what we have there is also for each of these tabs. 06:45.000 --> 06:50.000 We have this JavaScript bit that was otherwise run in the browser. 06:50.000 --> 06:55.000 And this server part crippled down a bit. 06:55.000 --> 07:00.000 We have that as well on the client side running inside that app. 07:00.000 --> 07:07.000 Now, coming from a desktop application developer perspective, you would say, 07:07.000 --> 07:09.000 it's kind of complicated. 07:09.000 --> 07:13.000 While you have the separation and stuff and talking. 07:13.000 --> 07:16.000 So, these two talk about the web socket. 07:16.000 --> 07:21.000 These two here in one application. 07:21.000 --> 07:26.000 They talk about a cross something that is called a fake web socket. 07:26.000 --> 07:29.000 But it's almost like a web socket. 07:29.000 --> 07:31.000 Just a bit simpler. 07:31.000 --> 07:33.000 And it's just added complexity, right? 07:33.000 --> 07:36.000 No, that's not a bug, that's a feature. 07:36.000 --> 07:48.000 Because this connection here between all things you see and all things that do the actual computing, 07:48.000 --> 07:56.000 you can switch that from doing a local fake communication with your local app back store. 07:56.000 --> 08:03.000 To doing transparently, reusing that connection, that web socket, as a real web socket, 08:03.000 --> 08:08.000 to your server and your document will stage up to sign. 08:08.000 --> 08:15.000 Because what you did here when you initially start to view that document, 08:15.000 --> 08:18.000 the client application tells to the server, 08:18.000 --> 08:22.000 I'll start to view this document, this remote document. 08:22.000 --> 08:27.000 And then the server tells you, okay, you can get the actual document for now. 08:27.000 --> 08:31.000 Why are this HDBS connection to whatever data store? 08:31.000 --> 08:38.000 So, we don't directly talk to the data store, which could be, 08:38.000 --> 08:42.000 next cloud or whatever, we'll just control this here. 08:42.000 --> 08:47.000 So, we have more flexibility, we can tell the client, 08:47.000 --> 08:51.000 just grab them from over there, we'll show them here, 08:51.000 --> 08:52.000 and you'll get them there. 08:52.000 --> 08:58.000 And then you have the initial idea of what that document at that moment is. 08:58.000 --> 09:05.000 And then when you want to actually operate on that, on modify it and change it, 09:05.000 --> 09:12.000 then we'll move on to the next slide. 09:12.000 --> 09:20.000 And that is when you start out with it. 09:20.000 --> 09:23.000 So, the first one, watching that document, 09:23.000 --> 09:27.000 and you're not actually yet modifying it. 09:27.000 --> 09:30.000 Because you just started up, and you're a lazy beaver, 09:30.000 --> 09:34.000 and most of the time you don't work anything. 09:34.000 --> 09:39.000 Just look at what others worked, and what others created. 09:39.000 --> 09:43.000 So, you're most of the time you're just watching these documents, 09:43.000 --> 09:45.000 and pretend you're working. 09:45.000 --> 09:50.000 But in reality, you're just delving away. 09:50.000 --> 09:54.000 We already have this connection to the server, which told us, 09:54.000 --> 09:59.000 this is the current state of the document that you're viewing there. 09:59.000 --> 10:02.000 And we have this real web socket connection, 10:02.000 --> 10:06.000 but it's kind of a lazy one, because we don't do anything across it. 10:06.000 --> 10:09.000 All the display here is done on the client side. 10:09.000 --> 10:15.000 The only thing we keep this web socket connection here is about this coming. 10:15.000 --> 10:20.000 So, the server and the server doesn't have to do much. 10:20.000 --> 10:26.000 It just has to take note, okay, there's somebody looking at this document, 10:26.000 --> 10:28.000 just about beaver at the moment. 10:29.000 --> 10:35.000 And more will might come, but I don't need to start any state on the server yet. 10:35.000 --> 10:39.000 Or much state, because there's not much to do. 10:39.000 --> 10:43.000 Now, more beaver is pop up. 10:43.000 --> 10:47.000 Two, three, fifty, hundreds of beavers. 10:47.000 --> 10:49.000 All looking at the same document. 10:49.000 --> 10:51.000 All lazy beavers. 10:51.000 --> 10:52.000 Nobody doing anything. 10:52.000 --> 10:56.000 So, they all have this document still in redone remote, 10:56.000 --> 11:01.000 because they're not really working to be true. 11:01.000 --> 11:03.000 So, what's about the server? 11:03.000 --> 11:09.000 The server can still stay green, because each of them now has this web socket connection 11:09.000 --> 11:12.000 to the server, but which doesn't have to do anything. 11:12.000 --> 11:17.000 It's just waiting for one of these beavers to wake up. 11:17.000 --> 11:25.000 And the server is still very conservative on its needs for performance. 11:25.000 --> 11:28.000 Because it doesn't have to do much. 11:28.000 --> 11:31.000 Now, beaver one wakes up. 11:31.000 --> 11:33.000 Oh my god, what happens? 11:33.000 --> 11:36.000 He wants to edit that document. 11:36.000 --> 11:40.000 Now, what's with all the other beavers? 11:40.000 --> 11:42.000 Hmm. 11:42.000 --> 11:46.000 Something has to change on the server's side. 11:46.000 --> 11:53.000 Ideally, there will be some dialogue popping up, 11:53.000 --> 11:56.000 but the dialogue got eaten by a software. 11:56.000 --> 11:57.000 I don't know. 11:57.000 --> 11:58.000 Okay. 11:58.000 --> 12:05.000 So, the dialogue will show you multiple opportunities or choices what to do. 12:05.000 --> 12:10.000 So, the one scenario is beaver one. 12:10.000 --> 12:12.000 Edit this document now. 12:12.000 --> 12:15.000 So, this web socket connection between the client, 12:15.000 --> 12:18.000 which until now did all the rendering here, 12:18.000 --> 12:22.000 and all the computation when you scroll through the document, 12:22.000 --> 12:25.000 was done on the client side until now. 12:25.000 --> 12:29.000 Now, this beaver starts to actually type something into the document, 12:29.000 --> 12:31.000 and edit these cartoons. 12:31.000 --> 12:34.000 So, this connection becomes hot. 12:34.000 --> 12:37.000 All the computation is now done on the server's side, 12:37.000 --> 12:39.000 on the server document. 12:39.000 --> 12:41.000 And then, channel back through the web socket, 12:41.000 --> 12:45.000 or the information, what actual pit maps to draw 12:45.000 --> 12:48.000 into the canvas on the client side. 12:48.000 --> 12:55.000 The other ones, for example, could say whatever the number one is doing, 12:55.000 --> 12:57.000 he's doing nonsense anyway. 12:57.000 --> 12:58.000 I don't care. 12:58.000 --> 13:00.000 I keep looking at the original one, 13:00.000 --> 13:03.000 because in the end he undo everything anyway. 13:03.000 --> 13:07.000 So, they keep these fake connections 13:07.000 --> 13:12.000 or these cool connections to these steps on the server's side, 13:12.000 --> 13:17.000 which still operate on this document completely client side. 13:18.000 --> 13:21.000 So, the server gets a bit hotter. 13:21.000 --> 13:23.000 Next scenario. 13:23.000 --> 13:28.000 All the beavers want to see what beaver number one does. 13:28.000 --> 13:33.000 So, even if they still don't actually modify the document themselves, 13:33.000 --> 13:36.000 they want to see what beaver one is doing, 13:36.000 --> 13:43.000 they're very interested beavers in seeing what their colleague actually does. 13:44.000 --> 13:46.000 And they might even decide so. 13:46.000 --> 13:47.000 There's first beaver over there, 13:47.000 --> 13:50.000 decides no, I don't want to edit. 13:50.000 --> 13:53.000 I'll keep sleeping and just blink once and twice 13:53.000 --> 13:55.000 and see what these other guys are doing. 13:55.000 --> 13:58.000 But this beaver actually wakes up and says, 13:58.000 --> 14:00.000 yeah, I'll operate on the document as well. 14:00.000 --> 14:06.000 And this is kind of the classical or the usual browser scenario. 14:06.000 --> 14:11.000 Very each of them has a hot and live web socket connection 14:11.000 --> 14:16.000 to the server and the server is doing all the computations 14:16.000 --> 14:20.000 for each of the three different ones and serving them. 14:20.000 --> 14:25.000 They're data depending on where they scroll to in the document. 14:25.000 --> 14:30.000 So, this is kind of heavy on the load over there. 14:30.000 --> 14:38.000 But give you the full flexibility of each one working on the document. 14:38.000 --> 14:43.000 Another scenario still a third scenario could be beaver number one. 14:43.000 --> 14:46.000 The middle one here says, I'll edit the document, 14:46.000 --> 14:52.000 but I'm not sure I'll do it right and maybe the others are not interested anyway. 14:52.000 --> 14:58.000 So we could have a third option that they operate on the local copy of the document 14:58.000 --> 15:03.000 and then from the server perspective everything keeps staying cool. 15:03.000 --> 15:08.000 Each of them are looking at the local kind of copies each of them 15:08.000 --> 15:11.000 doing their computations on the local side. 15:11.000 --> 15:15.000 And this one just having a local copy that they're moderating 15:15.000 --> 15:18.000 that they're operating on and actually modifying. 15:18.000 --> 15:22.000 And then some later time they'll have to save it back. 15:22.000 --> 15:27.000 And if multiple people want to save back then, of course we have these problems 15:27.000 --> 15:36.000 of doing the merging at that time. 15:36.000 --> 15:41.000 But that's a lighter time because for now they are just each of them editing it, 15:41.000 --> 15:43.000 faithfully locally. 15:43.000 --> 15:47.000 And what happens then we'll see later. 15:47.000 --> 15:51.000 Because can I get this already anyway? 15:51.000 --> 15:53.000 Quite. 15:53.000 --> 15:54.000 We're working on it. 15:55.000 --> 16:00.000 And there's of course some still some decisions to be made. 16:00.000 --> 16:03.000 Some naughty parts. 16:03.000 --> 16:07.000 And so we need to decide which of these scenarios actually makes sense 16:07.000 --> 16:12.000 to a user base which of them should be prioritized to implement 16:12.000 --> 16:15.000 and which might be nice to have additions. 16:15.000 --> 16:19.000 The protocol haven't been taken out completely yet. 16:19.000 --> 16:26.000 And of course with all these hundreds of beavers popping up at unpredictable times 16:26.000 --> 16:29.000 during the workflow. 16:29.000 --> 16:34.000 There's a bit of a space explosion in the state machine. 16:34.000 --> 16:38.000 What happens when people one is doing a and then another beaver comes up 16:38.000 --> 16:41.000 and another beaver comes up while the second one comes up. 16:41.000 --> 16:47.000 So yeah, we have to be careful that our beautiful implementation there 16:47.000 --> 16:51.000 where we had just this easy switch from a fake socket to a true web socket. 16:51.000 --> 16:57.000 And we get that right so that we don't mix up the different web sockets 16:57.000 --> 17:00.000 that each one gets. 17:00.000 --> 17:06.000 And the great news is if you want to work with us on that then 17:06.000 --> 17:12.000 I think we get over to the slides from Michael again. 17:12.000 --> 17:16.000 Because then there's this hack for us coming up. 17:16.000 --> 17:17.000 Who? 17:17.000 --> 17:18.000 Who? 17:18.000 --> 17:20.000 Can we see them in the back? 17:22.000 --> 17:23.000 Lovely. 17:23.000 --> 17:26.000 So we saved lots of exciting different options for getting it wrong. 17:26.000 --> 17:28.000 You know that's even the absolutely brilliant. 17:28.000 --> 17:31.000 The state machine we already talked earlier about weirdness is in state machines 17:31.000 --> 17:34.000 and we're going to find a whole lot more from user interaction. 17:34.000 --> 17:36.000 Obviously we talked about the conflicts. 17:36.000 --> 17:40.000 If you're on a train for an hour and someone else is editing the document 17:40.000 --> 17:44.000 of a problem and that problem is not made any better by hyper complicated things. 17:44.000 --> 17:47.000 It is made better by super easy comparison of what changed. 17:47.000 --> 17:51.000 So I think that's also going to be a big part of resolving the idea of the connection 17:51.000 --> 17:56.000 broke and now we need to make something good out of it later on. 17:56.000 --> 18:02.000 So the rest of this I guess is mostly looking at UI UX stuff 18:02.000 --> 18:07.000 and some of the things we've been doing there and just a bit of the improvements 18:08.000 --> 18:10.000 So we have quite a lot of telemetry. 18:10.000 --> 18:12.000 So actually some of the things that we're doing now 18:12.000 --> 18:15.000 flow out of watching what users actually do. 18:15.000 --> 18:17.000 I had a graph of all sorts of things. 18:17.000 --> 18:21.000 This is a nice graph of what operation is following what other operation. 18:21.000 --> 18:24.000 So you know you do a mouse move and then you do something else. 18:24.000 --> 18:29.000 And so it's kind of nice to see what's what's going on people are doing. 18:29.000 --> 18:33.000 That's an internal service and also somewhat some of our demo telemetry there 18:33.000 --> 18:36.000 that we watch and try and optimize the product. 18:36.000 --> 18:39.000 Yeah, particularly play that way obviously. 18:39.000 --> 18:42.000 And some of the optimizations that come out of that are pretty nice then. 18:42.000 --> 18:45.000 So making the UX just much prettier in a whole lot of ways. 18:45.000 --> 18:47.000 I have one minute and 19. 18:47.000 --> 18:49.000 So we're just going to with through some of the nice things 18:49.000 --> 18:51.000 about a context support. 18:51.000 --> 18:53.000 So lots of functionality we already had. 18:53.000 --> 18:56.000 But just making it nicer and more easy to get to. 18:56.000 --> 18:59.000 And then use more intuitive and functional. 18:59.000 --> 19:00.000 You're adding a slide. 19:00.000 --> 19:02.000 It would be nice to pick the layout when you're adding it. 19:02.000 --> 19:06.000 I'll just have a drop down better responsive tabs grouping and so on. 19:06.000 --> 19:10.000 We've also got a whole lot of new features that are coming actually really soon in the next month or so. 19:10.000 --> 19:14.000 So there you can play with them already there in the code base but just not released. 19:14.000 --> 19:16.000 So nice to page view there. 19:16.000 --> 19:19.000 Whole new interoperable table design thing. 19:19.000 --> 19:20.000 Thanks to Marcus and the. 19:20.000 --> 19:25.000 Balish and Marcus community hero of all that we love so much. 19:25.000 --> 19:31.000 Multiple sheet views which is frequently requested so you can filter staff and not corrupt someone else's view. 19:31.000 --> 19:35.000 So, you know, you can see different different things say there's five departments. 19:35.000 --> 19:40.000 Each department can see different different different view of the same underlying data. 19:40.000 --> 19:42.000 Also, so good things from Skylar. 19:42.000 --> 19:44.000 Have you given your mobile talk yet? 19:44.000 --> 19:46.000 Oh, you just now. 19:46.000 --> 19:47.000 Oh, well, there you are. 19:47.000 --> 19:48.000 So here for you got that. 19:48.000 --> 19:50.000 Follow me presentation is coming out later. 19:50.000 --> 19:52.000 So I'm not going to ruin Pranam's talk too badly. 19:52.000 --> 19:54.000 Yeah, absolutely. 19:54.000 --> 19:57.000 We have a whole bit of improved settings. 19:57.000 --> 20:00.000 I just really simplifying the huge massive settings. 20:00.000 --> 20:02.000 Lots of work on interoperability. 20:02.000 --> 20:04.000 So this is the most toxic waste. 20:04.000 --> 20:06.000 Oh, let's see there you go. 20:06.000 --> 20:09.000 The toxic waste of our interoperability work. 20:09.000 --> 20:11.000 And we're just hammering that down to squash it. 20:11.000 --> 20:12.000 I get that that's good. 20:12.000 --> 20:13.000 And cool days. 20:13.000 --> 20:17.000 If you can't make it Monday, Tuesday to come and make this rock then come to see us in Hamburg. 20:17.000 --> 20:22.000 And thank you so much to all good people that do so much of the hard work. 20:22.000 --> 20:24.000 And yeah, I don't have any more bevels. 20:24.000 --> 20:27.000 I think we gave 300 out today. 20:27.000 --> 20:28.000 Oh, if you won't bevels. 20:28.000 --> 20:29.000 Oh, brilliant. 20:29.000 --> 20:30.000 Where are they? 20:30.000 --> 20:31.000 It's crazy about the audience. 20:31.000 --> 20:34.000 Yeah, so Scarlet should have a whole suitcase full of, you know, there you go. 20:34.000 --> 20:37.000 And we need special bevel insurance to, you know, 20:37.000 --> 20:40.000 So we have this very hard work in creature, you know, 20:40.000 --> 20:44.000 and then we've picked them as our mascot, you know, for doing all sorts of things. 20:44.000 --> 20:45.000 Don't fight. 20:45.000 --> 20:46.000 There'll be a hundred more tomorrow. 20:46.000 --> 20:47.000 Something like that, at least. 20:47.000 --> 20:52.000 And we also have a comic called The Open Roads of Freedom 20:53.000 --> 20:59.000 that talks about open source and communities and all sorts of good things around that. 20:59.000 --> 21:02.000 So do you have a play with that should be slightly amusing. 21:02.000 --> 21:05.000 And yeah, look at that. 21:05.000 --> 21:07.000 Handles, trains and planes smoothly. 21:07.000 --> 21:08.000 That's what we need. 21:08.000 --> 21:11.000 And all sorts of new collaboration, locking things stuff. 21:11.000 --> 21:13.000 Thanks for everyone who contributes. 21:13.000 --> 21:16.000 So I know many people here contribute to both Librofist and 21:16.000 --> 21:18.000 Calabrofist and we think you're awesome. 21:18.000 --> 21:19.000 So keep it up. 21:19.000 --> 21:20.000 You'd be very patient. 21:20.000 --> 21:21.000 Thank you so much. 21:21.000 --> 21:29.000 We have time for a question. 21:29.000 --> 21:31.000 We have a few minutes for questions. 21:31.000 --> 21:33.000 Why don't I have a bevel yet? 21:33.000 --> 21:35.000 So Skyler's under arm is really quite something. 21:35.000 --> 21:36.000 Look at this, you know. 21:36.000 --> 21:40.000 This is years of training in those sports fields. 21:40.000 --> 21:41.000 Oh, yeah, yeah. 21:41.000 --> 21:43.000 So, you know, questions? 21:43.000 --> 21:44.000 Any questions? 21:44.000 --> 21:46.000 Yeah, would you like your questions? 21:46.000 --> 21:47.000 Yeah. 21:47.000 --> 21:50.000 I noticed recently there was a slight change 21:50.000 --> 21:53.000 for the colabro online version, which is usually 21:53.000 --> 21:55.000 integrated in the next thought. 21:55.000 --> 21:58.000 That the icons and the UI changed to be from 21:58.000 --> 22:00.000 B monochrome to more colorful. 22:00.000 --> 22:01.000 Yeah. 22:01.000 --> 22:05.000 So this is an intentional move towards back from 22:05.000 --> 22:07.000 We do everything monochrome. 22:07.000 --> 22:10.000 And now we do it back in colorful icons. 22:10.000 --> 22:11.000 I mean, personally, I find it nice. 22:11.000 --> 22:14.000 But I just wanted to know if this wasn't intentional change 22:14.000 --> 22:18.000 because of better UI and better recognizableity of the icons. 22:18.000 --> 22:19.000 Yeah. 22:19.000 --> 22:22.000 So you would be amazed at the impact that 22:22.000 --> 22:25.000 color has on people and the ability to distinguish 22:25.000 --> 22:27.000 components from each other. 22:27.000 --> 22:30.000 You know, like, we do lots of heavy lifting all day every day. 22:30.000 --> 22:33.000 And it's surprising when the most positive feedback you get 22:33.000 --> 22:36.000 is like, oh, the color, you know, I feel like, oh, 22:36.000 --> 22:38.000 my look at it and it's like, oh, this is, you know, 22:38.000 --> 22:40.000 what I mean, expecting familiar with. 22:40.000 --> 22:42.000 So, so yes, the color thing turns out to be really 22:42.000 --> 22:45.000 really helpful for people seeing which of their spreadsheets 22:45.000 --> 22:47.000 and which of their presentations and so on. 22:47.000 --> 22:50.000 I mean, it's much loved and we've persuaded the next cloud. 22:50.000 --> 22:51.000 So we will support it. 22:51.000 --> 22:53.000 I think to have the status bar at the bottom, which they'd 22:53.000 --> 22:56.000 carefully hidden and various other things that quite useful. 22:56.000 --> 23:00.000 So I think this, yeah, I mean, it's a really very mature 23:00.000 --> 23:02.000 office productivity suite. 23:02.000 --> 23:04.000 And it has a lot of features for a reason. 23:04.000 --> 23:06.000 And we should really be showing it to people. 23:06.000 --> 23:08.000 So they don't get where's there's no ruler. 23:08.000 --> 23:09.000 Yeah, well, actually there is a ruler. 23:09.000 --> 23:12.000 It's just being turned off and wouldn't it be nice if it wasn't? 23:12.000 --> 23:15.000 So yeah, so there's some changes in the options there. 23:15.000 --> 23:17.000 I think the monochrome stuff is probably still there. 23:17.000 --> 23:21.000 If you are a lover of monochromatic, heavy, bold icons, 23:21.000 --> 23:24.000 but yeah, I think that is a change this haven't recently. 23:24.000 --> 23:25.000 Another question? 23:25.000 --> 23:27.000 Fantastic. 23:27.000 --> 23:28.000 Huh? 23:28.000 --> 23:29.000 Going once? 23:29.000 --> 23:30.000 No. 23:30.000 --> 23:32.000 Ah, okay. 23:32.000 --> 23:39.000 So I'm very happy to collaborate with colleagues that are in the user experience community. 23:39.000 --> 23:41.000 So it's the user data open source. 23:41.000 --> 23:44.000 And the answer is yes, for you, HIKO, I share it with you, of course. 23:44.000 --> 23:52.000 Well, see what we're trying to do is we make sure that there's no user identifiable anything in it. 23:52.000 --> 23:55.000 And as far as I'm where, hand on heart, there isn't. 23:55.000 --> 23:57.000 But I'm not going to release lots of data. 23:57.000 --> 24:00.000 If there's even a small risk that there might be something in there. 24:00.000 --> 24:03.000 See, you know, commands we can have all sorts of parameters added to them. 24:03.000 --> 24:05.000 And we filter those off, which actually phrase away. 24:05.000 --> 24:09.000 A lot of useful information like what page size would you like or what thing. 24:09.000 --> 24:12.000 But they also have like user data in them. 24:12.000 --> 24:16.000 So we try and filter those things and so yes, it's not publicly shared. 24:16.000 --> 24:20.000 But if people are interested in design and interested in the stats and seem sensible, 24:20.000 --> 24:22.000 then we could share them. 24:22.000 --> 24:23.000 Yeah. 24:23.000 --> 24:24.000 Good question. 24:24.000 --> 24:25.000 Love it. 24:25.000 --> 24:27.000 Last question. 24:27.000 --> 24:29.000 Last question to finish. 24:29.000 --> 24:30.000 Ah. 24:30.000 --> 24:31.000 Again, you. 24:31.000 --> 24:32.000 That's all right. 24:32.000 --> 24:34.000 I'll give you the microphone. 24:34.000 --> 24:39.000 But the question is obvious if you are now also targeting a desktop environment, 24:39.000 --> 24:41.000 what happens with Librovis in the long term. 24:41.000 --> 24:45.000 Are there any plans to become an independent project? 24:45.000 --> 24:48.000 Because Librovis and Colabra on the desktop, 24:48.000 --> 24:50.000 I mean, it makes no sense of both products. 24:50.000 --> 24:53.000 If both products will fill the same requirements, 24:53.000 --> 24:56.000 when it just comes to editing documents. 24:56.000 --> 24:58.000 If you've ever watched, yes, minister, 24:58.000 --> 25:02.000 you'll see this episode where he is asked a question he doesn't want to answer. 25:02.000 --> 25:05.000 And he says, I'm glad you asked that question. 25:05.000 --> 25:08.000 And that is a question a lot of people wanting to know the answer for. 25:08.000 --> 25:09.000 And he goes on for a very long time. 25:09.000 --> 25:11.000 And it forgets what the question was in the end. 25:11.000 --> 25:14.000 Hopefully I've achieved a similar effect with fewer words. 25:14.000 --> 25:17.000 No, no, no. 25:17.000 --> 25:19.000 So Librovis is really, really good at lots of things. 25:19.000 --> 25:22.000 And it fills another niche. 25:22.000 --> 25:23.000 I would argue. 25:23.000 --> 25:25.000 And it's controlled obviously by the document foundation, 25:25.000 --> 25:27.000 who own that brand and that product. 25:27.000 --> 25:29.000 And we'll do what they want with it. 25:29.000 --> 25:32.000 We're obviously focused on a slightly different demographic. 25:32.000 --> 25:37.000 And that familiarity in terms of training and user experience for online and offline at same time. 25:37.000 --> 25:40.000 It just really helps our product maximum. 25:40.000 --> 25:44.000 Good news is vast amounts of the core work we do is completely shared. 25:44.000 --> 25:48.000 So lots of the features I've shared here are there in Librovis as well. 25:48.000 --> 25:50.000 And I think that's a vital strength. 25:50.000 --> 25:53.000 Writing your own office suite from scratch is just a folly. 25:53.000 --> 25:57.000 When there's so much great open source office technology out there. 25:57.000 --> 25:58.000 So I hope that helps. 25:58.000 --> 25:59.000 Thanks, guys. 25:59.000 --> 26:00.000 Very good. 26:00.000 --> 26:01.000 Thank you, Mark. 26:01.000 --> 26:02.000 Thank you. 26:02.000 --> 26:03.000 Thank you. 26:03.000 --> 26:05.000 Thank you. 26:05.000 --> 26:07.000 Thank you. 26:07.000 --> 26:08.000 So.