Category Archives: KDE - Page 2

Clazy

Les développeurs KDE ne sont pas en reste pour ce qui est des outils pour aider à améliorer la qualité du code.

Sérgio Martins a développé “Clazy” un outils qui utilise Clang pour rechercher et avertir de certaines améliorations à faire dans votre code. Certains de ces plugins peuvent directement modifier le code source.

Comment le builder ?

Déjà récupérer le code source git clone git://anongit.kde.org/clazy

Il faut clang-devel >= 3.6

Ensuite il faut le builder et cela contre clang.

mkdir build && cd build && cmake  -DCMAKE_CXX_COMPILER=/usr/bin/clang++ -DCMAKE_C_COMPILER=/usr/bin/clang -DCMAKE_INSTALL_PREFIX=<path> …/ && make install

Maintenant il faut s’assurer que <path>/lib64/ est dans votre LD_LIBRARY_PATH sinon ça ne marchera pas.

Dès que tout cela est fait vous pouvez l’essayer sur un projet.

Comment l’utiliser ?

Il faut export la variable CXX

export CXX=”clazy”

Ensuite il faut dire ce que vous voulez évaluer.

Si vous voulez avoir tous les warning reportés par clazy, il suffit d’exporter une deuxième variable:

export CLAZY_CHECKS=all_checks

Après il faut reconfigurer le build sur votre projet

cmake -DCMAKE_INSTALL_PREFIX=<path> ../

et là vous aller pouvoir voir tous les variables et les infos résultant.

Les divers plugins:

  • bogus-dynamic-cast
  • foreacher
  • global-const-char-pointer
  • inefficient-qlist
  • qstring-uneeded-heap-allocations
  • qstring-arg
  • qstring-ref
  • function-args-by-ref
  • qmap-with-key-pointer
  • non-pod-global-static
  • reserve-candidates
  • variant-sanitizer
  • virtual-call-ctor
  • missing-typeinfo
  • implicit-casts
  • old-style-connect
  • detaching-temporary
  • assert-with-side-effects
  • qgetenv

Comment faire les fixes directement dans le code?

C’est très simple 🙂 Il suffit de le dire à Clazy en exportant la variable CLAZY_FIXIT

Par exemple:

export CLAZY_FIXIT=”fix-missing-qstringref”

Il y a que quelques plugins qui permettent la modification directe.

export CLAZY_FIXIT=”fix-old-style-connects” (change le style de connexion signal/slots (la nouvelle API qui est arrivée avec Qt5)
export CLAZY_FIXIT=”fix-missing-qstringref” (ça adapte le code pour utiliser const + ref lorsque c’est possible)
export CLAZY_FIXIT=”fix-fromCharPtrAllocations” (les 3 autres c’est pour réduire l’allocation lors de l’utilisation des QString)
export CLAZY_FIXIT=”fix-qlatin1string-allocations”
export CLAZY_FIXIT=”fix-fromLatin1_fromUtf8-allocations”

CLAZY_FIXIT ne permet pas de faire tout ensemble c’est un plugin par compilation ce qui est un peu logique car changer un fichier en court de route et remodifier encore derrière serait très risqué)

Mais pour fixer kde j’ai créé un script. Vous pouvez l’utiliser clazy-compile

il suffit de le renommer en .sh et le l’exécuter il fait tout pour vous.

Le futur ?

Ben il y a toujours des vérifications de code à faire et des optimisations donc ça va continuer. Mais j’en sais pas plus 🙂

KDEPIM 5.0

KDEPIM 5.0 is the port of kdepim to kf5/qt5.

The porting was started in may 2014. It was a long way because kdepim is not just kmail. It’s based on Akonadi server and all libraries from kdepimlibs.

The first step was to make Akonadi worked against Qt5.

The second step was porting kdepimlibs to make it work with akonadi server and KF5.

The last step was porting kdepim to kdepimlibs.

But we are able to obtain a stable version for 15.08 !

What contains kdepim 5.0 ?

It contains all original applications:

  • KMail
  • KAddressBook
  • KOrganizer
  • Kontact
  • KAlarm
  • Blogilo
  • AccountWizard
  • KNotes
  • grantleeeditor*
  • importwizard

What applications were removed?

