The Xtended Call History Google Gadget allows you to view your call logs, click to return calls, and filter based on missed, received, and placed calls.

Benefits

The Xtended Call History Google Gadget provides multiple ways to interact with the web application. By supporting multiple containers, an end user can access his or her call logs in a variety of ways. 

The Xtended Call History Google Gadget is a simple, yet elegant, example of how easy it is to create applications using the Xtended Services Interface.  It supports the following features:

• View Call Logs
  

• Filter Missed, Received, and Placed Calls: Only see the types of call logs you need.
  

• Click to Return Call: Quickly return missed calls by clicking the caller ID.

The Xtended Call History Google Gadget allows a simple and efficient way to access your call logs in the following containers:

• iGoogle Portal: Add the Xtended Call History Google Gadget to your iGoogle homepage using all major web browsers (tested on Apple Safari, Internet Explorer, Google Chrome, Mozilla Firefox).

• Google Desktop: Add the Xtended Call History Google Gadget as a gadget that sits on your desktop or you may be dock the gadget to the Google Desktop sidebar.

• iPhone: A scaled-down version intended to be viewed using the Apple Safari for iPhone.

Design

The Xtended Call History Google Gadget is a basic gadget designed to demonstrate the use of the Xtended Service Interface. It is simple since it only uses two commands to provide its overall functionality. The rest of the magic is done on the client side.

Wendell Keuneman used the very feature rich ExtJS javascript library (http://www.extjs.com), for the user interface, and trusty Ajax and XML for asynchronous requests and response data.

To make this gadget as portable as possible Keuneman wrote a custom service in PHP which supports the proxying of RESTful Ajax requests. As most developers are aware, Ajax cross-domain calls are denied by the browser security sandbox. The proxy was written to work around this problem, yet still maintains a level of security by only accepting requests from the local host machine.

Technical Specifications