Stephan Bergmann

Towards an Operational Code Aesthetics

This talk will be a short refresher on the various functionality available in LibreOffice for (textual) URI processing. For historical reasons, that functionality is more arcane and error-prone than it needs to be. We will be looking at the typical pitfalls and fixes.

"But what about the extensions?" can be the death knell for whatever cool new feature somebody tries to implement in LibreOffice, as extensions naturally ask for interface stability. But what about them, anyway? Are they the saviour that brings diversity to our desktops, or are they just a ghostly phantom that stifles innovation? Lets take a look at the extension landscape out there.

...with clang-cl, thereby leveraging (some of) the Clang goodness we enjoy on the other platforms for the Windows-specific parts, too. This talk will highlight some of the findings made during that endeavour.

Advances in C++ have gathered momentum with C++11 and forthcoming C++14, and compiler writers busy to keep up. However, for reasons of cross-platform, cross-compiler, aging baselines, etc., the LibreOffice code base is still mostly stuck with C++98. We will discuss how to overcome blockers in adoption of modern C++ features and in what ways LibreOffice would benefit from them.

With UNO service information changed from active to passive, XML-based representation a while ago, UNO type information is the remaining topic that needs some love, clean-up, and improvement. From a curiously verbose UNOIDL syntax, to the awkward binary .rdb format, to the fact that type information is duplicated in different formats for binary UNO and Java UNO, all the way to the still unsolved great challenge of becoming incompatible compatibly, etc. etc. -- you get the idea.