GSoC Ideas

From The Document Foundation Wiki
Jump to: navigation, search

This page lists the project ideas for Google Summer of Code, see the general info about LibreOffice and GSoC. Feel free to pick any of the tasks listed in the Programming Tasks section of the EasyHacks page, but in that case you need to ask for mentors on the development mailing list if none is defined. All tasks on this page already indicate mentors for the task. New tasks on this page should be added only by those with the experience and time to invest in mentoring new developers.

Note that the LibreOffice project selects GSOC projects that are well researched and show a good understanding of the scope of the problem. It is also possible to create a project proposal not based on the ideas given below, if the application of the student shows good understanding of the problem. In fact, if you apply with one of the prepared ideas below, we expect you to show you did research beyond the abstracts given below even more.

When doing that please use this template:


=== Title of the task ===

Some detailed description of the things to accomplish.
Don't hesitate to provide details if you have some like code pointers, links to specifications, etc.

;Required skills / knowledge: C++, Reading other's code, and any other useful skill required go here.

;Difficulty: Range among easy, medium, hard

;Potential mentors
:''Joe Devel'', IRC: jdevel, mail: joe@devel.org

Please move successfully completed projects to Development/GSoC/Successfully Implemented Ideas.

Contents

General

Subpixel and stable glyph positioning tdf#103322

Fixing the bad text spacing we have due to lack of subpixel positioning. All graphics system we use (except GDI, but this is dying) support subpixel glyph positioning but we make no use of it as all our glyph positions are stored using integers and to rounding errors often accomulate resulting in bad and unstable text spacing and it gets worse on hidpi screens (resizing Writer window, for instance, causes glyphs to jump around but this shouldn’t happen).

Required skills / knowledge
C++, Reading other's code, some familiarity with fonts and text rendering is a plus
Difficulty
Hard
Potential mentors
Khaled Hosny, IRC: KhaledHosny, mail: khaledhosny@eglug.org

Support multicoloured font formats tdf#104403 tdf#105488

The latest version of the OpenType specification introduced few tables that allow for having multi-colored glyphs, which have many uses the most common is color Emoji.

The simplest of them is COLR/CPAL, which use layers of normal glyphs and color palettes to assign colors to each.

Another alternative is SVG table which embeds full SVG graphic for each glyph. This one might be a trickier as instead of rendering layered glyphs with different colors we will need to render SVG graphics. We already have decent SVG support, but I’m not sure how usable is it from a low level as text rendering in VCL.

Required skills / knowledge
C++, Reading other's code, some familiarity with fonts and graphics rendering is a plus
Difficulty
Medium
Potential mentors
Khaled Hosny, IRC: KhaledHosny, mail: khaledhosny@eglug.org


Add a DSL to the UI testing and improve the generated log file

The UI testing is one of our newest additions to our testing frameworks. The code is split between a C++ layer wrapping our GUI toolkit and a python test framework with the actual tests. Recently some work was done to start logging UI actions when they happen and generate log files that are close to the python test files. The next step is to define a domain specific language (DSL) that we can use to represent the UI testing actions and instead of generating log files generate these files. Additionally with a replay mode in the python framework it should be possible to replay the UI actions automatically. Such a feature would allow to easily add new tests and make bug reporting much easier.


As part of this GSoC project the DSL, the logging to the DSL format and the replay should be implemented. If there is enough time or the need for it the C++ layer should be extended to support more UI elements.


Most of the python part of the framework can be found in the uitest/ module.

Most of the commits related to the framework are prefixed with uitest: and can be found with this git search.

The file with most of the C++ wrappers can be found here.


Required skills / knowledge
Python, a bit of C++, an idea how to design a DSL
Difficulty
Medium
Potential mentors
Markus Mohrhard, IRC: moggi, mail: markus.mohrhard@googlemail.com


Improve VCL OpenGL backend

