Language Selection

English French German Italian Portuguese Spanish

Why Dolphin should have tabs

Filed under
Linux

According to the Dolphin webpage, Dolphin is: "a file manager for KDE focusing on usability." To expand; from my experiences with it, along with words from developers, Dolphin is a light-weight file-manager, meant to be strictly used for file-browsing. It is not meant to be a replacement for Konqueror. Konqueror, however, in KDE 4 will be the "power user" tool..made for more experienced linux/kde users. It will not be the default file-browser; Dolphin will.

While it all sounds very interesting, and from my experience, Dolphin seems to be progressing steadily, I still have a few concerns. However, my main issue, is the fact that the majority of the developers are against adding tabs.

The proposal for adding tabs, was posted in this thread http://lists.kde.org/?l=kfm-devel&m=118373314623787&w=2 , however it was quickly shot down by many of the developers. For instance, one said: "Ouch, honestly it doesn’t look like a good idea to me. It’ll be yet another setting for a feature you can already have elsewhere. "

Now I ask..is that really the case? Is it really yet another feature you can get elsewhere? Well, yes..Konqueror does indeed have tabs...

..but, should that disqualify tabs from being added? Does the fact that Konqueror has tabs make it so adding them to a filebrowser would be pointless? Would adding tabs to Dolphin make it less or more functional as a filebrowser? You tell me.

Let's look at it another way. Konqueror, as a "power user tool," has many different view options. You can have a tree view..a column view, etc. But..what do you know? So can Dolphin! Why? Because it makes things more convenient for different people. Do you really NEED a multi-column view in Dolphin when Konqueror can already do that? Technically, no..you don't NEED columns in Dolphin to be a standard file browser. You COULD just open new windows. But, like I said, it was added anyway..and for a good reason. Yet, if this useful feature is added, then why aren't tabs?

Essentially, tabs don't HAVE to be added. Nor' does one HAVE to have a MultiColumn view. However, there are some things..despite the fact that you can get them with other programs, that can be added to make things easier for the end user. In my view, tabs can (and do) generally enhance the FILE-BROWSING experience. And besides, isn't that the point of Dolphin; to be a functional and simple FILE-BROWSER? I for one, prefer tabs over multiple windows, and I know many do as well. Multiple windows for me, are annoying, cluttered, and over-all disorganized. Plus, opening a simple tab is much cleaner and more functional than opening a new window; a new window that can soon be lost behind the many other apps you have open (if you're a multi-tasker like myself!).

Overall, I think tabs should be added to Dolphin. While granted, it isn't a HAVE TO feature(neither is multi-column view), it is a feature that can help keep things for FILE-BROWSING neat, organized, and easier for the end-user. Plus, most applications now days have tabs, and most people just automatically look for them. Tabs ARE NOT a power-user feature, infact they've become just one of those "common sense" things; one of those things that have been proven to be very useful.

Personally, I'm not sure why the developers are so hell-bent on keeping tabs away from Dolphin; but I will say this: listen to the every-day kde user. Don't rely completely on philosophies or technical concepts. Don't cloud your mind with what's best for YOU. Instead, listen to the users; put yourself in their shoes. From the responses I've seen on several forums and blogs, I think it’s pretty apparent that most people want tabs. In my eyes, tabs are a standard feature that should be added; not with the purpose of making things more complex or bloated, but to add simplicity — which I thought, was the point of dolphin.

And finally, I'm not saying add every feature under the sun..and add a google bar, and turn Dolphin into Konqueror the second. No. I'm saying use common sense, and make Dolphin (especially since it will be the default file-browser) functional, smart, and easy to use.

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

Dolphin deficiencies

Konqueror is a better file manager than Dolphin; perhaps we should not disdain the Dolphin developers for pushing us toward a better alternative.

On the other hand, a significant part of Konqueror's superiority stems from multiple tabs. To get similar functionality without tabs, it is necessary to create a far less easily managed pile of windows.

Light weight is fine, as long as it doesn't make a mess. Right now, Dolphin is messy. A file manager without tabs is like a file clerk without arms. You can get there eventually, but it takes a lot more trips.

re: Dolphin deficiencies

So does this mean that the KDE 4 developers are no longer using Dolphin "inside" of the Konqueror shell, when you run the command "konqueror --profile filemanagement"? (if you know what I mean.)

