summaryrefslogtreecommitdiffstats
path: root/karm/doc
diff options
context:
space:
mode:
authortpearson <tpearson@283d02a7-25f6-0310-bc7c-ecb5cbfe19da>2011-08-10 22:19:39 +0000
committertpearson <tpearson@283d02a7-25f6-0310-bc7c-ecb5cbfe19da>2011-08-10 22:19:39 +0000
commit36a36a5c1015aa0d03f4515c401e907ddb9d6291 (patch)
tree0212ba6d2c749043134005a41f2bd0379619d40f /karm/doc
parent4c6f8d69e2d1501837affb472c4eb8fec4462240 (diff)
downloadtdepim-36a36a5c1015aa0d03f4515c401e907ddb9d6291.tar.gz
tdepim-36a36a5c1015aa0d03f4515c401e907ddb9d6291.zip
rename the following methods:
tqparent parent tqmask mask git-svn-id: svn://anonsvn.kde.org/home/kde/branches/trinity/kdepim@1246260 283d02a7-25f6-0310-bc7c-ecb5cbfe19da
Diffstat (limited to 'karm/doc')
-rw-r--r--karm/doc/design36
-rw-r--r--karm/doc/updating_parents.html2
2 files changed, 19 insertions, 19 deletions
diff --git a/karm/doc/design b/karm/doc/design
index fe37a300..b647f282 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 tqparent task.
+> > has at least one subtask it will be referred to as a parent 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
+> > If a task has no parent 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 tqparent had a timer active, it will continue to be active
+> > 2.1 If the parent 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 tqparent will not be changed by adding
+> > 2.2 The session time for the parent will not be changed by adding
> > the new child task.
-> > 2.3 The total time for the tqparent will not be changed by adding a
+> > 2.3 The total time for the parent will not be changed by adding a
> > the new child task.
-> > 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
+> > 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
> > 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 tqparent task.
+> > has at least one subtask it will be referred to as a parent 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
+> > If a task has no parent 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 tqparent had a timer active, it will be deactivated
-> > 2.2 The session time for the tqparent will set to zero
+> > 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.2.1 The session time for the child will be initialized to the last
-> > 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
+> > 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
> > timer.
-> > 4 The time (both session and total) for a tqparent will be the sum
+> > 4 The time (both session and total) for a parent 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 tqparent tasks
+* disallowing edits on parent 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 63587952..3b55ce30 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 tqparent task can have a timer active on it, it needs to be included in the summary
+<p>Since a parent 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>