KNodes was not ported to KDE4 pure and there is not a maintainer for it. So it was a big work for me if I wanted to port to pure KDE4 and porting after that to kf5

KTimeTracker was not maintains during some years and it was not really a pim application.

KDEPIM-Mobile: it was removed too because it depends against QtQuick1.0 it was not tested in 4.14 so in KF5 it was completly broken. So if some guy wants in the future to have it, it will be necessary to rewrite all.

KMailCVT: it was merged in the application importwizard.

What is news in kdepim 5.0?

  • First at all we ported to Qt5/KF5 🙂
  • New composer for KMail which has search/replace component integrated in composer directly.
  • contactprintthemeeditor allows to create some grantlee theme for kaddressbook
  • KAddressBook allows to send vcard file directly
  • Now we can manage IMAP folder which can be show in KOrganizer/KAddressBook.
  • Now we can share url on social network (as Facebook/Twitter etc.)
  • Add support for texttospeech based on Qt5TextToSpeech (which is not release yet).
  • Pimsettingexport has a console program now. (so we can backup from a script directly)
  • I merge all setting for email completion in an unique dialog.
  • SieveEditor has bookmark support.
  • a lot of others features that I don’t remember 🙂
  • KContacts has full vcard4 support.
  • Dan made a big work on Akonadi. He speeded up it a lot. It’s very fast now.

Future:

The future is in progress 🙂 KF5.1 is in development.

We have some new feature:

  • Sieveeditor has debug script support implemented based on “sieve-test” application.
  • KAddreebook has complement gravatar support
  • KAddressbook can display image based on an url
  • A lot of optimization was done
  • Some obsolete features were removed during Akademy coding session

KDEPIM report (week 26)

My focus was KAddressBook last week.

KAddressBook:

It’s not a complicated application, so I didn’t find a lot of bugs. But indeed as I maintain it I already fixed critical bugs.

Some fixes:

  • I improved gravatar support.
  • I added “Server Side Subscription” action. Before that it was necessary to go to kmail or go to resource settings and click on “ServerSide subscription” button. I was not userfriendly.
  • I continued to clean up code and I use new qt5 connect api.
  • I fixed a lot of bugs (as layout bugs etc.)

Other works in KDEPIM:

  • I fixed LDAP support which was broken when we ported it to QUrl now we can use it. It’s great 🙂
  • I fixed translation in korganizer.
  • AkonadiSearch dbus interface name was changed. So we couldn’t have email indexing information. Fixed.
  • I fixed Imap Resource interface too.
  • A lot of bugs were fixed in korganizer/kmail/sieveeditor etc.

Future:

Next week I will focus on KNotes and Kleopatra.

Other info:

Dan merged his work about replacing text protocol by a binary protocol for Akonadi. I confirm it’s faster.

He worked a lot to improve speed. Now kmail is very speed 🙂

I hope that he will add more speed patch 🙂

Sergio continued to add some optimizations in kdepimlibs/kdepim/akonadi. !!!

KDEPIM report

This week I focused my work on Akregator.

Akregator:

  • I fixed some errors on signal/slots
  • I reimplemented TextToSpeech support
  • I replaced QList to QVector where it was possible
  • I added some QStringLiteral
  • I used new Qt5 connect Api
  • I fixed some bugs.
  • I added support for share url (it allows to share url in Facebook/Twitter etc.)

Others work in KDEPIM:

  • I implemented ShareUrl, I use it in kmail/akregator
  • I fixed some bugs in Dav resource (thanks to Bruno Friedmann to provide me an access to an owncloud server). It was mainly GUI bugs.
  • I fixed some crashes in Accountwizard
  • KMail uses KPIM::CompletionConfigureDialog to configure addressline settings (it avoids 3 different dialogbox).
  • I added bookmarks support in Sieveeditor
  • I added spellchecking support in plaintexteditor.
  • I fixed application translations

Future:

Next week I will focus on the KAddressbook.

I hope that I will have more bug report about it.

Other Info:

Dan works on akonadi to replace protocol based on text to use a binary protocol directly.

He saw a lot of improvement. He hopes to merge it in master soon.

To conclude:

We are in good way to have a stable version for 15.08.

I was not sure some about it some weeks ago 🙂

KDEPIM KF5 status and test plan

Status:

