On 20 Dec 2011, Timothy Pearson spake thusly:

>>> > For you folks more experienced with coding TDE and
>>> Qt3, are there any
>>> > clever ways to eliminate the overhead with the non X
>>> commands? Seems
>>> > that would be more efficient and shave a few
>>> micro/millisecond
>>> > response times here and there, especially for older
>>> hardware. :)
>>>
>>> I doubt it.  Porting from Qt3 to Qt4 is non-trivial,
>>> but the amount of work depends on the program.  There's
>>> no way to eliminate X as long as Qt3 is used.
>>
>> I was not implying any porting to Qt4. :) Is there a decent technical
>> reason why the X overhead can't be eliminated from the non X TDE commands?
>
> In theory it might be possible to modify the Qt3 source and add an X-less
> application constructor.  I have no idea how complex that would be.

Of course this would still pull in the X shared libraries, incurring
most of the startup costs nonetheless. Fixing *that* would be a lot more
work. (Also, who knows how many places inside Qt3 assume the existence
of a live X display connection? After all, they've always had one they
can rely on.)

-- 
NULL && (void)