14 Sep
2013
14 Sep
'13
10:16 a.m.
2013/9/14 Timothy Pearson <kb9vqf(a)pearsoncomputing.net>
Since TDE now uses TQt3, the old Qt3 libraries
(unmaintained as they are!)
can be installed at the same time as TDE. At this point I don't see any
serious drawbacks to changing the TQt API; would anyone consider it a
major problem if Trolltech had changed the Qt3 API? We all probably would
have complained about it a bit and then moved on--how is this different
from the TDE project *improving* Qt3/TQt3 (e.g. adding proper threading
support) and changing the API as needed?
Tim
For now — yes, it's ok to do with TQt api anything we want to, but when it
was introduced for the first time IMO it was a huge issue, that called a
lot of concerns about further destiny of the TDE.
AFAIK Trolltech hadn't changed the Qt3 API. It was backward-compatible
through all it's lifetime... They had to release the Qt4 to change it.
That's why we are here now. Fix me if I'm wrong.
2013/9/14 François Andriot <francois.andriot(a)free.fr>
I confirm that, with TDE R14, I manage to get working
KDE4, working KDE3
and working TDE at the same time on the same openSuse computer.
So we leave alone QT3 for KDE3, now TDE is using TQT3 with its own API
without conflict with anyone else.
Francois
At least one conflict is still there: both tqt and qt3 uses QTDIR
environment
variable.
If we started to talk about it, Tim, can we do something about that?
Btw: what are your plans about tqt/tqtinteface?
We are about to remove the second one because it doesn't needed anymore,
isn't it?