Plasma/Active/PA4/Files: Difference between revisions
Line 63: | Line 63: | ||
=== Content-type Specific Metadata as Tags === | === Content-type Specific Metadata as Tags === | ||
Jerry has copied a number of photos from his camera SD card to his tablet. He opens Files to view the images and finds select metadata in the Tags section pulled from the keyword and geolocation metadata of the images. Similarly, he has a number of books on his device with author and other metadata associated with them. When opening books, this metadata appears in the Tags automatically. | Jerry has copied a number of photos from his camera SD card to his tablet. He opens Files to view the images and finds select metadata in the Tags section pulled from the keyword and geolocation metadata of the images. Similarly, he has a number of books on his device with author and other metadata associated with them. When opening books, this metadata appears in the Tags automatically. | ||
''Suggested Solution'': provide some specific UI for resource type (the same ones as the sidebar: documents, music, images...) | |||
that ui, living in the sidebar will allow to filter by metadata specific for the type, like author, album, geolocation, etc. | |||
Types of metadata can be specific for a resource type, for instance Album would be available only in "music" |
Revision as of 09:50, 29 October 2012
PA4 tasks discovery process for Files application.
Functional Defects
Method
One line per defect describing it. We will triage confirmed and unfixed to bugs.kde.org.
Status | Name | Summary | Developer |
---|---|---|---|
TODO | Tag reset | Select a tag, change file type being shown; tags UI is reset and you can not un-set the tag selected |
|
TODO | Perform a search that results in a folder being shown; enter the folder. The sidebar UI becomes permanently disabled. |
UI Improvements
Method
One section per issue. User stories for workflow related issues. Include a problem statement and possible solution:
Problem: ... User story: ... Suggested Solution: ...
Status | Name | Summary | Developer |
---|---|---|---|
TODO | Sidebar Tabs | Description |
|
IN PROGRESS | Intro Page | Description |
|
Sidebar Tabs
Problem: The sidebar tabs match the content area background, do not always line up with the sidebar and are visually noisy as separate tabs. Suggested Solution: Merge the three tabs into a single (visually) tab with dividers between the words; make the width be the sidebar width and position directly above it; adjust the image used so that it matches the sidebar "hatch" background better visually.
Intro Page
Problem: the intro page is redundant with the main sidebar: there are the same categories and they may get out of sync. Moveover it makes people want to "go back" when there is no need to. Suggested Solution: get rid of the intro page completely. Start with just the sidebar, selecting a category makes the main page slide in
Missing Functionality
Method
Provide a user story describing the workflow that is not currently possible. Implementation planning will happen in a second round. (So detailed solutions do not need to be suggested.)
Content-type Specific Metadata as Tags
Jerry has copied a number of photos from his camera SD card to his tablet. He opens Files to view the images and finds select metadata in the Tags section pulled from the keyword and geolocation metadata of the images. Similarly, he has a number of books on his device with author and other metadata associated with them. When opening books, this metadata appears in the Tags automatically.
Suggested Solution: provide some specific UI for resource type (the same ones as the sidebar: documents, music, images...) that ui, living in the sidebar will allow to filter by metadata specific for the type, like author, album, geolocation, etc. Types of metadata can be specific for a resource type, for instance Album would be available only in "music"