-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hello Tobias!

Am Donnerstag, 5. Oktober 2006 21:33 schrieb Tobias Klein:
> I'd like to participate in kde-pim development. 

Welcome to PIM!

> In short I'd like to help with the KDE4 porting and development of the
> kdepim apps / libs. My primary target would be KMail, but I'll
> probably also stumble across KAddressbook, KOrganizer, etc.
>
> After a short view into the existing code in svn I noticed that there
> are several parts of the application-GUI's broken. A first step would
> be to get the applications to a state in which they can be basically
> used as before the transition to qt4. 

Yes, a lot of visual stuff is broken. 

If your want to debug UI issues, then the KUIExtractor can help you (see 
playground/pim/uiextractor), in particular to debug where extra spaces come 
from. In Qt 4 each layout has a margin and a spacing, while in Qt3 these were 
properties of the containing widget. So now, almost always when you add a 
layout to widget or to another widget you manually need to set the margin to 
0, otherwise you get a double spacing.

To run any application in the uiextractor, simply compile and install 
uiextractor with Qt4 and kdelibs4.  You can then simply call
    kuiextractor applicationname args
(e.g. kuiextractor korganizer) to UI-debug the application (without any 
re-compiling or anything. It's all done via a DL_PRELOAD'ed library that 
installs the corresponding hooks). If you keep Ctrl+Shift+Alt pressed and 
move the mouse, a passive popup will tell you the widget (and the class of 
the widget) under the cursor, plus the spacing and margin of the layout.

See e.g.
http://www.fam.tuwien.ac.at/~reinhold/KOrganizer/KUIExtractor_KOrganizer.jpg

Notice the red frame around the widget under the cursor and the corresponding 
passive popup in the upper left corner of the screen.

> I think it is also important to 
> do as much refactoring as possible and identify those parts of the
> API which are broken by design due to their long development
> history ;-). A good approach would be to separate gui-views
> consequently from the underlieing data models (MVC) and prepare the
> integration with akonadi.

Absolutely. KOrganizer mostly has its own Model-view structure, but sooner or 
later that should be moved to Qt MVC.

> Is anyone already working on the things mentioned above? 

I doubt it...

Cheers,
Reinhold
- -- 
- ------------------------------------------------------------------
Reinhold Kainhofer, Vienna University of Technology, Austria
email: reinhold@kainhofer.com, http://reinhold.kainhofer.com/
 * Financial and Actuarial Mathematics, TU Wien, http://www.fam.tuwien.ac.at/
 * K Desktop Environment, http://www.kde.org, KOrganizer maintainer
 * Chorvereinigung "Jung-Wien", http://www.jung-wien.at/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)

iD8DBQFFKl1gTqjEwhXvPN0RAuvwAJ431ehFer89B6e0JB0ds9zXZFoMqgCeKd2c
aBsBoT6sHVg8DaFgE2bcJ4k=
=5qej
-----END PGP SIGNATURE-----
_______________________________________________
kde-pim mailing list
kde-pim@kde.org
https://mail.kde.org/mailman/listinfo/kde-pim
kde-pim home page at http://pim.kde.org/