||Dreamweaver: A Visual Tool for Serious Web Coders|
|Subject:||does deserve more consideration|
The other two comments reflect the constant challenge of pursuading web app developers to consider DWMX. Yes, it used to be a web page tool (but the integration of Ultradev into MX changed that). Yes, the code it used to build may not have been what you would write, but it's gotten better. Yes, one may prefer it not generate or even change their code, but that's controllable as an option. More important, there are a lot of features it has that are as or more valuable than those the "generate code". Then again, all those "features" can cause it to perform poorly in some environments (depends on processor speed, complexity of the page being edited, and more). There are ways to improve its performance by changing various settings that may be better suited in some environments/uses than others. There are articles at Macromedia's DesDev that identify some of these as well as discuss other matters of transitioning to DWMX from other editors. See the MM DesDev site, http://www.macromedia.com/desdev/mx/dreamweaver/, for more.