Initial conversion of kdepim to TQt

This will probably require some tweaking before it will build under Qt4,
however Qt3 builds are OK.  Any alterations this commit makes to kdepim
behaviour under Qt3 are unintentional and should be fixed.


git-svn-id: svn://anonsvn.kde.org/home/kde/branches/trinity/kdepim@1227832 283d02a7-25f6-0310-bc7c-ecb5cbfe19da

3 files changed, 26 insertions, 26 deletions

diff --git a/karm/doc/Mainpage.dox b/karm/doc/Mainpage.dox
index 7c8aee5f5..4bb930f3f 100644
--- a/karm/doc/Mainpage.dox
+++ b/karm/doc/Mainpage.dox
@@ -24,7 +24,7 @@ order and can return a pointer to a KCal::Todo object that holds the same
 information.
 
 Preferences is a singleton that stores configuration options.  It raises
-signals when options change (for example, the location where the karm data is
+Q_SIGNALS when options change (for example, the location where the karm data is
 stored) so the application can react and adjust.
 
 KarmStorage is a singleton that creates an interface for storing KArm data.
@@ -35,7 +35,7 @@ format.
 
 /** \page sig_slot_index Index of Signals and Slots
 
-To get an understanding of the flow program, it may be useful to see an overview of all of the signals, slots, and
+To get an understanding of the flow program, it may be useful to see an overview of all of the Q_SIGNALS, Q_SLOTS, and
 connections. See \see connections to get an index of what signal is connected to which slot.
 
 \section overview Summary of what each class provides
@@ -60,9 +60,9 @@ connections. See \see connections to get an index of what signal is connected to
     <tr><td>Task</td>             <td>&nbsp;</td> <td>&nbsp;</td> <td>Y     </td> <td>&nbsp;</td></tr>
 </table>
 
-\section signals Listing of all of the signals
+\section Q_SIGNALS Listing of all of the Q_SIGNALS
 
-These are the signals:
+These are the Q_SIGNALS:
 <ol>
     <li>IdleTimer::extractTime(int)
     <li>IdleTimer::stopTimer()
@@ -83,7 +83,7 @@ These are the signals:
     <li>Preferences::hideOnClose(bool)
 </ol>
 
-\section slots Listing of the slots
+\section Q_SLOTS Listing of the Q_SLOTS
 
 \subsection public Public Slots
 
diff --git a/karm/doc/design b/karm/doc/design
index be9a425fa..fe37a3002 100644
--- a/karm/doc/design
+++ b/karm/doc/design
@@ -35,24 +35,24 @@ On Thursday 24 October 2002 06:37 pm, tomas pospisek wrote:
 > > Id  Description
 > > ---------------------------------------------------------------------
 > > 1   Karm shall provide a hierarchical structure of tasks. If a task
-> >     has at least one subtask it will be referred to as a parent task.
-> >     If a task has no children it will be referred to as a leaf task.
-> >     If a task has no parent tasks it will be referred to as a root
+> >     has at least one subtask it will be referred to as a tqparent task.
+> >     If a task has no tqchildren it will be referred to as a leaf task.
+> >     If a task has no tqparent tasks it will be referred to as a root
 > >     task.
 > > 2   A new task can be created as a child of any existing task.
-> > 2.1   If the parent had a timer active, it will continue to be active
+> > 2.1   If the tqparent had a timer active, it will continue to be active
 >
 > It depends on how you start it. If you double click it. Any other timer
 > will be stopped and the new task started. If you start it through the
 > start button, both tasks will be active. This a bug IMO. See at the bottom
 > for my proposal.
 >
-> > 2.2   The session time for the parent will not be changed by adding
+> > 2.2   The session time for the tqparent will not be changed by adding
 > >       the new child task.
-> > 2.3   The total time for the parent will not be changed by adding a
+> > 2.3   The total time for the tqparent will not be changed by adding a
 > >       the new child task.
-> > 3     Any task (parent, leaf, or root) may have an independent timer.
-> > 4     The time (both session and total) for a parent will be the sum
+> > 3     Any task (tqparent, leaf, or root) may have an independent timer.
+> > 4     The time (both session and total) for a tqparent will be the sum
 > >       of its independent timer and the sum of all of its child timers.
 > >
 > > Unstable Development
@@ -62,21 +62,21 @@ On Thursday 24 October 2002 06:37 pm, tomas pospisek wrote:
 > > Id  Description
 > > ---------------------------------------------------------------------
 > > 1   Karm shall provide a hierarchical structure of tasks. If a task
-> >     has at least one subtask it will be referred to as a parent task.
-> >     If a task has no children it will be referred to as a leaf task.
-> >     If a task has no parent tasks it will be referred to as a root
+> >     has at least one subtask it will be referred to as a tqparent task.
+> >     If a task has no tqchildren it will be referred to as a leaf task.
+> >     If a task has no tqparent tasks it will be referred to as a root
 > >     task.
 > > 2   A new task can be created as a child of any existing task.
-> > 2.1 If the parent had a timer active, it will be deactivated
-> > 2.2 The session time for the parent will set to zero
+> > 2.1 If the tqparent had a timer active, it will be deactivated
+> > 2.2 The session time for the tqparent will set to zero
 > > 2.2.1       The session time for the child will be initialized to the last
-> >     session time of the parent.
-> > 2.3 The total time for the parent will be set to zero.
-> > 2.3.1       The total time for the parent will be initialized to the last
-> >     total time of the parent.
-> > 3   Only a leaf task may have a timer. A parent may not have its own
+> >     session time of the tqparent.
+> > 2.3 The total time for the tqparent will be set to zero.
+> > 2.3.1       The total time for the tqparent will be initialized to the last
+> >     total time of the tqparent.
+> > 3   Only a leaf task may have a timer. A tqparent may not have its own
 > >     timer.
-> > 4   The time (both session and total) for a parent will be the sum
+> > 4   The time (both session and total) for a tqparent will be the sum
 > >     only of its child timers.
 >
 > I see where you want to go, but I think it's not the right direction for
@@ -134,7 +134,7 @@ idea but can't quite see how the interface should work.
 
 Ok. So, I'll undo the changes related to:
 * summing only leaf tasks
-* disallowing edits on parent tasks
+* disallowing edits on tqparent tasks
 _______________________________________________
 kde-pim mailing list
 kde-pim@mail.kde.org
diff --git a/karm/doc/updating_parents.html b/karm/doc/updating_parents.html
index 3b55ce30f..63587952f 100644
--- a/karm/doc/updating_parents.html
+++ b/karm/doc/updating_parents.html
@@ -34,6 +34,6 @@ You should get something like this.</p>
 	<tr><td>&nbsp;</td> <td>Session: 3</td> <td>Total: 18</td></tr>
 </table>
 
-<p>Since a parent task can have a timer active on it, it needs to be included in the summary 
+<p>Since a tqparent task can have a timer active on it, it needs to be included in the summary 
 Session and Total times. So, in this example, the Session time will jump three minutes for every
 minute the timer is active.</p>