In the transition from KDE 3 to KDE 4 a new file manager, dolphin, was often discussed and now officially moved to the base part of KDE.
I just stumbled over this message saying that the file manager Dolphin is now part of kdebase (of KDE 4):
Moving Dolphin to kdebase, as discussed with Peter and others.
The big plan is: dolphin will become the default file manager (kicker buttons and file:/ links bring it up); or a more file-manager-oriented GUI than in kde3. File management in konqueror will remain available, e.g. for people who like to have profiles where it’s combined with other things. For code sharing even more, we are considering making a dolphinpart and using that as konqueror’s directory view.
The question remains what now happens with konqueror – keep in mind that one of the goals of KDE 4 was to only keep one app for each task inside the base packages. But with dolphin as the potentially new file manager and Webkit as the new potentially browser we may see alternatives to konqueror
vanish. More or less at least since quite some code in Webkit and Dolphin is related to konqueror (respectively parts of it).
For me it looks like Dolphin can do all I expect from a file manager (most important maybe the split view you do not have in the Windows explorer, for example). Also the interface seems to be pretty slick and smooth after all I know from Dolphin 0.8.1 (which is included in Fedora). It has some interesting improvements over the current konqueror and is worth a look.
I’m really looking forward to the improvements Dolphin will get in KDE 4 – I hope that the Oxygen guys will go over the interface to provide a cool default theme and that some small bits missing will be added as well. Nevertheless, if we get the Webkit/Dolphin couple it will take some time to get used to a new working style… but it could be worth it!
About the WebKit-might-replace-konqueror thing: superstoned is right in the comment section that WebKit is a rendering engine in the first place. I had the Unity attempts and screenshots in my mind when I was writing this article. But when you exchange khtml by WebKit in konqueror using kparts you might even not feel it.
Aseigo commented (thanks for that) that konqueror will not vanish, but will become a default option in some cases – a configurable default option of course. Read more about in this blog post of aseigo. So don’t start whining or blaming that konqueror might disappear, its just not true. As for this post, I changed the bit which can be misunderstood. And, as always: keep in mind that I am a huge KDE fan – but not an involved developer.