------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
         
http://bugs.kde.org/show_bug.cgi?id=140810         
           Summary: accessibility: editor status row (row/col/insert status)
                    hurts neighbours-belong-together rule
           Product: kdevelop
           Version: 3.3.5
          Platform: unspecified
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: NOR
         Component: general
        AssignedTo: kdevelop-bugs kdevelop org
        ReportedBy: Wolfram.R.Sieber GMail com


Version:           3.3.5 (using KDE 3.5.5, Debian Package 4:3.5.5a.dfsg.1-5 (4.0))
Compiler:          Target: i486-linux-gnu
OS:                Linux (i686) release 2.6.18-3-k7

Human machine interfaces usually use the neighbours-belong-together principle. (Sorry, I forgot the exact English name for that.) Means, things located nearby each other get considered as being parts of the same entity.

Editors such as kate feature a status bar next below the editor frame, to the far left of the frame. There, a user would expect it; having the status located there, is familiar.

Contrary to that, in kdevelop the status data appears in the far right bottom corner. Multiple inches away from the left bottom of the editor frame. -- At least, if a Konsole and a right sidebar are opened.

There, I found the status data only by random chance. It's far from the location one would expect it.

.
I see, that the tab-like appearance would break up if the status were moved to the bottom left corner of the editor frame, but where it currently resides doesn't look like a good place for me.

As an alternative approach: What about a floating (e.g. black on dark grey) status row *inside* the editor frame? ... Or just ignore the then-broken tab-like look, and put the status bar just where it would be expected -- to the bottom left of the editor frame?