As you know we decided to release kdepim kf5 in 15.08. (We have 2 months yet).

I use kdepim kf5 by default now on my main computer. Of course when I started to use it all apps crashed, or there was some part of code which was not ported to kf5 yet.

I tried to fix all crash that I found, I fixed a lot of bugs, and I finished some features (as Gravatar support, rewrite the kmail composer, reimplement text to speech etc.)

Now all applications work fine (no direct crash when I launch them). But of course it’s not perfect. I can’t use all application all the time. So I need some help to find bugs.

Test plan:

There is a lot of application in kdepim:

  • KMail
  • KAddressBook
  • KNotes
  • Kontact
  • KOrganizer
  • SieveEditor
  • AccountWizard
  • ImportWizard
  • etc. (Some others minor applications)

So I decided to focus each week on an application.

I will not work at 100% on a specific application, but I will use it a lot during this period and I will try to fix each bug that I will find.

As I worked a lot on KMail, I will not focus on it next week.

I will focus on Akregator, so if you can test it and you can report me bugs. I will not fix all bugs about akregator but I will try to for all porting bugs. I don’t have time to debug all akregator bugs 😉

How to test it ?

It’s better to use last version from git because I fix a lot of bugs each week. (I don’t know if distro provides snapshots).

I will increase version of kdepim each week so we will be sure that bug is against last version.

Limitation:

KDEPIM uses a lot of resource as Dav, Openxchange, etc. I don’t have access to them. So I can’t debug so it will good if some people will able to test them.

Thanks for your help.

KDEPIM KF5

History:

I started porting of kdepim to KF5 1 year ago (in may 2014). When I started it I thought that it should be easy. But it was not easy because firstly KF5 was not release and it was not stable, there was some bugs. Secondary kdepim is not just KMail, it contains the kdepim libs + akonadi + kdepim runtime + kdepim apps (as korganizer, kmail, etc.).

The first step was to adapt cmake files to new framework environment.

I removed some applications which were not ported to pure kde4 (depended to kde3support), or some unmaintained applications (as ktimertracker) etc.

The second step was to split kdepimlibs as frameworks (for the moment just one lib is released).

The last step was removing kdelibs4support (it’s still in progress). This step is very long because we need to port each kdepimlibs library (The big problem is the KLocale porting… It’s complicated and there is not Howto for it…).

Status:

Last week I decided to use kdepim kf5 as default on my computer.

It was not an easy decision because I use KMail for my work.

But before to do it, I implemented a class for migrating data applications, because now we use XDG path and not .kde path for config/apps data etc. as it was in kde4

First impression:

I am impressed because KMail works fine 🙂 I can send/receive emails !

KAddressBook was totally broken but I fixed it last week end.

KOrganizer worked correctly.

SieveEditor works very fine.

For other applications they are working fine but I didn’t have time to evaluate them correctly.

Dead line:

We decided to release kdepim with kf5-15.08, so in 2 months.

Is it possible to do it ?

I hope 🙂 But it will hard to fix all bugs without some helps.

kdepim-4.14 ?

I never stopped to work on kdepim-4.14, but indeed now that I switch to kf5 I will reduce the time that I took to debug it.

But I will continue to backport the fixes on kdepim-4.14 until we release kf5, because I am not sure at 100% that new version will kf5 version.

Future:

I will continue to debug all applications, I will finish some new features until we release it.

How to help ?

Just take an application, use it as usual and report all bugs that you find.

Full KF5

Depuis la semaine dernière j’utilise aucune application kde4.

ça veut dire que j’utilise kdepim kf5.

Oui j’ai tenté mais je l’ai pas fait n’importe comment. Déjà j’ai mis en place une vraie migration. (les folders n’étant pas migré ça posait quelques problèmes). De plus j’avais déjà fait un maximum de test à coté.

Mais bien sur ça vaut pas le test en live 🙂 Et là ben… comment dire… des bugs à profusion. Genre kaddressbook ne pouvait pas stocker les nouveaux contacts.

Donc j’ai passé du temps à rendre kdepim utilisable.

Mais maintenant c’est parti pour une longue chasse aux bugs 🙂

L’objectif c’est 15.08.

Est ce que je crois que ça sera opérationnel ? Heu… bien sur 🙂 Enfin si on est plus que 2 à bosser dessus. Dan est en train d’améliorer Akonadi, et moi je fixe le reste.

