Developing Applications with Google Gears
- How do I delete databases that were created from the Google Gears API?
- Is there a tool to interactively manage and query Gears' SQLite database tables?
- Can Google Gears LocalServer serve up scripting files like PHP or JSP?
- How do I make JavaScript source code available to a child WorkerPool during initialization?
- Is there a tool to interactively manage and query Gears' LocalServer?
- How do I 'offline' a cross-origin resource?
- What LocalServer store do you use when?
- Is there an isOnline function in Google Gears to check whether the application is online? Do you plan to have one?
- What is a cross-origin worker? What is it useful for? How do I use it?
- If I have two applications on separate ports, will they have the same LocalServer and Database files?
- Does LocalServer store URL parameters?
- Do I need to protect from multiple workers editing the database at once?
- Do WorkerPool workers have access to the DOM document object?
- Does Google Gears automatically make my web application work offline?
- Google Gears lets my web application work offline, right? How do I do that?
- Google Gears lets my web application store data on the user's computer, right? How do I do that?
- Google Gears lets my web application run code in the background, right? How do I do that?