https://bugs.kde.org/show_bug.cgi?id=385520
--- Comment #9 from Dominik Haumann <dhaum...@kde.org> --- @Nate: I will give some background here. Traditionally, Kate did not have tabs for over 15 years. The reason was always that tabs do not scale: It is not uncommon that users have many many files open (say >50), navigating between files then will simply not work anymore. Therefore, Kate always only had the so called "Documents" list as sidebar, which displays all opened files in a list view or tree view. Over time, some developers (including me) added some tab bar plugins, which could be enabled. There was a simple tab bar that more looked like an embedded toolbar. Then there was the multiline tab bar (by me), and I think even more. You can read about some of them here: https://kate-editor.org/2011/04/25/kates-tab-bar-plugins/ For Kate 5, we decided to follow the users' request and added a tabbar by default. However, we decided that this tabbar should be tightly integrated with the quick open feature (CTRL+ALT+O). The idea was to show as many tabs as possible, and tell the user how many documents do not fit anymore into the tabbar. These documents can then be quickly accessed via CTRL+ALT+O. Many users seem to like how this works right now. Maybe many also don't. Fact is: You will always find some who don't and have a loud voice. In this case: I can see that the tabbar is different, because it has absolutely nothing to do with a tabbar of e.g. console, dolphin, ... It works different by design. Now of course it may very well be that we completely borked things, and we simply did a bad job (which is most likely the case). But let me put it like this: Changing this to simple tabs like Dolphin won't cut it. Before changing this, this needs to be very well designed in the workflow. Compare with Visual Studio, compare with all the other text editors out there. Compare with extensions for Visual Studio. You will find 10+ different implementations, all having their strength and weaknesses. If our only weakness right now is the visual appearance and possibly a slightly different behavior, then maybe it's not the worst solution. PS: I currently do not have plans to change the current implementation. But of course, patches are welcome. -- You are receiving this mail because: You are watching all bug changes.
