Towards Kexi 2.6

I hope that Kexi like all the Calligra software will benefit from having a big release every 3 or 4 months. This way more than ever users become co-authors.

2.5 series
First, it's worth mentioning the 2.5 series received many improvements in already released 2.5.1 and 2.5.2 versions. Many users apparently found the forums (the link is now more convenient than mailing lists; not only questions moved here but for actual improvement and some planning discussions. It's honour to work with people that not only devote their limited time to the project but also use Kexi for their daily tasks, yet they store and process their valuable data with it!

As always it's important to have updated software so I can only encourage to do that. If you distro is slow with updates - politely request it every time, that's their job as a part of the equation. Many distros catched up and Calligra is now pretty well supported. There is no reason to keep software in the waiting-room too long when every feature and fix counts.



Evening conversation with my 7 y.o.:

me: Michael, tell me what's the next number after -1.


me: OK...

what's the next number after π?


Close enough as he answered after ~1 second, never even hearing about π ... unless he's secretly reading Wikipedia articles instead of playing games...

What's your interesting moment of this sort?


MS to reuse name from KDE and NSIS

Oh my. Microsoft has been using the "Metro" name to describe their new UX without prior careful checking for trademark infringement. PR blunder: Teutonic retailer Metro AG had to threaten them with legal action just two months before Win 8 release, when I bet some folders advertising Metro were already printed out.


40 years of Atari

This week we celebrated 40 years of Atari, once #1 computer brand.

For football and/or Atari fans - on time, some of us think that Mario Balotelli celebrated the anniversary too after scoring during the Germany vs Italy Euro 2012 semi-final match:

Anyway, have a good time at Akademy!


de Icaza: we're dropping XAML; QML's human friendly

Short story: Almost 3 years ago Miguel praised elegance of QML compared to XAML. It took so much time to abandon Moonlight but other than technical, the hottest reason is abandoning the XAML/Silverlight and whole .NET-on-Desktops idea by Microsoft itself.


Kexi's Easter Egg only on April Fools' Day

And Now for Something Completely Different.
Kexi's Easter Egg just appeared and quite magically it's only available on April Fools' Day ;)

To try, run any beta of Kexi 2.4 or 2.5 alpha. Then close the app, run again and look closer. Enjoy!

It works (I hope - untested!) thanks to the remote updates for the user feedback/news module[*] that we managed to fit within the Calligra 2.4 release plan. More on that later.

[*] BTW, you won't find any traces in the source code...


Q-Fridges - we're hiring!

There are job offers floating sporadically on planetkde so I guess this one would fit too especially that there are many related technologies involved.

You may remember my story about some crazy Qt device. Now there is apparent expansion both vertically and to other types of high-end devices, so:


Fruits of CSS2: Office Forms

(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.


Fruits of CSS2: Shared Themes

(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.


Fruits of CSS2: Eating Our Own Dog Food

It may seem obvious but eating our own dog food can definitely be good for your project's condition. Especially when it is maturing over time. How many testers can we have and how many personas for your user-centered design can we define and maintain? Usually just a few with the actual resources. Is only fulfilling needs of more or less fictional actors focusing on few use cases a good direction? Or does it put our vigilance to sleep?