Changes

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

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, that web developers could already build on. A small utility that generates sugarified web applications would also use that template. <br />The utility and a nice demo of Webified usage could then be made in a few days, two weeks at most. <br /> The integration with the Journal is not meant to be more complex than saving the Gears sqlite library and the URL in the Journal.<br />

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, that web developers could already build on. A small utility that generates sugarified web applications would also use that template. <br />The utility and a nice demo of Webified usage could then be made in a few days, two weeks at most. <br /> The integration with the Journal is not meant to be more complex than saving the HTML and Gears state in the Journal.<br />

The remaining time could then be spent on better integration, providing a small JavaScript wrapper API similar in concept to [http://fluidapp.com/developer/ Fluid's]), polishing things up and for any eventual emergencies.<br />

The remaining time could then be spent on polishing things up and for any eventual emergencies.<br />

Beyond GSoC, I would like to keep working this.

Beyond GSoC, I would like to keep working on this.

<br />Milestones:

<br />'''Milestones''':

# Webified SSB can load a website (hello world)

# Webified SSB can load a website (hello world)

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

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

# Browse can successfully "sugarize" GMail and the resulting .xo works.

# Browse can successfully "sugarize" GMail and the resulting activity works.

# Webified SSB can save it's Gears state in the Journal.

# Webified SSB can save it's Gears state in the Journal.

# JavaScript from inside a Webified SSB can call dbus stuff (dbus hello world)

# JavaScript from inside a Webified SSB can call dbus stuff (dbus hello world)

# Webified SSB can run a hello world userscript (GreaseMonkey)

 

# (Optional) Webified SSB can use hello world userstyle (CSS)

# Webified SSB can run a userscript (GreaseMonkey)

# Webified SSB can use a userstyle (CSS)

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

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

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

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

<strong> Myself</strong> <br />

'''Myself''' <br />

:The result of my project would be something akin to Fluid (and 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.<br />

:The result of my project would be something akin to Fluid (and 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.<br />

:The web is moving towards websites-as-applications and there are many projects to help integrate these new applications with the various desktop environments ([http://en.wikipedia.org/wiki/Adobe_Integrated_Runtime AIR], [http://en.wikipedia.org/wiki/Silverlight#Silverlight_3 Silverlight Out-of-Browser Experience], [http://developer.mozilla.org/en/Prism Mozilla Prism], [http://fluidapp.com Fluid]). There is also the bold [http://en.wikipedia.org/wiki/Palm_webOS webOS] from Palm, that fully embraces web technologies by making them the default toolkit for building applications for the platform.

:The web is moving towards websites-as-applications and there are many projects to help integrate these new applications with the various desktop environments ([http://en.wikipedia.org/wiki/Adobe_Integrated_Runtime AIR], [http://en.wikipedia.org/wiki/Silverlight#Silverlight_3 Silverlight Out-of-Browser Experience], [http://developer.mozilla.org/en/Prism Mozilla Prism], [http://fluidapp.com Fluid]). There is also the bold [http://en.wikipedia.org/wiki/Palm_webOS webOS] from Palm, that fully embraces web technologies by making them the default toolkit for building applications for the platform.

:It would be great to bring these ideas to Sugar, as they would enable easier usage of web applications and in general more orientation towards the web. It would also allow web developers to easily extend those websites to better integrate with Sugar, increasing the developer pool of and raising awareness towards Sugar.<br />

:It would be great to bring these ideas to Sugar, as they would enable easier usage of web applications and in general more orientation towards the web. It would also allow web developers to easily extend those websites to better integrate with Sugar, increasing the developer pool of and raising awareness towards Sugar.<br />

<strong>Bryan Berry</strong> [http://lists.sugarlabs.org/archive/iaep/2009-January/003451.html mailing list thread]<br />

'''Bryan Berry''' [http://lists.sugarlabs.org/archive/iaep/2009-January/003451.html mailing list thread]<br />

:Again, this requires people to learn python, a whole new language that they don't necessarily use at work. We need to enable developers to be very productive in just 2-3 hours per week. For them to be productive they need to be using tools they are already familiar w/.

:Again, this requires people to learn python, a whole new language that they don't necessarily use at work. We need to enable developers to be very productive in just 2-3 hours per week. For them to be productive they need to be using tools they are already familiar w/.

:Python is a tool popular among sysadmins and hackers. It is great tool. But folks who develop web UIs use css, html, javascript, and flash. I highly doubt that will change in the near or distant future. These are people we need to recruit as activity designers.

:Python is a tool popular among sysadmins and hackers. It is great tool. But folks who develop web UIs use css, html, javascript, and flash. I highly doubt that will change in the near or distant future. These are people we need to recruit as activity designers.

<strong>Tomeu Vizoso</strong> [http://lists.sugarlabs.org/archive/iaep/2009-January/003445.html same mailing list thread] <br />

'''Tomeu Vizoso''' [http://lists.sugarlabs.org/archive/iaep/2009-January/003445.html same mailing list thread] <br />

: Without needing to get into what is better for our deployments, I do see value in making easier to make Sugar activities using technologies such as HTML, CSS, etc

: Without needing to get into what is better for our deployments, I do see value in making easier to make Sugar activities using technologies such as HTML, CSS, etc

  Are you a mentor? Could I please get a paragraph in here from you? Pretty please?

  Are you a mentor? Could I please get a paragraph in here from you? Pretty please?