158
edits
Changes
no edit summary
* 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 />
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 />
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.
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.
# 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
# Browse can successfully "sugarize" GMail
# Webified SSB can save it's Gears state in the Journal.
# Webified SSB can save it's Gears state in the Journal.
# JavaScript from within a Webified SSB can make dbus calls (dbus hello world)
# JavaScript from inside a Webified SSB can play sounds through the dbus bridge
# (Optional) Webified SSB can run a hello world userscript (GreaseMonkey)
* 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.