Latelly I’ve been reading a lot about offline web applications, since this is the topic of my final project. I decided to focus on Google Gears for a couple of reasons, the most important being that this API is specifically designed for offline browsing, its new BSD, and it was mine and my boss’s favorite after I presented him all the options I could find (Adobe AIR, Microsoft Silverlight (I couldn’t find good information on taking webapps offline with Silverlight), Mozilla Prism, WhatWG HTML 5 specs.

One thing that I don’t fully understand in Google’s implementation of offline support is the need to press a button to go offline. Why did they use a button?? Imagine that you’re using your laptop, you forget to take Reader offline and next day you find yourself without a connection… Or imagine you are working with intermittent connection but this time you remembered to take Google Reader offline, but now you cannot take advantage of the limited connection you have to get updates; really annoying and frustrating, and Google Docs is also using the same approach.

I know it’s not easy to get rid of the evil “switch-between-online-and-offline” button, but I also know that it is possible, and I would be really nice to see it happen with Google Reader and Google Docs.

I have a an external 2,5” USB socket that I will try to use today to get everything out before I send it to warranty.

Since I don’t know much about code analysis and metrics, the short descriptions for the queries shipped with the app don’t help me much, so here is a quite nice description for each metric.

I’m doing my internship at Critical Software. The project is “Enabling offline execution of the WOW! Product”.
WOW stands for Work Orders Web, and work flow and work orders management tool. It is based in Java using Stripes and Spring.

To do the offline bit, I was investigating many options, but I choose Google Gears to do it. It will be a prototype, covering only a very limited portion of the online functionality.