Features/Show Thumb Drives As Hierarchical
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.
This should link to your home wiki page so we know who you are
- Name: James Simmons
- Email: <firstname.lastname@example.org>
- Targeted release: (SUGAR_VERSION)
- Last updated: (DATE)
- Percentage of completion: XX%
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
Plan Ceibal has created an Activity "Leer Pendrive" which simply displays the contents of removable devices as a GTK file chooser and lets people copy selected files to the clipboard, from where they can be pasted into the Journal. I understand there was a big demand for this. I followed this up with my own Activity, Sugar Commander, which lets you copy files directly to the Journal without using the clipboard. I understand that this Activity has a following and is routinely included on XOs in Australia. Neither of these Activities allow you to copy from the Journal to a thumb drive, and there is a legitimate need to do this.
The beneficiaries of this feature will be teachers, older students, and others who need to deal with thumb drives and SD cards and move data in and out of the Journal.
See the code for the Sugar Commander Activity for a simple implementation of this idea.
Have a look at the Sugar Commander Activity:
How To Test
If this is done well, when the user switches from viewing the Journal to viewing the contents of a removable drive he will see a conventional representation of files and directories like a GTK file chooser and will be able to copy files from this into the Journal and copy Journal entries into the file system. He'll also be able to create directories on the thumb drive, rename things, etc.
If the feature is implemented well then children who never use thumb drives, etc. won't know the new feature is there.
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?
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.
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.
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.