There are various improvements needed to the VCL OpenGL backend to make it faster:

  • On Linux it needs glyph caching with FreeType so it can render text faster. Also try to make it work on Windows.
  • Increase minimal version to OpenGL 3.2 core context. Currently the minimal version is OpenGL 3.0, which forces us to use the compatibility context but there is little reason not to up that to core context (most drivers nowadays should have no problem with it). However, for that the shaders need to be changed to the new format and code needs to be adapted not to use any more deprecated features.
  • Batch even more graphic calls to increase rendering speed. The most common calls are already batched but not all of them (texture based calls).
  • Minimize the (geometry) data that is send to the GPU. This was not yet optimized so a lot of data is send using floats when (for example) only bytes would be needed (or even less).
  • Improvements to texture and glyph caching algorithms (use 3D textures).
  • Support EGL.

OpenGL backend code can be found in here.

Required skills / knowledge
C++, OpenGL, reading other's code
Difficulty
Medium to Hard
Potential mentors
Tomaž Vajngerl, IRC: quikee, mail: quikee@gmail.com

Tests for the VCL graphic backends

We currently have some graphic tests located here, but they are incomplete and aren't being checked. The purpose of the tests is to identify if a graphic backend works correctly, which is especially important if the backend depends on the client hardware or drivers (like for example the OpenGL backend).

Each test draws to a small surface (VirtualDevice) and evaluates if what was drawn is correct or not by looking at the pixels. As backends don't draw equally (especially when using AA), it is needed to allow for a bit of discrepancy of the values (for example sometimes a backend won't draw one pixel). In this case the test is marked as "quirky" (acceptable result, but not what is expected).

First part of this task is to write additional tests that cover more graphic functions in VCL, then make this tests run when building a backend as well as when the user uses the backend for the first time (OpenGL for example). Also allow the user to run the tests and view the results for himself (add the UI for this).

Required skills / knowledge
C++, reading other's code
Difficulty
Medium
Potential mentors
Tomaž Vajngerl, IRC: quikee, mail: quikee@gmail.com

Make SVM (StarView Metafile) format independent of the VCL Metafile + tests of the format

The SVM file is a 1 to 1 dump of the content of VCL Metafile. This makes the VCL Metafile hard to modify as the SVM shouldn't change (for example to change away from the old geometry primitives in "tools" module - PolyPolyon, Polygon, Point, Rectangle,...) so to make this possible we need to separate the two. This is also very important to allow further refactoring of VCL to make it more modern (for example native 32-bit bitmaps and surfaces and to use alpha transparency and blending of the backends and not do its own thing).

This task would include to first complete the (import/export) test of the SVM format which are located here. The second part is then separate file writing/reading of the VCL Metafile to its own classes, to make them independent.

Required skills / knowledge
C++, reading other's code
Difficulty
Medium
Potential mentors
Tomaž Vajngerl, IRC: quikee, mail: quikee@gmail.com

Make Arabic text justification more robust tdf#104921

Currently finding kashida insertion positions and the width of each is done by Writer, but the actually kashida insertion is done by VCL. However, the positions and widths are not communicated explicitly between the two; instead Writer will modify the DX array at the kashida insertion position by the required width, then VCL will guess based on the character and script whether a given DX adjustment is a regular width change or a kashida insertion. This is clearly very brittle and is a source of all kinds of hard to fix random kashida insertion bugs.

To fix this, Writer should explicitly pass the kashida insertion points and widths to VCL, separate from the DX adjustments.

Required skills / knowledge
C++, Reading other's code, ability to read Arabic is a plus but not required
Difficulty
Medium to hard
Potential mentors
Khaled Hosny, IRC: KhaledHosny, mail: khaledhosny@eglug.org

Porting / platform / infrastructure specific topics

LibreOffice Online

LibreOffice online has developed significantly during the last year, but there is still a lot to do there. This task will include changes in the LibreOfficeKit, and in the web/JavaScript part too.

The main focus will be on making the features knows from the desktop version available in the Online version too; like the pivot tables, or other.

The online work takes place mostly in the online.git reporsitory: https://cgit.freedesktop.org/libreoffice/online/

Required skills / knowledge
C++, JavaScript optional.
Difficulty
Medium
Potential mentors
Jan Holesovsky, IRC: kendy mail: kendy @ collabora.com

LibreOffice Online Admin

LibreOffice Online has an admin-console which provides a view of how active the machine is, what documents are open, what memory is in-use, and so on.

