12 Feb
2012
12 Feb
'12
8:20 a.m.
On 02/12/2012 01:25 AM, David C. Rankin wrote:
These are the exact reasons I stopped to the move to Qt4 and picked up
maintinance of Qt3 (now becoming TQt3). I gave the conversion effort my
best shot (which took many, many months of effort) and stopped once it
became apparent how extensive Qt4's limitations were (especially in
drawing operations and native X11 window handling) and also how buggy Qt4
really is.
Thanks for the encouragement!
Tim
I don't see we save any effort going with
Qt4. I truly believe that
manpower
required would be less to maintain Qt3 rather than continually shooting
at the
moving target Qt4 will provide depending on whatever whim Trolltech has
that week.
If it ain't broke -> don't fix it :)
Let me qualify that,
I understand that the Qt4 toolset would make it easier for upstream
application support at sometime in the future. There is nothing wrong with
being
able to support (properly) apps built expecting Qt4. I don't know if that
could
be accomplished with a minimum "Qt4-runtime" similar to the
"KDE4-runtime"
without having to completely abandon Qt3.
I think a wise project would put out TDE-3.5.13 and work to put out an
alternative TDE-Qt4-3.5.13. I don't think they are mutually exclusive. But
I do
believe that a whole sale move to Qt4 would break over half-a-decade of
styles
and decorations that currently make Trinity well Trinity :)
Keep up the great work!