A gentle reminder: please occassionally check back on bugs you've reported and resolve them if they have been fixed in recent versions.

Sometimes we developers fix bugs but forget to resolve them ourselves; sometimes bugs are fixed by newer versions of other software we depend on; sometimes bugs are fixed as consequences of other fixes.

So help us out and resolve your own bugs when possible.

Thanks.

I often get asked about junior jobs in Calligra Words. I ususally say no, but now I actually have some.

The reason I say no is that there are no easy jobs left, and so jobs would take much more of my time than I would like. And I also don't want to purposely leave unfinished stuff behind.

Anyway here is a brief synopsis of the junior job: We have code that applies bold, italic etc, and it works, except it doesn't respect table cell protection. The job consists of repeating an example I've already made to the application of bold, italic and several other similar things.

It's pretty easy copy,paste,edit and will give you practical experience with the visitor pattern

You are a student, you would like to contribute to an Open Source project, and get paid for it ?

Then I may have something for you.
At my job at Fraunhofer in Kaiserslautern we are using the CDash testing server for testing the software we develop - various different High Performance applications for Linux clusters.

Since Monday, a feature I have been working on for quite a while has been merged into Calligra master. This is the style selection combo box.
Until Monday, the style selection widget was a home brewed widget based on QFrame. It wasn't optimal and that is a British understatement. Now this widget is still home brewed, but based on a QComboBox.

Have anyone seen user jhk or know what his real name or email is

If so then please leave a note either here or on irc #calligra

He has started some work on Calligra Words that I'm really interested in and I havn't seen him since middle of december.

As most of you are probably well aware, since quite a while it is not very hard to write Qt applications to run on Android devices. A couple of weeks ago we at KO GmbH decided to look into how hard it would be to get KDE applications to run, and more specifically, if it would be possible to run Calligra with one of its mobile UI's on an android device.

(this is a continuation of the Fruits of Calligra Suite Sprint #2 series)

2012 started and I am still summarizing ideas from the Sprint. Today an integration idea: Office Forms for Calligra apps.

Forms are useful for improving data entry. Alternatives like entering data into spreadsheet cells can be too error-prone or tedious for the end-users. Forms reuse the GUI paradigm that is most probably already known and accepted by the user.

First, it is good to know forms were historically handled in popular office software. Extra functionality in MS Office or OpenOffice/LibreOffice still tend to be added using form elements (widgets) like buttons directly embedded into the document.

OpenOffice with embedded invoicing functionality. Note the buttons floating within the spreadsheet area.

First, I've changed the branches that are being built on build.kde.org to reflect the branching of 4.8.

Second I've incorporated a build of Qt 4.8 branch that is triggered once a week to keep up with fixes there.

Third I've tried to get a build of Qt 5 up and running also, however this is where I've hit some bumps. I've been unable to get Qt 5 to build and as such not all other jobs are working :(

FYI:

I just added some symbolic links on the api.kde.org machine to make accessing the 'stable' and 'unstable' dox a little easier.

So now stable points to 4.7 and unstable points to 4.8.

For example:
http://api.kde.org/stable/kdepimlibs-apidocs is the url for the stable kdepimlibs 4.7
http://api.kde.org/unstable/kdepimlibs-apidocs is url for the upcoming kdepimlibs 4.8

(this is a continuation of the Fruits of Calligra Suite Sprint #2 series)

You don't need to become a seasoned web developer to know the value of styling documents with the CSS. This Sunday the technology turns 15 since its initial release.

We describe presentation semantics separately of document (or data in general) and this makes us feel empowered as professionals. More often than not when we look over the shoulder of an inexperienced user who clicks BOLD, ITALIC in an office suite, playing with font size combo box and what not, we feel overwhelming urge to say "wait, you can do this so much easier".

And then when we start spreading the document styles religion, you know what? That is not thought-out.

Read on to see why.