WEBVTT 00:00.000 --> 00:16.240 Hi, so I'm Scarlett Gray, and Clapper Office can finally run on mobile Linux. 00:16.240 --> 00:26.360 So I guess a bit of background may be necessary, so I've been to first in for a couple 00:26.360 --> 00:32.080 years, and how many of you have been to first in before? 00:32.080 --> 00:40.520 Okay, most of you, almost all of you, each year I've given a little bit of a presentation, 00:40.520 --> 00:48.880 I work at Clapperer, so I make office software, and I specifically make mobile office 00:48.880 --> 00:57.520 software, and up until this year, that's been on Android and iOS. 00:57.520 --> 01:02.560 Here is a presentation I gave last year, the in-flight Wi-Fi is bad, but my presentation 01:02.560 --> 01:05.040 is still good. 01:05.040 --> 01:12.080 It was about Clapper Office on Android and iOS, and it was a great presentation, it 01:12.080 --> 01:20.400 talked about how we had nice integration with mobile operating systems, I showed off present 01:20.400 --> 01:25.880 from the phone, and after my talk, people came to me and they said, hey, Scarlett, that 01:25.880 --> 01:34.240 was a great talk, but I use mobile Linux, can I use this? 01:34.240 --> 01:40.320 I heard you do mobile stuff, and people have been, in fact, saying that to me last year, 01:40.320 --> 01:50.320 the year before, I heard you do mobile stuff, can I use it on Linux, because though much 01:50.320 --> 01:56.040 of the wider world is stuck in the Apple and Google ecosystems, here we have a lot of 01:56.040 --> 02:01.960 people who really love mobile Linux, and it would be beautiful if we could get Clapper 02:02.040 --> 02:11.040 Office running on that, a mobile optimized office suite on mobile Linux. 02:11.040 --> 02:13.040 But there was no good way. 02:13.040 --> 02:21.640 I had to tell them, no, not really, there was a GTK app, an app that is intended to work 02:21.640 --> 02:28.040 similarly to the iOS and Android apps, but it's really only for debugging problems in 02:28.120 --> 02:36.120 them, it's not great, it's required to be run via the command line, it's that's all 02:36.120 --> 02:41.160 of the documentation, that is the whole of the documentation on the GTK app, it is intended 02:41.160 --> 02:48.360 for development use only, it's not digital compile and it's not very good, but could 02:48.360 --> 02:53.240 you run maybe in next cloud server on your phone, well kind of maybe, next have really 02:53.240 --> 02:57.880 wants to be publicly accessible, if you do that then you're going to start having a complaint 02:57.880 --> 03:02.920 that you're not provisioning certificates and giving it access to the wider world, it's 03:02.920 --> 03:11.320 kind of a pain, next cloud is great, if you're running a server for lots of people to use 03:11.320 --> 03:16.760 and share documents, it's not great if you're one person who wants to have office on their phone, 03:17.640 --> 03:22.440 it's not designed for this, right, next cloud is great as solving the problem it solves, 03:22.440 --> 03:29.720 it's terrible it's solving this, it's a bad idea, meanwhile back at cloud era, this is Michael 03:29.720 --> 03:35.000 Meeks, he's my boss's boss, he says we have this really great online office suite, 03:36.200 --> 03:43.800 wouldn't it be nice if our customers, people who used us, could get a consistent local UI, 03:43.800 --> 03:49.400 wouldn't it be nice if they could on their desktop, have something that looked kind of like 03:49.480 --> 03:53.640 clouder online, wouldn't it be nice if we had better system integration because 03:53.640 --> 04:01.320 copian paste on web is actually quite painful to write code for, and so we came up with clouder 04:01.320 --> 04:07.240 office desktop and we started writing this, these are some people who worked on it, there's 04:07.240 --> 04:16.600 software up there and tour and candy and they started work on the mobile, on the desktop office suite for 04:17.080 --> 04:26.680 Linux Mac and Windows and they were working on it based on the code that we already had for mobile, 04:26.680 --> 04:32.280 can we take some of the same sort of ideas about how we integrate with this system and can we 04:32.280 --> 04:37.960 bring it to desktop and actually there's a lot more people who who worked on it alongside them, 04:37.960 --> 04:44.360 not full time but who contributed patches that helped or who did mobile work that went into it 04:45.320 --> 04:52.200 and actually in fact the whole country of the community helped, right, because all of the code 04:52.200 --> 04:58.200 that that's there is based on the web stuff that we have already and everyone who's contributed 04:58.200 --> 05:04.920 to clouder and even liberal offices the whole has helped to make that better and more robust. 05:05.560 --> 05:18.040 So it's based on your platform web view it takes the online bits that we have in clouder online 05:18.040 --> 05:23.160 and it runs a server on your device with a separate communication layer that pretends to be a 05:23.160 --> 05:27.960 web socket so that the online bits that we have still work but you don't need to run a full server 05:28.040 --> 05:37.080 on your device and it runs on Linux so can we run it on mobile Linux? I have a couple of mobile 05:37.080 --> 05:44.520 Linux firms one of them was given to me by Java and I got one of my own they are a platform and 05:44.520 --> 05:51.960 a poker firm. I don't have an arm machine to build anything on and it's very very close to 05:51.960 --> 05:59.160 CFP when this releases so I need to get something quick. I package a collaborative office for 05:59.960 --> 06:07.720 next and I use some online next build service to get a first copy up and running and I have to 06:07.720 --> 06:11.640 mess around and copy around different parts of the build afterwards it's a horrible process it's 06:11.640 --> 06:18.360 terrible you should never use this but it works and this is a photo that I took around 30 minutes 06:18.360 --> 06:26.520 before the CFP closed of me writing my CFP with a version of collaborative office running on a phone. 06:32.040 --> 06:38.680 Thank you thank you I've got some problems right so here you can see the UI is still the 06:38.680 --> 06:43.560 desktop UI and it's got a the document is probably locked and has been opened as read over here 06:43.560 --> 06:47.960 it can't actually edit any of your files which is a little bit of a problem for an office suite. 06:49.000 --> 06:55.960 So let's see what we can fix. Oh yeah that's that's the time that's 2325 on the 06:55.960 --> 07:07.160 day the CFP closed it's it's quite late. Oh yeah yeah yeah more problems the new document page 07:07.960 --> 07:12.680 is rather payable to you as you can see the templates are all cut off that you can kind of work 07:12.680 --> 07:17.320 around this if you have if you have your phone in landscape mode but it's not great. 07:18.840 --> 07:24.760 Okay let's see what we can fix. So this the document is locks and has been open read only that 07:24.760 --> 07:29.800 that's completely fixed when we change the build process to build a flat pack that just went away. 07:32.360 --> 07:39.240 This one this this is half fixed we have the UI we need to make sure that it shows on mobile 07:39.320 --> 07:46.600 Linux right now a desktop is is hard coded so that it will show the desktop UI but we can 07:46.600 --> 07:50.840 change it to be based on say your screen size and that will that will fix that one. 07:52.120 --> 07:57.880 This one is a bit more a problem because we don't have the UI written so we need to 07:57.880 --> 08:02.760 write some better UI for showing templates right now as I mentioned you can use this work around 08:02.760 --> 08:08.120 where you have the your phone in landscape mode but it will would be nice to fix it. 08:09.800 --> 08:16.600 We also need a way of detecting mobile Linux because if we don't have a way of detecting mobile 08:16.600 --> 08:21.560 Linux then we don't know when to apply these automizations and and when to show you the the normal 08:21.560 --> 08:28.040 desktop UI I don't have a good way of doing this. If you if you know something please tell me 08:29.560 --> 08:36.120 we can look at the the kernel name that that's the thing I thought of because maybe you're using post 08:36.120 --> 08:43.320 market OS and that's probably probably quite mobile coded um we also have things in our 08:43.320 --> 08:48.520 web code to look and look at your screen size but that doesn't work in smaller windows so it will 08:48.520 --> 08:54.520 be really nice if if any of you know a way to detect whether a device is mobile Linux please send 08:54.520 --> 09:02.200 me a message send me an email scallid.grey at clover.com thanks okay but it lives it's usable 09:02.600 --> 09:10.200 it lives we can present from it you can get it right now off of the store it could be better there's 09:10.200 --> 09:16.360 lots of problems you can help please please help thank you