summaryrefslogtreecommitdiffstats
path: root/doc
diff options
context:
space:
mode:
authorMichele Calgaro <michele.calgaro@yahoo.it>2024-02-20 11:46:59 +0900
committerMichele Calgaro <michele.calgaro@yahoo.it>2024-04-02 16:49:11 +0900
commitf887a3ee8f51b158ffb32d88e1489a6f2e0a9dbb (patch)
tree3e047d1a1fc6d4e3b55af254251f52723fb46455 /doc
parentab992aba703fea5fba22a7f7fc3044d9306277ca (diff)
downloadkvirc-f887a3ee8f51b158ffb32d88e1489a6f2e0a9dbb.tar.gz
kvirc-f887a3ee8f51b158ffb32d88e1489a6f2e0a9dbb.zip
Replace Qt with TQt
Signed-off-by: Michele Calgaro <michele.calgaro@yahoo.it>
Diffstat (limited to 'doc')
-rw-r--r--doc/hackers.guide.txt42
1 files changed, 5 insertions, 37 deletions
diff --git a/doc/hackers.guide.txt b/doc/hackers.guide.txt
index 2b092285..693cf548 100644
--- a/doc/hackers.guide.txt
+++ b/doc/hackers.guide.txt
@@ -94,7 +94,7 @@ The source tree
| | | Threads, localisation, env, time, shared library..
| | |
| | `-- tal Toolkit Abstraction Layer: wrapper classes that
-| | inherit from KDE* or QT classes, depending on the
+| | inherit from TDE* or TQt classes, depending on the
| | compilation type.
| |
| |-- kvirc The KVIrc executable sources
@@ -374,7 +374,7 @@ Coding tips
an existing kvi_* wrapper and use that one instead. The wrapper is there
because of portability issues.
-- Don't use the STL features: anything that you need IS either in the Qt library
+- Don't use the STL features: anything that you need IS either in the TQt library
or in kvilib.
- Windows compilation has COMPILE_ON_WINDOWS #defined and a KDE compilation
@@ -407,7 +407,7 @@ KviStr
(especially in GUI modules) to handle correctly the UNICODE character set.
TQString
- The Qt UNICODE string. See the Qt documentation for details.
+ The TQt UNICODE string. See the TQt documentation for details.
This is the string that should be mostly used in KVIrc in the near future.
Take care: in general it is NOT null terminated.
There is a KviQString wrapper namespace (#include "kvi_qstring.h") that
@@ -423,13 +423,13 @@ TQString
concurrent threads.
(const) TQChar *
- The array of Qt chars. This is usually obtained by callling
+ The array of TQt chars. This is usually obtained by callling
KviQString::nullTerminatedArray() which itself is a hack...
This array is used in some functions that were written for
const char * strings and haven't been ported completely.
QCString
- The Qt non UNICODE string. See the Qt documentation for details.
+ The TQt non UNICODE string. See the TQt documentation for details.
The Goal:
- Use KviStr only where it is strictly needed (for protocol or performance
@@ -856,38 +856,6 @@ release is likely to be 3.2.7 while the next official stable release
might be 3.3, 3.4 or even 4.
-------------------------------------------------------------------------------
-Porting to Qt 4.x (while mantaining Qt 3.x compatibility) (Work In Progress)
--------------------------------------------------------------------------------
-
-For the moment, in random order:
-
-- Avoid using TQString::null, use KviQString::empty instead.
- This is because Qt 4.x does NOT have a null static variable. Qt 4.x in fact
- does not have the distinction between null and empty strings (Note that for
- KviStr this choice was made since the beginning).
- Do NOT replace all the uses of TQString::null with TQString() (as the qt 4.x
- porting documentation suggests) since for Qt 3.x this construct is SLOW.
-
-- We're building a compatibility layer in kvilib.
- Before using ANY Qt class, look if there is an override in kvilib.
- In fact always, prefer Kvi* classes over the Q* ones and include
- the "kvi_*.h" files instead of the <qt*.h> ones.
-
-- Widgets will be probably abstracted in kvilib/tal.
-
- Use:
- ./configure --enable-debug
- make clean
- make
- to build.
-
-- Use less possible Qt3Compat features.
-
-- Do not use the "char * c = KviQString::toUtf8(string).data();" construct.
- It leads to crashes on many compilers since the returned KviQCString
- goes out of scope just at the end of the instruction.
-
--------------------------------------------------------------------------------
Code documentation
-------------------------------------------------------------------------------