https://bugs.kde.org/show_bug.cgi?id=291102
--- Comment #4 from Henrik Fehlauer <rk...@lab12.net> --- I think they are helpful on the bottom (in a "usability heuristics" sense, no a "I've done an eyetracking study" sense). Perhaps there's an official/better reason, but at least for Dolphin's case just going by my gut feeling it would seem pretty weird to have a (visually nearly unified) tab strip on top, where some of the leftmost tabs would switch toolviews and the tabs on the right suddenly were for folders. The separation helps in making sure the user intuitively knows both are different. For Gwenview, I could see changing the tabs to at least being draggable/undockable like in Dolphin. Then it would be up to Qt or the widget style to provide a way to get tabs to the top, and the user could just split the toolviews so there would be no tabs at all. Another reason I could think of is that of spreading horizontal bars around a bit instead of having them all in one place. In general dense groups of buttons (tabs in our case) are easier to use if they are aligned to something as well as having a large "landing area". For example, imagine a UI with the menubar and then several rows of toolbars below (think an older version or MS Word). Those are hard on the eyes and difficult to navigate, adding tabs below would make this even worse. By using all 4 edges of of the window this problem is alleviated. In some rare cases this conflicts with external UI (here: the taskbar), but those are minor compared to the general case. -- You are receiving this mail because: You are watching all bug changes.
