Message: previous - next
Month: April 2012

Re: [trinity-devel] Extensive patching of inadvertent "TQ" conversions

From: Aleksey Midenkov <midenok@...>
Date: Mon, 16 Apr 2012 15:45:28 +0400
On Mon, Apr 16, 2012 at 11:14 AM, Darrell Anderson
<humanreadable@...> wrote:
>> In case of small and not well coordinated manpower the
>> project should think hardly of its priorities. In this project the goal and
>> essential priority is Usability. This is about numerous UI bugs and
>> blunders, subquality work that should be completed. This makes clear
>> direction. Not mere wandering in woods of code. That will put project
>> in wrong direction.
>> Timothy, please, remove TQ -> Q proxying. This direction
>> is not good and sooner or later will be reverted. Better sooner, less
>> double work.
> I admit I have my frustrations with the TQ layer. We have yet to see any direct benefit that I am aware.

There is no real benefits. I believe that any benefits may be done
without TQ layer.

> But I don't have the energy or knowledge to do anything about that. I want to believe there is a long term benefit and I'm willing to let the issue go at that. For now.
> The issue could be water under the bridge if we addressed the bug tracker. When usability is restored to at least 3.5.10 days then I believe users will ignore the TQ debate. (Developers might not but users will.)
> With all of the "Inadvertent TQ" patches I pushed we now can say that inadvertent TQ conversions are unlikely to be the cause of a bug. Although, as David and I discovered this weekend, merely restoring the inadvertent changes can still leave a hidden bug --- something that was patched to overcome the original inadvertent changes.
> Some of the usability bugs that are irritating people:
> ...

I can add a lot of usability bugs from my list. The most irritable
(though not a bug) is that cannot upgrade python to latest version due
to kde-guidance package limitation. This holds a lot of software from
being installed/upgraded or requires efforts for keeping several
snapshots of system. The important bugs that are on my mind:

kpowersave segfaults (no battery indicator);
gwenview segfaults;
rudimental kbluetooth (no real world functionality);
network-manager-kde frontend does not support latest network-manager API

There are lots of bugs and minor flaws that I keep recorded and intend
to fix like:

stupid message dialog popups in iteration loops;
wrong Shift selection in Konqueror, etc.;
a lot of kmail bugs including hangs, UI freezes, network and protocol
kpowersave incompatibility with TuxOnIce;
kdevelop UI incompleteness, etc.;
incomplete handling of keyboard/mouse settings which are not restored
on eject/insert;
and many, many more!

> We can fix these bugs, which would put the TQ issue behind us.

The problem is that this TQ issue caused (and will cause in future) a
lot of trouble. It is a blocker along with rushed build system
development that hold me from development. The year that have spent on
that could be much more productive. This makes me even doubt in
project future because users go away when they see no improvements in
such a long time. And python conflict is the one of good reasons for