Three ‘core’ JavaScript APIs are provided:

LocalServer A local cache html, JavaScript and image files. Also provides mapping from on-line URLs to off-line URLs.

Database Google Gears comes with an SQLite database which is accessible via the Database API.

WorkerPool I have not used this, but the Google Gears description states, it can “Make your web applications more responsive by performing resource-intensive operations asynchronously”.

I’ve put together an example which uses the LocalServer and Database JavaScript APIs.

Try out the Google Gears Example using the Digg API

Try out the following steps

• You’ll be asked to install Google Gears first, if you don’t already have it installed
• Fetch some Digg story titles from the drop down list, these story titles are saved into a local database provided by Google gears on you machine.
• This is where the magic happens! On the right hand side click capture.
• The document is now captured and available for off-line browsing. Go ‘off-line’, so in Firefox click ‘File’, ‘Work Offline’.
• View the URL again, and low and behold you will see the same web page even though you are Off-line. You’ll also notice a list of the titles that you had fetched before you went off-line.
• You can Erase the the document from Google Gears with the ‘Erase’ button too, and empty the database with ‘Empty’ if you wish.

And that’s that! Two out of three of the Google Gears demonstrated. Remember to put your browser back on-line when you’re done.

A couple of caveats

• Google Gears does not do server side scripting. The functionality that you wish to make available off-line must be implemented via JavaScript.
• Adding Google Gears functionality to an existing web application will require additional code in your application. How much code depends on the level of off-line functionality you want to achieve. You will need to insert logic into your app to check it’s off-line/on-line state and to tell it what to do if it’s off-line as well as when it’s on-line.

The ticket reads as follows:

I have found what I think is a bug with the interface/sortable plugin for jquery.

To explain my scenario. I am using the jquery and the sortable plugin from interface. The sortable items are divs as normal that contain object and embed tags to a flash swf file.

In FF when I drag the divs around the flash movie appears smooth and as you would expect.

However in IE 6 and IE7 when I drag the div around the flash movie will disappear and reappear. It will be replaced by the white rectangle that seems to get stuck and leave a trail and lingers for a split second. When I stop sorting/dragging the div the flash movie reappears..

I’ve made an example available, try drag around the Flash game here, when in IE .

Any ideas with this one?

Powered by ScribeFire.

OK forget that.

It will remove the quicktime player, but the audio will stay playing. Only in IE of course.

You’ll need to use Javascript to stop the quicktime movie.

The best guide I’ve found to do this.

Let’s say you have a quicktime movie, and it’s marked up in your HTML using the <object> tags.

In Firefox you can use the removeNode(id of your quicktime object tag) method to remove quicktime object. This works fine.

However in IE 6 and IE 7 this will not work. Surprise, surprise! The quicktime object/player will stay on the screen even though it does no longer exist in the DOM. You’ll need to refresh to get ride of it. Not very nice!

To properly remove a quicktime object using IE6 and Ie7 using javascript you’ll need to do one extra step.

What you’ll need to do is first set the css display property of the quicktime object to none.

Now you can use the normal removeNode(id of your quicktime object tag) to remove it.

So something like this

var e = document.getElementById(’id of your quicktime object’);
e.style.display = ‘none’;
document.body.removeChild(e);