Preparing to Use Dreamweaver
Before I give you the tour of Dreamweaver, there are a few things you'll need to know and do to prepare for using Dreamweaver to build your ColdFusion applications. Here is what you'll be doing to get ready:
- You'll create and store the Orange Whip Studio applications in a folder named ows beneath the Web root. This folder is referred to as the application root.
- You'll define a site in Dreamweaver that points to that same ows folder.
- You'll create a folder named images in the ows folder, which is used to store images used in many of the applications you'll be developing.
ON THE CD
The files and directories on the accompanying CD follow the same organization and naming conventions as described here.
NOTE
The ColdFusion MX 7 Extensions for Dreamweaver MX 2004 should already be installed. If you have not installed them yet, do so now. Visit the ColdFusion Admin, choose Resources and then follow the link to ColdFusion MX 7 Extensions for Dreamweaver MX 2004. You will be asked to save the file CFMX7DreamWeaverExtensions.mxp. After saving the file, double-click it to begin the install process. See the Extensions section later in this chapter for more information about installing extensions.Creating the Application Root
Every application should go in its own directory structure, andas explained earlierthe Orange Whip Studio applications reside in a directory named ows beneath the Web root.If you are using the integrated HTTP server and you installed ColdFusion in the default location, the Web root will be c:\cfusionmx7\wwwroot, and the application root for the Orange Whip Studio application will be c:\cfusionmx7\wwwroot\ows. If you are using an external HTTP server, the paths will vary accordingly. For example, if you are using Microsoft IIS, the Web root will be c:\inetpub\wwwroot, and the application root should be c:\inetpub\wwwroot\ows.
NOTE
If ColdFusion is deployed on Linux or Unix, the default installation location is /opt/coldfusionmx7, but the paths will likely be based on HTTP server and user settings. Consult your administration if you need help identifying these paths.The first order of business is to create that application root. You can use your operating system's file utilities (for example, Windows Explorer).You don't have to put anything in the new ows folder to make it accessible. The fact that ows is beneath the Web root makes that happen automatically.Starting Dreamweaver for the First Time
The first time you start Dreamweaver, you'll be prompted for the Workspace to use (as seen in Figure 2.1), and you'll have two options. The difference is just a matter of which panels are visible and where they are placed.
- Designer.
Panel groups are arranged to the right of the Document window. The Insert bar is ocated above the Document window, and the Property inspector below. Code and Design view are enabled simultaneously, with code on top and design below. A blank document is open, but not maximized. - Coder.
Enabling this option arranges the workspace in a pattern similar to Macro media HomeSite's environment. A blank document is maximizedthus displaying the MDI (multiple document interface)in Code view. The workspace is optimized for hand coders, but as you will see, it's not very different from the default Designer workspace.
Figure 2.1. Dreamweaver supports two different workspaces for Windows users, and you can switch between them as needed.

NOTE
Macintosh users don't have the option of choosing a workspace. The environment for the Macintosh platform can be arranged to resemble either the Design or Coder style workspaces available in Windows (see Figure 2.2). The MDI is not available; multiple documents are displayed as individual floating windows.
Figure 2.2. Macintosh users don't have the same workspace as Windows users; however the panels can be arranged for a similar working environment.
[View full size image]

Figure 2.3. Throughout this book, the Coder workspace is used.
[View full size image]
