Wednesday, February 20th, 2008

Gears 0.2 is in the wild, in production

Category: Gears, Google

We have talked before about Google Gears 0.2. Now, it has been fully released and has been updated on users machines so you can rely on the APIs. The API changes include:

  • New modules: HttpRequest and Timer. The main reason for these modules was that developers told us they wanted to make HTTP requests and create timers inside Gears workers. But these modules can also be used outside of workers. For example, one advantage to using the Gears HttpRequest module instead of normal XMLHttpRequest is that Gears HttpRequest module addresses a common problem making comet-style applications work on IE.
  • Improved support for handling errors in workers. This is an area where we received a lot of good feedback. Now, errors from workers are automatically bubbled up to the main page by default so that you can see them in the error console or in Firebug. Or, you can handle them explicitly with the new onerror event.
  • Ability to load workers from a URL, even cross-domain URLs. We’ve long wanted the ability to load workers from a URL. We’ve also wanted to provide a way for different domains to communicate safely. This is useful in the case of mashups, or when an application spans multiple domains. The new createWorkerFromUrl API solves both these problems.

Now 0.2 is in production, the Gears team can look to 0.3 and items such as:

  • Added initial Desktop module.
  • Factory changes:
    • Added the hasPermission property.
    • Added the getPermission() method.
  • LocalServer changes:
    • Added the oncomplete, onerror, and
      onprogress events to the
      ManagedResourceStore class.

And hopefully some really interesting items such as those that I have been chatting about.

What would you like to see?

Posted by Dion Almaer at 8:13 am
Comment here

3.4 rating from 17 votes

Comments Here »

Comments feed TrackBack URI

Leave a comment

You must be logged in to post a comment.