Zoho Gears Up for Offline Web Apps

Talking of Zoho, it seems it has beaten Google to the punch when it comes to using Google Gears for offline Web app word processing:

In August, we made Zoho Writer available offline. When we released it back then, the documents were available in read-only mode when offline. With today’s update, you’ll now be able to view and edit your documents offline. This functionality is based on Google’s open source project Google Gears. We thank them for the project and their support.|

For Zoho Writer to work offline, you’ll need to have Google Gears plug-in installed on your browser (works on Firefox 1.5+, IE 6+). Click on ‘Go Offline’ to access your documents offline. By default, we download 15 documents each from ‘My Docs’ and ‘Shared Docs’ section. You can change the default setting by clicking on the down arrow beside ‘Go Offline’ link. The documents are downloaded based on the ‘Sort Order’ in your ‘My Docs’ section.

When you are not connected to the internet, you can visit http://writer.zoho.com/offline to access and edit your documents offline. When you are back online, clicking on ‘Go Online’ will let you to synchronize the modified documents with the online versions.

A taste of things to come, when this will be standard for all Web apps. (Via Blognation.)

Why Javascript, not Flash? - Ask Zoho

I've only just come across this, perhaps the best summary of why using Flash is the wrong way to create Web apps:

1. Native to the Web

A real web application should natively support web standards - HTML & CSS are pretty much synonymous with “web standards”. The biggest reason we started out with Javascript is that it is native to the web - in the sense its core object model for Javascript is the HTML/CSS Document Object Model. The DOM is a gift to web applications. Even with the annoying browser differences in DOM (which sophisticated libraries increasingly hide), it is still far better to have the DOM than not have it. Flash, for all its advantages, sits in a separate space from the browser. In that sense, Flash is not that different from Java-on-the-client. In fact, Flash is Java-on-the-client-done-right.

I am sure Flash will eventually find a way to natively integrate with the browser but it is not there yet.

2. Open Source Library Support

This is a big one. The depth and variety of libraries available in Javascript just keep getting better. It is mind boggling just how much open source development is going on in Javascript. Developers keep pushing the envelope. For one example, look at the jQuery solar system demo. It shocked me the first time I saw it. Pretty impressive that Javascript could do that, right? The capabilities of Javascript exceed the client requirements of office productivity applications today, and there are tons more innovations coming.

3. Vector Graphics in Browsers

This is another big one. Vector graphics formats like SVG (Firefox, Opera), VML (IE), and HTML Canvas (Firefox, Safari, Opera), are becoming ubiquitous in browsers. Yeah, it sucks that IE doesn’t support SVG, but that can be worked around. Even cooler is the fact that SVG & VML are XML and very Javascript friendly. You can do real magic.

Obviously, number 2 is the heart of the matter: Javascript is just going to keep getting better, faster, thanks to the open development process. With Flash, you're dependent on the skills of one company (now, where have I heard that before?)