Donc forcément ça prend du temps.

Faut en même temps avoir des gens qui testent kf5 🙂

Est ce que je vais laisser tomber kde 4.14 ?

Bien sur que non je vais continuer à le fixer sans problème surtout que je suis pas sur que kdepim kf5 sorte vraiment pour la 15.08.

Là aussi j’ai besoin de bugs reports.

Voilà 🙂

kdebugsettings 1.0

Before to increase version to 1.0 I moved it from kdereview to kdeutils.

I added new features of course 🙂

Now you can import/export settings directly.

You can create a category file and it will load in kdebugsettings.

It’s very useful for big project as kdepim for example when I add a new logging categories for each module, but I don’t want to wait a new release.

So you need to create a “.categories” file and install it as “install( FILES kdepim.categories DESTINATION ${KDE_INSTALL_CONFDIR} )”

Future:

No idea 🙂 If you have so wishlist send me a bug 🙂

Embedded QML in qrc file

KDAB works on a lot of projects based on qml.
But sometime for specific applications it’s not safe to store directly qml file on file system.
As you know the QML files are plain text files.

For example if an user can have access to qml files he can change the logic of the application.
This is not critical for a application as  “Clock” but it can be critical in other domains.

So there is two methods to avoid it:

  • Using the Qt Resource for embedding the QML files (This blog will explain how to do).
  • Using the qtquickcompiler to generate a precompiled QML file (But a commercial license is needed)

The Qt Resource system allows to store a lot of data/binary files in executable directly.
Data can be an icon, a translation file, etc. and of course a QML file.

This blog will explain how to use it in a QML plugins implemented based on a QMLExtensionPlugins class.

For a standard application which uses some QML files this is very easy. We put them in a qrc file and we can access to it directly with a line as “view.setSource(QUrl(QStringLiteral(“qrc:/plugins.qml”)));”

We will see how to do it on a example based on qmlextensionplugins.

We adapted a qt qmlextensionplugins example (It’s the Clock example that you can find in qt source code) to create an little application.
Source code can be download here

It will display a clock.
The pro files were adapted to allow to install apps in “install” directory.
(qmake && make && make install).

When you look at install folder you can see all these files.

./plugins.qml
./extensionpluginsapps
./TimeExample/hour.png
./TimeExample/minute.png
./TimeExample/clock.png
./TimeExample/qmldir
./TimeExample/center.png
./TimeExample/libqmlqtimeexampleplugin.so
./TimeExample/Clock.qml
./TimeExample

=> As you see the QML files are stored on filesystem.

Now what we need to change for using Qt Resource ?

We will create a Qt Resouce file which will embed all qml files and icons.


<RCC>
<qresource prefix=”/clock”>
<file>Clock.qml</file>
<file>center.png</file>
<file>clock.png</file>
<file>hour.png</file>
<file>minute.png</file>
</qresource>
</RCC>

There is not a specific prefix.
And you just need to adapt qmldir for using a specific QtResource path (use qrc:///<path>)


module TimeExample
Clock 1.0 qrc:///clock/Clock.qml
plugin qmlqtimeexampleplugin

Of course the file qmldir can’t be stored in Qt Resource file otherwise  the application will not be able to  find plugin.

As you see now the list of files in install directory is limited to:

./extensionpluginsapps
./TimeExample/qmldir
./TimeExample/libqmlqtimeexampleplugin.so
./TimeExample

(of course I stored plugins.qml in another qrc file).

So the application is more safe now.

You can get source code here

KDebugSettings (0.3)

I improved kdebugsettings (and increased version to 0.3).

What’s new:

  • I added an Apply button so now we can test rules directly
  • We can customize kdeapplication rules, before we could just enable/disable them, now you can specify that you want to show just Debug/Critical/All (as for custom rules)
  • There is a new tab which shows rules which are stored in QT_LOGGING_RULES environment variable.
  • I added a warning when a rules starts by “*” which can override all others rules.
  • I added an Help button which show Qt qloggingcategory page

Future:

I will add a button to export/import rules.

I will ask to move it in kdereview. I think that it can move in official package.

Screenshots:

Warning about "*" rules

Customize kdeapplication rules

Customize rule