102
edits
Changes
Jump to navigation
Jump to search
Line 133:
Line 133: + + + + + + + Line 174:
Line 181: − +
Summer of Code/2016/SugarJournalSaveOption UtkarshT (view source)
Revision as of 13:13, 23 March 2016
, 13:13, 23 March 2016→About your project
*<b>Sugar Journal back and restore-</b>
*<b>Sugar Journal back and restore-</b>
Many of Sugar deployments are to areas where the purchase of a usb stick is problematic. The real problem is that the available storage for the Journal runs out. However, a straight backup and restore cannot create space to enlarge the effective size of the Journal. The Journal on the XO should be a cache for active items and the rest should be stored on a school server (a server with a large hard drive capable of storing the Journal objects for all XOs in the deployment. OLPC, at one point, suggested a reserve of 2GB per XO (e.g. 200GB for a 100 XO deployment). A simple example would be a RAM(XO) and Secondary storage(school servers) in PCs.
This feature will provide a way for users to deal with a full storage without significant technical skills. Currently the Journal, installed activities, and content files in /lhome/olpc/Library can contribute to filling the store. With a school server, a scheme to provide least-recently-used offload of content becomes possible. If all activities are available for download, least-recently used activities can be erased. If the Journal is stored on the school server, journal objects can be deleted locally (and later restored as needed). The motivation for the content /home/olpc/Library goes away if that content can be downloaded to the Journal as needed. The problem with the current scheme is that at best it is a sampler of the content sources (e.g. wikibooks). It would be better to put all of the content on the school server and have users download as needed.
Here is a flowchart to demonstrate the above proposed mechanism->
* Is there anything else we should have asked you or anything else that we should know that might make us like you or your project more?
* Is there anything else we should have asked you or anything else that we should know that might make us like you or your project more?
I am pretty good at taking up challenging tasks(I tried integrating features to Sugar that have been requested since a long time ;)). After the completion of my project I would like to continue with my work on adding keyboard accessibility to Journal and download manager improvement in Browse. I am also planning to write an API (as suggested by Mr.Sam Parkinson) to extend keyboard accessibility to Sugar.
I am pretty good at taking up challenging tasks(I introduced some cool features in Sugar that have been requested since a long time ;)) which seem difficult to others. After the completion of my project I would like to continue with my work on adding keyboard accessibility to Journal and download manager improvement in Browse. I am also planning to write an API (as suggested by Mr.Sam Parkinson) to extend keyboard accessibility to Sugar which would help kids to operate Sugar even without a mouse or some other pointing deviceǃ
Please include the category tag at the bottom of your page the Category tag for 2016 GSoC applications.
Please include the category tag at the bottom of your page the Category tag for 2016 GSoC applications.
[[Category:2016 GSoC applications]]
[[Category:2016 GSoC applications]]