Adobe AIR brings the Web to the desktop

One of the points of my article about the qooxdoo JavaScript library was the concept of building Web applications with a rich user interface that mimics desktop applications. This is good if you want to mimic the look and feel of a desktop application within a Web page. On the flip side is bringing the Web to the desktop - that is, leveraging Web development skills on the desktop. The Adobe Labs has released the Adobe Integrated Runtime (AIR), which provides this functionality.

Adobe describes AIR as a cross-operating system runtime that allows developers to leverage existing Web development skills to build and deploy rich Web applications to the desktop. It provides support for Flash, Flex, HTML, JavaScript, and AJAX.

Getting it

To get started with AIR development, you must install the AIR runtime on your computer. Once it is installed, you may download sample applications to see AIR in action and possibly take a peek under the covers at its code.

There are two downloads relevant to AIR development:

• Runtime provides the runtime environment for running AIR applications. Downloads are available for both Windows and Macintosh operating systems.
• Software Development Kit (SDK) provides everything necessary to build AIR applications. This includes templates, Adobe AIR APIs, and debugger and developer tools. The SDK is available for both Windows and Macintosh platforms. The command line debugger and developer tools require a Java installation (JRE or JDK version 1.4.2 or newer).

Additional downloads are available that allow you to build AIR applications within specific Web development tools:

• Adobe Flex Builder 3: Includes support for building Flex applications on Adobe AIR from within Flex Builder.
• Adobe Flex SDK: Allows you to build AIR applications via Flex.
• Adobe AIR Extension for Dreamweaver CS3: Adds support for building AIR applications within Dreamweaver CS3.
• Adobe AIR Extension for Flash CS3 Professional: Allows you to build AIR applications with Flash CS3 Professional.

In addition, a plug-in is available for the Aptana IDE. Once the runtime is installed, you can easily install and run AIR applications, and the SDK allows you to build AIR applications.

AIR HTML application basics

This article focuses on using standard Web technologies HTML and JavaScript to build an AIR application. AIR uses WebKit to parse, layout, and render HTML and JavaScript content. The AIR API provides host classes and objects for providing desktop applications functionality like reading and writing files and managing windows. In addition, an HTML-based AIR application has the Flash API available to it.

An important distinction of HTML-based AIR applications is that the use of the AIR API is optional. That is, you may choose to use only standard HTML and JavaScript to build an application and run it via the AIR runtime. The runtime includes an HTML renderer and JavaScript interpreter in addition to other features.

There are at least two files in every HTML-based AIR application. The first is an application descriptor file that specifies the application metadata via XML. The second file is a top-level HTML page. Also, AIR provides a JavaScript file (AIRAliases.js) that provides aliases for AIR API classes. More robust applications will include more files like Web pages and JavaScript code.

The AIR SDK includes plenty of sample code for getting a feel for the platform. The following sample code is included in the documentation to get you going with a first, simple application (the ever present Hello World demo).

The following descriptor file provides the details of the application. It references the AIR namespace and assigns a name to the application (Hello World!). The initalWindow element defines application startup behavior as an HTML file (Hello.html) is loaded.

<?xml version="1.0" encoding="UTF-8"?><br /><application xmlns="http://ns.adobe.com/air/application/1.0.M5"<br />appId="sample.HelloWorld" version="0.1"><br /><name>Hello World</name><br /><initialwindow><br /><content>Hello.html</content><br /><visible>true</visible><br /></initialwindow><br /></application>

The HTML file (Hello.html) defines the user interface displayed when the application is launched via the AIR runtime. First, the JavaScript aliases file is included to make it easier to work with AIR classes. Next, the JavaScript appLoad function defines what happens when the application loads (function called by onLoad event of page).

The JavaScript function loads data from a simple text file via AJAX and places the text from the file in the HTML element with the ID called replace.

<html><head><br /><title>Hello World</title><br /><script src="AIRAliases.js" mce_src="AIRAliases.js" type="text/javascript"></script><br /><script type="text/javascript"><br />function appLoad(){<br />xmlhttp = new XMLHttpRequest();<br />xmlhttp.open("GET", "request.txt",true);<br />xmlhttp.onreadystatechange=function() {<br />if (xmlhttp.readyState==4) {<br />document.getElementById('replace').innerHTML = xmlhttp.responseText;<br />} }<br />xmlhttp.send(null)<br />}<br /></script><br /></head><br /><body onload="appLoad();"><br /><h1>AIR</h1><br /><div id="replace"><br /><p>Placeholder</p><br /></div><br /></body><br /></html>

Once the application is developed, the AIR command line tools can be used to package and distribute it. The AIR Developer Tool (ADT) creates installation packages, but it requires a digital certificate.

A simple approach

The AIR platform offers a great approach to building desktop applications. I love the fact that it allows me to use existing skills like HTML and JavaScript.

The AIR API offers additional functionality for building client interfaces. The API is JavaScript, so it is easily used within your application. While the qooxdoo approach is the exact opposite, I find the AIR model much more intuitive and easy-to-use. Everything necessary to get started with AIR is freely available online.

Leverage existing skills

A key point of AIR is the ability to port Web development skills to desktop development. Also, using Web technologies like HTML and Flash deliver a familiar interface to users, and developers do not have to spend time learning a new technology such as Microsoft .NET for thick client development. Another strong point is the cross-platform support that is not readily available in other development platforms. If you are interested in desktop applications, take a look at AIR.

The Web browser has evolved into the de facto standard application interface these days, but client applications are still necessary. Have you been faced with developing applications for the desktop? Have you taken a look at AIR?

Control users’ temporary Internet files and browser history using Windows Server 2003 Group Policy

If monitoring software is too costly for your company’s budget, you may want to check out a solution that comes with Windows Server 2003 that will send you users’ Internet browsing information. Windows Server 2003 caches a user’s browser history when they use Internet Explorer. This makes it easier for users to find the site again, and it helps administrators monitor and track Internet activity and keep a better eye on equipment usage. Here’s what happens if you enable these settings.

You can set the location of the user browser history — and prevent users from deleting it — using Group Policy. Group Policy is also where you control temporary Internet files and cookies. To configure these settings, follow these steps:

1. Open the Group Policy Editor.
2. Select the User Configuration node.
3. Click Administrative Template.
4. Click Windows Components.
5. Click Internet Explorer.

With the Internet Explorer node selected, the Details pane is flooded with controls for Internet Explorer. About halfway down the list, you will see these three settings: Disable Changing Temporary Internet Files And Settings, Turn Off Delete Browsing History Functionality, and Disable Configuring History.

* Enabling the Disable Changing Temporary Internet Files And Settings setting within Group Policy. This will cause Internet Options in Internet Explorer to gray out the caching settings on the General tab. If you disable the policy, users will be able to modify these values.
* Enabling the Turn Off Delete Browsing History Functionality setting. Internet Explorer 7 disallows users to delete their browsing history. If you disable this policy, users will be able to delete their browsing history.
* Enabling the Disable Configuring History policy. This prevents users from clearing the history manually or changing the number of days after which the browser history will be cleared. This policy will prompt you to supply a value for the number of days that Internet Explorer should keep the history. If you disable this policy, users will be able to change these settings.

Note: In IE 6, browser history and temporary Internet files are separate; in IE 7, they are grouped together under the Browsing History section.