I get hundreds of millions of dollars every year by legitimising surveillance capitalists and enabling them to violate your privacy by default. (I wouldn’t exist without them.) Please trust me on privacy.
Why are you all looking at me like that?
OK, OK, you can stop glaring: I’m Mozilla, y’all love me. 💕
@aral So if you don't like Mozilla or Google, that leaves the one major browser engine you'd approve of being Apple's WebKit? I hope you can see why I say we need a Small Tech browser engine?
@fitheach @alcinnz @aral 'Moving and viewing files' over multiple protocols IS doing one thing well.
Confining that use to a single protocol means needing Multiple apps; as many as one for each protocol.
Dolphin does exactly this, so you win there (no web).
I enjoyed having the other protocols there as well though. Sometimes, i still do.
It's a while since I looked at Dolphin, but ti struck me as a mighty fine file manager.
The file manager/browser mash-up: didn't it start way-back when browsers were viewing the Desktop as if it was a webpage? I certainly remember the GNOME browser doing that (Galeon?). MS Windows did that for a while, too. Horrible idea.
Gosh, it isn't that long ago that file managers added features to allow use of WebDav, FTP and SSH/SCP etc. Libraries like KIO or filesystems like FUSE or GVFS were only added ten years ago, maybe slightly more.
Viewing file contents using FMs has probably been around a bit longer, usually by calling other applications. What seems weird to me is having a FM that is also a web browser (or is it a web browser that is also a FM?).
Finding the perfect file manager is like searching for the Holy Grail; the quest is eternal, and never fulfilled.
I have tried emelfm(2), and also Gnome Commander, Tux Commander, Nautilius, ROX, and many others. All of them have nice features, but I'm always looking for more. For years now my mainstay FMs have been Thunar and MC. Pretty happy with those two, although I would like a graphical two-pane FM (I know Dolphin, but KDE...).
@fitheach "The packaged versions of KDE apps"
What does this mean, sorry? I've never run into a situation when I can't mix and match any programs written with any old graphical tool kit.
When you install, e.g. konqueror or most any apps, under distros like Fedora, Debian, Ubuntu etc. you install a package where the developers have already made decisions for you regarding settings and dependencies. Alternatively, you could install the app from source(s) and perhaps avoid some un-needed dependencies.
@fitheach Can you give me an example please? I'm still not understanding. Everything is entirely changeable in prefs wrt what happens to each filetype, which is quite extensive.
I swear i'm not being deliberately obtuse Iain - just never ran into this problem you've experience with settings.
Depends, yes, of course. Any program using external libs has depends.
The dependencies are quite often flags which you set when you compile an app. When you install a package it has been compiled already, with decisions about those flags made by the package developer.
@fitheach I'm familiar with these things, yes.
Just looking for an example of where this limited people to only being able to use other kde applications with something.
It's very early here and perhaps I'm missing the obvious.
Have a look through the KDE documentation. This page (although talking about extragear) explains the high level organisation:
This page gives the flags when building from source:
Adding or omitting some of these modules could dramatically change the nature of individual KDE apps.
@fitheach Defaults are a very common thing and occur in many programs, but not all I suppose.
I was after a concrete example of where I could encounter a kde app I couldn't change the default for.
Let's drop it; I'm clearly failing to understand the problem, much less suggest a correction or fix for you.
When you compile an application the flags determine which features are enabled and which ones aren't.
If you install the same application using a package provided by your distro, the package developers have made those decisions for you.
A self compiled application can therefore have more or fewer features than a distro package. A typical reason for compiling yourself is to add experimental features the distro developers avoid for the sake of stability.
The docs I linked to gave an example of omitting the module kremotecontrol if your hardware doesn't support that feature. However, many of the KDE modules are mandatory as the DE is tightly integrated.
The social network of the future: No ads, no corporate surveillance, ethical design, and decentralization! Own your data with Mastodon!