Lightning talk session Come and tell us your most recent hack - in 5 mins!
This is a modal window.
Das Video konnte nicht geladen werden, da entweder ein Server- oder Netzwerkfehler auftrat oder das Format nicht unterstützt wird.
Formale Metadaten
| Titel |
| |
| Serientitel | ||
| Anzahl der Teile | 644 | |
| Autor | ||
| Mitwirkende | ||
| Lizenz | CC-Namensnennung 2.0 Belgien: Sie dürfen das Werk bzw. den Inhalt zu jedem legalen Zweck nutzen, verändern und in unveränderter oder veränderter Form vervielfältigen, verbreiten und öffentlich zugänglich machen, sofern Sie den Namen des Autors/Rechteinhabers in der von ihm festgelegten Weise nennen. | |
| Identifikatoren | 10.5446/41440 (DOI) | |
| Herausgeber | ||
| Erscheinungsjahr | ||
| Sprache |
Inhaltliche Metadaten
| Fachgebiet | ||
| Genre | ||
| Schlagwörter |
FOSDEM 2018611 / 644
2
3
5
6
7
8
10
12
16
18
27
29
30
31
32
34
39
46
47
48
55
57
58
61
64
67
76
77
80
85
88
92
93
98
101
105
110
114
115
116
118
121
123
128
131
132
133
134
140
141
142
143
146
147
149
162
164
171
173
177
178
179
181
182
184
185
187
188
189
190
191
192
200
201
202
204
205
206
207
211
213
220
222
224
229
230
231
233
237
241
242
243
250
252
261
265
267
270
276
279
280
284
286
287
288
291
296
298
299
301
302
303
304
305
309
310
311
312
313
316
318
319
322
325
326
327
329
332
334
335
336
337
340
344
348
349
350
354
355
356
359
361
362
364
365
368
369
370
372
373
374
376
378
379
380
382
386
388
389
390
393
394
396
400
401
404
405
406
407
409
410
411
415
418
421
422
423
424
426
427
429
435
436
439
441
447
449
450
451
452
453
454
457
459
460
461
462
464
465
470
472
475
477
478
479
482
483
486
489
490
491
492
493
494
496
497
498
499
500
501
503
506
507
508
510
511
512
513
514
515
517
518
519
522
523
524
525
527
528
534
535
536
538
539
540
541
543
544
545
546
547
548
550
551
553
554
555
559
560
561
564
565
568
570
572
573
574
576
578
579
580
586
587
588
590
593
594
596
597
598
601
603
604
606
607
608
610
613
614
615
616
618
619
621
623
624
626
629
632
633
634
635
636
639
641
644
00:00
E-FunktionInformationsmanagementMathematikObjektverfolgungAggregatzustandSystemverwaltungGoogolCodeDemo <Programm>Physikalisches SystemMKS-SystemZweiSchlussregelComputeranimation
00:38
FreewareZustandsmaschinePerspektiveKollaboration <Informatik>AggregatzustandVirtuelle MaschineElektronischer DatenaustauschBenutzerfreundlichkeitFormale GrammatikElement <Gruppentheorie>Attributierte GrammatikAnalysisGraphDatenstrukturAbstraktionsebeneKnotenmengeViewerTabelleRefactoringMathematikErwartungswertApp <Programm>InformationStandardabweichungSchreib-Lese-KopfServerSchedulingSpezialrechnerGeradeElektronische UnterschriftHyperlinkAvatar <Informatik>WebDAVBasis <Mathematik>ClientPatch <Software>ObjektverfolgungBitrateQuaderProgrammfehlerWeg <Topologie>DatenbankMathematikRechter WinkelLokales MinimumElektronische UnterschriftElektronische PublikationBildgebendes VerfahrenPatch <Software>Element <Gruppentheorie>GeradeSoftwareentwicklerKomplex <Algebra>Endliche ModelltheorieFront-End <Software>BeweistheorieServerOrdnung <Mathematik>DADSVersionsverwaltungSchedulingBenutzerbeteiligungVerzweigendes ProgrammStreaming <Kommunikationstechnik>TabelleKollaboration <Informatik>MereologieBildschirmmaskeTropfenSchreib-Lese-KopfLastWhiteboardHyperlinkGebäude <Mathematik>Office-PaketMultiplikationsoperatorGewicht <Ausgleichsrechnung>InformationsspeicherungRahmenproblemBildschirmfensterKartesische KoordinatenDokumentenserverVerknüpfungsgliedLesen <Datenverarbeitung>Äußere Algebra eines ModulsPerspektiveWeb-SeiteTouchscreenZustandsmaschineAggregatzustandAudiodateiAttributierte GrammatikAutorisierungFormale GrammatikGraphRichtungStabSoftwareMultiplikationCliquenweiteFitnessfunktionMakrobefehlRelativitätstheorieClientBasis <Mathematik>GraphfärbungDateiformatComputeranimation
10:30
Formale GrammatikMathematikApp <Programm>ErwartungswertInformationStandardabweichungWeb SiteVerschlingungSelbst organisierendes SystemComputeranimation
11:02
DigitalfilterHumanoider RoboterViewerParserBinärdatenBenutzerfreundlichkeitSchreiben <Datenverarbeitung>RouterDesintegration <Mathematik>MaßerweiterungAbschattungSoftwaretestFontSchnelltasteWeb-SeiteFreewaret-TestSystem-on-ChipFormale GrammatikMathematikApp <Programm>ErwartungswertInformationStandardabweichungAdditionMailing-ListeArithmetisches MittelProgrammierungTemplateFunktionalElektronische PublikationVerschlingungShape <Informatik>KonfigurationsraumGeradeFontKartesische KoordinatenProblemorientierte ProgrammierspracheProjektive EbeneInformationt-TestSchreiben <Datenverarbeitung>Spezielle unitäre GruppeStandardabweichungMultiplikationsoperatorMathematikMaßerweiterungAbschattungOpen SourceMereologieOffice-PaketTouchscreenVerzeichnisdienstBitTeilmengeKalkülSoftwaretestE-MailFramework <Informatik>InstantiierungDatenverwaltungWeb SiteWeb-SeiteFreewareOffene MengeFamilie <Mathematik>Computeranimation
17:31
FlächeninhaltNormalvektorNotebook-ComputerRechter WinkelGrundsätze ordnungsmäßiger DatenverarbeitungComputeranimation
18:26
ATMCompilerLesezeichen <Internet>NormalvektorTabelleR-ParitätMehrrechnersystemSpeicherbereichsnetzwerkQuellcodeBildschirmmaskeMeta-TagEingebettetes SystemSpezialrechnerResultanteMaschinencodeDezimalbruchGarbentheorieFarbverwaltungssystemMagnettrommelspeicherGammafunktionHilfesystemEinfügungsdämpfungZeichenketteElektronische PublikationDelisches ProblemTypentheorieMAPEindeutigkeitInhalt <Mathematik>Formale SpracheMaßerweiterungWidgetTexteditorWeb-SeiteSchnittmengeSchreiben <Datenverarbeitung>WikiPunktUmwandlungsenthalpieComputeranimation
23:08
InformationComputeranimation
23:36
Dienst <Informatik>PunktwolkeFlussdiagramm
Transkript: Englisch(automatisch erzeugt)
00:06
Okay, so everybody, last slot of the day, lightning talks, we got actually four people signed up here. First one will be, oh, rules are six minutes, and that will be hard and forced, so ten
00:24
seconds to the end of the talk, we're just going to stand up and applaud, so it's a very nice and winsome way to cut you off. Okay, first off, Svante. Okay, I call it distributed ODF applications, where is it, is it going this way, okay.
01:02
So from a bird perspective, right, ODF applications are just an, can we, Tossen, Tossen, I've got a screen problem, can we switch that it's fit, should, should, it should switch the screen, it's over here, so I'm, yeah, I'm just a pedantic, sorry, sorry, sorry,
01:23
I'm waiting six minutes for a brilliant thing, I just leave it this way, it's, it's good enough for me, full screen, that's much better, but it's, it should be, wait a minute, no then it's, why is it not working, okay, but, but, give up the page
01:52
here, you know, of page, fit page, fit page is better, fit page is good, let me switch,
02:04
that's much better, okay, sorry, so I've got one minute left, ah, stop, stop, okay, from a bird perspective, okay, so every, every, we have all ODF applications, Microsoft Office, ODF Toolkit and so on, it's always starting with you load the ODF file
02:24
into yourself and then you, the state machine, the user macros, they're adding, deleting or modifying the document, right, and at any given time, you flush it out, you save it, export it to another valid ODF, so this is from a bird perspective, everything that Libraff is doing, right, okay, very abstract, right,
02:45
because this is, this is very important, okay, and the next thing is when we have multiple of these state machines working together like here, then, and we want to collaborate in a, in a perfect sense like we do with software, then we need to, you can think of even as, not even as three Libraff's versions or
03:04
Microsoft, Libraff, so, but it might be Git repositories and look, there's about, this guy here is adding something, he's inserting new second paragraph and the others are pulling these changes and this one is just modifying the third paragraph and this one is just doing nothing, just receives the changes, right,
03:21
this is our goal, we want to go that direction, so currently we are not able to receive any of these changes, these high-level changes, we cannot receive some XML snipples because in the internal model we don't know anything about parts, we can only load everything and drop everything, so this is very, very important if we want to do collaboration that Libraff
03:43
learns to accept changes, so these changes are just some high-level fused changes, so what I'm going to do is I'm currently working on, I did it tomorrow this morning, that this ODF XML grammar is a nightmare, it's a very huge text file with a lot of XML notes, so what I do to answer questions like, what is
04:05
the late, what is the, what is the minimum document I loaded in a graph database, because this is exactly what they can do, what is the smallest ODT possible, are paragraphs nested at all, and all these things, you have to look into this long text file, and this is horrible, so what I did is, you see,
04:22
loading using a graph database and making, visualizing, this is only the table-table element with all the child elements and the red things are the attributes, right, you can't even see it from here, so I'm going now to improve this graph because this is just an eternal model and there are a few
04:41
things that we have to skip this, to view better, but we have to extend this grammar, we have to have a better tooling, otherwise, I mean, one, otherwise we cannot cope this complexity, right, and this is, I think this is the brilliant way to go using graph databases, annotate more, annotate these changes, because we think XML, oh this, now we specified everything, but in our
05:05
minds, in all the users' minds, the user changes are all the same, you can, in a paragraph, add, delete, a table and so on, or like I said, modify, format a paragraph, and we have to define these things and we have to define it in an
05:20
automatic way and specify this way, so we have something like ODF Git repositories, like we have real coloration, where you can, oh, here's my pull request, right, you have your ODF book outside, and as I read it and said, oh, there's a typo, I've got a pull request for you, and you don't have any ideas, you can internally have ideas, but you, we should be able to
05:41
have a coloration as powerful, or even more powerful, than the Git, that's it, thank you.
06:24
So, I'm having a quick talk about the state of LibreOffice at the city of Munich. First of all, who am I? I've worked for the Linux team since 2016, and I'm head of development for LibreOffice at the city of Munich, and we're presenting the city of Munich in the OSBA, and also in the
06:44
advisory board of the TDF, and I'm also working on GIMP, Darktable, and a lot of other stuff, but mainly doing packaging. But, you may ask, wait, didn't you decide to switch to Microsoft Office? Not really,
07:01
the government only decided to switch to Windows, and the city council will decide in November if they are going to switch or if they want to switch or not. So, but even if we switch to Microsoft Office, we need LibreOffice for the next four or five years, and at least two or three or maybe four releases, and so we are going to
07:25
continue the development as usual, and also continue our community efforts and the advisory board membership. What have we done? We started development of a new LibreOffice release based on
07:42
LibreOffice 5.2. We finally got a new build server, which improved building time a lot, building four releases at the same time. We also started development for Volmux 18, which will be released on Volmux.net, and JMux did a lot of work upstream on
08:06
scheduling and bug fixes, and we also sponsored a lot of work at CIB and KDAB, mostly CIB, pre-rotating images and also the border frames you talked about, signature lines, some we talked
08:24
about today, and improvements in hyperlink handling, KDE5 plasma backends, which is based on GDK3, a lot of work by KDAB in cooperation with CIB, and more than 40 improvements in OO XML and also many, many more bug fixes and performance improvements.
08:45
And what is to be done in 2018? We want to improve WebDAF support, followed by KDE5 support for our next Basis client 6.0 release, which is based on or which does use KDE5. We also want to roll out LibreOffice 5.2.8. All patches for this version,
09:06
ArtStream and backports are also available on our private branch. We are getting rid of more than 100 internal bugs, fulfilling a lot of feature requests by our users, and finally getting rid of LibreOffice 4.1, plus 300 or something like that,
09:24
backports and patches, which is diverging from 4.1, which is upstream. And we also are going to start development for the next release, which is based on LibreOffice 6.1. We want to make change tracking great again, when it doesn't crash,
09:47
but we are going to pay for it ourselves. More improvements of OO XML support and also add bug fixing and some user requests. And hopefully, we can host a bug-squashing party in
10:02
Munich. Last year, we didn't have a chance, but maybe next year. Oh, with you. Okay, that's all. Thanks.
10:34
Okay, while Torsten is preparing the website, hopefully,
10:43
my website. I sent you a link to a site. Stop the clock. Okay. We're talking about GSoC. As an organization, we
11:02
applied for being accepted, and application has been submitted. I have the dates here. Announcement, if we are accepted, will be on the 12th of February. And student application follows between March 12th and 27th. So, we are
11:21
hopefully looking for a lot of mentors and, of course, students. But since here are more mentors and students, I am happy to be able to announce, yeah, we have some success stories from last year. That could be you the next year.
11:40
So, that's the successful projects from the last GSoC season. And, yeah, so we've been doing GSoC in one way or the other since, I think, 2008, back in the day with Overbuild. And before that, I was doing that, I think, two years with Sun at OpenOffice. So, roughly, I don't
12:04
know, let's make it 10 years of GSoC between, I think, between, always between four and 12 students. So, it's a great opportunity both for mentoring, for getting into mentoring, for students. So, if you know students in your
12:23
community or friends and family, encourage them to try GSoC. It's a great thing. You get paid for open source work. It looks great on your resume. And you get a T-shirt.
12:41
And that's yours? Is it really? No, the left side is for you. Left side is mine. Oh, cool. I got the left side and have two minutes left. I'm really happy to have a chance to advertise some ideas from the design team. We just, we
13:02
have a really large list of topics that could be improved, for instance, change tracking, no question. Something what I would like to highlight is the addition thing. Addition means to integrate our extensions more closely
13:20
into the program. Integrating means it's a place where you use a function. You get a chance to add things from a third place, our extension site, or if you are in a company, you get restricted to the company extension. For instance, if you are in the templates manager, you can click on the link to add a template.
13:44
You don't need to go over the site. Should be quite an easy thing. Just a framework. It downloads a file from a link, kind of configuration should be behind it and the dialogue. Sounds quite easy to me. Blurry shadows, that's
14:04
something we really desperately need. We have a really hard shadow. A shape has a shape behind and that looks really terrible. Blurry shadows makes the draw even better, if it's possible at all. In this sense, we could also
14:23
improve the lines. If we have some kind of brushes so that lines get, looks like scribbled lines, it makes the tool a really great mock-up creation tool. Font handling, I talked this afternoon about font handling.
14:43
We have some topics around font handling where mentors are welcome. I think students should be really smart if they do work with that. Next one, welcome screen, is two minutes left. It's not really a welcome screen.
15:00
We have a problem with user configuration. We are still placing things in the user directory under slash four. And everything what the user configured themselves in the past is not overwritten. So if you update, you don't get the updated information. And that's not
15:21
that good. The idea here behind us that you can show a screen for the updated, when the new release is available, what of the previous configuration should be overwritten, so that the user can say, yes, I accept it. And this dialogue could be used as well for
15:43
welcome and tip of the day. Right, so this was all the user experience. High-level great ideas that you can really make an impact with and a big splash. And the right side is a few, sometimes a bit more low-level project ideas, just a random subset
16:02
of the ideas page. PageMaker is a document liberation project for import. Domain specific language for UI testing, this is to make it easier and quicker and nicer to write UI tests. SmartArt that got recently the last year had the import finally done.
16:22
So now it would be great if you could also edit that. And Charts and Orcus. Orcus is a special calc filter, import filter. Python support for liberal office Eclipse. And VML import for writer. VML is part of the old XML standard.
16:43
Okay, and we're running out of time. So just a summary and two links to the resources. Please do go out and advertise, encourage people, encourage mentors or mentor yourself or your student yourself. Thanks, everyone. Okay. And we have, I think, Olivier.
17:55
Okay. Yes. Let's see if we can see.
18:15
Great. So here we are. I
18:29
got sorry. Yes. I would like to show you everybody knows in the in the work of is
18:42
that the help files are quite hard to write. So we had in the past a small extension that allows you to use a writer file and generate a XHP file. But we had some issues with this
19:02
extension. We have some problems. So I decided to and one of the issues that you have to review the XML that is generated and sometimes fix each of the points of the tags. So I decided to look into case. Kate is the
19:22
editor and Kate has a very nice feature, which is some widgets that you can have here. And when you click on the widgets, you can generate all the XML and just insert the contents that you want. So I'm going to just show you how it
19:43
works. It's very simple. For example, I have these contents, which is purely text. And if I want to start generating a specific help file, for example, I come here with these.
20:03
Oh, there is a here new XHP fired. So double click here and then it generates the XML.
20:23
So I can here in page topic write anything I want. The page title also I can type anything I want. And the file name is vertically generated. So I want now this heading one.
20:43
I want to generate the XML for this heading one. And I get here a specific widget. Okay. So H1 and it generates. Oh, I'm sorry. So I select and I double click
21:04
on each one and then it generates a paragraph role equals feeding ID. This ID is the most cumbersome activity that we have to do because each idea has to be unique. Then it's equal one XML language in
21:24
US and your contents here. So if you have, for example, here I want to emphasize this put emphasize into this
21:43
string. I just double click here and it inserts the tags. Okay. So and then I want to transform that into a paragraph and double click and you have all the XML things that you need to do. So quite a fast way
22:03
to quickly get some contents and generate an HP file. And most of the very boring things that you need to do with the ID is automatically generated. It's a set of JavaScript that
22:23
runs in the text and you can have most of the XHP tags implemented here. So this is what I wanted to show and you can there is a page in
22:43
Turkey where I describe how it works. So no more excuse for missing help pages. Thank you. That was quick. Okay. Thank you very much.
23:15
That concludes the very last session of the day. Thank you all of you for being here. Thank you all the speakers for
23:25
for great information, for great talks. Thank you, Foster, for hosting us. And yeah, have a good evening and a great Sunday. I don't know. I think