First Okular Sprint ever at Barcelona

In May a group of three Okular developers met for four days at the Blue Systems Barcelona office to hack on the KDE universal document viewer.

Okular 2014 sprint group picture
Albert Astals Cid, Luigi Toscano and Fabio D'Urso

The first day the team triaged a lot of bugs resulting in a nice drop of unconfirmed bugs. There are still a lot of UNCONFIRMED items in that chart, almost all of them are wishes that we didn't know how to omit on the chart.

During the next days there were discussions about ideas and implementations, including:

  • Mimetype backend priority now that we have a txt backend that can open almost any file
  • Investigation about a printing regression regarding hardware margins in newer versions of CUPS
  • Removal of lots of widget code from backends
  • Idea of creating a command line okular2text application to test libokularcore which can be used in a gui-less environment.
Albert  talking about the workflow for saving documents
Albert talking about the workflow for saving documents

We decided that when porting to KF5 we will aim to have libokularcore be dependent on QtGui but not on QtWidget.

The most important item we discussed was how Okular saves file data. The proposal is to never autosave, making Okular act more like an editor. This has implications for bringing up old autosaved content if autosave was not used any more. By the end of the last day, we think we developed what seems a good plan. Now we only need time to code it ;)


Forgot to thank Blue Systems Barcelona for letting us use their office and the KDE e.V. for the financial support to have this sprint. If you want more sprints happening please donate at http://kde.org/community/donations/

By Albert Astals Cid at Sun, 2014/07/27 - 10:48pm

Always interesting to hear about your progress, thank you :)

I'm wondering if there's ever been any discussion about the slow speed at which Okular renders .pdf's that are not text but bitmap images for pages. I have often wondered why that was. Like I'll be waiting 5 seconds for Okular to render the next page of a scanned book and it breaks my reading flow.

By Michael at Mon, 2014/07/28 - 5:30am

A thing I've been missing for a while now is to display signatures of digitally signed PDF documents. I just leave the sugestion if someone takes another go at okular.


By Miguel Andrade at Mon, 2014/07/28 - 11:12am

I very much need this feature. It is something that is lacking in Linux. Why doesn't Okular have it?

By Birbo at Mon, 2014/08/11 - 8:14pm

I would really like to see some improvements to searching.
- searching in a big document is quite slow compared to acrobat reader
- I am not a fan of how Okular starts searching automatically - it will automatically start searching if I pause whily typing my search term. And it could search for the wrong thing if I make a typo while entering it.
- a search widget that could be a part of the toolbar near the top of the window would be great

Love the tabbed interface that Okular got recently though!

By DeKay at Mon, 2014/07/28 - 1:59pm

Nice to hear that development of Okular is going on.

Please improve the annotations in Okular. No FOSS covers that area in a manner that is really usable in business. Okular is already quite close to that but there are some points:
- missing ability to move pop-up note icons
- configurable icon size of pop-up notes (the default is too huge for many documents)
- option that enables that the text of the annotation is shown at the left/right margin at the corresponding height (now they are shown always at the upper left corner, the position is not stored, and no anchor is used)
- behavior of inline notes (initial size too huge, resizing after edit, manual resizing, font update)
- missing insert text annotation
- missing strike-through and replacement text annotation
- missing arrows.

Apart from that above, I am very happy with Okular. Many thanks!

By Heinz at Wed, 2014/07/30 - 12:43pm

It is highly recommended to put requests like these in the bug tracker as feature requests so the developers see them and can track progress.

By Jos Poortvliet at Sun, 2014/08/10 - 9:42am