There are a number of small features required here - in particular:

  • controlling debug logging settings remotely
  • a coloring debug log browser with simple filtering
  • showing the pkill -USR1 output in the web-UI
  • adding detailed version numbers
  • presenting data sent & received per document / session
  • Complete half-baked history view in admin-console (tdf116233)

There is also work to be done to simplify the admin-console - merging the Admin.cpp and the AdminModel.cpp code to simplify.

Required skills / knowledge
C++, JavaScript optional.
Difficulty
Easy
Potential mentors
Michael Meeks, IRC: mmeeks mail: michael.meeks @ collabora.com
Pranav Kant, IRC: pranavk mail: pranavk @ collabora.com

LibreOffice for Android

LibreOffice works nicely on Android these days, but there are stil many things to improve and fix. This task will focus on the Android Most Annoying Bugs:

https://bugs.documentfoundation.org/showdependencytree.cgi?id=84726&hide_resolved=1

and also on new features, like printing.

Required skills / knowledge
C++, Java.
Difficulty
Medium
Potential mentors
Tomaž Vajngerl, IRC: quikee mail: tomaz.vajngerl @ collabora.co.uk
Miklos Vajna, IRC: vmiklos mail: vmiklos @ collabora.co.uk

Implement more VCL functionality in the Qt5 VCL plugin

Since November 2017 during the LibreOffice 6.0 development cycle, VCL (Visual Class Library - LibreOffice GUI Toolkit) gained a Qt5 based backend; a rather incomplete one. You have to manually select the plugin on LibreOffice startup via an environment variable SAL_USE_VCLPLUGIN=qt5 and build with qt5. Additionally during current (6.1) development cycle VCL gained a patched gtk3 plugin (gtk3_kde5), which adds a KDE5 / Qt5 file picker on top of the gtk3 plugin.

The current state of the Q5 plugin:

  • Most basic drawing is implemented (AKA SalGraphics)
    • Font handling is broken and currently forces a Qt5 dependency on the main VCL library
    • Patches exist to move the font handling of SalCommonLayout in the respective VCL plugins and get rid of the main Qt5 dependency
    • A Cairo-based render path as a fallback with working fonts can be enforced with SAL_VCL_QT5_USE_CAIRO=1. This is used to verify the Qt5 based painting
  • Mouse is working
  • Keyboard is working

There is a branch with more Qt5 font fixes (still broken) and an initial Qt5 file picker.

TODOs

If there is an additional mentor, two students may work in different parts of the code.

For a student there are multiple possible entry points for GSoC.

  • Analyze and fix the Qt5 font handling
  • Port the extended file picker of the gtk3_kde5 plugin and fix the Qt5 one
  • Start implementing "native widget support" (see vcl/qt5/Qt5Graphics_Controls.cxx).
  • Build the plugin on other platforms (Windows, Mac)
  • General bug fixing: we don't yet track Qt5 bugs in bugzilla, but could start tracking them during GSoC.
Code pointers
Required skills / knowledge
C++, Reading other's code, (Qt5)
Difficulty
Medium - Hard
Potential mentors
Jan-Marek Glogowski, IRC: jmux, mail: glogow @ fbihome . de

User Experience

The design team collected a number of ideas in in the pad http://pad.documentfoundation.org/p/UX-GSoC_Ideas. Not for all ideas mentors have committed so far. If you are interested in a task that has no mentor you would need to find someone. If the topic needs further refinement feel free to contact the UX team in order to prioritize the usability engineering. Some examples for full-featured topics:

100 paper cuts

The student will solve a number of most-annoying issues and enhancement requests during the GSoC time. Issues are collected in https://nextcloud.documentfoundation.org/s/zraEHZxyCKBTNY7 with a rough estimation on effort.

If you want to apply for this, you should first solve one of the papercuts (pick an easy one) in advance.

Required skills / knowledge

  • C++, Reading other's code

Difficulty

  • Varying

Potential mentors

  • Samuel Mehrbrodt, IRC: samuel_m
  • Muhammet Kara, IRC: mkara, mail: muhammet.kara AT pardus.org.tr

Improvements to Notebookbar

