Dolphin/en: Difference between revisions
(Updating to match new version of source page) |
(Updating to match new version of source page) |
||
| Line 36: | Line 36: | ||
== Philosophy == | == Philosophy == | ||
Dolphin is a file manager focusing on usability. When reading the term ''Usability'' people often assume that the focus is on newbies and only basic features are offered. This assumption is wrong. | '''Dolphin''' is a file manager focusing on usability. When reading the term ''Usability'' people often assume that the focus is on newbies and only basic features are offered. This assumption is wrong. | ||
=== Target User Group === | === Target User Group === | ||
Focusing on usability means that features are discoverable and efficient to use. The feature set is defined indirectly by the target user group of Dolphin: | Focusing on usability means that features are discoverable and efficient to use. The feature set is defined indirectly by the target user group of '''Dolphin''': | ||
* '''Lisa''': Lisa is familiar with computers since 10 years. Due to her job she has experience with Word, Excel and Outlook. At home she mainly uses the computer for browsing the web and writing e-mails. She requires a file manager for managing photos from the camera, documents she gets per e-mail or PDF-documents she downloads with a browser. Lisa knows concepts like folders and a file hierarchy, but she is not familiar with the file hierarchy of Linux. | * '''Lisa''': Lisa is familiar with computers since 10 years. Due to her job she has experience with Word, Excel and Outlook. At home she mainly uses the computer for browsing the web and writing e-mails. She requires a file manager for managing photos from the camera, documents she gets per e-mail or PDF-documents she downloads with a browser. Lisa knows concepts like folders and a file hierarchy, but she is not familiar with the file hierarchy of Linux. | ||
| Line 46: | Line 46: | ||
* '''Simon''': Simon has been a developer at a software company for 8 years. At home he uses a file manager to maintain his large collection of photos and music. Additionally he owns a small homepage and needs to transfer updated files on the FTP server. Moving and copying files are regular tasks in Simon's workflow. | * '''Simon''': Simon has been a developer at a software company for 8 years. At home he uses a file manager to maintain his large collection of photos and music. Additionally he owns a small homepage and needs to transfer updated files on the FTP server. Moving and copying files are regular tasks in Simon's workflow. | ||
Not part of the target user group of Dolphin are Fred and Jeff: | Not part of the target user group of '''Dolphin''' are Fred and Jeff: | ||
* '''Fred''': Fred is 75 years old and is able to write e-mails and browsing the web. He is not familiar with file hierarchies and stores all his documents on the desktop. | * '''Fred''': Fred is 75 years old and is able to write e-mails and browsing the web. He is not familiar with file hierarchies and stores all his documents on the desktop. | ||
| Line 52: | Line 52: | ||
* '''Jeff''': Jeff is Linux-freak since the age of 16 a few years ago. He is developer and in his spare time he acts as administrator for a small company. Jeff has two monitors to keep the overview about his huge number of opened applications. | * '''Jeff''': Jeff is Linux-freak since the age of 16 a few years ago. He is developer and in his spare time he acts as administrator for a small company. Jeff has two monitors to keep the overview about his huge number of opened applications. | ||
This does not mean that Fred or Jeff cannot work with Dolphin. But there might be features and concepts of Dolphin that overburden Fred. Also Jeff might miss some features which are a must-have for his daily work. | This does not mean that Fred or Jeff cannot work with '''Dolphin'''. But there might be features and concepts of '''Dolphin''' that overburden Fred. Also Jeff might miss some features which are a must-have for his daily work. | ||
===Non-Intrusive Features=== | ===Non-Intrusive Features=== | ||
Before a feature is added in Dolphin, it is checked whether the feature is mandatory for the target user group. If this is not the case, then this does not mean that the feature cannot be added; first it must be clarified whether the feature might be non-intrusive, so that it adds value for users outside the primary target user group of Dolphin. ''Non-intrusive'' is mainly related to the user interface. A feature that adds a lot of clutter to the main menu, context menus or toolbar might harm the target user group. In this case the feature will not be added. | Before a feature is added in '''Dolphin''', it is checked whether the feature is mandatory for the target user group. If this is not the case, then this does not mean that the feature cannot be added; first it must be clarified whether the feature might be non-intrusive, so that it adds value for users outside the primary target user group of '''Dolphin'''. ''Non-intrusive'' is mainly related to the user interface. A feature that adds a lot of clutter to the main menu, context menus or toolbar might harm the target user group. In this case the feature will not be added. | ||
A good example of a feature that is non-intrusive is the embedded terminal in Dolphin. It only requires one entry inside a sub menu, but adds great value for Jeff, who is not part of the target user group. | A good example of a feature that is non-intrusive is the embedded terminal in '''Dolphin'''. It only requires one entry inside a sub menu, but adds great value for Jeff, who is not part of the target user group. | ||
===Options=== | ===Options=== | ||
Options are mandatory as the user "average Joe" does not exist. Still it is not the goal of Dolphin offering options for all kind of things. Again the focus is on the possible needs of the target user group. Each additional option makes it harder finding other options, so the same rules for features are applied to options too. | Options are mandatory as the user "average Joe" does not exist. Still it is not the goal of '''Dolphin''' offering options for all kind of things. Again the focus is on the possible needs of the target user group. Each additional option makes it harder finding other options, so the same rules for features are applied to options too. | ||
== Hints, Tips and Troubleshooting == | == Hints, Tips and Troubleshooting == | ||
Revision as of 09:00, 14 October 2014
 |
The dedicated file manager focusing on usability |
Feature Overview
At first look, this is a simple file manager, but it has many talents. Some features include:
- Split windows - view and use two directories at the same time
- Viewing attributes can be set (and remembered) independently for each window
- Tabbed browsing
- Use the optional informational panel on the right
- Or elect to have essential attribute information displayed in the window
- Use 'breadcrumb' navigation for speed
- One-click change to editable navigation bar
- Add Folders panel for traditional navigation
- Add a terminal in the directory you are currently browsing
- Many functions controlled by keyboard shortcuts
Tutorials
Philosophy
Dolphin is a file manager focusing on usability. When reading the term Usability people often assume that the focus is on newbies and only basic features are offered. This assumption is wrong.
Target User Group
Focusing on usability means that features are discoverable and efficient to use. The feature set is defined indirectly by the target user group of Dolphin:
- Lisa: Lisa is familiar with computers since 10 years. Due to her job she has experience with Word, Excel and Outlook. At home she mainly uses the computer for browsing the web and writing e-mails. She requires a file manager for managing photos from the camera, documents she gets per e-mail or PDF-documents she downloads with a browser. Lisa knows concepts like folders and a file hierarchy, but she is not familiar with the file hierarchy of Linux.
- Simon: Simon has been a developer at a software company for 8 years. At home he uses a file manager to maintain his large collection of photos and music. Additionally he owns a small homepage and needs to transfer updated files on the FTP server. Moving and copying files are regular tasks in Simon's workflow.
Not part of the target user group of Dolphin are Fred and Jeff:
- Fred: Fred is 75 years old and is able to write e-mails and browsing the web. He is not familiar with file hierarchies and stores all his documents on the desktop.
- Jeff: Jeff is Linux-freak since the age of 16 a few years ago. He is developer and in his spare time he acts as administrator for a small company. Jeff has two monitors to keep the overview about his huge number of opened applications.
This does not mean that Fred or Jeff cannot work with Dolphin. But there might be features and concepts of Dolphin that overburden Fred. Also Jeff might miss some features which are a must-have for his daily work.
Non-Intrusive Features
Before a feature is added in Dolphin, it is checked whether the feature is mandatory for the target user group. If this is not the case, then this does not mean that the feature cannot be added; first it must be clarified whether the feature might be non-intrusive, so that it adds value for users outside the primary target user group of Dolphin. Non-intrusive is mainly related to the user interface. A feature that adds a lot of clutter to the main menu, context menus or toolbar might harm the target user group. In this case the feature will not be added.
A good example of a feature that is non-intrusive is the embedded terminal in Dolphin. It only requires one entry inside a sub menu, but adds great value for Jeff, who is not part of the target user group.
Options
Options are mandatory as the user "average Joe" does not exist. Still it is not the goal of Dolphin offering options for all kind of things. Again the focus is on the possible needs of the target user group. Each additional option makes it harder finding other options, so the same rules for features are applied to options too.
Hints, Tips and Troubleshooting
Problem: Dolphin's menu entries and/or don't have any options. Nepomuk is enabled in System Settings.
- Solution: Rename the folder ~/.kde4/share/apps/dolphin (in some distros it will be ~/.kde/share/apps/dolphin) and restart dolphin. This will purge your dolphin customizations but the entries should be back. If everything works as expected you can then delete the folder. This happened to me after an upgrade from KDE 4.4 to 4.5
Problem: When I choose the application to open a specific filetype with, it seems to affect other filetypes too. It’s like Dolphin cannot tell the difference between the two different filetypes.
- Solution: Probably the KDE platform does not know about one of the two filetypes, so it associates the filetype to a different, known filetype. This is common with XML-based filetypes; even if they use a file extension of their own (e.g. .xliff or .graphml), if they are not a filetype known by the KDE platform, they will be treated as any other XML file, and opened with the default application to open XML files.
- To solve this issue, you can use File Associations to create an entry for the unrecognized filetype.
Also see forums and the Dolphin Handbook.
Keywords
File management, file manager, file browser, tags, metadata, Nepomuk