This page has become very long and very detailed - somewhat out-of-scale with most other pages. I wonder if it would be sensible to move a lot of this content to a tutorial on 'Getting the most out of Dolphin' or some such? The Tutorials page seems to be often viewed, and I think it would actually be found more often there than in a general overview page.
I'd help with this, if we go ahead, but it will impact on the language pages, I think, so we need some agreement first. --annew 10:29, 2 October 2008 (UTC)
To bring this into line with other applications I've written and introduction, then moved the whole of the original content to Tutorials (linked, of course). --annew 12:33, 9 November 2008 (UTC)
--Claus chr 2 August 2009
There's a problem - Amarok also has a very, very long wiki page. Should these long pages be acceptable, or should Amarok's page be changed as Dolphin's has? The madman 18:32, 13 September 2009 (UTC)
Is it really appropriate to make the description a bullet-point list of features? With Konqueror, Konsole and other applications (such as Okular and Amarok) using primarily descriptive paragraphs for their description (or whatever they have in place of the description), should Dolphin's be changed to better suite the general feel of the wiki? The madman 12:19, 13 September 2009 (UTC)
Recently, the translation markup in this page has been changed. Among other thing, the second bulleted list was spilt into two translation units. This has resulted in the list being displayed wrongly on the page: the last line of the first unit and the first line of the second unit is run into one line! The reason for this seems to be that there is no blank line between the two units.
Why split one relatively short list into two translation units, and can it be done without unfortunate side effect in the displayed page? --Claus chr 09:02, 28 June 2010 (CEST)
|Thread title||Replies||Last modified|
|GitHub links here/needs developer info||1||07:47, 30 September 2018|
|the use of dedicated||2||05:26, 23 June 2011|
|Troubleshooting section||1||08:11, 28 September 2010|
The first result from Googling "dolphin KDE source code" is https://github.com/KDE/dolphin , which has a one-line README
which redirects here. The code and commit history are indeed mirrored on GitHub. But developers wondering about changes ("pull requests" on GitHub), issues, project status, etc. will either realize the info is not on GitHub and give up, or follow the link here... and find no information for developers and give up. I had similar problems looking for other KDE projects.
Either that barebones GitHub README should be expanded to point developers to relevant resources (https://www.kde.org/applications/system/dolphin/development , Phabricator, bugs.kde.org ?), or this page needs to have something for developers.
I was just wondering why the word "dedicated" is used. And somehow I don't think that it makes much sense. It's just like saying Rekonq is a dedicated web browser...
Historical. At the point that that was written most people were still migrating to KDE4, and were used to Konqueror being part file-manager and part web-browser. I'd be inclined to leave it, as there are still people in this position, and at some point the Enterprise distros will presumably change to KDE4 so bringing a new generation of people used to a hybrid.
Hi, This page: http://userbase.kde.org/Troubleshooting suggests that application specific troubleshooting should go on the application page. I had this problem already twice so I though it might be useful for others. I'm new to this wiki - would it make sense to have a specific Troubleshooting section?
Problem: Dolphin's menu entries 'View - Additional' and/or 'View - Panels' are empty although nepomuk is enabled in System Settings.
Solution: Rename the folder '~/.kde4/share/apps/dolphin' and restart dolphin. This will purge your dolphin customizations but the entries should be back. This happened to me after an upgrade from KDE 4.4 to 4.5