One simple solution is not to. After all, you could create a simple AIR app that just invoked the URL of your ColdFusion app (perhaps in a frame if using HTML/JS, or in an HTML control if using Flex). But that’s cheating, all you’ve really done is turned your AIR app into a custom browser.
To truly turn your ColdFusion web app into an AIR app you need to keep in mind the following:
- AIR can’t process CFML, but it can process the HTML generated by CFML.
- Within an AIR application, relative paths will point within the AIR application, not back to the server.
With that said, here is a simple example (based on the two related Ajax controls that I posted months ago):
- Create a new project or site for your new AIR application.
- Execute the ColdFusion app (the .cfm for the two related controls) in your browser to make sure it is working.
- Use the browser View Source option to see the ColdFusion generated source.
- Save the source as a file in to your AIR project or site (you’ll probably want to use a .htm extension, instead of .cfm).
- Now just run the app (in Dreamweaver you can right click, and then Preview In Adobe AIR, or Package As Adobe AIR Application).
Obviously, this process is far from perfect. But, until we implement native AIR integration in ColdFusion, this is a workable solution.