Notebookbar reuses UI files definition known from Gtk+ (.ui files) as created by the Glade tool for upper part of the LibreOffice window, giving lots of freedom to the designers how to organize the UI. Current implementation has advanced during the last GSoC, but it is still incomplete: The content is cropped on resize, theming is not respected, and new functions such as style dropdown haven't been introduced yet. Beyond that, the customization via Glade is not suitable for normal users, and quick customization like toolbutton on/off is not possible.

Required skills / knowledge

  • C++, Reading other's code

Difficulty

  • Medium

Potential mentors

  • Jan Holesovsky, IRC: kendy mail: kendy @ collabora.co
  • Szymon Klos, IRC: eszka mail: szymon.klos @ collabora . com
  • UX team, IRC: channel #libreoffice-design, mail: design @ global.libreoffice . org

Block diagrams

Most expect feature in Draw is the better implementation of block diagrams. That includes the compatibility with Visio but also simplified workflows where entered data get formatted automatically. A couple of predefined styles/presets should allow to quickly switch from one diagram style to another.

Required skills / knowledge

  • (C++, Reading other's code)?

Difficulty

  • (Medium)?

Potential mentors

  • Thorsten Behrens, IRC: thorsten mail:
  • UX team, IRC: channel #libreoffice-design, mail: design @ global.libreoffice . org

Blurry shadows

In LibreOffice the shadows are just a copy of the object. Blurring with some options is missing, and well known in competitive open-source tools like Calligra. This feature is also needed for SVG import/export.

Required skills / knowledge

  • (C++, Reading other's code)?

Difficulty

  • (Medium)?

Potential mentors

  • Tomaž Vajngerl, IRC: quikee mail:
  • UX team, IRC: channel #libreoffice-design, mail: design @ global.libreoffice . org

Revamp print dialog

Current print dialog has an unclear workflow where for instance the page format does not match printer settings. Rework is needed to align the document/page settings with the printer settings. There is also a proper feedback required for the various settings and what will applied when printing. Last but not least the print dialog is cluttered and needs a clean-up. Mockups

Required skills / knowledge

  • C++, UI, reading other's code

Difficulty

  • Medium

Potential mentors

  • Katarina Behrens, IRC: bubli mail:bubli @ bubli . org
  • UX team, IRC: channel #libreoffice-design, mail: design @ global.libreoffice . org

Chart wizard

For experienced people the current wizard distracts from the workflow and steps are not naturally implemented, for instance the range is selected first and then the type of chart. Over the modules we have different ways to insert charts plus the wizard design is inconsistent to other dialogs which are tabbed. Mockups

Required skills / knowledge

  • C++, UI, UNO, reading other's code

Difficulty

  • Hard

Potential mentors

  • Katarina Behrens, IRC: bubli mail: bubli @ bubli . org
  • UX team, IRC: channel #libreoffice-design, mail: design @ global.libreoffice . org

Multi-color gradient

While the area fill style dialog has been reworked nicely the ability to deal with more than two steps for gradients is missing. Furthermore, gallery items with gradients that consists of more than two colors or non-linear gradients are interpreted as a collection of lines when ungrouped making a modification impossible. First analysis showed that multi-stop gradients are loaded well but not visualized as it. The project would need to implement the draw routines as well as the UI control in the area dialog as suggested.

Required skills / knowledge

  • (C++, Reading other's code)?

Difficulty

  • (Medium)?

Potential mentors

  • Armin Le-Grand, IRC: mail:
  • UX team, IRC: channel #libreoffice-design, mail: design @ global.libreoffice . org

Improve OpenPGP encryption experience

With LibreOffice 6.0, there's experimental PGP/GPG encryption support. A number of shortcomings are there still, that make using this cool feature unnecessarily hard, e.g. selecting recipients anew for every safe, or finding the right keys. Keyrings can get potentially infinitely large, so smart searching / traversing / filtering is needed. Additionally, some asynchronous querying would be great, as currently it takes several minutes to retrieve all keys for large keyrings.

Required skills / knowledge

  • C++, Reading other's code, some idea about public key crypto

Difficulty

  • Varying

Potential mentors

  • Thorsten Behrens, IRC: thorsten mail: thb@libreoffice.org
  • UX team, IRC: channel #libreoffice-design, mail: design@global.libreoffice.org

Base

Listbox separate read values from input values

A listbox acts as a mapping between values and display strings. The database (in general the value of the control) is one thing (drawn from the list content property), but the string shown to the user is another thing (drawn from the list entries property).

But these are actually used for *two* roles:

  • values read from the database
  • values input by the user

Sometimes, it is possible that the database contains values that the user should not be allowed to input. For example, historic / deprecated values, or more to the point the valid values depend on the value of other fields (or controls). One would then wish that the drop-down list feature only those values that are allowed in these particular circumstances.

The idea is to duplicate the "list entries" and "list contents" properties:

  • once for the role of mapping values read from the database(find what to display given a database value)
  • once for the role of mapping an entry chosen by the user to a database value (find what to write to the database when the user selects a list entry by its display string)

The idea is that the second set would in general be a subset of the first set, thereby giving the user a more limited selection for data entry, but still keeping the possibility of providing a user-friendly display string for other values read from the database.

How to handle listbox with Drop Down set to False is an open question.

Required skills / knowledge
C++, capacity to work autonomously.
Difficulty
medium
Potential mentors
Lionel Elie Mamane, IRC: schoinobates, mail: lionel AT mamane DOT lu

Basic

Draw

Impress

SmartArt editing in Impress

SmartArt is a nice feature that allows users to quickly add charts / diagrams to presentations. We have a partial implementation as an experimental feature; the task of this GSoC would be to finish it.

At the moment, we are able to import SmartArt as a stream of shapes that is available in the pptx presentations generated by MSO 2010. We are also able to create the shapes when the stream is not available in case you enable the Experimental features Tools ▸ Options. Unfortunately:

  • The rendering of such shapes is much worse than if we use the pre-rendered stream
  • We are unable to edit the imported SmartArt

This task should first focus on improving the rendering of the shapes themselves, and then, when the student gets more familiar with the code, should add user interface for SmartArt editing.

The current experimental SmartArt import lives in oox/source/drawingml/diagram/*. The commit that introduced the functionality is Import SmartArt graphics to Impress.

Further information: The related bug in the LibreOffice bug tracker is: tdf#37932. An external extension (not nicely integrated) trying to implement at least some SmartArt functionality: SmART (Extensions/SmART Gallery)

Required skills / knowledge
C++, Reading other's code.
Difficulty
Difficult
Potential mentors
Thorsten Behrens, IRC: thorsten, mail: thb@documentfoundation.org
Jan Holesovsky, IRC: kendy, mail: kendy@collabora.com

Attach animations to styles

Currently, Impress styles control most of the visual shape appearance, but not the slideshow animation effect. Which is a pity, as the styles concept is pretty powerful inside LibreOffice, and provides a nice way to change animation settings and type for a great number of objects simultaneously. For a slightly different view onto the same problem, see this bug report, and this one from the LibreOffice side.

Original patch from GSoC 2010: https://cgit.freedesktop.org/libreoffice/build/tree/patches/dev300/sd_effects_styles.diff?h=master-backup

Required skills / knowledge
C++, Reading other's code
Difficulty
Hard
Potential mentors
Thorsten Behrens, IRC: thorsten, mail: thb @ documentfoundation . org
Katarina Behrens, IRC: bubli, mail: bubli @ bubli . org

Rework Impress slideshow to use DrawingLayer primitives

The Impress slideshow, while being designed to only interact with Impress via interfaces, had to resort to an ugly hack to be able to render all Impress content. That was ok back in the day, but is becoming a liability these days. Nowadays, what one want to use is the DrawingLayer Primitives (https://wiki.openoffice.org/wiki/DrawingPrimitives), which means porting over slideshow/source/engine/shapes/* to use this kind of abstraction, instead of the StarView Metafile previously in use.

Required skills / knowledge
C++, Reading other's code.
Difficulty
Difficult
Potential mentors
Thorsten Behrens, IRC: thorsten, mail: thb @ documentfoundation . org

Mix and Merge Impress presentations

For the professional slide jockey, mixing a new presentation out of existing slide decks is a common task, that unfortunately Impress does not support very well. This task is about providing, possibly stand-alone, functionality to:

  • display lots of presentation files conveniently, possibly with tagging/searching functionality
  • out of existing slides, quickly create a new presentation
  • provide functionality to conveniently exchange / homogenize slide layouts and/or master pages, such that new presentation has consistent look
  • as a bonus task, be able to create virtual slide decks, by referencing other files, and have the resulting presentation automatically update, once the referenced slides are
  • can be built-in to Impress, stand-alone (but then portable across all our platforms), or web-based.

Code pointers:

Required skills / knowledge
ODF, UX, possibly c++, possibly Python, possibly web frameworks
Potential mentors
Thorsten Behrens, IRC: thorsten, mail: thb @ documentfoundation . org

Add Impress shape animations that use a real physics engine

Impress already sports a number of shape animation effects, though they start to look a bit dated in this day and age. With powerful 2D and 3D physics simulation engines available as open source, it would be cool to plug them for having slide contents interact with each other, bouncing around stuff on the screen. This task would involve:

  • integrating a suitably-licensed physics engine with LibreOffice (Box2D or Bullet come to mind)
  • interact with LibreOffice User Experience people on how to best present this in the UI
  • wire things up in the slideshow / canvas component of LibreOffice
  • be able to load and save the new effects, at least to odf files
  • in the end, have at least three effects ready to be used

Code pointers:

Required skills / knowledge
C++, basic game/animation skills useful, reading other people's code
Potential mentors
Thorsten Behrens, IRC: thorsten, mail: thb @ documentfoundation . org

Calc

Implement interface for external data source import into Calc

With more and more data in different forms it becomes more and more challenging to visualize and evaluate them. Calc could be an amazing tool to allow inspecting existing data. To allow that we would need an interface to import and more importantly update data from external data sources. The interface should be modelled similar to how the orcus interface is currently implemented and the data should be stored inside of a ScDBData (a database range). The interface would then be used together with either an existing document where you mark a range for the external data or a template document that is automatically filled. The initial work on providing some structure has already been done in sc/source/ui/dataprovider/ and in sc/source/ui/miscdlg/dataproviderdlg.cxx

This task is about extending the existing data providers and data transformations, implementing an usable UI for the feature and start working on storing the information in a file.

Required skills / knowledge
C++, Reading other's code, debugging

Difficulty: Medium

Potential mentors
Markus Mohrhard, IRC: moggi, mail: markus.mohrhard@googlemail.com

Support charts in orcus

Orcus is an external library for importing spreadsheet formats that is already used for a few features in Calc. However for now we are limited to spreadsheet support and we should extend support to charts. Orcus works by providing an interface of virtual methods that must be implemented on the client side. We try to keep the interface format independent and try to always support at least OOXML and ODF.

If the time permits we should also work on some experimental integration of the chart import code into LibreOffice.

The spreadsheet interface is mostly in include/orcus/spreadsheet. The chart interface should be similar.

Required skills / knowledge
C++, Reading other's code, debugging, Reading specifications

Difficulty: Medium

Potential mentors
Markus Mohrhard, IRC: moggi, mail: markus.mohrhard@googlemail.com

Implement table styles

Calc so far lacks real table styles, which for example can be seen in Impress tables, with formatting of header row, header column, banded rows and columns, total row, rightmost column, ...

The existing old technology Format → AutoFormat Styles are visually similar, but very inefficient in that they apply individual attributes to individual cells, which a) is slow, and b) bloats the document size, and also can't cope with hidden rows or columns to keep a visually stable table style layout.

Required skills / knowledge
C++, Reading other's code, Debugging, Understanding the concept of different layers of cell attribution, Having an idea of how a single attribute with one value could be used for this
Difficulty
Hard
Potential mentors
Eike Rathke, IRC: erAck, mail: erack@redhat.com

Writer

Document Themes

Document themes are a simple way to allow users to quickly & consistently restyle the entire document. There is an implementation of this in MSO, and also Calligra plans to something in this regard, so this task actually consists of 2 parts:

  • Implementing user interface for the feature
  • Implement the ODF support for that

More ideas about the feature you can get by reading http://blogs.msdn.com/b/jensenh/archive/2006/02/22/537054.aspx and https://blogs.kde.org/2011/12/14/fruits-css2-shared-themes .

The import code for DOCX is here: https://cgit.freedesktop.org/libreoffice/core/tree/writerfilter/source/ooxml, you might need to change also https://cgit.freedesktop.org/libreoffice/core/tree/writerfilter/source/dmapper

For XLSX and PPTX, it resides in https://cgit.freedesktop.org/libreoffice/core/tree/oox/source

Required skills / knowledge
C++, Reading other's code, reading specifications :-)
Difficulty
Hard
Potential mentors
Jan Holesovsky, IRC: kendy, mail: kendy @ collabora . com
Tomaž Vajngerl, IRC: quikee mail: tomaz.vajngerl @ collabora.co.uk

Help system

Integrate the new Help in the build system and packaging

The new offline Help system (help in local browser) is working on master build. However it is not in main build process as it has not packaging for distribution.

The objective of this project is to write the gbuild makefiles integrated into the main build process and deliver packages files for Linux, Windows and MacOS.

Required skills / knowledge gbuild, makefiles

Difficulty:

medium

Potential mentors:

  • Olivier Hallot, IRC: ohallot, mail: olivier.hallot@libreoffice.org
  • Jan Holesovsky, IRC: kendy, mail kendy@collabora.com

More information

contact Olivier

Filters

Improve MS Publisher import filter

libmspub, a library for import of MS Publisher documents, was implemented as a GSoC 2011 project. In the current state, the library only supports documents created by Publisher 2000 or newer. That is because, while the file format is technically still the same, it has gone through several evolutions which changed the representation of page content, text, etc. As a result of that, libsmpub can handle a document created by Publisher 2.0, but it only produces empty pages. With a Publisher 98 document, the result is somewhat better, but still not good.

The goal is to add support for Publisher 95-98, possibly also for older versions.

Required skills / knowledge

  • C++, Reading other's C++ code (to understand the existing libmspub code)
  • Python (for OLEToy)

Difficulty: medium

Potential mentors:

  • David Tardon, IRC: dtardon, mail: dtardon@redhat.com
  • Fridrich Strba?, IRC: Fridrich, mail: fridrich.strba@bluewin.ch

Improve Zoner Draw import filter

libzmf, a library for import of Zoner Draw documents, was implemented as a GSoC 2016 project. Currently the library only supports documents created by versions 4-5. There are two goals in this task:

  • handle some of the missing features (blending, warping of the bounding rectangle);
  • add support for the file format produced by versions 2-3.

Both formats have been almost completely reverse-engineered.

Required skills / knowledge

  • C++, Reading other's C++ code (to understand the existing libzmf code)
  • Python (for OLEToy) is welcome, but probably won't be needed

Difficulty: medium

Potential mentors:

  • David Tardon, IRC: dtardon, mail: dtardon@redhat.com

Improve Adobe Pagemaker import filter

libpagemaker, a library for import of Adobe Pagemaker documents, was implemented as a GSoC 2013 project. In the current state, the library only supports documents created by versions 6.5-7.0 on Windows. Documents of version 6.0 should be opened more-or-less correctly, but the support has never been specifically tested. Documents created on Mac are never opened correctly because of many oversights in the code.

The goals of this taks are to fix import of Mac 6.5-7.0 files, implement some missing features and add support for older versions, both Mac and Windows (starting at 6.0 and proceeding to older ones until we run out of time :-)

We will use OLEToy for any necessary reverse-engineering. We will also create documents for regression testing for all versions we add support for.

Required skills / knowledge

  • C++, Reading other's C++ code (to understand the existing libpagemaker code)
  • Python (for OLEToy)

Difficulty: medium

Potential mentors:

  • David Tardon, IRC: dtardon, mail: dtardon@redhat.com
  • Fridrich Strba?, IRC: Fridrich, mail: fridrich.strba@bluewin.ch

UNO

UNO is the LibreOffice component model, cross-language and intra- as well as inter-process. It is somewhat similar to Corba and COM. It is used to extend LibreOffice via document-related scripts and more general extension packages, as well as to use LibreOffice functionality remotely from another process.


Rust UNO Language Binding

UNO's cross-language abilities are implemented by bridging between various language-specific environments and a binary runtime representation (with a C API). Next to C++, Java, and Python, it would be great to have such a bridge also for a great language like Rust.

One aspect is to use Rust FFI to interface with the binary UNO C API. Another is to design the Rust representations of the various UNO constructs (its data types; objects with their multiple interfaces and methods; services and singletons), so that this language binding can not only be used to interact with existing LibreOffice services written in other languages, but also to create new services in Rust. A third aspect could be to create a pure Rust implementation of the UNO remote bridge protocol.

Some documentation pointers are:

Some code pointers are:

Required skills/knowldege: Rust, interfacing to low-level C/C++, working against formal specifications

Difficulty: medium to hard

Potential mentors:

  • Stephan Bergmann, IRC: sberg, mail: sbergman @ redhat . com
  • Michael Stahl, IRC: mst[_]*, mail: mstahl AT redhat DOT com
  • Bjoern Michaelsen, IRC: Sweetshark, mail: bjoern.michaelsen AT canonical DOT com

LUA UNO Language Binding

UNO's cross-language abilities are implemented by bridging between various language-specific environments and a binary runtime representation (with a C API). Next to C++, Java, and Python, it would be great to have such a bridge also for a small, lightweight scripting language like LUA.

LUA is small (few K lines of C), and written with the goal of embedding in mind:

Besides hooking LUA up with LibreOffice's UNO subsystem, a taker for this project would need to map the various UNO constructs (its data types; objects with their multiple interfaces and methods; services and singletons) to suitable LUA types, so that this language binding can not only be used to interact with existing LibreOffice services written in other languages, but also to create new services. LUA should be expressive enough to permit that (its dynamic typing helps a lot there), just for exceptions and error handling, some extra thoughts might be needed:

Some code pointers are:

Required skills/knowldege: LUA, interfacing to low-level C/C++, working against formal specifications

Difficulty: medium to hard

Potential mentors:

  • Michael Stahl, IRC: mst[_]*, mail: mst AT libreoffice DOT org
  • Thorsten Behrens, IRC: thorsten, mail: thb AT libreoffice DOT org
  • (Bjoern Michaelsen, IRC: Sweetshark)

Extension integration

Add Python extension support to LOEclipse

LOEclipse is an Eclipse plugin which supports developing & debugging Java extensions/components for LibreOffice. It is built in such a way that it can be extended to support other languages than Java. The task is to add support for Python extensions to LOEclipse.

Required skills / knowledge Java (LOEclipse is written in Java), Python (to understand Python extensions), Basic understanding of the Eclipse IDE and Platform

Difficulty: medium

Prerequisite To be accepted for this project, you don't need to do an Easy Hack in LibreOffice itself. Instead you should work on one of the LOEclipse issues and submit a pull request for it.

Potential mentors:

  • Samuel Mehrbrodt, IRC: samuel_m, mail: samuel.mehrbrodt@cib.de


Tooling

Integrate .ui dialogs with translation tooling/string search webservice to help translators

Translators often have a hard time determining the context of a string to translate. It would be great if translators would be able to search for a string and have it presented in the context of the UI, a picture of a dialog for example.

Required skills / knowledge python (when integrating into pootle), java (when integrating into opengrok) or php or other suitable framework for the user-facing part, reading c++ code to identify where strings come from (not all strings are in dialogs) and GTK/glade ui definitions as the basis for the rendered dialog, scripting/makefile stuff to automate updating of the data

Difficulty: easy (when only limiting yourself to the glade dialogs) to medium (depending on the level of integration with the current tools: pootle as the platform where translation happens or opengrok where the source code is indexed)

Potential mentors:

  • Christian Lohmaier, IRC: cloph, mail: cloph@documentfoundation.org

Ideas without a mentor

A number of ideas from previous years can be found at the Development/GSoC/Ideas without a mentor page. Please note that you need to find a mentor willing to mentor the task. There is no guarantee that anyone in the community is going to mentor one of these tasks this year.