Users should not have to learn hierarchical filesystems.
- As part of testing a syndication aggregator they are considering switching to, the user wants to import their feed list from an OPML file exported from their current default aggregator.
- Rather than forcing the user to play file clerk, the system presents a listing of all the OPML files within the search scope.
- The user wants to review the transcript of a recent conversation.
- The system locates and displays all of the chat transcripts.
QuickTime Player can also open images and audio files, but the primary use (based on my rather informal research) is for playing movies. As Cooper wrote, design for what is probable, not what is possible.
Notes and Thoughts
- The default dialog search rules (if any) would be set by the application's developer.
- Users could browse the filesystem hierarchically by clicking on a sidebar location which would then become the top level of the view. Column view would be available in Browse mode.
- Each dialog would remember whether it was in Spotlight or Browse mode.
- Performance is pretty good once Spotlight has indexed all UTIs for autocompletion with "Kind: Others ", but the initial run takes quite a while and makes the Finder appear to have crashed. Performing this step automatically at the time of a system update would be preferable.
- Multiple Kind rules either produce no results because they cannot find files matching both Kinds (as depicted below) or they cause the Finder to crash. I believe OR queries are possible using Raw Query input, but that is obviously not a good solution for most users.