Completed kdocker -> tdedocker renaming effort.

Signed-off-by: Michele Calgaro <[email protected]>

1 files changed, 10 insertions, 10 deletions

diff --git a/HACKING b/HACKING
index d782444..94dd3cb 100644
--- a/HACKING
+++ b/HACKING
@@ -15,11 +15,11 @@ Words of wisdom
 
 6. There's do or no do. There's no try.
 
-KDocker Window Docking Strategy and a little bit of history
+TDEDocker Window Docking Strategy and a little bit of history
 -----------------------------------------------------------
 Couple of things that will help you if you are looking through the code.
-I wanted a single instance of KDocker to be running all the time. So,
-whenever a new instance of KDocker was created it would ask the previous
+I wanted a single instance of TDEDocker to be running all the time. So,
+whenever a new instance of TDEDocker was created it would ask the previous
 instance take over.
 
 Two things to know about
@@ -39,25 +39,25 @@ for a better understanding.
 
 2. Sending ClientMessages to previous instances with the program name and
 arguments is painful and makes the code more complex. Before 1.0, I used to dump
-all the program arguments in ~/kdocker.<pid> and send the pid in a 
+all the program arguments in ~/tdedocker.<pid> and send the pid in a 
 ClientMessage. The file is then deleted after processing. As of 1.0, I set a
-property _KDOCKER_<pid> on the KDocker initial instance's window which holds
+property _KDOCKER_<pid> on the TDEDocker initial instance's window which holds
 the program arguments. (The correct way to transfer information is using
 XSelections)
 
 TRACING
 -------
-Add the following line in kdocker.pro (in fact just uncomment it)
+Add the following line in tdedocker.pro (in fact just uncomment it)
 DEFINES += ENABLE_TRACING
 
 Now do a "make clean" and "then make".
 
-Launch KDocker. Try recreating the problem.
+Launch TDEDocker. Try recreating the problem.
 - Right Click on the tray icon.
-- Choose "About KDocker"
+- Choose "About TDEDocker"
 - You should see a button called "Show Trace". Please note that this button
   will appear only when compiled with tracing
 - Try debugging yourself or send it to me
-- If you send SIGUSR1 to the KDocker process, it will dump all the trace to
-  ~/kdocker.trace
+- If you send SIGUSR1 to the TDEDocker process, it will dump all the trace to
+  ~/tdedocker.trace