Originally posted by GreatEmerald
View Post
Announcement
Collapse
No announcement yet.
Should Ubuntu Have Gone With KDE Instead Of GNOME?
Collapse
X
-
Originally posted by damonlynch View PostFor example, you can call a command line program;
Originally posted by damonlynch View Postor you can use the GIO API via gobject, which is perfectly usable by Qt programs too. Is the reverse true? Can a non-KDE application use the API you linked too?
Originally posted by damonlynch View PostAs of today there is no interface for a Qt program written in Python to use that API, for example.
Originally posted by damonlynch View PostThis has real implications for the average desktop user. It's particularly frustrating with respect to MTP, because KIO will not give up control of an MTP device as long as the KIO process that accessed the MTP device is still running. For KDE apps it's not a problem, because they all use KIO. For every other app outside that system, they're blocked from accessing the device.
- Likes 1
Comment
-
Originally posted by damonlynch View Post
Let's assume you're correct and kioslave is superior to gvfs/gio. Why, then, does no one outside of KDE use kioslave? Loads of desktops use gvfs/gio, and it works very well for them. It works well for non-Gnome applications and environments because there are easy to use hooks for developers to do things like "unmount" an MTP mount, for example. No such facility is provided by kioslave, and apparently there is zero interest in providing such a facility by the KDE devs. I think that's a mistake, but hey, I'm not a KDE dev so it's up to them what they do with their code.
Kio C++/Qt based thats the issue, only the fuse thing is missing.
Comment
-
Originally posted by TheBlackCat View PostYes, the KDE python bindings are not finished yet. But that is not a fundamental limitation of KIO, and there are lots of languages without gobject bindings. You just cherry-picked language that happens to have gobject bindings but not KF5 ones. Although you can still access the KIO dbus interface through python.
That is an inherent limitation of MTP, only one process can access it at a time. GIO has the same issue. The KIO-mtp developer wanted to create a cross-desktop library to avoid this problem, but I never heard of the GIO devs decided to cooperate or not.
I don't know how anyone could get around the MTP single access limitation because as you know that's a limitation in the MTP library itself. Is the KDE dev proposing rewriting that library, or wrapping the library in another library that cooperatively shares that access? Not that I'm proposing helping, mind you; I'm just curious.
Dolphin is more reticent than Gnome Files in giving up access to an MTP / gphoto2 mount. Last I tested it, you have to end the Dolphin process that once accessed the MTP / gphoto2 device, even if it is no longer displaying the contents of an MTP / gphoto2 device.
Comment
-
KDe PLASMA is the best experience on desktop. I used operating system based on Gnome and I have always replaced it because of wasting time on get the application available. PLASMA is better in productivity. Gnome desktop seems a desktop environment for smartphone. I'll give a chance to the next releases of Fedora.
Comment
Comment