The K Desktop Environment was pleased to see its users recently at the LinuxWorld Conference and Expo. Users were excited to learn about KDE 4.0, some of the hot new stuff in KDE 3.5, and thousands of Linux users got out of the house for a change.
To view parent comment, click here.
To read all comments associated with this story, please click here.
Member since:
Member since:2005-07-06
I don't care much about Gnome, I was talking about KDE.
It just seems there are too many different things being squeezed into the IOSlave concept, e.g.:
- protocols: file, http, ftp, fish
- things that should be filters: zip, tar, gzip
- disk access: media, drives, audiocd
- pseudo filesystems: system, settings, applications, homes
Member since:2005-07-06
Here's one example. Say Joe User looks at his home directory in Konqueror:
homes:/Joe_User
Yet if he clicks on a zip file in there the address turns into something like this:
zip:/home/joe/file.zip
Is that confusing or what?
It is, but the current KDE 3.4 situation is worse. People usually refer to each other by name and have done so for thousands of years. They should be able to do so in their OS environment as well.
Besides I think that most people will see the zip archive as an artefact of its own, just like they realize that trash:/ or for that matter homes:/ is a hierachies of their own. If he doesn't, he is in trouble just the same as the zip:/ "directory" will behave differently than his ordinay directories and that will confuse him too. The solution to that would be not to open zip files directly in konqueror, but I
think most people would think that would be a bad idea.
BTW: When the user decide to unpack it he would still be able to specify the desired location in termes of homes:/Some Person.
Member since:
2005-07-06
There's a proliferation of IOSlaves going on at the moment, like media:, homes:, system:, settings:, ... .
I get the feeling that that might come back to bite them, because it isn't terribly scalable and it conflicts with the actual concept of URLs: the bit before the colon should denote a protocol, not just some kind of filesystem shortcut.
Here's one example. Say Joe User looks at his home directory in Konqueror:
homes:/Joe_User
Yet if he clicks on a zip file in there the address turns into something like this:
zip:/home/joe/file.zip
Is that confusing or what?