> On Sat, Sep 14, 2013 at 5:41 AM, Timothy Pearson
> <kb9vqf@pearsoncomputing.net> wrote:
>>> 2013/9/13 Aleksey Midenkov <midenok@gmail.com>

<snip>

> There is no need in that. UI programs are not high-load programs, they
> don't
> require bleeding edge performance optimization. Everything worked fine
> there
> before Trinity! You've digging wrong places. Do UI, not system libs.

So in other words, our users are supposed to just put up with frequent
unresolvable crashes that were traced back to fundamental flaws in
Qt3/TQt3, while we change the stable UI that our users expect us NOT to
significantly change?  This is not 1999 anymore, users own systems with
multiple cores as a rule now, and some of the original KDE 3 code simply
was not thread safe!  Sure, it worked most of the time on hyperthreaded
processors, but not on real multicore systems, just search our bugtracker
for threading related bugs for a sampling of the problems *fixed* by
changing the TQt3 library.

As I have mentioned before, if you would like to see TDE on Qt4, why don't
you figure out a way to port the entire codebase over, or at least start
porting components yourself?  You will find that it is not an easy task!
Qt4 does not offer critical components that Qt3 did, and hacking around
the missing features *will* slow TDE down on many systems, just as KDE4
slowed down.  (Yes, I have tried!).

I don't want to get into this argument yet again.  If Qt4/Qt5 become
suitable for our use in the future, then we will consider a port.  Until
then, TDE continues to be available for X11 based systems as it always
has.

Tim

---------------------------------------------------------------------
To unsubscribe, e-mail: trinity-devel-unsubscribe@lists.pearsoncomputing.net
For additional commands, e-mail: trinity-devel-help@lists.pearsoncomputing.net
Read list messages on the web archive: http://trinity-devel.pearsoncomputing.net/
Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting