Changes

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 />Milestones:

<br />Milestones:

# Webified can load a website (hello world)

# Webified template can load a website (hello world)

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

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

# JavaScript from within Webified can make dbus calls

# JavaScript from within Webified template can make dbus calls

# Browse can successfully "sugarize" GMail.

# Browse can successfully "sugarize" GMail.