Original von Logge
Something I've been thinking of the past few days is that if Konqueror really needs to be both a web-browser and a filemanager at the same time. I think that a user that is new to GNU/n*x and KDE might be confused by the functions of Konqueror. Is it a webbrowser or is it a filemanager.
To me konqueror is much more than just a tool for browsing the web and a manager for local files. It's also an ftp client, webdav client, fish client, cvs frontend, ... (with the respective views and extensions)
The fact that it works with files on the local file system and files on a remote host is just a detail to the user due to the great network transparency of KDE. Konqueror makes them available to me independent of the way they are accessed. This abstraction leads to a great consistency. I can drag files from a webdav account and drop them to another box I have an ssh login on (using the fish protocol). Or from an ftp server to the local file system. I find this very user-friendly because I don't have to make myself familiar with 20 different applications that are all somewhat inconsistent and don't support half of the protocols I would like to use anyway...
Actually I like it the way it is... For the way I work it's necessary that konqueror understands all these protocols. I would not like a dumbed-down version of it.
One thing has been discussed on the mailing lists, though. There have been suggestions to make the profiles for web browsing and file management more distinct: The home URL should be defined per profile so that konqi would go the default page in web browsing mode and to the user's home directory when in file management mode. The toolbars and context menus should be adapted to the current mode, too...
But what exactly would be the things that would improve for the user if konqi was split up (other than being allegedly less confusing which would not justify - for me - the cost)? What do you see as missing in either "personality" of konqueror because the split has not been done?