This page is dedicated to discuss issues related to the port to KDE4. The effort is ongoing and it is not considered stable. It is only suitable for early adopters. If you are looking for the stable version, go to the official page of KMyMoney
KMyMoney 3.95 has been released on Dec 28th 2009 tarball.
Alternatively, you can get the source from the KDE SVN. (see link below)
KMyMoney depends on KDE SC 4.3. Specifically on kdelibs and kde PIM libs. Additionally, you may want to install other libraries that will provide additional functionality:
That said KMyMoney cannot be compiled using KDE SC 4.4 (trunk) right now due to an undefined method in a PIM class. We are currently trying to solve the issue with the PIM guys.
Get the source from KDE SVN or the latest tarball from https://sourceforge.net/projects/kmymoney2/files/KMyMoney-KDE4/3.95.0/kmymoney-3.95.0.tar.bz2/download
To install read the README.cmake file in the root folder of the source. The basic steps are the following:
$ mkdir build $ cd build $ cmake .. -DCMAKE_INSTALL_PREFIX=/usr/ $ make $ make install
This last step should be executed with root privileges (either switch to root or use sudo, or the appropiate steps on your installation)
To execute, either look for KMyMoney on the Office menu, or type kmymoney in a console window.
This version is only suitable for early adopters. It will behave fairly well, but the application might crash and you may lose some data. Make backups often.
For 3.95 version and later, we use the Bugzilla tracker at bugs.kde.org. Any bugs you find, please report it and assign to product kmymoney4. Also, if you need help write to email@example.com.
As a first step, we are leaving Qt3Support, if possible. There are cases when it is best to port to the corresponding Qt4 classes. Examples of these are the QButtonGroups, KActions, KPageWidget, QTabBar
For now, focus on make it work. Assess whether it will be faster using Qt3Support or a newer class.
The repository to use is the one in KDE SVN. svn://anonsvn.kde.org/home/kde/trunk/playground/office/kmymoney.
These are the issues that need to be fixed first before releasing a beta version.
I thought that we can put here a list of features that are known to work (after a developer testing):
|Tips and tricks||Working|
|Plugins||Working||KBanking plugin needs to be tested: I was able to download statements (2009-12-24)|
|Database||Working||Passes unit tests for MySQL, PostgreSQL and SQLite3. (fvilas)|
|GPG||Working||Needs testing, does not compile with KDE trunk|
Also, here you have the KrazyEBN report, which reports common issues on the code. Krazy Report
Please include the areas you are working on to avoid overlapping with other developers.
The following are on my TODO list but that does not mean that I don't need any help on them:
I will work on the account selector, probably migrate it to Qt4 widgets, because it does all kinds of weird stuff that can be probably optimized. (fixed by conet)
Working on the i18n and documentation issues with KDE-i18n team.
Also going through the Krazy report, and fixing issues there.
I will try to keep the strings together and work on coordination for the integration of/with other KDE applications. On the code front maybe setting up the Qt-Designer plugin for the KMyMoney widgets.
Please report here the issues you find.
libkdchart is an extract from koffice. If we find a bug there, it is best to report it to the kdchart maintainers
The mymoney folder contains the engine. It is covered by the unit tests and they run ok. This is a critical area of the application, so check with Thomas or Alvaro before making a change.
Of course, if you find a critical bug in anywhere on the application, send a mail to the mailing list or report it on bugs.kde.org.
https://mail.kde.org/mailman/listinfo/kmymoney-devel. Use it to discuss issues related to the port to KDE4.
Alvaro Soliverez is coordinating the KDE4 effort. You can reach me at asoliverez at gmail.com or on IRC under Hei_ku in the #kmymoney channel. Alternatively, you can contact Thomas Baumgart on the developers list.
(Contact the coordinator if you are willing to contribute)
Have it ready for kdereview before the end of the year. Is it too optimistic?