Most Read This Week
One Product for All: Dreamweaver MX
One Product for All: Dreamweaver MX
By: John Wilker
Jul. 11, 2003 12:00 AM
Dreamweaver has been around for years. We've all seen it in some version or other, but it has finally come into its own in the most recent version, MX.
Dreamweaver has always been a tool for creating code. Early versions had some understanding of ColdFusion, and subsequent versions knew some ASP. However, it was always regarded as a designer's tool, having only (at first) a WYSIWYG interface and very poor interaction with non-HTML code (ASP, PHP, ColdFusion, etc...).
Times have changed, and so has Dreamweaver, all for the better. Dreamweaver has evolved from its humble (though widely popular) designer tool beginnings, going through a phase where it was split into two products - Dreamweaver and Dreamweaver UltraDev - to where it is now, one product for all - Dreamweaver MX.
Shortly after the merger of Allaire and Macromedia, ColdFusion Studio and HomeSite became HomeSite+. The push was for all of us to use Dreamweaver MX. HomeSite+ was added to Studio MX as an "extra." I say it's an extra because it's not billed as part of Studio MX and must be installed separately (HomeSite+ can be found in the HomeSite+ folder on the Studio MX CD. Dreamweaver was enhanced in its evolution to MX, bringing more of a developer interface with the available Code view for editing of raw code, as well as its traditional WYSIWYG development. Few programs can so easily move between two such different environments. Dreamweaver does so with relative ease.
HomeSite+ was initially a sour grape for most ColdFusion Studio users. It was not customizable and lacked the features we liked. A few months ago, however, an update was released that makes HomeSite+ a major option for those who do not want the overhead that comes with Dreamweaver. You can customize the menus, relocate panes, pretty much everything we missed in Studio (see Figure 1).
(The Updated HomeSite+ installer can be found at: www.macromedia.com/cfusion/tdrc/ index.cfm?product=homesite) For more information on HomeSite+ and its features, you can see the June 2003 CFDJ article, "Getting into HomeSite+," Volume 5, issue 6).
Neat New Things
Dreamweaver plays very well with others now. XML and Style Sheet documents can be seamlessly integrated into your code like never before. By linking a DTD (that Dreamweaver can access) to your page, the Attributes and values of the XML file become available. Context menus allow you to work with XML with ease. Gone are the days of having to remember all of the styles you defined in your CSS file. When you link it to your page, Styles become context for class and ID tag attributes. No more having to have the CSS file open all the time (see Figure 2).
The only drawback, or rather shortcoming, in this handy functionality is that modular code seems incompatible. Pages that have the basic HTML file tags in different modules or includes don't get the benefit of the context feature. Only pages with the complete HTML tags do. Hopefully this is something that will be addressed sooner or later.
Site vs Project
Sites allow you to manage your code locally, on the testing server, as well as from a remote location, all from the same pane. You can quickly switch between views and even promote code easily. The local files can be integrated with a source control tool like Microsoft's VSS.
A few neat side benefits to the new Site pane include the ability to automatically generate a site map - talk about handy! You can also have Dreamweaver manage design notes. These notes are kept locally to make notes on pages and the whole site. Dreamweaver manages them for you. You can also take stock of a site's assets with a single tab. The Assets tab allows you to group and view the parts of a site for easy digestion. View all the Flash movies, all the images. See all the links, even all the colors used in the site.
Templates Are Fine, Until Someone Gets Hurt
The use of template parameters allows developers the power to not have to hard-code image paths and links in the master template file. By defining these parameters as constants at the top of the page, subsequent changes won't need to be hunted down throughout the page, not to mention the rest of the site. All 14 (for example) links to the Clear shim graphic file can be updated by changing one line of code. This change can then be effected site wide by saving the changes to the master template.
I have come across only two drawbacks to using templates. One is in more complex sites where, say your <HTML> and <HEAD> tags are in a module and your closing </HTML> tag is in yet another module. Trying to save a template in this condition will result in an error. The code a template comes from must be well formed and intact within the single file.
The other drawback is that making changes to a template can be problematic in an enterprise environment. If a template itself needs to be changed - let's say I'm adding a new menu item to the navigation - every page based on the template has to be checked out of the code repository in order for the changes to propagate throughout the site.
The assumption here is that you're using some form of code repository; like Visual Source Safe, etc. For small operations and projects this is a less important issue. For the sites I maintain I'm the only developer, so the code is usually all checked out by me anyway and there's never anyone else working on it. For environments where a team is working on a site, one person making changes like that can be problematic if the others are not ready to check their changes back in, in order to let the template changer do his thing.
Probably the most natural use of templates is in corporate intranet environments, where you likely have many content contributors of various skill levels, and many departments with varying rights. Marketing may need rights to more pieces of an intranet, things like footers, headers, content that appears in more than one place, etc., while other departments like HR, may only need to update the static content within the benefits page.
Templates aren't a replacement or even a very good alternative to a true content management solution, but in smaller projects and teams they may be just what you need for a fraction of the cost.
More Than a Single Product, a Suite
Dreamweaver allows you to place an image placeholder in your code that will let you pop right into Fireworks, do what you have to, and pop back into Dreamweaver, a much more fluid interaction. The same type of action is available with Flash. This functionality goes both ways. From Fireworks you can save a sliced graphic right into Dreamweaver.
The Dreamweaver Era
Reader Feedback: Page 1 of 1
Subscribe to the World's Most Powerful Newsletters
Today's Top Reads