Version: (using Devel) Installed from: Compiled sources Different default settings are needed for konqueror. The current defaults distributed with konqueror are unworkable and need to be improved to differentiate konqueror from dolphin. The defaults are overly conservative and take 10 minutes to sort out on each install. The following would be a big improvement: Navigation: Open archives as folder Open folders during drag operations General: Behavior: Rename inline Previews: Cursor Files Electronic Business Cards Font Files HTML Files Postscript, PDF and DVI Files SVG (why doesn't this have "Files" in the title) Text Files Context Menu: Show 'Delete' Command Show 'Copy To' and 'Move To' Commands Configure File Associations: ** are just a bloody mess Web Browsing: Ask for name and folder when adding Bookmarks Apperance: Fonts: Why Bitstream Vera Sans for everything?? I know these are not "Big" issues, but they make konqueror act like konqueror instead of Dolphin. Further it is simply a pain to have to set konqueror preferences to make konqueror behave like konqueror on every single install. Consider these, discuss it, and reach a reasoned decision about the defaults. Currently it looks like one individual assiged to the dolphin team, who had never used konqueror, was given the task coding the defaults, and then he set them to match dolphin.
Thanks for the report. I'll change the severity to "Wishlist" because this is not a bug. However, I'm afraid this might be impossible to implement. The problem is that Konqueror and Dolphin share the same code for the file management settings and also the settings file in the user's home directory (dolphinrc), so it's impossible to have different default settings for both :-(
(In reply to comment #1) > Thanks for the report. I'll change the severity to "Wishlist" because this is > not a bug. > The "not a bug" syndrome again? The question of which defaults are best is a usability issue and usability issues are bugs. Unless we have a separate category for them (which I would support). > However, I'm afraid this might be impossible to implement. The problem is that > Konqueror and Dolphin share the same code for the file management settings and > also the settings file in the user's home directory (dolphinrc), so it's > impossible to have different default settings for both :-( Are you saying that there is no way for the DolphinPart to determine if it is running in Dolphin or Konqueror? And, this is a feature request, to have separate RC files for the Dolphin part dependint of what application it is running in. Perhaps this is really 2 issues and should be split.
(In reply to comment #2) > The "not a bug" syndrome again? The question of which defaults are best is a > usability issue and usability issues are bugs. Unless we have a separate > category for them (which I would support). IMHO, default settings which are considered fine for one file manager (Dolphin) cannot suddenly become so useless that they are a "usability issue" if they are used in another file manager (Konqueror), especially because Konqueror is, as I understand it, mostly used by "power users" who will want to customize the settings to their personal needs anyway (and if they do it once, they can just copy their dolphinrc file to any other computer). > Are you saying that there is no way for the DolphinPart to determine if it is > running in Dolphin or Konqueror? And, this is a feature request, to have > separate RC files for the Dolphin part dependint of what application it is > running in. Having separate *rc files (or different default settings, that doesn't make a big difference) would also mean to have separate *.kcfg files in the source and in turn separate settings code for both applications. Additionally, this would require to add hacks all over the place in the file management code that choose the right settings code, depending on the application it's running in. All this would add *a lot* of complexity to the code and make it *much* harder to maintain. And as I said above, I think most Konqueror users change the settings manually according to their personal needs anyway, and they will probably not want different settings if they use Dolphin once in a while, so I don't think the benefits would be big enough to justify this. But that's just my personal opinion, and I'm not a core Konqueror developer.
I see that I wasn't clear (my bad) I was using 'issue' as others do as a generic term that includes 'bug' and 'feature request'. Perhaps 'usability question' would have been a better choice of words. American English is very sloppy and I should be more careful. That sounds complicated. But if the DolphinPart is a class, couldn't you just use dummy classes that do nothing but set on enumeration variable and them go to the DolphinPart class? This would work with subroutines. OTOH, I thought of something else. When you save a "View Profile" should this also save the configuration for the DolphinPart?