Changes

Jump to navigation Jump to search
401 bytes added ,  09:55, 12 April 2009
Line 70: Line 70:  
   Also, is necessary to define a directory structure in the storage device in order to let sugar recognize that a sugar-grane is present, eg:
 
   Also, is necessary to define a directory structure in the storage device in order to let sugar recognize that a sugar-grane is present, eg:
 
    
 
    
   sugar-grane_unique_user_id
+
   sugar-grane_unique_user_id/
 
   |
 
   |
 
   *--> session.info  -- Information about the sugar-grane session as id, creation date, last updated, etc
 
   *--> session.info  -- Information about the sugar-grane session as id, creation date, last updated, etc
 
   *--> Activities/  -- Full activities
 
   *--> Activities/  -- Full activities
 
   *--> Journal/      -- Journal information
 
   *--> Journal/      -- Journal information
   *--> Preferences/  -- User session preferences as colors, name, picture, etc
+
   *--> Preferences/  -- User session preferences as colors, name, picture, list of friends, etc
 
   
    
 
    
 +
  using the proposed structure defined above, when a mass storage device is plugged, Journal will mount the device per default behavior and then we try to detect if exists a sugar-grane_unique_user_id directory, after validate the session.info file information and if everything is ok, we launch a UI sugar_grane UI dialog asking to the user if he wants to switch to the session found.
 
    
 
    
 
* What is the timeline for development of your project? The Summer of Code work period is 7 weeks long, May 23 - August 10; tell us what you will be working on each week. (As the summer goes on, you and your mentor will adjust your schedule, but it's good to have a plan at the beginning so you have an idea of where you're headed.) Note that you should probably plan to have something "working and 90% done" by the midterm evaluation (July 6-13); the last steps always take longer than you think, and we will consider cancelling projects which are not mostly working by then.
 
* What is the timeline for development of your project? The Summer of Code work period is 7 weeks long, May 23 - August 10; tell us what you will be working on each week. (As the summer goes on, you and your mentor will adjust your schedule, but it's good to have a plan at the beginning so you have an idea of where you're headed.) Note that you should probably plan to have something "working and 90% done" by the midterm evaluation (July 6-13); the last steps always take longer than you think, and we will consider cancelling projects which are not mostly working by then.
22

edits

Navigation menu