[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-pim
Subject:    [Kde-pim] KPilot Open Jobs
From:       Adriaan de Groot <adridg () cs ! kun ! nl>
Date:       2001-12-20 22:45:46
[Download RAW message or body]

Are you bored? Is your love life lackluster? Do you want to MAKE MONEY
FAST? Do you want to FIND OUT WHAT MICROSOFT DOESNT WANT YOU to KNOW? ...
um ... back to reality: If you'd like to help out with KPilot but don't
really know where to start, and would like to get a little acquainted with
the code, the coding style, and some of the conventions used in KPilot,
read on! If you have grep and a text editor, read on!

The code, and particularly the debugging code, has gone though a number of
phases. For a while, there was that --debug 1023 stuff. I've decided that
that's actually kinda cumbersome for a GUI program, and debugging has
switched back to an all-or-nothing kinda thing. So some things need to be
changed all over the source code, and that's just the kind of exploratory
job for someone with grep and vi. In particular:

* kdDebug() everywhere needs to change into DEBUGCONDUIT, DEBUGKPILOT,
  or one of the other DEBUG* macros defined in kpilot/lib/options.h.
  This will send the debugging output to the sensible debug area.
  Which one you choose depends on where the file lives -- choose wisely.

* DEBUG* calls everywhere need to be surrounded by #ifdef DEBUG #endif.
  This is because some compilers don't optimize away unused strings,
  leading to big bulky (well, sorta) executables. Adding the #ifdefs
  makes sure that there's nothing at all left over from the debugging code
  when debugging is turned off.

* __FUNCTION__ needs to be replaced by k_funcinfo. The popmail conduit is
  bad for that one, at the very least.

* if (debug_level) and its cousin if (debug_level & SOMETHING) need to be
  removed, along with the set of brackets they introduce. The debugging
  statement (usually just a kdDebug() << whatever << endl;) needs to be
  out-dented one tabstop, to line it up properly.

These are, in one sense, rotten little jobs. But they'll take you to all
the corners of the KPilot code, show you some ugly (and some not-so-ugly)
code, and give you a feel for "the lay of the land." After that, fixing
all the remaining off-by-one bugs in the vcal conduit should be a breeze.


-- 
+------------------------------+
| Adriaan de Groot             | Drinken, in een bepaalde tijd symbolisch,
| http://www.cs.kun.nl/~adridg | is in een andere tijd zuipen - Wittgenstein

_______________________________________________
kde-pim mailing list
kde-pim@mail.kde.org
http://mail.kde.org/mailman/listinfo/kde-pim
kde-pim home page at http://pim.kde.org/
[prev in list] [next in list] [prev in thread] [next in thread]