2008-2010 restructuring discussion

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)

It doesn't necessarily have to be a tutorial. Actually it isn't a tutorial, tip or howto but more of a handbook. My suggestion would be to split up the current Dolphin page into more manageable chunks, something like Dolphin, Dolphin/Panels, Dolphin/Views, etc. (since each section is quite long and detailed).
As for language pages, we could just move them as well. But yes, we should wait for some agreement. Within two days perhaps? --Jucato
Splitting of a bigger page into many small ones would work, but it is against the wiki idea, or? Could not find the link I want to give. If you split a big page in many small ones it sometimes ends in having stubs. Also it is easier to search in one page instead of getting 10 pages as a search result and grep them for desired content. Just my 2 cents. --Mark Ziegler 12:53, 2 October 2008 (UTC)
Splitting into smaller chunks of information was just one idea. Of course we could just keep it all in one page, but definitely needs a proper table of contents. I was just thinking about the situation where the page gets too long and too overwhelming. Presenting it in more manageable chunks would be better, like what most KDE Handbooks do.
Whichever way is chosen, the important thing is that the "front page" for each app (http://userbase.kde.org/AppName) would be a simple, digested summary of the app with all the necessary info and links that a user can read at a glance: icon, screenshot, description, website, links to further info/tutorials/tips, maybe even a developer. --Jucato
It would be really cool if we could use expanding sections - simple page, with sections expanding on demand. I wonder if that is possible? --annew 16:13, 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)

This change created problems for the translated pages: The language template for the tutorial page still links translated pages to this page. As a consequence, only one of these pages can be translated, and that translation is shown both as introductory page and as tutorial.
Currently there are danish and russian translations of the introduction and german, frensh and polish translations of the tutorial. I have corrected the language template on the tutorial page and copied the contents of of the german, frensh and polish pages there. I haven't deleted these translations from this page, so now there are two identical copies of them. Maby someone could look into this?

--Claus chr 2 August 2009

Sorry I overlooked that. I need to do some more moves on the Tutorials pages, to make the links more consistent. I'll try to get this done today. Perhaps you could either ping me on IRC or exchange emails with me (annew at kde dot org), so that we can ensure that everything is brought into line. Thanks.--annew 09:37, 2 August 2009 (UTC)

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)

The Amarok page was written by the Amarok team. My feeling is that changes should only be made to it after consultation with the team. --annew 12:42, 13 September 2009 (UTC)

Description: A bullet-pointed list

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)

Again this is due to conflicts in the styles preferred by contributors. Consultation with previous authors should precede any major changes. They can usually be contacted by looking at the History of the page to get an author name, the writing a message on Talk:Username. They will be alerted to read the message. --annew 12:42, 13 September 2009 (UTC)
OK, thank you. I will go about asking the original author about this change.
This looks like the revision that changed from paragraphs to a bullet-list and, consequently, removed a lot of information about dolphin. Was this part of the change discussed above?

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 titleRepliesLast modified
GitHub links here/needs developer info223:34, 20 June 2019
yurchor keeps vandalizing the wiki with impunity106:11, 5 December 2018
the use of dedicated205:26, 23 June 2011
Troubleshooting section108:11, 28 September 2010

GitHub links here/needs developer info

The first result from Googling "dolphin KDE source code" is https://github.com/KDE/dolphin , which has a one-line README

See http://dolphin.kde.org for information about Dolphin.

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.

07:56, 29 September 2018

This is a question for the Dolphin developers. There is a Dolphin page on community.kde.org; maybe the link should go there? We could have a similar link here, but more extensive developer info really doesn't belong here.

07:47, 30 September 2018

Thanks, I filed KDE bug 408967 against Dolphin. It is quite a confusing maze! https://dolphin.kde.org is "the" website for Dolphin in applicaiton info, so it's not just for developers; if "community" is the right place then this page could have have a

https://community.kde.org/Dolphin has information for developers


23:34, 20 June 2019

yurchor keeps vandalizing the wiki with impunity

You do not have permission to edit this page, for the following reason:

The action you have requested is limited to users in one of the groups: Users, Administrators, trusted, KDEDevelopers.

You can view and copy the source of this page.


Return to Thread:Talk:Dolphin/yurchor keeps vandalizing the wiki with impunity.

See my entry on your user page.

06:11, 5 December 2018

the use of dedicated

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...

Zhao Han10:01, 7 April 2011

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.

annew10:44, 7 April 2011
Edited by 2 users.
Last edit: 05:26, 23 June 2011

alright, i see.

Zhao Han18:32, 9 April 2011

Troubleshooting section

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

Dinsdale22:05, 27 September 2010

Hi Dinsdale. Yes, when something is likely to be experienced by others it's good to share your knowledge. Please add a Hints and Tips section underneath the Tutorials section, and put your entry there. Thanks

annew08:11, 28 September 2010

This page was last edited on 28 September 2018, at 22:05. Content is available under Creative Commons License SA 4.0 unless otherwise noted.