Changes

:We would need to architect and build a UI abstraction layer that would enable users of different age groups to experience the system differently. This should be achieved requiring minimal change on part of the rest of the code base, especially activities.

:We would need to architect and build a UI abstraction layer that would enable users of different age groups to experience the system differently. This should be achieved requiring minimal change on part of the rest of the code base, especially activities.

:Scope:A UI abstraction framework is too much work: for something that we aren't even sure we need. And I won't be able to do it in 3 months single handedly. So I could start paving way for what could eventually become a framework, but still manage to do something useful for the community in these 3 months. Lets take the feature of discoverability of keyboard shortcuts and context menus. I could start working on bringing this feature into Sugar. But do younger children need keyboard shortcuts? Can the clues for enhancing discoverability of such features lead to confusion for those who dont need it? So depending upon the age of the child using the system (obtained from user profile), the system could choose to expose certain clues or not. I think this can be done in 3 months.

:Scope:A UI abstraction framework is too much work: for something that we aren't even sure we need. And I won't be able to do it in 3 months single handedly. So I could start paving way for what could eventually become a framework, but still manage to do something useful for the community in these 3 months. Lets take the feature of discoverability of keyboard shortcuts and context menus. I could start working on bringing this feature into Sugar. But do younger children need keyboard shortcuts? Can the clues for enhancing discoverability of such features lead to confusion for those who dont need it? So depending upon the age of the child using the system (obtained from user profile), the system could choose to expose certain clues or not. I will limit my target groups to two. What age ranges form the groups - needs to be explored (6-10 and 11-15 ?). I think this can be done in 3 months.

; 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.

:This work will be part of my Master's thesis. I would hence be working on the project for the next 1.5 years. I will detail my plan for GSoC and beyond.

:This work will be part of my Master's thesis. I would hence be working on the project for the next 1.5 years. I will detail my plan for the 3 month GSoC period and beyond that.

:May 1 - May 23: * Get to know the code base and the persons behind. * Back ground research of prior work concerning technology and children. * A small informal user study wherein I collect observations of children of different age groups using the system.

*May 1 - May 23:  

:Week 1: Brainstorm different designs based on the observations.

** Get to know the code base and the persons behind.  

:Week 2:

** Back ground research of prior work concerning technology and children.  

:Week 3:

** A small informal user study wherein observations of children from the 2 target age groups using the system are recorded.

*Week 1: Brainstorm different designs based on the observations. Form basic UI design principles and sample mockups for the different age groups. Improvise with feedback from mentor & community. These principles will guide the rest of my work.

*Week 7: Code review and commit. System should now have discoverability of keyboard shortcuts feature depending upon the age of the user.

*Week 8: Refactoring week. Review all committed code and there should be better ways of doing the same thing. Refactor, code review and commit. Blog.

*Week 9: Start work on improving discoverability of context menus.

*Week 10: Code review and commit.

*Week 11: Hook it up with the Adaptive core.

*Week 12: Finish work, core review and commit.

*Week 13: Document work. Blog. Prepare a presentation summarizing my work and experience (for the UBC CS department).

   

   

; Convince us, in 5-15 sentences, that you will be able to successfully complete your project in the timeline you have described. This is usually where people describe their past experiences, credentials, prior projects, schoolwork, and that sort of thing, but be creative. Link to prior work or other resources as relevant.

; Convince us, in 5-15 sentences, that you will be able to successfully complete your project in the timeline you have described. This is usually where people describe their past experiences, credentials, prior projects, schoolwork, and that sort of thing, but be creative. Link to prior work or other resources as relevant.

# We want to make sure that you can set up a [[Development Team#Development_systems|development environment]] before the summer starts. Please send us a link to a screenshot of your Sugar development environment with the following modification: when you hover over the XO-person icon in the middle of Home view, the drop-down text should have your email in place of "Restart." See the image on the right for an example. It's normal to need assistance with this, so please visit our IRC channel, #sugar on irc.freenode.net, and ask for help.

# We want to make sure that you can set up a [[Development Team#Development_systems|development environment]] before the summer starts. Please send us a link to a screenshot of your Sugar development environment with the following modification: when you hover over the XO-person icon in the middle of Home view, the drop-down text should have your email in place of "Restart." See the image on the right for an example. It's normal to need assistance with this, so please visit our IRC channel, #sugar on irc.freenode.net, and ask for help.

; What is your t-shirt size?

; What is your t-shirt size?

:XXL

:XXL (yeah I know, I have to lose weight :)

; Describe a great learning experience you had as a child.

; Describe a great learning experience you had as a child.

:I have been star-eyed kid passionate about absolute energy conservation for as long as I can remember; drawing plans and trying to build perpetual motion systems during playtime. I am not sure when or how it happened, but eventually I began to realize that perfect energy conservation might not be possible. That friction, trade-off and losses are an inevitable part of the equation.  

:I have been star-eyed kid passionate about absolute energy conservation for as long as I can remember; drawing plans and trying to build perpetual motion systems during playtime. I am not sure when or how it happened, but eventually I began to realize that perfect energy conservation might not be possible. That friction, trade-off and losses are an inevitable part of the equation.