diff options
Diffstat (limited to 'doc')
| -rw-r--r-- | doc/hackers.guide.txt | 30 |
1 files changed, 1 insertions, 29 deletions
diff --git a/doc/hackers.guide.txt b/doc/hackers.guide.txt index 0d421b95..8d8c0c0a 100644 --- a/doc/hackers.guide.txt +++ b/doc/hackers.guide.txt @@ -875,42 +875,14 @@ For the moment, in random order: - Widgets will be probably abstracted in kvilib/tal. -- Qt 4.x has no QCString anymore. It uses QByteArray instead. From my own - point of view this is ugly since the name is misleading and QByteArray - is forced to mantain the null terminator which is not needed - in normal "byte array" operations...but well, we have to live with it. - kvilib has kvi_qcstring.h that defines the KviQCString MACRO. - It expands to QCString under Qt 3.x and QByteArray under Qt 4.x. - -- Use: - #ifdef COMPILE_USE_QT4 - to check if the compilation requires Qt 4.x or Qt 3.x. - Later this *might* be automatically replaced with - #if TQT_VERSION >= 0x040000 - -- Use: - ./configure --enable-debug --enable-qt4 --with-qt4-moc=/path/moc - make clean - make - to switch to Qt 4.x Use: ./configure --enable-debug make clean make - to switch back to Qt 3.x + to build. - Use less possible Qt3Compat features. -- Before committing to the svn always test your changes under Qt 3.x: this is - the primary goal for now: keeping 3.x compatibility. - Qt 3.x-only developers are encouraged (but not required) to test their - changes agains Qt 4.x. - -- Use the KviQString::* wrapper functions around QString (take a look at - kvi_qstring.h) even if there exist QString functions that do the same - thing. This is because the QString interface has changed a lot between - Qt 3.x and Qt 4.x and KviQString introduces a compatibility layer. - - 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. |