Sugar Grane: Difference between revisions
m fix camelcase links |
|||
| Line 61: | Line 61: | ||
kid session to another Sugar environment if desired. | kid session to another Sugar environment if desired. | ||
* How it should work | |||
The main design of this project involves to patch the Sugar Core, adding the availability to reload different phases of the startup process as requested: | |||
- Read activities lists from given path | |||
- Load journal information using given path | |||
- Set current user information | |||
- Activities: Sugar read two main directories to get the activities list and then it build on fly the launcher for each one, | |||
* 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. | ||