Never mind, the question's been answered; they're apparently going to keep Konqueror's file manager the way it is. (Unless some KDE 4 dev changes his/her mind, that is.)

I don't use tabs in the Konqueror file manager. But the point is, Dolphin (at least the version in the last KDE Four Live CD) sucks rocks in comparison to Konqueror. Konqueror isn't that complicated, and I personally don't see Dolphin's reason for existence.

And I'm really starting to get pissed off at the KDE 4 developers who are making all these design decisions because they think they're good for us. Every single time someone criticizes their work, it seems like their first retort is, "Can you write code? No? Then STFU."

Maybe we'll know KDE's really grown up when there's separate groups of people who write code and who design applications and the UI, and the latter's "in charge" of the former. I think that's the real issue here.

(Maybe when all is said and done, I'll be embarrassed at my KDE 4 rants. I hope so.)

I agree completely

I agree completely eco2geek.

I've also ran into that "if you can't code, shut up" attitude. THIS is the attitude that keeps linux from going mainstream..or atleast, it's what holds it back. Not everyone can code, but that doesn't make their opinions/suggestions any less important. Infact, I'd like to think that the every day end-user IS what's truly important.

I also agree about Dolphin as a whole. I really don't see it's reason for existence either. From what I've heard however, is that the konqueror code was so messy and horrible they decided to use dolphin to make things easier. I'm not entirely sure how accurate that is, but I wouldn't doubt it. None-the-less, if Dolphin is going to be the default file-browser, they need to make it reasonably functional, and use-able for everyone (as a file-browser). As stated in my main article, I don't see how tabs are a "power user" function, nor' do I see the reason for NOT including them. Even aside from that, I really think developers need to listen to the ever-day user, and I mean this not about tabs, but in general.

KDE4 Issues

eco2geek--don't know whether you'll be embarrassed at your KDE4 rants. I'm in agreement with your observations.

I know how difficult development can be, and I've struggled to keep silent about my own concerns regarding KDE4 development. I do try to keep up by trying out the various betas and release candidates and reading dot.kde.org and www.planetkde.org. What I've tried and seen and read haven't been encouraging.

It looks like KDE4 will suffer in comparison to KDE3 in features, and perhaps also in post-application-launch performance (read Jos Poortvliet's blog series regarding performance issues in KDE4 here).

Some of the KDE developers have not taken criticism well (of course, not many people in this universe take criticism well, but some handle it outwardly a little better than others). I too have taken offense at snotty "retorts" from some KDE4 developers, whose comments have done nothing to help promote KDE.

Here's hoping that the impending KDE4.0 release is a good enough release to use on a daily basis, and that the KDE4.1 release follows quickly and is the blockbuster release in terms of features and performance it ought to be.

RE: KDE4 Issues

gfranken wrote:
Here's hoping that the impending KDE4.0 release is a good enough release to use on a daily basis, and that the KDE4.1 release follows quickly and is the blockbuster release in terms of features and performance it ought to be.

I'm hoping too. The release date is coming up pretty quick. It's getting there..but still, alot of functionality is definitely missing..atleast judging by the last beta.

More in Tux Machines

today's leftovers

  • [LabPlot] Improved data fitting in 2.5
    Until now, the fit parameters could in principle take any values allowed by the fit model, which would lead to a reasonable description of the data. However, sometimes the realistic regions for the parameters are known in advance and it is desirable to set some mathematical constrains on them. LabPlot provides now the possibility to define lower and/or upper bounds for the fit parameters and to limit the internal fit algorithm to these regions only.
  • [GNOME] Maps Towards 3.28
    Some work has been done since the release of 3.26 in September. On the visual side we have adapted the routing sidebar to use a similar styling as is used in Files (Nautilus) and the GTK+ filechooser.
  • MX 17 Beta 2
  • MiniDebconf in Toulouse
    I attended the MiniDebconf in Toulouse, which was hosted in the larger Capitole du Libre, a free software event with talks, presentation of associations, and a keysigning party. I didn't expect the event to be that big, and I was very impressed by its organization. Cheers to all the volunteers, it has been an amazing week-end!
  • DebConf Videoteam sprint report - day 0
    First day of the videoteam autumn sprint! Well, I say first day, but in reality it's more day 0. Even though most of us have arrived in Cambridge already, we are still missing a few people. Last year we decided to sprint in Paris because most of our video gear is stocked there. This year, we instead chose to sprint a few days before the Cambridge Mini-Debconf to help record the conference afterwards.
  • Libre Computer Board Launches Another Allwinner/Mali ARM SBC
    The Tritium is a new ARM single board computer from the Libre Computer Board project. Earlier this year the first Libre Computer Board launched as the Le Potato for trying to be a libre and free software minded ARM SBC. That board offered better specs than the Raspberry Pi 3 and aimed to be "open" though not fully due to the ARM Mali graphics not being open.
  • FOSDEM 2018 Will Be Hosting A Wayland / Mesa / Mir / X.Org Developer Room
    This year at the FOSDEM open-source/Linux event in Brussels there wasn't the usual "X.Org dev room" as it's long been referred to, but for 2018, Luc Verhaegen is stepping back up to the plate and organizing this mini graphics/X.Org developer event within FOSDEM.
  • The Social Network™ releases its data networking code
    Facebook has sent another shiver running up Cisco's spine, by releasing the code it uses for packet routing. Open/R, its now-open source routing platform, runs Facebook's backbone and data centre networks. The Social Network™ first promised to release the platform in May 2017. In the post that announced the release, Facebook said it began developing Open/R for its Terragraph wireless system, but since applied it to its global fibre network, adding: “we are even starting to roll it out into our data center fabrics, running inside FBOSS and on our Open Compute Project networking hardware like Wedge 100.”
  • Intel Icelake Support Added To LLVM Clang
    Initial support for Intel's Icelake microarchitecture that's a follow-on to Cannonlake has been added to the LLVM/Clang compiler stack. Last week came the Icelake patch to GCC and now Clang has landed its initial Icelake enablement too.
  • Microsoft's Surface Book 2 has a power problem
     

    Microsoft’s Surface Book 2 has a power problem. When operating at peak performance, it may draw more power than its stock charger or Surface Dock can handle. What we’ve discovered after talking to Microsoft is that it’s not a bug—it’s a feature.

Kernel: Linux 4.15 and Intel

  • The Big Changes So Far For The Linux 4.15 Kernel - Half Million New Lines Of Code So Far
    We are now through week one of two for the merge window of the Linux 4.15 kernel. If you are behind on your Phoronix reading with the many feature recaps provided this week of the different pull requests, here's a quick recap of the changes so far to be found with Linux 4.15:
  • Intel 2017Q3 Graphics Stack Recipe Released
    Intel's Open-Source Technology Center has put out their quarterly Linux graphics driver stack upgrade in what they are calling the latest recipe. As is the case with the open-source graphics drivers just being one centralized, universal component to be easily installed everywhere, their graphics stack recipe is just the picked versions of all the source components making up their driver.
  • Intel Ironlake Receives Patches For RC6 Power Savings
    Intel Ironlake "Gen 5" graphics have been around for seven years now since being found in Clarkdale and Arrandale processors while finally now the patches are all worked out for enabling RC6 power-savings support under Linux.

Red Hat: OpenStack and Financial News

Security: Google and Morgan Marquis-Boire

  • Google: 25 per cent of black market passwords can access accounts

    The researchers used Google's proprietary data to see whether or not stolen passwords could be used to gain access to user accounts, and found that an estimated 25 per cent of the stolen credentials can successfully be used by cyber crooks to gain access to functioning Google accounts.

  • Data breaches, phishing, or malware? Understanding the risks of stolen credentials

    Drawing upon Google as a case study, we find 7--25\% of exposed passwords match a victim's Google account.

  • Infosec star accused of sexual assault booted from professional affiliations
    A well-known computer security researcher, Morgan Marquis-Boire, has been publicly accused of sexual assault. On Sunday, The Verge published a report saying that it had spoken with 10 women across North America and Marquis-Boire's home country of New Zealand who say that they were assaulted by him in episodes going back years. A woman that The Verge gave the pseudonym "Lila," provided The Verge with "both a chat log and a PGP signed and encrypted e-mail from Morgan Marquis-Boire. In the e-mail, he apologizes at great length for a terrible but unspecified wrong. And in the chat log, he explicitly confesses to raping and beating her in the hotel room in Toronto, and also confesses to raping multiple women in New Zealand and Australia."