Changes

====About your project====

====About your project====

* What is the name of your project?

<br />* What is the name of your project?

Webified Toolkit

Webified Toolkit

* Describe your project in 10-20 sentences. What are you making? Who are you making it for, and why do they need it? What technologies (programming languages, etc.) will you be using?

<br />* Describe your project in 10-20 sentences. What are you making? Who are you making it for, and why do they need it? What technologies (programming languages, etc.) will you be using?

I'm making a small toolkit that can allow building activities using web technologies.<br/><br/>

I'm making a small toolkit that can allow building activities using web technologies.<br/><br/>

I will be focusing on the second stragety.<br />

I will be focusing on the second stragety.<br />

* Why not use existing solutions like Mozilla Prism or Titanium?

<br />* Why not use existing solutions like Mozilla Prism or Titanium?

# Prism. It's just a stripped-down firefox. To make it useful, at least Gears would have to be installed and there would still remain the issue of integration, since Prism is designed for regular desktops. Porting Prism would be too much work, but there may be useful code in Prism, like the webapp creation utility.  

# Prism. It's just a stripped-down firefox. To make it useful, at least Gears would have to be installed and there would still remain the issue of integration, since Prism is designed for regular desktops. Porting Prism would be too much work, but there may be useful code in Prism, like the webapp creation utility.  

# Titanium. Titanium is more interesting, as it already is an SDK for creating desktop applications with web technologies. It's only real technical disadvantage is introducing a new dependency (webkit) in Sugar. However, it's [http://titanium-js.appspot.com/Core/Titanium design] is largely incompatible with Sugar, as it focuses on traditional desktops. Refactoring all that to fit into Sugar would be too much work.

# Titanium. Titanium is more interesting, as it already is an SDK for creating desktop applications with web technologies. It's only real technical disadvantage is introducing a new dependency (webkit) in Sugar. However, it's [http://titanium-js.appspot.com/Core/Titanium design] is largely incompatible with Sugar, as it focuses on traditional desktops. Refactoring all that to fit into Sugar would be too much work.

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

<br />* 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.

I plan to get Gears integration, dbus access and a nicer js wrapper on top of that done in the first 2-3 weeks. This would create a template for web-based activities, what web developers would use when starting web activities. A small utility that generates sugarified web applications would also use that template. <br />The utility and small demo of using the APIs directly(second usage of the toolkit) could then be made in a few days, one week at most. The rest of the time could then be spent for polishing things up or for emergencies.

I plan to get Gears integration, dbus access and a nicer js wrapper on top of that done in the first 2-3 weeks. This would create a template for web-based activities, what web developers would use when starting web activities. A small utility that generates sugarified web applications would also use that template. <br />The utility and small demo of using the APIs directly(second usage of the toolkit) could then be made in a few days, one week at most. The rest of the time could then be spent for polishing things up or for emergencies.

<br /><br />Milestones:

<br />Milestones:

# Webified can load a website (hello world)

# Webified can load a website (hello world)

# Webified can use GMail in offline mode (through Gears)

# Webified can use GMail in offline mode (through Gears)

# JavaScript from within Webified can make dbus calls

# JavaScript from within Webified can make dbus calls

# Browse can successfully "sugarize" GMail.

# Browse can successfully "sugarize" GMail.

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

 

<br />* 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.

Python is my favourite programming language and JavaScript is a close enough second.

Python is my favourite programming language and JavaScript is a close enough second.

I have also used   

I have also used   

====You and the community====

====You and the community====

 

<br />* If your project is successfully completed, what will its impact be on the Sugar Labs community? Give 3 answers, each 1-3 paragraphs in length. The first one should be yours. The other two should be answers from members of the Sugar Labs community, at least one of whom should be a Sugar Labs GSoC mentor. Provide email contact information for non-GSoC mentors.

* If your project is successfully completed, what will its impact be on the Sugar Labs community? Give 3 answers, each 1-3 paragraphs in length. The first one should be yours. The other two should be answers from members of the Sugar Labs community, at least one of whom should be a Sugar Labs GSoC mentor. Provide email contact information for non-GSoC mentors.

The result of my project would be something akin to Mozilla Prism, but tailored for Sugar. It would allow users to make separate activities out of websites and, if those websites support Gears, also take them offline. It would also allow web developers to more easily develop applications for Sugar.

The result of my project would be something akin to Mozilla Prism, but tailored for Sugar. It would allow users to make separate activities out of websites and, if those websites support Gears, also take them offline. It would also allow web developers to more easily develop applications for Sugar.

* Sugar Labs will be working to set up a small (5-30 unit) Sugar pilot near each student project that is accepted to GSoC so that you can immediately see how your work affects children in a deployment. We will make arrangements to either supply or find all the equipment needed. Do you have any ideas on where you would like your deployment to be, who you would like to be involved, and how we can help you and the community in your area begin it?

<br />* Sugar Labs will be working to set up a small (5-30 unit) Sugar pilot near each student project that is accepted to GSoC so that you can immediately see how your work affects children in a deployment. We will make arrangements to either supply or find all the equipment needed. Do you have any ideas on where you would like your deployment to be, who you would like to be involved, and how we can help you and the community in your area begin it?

* What will you do if you get stuck on your project and your mentor isn't around?

<br />* What will you do if you get stuck on your project and your mentor isn't around?

Ask other mentors and GSoC students or developers of related open source software.

Ask other mentors and GSoC students or developers of related open source software.

* How do you propose you will be keeping the community informed of your progress and any problems or questions you might have over the course of the project?  

<br />* How do you propose you will be keeping the community informed of your progress and any problems or questions you might have over the course of the project?  

In the worst case emails to my mentor and commits. Maybe I'll set up a blog and use that.

In the worst case emails to my mentor and commits. Maybe I'll set up a blog and use that.