Difference between revisions of "Features/Show Thumb Drives As Hierarchical"
(Created page with "<noinclude> Category:Feature Page Incomplete <Feature Name> <!-- You can add categories to tie features back to real deployments/schools requesting them,...") |
|||
| Line 5: | Line 5: | ||
[[Category:Features requested by School Xyz|<Feature Name>]] (the |Feature Name option sorts the entry on the category page under the first letter of <Feature Name>). --> | [[Category:Features requested by School Xyz|<Feature Name>]] (the |Feature Name option sorts the entry on the category page under the first letter of <Feature Name>). --> | ||
</noinclude> | </noinclude> | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
== Summary == | == Summary == | ||
| − | + | There is a desire from many users to replace the part of the Journal UI that represents files on thumb drives and SD cards as if they were Journal entries, instead of what they actually are, which is files within directories. I suggest that only Journal entries should be represented as such, and that thumb drives and SD cards should be represented conventionally. | |
== Owner == | == Owner == | ||
''This should link to your home wiki page so we know who you are'' | ''This should link to your home wiki page so we know who you are'' | ||
| − | * Name: [[User: | + | * Name: [[User:Jdsimmons| James Simmons]] |
| − | + | * Email: <nicestep@gmail.com> | |
| − | * Email: < | ||
== Current status == | == Current status == | ||
| Line 31: | Line 21: | ||
== Detailed Description == | == Detailed Description == | ||
| − | + | There is a desire from many users to replace the part of the Journal UI that represents files on thumb drives and SD cards as if they were Journal entries, instead of what they actually are, which is files within directories. Representing these files as if they are Journal entries creates an expectation in the user that they will behave as Journal entries do, and in fact they do not. It also makes it difficult, perhaps impossible, to deal with directories on the thumb drive or SD card. | |
== Benefit to Sugar == | == Benefit to Sugar == | ||
Revision as of 15:17, 21 November 2011
Summary
There is a desire from many users to replace the part of the Journal UI that represents files on thumb drives and SD cards as if they were Journal entries, instead of what they actually are, which is files within directories. I suggest that only Journal entries should be represented as such, and that thumb drives and SD cards should be represented conventionally.
Owner
This should link to your home wiki page so we know who you are
- Name: James Simmons
- Email: <nicestep@gmail.com>
Current status
- Targeted release: (SUGAR_VERSION)
- Last updated: (DATE)
- Percentage of completion: XX%
Detailed Description
There is a desire from many users to replace the part of the Journal UI that represents files on thumb drives and SD cards as if they were Journal entries, instead of what they actually are, which is files within directories. Representing these files as if they are Journal entries creates an expectation in the user that they will behave as Journal entries do, and in fact they do not. It also makes it difficult, perhaps impossible, to deal with directories on the thumb drive or SD card.
Benefit to Sugar
What is the benefit to the platform? If this is a major capability update, what has changed? If this is a new feature, what capabilities does it bring? Why will Sugar become a better platform or project because of this feature?
Make sure to note here as well if this feature has been requested by a specific deployment, or if it has emerged from a bug report.
Scope
What work do the developers have to accomplish to complete the feature in time for release? Is it a large change affecting many parts of the distribution or is it a very isolated change? What are those changes?
UI Design
Does the feature have a direct impact on the work flow, or does it need a UI? Link here mockups, or add detailed descriptions.
How To Test
Features/Show Thumb Drives As Hierarchical/Testing
User Experience
If this feature is noticeable by its target audience, how will their experiences change as a result? Describe what they will see or notice.
Dependencies
What other packages (RPMs) depend on this package? Are there changes outside the developers' control on which completion of this feature depends? In other words, does your feature depend on completion of another feature owned by someone else or that you would need to coordinate, which might cause you to be unable to finish on time? Other upstream projects like Python?
Contingency Plan
If you cannot complete your feature by the final development freeze, what is the backup plan? This might be as simple as "None necessary, revert to previous release behaviour." Or it might not. If your feature is not completed in time, we want to assure others that other parts of Sugar will not be in jeopardy.
Documentation
Is there upstream documentation on this feature, or notes you have written yourself? Has this topic been discussed in the mailing list or during a meeting? Link to that material here so other interested developers can get involved.
Release Notes
The Sugar Release Notes inform end-users about what is new in the release. An Example is 0.84/Notes. The release notes also help users know how to deal with platform changes such as ABIs/APIs, configuration or data file formats, or upgrade concerns. If there are any such changes involved in this feature, indicate them here. You can also link to upstream documentation if it satisfies this need. This information forms the basis of the release notes edited by the release team and shipped with the release.