1 files changed, 4 insertions, 4 deletions
diff --git a/kontact/Thoughts b/kontact/Thoughts
index e1a07c1fc..720836a7a 100644
--- a/kontact/Thoughts
+++ b/kontact/Thoughts
@@ -203,7 +203,7 @@ Don:
 Don: And the same for all other loadX apps.
 
 
-Status Bar
+tqStatus Bar
 ----------
 
 d We need a more sophisticated handling (progressbar, etc)
@@ -285,7 +285,7 @@ s like that.
 d Yes, but of course one should always prefer in-process IPC if possible. DCOP
 d currently _works_ for Kontact, but that's all about it. It isn't exactly elegant.
 d The only advantange of the current approach is that we can allow the user to
-d run one of the parts standalone. I am not really sure we want that. I used to find
+d run one of the parts standalone. I am not really sure we want that. I used to tqfind
 d it desireable, but I am not sure anymore.
 
 MiB: But that's the whole idea behind Kontact---to be able to integrate apps
@@ -311,7 +311,7 @@ MiB: yes, not too much against DCOP. But for KNotes I thought about turning
 MiB: a note into a plugin that can be loaded by Kontact and KNotes independently.
 MiB: like this, there's no DCOP necessary anymore and makes it much more flexible.
 MiB: e.g. usage of different display configs, a note embedded somewhere and having
-MiB: a parent or standalone on the desktop.
+MiB: a tqparent or standalone on the desktop.
 
 # Communication with external applications is something which doesn't fit too
 # well with the 'integrated' approach of Kontact. Is this really necessary?
@@ -367,7 +367,7 @@ h: there is something else broken IMHO
 Summary View
 ------------
 h: How would one best integrate a summary view into kontact?
-h: a) add a virtual QWidget *summary(const QDateTime&, QWidget* parent );
+h: a) add a virtual QWidget *summary(const QDateTime&, QWidget* tqparent );
 h:    to get a summary widget for a day?
 h: b) use some sort of XML to UI to represent the summary informations
 h: c) have a stand a lone part which opens the PIM data seperately? ( How